Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Standard SNMP MIBs Supported by Junos OS

 

Junos OS supports the Standard MIBs listed in Table 1.

Note

For details on SNMP MIB support on EX4600 switches, QFX Series switches, and QFabric systems, see SNMP MIBs Support.

Table 1: Standard MIBs supported by Junos OS

Standard MIB

Exceptions

Platforms

IEEE 802.1ab section 12.1, Link Layer Discovery Protocol (LLDP) MIB

EX Series implementation of LLDP MIB supports both IPv4 and IPv6 configuration.

EX Series and MX Series

IEEE, 802.3ad, Aggregation of Multiple Link Segments

Supported tables and objects:

  • dot3adAggPortTable, dot3adAggPortListTable, dot3adAggTable, and dot3adAggPortStatsTable

    Note: EX Series switches do not support the dot3adAggPortTable and dot3adAggPortStatsTable.

  • dot3adAggPortDebugTable (only dot3adAggPortDebugRxState, dot3adAggPortDebugMuxState, dot3adAggPortDebugActorSyncTransitionCount, dot3adAggPortDebugPartnerSyncTransitionCount, dot3adAggPortDebugActorChangeCount, and dot3adAggPortDebugPartnerChangeCount)

    Note: EX Series switches do not support the dot3adAggPortDebugTable.

  • dot3adTablesLastChanged

EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, and vSRX

IEEE, 802.1ag, Connectivity Fault Management

Supported tables and objects:

  • dot1agCfmMdTableNextIndex

  • dot1agCfmMdTable (except dot1agCfmMdMhfldPermission)

  • dot1agCfmMaNetTable

  • dot1agCfmMaMepListTable

  • dot1agCfmDefaultMdDefLevel

  • dot1agCfmDefaultMdDefMhfCreation

  • dot1agCfmMepTable (except dot1agCfmMepLbrBadMsdu, dot1agCfmMepTransmitLbmVlanPriority, dot1agCfmMepTransmitLbmVlanDropEnable, dot1agCfmMepTransmitLtmFlags, dot1agCfmMepPbbTeCanReportPbbTePresence, dot1agCfmMepPbbTeTrafficMismatchDefect, dot1agCfmMepPbbTransmitLbmLtmReverseVid, dot1agCfmMepPbbTeMismatchAlarm, dot1agCfmMepPbbTeLocalMismatchDefect, and dot1agCfmMepPbbTeMismatchSinceReset)

  • dot1agCfmLtrTable (except dot1agCfmLtrChassisIdSubtype, dot1agCfmLtrChassisId, dot1agCfmLtrManAddressDomain, dot1agCfmLtrManAddress, dot1agCfmLtrIngressPortIdSubtype, dot1agCfmLtrIngressPortId, dot1agCfmLtrEgressPortIdSubtype, dot1agCfmLtrEgressPortId, and dot1agCfmLtrOrganizationSpecificTlv)

  • dot1agCfmMepDbTable (except dot1agCfmMebDbChassisIdSubtype, dot1agCfmMebDbChassisId, dot1agCfmMebDbManAddressDomain, and dot1agCfmMebDbManAddress)

EX Series, MX Series, and QFX Series

IEEE, 802.1ap, Management Information Base (MIB) definitions for VLAN Bridges

Supported tables and objects:

  • ieee8021CfmStackTable

  • ieee8021CfmVlanTable

  • ieee8021CfmDefaultMdTable (except ieee8021CfmDefaultMdIdPermission)

  • ieee8021CfmMaCompTable (except ieee8021CfmMaCompIdPermission)

MX Series

RFC 1155, Structure and Identification of Management Information for TCP/IP-based Internets

No exceptions

All platforms

RFC 1157, A Simple Network Management Protocol (SNMP)

No exceptions

All platforms

RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments

Supported tables and objects:

  • isisSystem

  • isisMANAreaAddr

  • isisAreaAddr

  • isisSysProtSupp

  • isisSummAddr

  • isisCirc

  • isisCircLevel

  • isisPacketCount

  • isisISAdj

  • isisISAdjAreaAddr

  • isisAdjIPAddr

  • isisISAdjProtSupp

  • isisRa

  • isisIPRA

All platforms

