The chassis process (chassisd) took the indicated component (field-replaceable unit, or FRU) offline for the indicated reason.
When a CHASSISD_FRU_OFFLINE_NOTICE event occurs, a message similar to the following is reported:
chassisd[1306]: %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 1 offline: Offlined by cli command chassisd[3130]: CHASSISD_FRU_OFFLINE_NOTICE: Taking CB 1 offline: None chassisd[1310]: %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking SCG 1 offline: Sonet out clock not present CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Error chassisd[2970]: %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking SFM 1 offline: shutdown due to error chassisd[1072]: %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 1 offline: Power cycle chassisd[1100]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 5 offline: Restarting unresponsive board chassisd[4564]: CHASSISD_FRU_OFFLINE_NOTICE: Taking CB 1 offline: No power CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 2 offline: ISSU Failure chassisd[4662]: %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 5 offline: Removal %DAEMON-5-CHASSISD_FRU_OFFLINE_NOTICE: Taking SIB 0 offline: Reconnect
The chassisd process can take an FRU component offline for many reasons, from being the result of a CLI command, to a possible software or hardware error. The exact cause needs to be investigated by an examination of the associated device logs.
Perform these steps to determine the cause and resolve the problem (if any):
1. Collect the show command output to help determine the cause of this message.
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
2. Analyze the show command output. Look for any related events that occurred at or just before the
CHASSISD_FRU_OFFLINE_NOTICE
message.
If the syslog message is “Offlined by cli command,” then obviously this is expected.
3. During a maintenance window, as it will impact transit traffic, try rebooting and/or reseating the FRU component. In some instances, the network device will need to be rebooted. If a reseat of the component is done, use a flashlight when the component is removed to check for bent pins on the associated connector.