System Management with SNMP


Simple Network Management Protocol (SNMP) enables the monitoring of network devices from a central location. The SNMP agent exchanges network management information with SNMP manager software running on a network management system (NMS), or host. The agent responds to requests for information and actions from the manager. The agent also controls access to the agent's management information base (MIB), the collection of objects that can be viewed or changed by the SNMP manager.

The SNMP manager collects information on network connectivity, activity, and events by polling managed devices. Communication between the agent and the manager occurs in one of the following forms:

  • Get , GetBulk , and GetNext requests ”The manager requests information from the agent; the agent returns the information in a Get response message.

  • Set requests ”The manager changes the value of a MIB object controlled by the agent; the agent indicates status in a Set response message.

  • Traps notification ”The agent sends traps to notify the manager of significant events that occur on the network device.

Management Information Base

A management information base, or MIB, is a hierarchy of information used to define managed objects in a network device. The MIB structure is based on a tree structure, which defines a grouping of objects into related sets. Each object in the MIB is associated with an object identifier (OID), which names the object. The "leaf" in the tree structure is the actual managed object instance, which represents a resource, event, or activity that occurs in your network device.

MIBs are either standard or enterprise-specific. Standard MIBs are created by the IETF and documented in various RFCs. Depending on the vendor, many standard MIBs are delivered with the NMS software. You can also download the standard MIBs from the IETF Web site, http://www.ietf.org, and compile them into your NMS if necessary.

For the contents of Juniper Networks enterprise MIBs, see the JUNOS technical documentation Network Management.

Enterprise MIBs are developed and supported by a specific equipment manufacturer. If your network contains devices that have enterprise MIBs, you must obtain them from the manufacturer and compile them into your network management software. Table 5.10 lists the enterprise MIBs supported in JUNOS 5.4.

Table 5.10. JUNOS Enterprise MIBs
MIB Description
Chassis Environmental monitoring (power supply state, board voltages, fans, temperatures , air flow) and inventory support for the chassis, SCB, SSB, SFM, FPCs, and PICs
MPLS Support for the JUNOS MPLS implementation
Extensions to the interface MIB (RFC 1213) Support for Juniper Networks PICs
Alarm Juniper Networks outer chassis alarm
Firewall Accessibility to firewall filter counters through SNMP queries; routers must have the Internet Processor II ASIC to perform firewall monitoring
Destination class usage Monitoring of packet counts based on the ingress and egress points for traffic transiting your networks
Extensions to ping MIB (RFC 2925) Support for the JUNOS ping command implementation
Extensions to traceroute MIB Support for the JUNOS traceroute command implementation
ATM Support for JUNOS ATM implementation
IPv6 and ICMPv6 Support for JUNOS implementation of IPv6 and ICMPv6
IPv4 Support for JUNOS implementation of IPv4
Extensions to RMON events and alarms MIB Support for JUNOS implementation of RMON events and alarms
Extensions to LDP traps MIB Support for JUNOS implementation of LDP traps. LDP traps support IPv4 standards only
CoS Support for JUNOS CoS implementation
Reverse- path forwarding Support for JUNOS RPF implementation
Source class usage Support for JUNOS implementation of source class usage

SNMP Traps

You can also download the standard traps from the IETF Web site, http://www.ietf.org.

Traps report significant events occurring on a network device, most often errors or failures. SNMP traps are defined in either standard or enterprise MIBs. Standard traps are created by the IETF and documented in various RFCs. The standard traps are compiled into the network management software. Enterprise traps are developed and supported by a specific equipment manufacturer. If your network contains devices that have enterprise traps, you must obtain them from the manufacturer and compile them into your network management software. Table 5.11 and Table 5.12 summarize the SNMP traps supported by the JUNOS software.

For SNMP version 1, the JUNOS software supports the traps listed in Table 5.11 and Table 5.12. If you need SNMP version 1 traps for BGP and OSPF, you must translate into SMI version 1 format the BGP and OSPF SMI version 2 trap definitions from RFC 1657 ( Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol [BGP-4] using SMIv2 ) and RFC 1850 ( OSPF Version 2 Management Information Base ). If you need SNMP version 2 traps for BGP and OSPF, you do not need to reformat the SMI version 2 trap definitions in RFCs 1657 and 1850; you use the definitions as they are documented in the RFCs.