RFC 1212, Concise MIB Definitions

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 1213, Management Information Base for Network Management of TCP/IP-Based Internets: MIB-II

Junos OS supports the following areas:

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

    • Statistics counters

    • IP, except for ipRouteTable, which has been replaced by ipCidrRouteTable (RFC 2096, IP Forwarding Table MIB)

    • SNMP management

    • Interface management

  • SNMPv1 Get, GetNext requests, and version 2 GetBulk request

  • Junos OS-specific secured access list

  • Master configuration keywords

  • Reconfigurations upon SIGHUP

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

Junos OS supports only MIB II SNMP version 1 traps and version 2 notifications.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types

Junos OS supports T1 MIB.

ACX Series, M Series, SRX Series, and T Series

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

Junos OS supports T3 MIB.

M Series and T Series

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

Supported tables and objects:

  • pppLcp 1 object

  • pppLinkStatustable table

  • pppLinkConfigTable table

M Series, MX Series, and PTX Series

RFC 1657, Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, and T Series

RFC 1695, Definitions of Managed Objects for ATM Management Version 8.0 Using SMIv2

No exceptions

ACX Series, M Series, PTX Series, and T Series

RFC 1850, OSPF Version 2 Management Information Base

Unsupported tables, objects, and traps:

  • ospfOriginateNewLsas object

  • ospfRxNewLsas object

  • The host table

  • ospfOriginateLSA trap

    ospfLsdbOverflow trap

    ospfLsdbApproachingOverflow trap

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 1901, Introduction to Community-based SNMPv2

No exceptions

All platforms

RFC 2011, SNMPv2 Management Information Base for the Internet Protocol Using SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, and T Series

RFC 2012, SNMPv2 Management Information Base for the Transmission Control Protocol Using SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2013, SNMPv2 Management Information Base for the User Datagram Protocol Using SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2024, Definitions of Managed Objects for Data Link Switching Using SMIv2

Unsupported tables, objects, and traps with read-only access:

  • dlswInterface object group

    dlswSdlc object group

    dlswDirLocateMacTable table

    dlswDirNBTabletable

    dlswDirLocateNBTable table

    dlswCircuitDiscReasonLocal tabular object

    dlswCircuitDiscReasonRemote tabular object

    dlswDirMacCacheNextIndex scalar object

    dlswDirNBCacheNextIndex scalar object

M Series, MX Series, and T Series

RFC 2096, IP Forwarding Table MIB

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

The ipCidrRouteTable has been extended to include the tunnel name when the next hop is through an RSVP-signaled LSP.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

Unsupported table and objects:

  • frCircuitTable

  • frErrTable

M Series, MX Series, SRX Series, and T Series

RFC 2233, The Interfaces Group MIB Using SMIv2

Note: RFC 2233 has been replaced by RFC 2863, IF MIB. However, Junos OS supports both RFC 2233 and RFC 2863.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2287, Definitions of System-Level Managed Objects for Applications

Supported tables and objects:

  • sysApplInstallPkgTable

  • sysApplInstallElmtTable

  • sysApplElmtRunTable

  • sysApplMapTable

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2465, Management Information Base for IP Version 6: Textual Conventions and General Group (except for IPv6 interface statistics)

Junos OS does not support IPv6 interface statistics.

ACX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2495, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

Unsupported tables, objects, and traps:

  • dsx1FarEndConfigTable

  • dsx1FarEndCurrentTable

  • dsx1FarEndIntervalTable

  • dsx1FarEndTotalTable

  • dsx1FracTable

ACX Series, M Series, SRX Series, and T Series

RFC 2515, Definitions of Managed Objects for ATM Management

Unsupported table and objects:

  • atmVpCrossConnectTable

  • atmVcCrossConnectTable

  • aal5VccTable

ACX Series, M Series, and T Series

RFC 2570, Introduction to Version 3 of the Internet-standard Network Management Framework

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2571, An Architecture for Describing SNMP Management Frameworks (read-only access)

Note: RFC 2571 has been replaced by RFC 3411. However, Junos OS supports both RFC 2571 and RFC 3411.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) (read-only access)

Note: RFC 2572 has been replaced by RFC 3412. However, Junos OS supports both RFC 2572 and RFC 3412.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

