This article explains the recovery of the reported SIB fault Major alarm because of failure in outq LLM SRAM and failed to read outqg and outqd protect interrupt registers.

=========================
The following alarm was raised
=========================

root@switch-re>show chassis alarms no-forwarding 

1 alarms currently active

Alarm time         Class  Description

2024-08-22 02:40:12 UTC  Major  SIB 3 Fault

=====================================================================================
The logs indicate the SIB3 detected error on outq LLM SRAM and failed to read outqg and outqd protect interrupt registers
=====================================================================================

Aug 22 02:40:12 switch-re0 spmb0 SIB3_PF_1 pfchip_outqr_scan_error_reg: Detected outq Req LLM SRAM corrected llm err.

Aug 22 02:40:12  switch-re0 spmb0 SIB3_PF_1 pfchip_outqg_scan_error_reg: failed to read outqg protect interrupt registers, reg=0x3020640. 

Aug 22 02:40:12  switch-re0 spmb0 SIB3_PF_1 pfchip_outqd_scan_error_reg: failed to read outqd protect interrupt registers, reg=0x3000640. 

Aug 22 02:40:12  switch-re0 chassisd[8894]: CHASSISD_FM_SIB_ERROR: Fabric management error for SIB 3: Set SIB to FAULT (Fault due to PIO errors)

Aug 22 02:40:12  switch-re0 chassisd[8894]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Failed (jnxFruContentsIndex 15, jnxFruL1Index 4, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName SIB 3, jnxFruType 9, jnxFruSlot 3)

Aug 22 02:40:12  switch-re0 alarmd[24246]: Alarm set: SIB id=16778100, color=RED, class=CHASSIS, reason=SIB 3 Fault

-Most of the time these errors are transient in nature, removal and insertion of the corresponding SIB resolves the issue.

-If removal and insertion of the SIB did not help, replacement of the SIB was to be done.