Description

The "HMCIF Rx retry attempts failed" message reports the EACHIP HMCIF receive link is not able to be established as expected.

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] .

.

Symptoms

When a "HMCIF Rx retry attempts failed"​ event occurs, a message similar to the following is reported:

Jul 23 19:08:19.262 router0: %PFE-3: fpc8 Cmerror Op Set: EA[0:0]: EA[0:0]: HMCIF Rx: Link0: HMCIF Rx retry attempts failed

Indications:

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

  2. Major Alarm will be raised

Solution

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 "HMCIF Rx retry attempts failed" 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

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.

 

Modification History

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