Note: RFC 2576 has been replaced by RFC 3584. However, Junos OS supports both RFC 2576 and RFC 3584.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2578, Structure of Management Information Version 2 (SMIv2)

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2579, Textual Conventions for SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2580, Conformance Statements for SMIv2

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2662, Definitions of Managed Objects for ADSL Lines

No exceptions

M Series, MX Series, SRX Series, and T Series

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

Note: The list of managed objects specified in RFC 2665 has been updated by RFC 3635 by including information useful for the management of 10-Gigabit per second Ethernet interfaces.

For M Series, T Series, and MX Series, the SNMP counters do not count the Ethernet header and frame check sequence (FCS). Therefore, the Ethernet header bytes and the FCS bytes are not included in the following four tables:

  • ifInOctets

  • ifOutOctets

  • ifHCInOctets

  • ifHCOutOctets

However, the EX switches adhere to RFC 2665.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

Unsupported table and objects:

  • vrrpStatsPacketLengthErrors

Note: Junos OS does not support this standard for row creation and the Set operation.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2790, Host Resources MIB

Supported tables and objects:

  • hrStorageTable

    Note: 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.

  • hrSystem group

  • hrSWInstalled group

  • hrProcessorTable

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2819, Remote Network Monitoring Management Information Base

Supported tables and objects:

  • etherStatsTable (for Ethernet interfaces only), alarmTable, eventTable, and logTable are supported on all devices running Junos OS.

  • historyControlTable and etherHistoryTable (except etherHistoryUtilization object) are supported only on EX Series switches.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2863, The Interfaces Group MIB

Note: RFC 2863 replaces RFC 2233. However, Junos OS supports both RFC 2233 and RFC 2863.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2864, The Inverted Stack Table Extension to the Interfaces Group MIB

No exceptions

M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2922, The Physical Topology (PTOPO) MIB

Supported objects:

  • ptopoConnDiscAlgorithm

  • ptopoConnAgentNetAddrType

  • ptopoConnAgentNetAddr

  • ptopoConnMultiMacSASeen

  • ptopoConnMultiNetSASeen

  • ptopoConnIsStatic

  • ptopoConnLastVerifyTime

  • ptopoConnRowStatus

EX Series and SRX Series

RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations

Supported tables and objects:

  • pingCtlTable

  • pingResultsTable

  • pingProbeHistoryTable

  • pingMaxConcurrentRequests

  • traceRouteCtlTable

  • traceRouteResultsTable

  • traceRouteProbeHistoryTable

  • traceRouteHopsTable

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2932, IPv4 Multicast Routing MIB

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2934, Protocol Independent Multicast MIB for IPv4

Note: In Junos OS, RFC 2934 is implemented based on a draft version, pimmib.mib, of the now standard RFC.

Support for the pimNeighborLoss trap was added in Release 11.4.

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 2981, Event MIB

No exceptions

ACX Series, M Series, MX Series, PTX Series, and T Series

RFC 3014, Notification Log MIB

No exceptions

ACX Series, M Series, MX Series, PTX Series, and T Series

RFC 3019, IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol

No exceptions

M Series, MX Series, PTX Series, SRX Series, and T Series

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

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

Note: RFC 3411 replaces RFC 2571. However, Junos OS supports both RFC 3411 and RFC 2571.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

Note: RFC 3412 replaces RFC 2572. However, Junos OS supports both RFC 3412 and RFC 2572.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3413, Simple Network Management Protocol (SNMP) Applications

Unsupported tables and objects:

  • Proxy MIB

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3415, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3416, Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)

Note: RFC 3416 replaces RFC 1905, which was supported in earlier versions of Junos OS.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP)

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

Note: RFC 3418 replaces RFC 1907, which was supported in earlier versions of Junos OS.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3498, Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures (implemented under the Juniper Networks enterprise branch [jnxExperiment])

No exceptions

M Series and T Series

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

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3591 Managed Objects for the Optical Interface Type

