Users may see logs such as "set report-fabric-desterr-on-asic-wedge to 0" during a Routing Engine switchover. This article explains that these messages are informational only and can be safely ignored.

 

During an RE switchover, logs like the following may be seen:

Oct  9 01:00:50.861 2020  router : %PFE-6: member1-fpc6 set report-fabric-desterr-on-asic-wedge to 0
Oct  9 01:01:44.101 2020  router : %PFE-6: member1-fpc1 set report-fabric-desterr-on-asic-wedge to 0
Oct  9 01:01:44.317 2020  router : %PFE-6: member1-fpc0 set report-fabric-desterr-on-asic-wedge to 0

 

These logs are informational messages and are seen when syslog is configured with "pfe" set to level "info" or higher. For example:

set system syslog file messages pfe info

This message was added as part of the changes made by PR1184761, where the self-ping monitoring system for FPCs was decoupled from the Fabric Healing Mechanism.

Prior to the changes in this PR, the default behavior was to report a self ping failure as a destination error on the fabric, which would trigger the Fabric Healing Mechanism. After the changes in this PR, the default behavior is to not report a destination error and instead disable the affected PFE.

A hidden knob was also added to allow users to revert to the original behavior set chassis fabric degraded report-desterr-on-asic-wedge.

Note: Unless directed by JTAC, it is recommended to retain the default behavior.

These log messages indicate whether a self-ping failure will report as a destination error on the fabric based on the knob above. The default behavior is to not report a fabric destination error upon detection of a self-ping failure indicated by the value zero(0) in the log message.