Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

SNMP MIBs and Traps Supported by Junos OS

Enterprise-Specific SNMP MIBs Supported by Junos OS

Junos OS supports the enterprise-specific MIBs listed in Table 1. For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer.

Table 1: Enterprise-specific MIBs supported by Junos OS

Enterprise-Specific MIB

Description

Platforms

AAA Objects MIB

Provides support for monitoring user authentication, authorization, and accounting through the RADIUS, LDAP, SecurID, and local authentication servers.

SRX Series and vSRX

Access Authentication Objects MIB

Provides support for monitoring firewall authentication, including data about the users trying to access firewall-protected resources and the firewall authentication service itself.

SRX Series and vSRX

Alarm MIB

Provides information about alarms from the router chassis.

All platforms

Analyzer MIB

Provides information about analyzer and remote analyzer related to port mirroring on the EX Series Ethernet Switches. Port mirroring is a method used on enterprise switches to monitor and analyze traffic on the network. When port mirroring is enabled, copies of all (or a sample set of) packets are forwarded from one port of the switch to another port on the same switch (analyzer) or on another switch (remote analyzer) where the packet can be analyzed and studied.

EX Series, QFabric system, and QFX Series

Antivirus Objects MIB

Provides information about the antivirus engine, antivirus scans, and antivirus scan-related traps.

SRX Series and vSRX

ATM Class-of-Service MIB

Provides support for ATM interfaces and virtual connections.

ACX Series, M Series, and T Series

ATM MIB

Provides support for monitoring Asynchronous Transfer Mode, version 2 (ATM2) virtual circuit (VC) class-of-service (CoS) configurations. It also provides CoS queue statistics for all VCs that have CoS configured.

M Series, SRX Series, T Series and vSRX

BGP4 V2 MIB

Provides support for monitoring BGP peer-received prefix counters. It is based upon similar objects in the MIB documented in Internet draft draft-ietf-idr-bgp4-mibv2-03.txt, Definitions of Managed Objects for the Fourth Version of BGP (BGP-4), Second Version.

All platforms

BGP MIB

Contains the objects for BGP version.

MX Series

Bidirectional Forwarding Detection MIB

Provides support for monitoring Bidirectional Forwarding Detection (BFD) sessions.

All platforms

Chassis Cluster MIB

Provides information about objects that are used whenever the state of the control link interfaces or fabric link interfaces changes (up to down or down to up) in a chassis cluster deployment.

SRX Series and vSRX

Chassis Definitions for Router Model MIB

Contains the object identifiers (OIDs) that are used by the Chassis MIB to identify platform and chassis components. The Chassis MIB provides information that changes often, whereas the Chassis Definitions for Router Model MIB provides information that changes less often.

ACX Series, M Series, MX Series, PTX Series, QFX Series, SRX550, SRX1500, and T Series

Chassis MIBs

Provides support for environmental monitoring (power supply state, board voltages, fans, temperatures, and air flow) and inventory support for the chassis, System Control Board (SCB), System and Switch Board (SSB), Switching and Forwarding Module (SFM), Switch Fabric Board (SFB), Flexible PIC Concentrators (FPCs), and PICs.

All platforms

Class-of-Service MIB

Provides support for monitoring interface output queue statistics per interface and per forwarding class.

Provides support for monitoring Priority-Based Flow Control (PFC) statistics. The entries in the jnxCosPfcPriorityTable of Class-of-Service MIB include jnxCosPfcPriorityEntry, jnxCosIfIndex, jnxCosPfcPriorityIndex, jnxCosPfcPriorityRequestsTx, and jnxCosPfcPriorityRequestsRx.

ACX Series, EX Series, M Series, MX Series, PTX Series, QFabric system, QFX Series, SRX Series, T Series, and vSRX

CGNAT MIB

Provides information about various services interfaces Used for CGNAT implementation.

  • SRX – USF (MX-SPC3) JUNIPER-JS-NAT-MIB
  • MS-MPC JUNIPER-NET-MIB

MX Series and SRX Series

Configuration Management MIB

Provides notification for configuration changes as SNMP traps. Each trap contains the time at which the configuration change was committed, the name of the user who made the change, and the method by which the change was made. A history of the last 32 configuration changes is kept in jnxCmChgEventTable.

All platforms

Destination Class Usage MIB

Provides support for monitoring packet counts based on the ingress and egress points for traffic transiting your networks. Ingress points are identified by the input interface. Egress points are identified by destination prefixes grouped into one or more sets, known as destination classes. One counter is managed per interface per destination class, up to a maximum of 16 counters per interface.

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

DHCP MIB

Provides SNMP support (get and trap) for DHCP local server and relay configurations. It also provides support for bindings and leases tables, and for statistics.

M Series, MX Series, and T Series

DHCPv6 MIB

Provides SNMP support (get and trap) for DHCPv6 local server and relay configurations. It also provides support for bindings and leases tables, and for statistics.

M Series, MX Series, and T Series

Digital Optical Monitoring MIB

Provides support for the SNMP Get request for statistics and SNMP Trap notifications for alarms.

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

DNS Objects MIB

Provides support for monitoring DNS proxy queries, requests, responses, and failures.

SRX Series and vSRX

Dynamic Flow Capture MIB

Provides support for monitoring the operational status of dynamic flow capture (DFC) PICs.

M Series and T Series

Ethernet MAC MIB

Monitors media access control (MAC) statistics on Gigabit Ethernet intelligent queuing (IQ) interfaces. It collects MAC statistics; for example, inoctets, inframes, outoctets, and outframes on each source MAC address and virtual LAN (VLAN) ID for each Ethernet port.

EX Series, M Series, MX Series, QFX Series, SRX300, SRX320, SRX340, SRX550, SRX1500 and T Series

Event MIB

Defines a generic trap that can be generated using an op script or event policy. This MIB provides the ability to specify a system log string and raise a trap if that system log string is found.

ACX Series, EX Series, M Series, MX Series, PTX Series, QFabric system, QFX Series, SRX1500, SRX300, SRX320, SRX340, SRX550, and T Series

Experimental MIB

Contains object identifiers for experimental MIBs.

ACX Series, M series, MX Series, and T series

EX Series MAC Notification MIB

Contains Juniper Networks' implementation of enterprise-specific MIB for Ethernet Mac Stats for EX Series.

EX Series

EX Series SMI MIB

Contains the Structure of Management Information for Juniper Networks EX Series platforms.

EX Series

Firewall MIB

Provides support for monitoring firewall filter counters. Routers must have the Internet Processor II ASIC to perform firewall monitoring.

ACX Series, EX Series, M Series, MX Series, PTX Series, QFabric system, QFX Series, SRX300, SRX320, SRX340, SRX550, SRX1500 and T Series

