The "FI Link sanity checks" message reports a transient hardware issue.

 chassisd[7240]: %DAEMON-3: <FPC 11> ASIC Error detected errorno 0x00070137 
 chassisd[7240]: %DAEMON-3: <FPC 11> ASIC Error detected errorno 0x00070137 
 %PFE-3: fpc11 Cmerror Op Set: XMCHIP(2): XMCHIP(2): FI: Link sanity checks - Type 4, Seq Number 604, Stream 207, Link0 0x4, Link1 0xc, Link2 0xe000  
 %PFE-3: fpc11 XMCHIP(2): XMCHIP(2): FI: Reorder cell timeout - Stream 206, Count 32 
 %PFE-3: fpc11 XMCHIP(2): XMCHIP(2): FI: Packet CRC error - Stream 205, Count 1 
 %PFE-3: fpc11 XMCHIP(2): XMCHIP(2): FI: Aliasing on allocates error - Pipe count 0, Count 2

This is a Troubleshooting Article for a PFE ASIC Syslog Event.

To view other documented syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events  [juniper.net].

When a "FI Link sanity checks" event occurs, a message similar to the following is reported:

 %PFE-3: fpc11 XMCHIP(2): XMCHIP(2): FI: Cell underflow at the state stage - Stream 206, Count 1 

1. Traffic impact depends on the counter value and the frequency. Each counter is a cell drop and Link Sanity check event will have a very brief (few msec) traffic interruption for the PFE reporting.
2. If this event happens several times in sequence there might an exposure. Traffic flows passing from the fabric side for this PFE entity might experience higher latency up to 500msec, without traffic drop and restarting the FPC is strongly recommended
3. This is minor alarm as single event does not cause permanent operational impact. A major alarm will be reported when seen with  KB31611 - Syslog message: XMCHIP.*FI.*Cell underflow at the state stage  [juniper.net].

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.

   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 pfe network <fpc#>
   show nvram
   show syslog messages
   exit

    

2. Analyze the show command output.

   In the 'show log messages', review the events that occurred at or just before the appearance of the "FI Link sanity checks" message. Frequently these events help identify the cause.

   • No RMA required.
   • Restart the MPC and monitor the errors.
   • Contact your technical support representative if the issue is seen after a FPC restart.