Supported Network Management Features and Standards

The JUNOS software supports the use of scripts and event-triggered policies that you write to automate network management. The functions you can perform with these utilities include the following:

• Automatically detect, diagnose, and fix network problems. When it detects a problem, the script can issue a command that includes options appropriate to the current situation, and then interpret the command output to determine the next appropriate command or action.
• Periodically check for alarms or other indicators of network or chassis problems, and perform specific actions if they exist.
• Respond automatically to the occurrence of events and conditions that also trigger system log messages or SNMP traps.
• Verify that the routing platform’s configuration includes only statements you deem appropriate for your network, and automatically add or remove statements as necessary.
• Automatically change the routing platform’s configuration in response to network problems or conditions you specify.
• Generate custom error, warning, or system log messages.

For more information about scripts and event policies, see the JUNOS Configuration and Diagnostic Automation Guide.

The JUNOS software substantially supports SNMP version 1, version 2c, and version 3. The JUNOS SNMP agent software accepts both IP version 4 (IPv4) and IP version 6 (IPv6) addresses.

The JUNOS software supports the majority of network management features defined in the following standards documents. All RFCs and Internet drafts are published by the Internet Engineering Task Force (IETF).

• Extended Security Options (ESO) Consortium, ESO Consortium MIB
• Institute of Electrical and Electronics Engineers (IEEE) standard 802.3ad, Aggregation of Multiple Link Segments (only the following objects: dot3adAggPortDebugActorChangeCount, dot3adAggPortDebugActorSyncTransitionCount, dot3adAggPortDebugPartnerChangeCount, dot3adAggPortDebugPartnerSyncTransitionCount, dot3adAggPortDebugMuxState, dot3adAggPortDebugRxState, dot3adAggPortTable, dot3adAggPortListTable, dot3adAggPortStatsTable, dot3adAggTable, and dot3adTablesLastChanged)

  Gigabit Ethernet interfaces on J-series Services Routers do not support the 802.3ad MIB.

• Internet Assigned Numbers Authority (IANA), IANAiftype Textual Convention MIB (referenced by RFC 2863, The Interfaces Group MIB)
• RFC 1155, Structure and Identification of Management Information for TCP/IP-based Internets
• RFC 1156, Management Information Base for Network Management of TCP/IP-based internets
• RFC 1157, A Simple Network Management Protocol (SNMP)
• RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments (only the following objects: isisAreaAddr, isisCirc, isisCircLevel, isisISAdj, isisISAdjAreaAddr, isisAdjIPAddr, isisISAdjProtSupp, isisIPRA, isisMANAreaAddr, isisPacketCount, isisRa, isisSysProtSupp, isisSummAddr, and isisSystem)
• RFC 1212, Concise MIB Definitions

• RFC 1213, Management Information Base for Network Management of TCP/IP-based internets: MIB-II. The JUNOS software supports the following features:

  • MIB II and its SNMP version 2 derivatives, including the following:

    • Statistics counters
    • IP (except for the ipRouteTable object, which has been replaced by ipCidrRouteTable [RFC 2096, IP Forwarding Table MIB])
    • SNMP management
    • Interface management
  • SNMP version 1 Get and GetNext requests and version 2 GetBulk requests
  • JUNOS-specific secured access list
  • Master configuration keywords
  • Reconfigurations upon receipt of the SIGHUP signal