Flow Collection Services MIB

Provides statistics on files, records, memory, FTP, and error states of a monitoring services interface. It also provides SNMP traps for unavailable destinations, unsuccessful file transfers, flow overloading, and memory overloading.

M Series and T Series

GRE Keepalive Monitoring MIB

Provides support for monitoring generic routing encapsulation (GRE) keepalive status. This MIB also provides an SNMP trap when GRE keepalive status changes.

SRX Series and vSRX instances

Host Resources MIB

Extends the hrStorageTable object, providing a measure of the usage of each file system on the router in percentage format. Previously, the objects in the hrStorageTable measured the usage in allocation units—hrStorageUsed and hrStorageAllocationUnits—only. Using the percentage measurement, you can more easily monitor and apply thresholds on usage.

ACX Series, EX Series, M Series, MX Series, QFX Series, SRX300, SRX320, SRX340, SRX550, SRX1500 and T Series

Interface Accounting Forwarding Class MIB

Extends the Juniper Enterprise Interface MIB and provides support for monitoring statistics data for interface accounting and IETF standardization.

M Series, MX Series, SRX Series, and vSRX

Interface MIB

Extends the standard ifTable (RFC 2863) with additional statistics and Juniper Networks enterprise-specific chassis information.

ACX Series, EX Series, M Series, MX Series, PTX Series, QFabric system, QFX Series, SRX300, SRX320, SRX340, SRX550, SRX1500 and T Series

IP Forward MIB

Extends the standard IP Forwarding Table MIB (RFC 4292) to include CIDR forwarding information.

All platforms

IPsec Generic Flow Monitoring Object MIB

Based on jnx-ipsec-monitor-mib, this MIB provides support for monitoring IPsec and IPsec VPN management objects.

SRX Series and vSRX

IPsec Monitoring MIB

Provides operational and statistical information related to the IPsec and IKE tunnels on Juniper Networks routers.

M Series, SRX Series, and T Series

IPsec VPN Objects MIB

Provides support for monitoring IPsec and IPsec VPN management objects for Juniper products. This MIB is an extension of jnx-ipsec-flow-mon.mib.

SRX Series and MX Series with USF

IPv4 MIB

Provides additional Internet Protocol version 4 (IPv4) address information, supporting the assignment of identical IPv4 addresses to separate interfaces.

All platforms

IPv6 and ICMPv6 MIB

Provides IPv6 and Internet Control Message Protocol version 6 (ICMPv6) statistics.

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

jnxJsChassisHA

Provides Chassis High Availability with ensuring minimal disruption to services in case of a failover. If one of the chassis in a High Availability environment fails, the other chassis takes over the function of the failed chassis with minimal service interruption. This module defines the objects pertaining to Chassis High Availability.

SRX5400, SRX5600, and SRX5800.

jnxJsFlowSofSummary MIB

Provides the total number of Express Path mode (formerly known as services offloading) sessions in use and total number of packets processed so far in logical system.

SRX4600, SRX5400, SRX5600, and SRX5800.

jnxJsChNodeCPUStatus

Monitors Routing Engine CPU load usage. It sends a notification to users when Routing Engine CPU load is below set threshold.

SRX5400, SRX5600, SRX5800, SRX4600, SRX4200, SRX4100, and SRX1500.

jnxJsChNodeJunosKernelStatus

Monitors Junos Kernel usage.

SRX5400, SRX5600, SRX5800, SRX4600, SRX4200, SRX4100, and SRX1500.

jnxUserFirewalls MIB

Exports statistics of User Firewall identity-management counters.

SRX Series and vSRX

jnxTLBMIB

Exports statistics of Traffic Load Balancer application

MX240, MX480, and MX960

JNX BGP MIB2

Support IPV6 objects and prefix counters for BGP.

MX Series

JNX VPN MIB (L2VPN)

Contains information about L2VPN protocol.

MX Series

L2ALD MIB

Contains information about the Layer 2 Address Learning Daemon (L2ALD) and related traps, such as the routing instance MAC limit trap and the interface MAC limit trap. This MIB also provides VLAN information in the jnxL2aldVlanTable table for Enhanced Layer 2 Software (ELS) EX Series and QFX Series switches.

Note:

Non-ELS EX Series switches support the VLAN MIB (jnxExVlanTable table) for VLAN information instead of this MIB. See the SNMP MIB Explorer.

EX Series, MX Series, QFX Series, and T Series

L2CP MIB

Provides information about Layer 2 Control Protocols (L2CP) based features. Currently, Junos OS supports only the jnxDot1dStpPortRootProtectEnabled, jnxDot1dStpPortRootProtectState, and jnxPortRootProtectStateChangeTrap objects.

MX Series

L2TP MIB

Provides information about Layer 2 Transport Protocol (L2TP) tunnels and sessions.

M Series, MX Series, and T Series

LDP MIB

Provides LDP statistics and defines LDP label-switched path (LSP) notifications. LDP traps support only IPv4 standards.

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

License MIB

Extends SNMP support to licensing information, and introduces SNMP traps that alert users when the licenses are about to expire, expire, or when the total number of users exceeds the number specified in the license.

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

Logical Systems MIB

Extend SNMP support to logical systems security profile through various MIBs defined under jnxLsysSecurityProfile.

SRX Series

LTE MIB

Extend SNMP support to monitor the 4G LTE Mini-Physical Interface Module (Mini-PIM) status using SNMP remote network management.

SRX300, SRX320, SRX340, SRX345, and SRX550M.

LSYSTSYS MIB (jnxLsysVD) Shows the below details of configured logical systems and tenant:
  • total LSYS count
  • total TSYS count
  • total security profiles count
  • maximally allowed LSYS capacity
  • maximally allowed TSYS capacity
  • maximally allowed security profiles capacity
SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800, and vSRX

MIMSTP MIB

Provides information about MSTP instances (that is, routing instances of type Virtual Switch/Layer 2 control, also known as virtual contexts), MSTIs within the MSTP instance, and VLANs associated with the MSTI.

MX Series and T Series

MPLS LDP MIB

Contains object definitions as described in RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP).

Note:

Objects in the MPLS LDP MIB were supported in earlier releases of Junos OS as a proprietary LDP MIB (mib-ldpmib.txt). Because the branch used by the proprietary LDP (mib-ldpmib.txt) conflicts with RFC 3812, the proprietary LDP MIB (mib-ldpmib.txt) has been deprecated and replaced by the enterprise-specific MPLS LDP MIB (mib-jnx-mpls-ldp.txt).

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

MPLS MIB

Provides MPLS information and defines MPLS notifications.

Note:

