Description

A parity error is seen in the SRAM memory/MQSS chip of the PFE of the FPC.

This article will help troubleshoot a PFE ASIC syslog event.

Symptoms

The following was reported: 

fpc1 MQSS(0):MQSS(0): CMACPCS0: Protect: Parity error detected for FEC receive deskew SRAM (128x42) - data32 0x3c, data32_log_err 0x4,  data32_log_address 0x0
alarmd[4145]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 1 Major Errors
craftd[3629]:  Major alarm set, FPC 1 Major Errors

Indications:

  • Traffic impact at Ethernet port level 
  • Service impacting 
  • Major FPC alarm will be raised

Solution

According to the syslog, this error is caused by a transient hardware parity error in the SRAM memory. Traffic impact is seen on the ethernet port level. There is no impact at the PFE level. 

  • Collect the following 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
start shell network pfe <fpc#>
show nvram
show syslog messages
exit
  • No RMA is required
  • Perform a reboot of the FPC during a maintenance window.
  • Contact your JTAC Representative if this issue is seen frequently on the same ethernet ports even exist after FPC reboot.