The "LKUP_ASIC_JGCI_MAJOR_CRC_ERROR (0x40050)" message reports a transient hardware parity CRC error.
This is a Troubleshooting Article for a PFE ASIC Syslog Event mentioned above.
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 an "LKUP_ASIC_JGCI_MAJOR_CRC_ERROR (0x40050)" event occurs, a message similar to the following is reported:
"Aug 9 02:05:34 router0 fpc0 CMError: /fpc/0/pfe/0/cm/0/XL[0:0]/0/LKUP_ASIC_JGCI_MAJOR_CRC_ERROR (0x40050), scope: pfe, category: functional, severity: major, module: XL[0:0], type: JGCI CRC Errors"
Indications:
The cause is due to a transient hardware parity error detected on the chip. If there is a service impact, then other events will be reported.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
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.
Analyze the show command output.
In the 'show log messages', review the events that occurred at or just before the appearance of the "LKUP_ASIC_JGCI_MAJOR_CRC_ERROR (0x40050" message. Frequently these events help identify the cause.
• If the occurrences are few, FPC restart during the maintenance window is required to clear the alarms.
request chassis fpc slot # offline
*** 5 sec wait***
request chassis fpc slot # online
( # indicates slot number of FPC)
Contact your Juniper support representative JTAC Support if the issue is seen after a FPC restart.