To collect information about MPLS statistics on transit routers, use the enterprise-specific RSVP MIB (mib-jnx-rsvp.txt) instead of the enterprise-specific MPLS MIB (mib-jnx-mpls.txt).

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

MVPN MIB

Contains objects that enable SNMP manager to monitor MVPN connections on the provider edge routers. The enterprise-specific MVPN MIB is the Juniper Networks extension of the IETF standard MIBs defined in Internet draft draft-ietf-l3vpn-mvpn-mib-03.txt, MPLS/BGP Layer 3 VPN Multicast Management Information Base.

All platforms

MPLS L3VPN MIB

Contains the attributes for L3VPN based MPLS.

MX Series

MPLS VPN MIB

Contains the objects for MPLS VPN.

MX Series

NAT Objects MIB

Provides support for monitoring network address translation (NAT). .

EX Series and SRX Series

NAT Resources-Monitoring MIB

Provides support for monitoring NAT pools usage and NAT rules. Notifications of usage of NAT resources are also provided by this MIB. This MIB is currently supported on the Multiservices PIC and Multiservices DPC on M Series and MX Series routers only.

M Series and MX Series

OTN Interface Management MIB

Defines objects for managing Optical Transport Network (OTN) interfaces on devices running Junos OS.

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

Packet Forwarding Engine MIB

Provides notification statistics for Packet Forwarding Engines.

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

Packet Mirror MIB

Enables you to capture and view packet mirroring-related information. This MIB is currently supported by Junos OS for MX Series routers only. Packet mirroring traps are an extension of the standard SNMP implementation and are only available to SNMPv3 users.

MX Series

PAE Extension MIB

Extends the standard IEEE802.1x PAE Extension MIB, and contains information for Static MAC Authentication.

EX Series

Passive Monitoring MIB

Performs traffic flow monitoring and lawful interception of packets transiting between two routers.

M Series and T Series

Ping MIB

Extends the standard Ping MIB control table (RFC 2925). Items in this MIB are created when entries are created in pingCtlTable of the Ping MIB. Each item is indexed exactly as it is in the Ping MIB.

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

Policy Objects MIB

Provides support for monitoring the security policies that control the flow of traffic from one zone to another.

SRX Series

Power Supply Unit MIB

Enables monitoring and managing of the power supply on a device running Junos OS.

EX Series and QFabric system

PPP MIB

Provides SNMP support for PPP-related information such as the type of authentication used, interface characteristics, status, and statistics. This MIB is supported on Common Edge PPP process, jpppd.

M Series and MX Series

PPPoE MIB

Provides SNMP support for PPPoE-related information such as the type of authentication used, interface characteristics, status, and statistics. This MIB is supported on Common Edge PPPoE process, jpppoed.

M Series and MX Series

Pseudowire ATM MIB

Extends the standard Pseudowire MIB, and defines objects used for managing the ATM pseudowires in Juniper products. The enterprise-specific Pseudowire ATM MIB is the Juniper Networks implementation of RFC 5605, Managed Objects for ATM over Packet Switched Networks (PSNs).

M Series and MX Series

Pseudowire TDM MIB

Extends the standard Pseudowire MIB, and contains information about configuration and statistics for specific pseudowire types. The enterprise-specific Pseudowire TDM MIB is the Juniper Networks implementation of the standard Managed Objects for TDM over Packet Switched Network MIB (draft-ietf-pwe3-tdm-mib-08.txt).

ACX Series, M Series, and T Series

PTP MIB

Monitors the operation of PTP clocks within the network.

MX Series

Real-Time Performance Monitoring MIB

Provides real-time performance-related data and enables you to access jitter measurements and calculations using SNMP.

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

Reverse-Path-Forwarding MIB

Monitors statistics for traffic that is rejected because of reverse-path-forwarding (RPF) processing.

All platforms

RMON Events and Alarms MIB

Supports the Junos OS extensions to the standard Remote Monitoring (RMON) Events and Alarms MIB (RFC 2819). The extension augments alarmTable with additional information about each alarm. Two new traps are also defined to indicate when problems are encountered with an alarm.

All platforms

RSVP MIB

Provides information about RSVP-traffic engineering sessions that correspond to MPLS LSPs on transit routers in the service provider core network.

Note:

To collect information about MPLS statistics on transit routers, use the enterprise-specific RSVP MIB (mib-jnx-rsvp.txt) instead of the enterprise-specific MPLS MIB (mib-jnx-mpls.txt).

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

Service OAM MIB The jnx-soam-pm.mib MIB provides SNMP support for service OAM performance monitoring functions. SRX380, SRX300, SRX320, SRX340, SRX345, and SRX550HM

Security Interface Extension Objects MIB

Provides support for the security management of interfaces.

EX Series, SRX Series, and vSRX

Security Screening Objects MIB

Defines the MIB for the Juniper Networks Enterprise Firewall screen functionality.

SRX Series and vSRX

Services PIC MIB

Provides statistics for Adaptive Services (AS) PICs and defines notifications for AS PICs.

M Series and T Series

SNMP IDP MIB

Contains Juniper Networks' implementation of enterprise specific MIB for IDP.

SRX Series and vSRX

SONET APS MIB

Monitors any SONET interface that participates in Automatic Protection Switching (APS).

M Series and T Series

SONET/SDH Interface Management MIB

Monitors the current alarm for each SONET/SDH interface.

M Series and T Series

Source Class Usage MIB

Counts packets sent to customers by performing a lookup on the IP source address and the IP destination address. The Source Class Usage (SCU) MIB makes it possible to track traffic originating from specific prefixes on the provider core and destined for specific prefixes on the customer edge.

M Series, T Series, and SRX Series

SPU Monitoring MIB

Provides support for monitoring SPUs on SRX5600 and SRX5800 devices.

SRX Series and vSRX

Structure of Management Information MIB

Explains how the Juniper Networks enterprise-specific MIBs are structured.

ACX Series, EX Series, M Series, MX series, QFX Series, SRX Series, T Series and vSRX

Structure of Management Information MIB for EX Series Ethernet Switches

Defines a MIB branch for switching-related MIB definitions for the EX Series Ethernet Switches.

EX Series

Structure of Management Information MIB for SRX Series

Contains object identifiers (OIDs) for the security branch of the MIBs used in Junos OS for SRX Series devices, services, and traps.

SRX Series and vSRX

Subscriber MIB

Provides SNMP support for subscriber-related information.

ACX Series, MX Series, and T Series

System Log MIB

Enables notification of an SNMP trap-based application when an important system log message occurs.

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

Traceroute MIB

Supports the Junos OS extensions of traceroute and remote operations. Items in this MIB are created when entries are created in the traceRouteCtlTable of the Traceroute MIB. Each item is indexed exactly the same way as it is in the Traceroute MIB.

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

