Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Supported Network Management Standards

Junos OS supports the majority of network management features defined in the following standards documents.

  • Extended Security Options (ESO) Consortium, ESO Consortium MIB.

    As of February 2011, the text of this MIB is accessible at http://www.snmp.com/eso/esoConsortiumMIB.txt.

  • Institute of Electrical and Electronics Engineers (IEEE) Standard 802.3ad, Aggregation of Multiple Link Segments (published as Clause 43 in Section 3 of the 802.3 specification)

    Only the following MIB objects are supported:

    • dot3adAggPortDebugActorChangeCount

    • dot3adAggPortDebugActorSyncTransitionCount

    • dot3adAggPortDebugMuxState

    • dot3adAggPortDebugPartnerChangeCount

    • dot3adAggPortDebugPartnerSyncTransitionCount

    • dot3adAggPortDebugRxState

    • dot3adAggPortListTable

    • dot3adAggPortStatsTable

    • dot3adAggPortTable

    • dot3adAggTable

    • dot3adTablesLastChanged

  • Integrated Local Management Interface (ILMI) MIB in the Integrated Local Management Interface (ILMI) Specification, Version 4.0.

    This document is accessible at https://www.broadband-forum.org/component/sppagebuilder/?view=page&id=185 under ATM Forum Technical Specifications.

    Only the atmfMYIPNmAddress and atmfPortMyIfname objects are supported.

  • Internet Assigned Numbers Authority (IANA), IANAiftype Textual Convention MIB (referenced by RFC 2863, The Interfaces Group MIB)

    As of February 2011, the text of this MIB is accessible at http://www.iana.org/assignments/ianaiftype-mib.

  • RFC 1122, Requirements for Internet Hosts -- Communication Layers

  • 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 MIB objects are supported:

    • isisAdjIPAddr

    • isisAreaAddr

    • isisCirc

    • isisCircLevel

    • isisIPRA

    • isisISAdj

    • isisISAdjAreaAddr

    • isisISAdjProtSupp

    • isisMANAreaAddr

    • isisPacketCount

    • isisRa

    • isisSysProtSupp

    • isisSummAddr

    • isisSystem

  • RFC 1212, Concise MIB Definitions

  • RFC 1213, Management Information Base for Network Management of TCP/IP-based internets: MIB-II

    Only the following features are supported:

    • Junos OS-specific secured access list

    • Primary configuration keywords

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

      • Interface management

      • IP (except for the ipRouteTable object, which has been replaced by the inetCidrRouteTable object, [RFC 4292, IP Forwarding MIB])

      • SNMP management

      • Statistics counters

    • Reconfigurations upon receipt of the SIGHUP signal

    • SNMP version 1 Get and GetNext requests and version 2 GetBulk requests

  • RFC 1215, A Convention for Defining Traps for use with the SNMP

    Only MIB II SNMP version 1 traps and version 2 notifications are supported.

  • RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types (obsoleted by RFC 2495)

    The T1 MIB is supported.

  • RFC 1407, Definitions of Managed Objects for the DS3/E3 Interface Type (obsoleted by RFC 2496)

    The T3 MIB is supported.

  • RFC 1471, The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol

  • 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

    The bgpBackwardTransition and bgpEstablished notifications are not supported.

  • 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

    The following features are not supported:

    • Host Table

    • ospfLsdbApproachingOverflow trap

    • ospfLsdbOverflow trap

    • ospfOriginateLSA trap

    • ospfOriginateNewLsas MIB object

    • ospfRxNewLsas MIB object

  • 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

  • RFC 2068, Hypertext Transfer Protocol -- HTTP/1.1

  • 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).

    Note:

    RFC 2096 has been replaced by RFC 4292. However, Junos OS currently supports both RFC 2096 and RFC 4292.

  • RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2

    Only the frDlcmiTable object is supported.

  • 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 MIB objects are supported:

    • sysApplElmtRunTable

    • sysApplInstallElmtTable

    • sysApplInstallPkgTable

    • sysApplMapTable

  • RFC 2465, Management Information Base for IP Version 6: Textual Conventions and General Group

    IP version 6 (IPv6) and Internet Control Message Protocol version 6 (ICMPv6) statistics are not supported.

  • 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

    The following MIB objects are not supported:

    • dsx1FarEndConfigTable

    • dsx1FarEndCurrentTable

    • dsx1FarEndIntervalTable

    • dsx1FarEndTotalTable

    • dsx1FracTable

  • RFC 2496, Definitions of Managed Objects for the DS3/E3 Interface Type

    The following MIB objects are not supported:

    • dsx3FarEndConfigTable

    • dsx3FarEndCurrentTable

    • dsx3FarEndIntervalTable

    • dsx3FarEndTotalTable

    • dsx3FracTable

  • RFC 2515, Definitions of Managed Objects for ATM Management

    The following MIB objects are not supported:

    • aal5VccTable

    • atmVcCrossConnectTable

    • atmVpCrossConnectTable

  • 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

    Only read-only access is supported.

  • RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) (obsoleted by RFC 3412)

    Only read-only access is supported.

  • 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

  • RFC 2665, Definitions of Managed Objects for the Ethernet-like Interface Types

  • RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol

    The following features are not supported:

    • Row creation

    • Set operation

    • vrrpStatsPacketLengthErrors MIB object

  • RFC 2790, Host Resources MIB

    Only the following MIB objects are supported:

    • 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.

    • Objects in the hrSystem group.

    • Objects in the hrSWInstalled group.

  • RFC 2819, Remote Network Monitoring Management Information Base

    Only the following MIB objects are supported:

    • alarmTable

    • etherStatsTable object for Ethernet interfaces

    • eventTable

    • logTable

  • 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 MIB objects are supported:

    • pingCtlTable

    • pingMaxConcurrentRequests

    • pingProbeHistoryTable

    • pingResultsTable

    • traceRouteCtlTable

    • traceRouteHopsTable

    • traceRouteProbeHistoryTable

    • traceRouteResultsTable

  • RFC 2932, IPv4 Multicast Routing MIB

  • 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

    The proxy MIB is not supported.

  • 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

    Support is 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 3635, Definitions of Managed Objects for the Ethernet-like Interface Types

    Supports all objects, except dot3StatsRateControlAbility and dot3StatsRateControlStatus in dot3StatsEntry table.

    Note:

    The values of the following objects in dot3HCStatsEntry table will be always zero for both 32-bit counters and 64-bit counters:

    • dot3HCStatsSymbolErrors

    • dotHCStatsInternalMacTransmitErrors

  • 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)

    Only read-only access is supported, and the following features and MIB objects are not supported:

    • MPLS tunnels as interfaces

    • mplsTunnelCRLDPResTable object

    • mplsTunnelPerfTable object

    • The following objects in the TunnelResource table:

      • mplsTunnelResourceExBurstSize

      • mplsTunnelResourceMaxBurstSize

      • mplsTunnelResourceMeanBurstSize

      • mplsTunnelResourceMeanRate

      • mplsTunnelResourceWeight

    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)

    Only read-only access is supported, and the following MIB objects are not supported:

    • mplsInSegmentMapTable

    • mplsInSegmentPerfTable

    • mplsInterfacePerfTable

    • mplsOutSegmentPerfTable

    • mplsXCDown

    • mplsXCUp

  • RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)

    Only the following MIB objects are supported:

    • mplsLdpLsrID

    • mplsLdpSesPeerAddrTable

  • RFC 3826, The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model

  • RFC 4001, Textual Conventions for Internet Network Addresses

  • RFC 4087, IP Tunnel MIB

    Supports MIB objects with MAX-ACCESS of read-only in the following tables:

    • tunnelIfTable

    • tunnelInetConfigTable

  • RFC 4133, Entity MIB

    Supports tables and objects except:

    • entityLogicalGroup table

    • entPhysicalMfgDate and entPhysicalUris objects in entityPhysical2Group table

    • entLPMappingTable and entPhysicalContainsTable in entityMappingGroup table

    • entityNotoficationsGroup table

    Note:

    Supported only on MX240, MX480, and MX960 routers.

  • RFC 4188, Definitions of Managed Objects for Bridges

  • RFC 4268, Entity State MIB

    Note:

    Supported only on MX240, MX480, and MX960 routers.

  • RFC 4292, IP Forwarding MIB

    Supports the following table and associated MIB objects:

    • inetCidrRouteTable

    • inetCidrRouteNumber

    • inetCidrRouteDiscards

  • RFC 4382, MPLS/BGP Layer 3 Virtual Private Network (VPN) MIB

    Supports the following scalar objects and tables:

    • mplsL3VpnConfiguredVrfs

    • mplsL3VpnActiveVrfs

    • mplsL3VpnConnectedInterfaces

    • mplsL3VpnNotificationEnable

    • mplsL3VpnVrfConfMaxPossRts

    • mplsL3VpnVrfConfRteMxThrshTime

    • mplsL3VpnIllLblRcvThrsh

    • mplsL3VpnVrfTable

    • mplsL3VpnVrfPerfTable

    • mplsL3VpnVrfRteTable

    • mplsVpnVrfRTTable

  • Internet draft draft-ietf-bfd-mib-02.txt, Bidirectional Forwarding Detection Management Information Base

    Only read-only access is supported, and the bfdSessDown and bfdSessUp traps are supported. Objects in the bfdSessMapTable and bfdSessPerfTable tables are not supported. The MIB that supports this draft is mib-jnx-bfd-exp.txt under the Juniper Networks Enterprise jnxExperiment branch.

  • RFC 4273, Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version

    Only the following MIB objects are supported:

    • jnxBgpM2PrefixInPrefixes

    • jnxBgpM2PrefixInPrefixesAccepted

    • jnxBgpM2PrefixInPrefixesRejected

  • RFC 4444, Management Information Base for Intermediate System to Intermediate System (IS-IS)

    Only the following tables are supported:

    • isisISAdjAreaAddrTable

    • isisISAdjIPAddrTable

    • isisISAdjProtSuppTable

    • isisISAdjTable

  • RFC 4741, NETCONF Configuration Protocol (RFC 4741 is obsoleted by RFC 6241)

  • RFC 4742, Using the NETCONF Configuration Protocol over Secure Shell (SSH) (RFC 4742 is obsoleted by RFC 6242)

  • RFC 5424, The Syslog Protocol

  • RFC 5601, Pseudowire (PW) Management Information Base (MIB)

  • RFC 5603, Ethernet Pseudowire (PW) Management Information Base (MIB)

  • Internet draft draft-ietf-msdp-mib-08.txt, Multicast Source Discovery protocol MIB

    The following MIB objects are not supported:

    • msdpBackwardTransition

    • msdpEstablished

    • msdpRequestsTable

  • RFC 6020, YANG - A data modeling language for NETCONF

  • RFC 6241, Network Configuration Protocol (NETCONF) (RFC 6241 obsoletes RFC 4741)

    The following features are not supported:

    • Advertisement of NETCONF 1.1 capabilities during session establishment

    • :confirmed-commit:1.1 capability, which includes the <cancel-commit> operation and the <persist> and <persist-id> parameters for the <commit> operation

  • RFC 6242, Using the NETCONF Protocol over Secure Shell (SSH) (RFC 6242 obsoletes RFC 4742)

    The following feature is not supported:

    • Chunked framing

  • RFC 6527, Definitions of Managed Objects for the Virtual Router Redundancy Protocol Version 3 (VRRPv3)

    The following features are not supported:

    • Row creation

    • Set operation

    • vrrpv3StatisticsPacketLengthErrors MIB object

    • vrrpv3StatisticsRowDiscontinuityTime MIB object

  • RFC 7589, Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication

  • RFC 8071, NETCONF Call Home and RESTCONF Call Home

    Only NETCONF Call Home over SSH is supported.

  • Internet draft draft-ietf-ospf-ospfv3-mib-11.txt, Management Information Base for OSPFv3

    Only read-only access is supported, and only for the ospfv3NbrTable table. The MIB that supports this draft is mib-jnx-ospfv3mib.txt under the Juniper Networks Enterprise jnxExperiment branch; MIB object names are prefixed with jnx (for example, jnxOspfv3NbrAddressType).

  • 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

The following RFCs do not define standards, but provide information about network management. The IETF classifies them variously as “Best Current Practice,” “Experimental” or “Informational.”

  • RFC 1901, Introduction to Community-based SNMPv2

  • RFC 2330, Framework for IP Performance Metrics

  • RFC 2934, Protocol Independent Multicast MIB for IPv4

  • RFC 3410, Introduction and Applicability Statements for Internet Standard Management Framework

  • RFC 3584, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework

  • RFC 5601, PW-FRAME-MIB

    Supported on MX Series routers with MPC/MIC interfaces that use the ATM MIC with SFP.

  • RFC 5603, PWE3 MIB

    Supported on MX Series routers with MPC/MIC interfaces that use the ATM MIC with SFP.

  • Internet draft draft-ietf-l3vpn-mvpn-mib-03.txt, MPLS/BGP Layer 3 VPN Multicast Management Information Base

    Implemented under the Juniper Networks enterprise branch [jnxExperiment]. OID for jnxMvpnExperiment is .1.3.6.1.4.1.2636.5.12. This includes jnxMvpnNotifications traps.

Related Documentation