Supported tables and objects:

  • optIfOTMnTable (except optIfOTMnOpticalReach, optIfOTMnInterfaceType, and optIfOTMnOrder)

  • optIfOChConfigTable (except optIfOChDirectionality and optIfOChCurrentStatus)

  • optIfOTUkConfigTable (except optIfOTUkTraceIdentifierAccepted, optIfOTUkTIMDetMode, optIfOTUkTIMActEnabled, optIfOTUkTraceIdentifierTransmitted, optIfOTUkDEGThr, optIfOTUkDEGM, optIfOTUkSinkAdaptActive, and optIfOTUkSourceAdaptActive)

  • optIfODUkConfigTable (except optIfODUkPositionSeqCurrentSize and optIfODUkTtpPresent)

M Series, MX Series, PTX Series, and T Series

RFC 3592, Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type

No exceptions

M Series, MX Series, and T Series

RFC 3621, Power Ethernet MIB

No exceptions

EX Series

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

Unsupported tables and objects:

  • dot3StatsRateControlAbility

  • 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

MX Series

RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer

Unsupported tables and objects:

  • etherWisDeviceTable,

  • etherWisSectionCurrentTable

  • etherWisFarEndPathCurrentTable

M Series, MX Series, PTX Series, and T Series

RFC 3811, Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management

No exceptions

ACX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) (read-only access)

MPLS tunnels as interfaces are not supported.

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

Unsupported tables and objects:

  • mplsTunnelResourceMeanRate in TunnelResource table

  • mplsTunnelResourceMaxBurstSize in TunnelResource table

  • mplsTunnelResourceMeanBurstSize in TunnelResource table

  • mplsTunnelResourceExBurstSize in TunnelResource table

  • mplsTunnelResourceWeight in TunnelResource table

  • mplsTunnelPerfTable

  • mplsTunnelCRLDPResTable

ACX Series, M Series, MX Series, PTX Series, and T Series

RFC 3813, Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)

Unsupported tables and objects (read-only access):

  • mplsInterfacePerfTable

  • mplsInSegmentPerfTable

  • mplsOutSegmentPerfTable

  • mplsInSegmentMapTable

  • mplsXCUp

  • mplsXCDown

ACX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 3877, Alarm Management Information Base

  • Junos OS does not support the alarmActiveStatsTable.

  • Traps that do not conform to the alarm model are not supported. However, these traps can be redefined to conform to the alarm model.

MX Series

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

Unsupported tables and objects:

  • dsx3FarEndConfigTable

  • dsx3FarEndCurrentTable

  • dsx3FarEndIntervalTable

  • dsx3FarEndTotalTable

  • dsx3FracTable

M Series and T Series

RFC 4087, IP Tunnel MIB

Describes MIB objects in the following tables for managing tunnels of any type over IPv4 and IPv6 networks:

  • tunnelIfTable—Provides information about the tunnels known to a router.

  • tunnelInetConfigTable—Assists dynamic creation of tunnels and provides mapping from end-point addresses to the current interface index value.

Note: Junos OS supports MAX-ACCESS of read-only for all the MIB objects in tunnelIfTable and tunnelInetConfigTable tables.

M Series, MX Series, and T Series

RFC 4133, Entity MIB

Unsupported tables and objects:

  • entityLogicalGroup table

  • entPhysicalMfgDate and entPhysicalUris objects in entityPhysical2Group table

  • entLPMappingTable and entPhysicalContainsTable in entityMappingGroup table

  • entityNotoficationsGroup table

Only MX240, MX480, and MX960 routers, and EX2200 and EX3300 switches

RFC 4188, Definitions of Managed Objects for Bridges

  • Supports 802.1D STP(1998)

  • Supported subtrees and objects:

    • dot1dStp subtree is supported on MX Series 5G Universal Routing Platforms.

    • dot1dTpFdbAddress, dot1dTpFdbPort, and dot1dTpFdbStatus objects from the dot1dTpFdbTable of the dot1dTp subtree are supported on EX Series Ethernet Switches.

    • dot1dTpLearnedEntryDiscards and dot1dTpAgingTime objects are supported on M Series and T Series routers.

MX Series, EX Series, and M Series and T Series

RFC 4268, Entity State MIB

No exceptions

Only MX240, MX480, and MX960 routers, and EX2200 and EX3300 switches

RFC 4273, Definitions of Managed Objects for BGP-4

Supported tables and objects:

  • jnxBgpM2PrefixInPrefixesAccepted

  • jnxBgpM2PrefixInPrefixesRejected