Tunnel Stats MIB

Supports monitoring of tunnel statistics for IPV4 over IPV6 tunnels. This MIB currently displays three counters: tunnel count in rpd, tunnel count in Kernel, and tunnel count in the Packet Forwarding Engine.

all platforms

Utility MIB

Provides SNMP support for exposing the Junos OS data and has tables that contain information about each type of data, such as integer and string.

EX Series, M Series, MX Series, QFabric system, QFX Series, SRX Series, T Series, and vSRX

Virtual Chassis MIB

Contains information about the virtual chassis on the EX Series Ethernet Switches and the MX Series.

EX Series and MX Series

VLAN MIB

Contains information about prestandard IEEE 802.10 VLANs and their association with LAN emulation clients.

Note:

For ELS EX Series switches and QFX Series switches, VLAN information is provided in the L2ALD MIB in the jnxL2aldVlanTable table instead of in this MIB. See theSNMP MIB Explorer for details.

Non-ELS EX Series Ethernet switches use the jnxExVlanTable table in this MIB to provide VLAN configuration information, and the jnxVlanTable table in this MIB has been deprecated and is no longer used.

EX Series and QFX Series

VPLS MIBs

Provides information about generic, BGP-based, and LDP-based VPLS, and pseudowires associated with the VPLS networks. The enterprise-specific VPLS MIBs are Juniper Networks extensions of the following IETF standard MIBs defined in Internet draft draft-ietf-l2vpn-vpls-mib-05.txt, and are implemented as part of the jnxExperiment branch:

  • VPLS-Generic-Draft-01-MIB implemented as mib-jnx-vpls-generic.txt

  • VPLS-BGP-Draft-01-MIB implemented as mib-jnx-vpls-bgp.txt

  • VPLS-LDP-Draft-01-MIB implemented as mib-jnx-vpls-ldp.txt

M Series, MX Series, and T Series

VPN Certificate Objects MIB

Provides support for monitoring the local and CA certificates loaded on the router.

EX Series, SRX Series, and vSRX

VPN MIB

Provides monitoring for Layer 3 VPNs, Layer 2 VPNs, and virtual private LAN service (VPLS) (read access only).

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

Starting in Junos OS Release 18.4R1, you can monitor 4G LTE Mini-PIM status by using SNMP remote network management.

You can use the following commands to monitor the 4G LTE Mini-PIM status:

show snmp mib walk ascii jnxWirelessWANNetworkInfoTable

show snmp mib walk ascii jnxWirelessWANFirmwareInfoTable

In previous releases, the show modem wireless network interface interface-name and show modem wireless firmware interface interface-name commands are used to check the 4G LTE Mini-PIM status.

Starting in Junos OS Release 19.4R1, on SRX5000 Series devices with SRX5K-SPC3 card, we have enhanced the existing IPsec VPN flow monitor MIB jnxIpSecFlowMonMIB to support the global IKE statistics for tunnels using IKEv2. Use the show security ike stats command to display the global statistics of tunnels such as in-progress, established, and expired negotiations using IKEv2.

Starting in Junos OS Release 20.1R1, you can enable the peer down and IPsec tunnel down traps and configure the certificate authority (CA) and local certificate traps. We’ve enhanced the existing IPsec VPN flow monitor MIB jnxIpSecFlowMonMIB to support the global data plane, active IKE SA, active IPsec SA, and active peer statistics for tunnels using IKEv2. We've also enhanced the output of the show security ike stats command to add additional options (<brief> | <detail>). Use the clear security ike stats command to clear the IKEv2 statistic counters.

For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer.

Starting in Junos OS Release 20.4R1, you can monitor CPU and Kernel usage on Routing Engine using reswatch process.

Standard SNMP MIBs Supported by Junos OS

Junos OS supports the Standard MIBs listed in Table 2.

Note:

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

Table 2: 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, PTX 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), L3VPN MIB

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

No exceptions

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.

Enterprise-Specific MIBs for Junos OS Evolved

Starting in Junos OS Evolved Release 19.1R1, the enterprise-specific MIBs listed in Table 3 are supported. For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer.

Table 3: Enterprise-Specific MIBs Supported by Junos OS Evolved

Enterprise-Specific MIB

Description

Exceptions

Platform

BGP4 V2 MIB

Provides support for monitoring BGP peer-received prefix counters. It is based upon similar objects in the MIB documented in Internet draft draft-ietf-idr-bgp4-mibv2-03.txt, Definitions of Managed Objects for the Fourth Version of BGP (BGP-4), Second Version.

No exceptions

PTX10003

Chassis MIBs

Provides support for environmental monitoring (power supply state, board voltages, fans, temperatures, and air flow) and inventory support for the chassis, System Control Board (SCB), System and Switch Board (SSB), Switching and Forwarding Module (SFM), Switch Fabric Board (SFB), Flexible PIC Concentrators (FPCs), and PICs.

Supported traps:

  • jnxFruInsertion

  • jnxFruRemoval

  • jnxFruPowerOn

  • jnxFruPowerOff

  • jnxFruOnline

  • jnxFruOffline

  • jnxFruFailed

  • jnxFruOK

  • jnxPowerSupplyFailure

  • jnxPowerSupplyOK

  • jnxPowerSupplyInputFailure

  • jnxPowerSupplyInputOK

  • jnxFanFailure

  • jnxFanOK

  • jnxOverTemperature

  • jnxTemperatureOK

Supported tables and objects:

  • jnxBoxClass

  • jnxBoxDescr

  • jnxBoxSerialNo

  • jnxBoxRevision

  • jnxBoxInstalled

  • jnxContentsLastChange

  • jnxContainersTable

  • jnxOperatingTable

  • jnxRedundancyTable

  • jnxContentsTable

  • jnxFilledTable

  • jnxFruTable

PTX10003

Firewall MIB Provides bytes and packets count of interface attached policers.

Supported tables and objects:

  • jnxFWCntrXTable
PTX10001-36MR, PTX10004, and PTX10008

Class-of-Service MIB

Provides support for monitoring interface output queue statistics per interface and per forwarding class.

No exceptions

PTX10003

Host Resources MIB

Extends the hrStorageTable object, providing a measure of the usage of each file system on the router in percentage format. Previously, the objects in the hrStorageTable measured the usage in allocation units—hrStorageUsed and hrStorageAllocationUnits—only. Using the percentage measurement, you can more easily monitor and apply thresholds on usage.

Supported tables and objects:

  • hrStorageTable

  • jnxHrStorage

  • hrSWInstalledTable

  • hrSystemUptime

  • hrSystemDate

  • hrSystemInitialLoadDevice

  • hrSystemInitialLoadParameters

  • hrSystemNumUsers

  • hrSystemProcesses

  • hrSystemMaxProcesses

  • hrMemorySize

  • hrSWInstalledLastChange

  • hrSWInstalledLastUpdateTime

