The chassis process (chassisd), which controls hardware components on the routing platform, detected that F chips were not yet initialized on the Control Board (CB).
The problem related to this syslog message is described in the following sections:
The CHASSISD_FASIC_INIT_ERROR message is logged each time that the chassis process detects that the F chips on a control board have not been initialized.
When a CHASSISD_FASIC_INIT_ERROR event occurs, a message similar to the following is reported:
chassisd: CHASSISD_FASIC_INIT_ERROR: Fchips were not configured yet
The cause of the F chip configuration failure may be due to the hardware being in a state that is preventing it from responding properly.
Examine the following output to help determine the cause of this message:
show log messages
show log chassisd
Look for any related events that occurred at or just before the CHASSISD_FASIC_INIT_ERROR message.
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:
start shell pfe network [cb#]
> show syslog messages
> show nvram
> show sib fchips all
request pfe execute command "show syslog messages" target [cb#]
request pfe execute command "show nvram" target [cb#]
request pfe execute command "sshow sib fchips 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.
During a maintenance window, as it will impact transit traffic, try the following:
- Reseat the control board in its slot.
- Move or swap the part, if possible, to an alternate slot.
- Replace the component with a spare.