Description

This article explains the meaning of the following error seen on the device and indicates if any actions need to be taken: 

FPC 1 Routing Chip Errors Detected  - Error code: 1040

Symptoms

XX@XXXX> show chassis alarms
1 alarms currently active
Alarm time               Class  Description
2020-05-17 09:46:39 UTC  Minor  FPC 1 Routing Chip Errors Detected  - Error code: 1040

The following syslog messages are seen during the alarm: 

May 17 09:46:38  XXXX fpc1 RCHIP(1): 1 Discards - data error 
May 17 09:46:39  XXXX alarmd[1461]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 1 Routing Chip Errors Detected  - Error code: 1040
May 17 09:46:39  XXXX craftd[1462]:  Minor alarm set, FPC 1 Routing Chip Errors Detected  - Error code: 1040
May 17 09:46:40  XXXX fpc1 RCHIP(1): SRAM parity error at loc 0x745ae4 value 0x308d4c18 from key engine

Solution

The alarm is caused by a SRAM memory read parity error condition at loc 0x745ae4. The PFE has reported RCHIP memory parity error. A parity error is an error that results from irregular changes to data, as it is recorded when it is entered in memory. This error is usually transient in nature.

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.

    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 pfe network <fpc#>
show nvram
show syslog messages

  2. Analyze the show command output.

    In the 'show log messages' , review the events that occurred at or just before the appearance of the 'SRAM parity error at loc 0x745ae4 value 0x308d4c18 from key engine' message. Frequently, these events help identify the cause.

  3. Look for other events.

  4. FPC restart is recommended to clear this alarm and log message and repair the SRAM parity error.

    Command: 

    user@xx> request chassis fpc slot <slot number> offline     
Wait for a few minutes.
user@xx> request chassis fpc slot <slot number> online

    OR

    Execute: 

    user@xx> request chassis fpc slot <slot number> restart
No RMA is required

In case the syslog messages appear after the reboot, contact JTAC Support for further investigation.

Modification History

2020-10-30: Corrected Solution item 1 (start shell network pfe <fpc#> To: start shell pfe network <fpc#> )