Junos OS SNMP Agent, MIBs, and traps | - The Junos OS SNMP agent runs on Juniper Networks routers,
exchanging network management information with SNMP manager software
running on an NMS or host. The SNMP manager collects information about
network connectivity, activity, and events by polling the router.
The agent responds to requests for information and actions from the
manager.
- The SNMP agent also controls access to the agent’s
MIBs. The Junos OS chassis MIB represents each component and the status
of the components.
- The agent sends a trap to the SNMP manager software when
an event occurs on the router. A trap reports significant events occurring
on a network device; for example, most often errors or failures.
|
Junos OS | The primary means of accessing and controlling the Junos
OS is the CLI. For M5, M10, M20, and M40 routers, the router provides three
ports on the craft interface for connecting external management devices
to the Routing Engine and hence to the Junos OS. For M40e, M160, M320, T320, T640, T1600, TX Matrix, and TX Matrix
Plus routers, the management ports are located on the Connector Interface
Panel (CIP). For M7i, M10i, and M120 routers, the management ports are located
on the Routing Engine. The management ports include the following: - Ethernet—Used to connect the Routing Engine to a
management LAN (or any other device that plugs into an Ethernet connection)
for out-of-band management of the router. The Ethernet port can be
10 or 100 Mbps and uses an autosensing RJ-45 connector. The Ethernet
management port has two LEDs, which indicate the type of connection
in use. A yellow LED lights when a 10-Mbps connection is active, and
a green LED lights when a 100-Mbps connection is active.
- Console—Used to connect a system console to the
Routing Engine with an RS-232 serial cable.
- Auxiliary—Used to connect a laptop computer or modem
to the Routing Engine with an RS-232 cable.
|
Junos OS commands | The Junos OS CLI has two modes: operational and
configuration. Note:
You only need to type cli if
you log in to the router as root. Otherwise, the CLI should be already
in operational mode. - In operational mode, you monitor and troubleshoot the
software, network connectivity, and router by entering commands. To
enter operational mode, log in to the router and type cli at the command prompt.
- In configuration mode, you configure the Junos OS that
controls the router. To enter configuration mode:
- Log in to the router.
- Start the CLI by typing cli at the command prompt.
- Type edit at the command prompt.
For more information about commands, see Checklist for Monitoring the CIP. |
Router craft interface | The craft interface provides status and troubleshooting
information at a glance and lets you perform many system control functions.
The craft interface provides the following information: - M5 and M10 routers: Alarm LEDs and lamp test button, Routing
Engine ports, link and activity status lights, and PIC online/offline
buttons
- M7i router: Networking interface Link/Activity LEDs, PIC
On/Off LEDs, and alarm LEDs are located on the FIC
- M10i routers: HCM status LEDs, PIC On/Off LEDs, and alarm
LEDs are located on the HCM
- M20 router: Alarm relay contacts, LEDs, and cutoff button,
Routing Engine interface ports and status indicators, Routing Engine
LEDs and offline buttons, Flexible PIC Concentrator (FPC) LEDs and
offline button
- M40 router: Alarm relay contacts, LEDs, cutoff button,
FPC LEDs and offline button, LCD display and navigation buttons, and
Routing Engine LEDs and interface ports
- M40e router: Alarm LEDs and alarm cutoff/lamp test button,
LCD display and navigation buttons, host module LEDs, and FPC LEDs
and offline button
- M120 router: Alarm LEDs and alarm cutoff/lamp test button,
Routing Engine interface ports and status indicators, external clock
interface ports, host subsystem LEDs, FEB LEDs, FPC LEDs, power supply
LEDs, and alarm relay contacts
- M160 router: Alarm LEDs and alarm cutoff/lamp test button,
LCD display and navigation buttons, host module LEDs, and FPC LEDs
and offline button
- M320 router: Routing Engine LEDs, Switch Interface Board
(SIB) LEDs, power supply LEDs, LCD display and navigation buttons,
alarm LEDs, and FPC LEDs
- T320, T640, T1600, TX Matrix, TX Matrix Plus routers:
Alarm LEDs and lamp test button, LCD display and navigation buttons,
host subsystem LEDs, SIB LED, FPC LEDs, and FPC online/offline buttons
The M40e, M160, T320, T640, T1600, TX Matrix, and TX Matrix
Plus routers have a CIP that contains the alarm relay contacts, management
ports, and link and activity status lights. To display craft interface information, use the following command: show chassis craft-interface |
Router component LEDs | Router components have faceplates with LEDs that display the component status: - M5 and M10 routers: PICs and power supplies
- M7i router: Compact Forwarding Engine Board (CFEB), PICs,
Fixed Interface Cards (FICs) (Fast Ethernet and Gigabit Ethernet),
and power supplies
- M10i router: CFEB, High-Availability Chassis Manager (HCM),
and power supplies
- M20 router: System and Switch Boards (SSBs) and power
supplies
- M40 router: System Control Boards (SCBs) and power supplies
- M40e router: Switching and Forwarding Modules (SFMs),
Packet Forwarding Engine Clock Generators (PCGs), Miscellaneous Control
Subsystem (MCS), and power supplies
- M120 router: Forwarding Engine Board (FEB), Routing Engine
and Control Boards, and power supplies
- M160 router: SFMs, PCGs, MCS, and power supplies
- M320 router: SIBs, Control Boards, and power supplies
- T320, T640, T1600 routers: SIBs, Control Boards, SONET
Clock Generators (SCGs), and power supplies
- TX Matrix router: SIBs, Control Boards, power supplies,
Routing Engines
- TX Matrix Plus router: SIBs, Control Boards, Control Interface
Panel, power supplies, Routing Engines
To display some router component LED status, use the following
command: show chassis craft-interface |
messagessystem log file | The messages system log file records the messages
generated by component operational events, including error messages
generated by component failures. To view the messages log
file, use the following command: show log messages To monitor the messages log file in real time, use
the following command: monitor start messages To stop monitoring the messages log file, use the following
command: monitor stop messages |
chassisd system log file | The chassis daemon (chassisd) log file keeps
track of the state of each chassis component. To view the chassisd log file, use the following command: show log chassisd To monitor the chassisd log file in real time, use
the following command: monitor start chassisd To stop monitoring the chassisd log file, use the following
command: monitor stop chassisd |
Swap test | Remove the failed component. Replace it with one that
you know works. Check the component status. If the replacement component
works, it confirms that the original one failed. |
JTAC | For technical support, open a support case using the
Case Manager link at http://www.juniper.net/support/ or call
1-888-314-JTAC (within the United States) or 1-408-745-9500 (outside
the United States). JTAC can do more extensive testing to determine
the root of the problem. |
