This article explains the meaning of the "MQSS_CMERROR_LI_PROTECT_FSET_REG_CORRECTED_LI_ASYNC_SRAM (0x220586)" alarm that is seen on MX Series routers and indicates if any actions need to be taken.

The following log messages are seen on the Flexible PIC Concentrator (FPC):

Jan 4 07:06:39 XXXX : %PFE-3: fpc7 MQSS(1): LI-1: Protect: Multiple Errors 0x0 

Jan 4 07:06:39 XXXX : %PFE-5: fpc7 Error: /fpc/7/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_LI_PROTECT_FSET_REG_CORRECTED_LI_ASYNC_SRAM (0x220586), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: LI_PERR: Corrected: Asynchronous interface SRAM 

Jan 4 07:06:39 XXXX : %PFE-5: fpc7 Performing action log for error /fpc/7/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_LI_PROTECT_FSET_REG_CORRECTED_LI_ASYNC_SRAM (0x220586) in module: MQSS(1) with scope: pfe category: functional level: minor 

Jan 4 07:06:39 XXXX : %PFE-5: fpc7 Performing action cmalarm for error /fpc/7/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_LI_PROTECT_FSET_REG_CORRECTED_LI_ASYNC_SRAM (0x220586) in module: MQSS(1) with scope: pfe category: functional level: minor 

Jan 4 07:06:39 XXXX : %PFE-3: fpc7 Cmerror Op Set: MQSS(1): MQSS(1): LI-1: Protect: Parity error corrected for asynchronous interface SRAM  

Jan 4 07:06:39 XXXX chassisd[7212]: %DAEMON-3: <FPC 7> ASIC Error detected errorno 0x00220586 

Jan 4 07:06:39 XXXX alarmd[7578]: %DAEMON-4: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 7 Minor Errors

Jan 4 07:06:39 XXXX craftd[7217]: %DAEMON-4: Minor alarm set, FPC 7 Minor Errors

This is due to a transient hardware SRAM error with EACHIP.

The "Parity error corrected for buffer free list memory for bank" message reports a transient hardware error which was automatically corrected.

Since this is a major error "PFE Disable" action will be performed and the affected PFE will 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.

1. 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.
2. show log messages
3. show log chassisd
4. start shell network pfe <fpc#>
5. show nvram
6. show syslog messa

To clear this alarm, take the FPC offline, and bring it online again or restart the FPC during a maintenance window.

user@mx> request chassis fpc slot <slot number> offline
Wait for a few minutes.

user@mx> request chassis fpc slot <slot number> online

OR

Execute:

user@mx> request chassis fpc slot <slot number> restart