Step 3: Display SFM Error Messages in the Chassis Daemon Log File

The chassis daemon (chassisd) log file keeps track of the state of each chassis component.

Action

To display the SFM error messages logged in the chassis daemon, use the following CLI command:

user@host> show log chassisd

Sample Output

user@host> show log chassisd

Jun 11 20:50:16 mcs_intr_handler fpm_mcsfd 10

Jun 11 20:50:16 mcs_intr mcs_ints_pending 0x7cbf20 button_status 0x0

Jun 11 20:50:16 bp_handle_button_intr button status 0x0

Jun 11 20:50:16 mcs_intr_handler fpm_mcsfd 10

Jun 11 20:50:16 mcs_intr mcs_ints_pending 0x7cbf20 button_status 0x8

Jun 11 20:50:16 bp_handle_button_intr button status 0x8

Jun 11 20:50:16 mcs_intr_handler fpm_mcsfd 10

Jun 11 20:50:16 mcs_intr mcs_ints_pending 0x7cbf20 button_status 0x8

Jun 11 20:50:16 bp_handle_button_intr button status 0x8

Jun 11 20:50:16 received second FPM key press, clearing timer!

Jun 11 20:50:18 bp_button_timer: taking sfm 1 offline

Jun 11 20:50:18 take_sfm_offline - slot 1 reason 7

Jun 11 20:50:18 cleaning up sfm 1 connection

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Blue LED Off [0x16]

Jun 11 20:50:18 SPP 1 - Blue LED Off

Jun 11 20:50:18 send: fpc 0, sfm 1 offline

Jun 11 20:50:18 send: fpc 1, sfm 1 offline

Jun 11 20:50:18 send: fpc 2, sfm 1 offline

Jun 11 20:50:18 send: fpc 6, sfm 1 offline

Jun 11 20:50:18 send: fpc 7, sfm 1 offline

Jun 11 20:50:18 fpc 2, sfm 1 offline ack

Jun 11 20:50:18 fpc 2, sfm 1 offline ack, online 0xc7 online-acks 0x4

Jun 11 20:50:18 fpc 1, sfm 1 offline ack

Jun 11 20:50:18 fpc 1, sfm 1 offline ack, online 0xc7 online-acks 0x6

Jun 11 20:50:18 fpc 0, sfm 1 offline ack

Jun 11 20:50:18 fpc 0, sfm 1 offline ack, online 0xc7 online-acks 0x7

Jun 11 20:50:18 fpc 7, sfm 1 offline ack

Jun 11 20:50:18 fpc 7, sfm 1 offline ack, online 0xc7 online-acks 0x87

Jun 11 20:50:18 fpc 6, sfm 1 offline ack

Jun 11 20:50:18 fpc 6, sfm 1 offline ack, online 0xc7 online-acks 0xc7

Jun 11 20:50:18 sfm_offline_now plane 1 conn 0x8152638

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Assert PLL Bypass [0x13]

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Assert Board Reset [0x2e]

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Assert ASIC Reset [0x28]

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Disable Power [0x10]

Jun 11 20:50:18 SPP 1 - Disable Power [addr 0x9 cmd 0x10]

Jun 11 20:50:18 CMB readback SPP 1 [0xe9, 0xf2] -> 0x26

Jun 11 20:50:18 power disable verified, SPP 1

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Blue LED Off [0x16]

Jun 11 20:50:18 SPP 1 - Blue LED Off

Jun 11 20:50:18 CMB cmd to SPP 1 [0xe9], Green LED Off [0x1a]

Jun 11 20:50:18 SPP 1 - Green LED Off

Jun 11 20:50:18 check_sfm_online_alarm: present 0xf waiting 0x0 online 0xd

Jun 11 20:50:18 send_pfe_status(): sfm 0, sfm_online_mask 0xd fpc_online_mask 
0xc7

Jun 11 20:50:18 send_pfe_status(): sfm 2, sfm_online_mask 0xd fpc_online_mask 
0xc7

[...Output truncated...]

What It Means

The chassisd database provides the date, time, and a component status message. The chassisd database is dynamic. It is initialized at router startup and is updated when components are added or removed. You can search for multiple items in the chassisd log file by using the | match "item |item |item" command. For example, | match "sfm|kernel|tnp"is a search for error messages for the SFM, kernel, and Trivial Networking Protocol (TNP), and indicates communication issues between the Routing Engine and the Packet Forwarding Engine components.