The "Response FIFO overflow" message reports an EACHIP memory buffer overflow condition.

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 "Response FIFO overflow" event occurs, a message similar to the following is reported:

Jul 23 19:04:43.744 router0: %PFE-3: fpc8 Cmerror Op Set: EA[0:0]: EA[0:0]: HMCIF Rx: Link0: Response FIFO 0 overflow

Indications:

1. Traffic impact or PFE packet forwarding is permanently compromised if errors are seen repeatedly

2. Major Alarm will be raised

This is due to a transient hardware issue.

{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 "Response FIFO overflow" message. Frequently, these events help identify the cause.

• No RMA is required

• FPC restart  during a maintenance window should clear this error.

• Contact your technical support representative if seen again as RMA might be needed

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