ACX Series, EX Series, M Series, MX Series, SRX Series, and T Series

RFC 4292, IP Forwarding MIB

Supported tables and objects:

  • inetCidrRouteTable

  • inetCidrRouteNumber

  • inetCidrRouteDiscards

Note: Junos OS currently supports these MIB objects that will be deprecated in future releases: ipCidrRouteTable, ipCidrRouteNumber, and ipCidrRouteDiscards.

ACX Series, EX Series, M Series, MX Series, PTX Series, and T Series

RFC 4293, Management Information Base for the Internet Protocol (IP)

Supports only the mandatory groups.

MX Series and EX Series

RFC 4318, Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol

Supports 802.1w and 802.1t extensions for RSTP.

EX Series, M Series, MX Series, and T Series

RFC 4363b, Q-Bridge VLAN MIB

No exceptions

MX Series and EX Series

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

Supported tables and objects:

  • mplsL3VpnActiveVrfs

  • mplsL3VpnConfiguredVrfs

  • mplsL3VpnConnectedInterfaces

  • mplsL3VpnVrfConfMidRteThresh

  • mplsL3VpnVrfConfHighRteThresh

  • mplsL3VpnIfConfRowStatus

  • mplsL3VpnIllLblRcvThrsh

  • mplsL3VpnNotificationEnable

  • mplsL3VpnVrfConfMaxPossRts

  • mplsL3VpnVrfConfRteMxThrshTime

  • mplsL3VpnVrfOperStatus

  • mplsL3VpnVrfPerfCurrNumRoutes

  • mplsL3VpnVrfPerfTable

  • mplsL3VpnVrfRteTable

  • mplsVpnVrfRTTable

  • mplsL3VpnVrfTable

  • mplsL3VpnIfConfTable

EX Series, M Series, MX Series, PTX Series, and T Series

RFC 4444, IS-IS MIB

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

RFC 4668, RADIUS Accounting Client Management Information Base (MIB) for IPv6 (read-only access)

No exceptions

MX Series

RFC 4670, RADIUS Accounting Client Management Information Base (MIB) (read-only access)

No exceptions

MX Series

RFC 4801, Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management Information Base (MIB) (read-only access)

No exceptions

M Series, MX Series, and T Series

RFC 4802, Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering (TE) Management Information Base (MIB) (read-only access)

Unsupported tables and objects:

  • gmplsTunnelReversePerfTable

  • gmplsTeScalars

  • gmplsTunnelTable

  • gmplsTunnelARHopTable

  • gmplsTunnelCHopTable

  • gmplsTunnelErrorTable

M Series, MX Series, and T Series

RFC 4803, Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base (MIB) (read-only access)

Note: The tables in GMPLS TE (RFC 4802) and LSR (RFC 4803) MIBs are extensions of the corresponding tables from the MPLS TE (RFC 3812) and LSR (RFC 3813) MIBs and use the same index as the MPLS MIB tables.

Unsupported tables and objects:

  • gmplsLabelTable

  • gmplsOutsegmentTable

M Series, MX Series, and T Series

RFC 5132, IP Multicast MIB

Note: This RFC obsoletes RFC2932.

Unsupported table:

  • ipMcastZoneTable

All platforms

RFC 5643, Management Information Base for OSPFv3 (read-only access)

Unsupported tables and objects:

  • ospfv3HostTable

  • ospfv3CfgNbrTable

  • ospfv3ExitOverflowInterval

  • ospfv3ReferenceBandwidth

  • ospfv3RestartSupport

  • ospfv3RestartInterval

  • ospfv3RestartStrictLsaChecking

  • ospfv3RestartStatus

  • ospfv3RestartAge

  • ospfv3RestartExitReason

  • ospfv3NotificationEnable

  • ospfv3StubRouterSupport

  • ospfv3StubRouterAdvertisement

  • ospfv3DiscontinuityTime

  • ospfv3RestartTime

  • ospfv3AreaNssaTranslatorRole

  • ospfv3AreaNssaTranslatorState

  • ospfv3AreaNssaTranslatorStabInterval

  • ospfv3AreaNssaTranslatorEvents

  • ospfv3AreaTEEnabled

  • ospfv3IfMetricValue

  • ospfv3IfDemandNbrProbe

