This article explains the syslog MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FSET_REG_DETECTED_TCPNP_SRAM and how to address it
FPC 4 PFE 0 was disabled due to MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FSET_REG_DETECTED_TCPNP_SRAM major error. Below logs could be seen when the issue is encountered:
Jun 25 04:01:12 mx10008-re0 inetd[17152]: Number of tftp connections at max limit (1)
Jun 25 04:01:12 mx10008-re0 fpc4 MQSS(5): CPQF: Protect: Multiple Errors 0x100
Jun 25 04:01:12 mx10008-re0 fpc4 CMError: /fpc/4/pfe/0/cm/0/MQSS(5)/5/MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FSET_REG_DETECTED_TCPNP_SRAM (0
x220329), scope: pfe, category: functional, severity: major, module: MQSS(5), type: CPQF_SRAM_PAR_PROTECT: Detected: TCPNP SRAM, oc_category:
Jun 25 04:01:12 mx10008-re0 fpc4 Performing action get-state for error /fpc/4/pfe/0/cm/0/MQSS(5)/5/MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FS
ET_REG_DETECTED_TCPNP_SRAM (0x220329) in module: MQSS(5) with scope: pfe category: functional level: major, oc_category: default
Jun 25 04:01:52 mx10008-re0 fpc4 Performing action cmalarm for error /fpc/4/pfe/0/cm/0/MQSS(5)/5/MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FSET
_REG_DETECTED_TCPNP_SRAM (0x220329) in module: MQSS(5) with scope: pfe category: functional level: major, oc_category: default
Jun 25 04:01:52 mx10008-re0 fpc4 Performing action disable-pfe for error /fpc/4/pfe/0/cm/0/MQSS(5)/5/MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_
FSET_REG_DETECTED_TCPNP_SRAM (0x220329) in module: MQSS(5) with scope: pfe category: functional level: major, oc_category: default
Jun 25 04:01:52 mx10008-re0 fpc4 PFE 5: 'PFE Disable' action performed. Bringing down ifd et-4/5/0 528
Jun 25 04:01:52 mx10008-re0 fpc4 PFE 5: 'PFE Disable' action performed. Bringing down ifd et-4/5/1 529
Jun 25 04:01:52 mx10008-re0 alarmd[18154]: Alarm set: FPC id=150996072, color=RED, class=CHASSIS, reason=FPC 4 Major Errors
Jun 25 04:01:52 mx10008-re0 craftd[17147]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 4 silent: 0 short_
reason=FPC 4 Major Errors long_reason=FPC 4 Major Errors id=150996072 reason=150994944
Jun 25 04:01:52 mx10008-re0 craftd[17147]: Major alarm set, FPC 4 Major Errors
Jun 25 04:01:52 mx10008-re0 fpc4 PFE 5: 'PFE Disable' action performed. Bringing down ifd et-4/5/2 530
The log message indicates an SRAM parity error has been detected in TCPNP [Tail Chunk Pointer Next Pointer memory block] which is transient. However, as this is a major error "PFE Disable" action will be performed and the affected PFE will be disabled causing the interfaces under that PFE to go down.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
1) Collect the show command output.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages
show log chassisd
show system errors active detail fpc <fpc>
start shell network pfe
show nvram
show syslog messages
show cmerror module brief
show cmerror module <id> error 0x220329 <<<<<< replace id with module id from above output
exit
2) Analyze the show command output.
In the 'show log messages', review the events that occurred at or just before the appearance of the "MQSS_CMERROR_CPQF_SRAM_PAR_PROTECT_FSET_REG_DETECTED_TCPNP_SRAM" message. Frequently these events help identify the cause.
3) To clear the error condition and enable the affected PFE, reboot the FPC.
Take the FPC offline and bring it online again or restart the FPC during a maintenance window, to clear a possible improper state on the chip:
user@mx> request chassis fpc slot offline
Wait for a few minutes.
user@mx> request chassis fpc slot online
OR
user@mx> request chassis fpc slot restart
Please contact JTAC if the major error alarm returns even after the FPC reset.