• RFC 1215, A Convention for Defining Traps for use with the SNMP (only MIB II SNMP version 1 traps and version 2 notifications)
• RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types (T1 MIB is supported) (obsoleted by RFC 2495)
• RFC 1407, Definitions of Managed Objects for the DS3/E3 Interface Type (T3 MIB is supported) (obsoleted by RFC 2496)
• RFC 1472, The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol
• RFC 1473, The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol
• RFC 1657, Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 (except for the bgpBackwardTransition and bgpEstablished notifications)
• RFC 1695, Definitions of Managed Objects for ATM Management Version 8.0 Using SMIv2 (obsoleted by RFC 2515)
• RFC 1724, RIP Version 2 MIB Extension
• RFC 1850, OSPF Version 2 Management Information Base (except for the ospfOriginateNewLsas and ospfRxNewLsas objects, the Host Table, and the ospfLsdbApproachingOverflow, ospfLsdbOverflow, and ospfOriginateLSA traps)
• RFC 1901, Introduction to Community-based SNMPv2
• RFC 1905, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) (obsoleted by RFC 3416)
• RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) (obsoleted by RFC 3418)
• RFC 2011, SNMPv2 Management Information Base for the Internet Protocol using SMIv2
• RFC 2012, SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2
• RFC 2013, SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2
• RFC 2024, Definitions of Managed Objects for Data Link Switching using SMIv2 (read-only access) (except for the dlswInterface and dlswSdlc object groups; the dlswDirLocateMacTable, dlswDirLocateNBTable, and dlswDirNBTable tables; the dlswCircuitDiscReasonLocal and dlswCircuitDiscReasonRemote tabular objects; and the dlswCircuitS1Dlc, dlswDirMacCacheNextIndex, and dlswDirNBCacheNextIndex scalar objects)
• RFC 2096, IP Forwarding Table MIB (The ipCidrRouteTable object is extended to include the tunnel name when the next hop is through an RSVP-signaled label-switched path [LSP].)
• RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2 (only the frDlcmiTable object)
• RFC 2233, The Interfaces Group MIB using SMIv2 (obsoleted by RFC 2863)
• RFC 2287, Definitions of System-Level Managed Objects for Applications (only the following objects: sysApplElmtRunTable, sysApplInstallElmtTable, sysApplInstallPkgTable, and sysApplMapTable)
• RFC 2465, Management Information Base for IP Version 6: Textual Conventions and General Group (except for IPv6 and Internet Control Message Protocol version 6 [ICMPv6] statistics)
• RFC 2466, Management Information Base for IP Version 6: ICMPv6 Group
• RFC 2495, Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (except for the following objects: dsx1FarEndConfigTable, dsx1FarEndCurrentTable, dsx1FarEndIntervalTable, dsx1FarEndTotalTable, and dsx1FracTable)
• RFC 2496, Definitions of Managed Objects for the DS3/E3 Interface Type (except for the following objects: dsx3FarEndConfigTable, dsx3FarEndCurrentTable, dsx3FarEndIntervalTable, dsx3FarEndTotalTable, and dsx3FracTable)
• RFC 2515, Definitions of Managed Objects for ATM Management (except for the aal5VccTable, atmVcCrossConnectTable, and atmVpCrossConnectTable objects)
• RFC 2558, Definitions of Managed Objects for the SONET/SDH Interface Type (obsoleted by RFC 3592)
• RFC 2570, Introduction to Version 3 of the Internet-standard Network Management Framework
• RFC 2571, An Architecture for Describing SNMP Management Frameworks (read-only access)
• RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) (read-only access) (obsoleted by RFC 3412)
• RFC 2576, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
• RFC 2578, Structure of Management Information Version 2 (SMIv2)
• RFC 2579, Textual Conventions for SMIv2
• RFC 2580, Conformance Statements for SMIv2
• RFC 2662, Definitions of Managed Objects for the ADSL Lines (J-Series Services Routers; all MIB tables, objects, and traps applicable to the asymmetric digital subscriber line [ADSL] transceiver unit–remote [ATU-R] agent)
• RFC 2665, Definitions of Managed Objects for the Ethernet-like Interface Types
• RFC 2667, IP Tunnel MIB
• RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol (except for row creation, the Set operation, and the vrrpStatsPacketLengthErrors object)

• RFC 2790, Host Resources MIB. The following objects are supported:

  • Only the hrStorageTable object. The file systems /, /config, /var, and /tmp always return the same index number. When SNMP restarts, the index numbers for the remaining file systems might change.
  • Only the objects in the hrSystem and hrSWInstalled groups.
• RFC 2819, Remote Network Monitoring Management Information Base (only the alarmTable, eventTable, and logTable objects and the etherStatsTable object for Ethernet interfaces)
• RFC 2863, The Interfaces Group MIB
• RFC 2864, The Inverted Stack Table Extension to the Interfaces Group MIB
• RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations (only the following objects: pingCtlTable, pingMaxConcurrentRequests, pingProbeHistoryTable, pingResultsTable, traceRouteCtlTable, traceRouteHopsTable, traceRouteProbeHistoryTable, and traceRouteResultsTable)
• RFC 2932, IPv4 Multicast Routing MIB
• RFC 2933, Internet Group Management Protocol MIB
• RFC 2934, Protocol Independent Multicast MIB for IPv4
• RFC 2981, Event MIB
• RFC 3014, Notification Log MIB
• RFC 3019, IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol
• RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
• RFC 3412, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
• RFC 3413, Simple Network Management Protocol (SNMP) Applications (except for the proxy MIB)
• RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
• RFC 3415, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
• RFC 3416, Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)
• RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP)
• RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
• RFC 3498, Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures (implemented under the Juniper Networks enterprise branch)
• RFC 3592, Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type
• RFC 3811, Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
• RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) (read only access)

  The following restrictions apply:

  • MPLS tunnels as interfaces are not supported.
  • The following objects in the TunnelResource table are not supported: mplsTunnelResourceExBurstSize, mplsTunnelResourceMaxBurstSize, mplsTunnelResourceMeanBurstSize, mplsTunnelResourceMeanRate, and mplsTunnelResourceWeight.
  • The mplsTunnelCRLDPResTable and mplsTunnelPerfTable objects are not supported.
  • The mplsTunnelCHopTable object is supported on ingress routers only.

  Note: The branch used by the proprietary LDP MIB (ldpmib.mib) conflicts with RFC 3812. ldpmib.mib has been deprecated and replaced by jnx-mpls-ldp.mib.

