Description

Why device doesn't show the HW monitoring code in "show chassis cluster status" when there is a major alarm on secondary node. Article also mention what will happen if device failover to the node with the hardware alarm. 

Symptoms

Node1 with major alarm do not have any impact on cluster status. 

 

root@KMLPNU01FW99> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-12-29 05:48:37 UTC  Major  FPC 1 PIC Fatal MSMI or catastrophic error from CPU

 

Cluster status:

Cluster ID: 1
Node   Priority Status               Preempt Manual   Monitor-failures

Redundancy group: 0 , Failover count: 0
node0  200      primary              no      no       None
node1  2        secondary            no      no       None

Redundancy group: 1 , Failover count: 0
node0  200      primary              no      no       None
node1  20       secondary            no      no       None

Redundancy group: 2 , Failover count: 0
node0  200      primary              no      no       None
node1  2        secondary            no      no       None

Solution

  • The hardware alarm observed is rare & not included in the list to trigger the HW Monitoring failure status in show chassis cluster status output. This is as per design.
  • In such incident, the FPCs continue rebooting and hence the failover will not happen. It would not permit a failover to the node with FPC in offline status.
  • Only if the FPC is online it can trigger the alarm here as it is related to CPU. 
  • As an action plan reseat the card, if alarm still persist please contact JTAC. 

Modification History

2025-03-03 : Article Created