PTX10003

Interface MIB

Extends the standard ifTable (RFC 2863) with additional statistics and Juniper Networks enterprise-specific chassis information.

No exceptions

PTX10003

IPv4 MIB

Provides additional IPv4 address information, supporting the assignment of identical IPv4 addresses to separate interfaces.

No exceptions

PTX10003

IPv6 and ICMPv6 MIB

Provides IPv6 and Internet Control Message Protocol version 6 (ICMPv6) statistics.

Unsupported objects

  • jnxIcmpv6GlobalStats branch and the objects under it

PTX10003

LDP MIB

Provides LDP statistics and defines LDP label-switched path (LSP) notifications. LDP traps support only IPv4 standards.

No exceptions

PTX10003

MPLS LDP MIB

Contains object definitions as described in RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP).

No exceptions

PTX10003

MPLS MIB

Provides MPLS information and defines MPLS notifications.

No exceptions

PTX10003

RSVP MIB

Provides information about RSVP-traffic engineering sessions that correspond to MPLS LSPs on transit routers in the service provider core network.

No exceptions

PTX10003

SFF Digital Optical Monitor MIB

Defines objects used for Digital Optical Monitor on interfaces of Juniper products.

Supported tables:

  • jnxDomCurrentTable

  • jnxDomModuleLaneTable

PTX10003

TWAMP MIB (jnxTwampMib) Monitors network performance using Two-Way Active Measurement Protocol.

Supported tables:

  • jnxTwampClientResultsSampleTable
  • jnxTwampClientResultsSummaryTable
  • jnxTwampClientResultsCalculatedTable
  • jnxTwampClientHistorySampleTable
  • jnxTwampClientHistorySummaryTable
  • jnxTwampClientHistoryCalculatedTable
  • jnxTwampClientControlConnectionTable
  • jnxTwampClientTestSessionsTable

Supported traps:

  • jnxTwampClientControlConnectionClosed
  • jnxTwampClientTestIterationFinished
  • pingProbeFailed
  • pingTestFailed
  • pingTestCompleted
  • jnxPingRttThresholdExceeded
  • jnxPingRttJitterThresholdExceeded
  • jnxPingEgressThresholdExceeded
  • jnxPingEgressJitterThresholdExceeded
  • jnxPingIngressThresholdExceeded
  • jnxPingIngressJitterThresholdExceeded
  • jnxPingMaxRttThresholdExceeded
PTX10001-36MR, PTX10003, PTX10004, and PTX10008
Timing MlB (jnxTimingNotfnsMIB) Defines Synchronous Ethernet (SyncE) objects, faults, and events. Supported traps:
  • jnxTimingFaultLOSSet
  • jnxTimingFaultLOSClear
  • jnxTimingFaultEFDSet
  • jnxTimingFaultEFDClear
  • jnxTimingFaultLOESMCSet
  • jnxTimingFaultLOESMCClear
  • jnxTimingFaultQLFailSet
  • jnxTimingFaultQLFailClear
  • jnxTimingFaultLTISet
  • jnxTimingFaultLTIClear
  • jnxTimingFaultPriSrcFailed
  • jnxTimingFaultSecSrcFailed
  • jnxTimingEventPriSrcRecovered
  • jnxTimingEventSecSrcRecovered
  • jnxTimingEventPriRefChanged
  • jnxTimingEventSecRefChanged
  • jnxTimingEventQLChangedRx
  • jnxTimingEventQLChangedTx
  • jnxTimingEventDpllStatus
  • jnxTimingEventSynceDpllStatus
Supported objects and tables:
  • jnxClksyncIfIndex
  • jnxClksyncIntfName
  • jnxClksyncQualityCode
  • jnxClksyncQualityCodeStr
  • jnxClksyncDpllState
  • jnxClksyncDpllStateStr
  • jnxClksyncSynceLockedIfIndex
  • jnxClksyncSynceLockedIntfName
  • jnxClksyncSynceQualityTable
PTX10008

VPN MIB

Provides monitoring for Layer 3 VPNs, Layer 2 VPNs, and virtual private LAN service (VPLS).

Unsupported objects

  • jnxVpnActiveVpns

  • jnxVpnConfiguredVpns

PTX10003

Standard MIBs for Junos OS Evolved

Starting in Junos OS Evolved Release 19.1R1, the Standard MIBs listed in Table 4 are supported. For information about Standard MIB objects, see the SNMP MIB Explorer.

Table 4: Standard MIBs Supported by Junos OS Evolved

Standard MIB

Exceptions

Platforms

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

No exceptions

PTX10003

RFC 1157, A Simple Network Management Protocol (SNMP)

No exceptions

PTX10003

RFC 1212, Concise MIB Definitions

No exceptions

PTX10003

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

Unsupported tables and objects:

  • ICMP group

PTX10003

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

No exceptions

PTX10003

RFC 1850, OSPF Version 2 Management Information Base

No exceptions

PTX10003

RFC 1901, Introduction to Community-Based SNMPv2

No exceptions

PTX10003

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

No exceptions

PTX10003

RFC 2096, IP Forwarding Table MIB

No exceptions

PTX10003

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

Supported tables and objects:

  • ipv6AddrTable

  • ipv6NetToMediaTable

  • ipv6IfTable

  • ipv6IfStatsTable

  • ipv6AddrPrefixTable

  • ipv6IfTableLastChange

  • ipv6Interfaces

  • ipv6Forwarding

  • ipv6DefaultHopLimit

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

RFC 2579, Textual Conventions for SMIv2

No exceptions

PTX10003

RFC 2580, Conformance Statements for SMIv2

No exceptions

PTX10003

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

Unsupported tables and objects:

  • dot3

PTX10003

RFC 2790, Host Resources MIB

Unsupported tables and objects:

  • hrDeviceTable

  • hrSWRunTable

  • hrSWRunPerfTable

PTX10003

RFC 2863, The Interfaces Group MIB

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

RFC 2932, IPv4 Multicast Routing MIB

No exceptions

PTX10003

RFC 2934, Protocol Independent Multicast MIB for IPv4

No exceptions

PTX10003

RFC 2981, Event MIB

No exceptions

PTX10003

RFC 3014, Notification Log MIB

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

RFC 3413, Simple Network Management Protocol (SNMP) Applications

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003, PTX10008

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

PTX10003

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

No exceptions

PTX10003

RFC 3877, Alarm Management Information Base

No exceptions

PTX10003

RFC 4133, Entity MIB

Supported table:

  • entPhysicalTable

