Verifying Craft Interface Failure

To verify craft interface failure:

1. Displaying Craft Interface Alarms
2. Display Craft Interface Error Messages in the System Log File
3. Displaying Craft Interface Messages in the Chassis Daemon Log File
4. Displaying Craft Interface Hardware Information

Displaying Craft Interface Alarms

Purpose

A craft interface failure generates a red or yellow alarm, or both. For information about conditions that trigger craft interface alarms.

Action

To display a craft interface alarm, use the following command:

Sample Output

user@host>  show chassis alarms
1 alarms currently active
Alarm time               Class  Description
2002-05-09 00:00:54 UTC  Major  fxp0: ethernet link down

user@host>  show chassis alarms
2 alarms currently active
Alarm time               Class  Description
2002-06-07 18:20:00 UTC  Minor  Craft Failure
2002-06-07 18:20:00 UTC  Minor  Front Top Fan Absent

Meaning

(M20 router) If the craft interface fails or is removed, you see an alarm. For example, if you remove the craft interface, a major management Ethernet interface down alarm is generated. The Ethernet link to the router is down. The Ethernet management interface, or fpx0, provides an out-of-band method for connecting to the router. You can connect to the management interface over the network using utilities such as secure shell (SSH) and telnet. The Simple Network Management Protocol (SNMP) can use the management interface to gather statistics from the router.

(M40e and M160 routers) The craft interface is connected to the front top fan assembly. If the craft interface fails or is removed, a craft interface failure alarm and a front top fan absence alarm are generated.

Display Craft Interface Error Messages in the System Log File

Purpose

To determine the details of the craft interface error messages in the system log file.

Action

To display craft interface error messages in the system log file, use the following command:

Sample Output

user@host>  show log messages
Jun  3 16:43:19 flitter ssb CM(0): ALARM SET: (Major) fxp0: ethernet link down 
Jun  3 16:43:19 flitter craftd[582]: forwarding display request to chassisd: type = 4, subtype = 43 
Jun  3 16:43:19 flitter alarmd[581]: Alarm set: fxp0 color=RED, class=ETHER, reason=fxp0: ethernet link down 
Jun  3 16:43:19 flitter mib2d[586]: SNMP_TRAP_LINK_DOWN: ifIndex 1, ifAdminStatus up(1), ifOperStatus down(2), ifName fxp0
Jun  3 16:43:21 flitter /kernel: fxp0: media DOWN 100Mb / full-duplex

user@host>  show log messages
Jun  7 18:18:50 myrouter craftd[2654]:  Minor alarm set, Front Top Fan Absent
Jun  7 18:18:50 myrouter chassisd[2652]: CHASSISD_BLOWERS_SPEED: blowers 
being set to full speed [fan/blower missing]
Jun  7 18:18:50 myrouter alarmd[2653]: Alarm set: Fan color=YELLOW, 
class=CHASSIS, reason=Front Top Fan Absent
Jun  7 18:18:50 myrouter craftd[2654]: fpm led error: Unknown error: -1
Jun  7 18:18:50 myrouter alarmd[2653]: Alarm set: Craft IF color=YELLOW, 
class=CHASSIS, reason=Craft Failure
Jun  7 18:18:50 myrouter craftd[2654]:  Minor alarm set, Craft Failure

Meaning

The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. Use the show log messages command to browse error messages that are generated at least 5 minutes before and after an event. 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 prior to the event.

For an M20 router, the messages file output shows that the Ethernet management interface (fpx0) that provides an out-of-band method for connecting to the router from the craft interface is down. For more information about system log messages, see the Junos OS System Log Messages Reference.

For an M160 router, since the craft interface is attached to the front top fan, you see both craft interface and fan error messages.

Displaying Craft Interface Messages in the Chassis Daemon Log File

Purpose

To determine the details of the craft interface 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 craft interface status messages in the chassisd log file, use the following command:

Sample Output

Jun  7 18:18:50 *** inventory change ***
Jun  7 18:18:50 fru 42 set alarm 0x2
Jun  7 18:18:50 alarm op fru 42 op 1 reason 2
Jun  7 18:18:50 send: yellow alarm set, class 100 obj 100 reason 2
Jun  7 18:18:50 front top blower removed
Jun  7 18:18:50 FPM set alarm 0x1
Jun  7 18:18:50 alarm op fru 33 op 1 reason 1
Jun  7 18:18:50 send: yellow alarm set, class 100 obj 106 reason 106
Jun  7 18:18:50 FPM removed
Jun  7 18:18:50 CHASSISD_BLOWERS_SPEED: blowers being set to full speed 
[fan/blower missing]

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.

Displaying Craft Interface Hardware Information

Purpose

To display the craft interface hardware information.

Action

To view the craft interface hardware information, use the following CLI command:

Sample Output

user@host>  show chassis hardware
Hardware inventory:
Item             Version  Part number  Serial number     Description
[...Output truncated...]
Display          REV 07   710-000150   AA7812           

user@host>  show chassis hardware
Hardware inventory:
Item             Version  Part number  Serial number     Description
[...Output truncated...]
FPM CMB          REV 03   710-001642   AH5159           
FPM Display      REV 01   710-001647   AA2920           
[...Output truncated...]

Meaning

For M5, M10, M20, and M40 routers, the command output displays the display version level, part number, and serial number. For M40e, M120, M160, M320, and T320, T640, and T1600 routers, the command output displays the hardware information for the FPM CMB or the FPM GBUS and the FPM display. If the craft interface has failed or is absent, you will not see the craft interface or FPM hardware information in the command output.