M Series, MX Series, PTX Series, SRX Series, and T Series

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

  • Row creation

  • The Set operation

  • Unsupported tables and objects:

    • vrrpv3StatisticsRowDiscontinuityTime

    • vrrpv3StatisticsPacketLengthErrors

ACX Series

RFC 7420, Path Computation Element Communication

The PCEP MIB module is limited to "read-only" access except for pcePcepNotificationsMaxRate, which is used to throttle the rate at which the implementation generates notifications. In the mentioned tables only PCEP peer and PCEP session table will be supported in this release.

For pcePcepPeerTable, the following members are not supported:

  • pcePcepPeerDiscontinuityTime TimeStamp,

  • pcePcepPeerLWMRspTime Unsigned32,

  • pcePcepPeerHWMRspTime Unsigned32,

  • pcePcepPeerNumPCReqSent Counter32,

  • pcePcepPeerNumPCReqRcvd Counter32,

  • pcePcepPeerNumPCRepSent Counter32,

  • pcePcepPeerNumPCRepRcvd Counter32,

  • pcePcepPeerAvgRspTime Unsigned32,

  • pcePcepPeerNumReqSent Counter32,

  • pcePcepPeerNumReqSentEroRcvd Counter32,

  • pcePcepPeerNumReqSentErrorRcvd Counter32,

  • pcePcepPeerNumReqSentTimeout Counter32,

  • pcePcepPeerNumReqSentPendRep Counter32,

  • pcePcepPeerNumReqSentCancelSent Counter32,

  • pcePcepPeerNumReqSentClosed Counter32,

  • pcePcepPeerNumReqRcvd Counter32,

  • pcePcepPeerNumPCNtfSent Counter32,

  • pcePcepPeerNumPCNtfRcvd Counter32,

  • pcePcepPeerNumSvecSent Counter32,

  • pcePcepPeerNumSvecReqSent Counter32,

  • pcePcepPeerNumSvecRcvd Counter32,

  • pcePcepPeerNumSvecReqRcvd Counter32,

  • pcePcepPeerNumReqRcvdPendRep Counter32,

  • pcePcepPeerNumReqRcvdEroSent Counter32,

  • pcePcepPeerNumReqRcvdNoPathSent Counter32,

  • pcePcepPeerNumReqRcvdCancelSent Counter32,

  • pcePcepPeerNumReqRcvdErrorSent Counter32,

  • pcePcepPeerNumReqRcvdCancelRcvd Counter32,

  • pcePcepPeerNumReqRcvdClosed Counter32,

  • pcePcepPeerNumRepRcvdUnknown Counter32,

  • pcePcepPeerNumReqRcvdUnknown Counter32,

  • pcePcepPeerNumReqSentNoPathRcvd Counter32,

  • pcePcepPeerNumReqSentCancelRcvd Counter32

MX Series and PTX Series

For pcePcepSessTable, the following members are not supported:

  • pcePcepSessNumPCReqSent Counter32,

  • pcePcepSessNumPCReqRcvd Counter32,

  • pcePcepSessKAHoldTimeRem Unsigned32,

  • pcePcepSessOverloaded TruthValue,

  • pcePcepSessOverloadTime Unsigned32,

  • pcePcepSessPeerOverloaded TruthValue,

  • pcePcepSessPeerOverloadTime Unsigned32,

  • pcePcepSessNumPCNtfSent Counter32,

  • pcePcepSessNumPCNtfRcvd Counter32,

  • pcePcepSessNumReqSent Counter32,

  • pcePcepSessNumReqSentPendRep Counter32,

  • pcePcepSessNumReqSentEroRcvd Counter32,

  • pcePcepSessNumReqSentNoPathRcvd Counter32,

  • pcePcepSessNumReqSentCancelRcvd Counter32,

  • pcePcepSessNumReqSentErrorRcvd Counter32,

  • pcePcepSessNumReqSentTimeout Counter32,

  • pcePcepSessNumReqSentCancelSent Counter32,

  • pcePcepSessAvgRspTime Unsigned32,

  • pcePcepSessLWMRspTime Unsigned32,

  • pcePcepSessHWMRspTime Unsigned32,

  • pcePcepSessNumSvecSent Counter32,

  • pcePcepSessNumSvecReqSent Counter32,

  • pcePcepSessNumReqRcvd Counter32,

  • pcePcepSessNumSvecRcvd Counter32,

  • pcePcepSessNumSvecReqRcvd Counter32,

  • pcePcepSessNumReqRcvdPendRep Counter32,

  • pcePcepSessNumReqRcvdEroSent Counter32,

  • pcePcepSessNumReqRcvdNoPathSent Counter32,

  • pcePcepSessNumReqRcvdCancelSent Counter32,

  • pcePcepSessNumReqRcvdErrorSent Counter32,

  • pcePcepSessNumReqRcvdCancelRcvd Counter32,

  • pcePcepSessNumRepRcvdUnknown Counter32,

  • pcePcepSessNumReqRcvdUnknown Counter32