PTX10003

RFC 4292, IP Forwarding MIB

No exceptions

PTX10003

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

Supported tables:

  • ipAddressTable

  • ipAddrTable

  • ipNetToPhysicalTable

  • ipNetToMediaTable

  • ipSystemStatsTable

Unsupported objects:

  • icmpMsgStatsIPVersion

  • icmpMsgStatsType

  • icmpMsgStatsInPkts

  • icmpMsgStatsOutPkts

  • icmpStatsIPVersion

  • icmpStatsInMsgs

  • icmpStatsInErrors

  • icmpStatsOutMsgs

  • icmpStatsOutErrors

PTX10003

RFC 4444, IS-IS MIB

No exceptions

PTX10003

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

No exceptions

PTX10003

IEEE, 802.3ad, Aggregation of Multiple Link Segments

Supported objects for PTX10008 on Junos OS Evolved Release 20.1R1:

  • dot3adAggPortStatsLACPDUsRx, dot3adAggPortStatsMarkerPDUsRx, dot3adAggPortStatsMarkerResponsePDUsRx, dot3adAggPortStatsUnknownRx, dot3adAggPortStatsIllegalRx, dot3adAggPortStatsLACPDUsTx, dot3adAggPortStatsMarkerPDUsTx, and dot3adAggPortStatsMarkerResponsePDUsTx

  • dot3adInterfaceName, dot3adOperState, dot3adAggname, and dot3adInterfaceTimeout.

Unsupported objects for PTX10008 on Junos OS Evolved Release 20.1R1:

  • dot3adAggActorSystemPriority, dot3adAggActorSystemID, dot3adAggActorAdminKey, and dot3adAggActorOperKey.

  • dot3adAggMACAddress, dot3adAggAggregateOrIndividual, dot3adAggPartnerSystemID, dot3adAggPartnerSystemPriority, dot3adAggPartnerOperKey, dot3adAggCollectorMaxDelay, dot3adAggPortListPorts, and dot3adTablesLastChanged

  • dot3adAggPortActorSystemPriority, dot3adAggPortActorSystemID, dot3adAggPortActorAdminKey, dot3adAggPortActorOperKey, dot3adAggPortActorPort,dot3adAggPortActorPortPriority, dot3adAggPortActorAdminState, and dot3adAggPortActorOperState

  • dot3adAggPortPartnerAdminSystemPriority, dot3adAggPortPartnerOperSystemPriority, dot3adAggPortPartnerAdminSystemID, dot3adAggPortPartnerOperSystemID, dot3adAggPortPartnerAdminKey,dot3adAggPortPartnerOperKey, dot3adAggPortPartnerAdminPort, dot3adAggPortPartnerOperPort, dot3adAggPortPartnerAdminPortPriority, and dot3adAggPortPartnerOperPortPriority

  • dot3adAggPortDebugRxState, dot3adAggPortDebugLastRxTime, dot3adAggPortDebugMuxState, dot3adAggPortDebugMuxReason, dot3adAggPortDebugActorChurnState, dot3adAggPortDebugPartnerChurnState, dot3adAggPortDebugActorChurnCount, dot3adAggPortDebugPartnerChurnCount, dot3adAggPortDebugActorSyncTransitionCount, dot3adAggPortDebugPartnerSyncTransitionCount, dot3adAggPortDebugActorChangeCount, and dot3adAggPortDebugPartnerChangeCount.

PTX10003

Internet Assigned Numbers Authority, IANAiftype Textual Convention MIB

No exceptions

PTX10003

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

No exceptions

PTX10003

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

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

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

No exceptions

PTX10003

Standard SNMP Traps Supported by Junos OS

This topic provides the list of standard SNMPv1 and SNMPv2 traps supported by devices running Junos OS. For more information about traps see SNMP MIB Explorer.

Starting in Junos OS Release 20.1, after graceful routing engine switchover (GRES), the new primary Routing Engine sends a single warmStart notification. The primary Routing Engine sends a coldStart notification when the device comes up. The primary Routing Engine also sends warmStart notifications for subsequent restarts of the SNMP daemon. After GRES, the new primary Routing Engine sends a single warmStart notification and the backup Routing Engine does not send any notification.

Standard SNMP Version 1 Traps

Table 5 provides an overview of the standard traps for SNMPv1. The traps are organized first by trap category and then by trap name, and include their enterprise ID, generic trap number, and specific trap number. The system logging severity levels are listed for those traps that have them with their corresponding system log tag. Traps that do not have corresponding system logging severity levels are marked with an en dash (–) in the table.

For more information about system log messages, see the System Log Explorer.

Table 5: Standard Supported SNMP Version 1 Traps

Defined in

Trap Name

Enterprise ID

Generic Trap Number

Specific Trap Number

System Logging Severity Level

Syslog Tag

Supported On

Startup Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

authenticationFailure

1.3.6.1.4.1.2636

4

0

Notice

SNMPD_ TRAP_ GEN_FAILURE

All devices running Junos OS.

coldStart

1.3.6.1.4.1.2636

0

0

Critical

SNMPD_TRAP_ COLD_START

All devices running Junos OS.

warmStart

1.3.6.1.4.1.2636

1

0

Error

SNMPD_TRAP_ WARM_START

All devices running Junos OS.

Link Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

linkDown

1.3.6.1.4.1.2636

2

0

Warning

SNMP_ TRAP_ LINK_DOWN

All devices running Junos OS.

linkUp

1.3.6.1.4.1.2636

3

0

Info

SNMP_TRAP_ LINK_UP

All devices running Junos OS.

Remote Operations Notifications

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

pingProbeFailed

1.3.6.1.2.1.80.0

6

1

Info

SNMP_TRAP _PING_ PROBE_ FAILED

All devices running Junos OS.

pingTestFailed

1.3.6.1.2.1.80.0

6

2

Info

SNMP_TRAP_ PING_TEST _FAILED

All devices running Junos OS.

pingTestCompleted

1.3.6.1.2.1.80.0

6

3

Info

SNMP_TRAP_ PING_TEST_ COMPLETED

All devices running Junos OS.

RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16

6

2

All devices running Junos OS.

risingAlarm

1.3.6.1.2.1.16

6

1

All devices running Junos OS.

Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7

6

1

M, T, MX, J, EX, and SRX Series devices.

bgpBackwardTransition

1.3.6.1.2.1.15.7

6

2

M, T, MX, J, EX, and SRX Series devices.

OSPF TRAP MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2

6

1

M, T, MX, J, EX, and SRX Series devices.

ospfNbrStateChange

1.3.6.1.2.1.14.16.2

6

2

M, T, MX, J, EX, and SRX Series devices.

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2

6

3

