The "trap-info logic not initialized" message reports a transient software initialization issue while system has encountered other Hardware issues during boot-up.

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 "trap-info logic not initialized" event occurs, a message similar to the following is reported:

Feb 27 12:10:00 router0 fpc2 LUCHIP(1): Display trap-info logic not initialized.

Indications:

• May impact service 
• Other syslog messages will provide more information

This is due to LUCHIP software not initializing the hardware as expected. Other system messages will provide more information on the root cause.

{DIDYOUKNOWSERVICENOWTOKEN.EN_US}

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.

   {SYSLOGSERVICENOWTOKEN.EN_US}

   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 network pfe <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 "trap-info logic not initialized" message. Frequently, these events help identify the cause.

• ​Perform  FPC restart to recover
• If the error is seen again, contact your technical support representative for further guidance.

This article is indexed in  KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag LUCHIPTSG

2022-10-21 - Publish KB as public - missing from previous review
2019-10-14: Article reviewed for accuracy; no changes required.