Table 5.11. Supported SNMP Version 1 Standard Traps
Trap Name Enterprise ID Generic Trap Number Specific Trap Number Trap Category
Cold start 1.3.6.1.4.1.2636 Startup
Warm start 1.3.6.1.4.1.2636 1 Startup
Link down 1.3.6.1.4.1.2636 2 Link
Link up 1.3.6.1.4.1.2636 3 Link
Authentication failure 1.3.6.1.4.1.2636 4 Authentication
BGP established 1.3.6.1.2.1.15.7 6 1 Routing
BGP backward transition 1.3.6.1.2.1.15.7 6 2 Routing
OSPF virtual interface state change 1.3.6.1.2.1.14.16.2 6 1 Routing
OSPF neighbor state change 1.3.6.1.2.1.14.16.2 6 2 Routing
OSPF virtual neighbor state change 1.3.6.1.2.1.14.16.2 6 3 Routing
OSPF interface configuration error 1.3.6.1.2.1.14.16.2 6 4 Routing
OSPF virtual interface configuration error 1.3.6.1.2.1.14.16.2 6 5 Routing
OSPF interface authentication error 1.3.6.1.2.1.14.16.2 6 6 Routing
OSPF virtual interface authentication error 1.3.6.1.2.1.14.16.2 6 7 Routing
OSPF interface receiving bad packet 1.3.6.1.2.1.14.16.2 6 8 Routing
OSPF virtual interface receiving bad packet 1.3.6.1.2.1.14.16.2 6 9 Routing
OSPF transmit packet retransmitted 1.3.6.1.2.1.14.16.2 6 10 Routing
OSPF virtual interface transmit packet retransmitted 1.3.6.1.2.1.14.16.2 6 11 Routing
OSPF originating LSA (currently not supported) 1.3.6.1.2.1.14.16.2 6 12 Routing
OSPF maximum aged LSA 1.3.6.1.2.1.14.16.2 6 13 Routing
OSPF LSDB overflow (currently not supported) 1.3.6.1.2.1.14.16.2 6 14 Routing
OSPF LSDB approaching overflow (currently not supported) 1.3.6.1.2.1.14.16.2 6 15 Routing
OSPF interface state change 1.3.6.1.2.1.14.16.2 6 16 Routing
Ping probe failed 1.3.6.1.2.1.80.0 6 1 Remote-operations
Ping test failed 1.3.6.1.2.1.80.0 6 2 Remote-operations
Ping test completed 1.3.6.1.2.1.80.0 6 3 Remote-operations
Redundancy switchover 1.3.6.1.4.1.2636.4.1 6 4 Chassis
Table 5.12. Supported SNMP Version 1 Enterprise Traps
Trap Name Enterprise ID Generic Trap Number Specific Trap Number Trap Category
Power failure 1.3.6.1.4.1.2636.4.1 6 1 Chassis
Fan failure 1.3.6.1.4.1.2636.4.1 6 2 Chassis
Overtemperature 1.3.6.1.4.1.2636.4.1 6 3 Chassis
MPLS LSP up 1.3.6.1.4.1.2636.3.2.4 6 1 Routing
MPLS LSP down 1.3.6.1.4.1.2636.3.2.4 6 2 Routing
MPLS LSP change 1.3.6.1.4.1.2636.3.2.4 6 3 Routing

JUNOS SNMP Agent Features

The JUNOS SNMP agent software consists of an SNMP master agent that delegates all SNMP requests to subagents. Each subagent is responsible for the support of a specific set of MIBs. The JUNOS software supports SNMP version 1 and version 2c. SNMP version 1 is the initial implementation of SNMP that defines architecture and framework for SNMP. SNMP version 2c is the revised protocol, with improvements to performance and manager-to-manager communications. Specifically, SNMP version 2c implements community strings, which act as passwords when determining who, what, and how the SNMP clients can access the data in SNMP agent. The community string is contained in SNMP Get , GetBulk , GetNext , and Set requests. The agent might require a different community string for Get , GetBulk , and GetNext (read-only access) than for Set (read-write access). The JUNOS SNMP implementation supports Set requests only with the ping MIB. To use Set requests with the ping MIB, you must create a MIB view that includes the ping MIB subtree and include the view statement at the [edit snmp community] hierarchy level.

The JUNOS implementation of SNMP supports the IPv6 objects defined in RFC 2465, with the exception of ipv6IfStatsTable . The Juniper IPv6 MIB supports additional IPv6 and ICMPv6 statistics. The JUNOS SNMP agent software accepts IPv4 and IPv6 addresses for transport over IPv4 and IPv6.

System Logging for SNMP Traps

For more information about syslog severity levels, see the JUNOS technical documentation Getting Started.

When a trap condition occurs, whether the SNMP agent sends a trap to an NMS or not, the trap is logged if the system logging is configured to log an event with that syslog severity level. Table 5.13 lists the syslog severity levels for the SNMP traps supported by the JUNOS software. These levels cannot be changed.

Table 5.13. System Logging Severity Levels for SNMP Traps
Trap Type Trap Name Severity Level
Standard Traps Cold start critical
  Warm start error
  Link down warning
  Link up info
  Authentication failure notice
Enterprise Traps Power failure critical
  Fan failure critical
  Over temperature alert


Juniper Networks Field Guide and Reference
Juniper Networks Field Guide and Reference
ISBN: 0321122445
EAN: 2147483647
Year: 2002
Pages: 185

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net