ESO Consortium MIB, which can be found at http://www.snmp.com/eso/

Note: The ESO Consortium MIB has been replaced by RFC 3826.

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

Internet Assigned Numbers Authority, IANAiftype Textual Convention MIB

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

Internet draft draft-ietf-atommib-sonetaps-mib-10.txt, Definitions of Managed Objects for SONET Linear APS Architectures

As defined under the Juniper Networks enterprise branch [jnxExperiment] only

M Series, MX Series, and T Series

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

(Represented by mib-jnx-bfd-exp.txt and implemented under the Juniper Networks enterprise branch [jnxExperiment]. Read only. Includes bfdSessUp and bfdSessDown traps. Does not support bfdSessPerfTable and bfdSessMapTable.)

ACX Series, EX Series, M Series, MX Series, SRX Series, and T Series

Internet draft draft-ietf-idmr-igmp-mib-13.txt, Internet Group Management Protocol (IGMP) MIB

No exceptions

EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

Internet draft draft-ietf-idmr-pim-mib-09.txt, Protocol Independent Multicast (PIM) MIB

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series , and T Series

Internet draft draft-ietf-isis-wg-mib-07.txt, Management Information Base for IS-IS

Note: Replaced with RFC 4444, IS-IS MIB in Junos OS Release 11.3 and later.

Unsupported tables and objects:

  • isisISAdjTable

  • isisISAdjAreaAddrTable

  • isisISAdjIPAddrTable

  • isisISAdjProtSuppTable)

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

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. Read only. Includes jnxMvpnNotifications traps.)

M Series, MX Series, and T Series

Internet draft draft-ietf-mpls-mldp-mib-02.txt, Definitions of Managed Objects for the LDP Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths

Unsupported tables and objects:

  • mplsMldpInterfaceStatsTable

Also, the following fields of the mplsMldpFecUpstreamSessTable are not implemented because these statistics are not currently supported in LDP or PFE:

  • mplsMldpFecUpstreamSessPackets

  • mplsMldpFecUpstreamSessBytes

  • mplsMldpFecUpstreamSessDiscontinuityTime

M Series, MX Series, PTX Series, and T Series

Internet draft draft-ietf-mpls-p2mp-te-mib-09.txt, P2MP MPLS-TE MIB (read-only access)

Unsupported table:

  • mplsTeP2mpTunnelBranchPerfTable

ACX Series, M Series, MX Series, PTX Series, and T Series

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

Support for ospfv3NbrTable only.

M Series, MX Series, PTX Series, SRX Series, and T Series

Internet draft draft-ietf-ppvpn-mpls-vpn-mib-04.txt, MPLS/BGP Virtual Private Network Management Information Base Using SMIv2

Supported tables and objects:

  • mplsVpnScalars

  • mplsVpnVrfTable

  • mplsVpnPerTable

  • mplsVpnVrfRouteTargetTable

M Series, MX Series, PTX Series, and T Series

Internet draft draft-kamarthy-gdoi-mib-01, Management Information Base for the Group Domain of Interpretation (GDOI)

Caveats:

  • The GDOI MIB from the IETF draft is modified to include only the group member tables and notifications.

  • Only the SNMP notifications that are applicable to MX Series group members are supported.

MX Series

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

No exceptions

ACX Series, EX Series, M Series, MX Series, PTX Series, SRX Series, and T Series

For information about standard SNMP MIB objects, see the SNMP MIB Explorer.