Description

This article describes a scenario when FPC Minor Error "XMCHIP(*): XMCHIP(*): WI<>: WI CPQ Free Pointer SRAM Protect: Multiple Errors" is reported on MX router and clarifies whether any actions need to be taken.

Symptoms

MX router reports the following FPC Minor Errors alarm, in the examples below this error was reported by MPC5-EQ in slots 3 and 9. Please note that the error-id for XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM may vary depending on the JUNOS release version. In earlier releases it was 0x7032c and at the moment of writing it is 0x7035e.

  • show system alarms
user@device> show system alarms
1 alarms currently active
Alarm time Class Description
<date> <time> Minor FPC 9 Minor Errors
      • show chassis error active detail fpc-slot <>
      user@device> show chassis errors active detail fpc-slot 9
      Slot 9
      
      --------------------------------------------------
      Location      : FPC 9
      Identifier    : /fpc/9/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM
      Error         : XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM
      Scope         : pfe
      Category      : functional
      Severity      : Minor
      Details       : WI_PROTECT: Detected: Parity error for wicpq free pointer SRAM
      Count         : 1
      Support       : No help info provided
      • show log messages
      %PFE-3: fpc9 XMCHIP(1): XMCHIP(1): WI1: WI CPQ Free Pointer SRAM Protect: Multiple Errors 0x0
      %DAEMON-3: <FPC 9> ASIC Error detected errorno 0x0007035e
      %DAEMON-4: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 9 Minor Errors
      %DAEMON-4: Minor alarm set, FPC 9 Minor Errors
      %PFE-5: fpc9 CMError: /fpc/9/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7035e), scope: pfe, category: functional, severity: minor, module: XMCHIP(1), type: WI_PROTECT: Detected: Parity err
      %PFE-5: fpc9 Performing action log for error /fpc/9/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7035e) in module: XMCHIP(1) with scope: pfe category: functional level: minor
      %PFE-5: fpc9 Performing action cmalarm for error /fpc/9/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7035e) in module: XMCHIP(1) with scope: pfe category: functional level: minor
      %PFE-3: fpc9 Cmerror Op Set: XMCHIP(1): XMCHIP(1): WI1: WI CPQ Free Pointer SRAM Protect: Parity error (0x800)  (URI: /fpc/9/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM)
      • show log messages (in earlier releases)
      %PFE-3: fpc3 XMCHIP(0): XMCHIP(0): WI1: WI CPQ Free Pointer SRAM Protect: Multiple Errors 0x40
      %DAEMON-3: <FPC 3> ASIC Error detected errorno 0x0007032c
      %DAEMON-4: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 3 Minor Errors
      %DAEMON-4: Minor alarm set, FPC 3 Minor Errors
      %PFE-5: fpc3 Error: /fpc/3/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7032c), scope: pfe, category: functional, severity: minor, module: XMCHIP(0), type: WI_PROTECT: Detected: Parity error
      %PFE-5: fpc3 Performing action log for error /fpc/3/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7032c) in module: XMCHIP(0) with scope: pfe category: functional level: minor
      %PFE-5: fpc3 Performing action cmalarm for error /fpc/3/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM (0x7032c) in module: XMCHIP(0) with scope: pfe category: functional level: minor
      %PFE-3: fpc3 Cmerror Op Set: XMCHIP(0): XMCHIP(0): WI1: WI CPQ Free Pointer SRAM Protect: Parity error (0x40)

      Solution

      The WI CPQ Free Pointer SRAM Protect is a transient hardware error condition and does not cause any operational impact. The cause is due to a transient hardware parity error detected on the chip. If there is a service impact, then other events will be also reported.

       

      Indications:

      • A single occurrence of the syslog, not seen with other events, indicates a one-time hardware error. Multiple continuous occurrences indicate persistent underlying issues.
      • No permanent impact of packet forwarding.
      • A minor alarm will be raised.

      In the output of 'show log messages', review the events that occurred at or just before the appearance of the "WI CPQ Free Pointer SRAM Protect: Parity error" message. Frequently these events help identify the cause.
       

      1. ​No RMA is required.
      2. With a single occurrence, the alarm can be cleared using the command clear chassis fpc errors fpc-slot <> all
      3. The multiple continuous occurrences of errors This requires the FPC reboot during the MW window to clear the alarms.

      If the issue remains unresolved, please contact JTAC for further investigation.

      Modification History

      2024-10-31: Major formatting changes

      2024-03-08: Article Created