The "EOP (End Of Packet) errors from input blocks" message reports a transient hardware issue.

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 "EOP errors from input blocks" event occurs, a message similar to the following is reported:

Indications:

• Service Impact: This message alone is not considered to be major, but informational. 
• No permanent impact of packet forwarding
• For each error entry, few data traffic packet drops can be seen, but the losses aren’t persistent and traffic should resume at 100% as before.

The cause is due to the XMCHIP detecting a temporary issue processing transit traffic.  

{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 "EOP errors from input blocks" message. Frequently these events help identify the cause.

   • No RMA required
   • No action is needed. This error alone won't trigger an alarm.
   • Contact your technical support representative if the issue is seen after an FPC restart .

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

2019-10-14: Article reviewed for accuracy; no changes required.