RKME is a key match engine located in the FPC SRCHIP/RCHIP hardware. The RKME engine received the ‘interrupt shown’ error.
When an RKME event occurs, a message similar to the following is reported:
fpc0 SRCHIP(1): RKME int_status1 0x100 fpc4 SRCHIP(0): %PFE-3: RKME int_status1 0x100
The cause could be due to poor link quality on one of the FPC transit traffic connections, FPC hardware in an improper operating state, or software pointer corruption in the jtree table.
Examine the following outputs to help determine the cause of this message:
show log messages show log chassisd show pfe statistics traffic start shell pfe network fpc# show pfe manager statistics show ttp statistics show pfe statistics traffic show pfe statistics error show rchip 0 statistics errors show rchip 1 statistics errors show syslog messages show nvram sh ifd brief sh ifl brief sh jtree # debug ip check jumptable sh jtree # debug ip check table sh jtree # memory sh jtree # memory extensive sh rsmon sh nh fab nh 0 exit
Look for any related events, which occurred at or just before the RKME message, in the syslog and chassisd outputs.
Perform these steps:
1. If the Junos version is between 10.2 and 11.2 inclusive, upgrade to one of the following builds or higher: 11.3R1 10.4R4 10.4R3 10.3R4 10.2R4 11.2R1 11.1R2
2. If the message was preceeded by an interface flap, then upgrade to one of the following builds or higher: 10.4R9 10.4R8 11.1R7 11.2R5 11.4R2 12.1R1
3. Check the link(s) on the FPC to see if a particular connection has many link flaps or other connection problems. Poor link quality can produce this message.
4. Perform the following procedure during a maintenance window, as it will impact transit traffic:
- Reset the FPC (rebuilds jtree table on the FPC).
- Swap the FPC with a spare (checks to see if it is a hardware issue).
- Reboot the Routing Engine (rebuilds jtree table in RE memory).
5. If the log messages continue, open a case with your technical support representative to further investigate the issue.