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

Action

To display FPC error messages in the chassisd log file, use the following CLI command:

user@host> show log chassisd | match "fpc | kernel | tnp"

Sample Output

user@host> show log chassisd | match "fpc | kernel | tnp"

Nov 11 15:58:31 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=0, tnpaddr=2

Nov 11 15:58:42 m40-2 tnp.bootpd[2497]: BOOTPD_BOOTSTRING: Boot string: boot 1 
fpc.jbf

Nov 11 15:58:42 m40-2 tnp.tftpd[2647]: TFTPD_CONNECT_INFO: tftp read from addr 
16 port 1024 file fpc.jbf

Nov 11 15:58:42 m40-2 tnp.bootpd[2497]: BOOTPD_BOOTSTRING: Boot string: boot 1 
fpc.jbf

Nov 11 15:58:43 m40-2 tnp.tftpd[2649]: TFTPD_CONNECT_INFO: tftp read from addr 
17 port 1024 file fpc.jbf

Nov 11 15:58:44 m40-2 tnp.tftpd[2651]: TFTPD_CONNECT_INFO: tftp read from addr 
18 port 1024 file fpc.jbf

Nov 11 15:58:45 m40-2 tnp.tftpd[2653]: TFTPD_CONNECT_INFO: tftp read from addr 
19 port 1024 file fpc.jbf

Nov 11 15:58:46 m40-2 tnp.tftpd[2655]: TFTPD_CONNECT_INFO: tftp read from addr 
20 port 1024 file fpc.jbf

Nov 11 15:58:47 m40-2 tnp.tftpd[2657]: TFTPD_CONNECT_INFO: tftp read from addr 
21 port 1024 file fpc.jbf

Nov 11 15:58:47 m40-2 fpc6 TFTP Error - Timeout

Nov 11 15:58:47 m40-2 fpc7 TFTP Error - Timeout

Nov 11 15:58:48 m40-2 tnp.tftpd[2659]: TFTPD_CONNECT_INFO: tftp read from addr 
22 port 1024 file fpc.jbf

Nov 11 15:58:49 m40-2 tnp.tftpd[2661]: TFTPD_CONNECT_INFO: tftp read from addr 
23 port 1024 file fpc.jbf

Nov 11 15:58:50 m40-2 tnp.tftpd[2663]: TFTPD_CONNECT_INFO: tftp read from addr 
22 port 1024 file fpc.jbf

Nov 11 15:58:50 m40-2 fpc6 TFTP read - saw block 1, expected 572

Nov 11 15:58:51 m40-2 tnp.tftpd[2665]: TFTPD_CONNECT_INFO: tftp read from addr 
23 port 1024 file fpc.jbf

Nov 11 15:58:51 m40-2 fpc6 TFTP read - saw block 1, expected 731

Nov 11 15:58:51 m40-2 fpc7 TFTP read - saw block 1, expected 200

Nov 11 15:58:52 m40-2 fpc6 TFTP read - saw block 1, expected 775

Nov 11 15:58:52 m40-2 fpc7 TFTP read - saw block 1, expected 265

Nov 11 15:58:52 m40-2 tnp.tftpd[2647]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:58:53 m40-2 fpc6 TFTP read - saw block 1, expected 782

Nov 11 15:58:53 m40-2 fpc7 TFTP read - saw block 1, expected 340

Nov 11 15:58:54 m40-2 fpc7 TFTP read - saw block 1, expected 428

Nov 11 15:58:54 m40-2 fpc6 TFTP read - saw block 1, expected 1016

Nov 11 15:58:55 m40-2 fpc7 TFTP read - saw block 1, expected 531

Nov 11 15:58:57 m40-2 tnp.tftpd[2649]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:58:57 m40-2 tnp.tftpd[2651]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:58:58 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=1, tnpaddr=16

Nov 11 15:58:58 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 0 restart

Nov 11 15:59:00 m40-2 tnp.tftpd[2653]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:59:00 m40-2 tnp.tftpd[2659]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:59:01 m40-2 tnp.tftpd[2655]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:59:02 m40-2 tnp.tftpd[2661]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:59:02 m40-2 tnp.tftpd[2657]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks 
of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'

Nov 11 15:59:03 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=2, tnpaddr=17

Nov 11 15:59:03 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 1 restart

Nov 11 15:59:03 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=3, tnpaddr=18

Nov 11 15:59:03 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 2 restart

Nov 11 15:59:06 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=4, tnpaddr=19

Nov 11 15:59:06 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 3 restart

Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=5, tnpaddr=22

Nov 11 15:59:07 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 6 restart

Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=6, tnpaddr=20

Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 4 restart

Nov 11 15:59:08 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=7, tnpaddr=23

Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 7 restart

Nov 11 15:59:09 m40-2 /kernel: pfe_listener_connect: conn established: listener 
idx=8, tnpaddr=21

Nov 11 15:59:09 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 5 restart

What It Means

The chassisd log file is a database that 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. The sample command output shows the results of a multiple item search in the log file ("fpc | kernel | tnp"): error messages for the FPC, kernel, and Trivial Networking Protocol (TNP) that indicate communication issues between the Routing Engine and the Packet Forwarding Engine components.