• RFC 3813, Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB) (except for the following objects: mplsInSegmentPerfTable, mplsInSegmentMapTable, mplsInterfacePerfTable, mplsOutSegmentPerfTable, mplsXCDown, and mplsXCUp; read only)
• RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP) (only the mplsLdpLsrID and mplsLdpSesPeerAddrTable objects)
• RFC 3826, The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model
• RFC 4444, Management Information Base for Intermediate System to Intermediate System (IS-IS)
• Internet draft draft-ietf-bfd-mib-02.txt, Bidirectional Forwarding Detection Management Information Base. This MIB provides SNMP trap support for BFD liveness detection. (Support is read-only and includes the bfdSessDown and bfdSessUp traps. Objects in the bfdSessMapTable and bfdSessPerfTable tables are not supported.) MIB draft-ietf-bfd-mib-02.txt is represented by mib-jnx-bfd-exp.txt and is implemented under the Juniper Networks Enterprise jnxExperiment branch.
• Internet draft draft-ietf-idr-bgp4-mibv2-04.txt, Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version (only the following objects: jnxBgpM2PrefixInPrefixes, jnxBgpM2PrefixInPrefixesAccepted, and jnxBgpM2PrefixInPrefixesRejected)
• Internet draft draft-ietf-isis-wg-mib-16.txt, Management Information Base for IS-IS (only the following tables: isisISAdjAreaAddrTable, isisISAdjIPAddrTable, isisISAdjProtSuppTable, and isisISAdjTable)
• Internet draft draft-ietf-msdp-mib-08.txt, Multicast Source Discovery protocol MIB (except for the msdpBackwardTransition, msdpEstablished, and msdpRequestsTable objects)
• Internet draft draft-ietf-ospf-ospfv3-mib-11.txt, Management Information Base for OSPFv3 (Represented by mib-jnx-ospfv3mib.txt and implemented under the Juniper Networks Enterprise jnxExperiment branch. Support for the ospfv3NbrTable table only. Read-only. Object names are prefixed by jnx, as in jnxOspfv3NbrAddressType, jnxOspfv3NbrPriority, and jnxOspfv3NbrTable.)
• Internet draft draft-ietf-ppvpn-mpls-vpn-mib-05.txt, MPLS/BGP Virtual Private Network Management Information Base Using SMIv2 (only the following objects and tables: mplsVpnScalars, mplsVpnVrfPerfTable, mplsVpnVrfRouteTargetTable, and mplsVpnVrfTable; expires May 2003)
• Internet draft draft-reeder-snmpv3-usm-3desede-00.txt, Extension to the User-Based Security Model (USM) to Support Triple-DES EDE in “Outside” CBC Mode
• Integrated Local Management Interface (ILMI) MIB (only the atmfMYIPNmAddress and atmfPortMyIfname objects). For more information about the ILMI MIB, see the JUNOS Network Management Configuration Guide and the ATM Forum Web site at http://www.atmforum.com/.

The JUNOS software provides numerous enterprise MIBs, including the following:

• Alarm
• Asynchronous Transfer Mode (ATM)
• ATM class of service (CoS)
• BGP4 version 2
• Chassis
• Chassis definitions for routing platform model
• Chassis forwarding
• CoS
• Configuration management
• Destination class usage
• Dynamic flow capture
• Ethernet media access control (MAC)
• Experimental
• Firewall
• Flow collector services
• Host resources
• IP Security (IPsec) monitoring
• IPv4
• IPv6 and ICMPv6
• LDP
• MPLS
• Passive monitoring
• RSVP traffic engineering
• Reverse path forwarding
• Services Physical Interface Card (PIC)
• SONET Automatic Protection Switching (APS)
• SONET/SDH interface management
• Source class usage
• Structure of Management Information (SMI)
• Virtual private network (VPN)

In addition, the JUNOS software provides extensions to the interface, ping, remote monitoring (RMON) events and alarms, and traceroute MIBs.

For some traps, a message is directed to the system log when the trap condition occurs, even if the SNMP agent does not send the trap to a network management system (NMS).

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.