The chassis process (chassisd), which controls hardware components on the routing platform, detected that SRAM (static random access memory) failed to initialize for the indicated F chip on the indicated Control Board (CB).
The CHASSISD_FASIC_SRAM_ERROR message is logged each time the chassis process fails to initialize the SRAM on an F chip installed on a control board.
When a CHASSISD_FASIC_SRAM_ERROR event occurs, a message similar to the following is reported:
|
1 |
CHASSISD_FASIC_SRAM_ERROR: Fchip (CB 0, ID 0): sram fuse initialization failed |
The cause of this message is due to either communication to the F chip hardware not completing properly, or the F chip being in a state that is not allowing the SRAM to be initialized.
Examine the following output to help determine the cause of this message:
|
1 2 3 4 |
show log messages show log chassisd show chassis alarms show pfe statistics error |
Look for any related events that occurred at or just before the CHASSISD_FASIC_SRAM_ERROR message. There may also be other alarms listed for the control board.
Since the message refers to a control board, then obtain the logs from that control board. This can be done with one of the following sets of commands:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
start shell pfe network [cb#] > show syslog messages > show nvram > show sib fchips all > show sib smfs_and_fchips all > show sib stats totals detail all > exit -OR-- request pfe execute command "show syslog messages" target [cb#] request pfe execute command "show nvram" target [cb#] request pfe execute command "show sib fchips all" target [cb#] request pfe execute command "show sib smfs_and_fchips all" target [cb#] request pfe execute command "show sib stats totals detail all" target [cb#] |
Be sure to replace the [cb#] entry above with the reference to the control board component that is reporting the log message, such as ‘cb0’ or ‘spmb1’. The component logs can then be reviewed to see if they report any internal errors.
Perform these steps:
1. During a maintenance window, as it will impact transit traffic, try the following:
- Reset the control board.
- Reseat the control board in its slot.
- Move or swap the part, if possible, to an alternate slot.
- Replace the component with a spare.
2. If the failure messages continue, open a case with Juniper technical support representative to investigate the issue further.
