Description

ACX7100 displaying log message EVO_PFEMAND_ASIC_PROGRAM_FAILED repeatedly.

Symptoms

This applies to all ACX EVO platforms (and not ACX Junos platforms)

The errors with no functional impact are seen due to different sequencing of events from upper layers.

 

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

evo-pfemand[10272]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - entry doesn't exist in hardware

 

There are no functional impacts.

 

Solution

This issue is resolved in 23.2R2-EVO and 23.3R1-EVO.

 

However, since there are no functional impacts, the customer can choose to block out these error messages from appearing in the log using the following KB https://supportportal.juniper.net/s/article/Junos-Platform-Example-How-to-prevent-certain-syslog-messages-from-being-written-to-the-log-file?language=en_US

Modification History

2024-01-31 : Article Created