Check for SCB Alarms
To check for SCB alarms:
- Display SCB Error Messages in the System Log File
- Display SCB Error Messages in the Chassis Daemon Log File
Display SCB Error Messages in the System Log File
Purpose
To determine the details of the SCB error messages in the system log file.
Action
An SCB failure can cause the fpx0 interface, the Ethernet connection to a management LAN, to go up and down.
To display SCB error messages in the system log file, use the following CLI command:
Sample Output
user@host> show log messages
Nov 19 04:35:29 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:29 host rpd[355]: task_connect: task BGP_209.192.168.0.21+179 addr 192.168.0.21+179: No route to host Nov 19 04:35:29 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:29 host rpd[355]: bgp_connect_start: connect 192.168.0.21 (Internal AS 209): No route to host Nov 19 04:35:29 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:29 host last message repeated 9 times Nov 19 04:35:29 host tnp.bootpd[369]: BOOTPD_BOOTSTRING: boot 1 scb.jbf Nov 19 04:35:29 host tnp.tftpd[389]: TFTPD_INFO: tftp read from addr 2 po rt 1024 file scb.jbf Nov 19 04:35:31 host tnp.tftpd[389]: TFTPD_INFO: sent 1348 blocks of 1024 and 1 block of 780 for file /usr/share/pfe/scb.jbf Nov 19 04:35:32 host mgd[387]: UI_CMDLINE_READ_LINE: user 'user', command 'show chassis scb ' Nov 19 04:35:34 host /kernel: fxp1: link media DOWN 10Mb / half-duplex Nov 19 04:35:34 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:34 host rpd[355]: EVENT <UpDown> fxp1.0 index 1 <Broadcast Multicast> address #0 0.80.82.18.14.83 Nov 19 04:35:34 host mib2d[354]: SNMP_TRAP_LINK_DOWN: ifIndex 2, ifAdminStatus up(1), ifOperStatus down(2), ifName fxp1 Nov 19 04:35:34 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:34 host last message repeated 4 times Nov 19 04:35:35 host /kernel: fxp1: media DOWN 100Mb / half-duplex Nov 19 04:35:36 host /kernel: fxp1: link UP 100Mb / half-duplex Nov 19 04:35:36 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:36 host rpd[355]: EVENT <UpDown> fxp1.0 index 1 <Up Broadcast Multicast> address #0 0.80.82.18.14.83 Nov 19 04:35:36 host mib2d[354]: SNMP_TRAP_LINK_UP: ifIndex 2, ifAdminStatus up(1), ifOperStatus up(1), ifName fxp1 Nov 19 04:35:36 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:36 host last message repeated 4 times Nov 19 04:35:37 host /kernel: fxp1: link media DOWN 10Mb / half-duplex Nov 19 04:35:37 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:37 host rpd[355]: EVENT <UpDown> fxp1.0 index 1 <Broadcast multicast> address #0 0.80.82.18.14.83 Nov 19 04:35:37 host mib2d[354]: SNMP_TRAP_LINK_DOWN: ifIndex 2, ifAdminStatus up(1), ifOperStatus down(2), ifName fxp1 Nov 19 04:35:37 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host Nov 19 04:35:37 host last message repeated 4 times Nov 19 04:35:38 host /kernel: fxp1: media DOWN 100Mb / full-duplex Nov 19 04:35:38 host /kernel: fxp1: link UP 100Mb / full-duplex Nov 19 04:35:38 host snmpd[353]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: sendto: No route to host
Meaning
The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. When the SCB fails, the fxp1 interface keeps going up and down. You can use the show log messages | match scb command to see error messages that are generated when an SCB fails or is offline. Use this information to diagnose a problem and to let the Juniper Networks Technical Assistance Center (JTAC) know what error messages were generated and the router events that occurred before and after the problem. For more information about system log messages, see the Junos OS System Log Messages Reference.
Display SCB Error Messages in the Chassis Daemon Log File
Purpose
To determine the details of the SCB error messages in the chassis daemon log file.
Action
To display SCB error messages in the chassis daemon (chassisd) log file, use the following command:
Sample Output
user@host> show log chassisdNov 19 04:09:02 closing alarmd connection. Nov 19 04:09:02 closing craftd connection. Nov 19 04:09:02 rcv: chassisd_ipc_dispatch() null ipc_pipe_read, closing connect ion Nov 19 04:09:02 alarmd connection completed Nov 19 04:09:02 craftd connection completed Nov 19 04:09:30 rcv reply: SCB Restart Nov 19 04:09:30 send: scb config cmd Nov 19 04:09:30 send: display hostname <ewr-edge-03>, uptime 16182073 seconds Nov 19 04:09:30 send: password = nnection. Nov 19 04:09:30 send: display unlockction. Nov 19 04:09:30 send: clear all chassis class alarmsc_pipe_read, closing connect Nov 19 04:09:30 send: set boolean type 0 slot 0 which 1 off Nov 19 04:09:30 rcv reply: Backplane MAC addrs recieved Nov 19 04:09:30 rcv reply: Backplane SRAM size 8388608 banks[ 1 1 1 1 ] Nov 19 04:09:30 jtree init (2097152 4) Nov 19 04:09:35 repead pid 15567, status 0 Nov 19 04:09:41 rcv reply: chassis info Nov 19 04:09:49 CHASSISD_EVENT: slot 0 restart Nov 19 04:09:50 pic online req, pic 0 type 515, fpc 0 Nov 19 04:09:50 send: fpc 0 pic 0 online ack Nov 19 04:09:51 CHASSISD_EVENT: slot 0 attach Nov 19 04:09:51 rcv reply: PIC attach fpc 0 pic 0 type 515 version 260 Nov 19 04:09:52 CHASSISD_EVENT: slot 1 restart Nov 19 04:09:53 pic online req, pic 0 type 515, fpc 1 Nov 19 04:09:53 send: fpc 1 pic 0 online ack Nov 19 04:09:54 CHASSISD_EVENT: slot 2 restart Nov 19 04:09:55 pic online req, pic 0 type 518, fpc 2 Nov 19 04:09:55 send: fpc 2 pic 0 online ack Nov 19 04:09:55 pic online req, pic 1 type 518, fpc 2 Nov 19 04:09:55 send: fpc 2 pic 1 online ack Nov 19 04:09:55 pic online req, pic 2 type 518, fpc 2 515 version 260 Nov 19 04:09:55 send: fpc 2 pic 2 online ackrt Nov 19 04:09:57 CHASSISD_EVENT: slot 3 restart, fpc 1 Nov 19 04:09:58 CHASSISD_EVENT: slot 4 restart Nov 19 04:09:58 CHASSISD_EVENT: slot 1 attach Nov 19 04:09:59 pic online req, pic 0 type 518, fpc 4
Meaning
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 “scb | kernel | tnp” is a search for error messages for the SCB, kernel, and Trivial Networking Protocol (TNP), and indicates communication issues between the Routing Engine and the Packet Forwarding Engine components.
