This is article explains how to deal with the Major alarm on PTX10008 [EVO] SIB 0 FPC Link Errors
1 alarms currently active
Alarm time Class Description
2024-06-03 07:50:37 PDT Major SIB 0 FPC Link Errors
SIB 0
----------------------------------------------------------------
Error Name : sib_link_to_fpc_fault
Identifier : /sib/0/fabspoked-fchip/0/cm/0/fchip/0/sib_link_to_fpc_fault
Description : sib_link_to_fpc_fault
State : enabled
Scope : board
Category : internal
Level : major
Threshold : 1
Error limit : 144
Occur count : 6
Clear count : 5
Last occurred(ms ago) : 44081584
System Active Errors Detail Information
First Collect the RSI and /var/logs from the device with the below command outputs.
> show chassis alarms | no-more
> show chassis sibs | no-more
> show chassis sibs detail | no-more
> show chassis fabric topology | no-more
> show chassis fabric sibs | no-more
> show chassis fabric fpcs | no-more
> show chassis fabric errors fpc <slot-no> | no-more
> show chassis fabric errors sib <slot-no> | no-more
> show chassis fabric errors autoheal | no-more
> show chassis fabric summary | no-more
> show chassis fabric reachability | no-more
> show chassis fabric reachability detail | no-more
From SPMB[0-1] shell
> start shell pfe network spmb<0 and 1>
# show ccl statistics detail
# show ccl errors
From FPC shell
> start shell pfe network fpc<slot-no>
# show ccl links
You need to analyze the logs and identify which FPC and SIB have the errors on the link between them.
Feb 29 05:21:24.668 lab-re0 fpc0 cmqfx: Link errors detected for PFE 4 SIB 0 Plane 1
Feb 29 05:21:25.090 lab-re0 chassisd[22469]: CHASSISD_FM_ERROR: fm_qfx10_ev_fpc_state_handler: Packet Forwarding Engine got link errors (SIB#0, Packet Forwarding Engine 4 on FPC 0)
Feb 29 05:21:25.092 lab-re0 alarmd[22780]: Alarm set: FPC id=369098856, color=YELLOW, class=CHASSIS, reason=SIB 0 FPC Link Errors
Fabric management FPC state:
FPC #0
PFE #4
SIB0_FASIC1 (plane 1) Plane Disabled, Links Error
The above is showing issues with FPC towards plane 1, and plane 1 is part of SIB0.
To clear the alarm:
Offline the affected FPC
Offline the affected plane
Wait a few minutes
Online the affected plane
Online the affected FPC
request chassis fpc slot X offline
request chassis fabric plane X offline
Wait a couple of minutes
request chassis fabric plane X online
Wait until the plane is back online
request chassis fpc slot X online
The alarm should be cleared after that, and then monitoring should be done for a few days.
If the alarm comes back, you can try inserting the FPC into a different slot to see if the issue follows the FPC or the slot.
Either the SIB or FPC or both might have hardware issues and should be replaced.