It is important to be able to check on the health of the overall router and of individual components at will. This section will provide you with the commands needed to perform this task and will explain the various qualifiers for each command. This will be a section to earmark as you work with the Juniper Networks routers until you become proficient enough to know the commands by heart. 15.4.1 Environmental MonitoringThis section addresses how to monitor the temperature, alarms, and general environment of the router. It is important to be able to do these both locally and remotely because there is often no one present at the router. With more and more networks becoming centrally managed, this is a critical component of overall network health control. 15.4.1.1 Remote Craft Interface Monitoring on the M40, M40e, and M160 RoutersWhen it is impossible to be in front of the router you wish to troubleshoot, it is handy to be able to view virtually the information that is currently being displayed on that router's craft interface. Note that this is only true for data that is displayed on an M40, M40e, or M160 router equipped with an LCD display on the craft interface. The following command can be used in JUNOS view privilege mode from a terminal session to retrieve this data: lab@Chicago> show chassis craft-interface This command would offer output similar to that displayed below. Notice that there are no alarms and no known problems on this M20 router. Because there is no LCD screen on the craft interface of the M20 router, this command is the only way to discover this information. There are FPCs present in every available slot, again, with no problems. Red alarm: LED off, relay off Yellow alarm: LED off, relay off Host OK LED: On Host fail LED: Off FPCs 0 1 2 3 ------------------- Green * * * * Red . . . . LCD screen:\LCD Screen: New York Up: 10+7:05:32 Temperature OK Each router type has a different output for this command. Please refer to your JUNOS software configuration manual or go online to the Juniper Networks Web site at www.juniper.net/techpubs/software.html. 15.4.1.2 Chassis AlarmsWe mentioned chassis alarms earlier in Section 15.3.1. You can also gather this information remotely. A chassis alarm is defined as an alarm that originates in a router component, such as the power supply. If a power supply fails, a chassis alarm will be generated. Of course, on the M40, M40e, and M160 models, which are equipped with an LCD display on the craft interface, you can view these alarms if you are standing at the router. By using the CLI from a local or remote terminal session, you can gather information on active chassis alarms by using the command: lab@Chicago> show chassis alarms Tables 15-1 and 15-2 show the output you will see for each type of alarm for models M5, M10, M20, and M40 and for model M160. Table 15-1. Chassis Alarm CLI Output for Models M5, M10, M20, and M40
Table 15-2. Chassis Alarm CLI Output for Model M160
15.4.2 Power-Supply MonitoringIt is important to check the power supplies on the routers regularly. Although all Juniper Networks M-Series routers have redundant power supplies, it is critical that you know the status of all power supplies at all times. Doing so will help to head off any future total failure of the router if one power supply is nonfunctional and the standby (which has become the master) fails. There are three ways to monitor the power supply for operational status:
Visual inspection can provide the status of the system LEDs, as was discussed earlier in Section 15.3.1, and of the output on the LCD display of the craft interface on M40, M40e, and M160 models only. If the power supply is functioning normally, you should see a solid green OK LED illuminated on the power-supply faceplate, no system alarms, and no trouble indicated in the LCD display of the craft interface. Table 15-3 offers some tips on troubleshooting a power supply that is not functioning normally. 15.4.3 Control Board MonitoringIt is at least as important to monitor the health of the system control boards as it is to monitor any other system component. These boards are integral to the router's functioning, as you learned in Chapter 3. When troubleshooting the router, take careful note of the condition of the control boards . Here are a few tips:
The following sections address how to determine the status of the system control boards for each type of Juniper Networks router by visually inspecting the LEDs. Table 15-3. Power-Supply Troubleshooting
15.4.3.1 M5 and M10 Control BoardThe M5 and M10 routers do not have a control board. 15.4.3.2 M20 Control BoardThe M20 model has five LED indicators on the front faceplate.
15.4.3.3 M40 Control BoardThe M40 model has an SCB on which there are four LED indicators:
15.4.3.4 M160 Control BoardThe M160 model has two types of control module: the SFM and PCG. The health and operational status of both components can be discovered through a visual inspection of the LEDs on the components. The SFM has two LEDs on the front faceplate: green for OK and amber for FAIL. Similar to LEDs on other component LEDs, solid green indicates an operational status, blinking green indicates that the component is still initializing, and solid amber indicates a component failure. If an SFM fails, try swapping it out with a spare SFM. If the new SFM works, contact Juniper Networks for replacement of the faulty module. The PCG is located in the rear of the chassis beside the routing engine and has three LED indicators:
|