This article explains the meaning of the "CMERROR_MQ_FI_INT_REG_LINK_SANITY_CHECK_MAJOR (0x30065)" 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):

Mar 28 22:59:58 CHASSISD_FPC_ASIC_ERROR: <FPC 7> ASIC Error detected errorno 0x00030065 (null)

Mar 28 23:00:11 send: red alarm set, device FPC 7, reason FPC 7 Major Errors

Mar 28 23:00:11 send: red alarm set, device FPC 7, reason FPC 7 Major Errors

Mar 28 22:59:58 RE0 fpc7 MQCHIP(3) FI Link sanity checks, type 4 seq 542 stream 29 link0 32769 link1 3 link2 4 

Mar 28 22:59:59 RE0 fpc7 Error: /fpc/7/pfe/0/cm/0/MQ_Chip(3)/3/CMERROR_MQ_FI_INT_REG_LINK_SANITY_CHECK_MAJOR (0x30065), scope: pfe, category: functional, severity: major, module: MQ Chip(3), type: FI: Major link sanity check errors 

Mar 28 22:59:59 RE0 fpc7 Performing action log for error /fpc/7/pfe/0/cm/0/MQ_Chip(3)/3/CMERROR_MQ_FI_INT_REG_LINK_SANITY_CHECK_MAJOR (0x30065) in module: MQ Chip(3) with scope: pfe category: functional level: major 

Mar 28 23:00:01 RE0 fpc7 Performing action get-state for error /fpc/7/pfe/0/cm/0/MQ_Chip(3)/3/CMERROR_MQ_FI_INT_REG_LINK_SANITY_CHECK_MAJOR (0x30065) in module: MQ Chip(3) with scope: pfe category: functional level: major 

Mar 28 23:00:11 RE0 fpc7 Performing action cmalarm for error /fpc/7/pfe/0/cm/0/MQ_Chip(3)/3/CMERROR_MQ_FI_INT_REG_LINK_SANITY_CHECK_MAJOR (0x30065) in module: MQ Chip(3) with scope: pfe category: functional level: major 

Mar 28 23:00:11 RE0 fpc7 Cmerror Op Set: MQ Chip(3): MQCHIP(3) FI Link sanity checks, type 4 seq 542 stream 29 link0 32769 link1 3 link2 4  

The cause is due to an incremented Link Sanity Check counter in the MQ chip.This counter increments if the hardware detects a possible corrupted packet.This is a read-to-clear type register. Once the software reads it, then it's cleared automatically.

A single occurrence of this syslog, not seen with other events, indicates a one-time hardware error indicating a transient issue. We can CLI command "clear chassis fpc errors fpc-slot <slot#> all" to clear the error.

If you are seeing the error continuously. Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.

a) Look for other events around the same time the alarm occurred.

b) If the error occurs multiple times, 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 MQ chip.

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

Wait for a few minutes.

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

OR

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