Description

This article explains the meaning of the "MQSS Error code: 0x2204c4" alarm that is seen on MX Series routers and indicates if any actions need to be taken.


Apr 16 09:37:20.622 2024 labuser@labhost alarmd[92658]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 11 Major Errors - MQSS Error code: 0x2204c4

Apr 16 09:37:20.623 2024 labuser@labhost craftd[13452]: Major alarm set, FPC 11 Major Errors - MQSS Error code: 0x2204c4


Symptoms

MX router with MPC7E/8E/9E installed will report the following alarm. The exact MQSS module number, number of CP table and error codes may vary, the example below is shown for MPC9E in slot 11:


Below logs will be seen on message logs when parity errors are reported by FPCs 

Apr 16 09:37:20.518 2024 labuser@labhost fpc11 MQSS(1): FI: Protect 2: Multiple Errors 0x0 

Apr 16 09:37:20.618 2024 labuser@labhost inetd[13463]: Number of tftp connections at max limit (1)

Apr 16 09:37:20.618 2024 labuser@labhost chassisd[56151]: FPC 11 sent action 0x44 that is not configured 0x2 


Apr 16 09:37:20.622 2024 labuser@labhost alarmd[92658]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 11 Major Errors - MQSS Error code: 0x2204c4

Apr 16 09:37:20.623 2024 labuser@labhost craftd[13452]: Major alarm set, FPC 11 Major Errors - MQSS Error code: 0x2204c4


Apr 16 09:38:29.775 2024 labuser@labhost fpc11 Cmerror Op Set: MQSS(1): MQSS(1): FI: Protect 2: Parity error detected for bank 12 of CP table - data32_log_err 0x1000, data32_log_address 0x2dc 



The above errors will lead to PFE disable actions of the affected FPC#PFE

Apr 16 09:38:29.272 2024 labuser@labhost fpc11 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-11/0/6 293 

Apr 16 09:38:29.327 2024 labuser@labhost fpc11 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-11/0/7 294 

Apr 16 09:38:29.380 2024 labuser@labhost fpc11 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-11/0/8 295 

Apr 16 09:38:29.435 2024 labuser@labhost fpc11 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-11/0/9 296 


Apr 16 09:38:29.372 2024 labuser@labhost mib2d[92662]: SNMP_TRAP_LINK_DOWN: ifIndex 1685, ifAdminStatus up(1), ifOperStatus down(2), ifName et-11/0/6

Apr 16 09:38:29.758 2024 labuser@labhost mib2d[92662]: SNMP_TRAP_LINK_DOWN: ifIndex 1686, ifAdminStatus down(2), ifOperStatus down(2), ifName et-11/0/7

Apr 16 09:38:29.864 2024 labuser@labhost mib2d[92662]: SNMP_TRAP_LINK_DOWN: ifIndex 1687, ifAdminStatus up(1), ifOperStatus down(2), ifName et-11/0/8

Apr 16 09:38:29.864 2024 labuser@labhost mib2d[92662]: SNMP_TRAP_LINK_DOWN: ifIndex 1688, ifAdminStatus up(1), ifOperStatus down(2), ifName et-11/0/9

Solution

This is due to a transient hardware error condition within the EACHIP. A reboot of FPC is required to clear the alarm and also to bring up interfaces

Modification History

2024-04-26 : Article Created