Description

This article explains the meaning of the "XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70138)" and "XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70137)" alarms that are seen on MX Series routers and indicates if any actions need to be taken.

Symptoms

Sanity Check point error logs mentioned below may found in /var/log/messages of the device.


Typically no user impact when transient.

It may lead to packet drops, CRC errors, or degraded forwarding performance if persistent or these error happens from time to time.

%PFE-5:fpc<#> CMError: /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70138), scope: pfe, category: functional, severity: minor, module: XMCHIP(1), type: FI: Minor link sanity check errors

%PFE-5: fpc<#> Performing action log for error /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70138) in module: XMCHIP(1) with scope: pfe category: functional level: minor

chassisd[24342]: %DAEMON-3-CHASSISD_FPC_ASIC_ERROR: <FPC 11> ASIC Error detected errorno 0x00070138 (null)

alarmd[26798]: %DAEMON-4: Alarm set: FPC id=167775080, color=YELLOW, class=CHASSIS, reason=FPC 11 Minor Errors

craftd[24345]: %DAEMON-4: Minor alarm set, FPC 11 Minor Errors

%PFE-5: fpc<#> Performing action cmalarm for error /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70138) in module: XMCHIP(1) with scope: pfe category: functional level: minor

: %PFE-3: fpc<#> Cmerror Op Set: XMCHIP(1): XMCHIP(1): FI: Link sanity checks - Type 2, Seq Number 194, Stream 169, Link0 0x1, Link1 0x60, Link2 0x2 (URI: /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR)

 

Similar error with different error-no may also seen in FPC

 

user@device> show chassis alarms no-forwarding
1 alarms currently active
Alarm time    Class Description
2024-11-29 05:06:06 UTC Minor FPC 0 Minor Errors


Nov 29 05:06:05 router %PFE-5: fpc<#> Error: /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70137), scope: pfe, category: functional, severity: minor, module: XMCHIP(1), type: FI: Minor link sanity check errors
Nov 29 05:06:05 router %PFE-5: fpc<#> Performing action log for error /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70137) in module: XMCHIP(1) with scope: pfe category: functional level: minor
Nov 29 05:06:06 router %PFE-5: fpc<#> Performing action cmalarm for error /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70137) in module: XMCHIP(1) with scope: pfe category: functional level: minor
Nov 29 05:06:06 router chassisd[9058]: %DAEMON-3-CHASSISD_FPC_ASIC_ERROR: <FPC 0> ASIC Error detected errorno 0x00070137 (null)
Nov 29 05:06:06 router alarmd[14732]: %DAEMON-4: Alarm set: FPC id=167772264, color=YELLOW, class=CHASSIS, reason=FPC 0 Minor Errors
Nov 29 05:06:06 router craftd[9062]: %DAEMON-4: Minor alarm set, FPC 0 Minor Errors
Nov 29 05:06:06 router : %PFE-3: fpc<#> Cmerror Op Set: XMCHIP(1): XMCHIP(1): FI: Link sanity checks - Type 4, Seq Number 75, Stream 21, Link0 0x1, Link1 0x4, Link2 0xa4 (URI: /fpc/<#>/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR)
Nov 29 05:07:00 router kernel: %KERN-3: nd6_cache_lladdr: no route to src fe80::a96:adff:fe41:e613 dst=ff02::1 received on ifl 551
Nov 29 05:07:55 router : %PFE-3: fpc<#> XMCHIP(1): XMCHIP(1): FI: Packet CRC error - Stream 21, Count 1
Nov 29 05:07:57 router : %PFE-3: fpc<#> XMCHIP(1): XMCHIP(1): FI: Packet CRC error - Stream 16, Count 1
Nov 29 05:07:58 router : %PFE-4: fpc<#> XMCHIP(1): XMCHIP(1): FI: Cell underflow at the state stage - Stream 21, Count 11
Nov 29 05:07:58 router : %PFE-3: fpc<#> XMCHIP(1): XMCHIP(1): FI: Packet CRC error - Stream 21, Count 1

Solution

XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK is a minor alarm indicating a transient hardware condition detected by the Fabric Interface (FI) link sanity-check mechanism on Juniper MX Series routers. 


This alarm signifies that the hardware has observed a potential issue related to link integrity or data corruption within the FI subsystem of the XMCHIP (the Packet Forwarding Engine ASIC).


A sanity-check failure typically points to a momentary or non‑persistent issue.

When this condition occurs for the first time, users may see a Minor alarm raised in the system.

If the alarm appears only once, it is generally safe to clear the error and continue monitoring the device.


You can clear the error using the following CLI command:


cli> clear chassis fpc errors all fpc-slot <fpc_slot_number>

 

If the error occurs multiple times or FPC is showing other errors also, Please restart the FPC during a maintenance window.

 

Execute:

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

Modification History

2024-12-03 : Updated with XMCHIP_CMERROR_FI_INT_REG_LINK_SANITY_CHECK_MINOR (0x70137) error no.

2024-07-04 : Article Created

2024-11-12 : dconejomora - adding MX480 to the affected platforms