M, T, MX, J, EX, and SRX Series devices.

ospfIfConfigError

1.3.6.1.2.1.14.16.2

6

4

M, T, MX, J, EX, and SRX Series devices.

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2

6

5

M, T, MX, J, EX, and SRX Series devices.

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2

6

6

M, T, MX, J, EX, and SRX Series devices.

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2

6

7

M, T, MX, J, EX, and SRX Series devices.

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

8

M, T, MX, J, EX, and SRX Series devices.

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

9

M, T, MX, J, EX, and SRX Series devices.

ospfTxRetransmit

1.3.6.1.2.1.14.16.2

6

10

M, T, MX, J, EX, and SRX Series devices.

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2

6

11

M, T, MX, J, EX, and SRX Series devices.

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2

6

13

M, T, MX, J, EX, and SRX Series devices.

ospfIfStateChange

1.3.6.1.2.1.14.16.2

6

16

M, T, MX, J, EX, and SRX Series devices.

VRRP Notifications

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

vrrpTrapNewMaster

1.3.6.1.2.1.68

6

1

Warning

VRRPD_NEW MASTER_TRAP

All devices running Junos OS.

vrrpTrapAuthFailure

1.3.6.1.2.1.68

6

2

Warning

VRRPD_AUTH_ FAILURE_TRAP

All devices running Junos OS.

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

vrrpv3NewMaster

1.3.6.1.2.1.207

6

1

Warning

VRRPD_NEW_MASTER

M and MX

vrrpv3ProtoError

1.3.6.1.2.1.207

6

2

Warning

VRRPD_V3_PROTO_ERROR

M and MX

Standard SNMP Version 2 Traps

Table 6 provides an overview of the standard SNMPv2 traps supported by the Junos OS. The traps are organized first by trap category and then by trap name and include their snmpTrapOID. The system logging severity levels are listed for those traps that have them with their corresponding system log tag. Traps that do not have corresponding system logging severity levels are marked with an en dash (–) in the table.

Table 6: Standard Supported SNMP Version 2 Traps

Defined in

Trap Name

snmpTrapOID

System Logging Severity Level

Syslog Tag

Supported On

Startup Notifications

RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)

coldStart

1.3.6.1.6.3.1.1.5.1

Critical

SNMPD_TRAP_ COLD_START

All devices running Junos OS.

warmStart

1.3.6.1.6.3.1.1.5.2

Error

SNMPD_TRAP_ WARM_START

All devices running Junos OS.

authenticationFailure

1.3.6.1.6.3.1.1.5.5

Notice

SNMPD_TRAP_ GEN_FAILURE

All devices running Junos OS.

Link Notifications

RFC 2863, The Interfaces Group MIB

linkDown

1.3.6.1.6.3.1.1.5.3

Warning

SNMP_TRAP_ LINK_DOWN

All devices running Junos OS.

linkUp

1.3.6.1.6.3.1.1.5.4

Info

SNMP_TRAP_ LINK_UP

All devices running Junos OS.

Remote Operations Notifications

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

pingProbeFailed

1.3.6.1.2.1.80.0.1

Info

SNMP_TRAP_ PING_PROBE_ FAILED

All devices running Junos OS.

pingTestFailed

1.3.6.1.2.1.80.0.2

Info

SNMP_TRAP_PING_ TEST_FAILED

All devices running Junos OS.

pingTestCompleted

1.3.6.1.2.1.80.0.3

Info

SNMP_TRAP_PING_ TEST_COMPLETED

All devices running Junos OS.

RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16.0.1

All devices running Junos OS.

risingAlarm

1.3.6.1.2.1.16.0.2

All devices running Junos OS.

Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7.1

All devices running Junos OS.

bgpBackwardTransition

1.3.6.1.2.1.15.7.2

All devices running Junos OS.

OSPF Trap MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2.1

All devices running Junos OS.

ospfNbrStateChange

1.3.6.1.2.1.14.16.2.2

All devices running Junos OS.

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2.3

All devices running Junos OS.

ospfIfConfigError

1.3.6.1.2.1.14.16.2.4

All devices running Junos OS.

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2.5

All devices running Junos OS.

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2.6

All devices running Junos OS.

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2.7

All devices running Junos OS.

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2.8

All devices running Junos OS.

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2.9

All devices running Junos OS.

ospfTxRetransmit

1.3.6.1.2.1.14.16.2.10

All devices running Junos OS.

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2.11

All devices running Junos OS.

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2.13

All devices running Junos OS.

ospfIfStateChange

1.3.6.1.2.1.14.16.2.16

All devices running Junos OS.

MPLS Notifications

RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base

mplsTunnelUp

mplsTunnelDown

mplsTunnelRerouted

mplsTunnelReoptimized

Entity State MIB Notifications

RFC 4268, Entity State MIB

entStateOperEnabled

1.3.6.1.2.1.131.0.1

Notice

CHASSISD_SNMP_TRAP3

MX240, MX480, and MX960

entStateOperDisabled

1.3.6.1.2.1.131.0.2

Notice

CHASSISD_SNMP_TRAP3

MX240, MX480, and MX960

L3VPN Notifications

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

mplsL3VpnVrfUp

mplsL3VpnVrfDown

mplsL3VpnVrf RouteMidThresh Exceeded

mplsL3VpnVrf NumVrfRouteMax ThreshExceeded

mplsL3VpnNum VrfRouteMax ThreshCleared

VRRP Notifications

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

vrrpTrapNewMaster

1.3.6.1.2.1.68.0.1

Warning

VRRPD_ NEWMASTER_ TRAP

All devices running Junos OS.

vrrpTrapAuthFailure

1.3.6.1.2.1.68.0.2

Warning

VRRPD_AUTH_ FAILURE_ TRAP

All devices running Junos OS.

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

vrrpv3NewMaster

1.3.6.1.2.1.207.0.1

Warning

VRRPD_NEW_MASTER

M and MX

vrrpv3ProtoError

1.3.6.1.2.1.207.0.2

Warning

VRRPD_V3_PROTO_ERROR

M and MX

Customized SNMP MIBs for Syslog Traps

SNMP syslog traps are alert messages sent from a remote SNMP-enabled device to a central collector notifying you of a component failure or when critical resources are out of configurable limits. This information is captured in a Management Information Base (MIB). The Juniper Networks enterprise-specific System Log MIB enables notification of an SNMP trap-based application when an important system log message occurs. The MIB is defined to map the syslog entry to the generic jnxSyslogTrap OID.

The jnxSyslogTrap OID is a trap based on the logs generated in the syslog. The Event process (eventd) monitors syslog and, based on the event policy raise-trap configuration statement for syslog events, sends all syslog events into one generic syslog-defined trap MIB, which is jnxSyslogTrap.

