Monitor Hardware Components
Action
To use the CLI to monitor Juniper Networks routers, follow these steps:
If the operational mode prompt does not appear when you log in to the router, type
clito start the JUNOS software and enter operational mode. The prompt changes to>,indicating that you are in operational mode.
- Use one of the operational mode CLI commands listed in Table 9 to monitor router hardware.
Table 9: Operational Mode CLI Commands for Router Monitoring
Displays the router hostname, model number, and version of JUNOS software running on the router.
Displays the version of firmware running on the SCB, SFM, SSB, FEB, and FPCs.
Displays an inventory of the hardware components installed in the router, including the component name, version, part number, serial number, and a brief description.
Displays environmental information about the router chassis, including the temperature and status.
Displays more detailed environmental information for the following router components: FPCs, Front Panel Module (FPM), Miscellaneous Subsystem (MCS), PFE Clock Generator (PCG), Power Entry Module (PEM) or power supply, control board, SONET clock generator (SCG), Switch Interface Board (SIB), Routing Engine, and SFM. This command works only on the M40e, M160, and T320 routers, and the T640 routing node.
Displays operational status information about the router, including the alarm status and LED status of major components.
Displays the current router component alarms that have been generated, including the date, time, severity level, and description.
Displays more detailed operational status information about the FPCs, Routing Engine, FEB, SCB, SFMs, and SSB router components, including the temperature of air passing by the Switch Plane Processor (SPP) card and the Switch Plane Router (SPR) card (the two SFM serial components), in degrees Centigrade. The command displays the total CPU DRAM and SRAM being used by the SFM processor. The command output displays the time that the SFM became active and how long the SFM has been up and running. A small uptime can indicate a problem.
Displays the contents of the messages system log file that records messages generated by component operational events, including error messages generated by component failures.
To monitor the messages file in real time, use the monitor start messages CLI command. This command displays the new entries in the file until you stop monitoring by using the monitor stop messages CLI command.
Displays the contents of the chassis daemon (chassisd) log file that keeps track of the state of each chassis component
To monitor the chassisd file in real time, use the monitor start chassisd CLI command. This command displays the new entries in the file until you stop monitoring by using the monitor stop chassisd CLI command.
Use this command when you contact the Juniper Networks Technical Assistance Center (JTAC) about your component problem. This command is the equivalent of using the following CLI commands (see Contact JTAC):