Using one generic MIB OID is inconvenient for customers who want to process syslog trap OID values to discover specific events because it is impossible to distinguish alarms having the same OID. But as of Junos OS Release 18.3R1, you can map a custom OID to a particular log and load it on the device dynamically.

The benefit of this feature is that because there is a way to assign specific OIDs to different types of syslog events, you can now effectively monitor for each different type of syslog event.

Overview of Custom SNMP MIBs

To create a custom SNMP MIB for a syslog trap, you must complete the following tasks:

  • Write the custom MIB.

  • Convert the MIB file to YANG format and copy the YANG file to the device.

  • Load the YANG file onto the device.

The following sections overview these steps.

Write the MIB File

Before you can map a particular log with a custom OID, you must write a custom MIB. To avoid collisions, you must define your MIB objects and traps only under the reserved roots shown in Table 7.

Table 7: MIB Roots for Custom MIB Modules

Root

Description

OID

.iso.org.dod.internet.private.enterprises.juniperMIB.jnxMibs.jnxCustomMibRoot

Custom MIB module

.1.3.6.1.4.1.2636.3.86

.iso.org.dod.internet.private.enterprises.juniperMIB.jnxTraps.jnxCustomSyslogNotifications

Custom trap notification

.1.3.6.1.4.1.2636.4.30

Convert to a YANG File

Before loading your MIB definition onto the device, you must convert the MIB file to YANG format. The recommended way to covert the MIB file to YANG is to use the smidump v0.5.0 tool. The smidump tool is an open source application which can be installed on your laptop (see https://www.ibr.cs.tu-bs.de/projects/libsmi/smidump.html).

Once the file is in YANG format, you must copy it to the device. Then, using a CLI command, you load the into the SNMP process (snmpd). A corresponding JSON file is then generated, which snmpd parses and from it builds the database of the OID hierarchy. If some unknown tag is found, snmpd returns the appropriate error message.

CLI Commands to Use for Managing YANG Files

To load the YANG module into snmpd, use the snmp option with the request system yang add command:

The yang-filename includes the absolute path.

Note:

In order to run the request system yang add command, you must have super-user access.

There are two other commands for managing YANG files on devices: show system yang package and request system yang delete.

Defining a Custom MIB for a Syslog Trap

In this procedure, we use the following example files:

Note:

Although YANG can be written manually by referring to the example YANG provided in this documentation, we recommend you convert the MIB to YANG format using the smidump tool v0.5.0.

To define a custom MIB for a syslog trap:

  1. Load your MIB onto the network management system (NMS) and check if there are any errors.
  2. Invoke the smidump tool using the following command, where dependency-mib, input-custom-mib-file, and YANG-MODULE-NAME are variables for specific filenames:

    For example:

    As output, you will get the converted YANG file JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang.

    Notice that the input custom MIB file mib-jnx-example-custom-syslog.txt is dependent on SNMPv2-SMI, JUNIPER-SMI, and IF-MIB. But since SNMPv2-SMI and IF-MIB are standard MIBs, their definitions are already present in smidump. So, the only dependent MIB file required is mib-jnx-smi.txt, which has module JUNIPER-SMI definitions.

  3. Copy the file JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang to any path on the device, and copy all the dependent YANG files to the device at the following path: /opt/lib/python2.7/site-packages/pyang/modules.
    Note:

    You must convert all the dependent MIBs to YANG files and copy to these to the device.

    Following are some of the standard MIBs that have been converted to YANG modules and are present in the above path: IANAifType-MIB.yang, ietf-yang-types.yang, ietf-inet-types.yang, IF-MIB.yang, JUNIPER-SMI.yang, SNMPv2-TC.yang.

  4. Using the CLI, load the YANG modules into snmpd using this command:

    For example:

    The YANG module is converted to JSON format and goes to snmpd for parsing and creating the internal database.

  5. To verify the trap based on the syslog with the newly added trap definitions is working, spoof (mimic) the trap. You can do this either using the CLI or an event policy. The following is an example of spoofing the trap using the CLI. See Customized SNMP MIBs for Syslog Traps for an example of using an event policy.

mib-jnx-example-custom-syslog.txt

JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang

Limitations of Using Custom SNMP Traps

Be careful to write the event scripts in such a way that they won’t trigger traps for frequently occurring syslogs. This practice avoids introducing more load on the device.

If you add an object whose access type is readonly or readwrite, that object will not be available for polling in snmp polling operations such as snmpget or snmpwalk; it will be treated as access type notifyonly. This is because this feature is for adding dynamic TRAP OID definitions to the device so that customer can write scripts to send custom traps for each syslog. Access types readonly and readwrite are for snmp polling, whereas notifyonly is for traps.

For custom MIBs, the definition of a custom table is not supported. If you want to send a trap that has a table object as a varbind, use the already defined table in Junos MIBs rather than defining a custom table in your custom MIB.

The YANG file needs to be loaded on all the chassis nodes and Routing Engines separately. The request system yang add command does not automatically copy it to backup Routing Engine.

Example Custom Syslog Trap

This example custom syslog trap illustrates a use case in which the operator wants to receive traps when either of the following occur:

  • A user enters the configuration mode in the CLI (event defined as ui_dbase_login_event)

  • A user does a commit (event defined as ui_commit)

Before the custom syslog trap feature was supported, the only way to do this was to use jnxSyslogTrap, which has a fixed OID, for both events. With the custom syslog trap feature, you can now generate traps that have custom defined OIDs.

To define a custom syslog trap:

  1. Use the sample mib-jnx-example-custom-syslog-txt file provided (see #id-customized-snmp-mibs-for-syslog-traps__d698e103) and convert it to JUNIPER-EXAMPLE-CUSTOM-SYSLOIG-MIB.yang (see #id-customized-snmp-mibs-for-syslog-traps__d698e108).
  2. Copy the YANG file onto your device.
  3. Load the SNMP YANG file.
  4. Copy the slax script (see #id-customized-snmp-mibs-for-syslog-traps__d698e113) to /var/db/scripts/event to spoof the trap .

    For ui_dbase_login_event, you will configure the enteredConfigMode trap which has the username varbind.

    For ui_commit, you will configure the configCommitted trap which has the username command an comment as three varbinds.

  5. Configure the trap:
  6. Enable snmpd traceoptions and trap target to verify the traps that are sent.
  7. Verify trap is working.

Sample MIB file

Sample YANG Converted File

slax Script cutom_trap.slax (in /var/db/scripts/event)

Release History Table
Release
Description
20.1R1
Starting in Junos OS Release 20.1, after graceful routing engine switchover (GRES), the new primary Routing Engine sends a single warmStart notification.