ON THIS PAGE
SNMP MIBs and Traps Supported by Junos OS and Junos OS Evolved
Understand the Integrated Local Management Interface
The Integrated Local Management Interface (ILMI) provides a mechanism for Asynchronous Transfer Mode (ATM)-attached devices, such as hosts, routers, and ATM switches, to transfer management information. ILMI provides a bidirectional exchange of management information between two ATM interfaces across a physical connection. ILMI information is exchanged over a direct encapsulation of SNMP version 1 (RFC 1157, A Simple Network Management Protocol) over ATM Adaptation Layer 5 (AAL5) using a virtual path identifier/virtual channel identifier (VPI/VCI) value (VPI=0, VCI=16).
Junos OS supports only two ILMI MIB variables:
-
atmfMYIPNmAddress -
atmfPortMyIfname
For ATM1 and ATM2 intelligent queuing (IQ) interfaces, you can configure ILMI to communicate directly with an attached ATM switch to enable querying of the switch’s IP address and port number.
For more information about the
ILMI MIB, see atmfMYIPNmAddress or atmfPortMyIfname in the SNMP MIB
Explorer.
See Also
SNMP MIBs Support
The QFX Series standalone switches, QFX Series Virtual Chassis, and QFabric systems support standard MIBs and Juniper Networks enterprise-specific MIBs.
For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer. You can use SNMP MIB Explorer to view information about various MIBs, MIB objects, and SNMP notifications supported on Juniper Networks devices.
For more information, see:
- MIBs Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis
- MIBs Supported on QFabric Systems
MIBs Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis
The QFX Series standalone switches and QFX Series Virtual Chassis support both standard MIBs and Juniper Networks enterprise-specific MIBs. For more information, see:
RFC |
Additional Information |
|---|---|
IEEE 802.1ab section 12.1, Link Layer Discovery Protocol (LLDP) MIB |
Supported tables and objects:
|
IEEE 802.3ad, Aggregation of Multiple Link Segments |
The following tables and objects are supported:
|
RFC 1286, Definitions of Managed Objects for Bridges |
— |
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. |
RFC 2933, Internet Group Management Protocol (IGMP) MIB |
— |
RFC 4318, Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol |
Supports 802.1w and 802.1t extensions for RSTP. Not supported on OCX Series devices. |
RFC 4363b, Q-Bridge VLAN MIB |
Note:
On QFX3500 and QFX3600 switches, the dot1dTpFdbTable table (RFC
4188, Definitions of Managed Objects for Bridges) is populated only with MAC addresses learned on the default VLAN.
To see the MAC addresses of all VLANs, specify the dot1qTpFdbTable
table (in this MIB) when you issue the Not supported on OCX Series devices. |
Internet Assigned Numbers Authority, IANAiftype Textual Convention MIB (referenced by RFC 2233) |
|
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 |
— |
Internet draft draft-ietf-idmr-igmp-mib-13.txt, Internet Group Management Protocol (IGMP) MIB |
— |
ESO Consortium MIB |
Note:
The ESO Consortium MIB has been replaced by RFC 3826. See http://www.snmp.com/eso/. |
MIB |
Description |
|---|---|
Alarm MIB (mib-jnx-chassis-alarm) |
Provides support for alarms from the switch. |
Analyzer MIB (mib-jnx-analyzer) |
Contains analyzer and remote analyzer data related to port mirroring. Not supported on OCX Series devices. |
Chassis MIB (mib-jnx-chassis) |
Provides support for environmental monitoring (power supply state, board voltages, fans, temperatures, and airflow) and inventory support for the chassis, Flexible PIC Concentrators (FPCs), and PICs. Note:
The jnxLEDTable table has been deprecated. |
Chassis Definitions for Router Model MIB (mib-jnx-chas-defines) |
Contains the object identifiers (OIDs) that are used by the Chassis MIB to identify routing and switching platforms 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. |
Class-of-Service MIB (mib-jnx-cos) |
Provides support for monitoring interface output queue statistics per interface and per forwarding class. |
Configuration Management MIB (mib-jnx-cfgmgmt) |
Provides notification for configuration changes and rescue configuration changes in the form of 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. |
Ethernet MAC MIB (mib-jnx-mac) |
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. Not supported on OCX Series devices. |
Event MIB (mib-jnx-event) |
Defines a generic trap that can be generated using an operations 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. In Junos OS release 13.2X51-D10 or later, if you configured an event policy to raise a trap when a new SNMP trap target is added, the SNMPD_TRAP_TARGET_ADD_NOTICE trap is generated with information about the new target. |
Firewall MIB (mib-jnx-firewall) |
Provides support for monitoring firewall filter counters. |
Host Resources MIB (mib-jnx-hostresources) |
Extends the hrStorageTable object, providing a measure of the usage of each file system on the switch as a percentage. 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. |
Interface MIB (Extensions) (mib-jnx-if-extensions) |
Extends the standard ifTable (RFC 2863) with additional statistics and Juniper Networks enterprise-specific chassis information in the ifJnxTable and ifChassisTable tables. |
L2ALD MIB (mib-jnx-l2ald) |
Provides information about Layer 2 Address Learning and related traps, such as the routing instance MAC limit trap and 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 use the VLAN MIB (jnxExVlanTable) for VLAN information instead of this MIB. |
MPLS MIB (mib-jnx-mpls) |
Provides MPLS information and defines MPLS notifications. Note:
This MIB is not supported on the QFX5100 switch. |
MPLS LDP MIB (mib-jnx-mpls-ldp) |
Contains object definitions as described in RFC 3815, Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP). Note:
This MIB is not supported on the QFX5100 switch. |
Ping MIB (mib-jnx-ping) |
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. |
RMON Events and Alarms MIB (mib-jnx-rmon) |
Supports Junos OS extensions to the standard Remote Monitoring (RMON) Events and Alarms MIB (RFC 2819). The extension augments the alarmTable object with additional information about each alarm. Two additional traps are also defined to indicate when problems are encountered with an alarm. |
Structure of Management Information MIB (mib-jnx-smi) |
Explains how the Juniper Networks enterprise-specific MIBs are structured. |
System Log MIB (mib-jnx-syslog) |
Enables notification of an SNMP trap-based application when an important system log message occurs. |
Utility MIB (mib-jnx-util) |
Provides you with SNMP MIB container objects of the following types: 32-bit counters, 64-bit counters, signed integers, unsigned integers, and octet strings. You can use these objects to store data that can be retrieved using other SNMP operations. |
VLAN MIB (mib-jnx-vlan) |
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 available in the L2ALD MIB in the jnxL2aldVlanTable table instead of in the VLAN MIB For non-ELS EX Series switches, VLAN information is provided in the VLAN MIB in the jnxExVlanTable table. Not supported on OCX Series devices. |
MIBs Supported on QFabric Systems
The QFabric systems support both standard MIBs and Juniper Networks enterprise-specific MIBs. For more information, see:
RFC |
Additional Information |
|---|---|
RFC 1286, Definitions of Managed Objects for Bridges |
— |
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. |
RFC 2933, Internet Group Management Protocol (IGMP) MIB |
— |
RFC 4363b, Q-Bridge VLAN MIB |
The QFabric system supports the following tables only:
Not supported on OCX Series devices. |
QFabric-specific MIBs are not supported on OCX Series devices.
MIB |
Description |
|---|---|
Analyzer MIB (mib-jnx-analyzer) |
Contains analyzer and remote analyzer data related to port mirroring. The QFabric system supports:
|
Chassis MIB (mib-jnx-chassis) |
Note:
The Chassis MIB has been deprecated for the QFabric system. We recommend that you use the Fabric Chassis MIB (mib-jnx-fabric-chassis) for information about the QFabric system. |
Class-of-Service MIB (mib-jnx-cos) |
Provides support for monitoring interface output queue statistics per interface and per forwarding class. The QFabric system supports the following tables and objects:
The QFabric system does not support any traps for this MIB. |
Configuration Management MIB (mib-jnx-cfgmgmt) |
Provides notification for configuration changes and rescue configuration changes in the form of 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. Note:
On the QFabric system, these conditions apply:
|
Fabric Chassis MIB (mib-jnx-fabric-chassis) |
Provides hardware information about the QFabric system and its component devices. This MIB is based on the Juniper Networks enterprise-specific Chassis MIB but adds another level of indexing that provides information for QFabric system component devices. |
Interface MIB (Extensions) (mib-jnx-if-extensions) |
Extends the standard ifTable (RFC 2863) with additional statistics and Juniper Networks enterprise-specific chassis information in the ifJnxTable and ifChassisTable tables. Note:
On the QFabric system, scalar variables are not supported. |
Power Supply Unit MIB (mib-jnx-power-supply-unit) |
Provides support for environmental monitoring of the power supply unit for the Interconnect device of the QFabric system. Note:
On the QFabric system, scalar variables for the jnxPsuObjects 1 object ID in the jnxPsuScalars table are not supported. |
QFabric MIB (jnx-qf-smi) |
Explains how the Juniper Networks enterprise-specific QFabric MIBs are structured. Defines the MIB objects that are reported by the QFabric system and the contents of the traps that can be issued by the QFabric system. |
Utility MIB (mib-jnx-util) |
Provides you with SNMP MIB container objects of the following types: 32-bit counters, 64-bit counters, signed integers, unsigned integers, and octet strings. You can use these objects to store data that can be retrieved using other SNMP operations. |
See Also
MIB Objects for the QFX Series
This topic lists the Juniper Networks enterprise-specific SNMP Chassis MIB definition objects for the QFX Series:
- QFX Series Standalone Switches
- QFabric Systems
- QFabric System QFX3100 Director Device
- QFabric System QFX3008-I Interconnect Device
- QFabric System QFX3600-I Interconnect Device
- QFabric System Node Devices
QFX Series Standalone Switches
jnxProductLineQFXSwitch OBJECT IDENTIFIER ::= { jnxProductLine 82 }
jnxProductNameQFXSwitch OBJECT IDENTIFIER ::= { jnxProductName 82 }
jnxProductModelQFXSwitch OBJECT IDENTIFIER ::= { jnxProductModel 82 }
jnxProductVariationQFXSwitch OBJECT IDENTIFIER ::= { jnxProductVariation 82 }
jnxProductQFX3500s OBJECT IDENTIFIER ::= { jnxProductVariationQFXSwitch 1 }
jnxProductQFX360016QS OBJECT IDENTIFIER ::= { jnxProductVariationQFXSwitch 2 }
jnxProductQFX350048T4QS OBJECT IDENTIFIER ::= { jnxProductVariationQFXSwitch 3 }
jnxProductQFX510024Q OBJECT IDENTIFIER ::= { jnxProductVariationQFXSwitch 4 }
jnxProductQFX510048S6Q OBJECT IDENTIFIER ::= { jnxProductVariationQFXSwitch 5 }
jnxChassisQFXSwitch OBJECT IDENTIFIER ::= { jnxChassis 82 }
jnxSlotQFXSwitch OBJECT IDENTIFIER ::= { jnxSlot 82 }
jnxQFXSwitchSlotFPC OBJECT IDENTIFIER ::= { jnxSlotQFXSwitch 1 }
jnxQFXSwitchSlotHM OBJECT IDENTIFIER ::= { jnxSlotQFXSwitch 2 }
jnxQFXSwitchSlotPower OBJECT IDENTIFIER ::= { jnxSlotQFXSwitch 3 }
jnxQFXSwitchSlotFan OBJECT IDENTIFIER ::= { jnxSlotQFXSwitch 4 }
jnxQFXSwitchSlotFPB OBJECT IDENTIFIER ::= { jnxSlotQFXSwitch 5 }
jnxMediaCardSpaceQFXSwitch OBJECT IDENTIFIER ::= { jnxMediaCardSpace 82 }
jnxQFXSwitchMediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceQFXSwitch 1 }
QFabric Systems
jnxProductLineQFX3000 OBJECT IDENTIFIER ::= { jnxProductLine 84 }
jnxProductNameQFX3000 OBJECT IDENTIFIER ::= { jnxProductName 84 }
jnxProductModelQFX3000 OBJECT IDENTIFIER ::= { jnxProductModel 84 }
jnxProductVariationQFX3000 OBJECT IDENTIFIER ::= { jnxProductVariation 84 }
jnxProductQFX3000-G OBJECT IDENTIFIER ::= { jnxProductVariationQFX3000 1 }
jnxProductQFX3000-M OBJECT IDENTIFIER ::= { jnxProductVariationQFX3000 2 }
jnxChassisQFX3000 OBJECT IDENTIFIER ::= { jnxChassis 84 }
QFabric System QFX3100 Director Device
jnxProductLineQFX3100 OBJECT IDENTIFIER ::= { jnxProductLine 100 }
jnxProductNameQFX3100 OBJECT IDENTIFIER ::= { jnxProductName 100 }
jnxProductModelQFX3100 OBJECT IDENTIFIER ::= { jnxProductModel 100 }
jnxProductVariationQFX3100 OBJECT IDENTIFIER ::= { jnxProductVariation 100 }
jnxChassisQFX3100 OBJECT IDENTIFIER ::= { jnxChassis 100 }
jnxSlotQFX3100 OBJECT IDENTIFIER ::= { jnxSlot 100 }
jnxQFX3100SlotCPU OBJECT IDENTIFIER ::= { jnxSlotQFX3100 1 }
jnxQFX3100SlotMemory OBJECT IDENTIFIER ::= { jnxSlotQFX3100 2 }
jnxQFX3100SlotPower OBJECT IDENTIFIER ::= { jnxSlotQFX3100 3 }
jnxQFX3100SlotFan OBJECT IDENTIFIER ::= { jnxSlotQFX3100 4 }
jnxQFX3100SlotHardDisk OBJECT IDENTIFIER ::= { jnxSlotQFX3100 5 }
jnxQFX3100SlotNIC OBJECT IDENTIFIER ::= { jnxSlotQFX3100 6 }
QFabric System QFX3008-I Interconnect Device
jnxProductLineQFXInterconnect OBJECT IDENTIFIER ::= { jnxProductLine 60 }
jnxProductNameQFXInterconnect OBJECT IDENTIFIER ::= { jnxProductName 60 }
jnxProductModelQFXInterconnect OBJECT IDENTIFIER ::= { jnxProductModel 60 }
jnxProductVariationQFXInterconnect OBJECT IDENTIFIER ::= { jnxProductVariation 60 }
jnxProductQFX3008 OBJECT IDENTIFIER ::= { jnxProductVariationQFXInterconnect 1 } jnxProductQFXC083008 OBJECT IDENTIFIER ::= { jnxProductVariationQFXInterconnect 2 }
jnxProductQFX3008I OBJECT IDENTIFIER ::= { jnxProductVariationQFXInterconnect 3 }
jnxChassisQFXInterconnect OBJECT IDENTIFIER ::= { jnxChassis 60 }
jnxSlotQFXInterconnect OBJECT IDENTIFIER ::= { jnxSlot 60 }
jnxQFXInterconnectSlotFPC OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 1 }
jnxQFXInterconnectSlotHM OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 2 }
jnxQFXInterconnectSlotPower OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 3 }
jnxQFXInterconnectSlotFan OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 4 }
jnxQFXInterconnectSlotCBD OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 5 }
jnxQFXInterconnectSlotFPB OBJECT IDENTIFIER ::= { jnxSlotQFXInterconnect 6 }
jnxMediaCardSpaceQFXInterconnect OBJECT IDENTIFIER ::= { jnxMediaCardSpace 60 }
jnxQFXInterconnectMediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceQFXInterconnect 1 }
jnxMidplaneQFXInterconnect OBJECT IDENTIFIER ::= { jnxBackplane 60 }
QFabric System QFX3600-I Interconnect Device
jnxProductLineQFXMInterconnect OBJECT IDENTIFIER ::= { jnxProductLine 91 }
jnxProductNameQFXMInterconnect OBJECT IDENTIFIER ::= { jnxProductName 91 }
jnxProductModelQFXMInterconnect OBJECT IDENTIFIER ::= { jnxProductModel 91 }
jnxProductVariationQFXMInterconnect OBJECT IDENTIFIER ::= { jnxProductVariation 91 }
jnxProductQFX3600I OBJECT IDENTIFIER ::= { jnxProductVariationQFXMInterconnect 1 }
jnxChassisQFXMInterconnect OBJECT IDENTIFIER ::= { jnxChassis 91 }
jnxSlotQFXMInterconnect OBJECT IDENTIFIER ::= { jnxSlot 91 }
jnxQFXMInterconnectSlotFPC OBJECT IDENTIFIER ::= { jnxSlotQFXMInterconnect 1 }
jnxQFXMInterconnectSlotHM OBJECT IDENTIFIER ::= { jnxSlotQFXMInterconnect 2 }
jnxQFXMInterconnectSlotPower OBJECT IDENTIFIER ::= { jnxSlotQFXMInterconnect 3 }
jnxQFXMInterconnectSlotFan OBJECT IDENTIFIER ::= { jnxSlotQFXMInterconnect 4 }
jnxQFXMInterconnectSlotFPB OBJECT IDENTIFIER ::= { jnxSlotQFXMInterconnect 5 }
jnxMediaCardSpaceQFXMInterconnect OBJECT IDENTIFIER ::= { jnxMediaCardSpace 91 }
jnxQFXMInterconnectMediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceQFXMInterconnect 1 }
QFabric System Node Devices
jnxProductLineQFXNode OBJECT IDENTIFIER ::= { jnxProductLine 61 }
jnxProductNameQFXNode OBJECT IDENTIFIER ::= { jnxProductName 61 }
jnxProductModelQFXNode OBJECT IDENTIFIER ::= { jnxProductModel 61 }
jnxProductVariationQFXNode OBJECT IDENTIFIER ::= { jnxProductVariation 61 }
jnxProductQFX3500 OBJECT IDENTIFIER ::= { jnxProductVariationQFXNode 1 }
jnxProductQFX360016Q OBJECT IDENTIFIER ::= { jnxProductVariationQFXNode 3 }
jnxChassisQFXNode OBJECT IDENTIFIER ::= { jnxChassis 61 }
jnxSlotQFXNode OBJECT IDENTIFIER ::= { jnxSlot 61 }
jnxQFXNodeSlotFPC OBJECT IDENTIFIER ::= { jnxSlotQFXNode 1 }
jnxQFXNodeSlotHM OBJECT IDENTIFIER ::= { jnxSlotQFXNode 2 }
jnxQFXNodeSlotPower OBJECT IDENTIFIER ::= { jnxSlotQFXNode 3 }
jnxQFXNodeSlotFan OBJECT IDENTIFIER ::= { jnxSlotQFXNode 4 }
jnxQFXNodeSlotFPB OBJECT IDENTIFIER ::= { jnxSlotQFXNode 5 }
jnxMediaCardSpaceQFXNode OBJECT IDENTIFIER ::= { jnxMediaCardSpace 61 }
jnxQFXNodeMediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceQFXNode 1 }
See Also
Fabric Chassis MIB
The Juniper Networks enterprise-specific SNMP Fabric Chassis MIB (mib-jnx-fabric-chassis) provides hardware information about the QFabric system and its component devices in a single MIB. The Fabric Chassis MIB is based on the Juniper Networks enterprise-specific Chassis MIB that provides information for individual devices. Unlike the Chassis MIB, the Fabric Chassis MIB represents the QFabric system component devices as part of the QFabric system. Only the information from the Fabric Chassis MIB (and not from individual Chassis MIBs) is available to SNMP management clients of the QFabric system.
The Fabric Chassis MIB uses the basic information structure of the Chassis MIB, but adds another level of indexing that provides detailed information about QFabric system devices. Each physical device in a QFabric system (such as a Node device or an Interconnect device) is represented with its hardware components, including the power supply, fans, and front and rear cards.
As in other SNMP systems, the SNMP manager resides on the network management system (NMS) of the network to which the QFabric system belongs. The SNMP agent (snmpd) resides in the QFabric system Director software and is responsible for receiving and distributing all traps as well as responding to all queries from the SNMP manager.
In addition, there is an SNMP subagent running in the Routing Engine of each Node group and Interconnect device. The SNMP subagent manages the information about the component device, and that information is communicated to the SNMP agent in the Director software as needed. Traps that are generated by a Node device are sent to the SNMP agent in the Director software, which in turn processes and sends them to the target IP addresses that are defined in the SNMP configuration.
Table 5 describes the tables and objects in the Fabric Chassis MIB.
Table or Object Name |
Root OID |
Description |
|---|---|---|
| Tables with Counterparts in the Chassis MIB | ||
jnxFabricContainersTable |
1.3.6.1.4.1.2636.3.42.2.2.2 |
Provides information about different types of containers in QFabric system devices.
|
jnxFabricContentsTable |
1.3.6.1.4.1.2636.3.42.2.2.3 |
Contains contents that are present across all devices represented in the jnxFabricDeviceTable object. This table includes all field replaceable units (FRUs) and non-FRUs for QFabric system devices.
|
jnxFabricFilledTable |
1.3.6.1.4.1.2636.3.42.2.2.4 |
Shows the status of containers in QFabric devices. The jnxFabricFilledState object represents the state of the component: (1) unknown, (2) empty, or (3) filled. Note:
The jnxFabricFilledTable object does not contain information about the Director group. |
jnxFabricOperatingTable |
1.3.6.1.4.1.2636.3.42.2.2.5 |
Represents different operating parameters for the contents that are populated in the jnxFabricContentsTable object.
The jnxFabricOperatingState object provides the state of the device: (1) unknown, (2) running, (3) ready, (4) reset, (5) runningAtFullSpeed (for fans only), (6) down, (6) off (for power supply units), or (7) standby. |
jnxFabricRedundancyTable |
1.3.6.1.4.1.2636.3.42.2.2.6 |
Represents the redundancy information that is available at different subsystem levels across the QFabric system. Information about the Routing Engines in Node devices is included, but there are no corresponding entries for Interconnect devices in this table. The jnxFabricRedundancyState object indicates the state of the subsystem: (1) unknown, (2) primary, (3) backup, or (4) disabled. Note:
Information about redundant Director devices, virtual machines (VMs) within Director groups, and Virtual Chassis devices is not available at this time. |
jnxFabricFruTable |
1.3.6.1.4.1.2636.3.42.2.2.7 |
Contains all FRUs for the QFabric system in the jnxFabricDeviceTable table. The FRUs are listed regardless of whether or not they are installed or online. The jnxFabricFruState object represents the state of the FRU, including online, offline, or empty, and so on. This table also contains information about each FRU, such as name, type, temperature, time last powered on, and time last powered off. Note:
The jnxFabricFruTable table does not include network interface cards (NICs) on Director devices. |
| Table Specific to the Fabric Chassis MIB | ||
jnxFabricDeviceTable |
1.3.6.1.4.1.2636.3.42.2.2.1 |
Contains information about all devices in the QFabric system. This table organizes scalar variables represented in the Chassis MIB into a table format for the QFabric system component devices. Columns in this table include device information such as model, device alias, and serial number. The jnxFabricDeviceIndex identifies each QFabric system device (Node device, Interconnect device, and Director device). Note:
At this time, information about the Virtual Chassis is not available. Note:
The following objects are not supported:
|
| Scalar Variables | ||
The following scalar variables are supported:
|
1.3.6.1.4.1.2636.3.42.2.1 |
Describe the QFabric system as a whole. Note:
The jnxFabricFirmwareRevision scalar variable is not supported at this time. |
Table 6 describes the SNMPv2 traps that are defined in the Fabric Chassis MIB.
Only SNMPv2 traps are supported on the QFabric system.
Trap Group and Name |
Root OID |
Description |
|---|---|---|
jnxFabricChassisTraps group—Includes the following traps:
|
1.3.6.1.4.1.2636.4.19 |
Indicates an alarm condition. Note:
Hardware events on the Director group are detected by scanning. As a result, a trap may not be generated until up to 30 seconds after the event has occurred. Note:
The software does not distinguish between the fan removal and fan failure events on the Director group. In each case, both the jnxFabricFanFailure and jnxFabricFruFailed traps are generated. |
jnxFabricChassisOKTraps group—Includes the following traps:
|
1.3.6.1.4.1.2636.4.20 |
Indicates an alarm cleared condition. |
See Also
Utility MIB
The Juniper Networks enterprise-specific Utility MIB, whose object ID is {jnxUtilMibRoot 1}, defines objects for counters, integers, and strings. The Utility MIB contains one table for each of the following five data types:
32-bit counters
64-bit counters
Signed integers
Unsigned integers
Octet strings
You can use these containers MIB objects to store the data that are not supported for SNMP operations. You can populate data for these objects either by using CLI commands or with the help of Op scripts and an RPC API that can invoke the CLI commands.
Each data type has an arbitrary ASCII name, which is defined when the data is populated, and a timestamp that shows the last time when the data instance was modified. For a downloadable version of this MIB, see Routing Policies, Firewall Filters, and Traffic Policers User Guide.
For information about the enterprise-specific Utility MIB objects, see the following topics:
Using the Enterprise-Specific Utility MIB to Enhance SNMP Coverage
Even though the Junos OS has built-in performance metrics and monitoring options, you might need to have customized performance metrics. To make it easier for you to monitor such customized data through a standard monitoring system, the Junos OS provides you with an enterprise-specific Utility MIB that can store such data and thus extend SNMP support for managing and monitoring the data of your choice.
The following CLI commands enable you to set and clear Utility MIB object values:
-
request snmp utility-mib set instance name object-type <counter | counter 64 | integer | string | unsigned integer> object-value value -
request snmp utility-mib clear instance name object-type <counter | counter 64 | integer | string | unsigned integer>
The instance name option of the request
snmp utility-mib <set | clear> command specifies the name of the
data instance and is the main identifier of the data. The object-type
<counter | counter 64 | integer | string | unsigned integer>
option enables you to specify the object type, and the object-value
value option enables you to set the value of the
object.
To automate the process of populating Utility MIB data, you can use a combination of
an event policy and event script. The following examples show the configuration for
an event policy to run show system buffers every hour and to store
the show system buffers data in Utility MIB objects by running an
event script (check-mbufs.slax).
Event Policy Configuration
To configure an event policy that runs the show system buffers
command every hour and invokes check-mbufs.slax to store the
show system buffers data into Utility MIB objects, include the
following statements at the [edit] hierarchy level:
event-options {
generate-event {
1-HOUR time-interval 3600;
}
policy MBUFS {
events 1-HOUR;
then {
event-script check-mbufs.slax; # script stored at /var/db/scripts/event/
}
}
event-script {
file check-mbufs.slax;
}
}
check-mbufs.slax Script
The following example shows the check-mbufs.slax script that is
stored under /var/db/scripts/event/:
------ script START ------
version 1.0;
ns junos = "http://xml.juniper.net/junos/*/junos";
ns xnm = "http://xml.juniper.net/xnm/1.1/xnm";
ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0";
ns ext = "http://xmlsoft.org/XSLT/namespace";
match / {
<op-script-results>{
var $result = jcs:invoke("get-buffer-informations");
var $rpc = <request-snmp-utility-mib-set> {
<object-type> "integer";
<instance> "current-mbufs";
<object-value> $result/current-mbufs;
}
var $res = jcs:invoke($rpc);
expr jcs:syslog("external.info", $res/..//snmp-utility-mib-results/snmp-utility-mib-result);
}
}
------ script END ------
You can run the following command to check the data stored in the Utility MIB as a result of the event policy and script shown in the preceding examples:
user@host> show snmp mib walk jnxUtilData ascii jnxUtilIntegerValue."current-mbufs" = 0 jnxUtilIntegerTime."current-mbufs" = 07 da 05 0c 03 14 2c 00 2d 07 00 user@caramels>
The show snmp mib walk command is not available on the QFabric
system, but you can use external SNMP client applications to perform this
operation.
See Also
Enterprise-Specific SNMP MIBs Supported by Junos OS
Junos OS supports the enterprise-specific MIBs listed in Table 7. For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer.
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 Virtual Firewall |
|
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. |
SRX Series and vSRX Virtual Firewall |
|
Alarm MIB |
Provides information about alarms from the router chassis. |
All platforms except MX10003 and MX204 devices. |
|
Analyzer MIB |
Provides information about analyzer and remote analyzer related to port mirroring on the EX Series Ethernet Switches. |
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 Virtual Firewall |
|
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 Virtual Firewall |
|
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 Virtual Firewall |
|
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 |
ACX Series, EX Series, M Series, MX Series, PTX Series, QFabric system, QFX Series, SRX Series, T Series, and vSRX Virtual Firewall |
|
CGNAT MIB |
Provides information about services interfaces used for CGNAT implementation.
|
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. History of the last 32 configuration changes is
kept in |
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 Virtual Firewall |
|
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 Virtual Firewall |
|
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, |
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 Virtual Firewall instances |
|
Host Resources MIB |
Extends the |
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 Virtual Firewall |
|
Interface MIB |
Extends the standard |
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 |
SRX Series and vSRX Virtual Firewall |
|
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 |
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 Virtual Firewall |
|
jnxASICExternalMemTraps |
Provides information on ASIC external memory error. | QFX10002-36Q, QFX10002-60C, QFX10002-72Q, QFX10008, QFX10016, PTX1000, PTX10002-60C, PTX10008, PTX10016 |
| jnxASICExternalMemOKTraps | Provides information on ASIC external memory error. | QFX10002-36Q, QFX10002-60C, QFX10002-72Q, QFX10008, QFX10016, PTX1000, PTX10002-60C, PTX10008, PTX10016 |
| jnxHmcFatal | Provides information when the specified HMC on a specific FPC has failed. | QFX10002-36Q, QFX10002-60C, QFX10002-72Q, QFX10008, QFX10016, PTX1000, PTX10002-60C, PTX10008, PTX10016 |
| jnxHmcOK | Provides information when the specified HMC on a specific FPC has recovered from the failure. | QFX10002-36Q, QFX10002-60C, QFX10002-72Q, QFX10008, QFX10016, PTX1000, PTX10002-60C, PTX10008, PTX10016 |
|
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 Virtual Firewall |
|
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 process (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 Note:
Non-ELS EX Series switches support the VLAN MIB ( |
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 |
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, expired, 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
|
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) | Provides the following details of configured logical systems and
tenant:
|
SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800, and vSRX Virtual Firewall |
|
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 are supported in earlier releases of Junos OS as a
proprietary LDP MIB ( |
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 ( |
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 |
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 |
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 ( |
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 Virtual Firewall |
|
Security Screening Objects MIB |
Defines the MIB for the Juniper Networks Enterprise Firewall screen functionality. |
SRX Series and vSRX Virtual Firewall |
|
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 Virtual Firewall |
|
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 Virtual Firewall |
|
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 Virtual Firewall |
|
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 Firewalls, services, and traps. |
SRX Series and vSRX Virtual Firewall |
|
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 |
|
Timing MIB |
Defines Synchronous Ethernet (SyncE) and Precision Time Protocol (PTP) objects, faults, and events. |
ACX710 |
|
Traceroute MIB |
Supports the Junos OS extensions of traceroute and remote operations. Items in this MIB
are created when entries are created in the |
EX Series, M Series, MX Series, SRX Series, T Series, and vSRX Virtual Firewall |
|
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 Firewall |
|
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 Non-ELS EX Series Ethernet switches use the |
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
|
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 Virtual Firewall |
|
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
Starting in Junos OS Release 19.4R1, on SRX5000 line 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.
Starting in Junos OS Release 20.4R1, you can monitor CPU and Kernel usage on Routing Engine using reswatch process.
See Also
Standard SNMP MIBs Supported by Junos OS
Junos OS supports the Standard MIBs listed in Table 8.
For details on SNMP MIB support on EX4600 switches, QFX Series switches, and QFabric systems, see SNMP MIBs Support.
Standard MIB |
Supported and unsupported tables and objects |
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:
|
EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, and vSRX |
IEEE, 802.1ag, Connectivity Fault Management |
Supported tables and objects:
|
EX Series, MX Series, PTX Series, and QFX Series |
IEEE, 802.1ap, Management Information Base (MIB) definitions for VLAN Bridges |
Supported tables and objects:
|
MX 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 2922, The Physical Topology (PTOPO) MIB |
Supported objects:
|
EX Series and SRX Series |
RFC 3591 Managed Objects for the Optical Interface Type |
Supported tables and objects:
|
M Series, MX Series, PTX Series, and T Series |
RFC 3621, Power Ethernet MIB |
No exceptions |
EX Series |
RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer |
Unsupported tables and objects:
|
M Series, MX Series, PTX Series, and T Series |
RFC 3877, Alarm Management Information Base |
|
MX Series |
RFC 3896, Definitions of Managed Objects for the DS3/E3 Interface Type |
Unsupported tables and objects:
|
M Series and T 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 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:
|
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:
|
M Series, MX Series, and T Series |
RFC 5132, IP Multicast MIB Note:
This RFC obsoletes RFC2932. |
Unsupported table:
|
All platforms |
RFC 5643, Management Information Base for OSPFv3 (read-only access) |
Unsupported tables and objects:
|
M Series, MX Series, PTX Series, SRX Series, and T 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
|
MX Series and PTX Series |
For
|
||
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 [ |
M Series, MX Series, and T Series |
Internet draft draft-ieft-bfd-mib-02.txt, Bidirectional Forwarding Detection Management Information Base |
(Represented by |
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:
|
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 [ |
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:
|
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 |
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:
|
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:
|
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.
For information about RFCs, see the Standards Reference Guide.
Enterprise-Specific MIBs for Junos OS Evolved
Starting in Junos OS Evolved Release 19.1R1, the enterprise-specific MIBs listed in Table 9 are supported. For information about enterprise-specific SNMP MIB objects, see the SNMP MIB Explorer.
|
Enterprise-Specific MIB |
Description |
Supported and unsupported tables and objects |
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 and PTX10001-36MR |
|
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:
Supported tables and objects:
|
PTX10003 and PTX10001-36MR |
|
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
|
No exceptions |
PTX Series and QFX Series |
| Destination class usage (DCU) MIB | Provides support for monitoring SCU and DCU counters. | No exceptions | PTX10001-36MR, PTX10004, PTX10008, and PTX10016 |
| DHCP |
Provides SNMP support (get only) for DHCP stateless relay configurations. Stateless relay does not include support for bindings and leases tables. Supported tables and objects:
|
Support does not include the following MIB
objects:
|
PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130, QFX5220 |
| DHCPv6 |
Provides SNMP support (get only) for DHCPv6 stateless relay configurations. Stateless relay does not include support for bindings and leases tables. Supported tables and objects:
|
Support does not include the following MIB
object:
|
PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130, QFX5220 |
| Firewall MIB | Provides bytes and packets count of interface attached policers. |
Supported tables and objects:
The values of the following objects in jnxFWCntrPolicerOutSpecPktCount and jnxFWCntrPolicerOutSpecByteCount are supported, whereas the rest of the MIBs are not supported and will always be zero. |
PTX10001-36MR, PTX10003, PTX10004, and PTX10008 |
|
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:
|
PTX10003 |
|
Interface MIB |
Extends the standard ifTable (RFC 2863) with additional statistics
and Juniper Networks enterprise-specific chassis information in the
|
No exceptions |
PTX10003 and QFX5220 |
|
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
|
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:
|
PTX10003 |
|
SNMP USM HMAC-SHA-2 MIB |
Contains Juniper Networks' implementation of enterprise specific MIB for SNMP USM HMAC-SHA-2. |
Supported Objects:
|
ACX7100 - 32C, ACX7100 - 48L, ACX7509, ACX7900, ACX7024, PTX1000136MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130 - 32CD, QFX5130 - 48C, QFX5130 - 48CM, QFX5700, QFX5220, QFX5230 - 64CD |
| Source class usage (SCU) MIB | Provides support for monitoring SCU and DCU counters. |
No exceptions |
PTX10001-36MR, PTX10004, PTX10008, and PTX10016 |
| TWAMP MIB (jnxTwampMib) | Monitors network performance using Two-Way Active Measurement Protocol. |
Supported tables:
Supported traps:
|
PTX10001-36MR, PTX10003, PTX10004, and PTX10008 |
| Timing MlB (jnxTimingNotfnsMIB) | Defines Synchronous Ethernet (SyncE) objects, faults, and events. | Supported traps:
|
PTX10008 |
|
VPN MIB |
Provides monitoring for Layer 3 VPNs, Layer 2 VPNs, and virtual private LAN service (VPLS). |
Unsupported objects
|
PTX10003 |
See Also
Standard MIBs for Junos OS Evolved
Table 10 shows the Standard MIBs supported in Junos OS Evolved. For information about Standard MIB objects, see the SNMP MIB Explorer.
|
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:
|
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:
|
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:
|
PTX10003 |
|
RFC 2790, Host Resources MIB |
Unsupported tables and objects:
|
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):
|
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 4087, IP Tunnel MIB |
Describes MIB objects in the following tables for managing tunnels of any type over IPv4 and IPv6 networks:
|
PTX Series (PTX10008, PTX10001-36MR, PTX10001, and PTX10004) |
|
RFC 4133, Entity MIB |
Supported table:
|
PTX10003 |
|
RFC 4292, IP Forwarding MIB |
No exceptions |
PTX10003 |
|
RFC 4293, Management Information Base for the Internet Protocol (IP) |
Supported tables:
Unsupported objects:
|
PTX10003 |
|
RFC 4293, Management Information Base for the Internet Protocol (IP) |
Supported tables:
|
ACX7100-32C, PTX10008, and QFX10008 |
|
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:
Unsupported objects for PTX10008 on Junos OS Evolved Release 20.1R1:
|
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 |
See Also
SNMP Traps Support
The QFX Series standalone switches, QFX Series Virtual Chassis, and QFabric systems support standard SNMP traps and Juniper Networks enterprise-specific traps.
For more information, see:
- SNMP Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis
- SNMP Traps Supported on QFabric Systems
SNMP Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis
QFX Series standalone switches and QFX Series Virtual Chassis support SNMPv1 and v2 traps. For more information, see:
SNMPv1 Traps
QFX Series standalone switches and QFX Series Virtual Chassis support both standard SNMPv1 traps and Juniper Networks enterprise-specific SNMPv1 traps. See:
The traps are organized first by trap category and then by trap name. The system logging severity levels are listed for those traps that have them. Traps that do not have corresponding system logging severity levels are marked with an en dash (–).
Defined in |
Trap Name |
Enterprise ID |
Generic Trap Number |
Specific Trap Number |
System Logging Severity Level |
Syslog Tag |
|---|---|---|---|---|---|---|
| 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 |
linkUp |
1.3.6.1.4.1.2636 |
3 |
0 |
Info |
SNMP_TRAP_ LINK_UP |
|
| 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 |
pingTestFailed |
1.3.6.1.2.1.80.0 |
6 |
2 |
Info |
SNMP_TRAP_ PING_TEST _FAILED |
|
pingTestCompleted |
1.3.6.1.2.1.80.0 |
6 |
3 |
Info |
SNMP_TRAP_ PING_TEST_ COMPLETED |
|
traceRoutePathChange |
1.3.6.1.2.1.81.0 |
6 |
1 |
Info |
SNMP_TRAP_ TRACE_ROUTE_ PATH_CHANGE |
|
traceRouteTestFailed |
1.3.6.1.2.1.81.0 |
6 |
2 |
Info |
SNMP_TRAP_ TRACE_ROUTE_ TEST_FAILED |
|
traceRouteTestCompleted |
1.3.6.1.2.1.81.0 |
6 |
3 |
Info |
SNMP_TRAP_ TRACE_ROUTE_ TEST_COMPLETED |
|
| RMON Alarms | ||||||
RFC 2819a, RMON MIB |
fallingAlarm |
1.3.6.1.2.1.16 |
6 |
2 |
– |
– |
risingAlarm |
1.3.6.1.2.1.16 |
6 |
1 |
– |
– |
|
| Routing Notifications | ||||||
BGP 4 MIB |
bgpEstablished |
1.3.6.1.2.1.15.7 |
6 |
1 |
– |
– |
bgpBackwardTransition |
1.3.6.1.2.1.15.7 |
6 |
2 |
– |
– |
|
OSPF TRAP MIB |
ospfVirtIfStateChange |
1.3.6.1.2.1.14.16.2 |
6 |
1 |
– |
– |
ospfNbrStateChange |
1.3.6.1.2.1.14.16.2 |
6 |
2 |
– |
– |
|
ospfVirtNbrStateChange |
1.3.6.1.2.1.14.16.2 |
6 |
3 |
– |
– |
|
ospfIfConfigError |
1.3.6.1.2.1.14.16.2 |
6 |
4 |
– |
– |
|
ospfVirtIfConfigError |
1.3.6.1.2.1.14.16.2 |
6 |
5 |
– |
– |
|
ospfIfAuthFailure |
1.3.6.1.2.1.14.16.2 |
6 |
6 |
– |
– |
|
ospfVirtIfAuthFailure |
1.3.6.1.2.1.14.16.2 |
6 |
7 |
– |
– |
|
ospfIfRxBadPacket |
1.3.6.1.2.1.14.16.2 |
6 |
8 |
– |
– |
|
ospfVirtIfRxBadPacket |
1.3.6.1.2.1.14.16.2 |
6 |
9 |
– |
– |
|
ospfTxRetransmit |
1.3.6.1.2.1.14.16.2 |
6 |
10 |
– |
– |
|
ospfVirtIfTxRetransmit |
1.3.6.1.2.1.14.16.2 |
6 |
11 |
– |
– |
|
ospfMaxAgeLsa |
1.3.6.1.2.1.14.16.2 |
6 |
13 |
– |
– |
|
ospfIfStateChange |
1.3.6.1.2.1.14.16.2 |
6 |
16 |
– |
– |
|
| 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 |
coldStart |
1.3.6.1.4.1.2636 |
0 |
0 |
Critical |
SNMPD_TRAP_ COLD_START |
|
warmStart |
1.3.6.1.4.1.2636 |
1 |
0 |
Error |
SNMPD_TRAP_ WARM_START |
|
| 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 |
vrrpTrapAuthFailure |
1.3.6.1.2.1.68 |
6 |
2 |
Warning |
VRRPD_AUTH_ FAILURE_TRAP |
|
Defined in |
Trap Name |
Enterprise ID |
Generic Trap Number |
Specific Trap Number |
System Logging Severity Level |
System Log Tag |
|---|---|---|---|---|---|---|
| Chassis Notifications (Alarm Conditions) | ||||||
Chassis MIB (jnx-chassis. mib) |
jnxPowerSupplyFailure |
1.3.6.1.4.1.2636.4.1 |
6 |
1 |
Warning |
CHASSISD_ SNMP_ TRAP |
jnxFanFailure |
1.3.6.1.4.1.26361 |
6 |
2 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxOverTemperature |
11.4.1.2636.4.1 |
6 |
3 |
Alert |
CHASSISD_ SNMP_ TRAP |
|
jnxFruRemoval |
1.3.6.1.4.1.2636.4.1 |
6 |
5 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruInsertion |
1.3.6.1.4.1.2636.4.1 |
6 |
6 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruPowerOff |
1.3.6.1.4.1.2636.4.1 |
6 |
7 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruPowerOn |
1.3.6.1.4.1.2636.4.1 |
6 |
8 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruFailed |
1.3.6.1.4.1.2636.4.1 |
6 |
9 |
Warning |
CHASSISD_ SNMP_ TRAP |
|
jnxFruOffline |
1.3.6.1.4.1.2636.4.1 |
6 |
10 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruOnline |
1.3.6.1.4.1.2636.4.1 |
6 |
11 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruCheck |
1.3.6.1.4.1.2636.4.1 |
6 |
12 |
Warning |
CHASSISD_ SNMP_ TRAP |
|
jnxPowerSupplyOk |
1.3.6.1.4.1.2636.4.2 |
6 |
1 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxFanOK |
1.3.6.1.4.1.2636.4.2 |
6 |
2 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxTemperatureOK |
1.3.6.1.4.1.2636.4.2 |
6 |
3 |
Alert |
CHASSISD_ SNMP_ TRAP |
|
| Configuration Notifications | ||||||
Configuration Management MIB (jnx- configmgmt. mib) |
jnxCmCfgChange |
1.3.6.1.4.1.2636.4.5 |
6 |
1 |
– |
– |
jnxCmRescueChange |
1.3.6.1.4.1.2636.4.5 |
6 |
2 |
– |
– |
|
| Remote Operations | ||||||
Ping MIB (jnx-ping.mib) |
jnxPingRttThresholdExceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
1 |
– |
– |
jnxPingRttStdDevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
2 |
– |
– |
|
jnxPingRttJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
3 |
– |
– |
|
jnxPingEgressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
4 |
– |
– |
|
jnxPingEgressStdDev ThresholdExceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
5 |
– |
– |
|
jnxPingEgressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
6 |
– |
– |
|
jnxPingIngressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
7 |
– |
– |
|
jnxPingIngressStddevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
8 |
– |
– |
|
jnxPingIngressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9 |
6 |
9 |
– |
– |
|
| RMON Alarms | ||||||
RMON MIB (jnx-rmon. mib) |
jnxRmonAlarmGetFailure |
1.3.6.1.4.1.2636.4.3 |
6 |
1 |
– |
– |
jnxRmonGetOk |
1.3.6.1.4.1.2636.4.3 |
6 |
2 |
– |
– |
|
SNMPv2 Traps
Table 13 lists the standard SNMP traps
Table 14 lists the Juniper Networks enterprise-specific traps
Defined in |
Trap Name |
SNMP Trap OID |
System Logging Severity Level |
Syslog Tag |
|---|---|---|---|---|
| Link Notifications | ||||
RFC 2863, The Interfaces Group MIB |
linkDown |
1.3.6.1.6.3.1.1.5.3 |
Warning |
SNMP_TRAP_ LINK_DOWN |
linkUp |
1.3.6.1.6.3.1.1.5.4 |
Info |
SNMP_TRAP_ LINK_UP |
|
| 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 |
pingTestFailed |
1.3.6.1.2.1.80.0.2 |
Info |
SNMP_TRAP_PING_ TEST_FAILED |
|
pingTestCompleted |
1.3.6.1.2.1.80.0.3 |
Info |
SNMP_TRAP_PING_ TEST_COMPLETED |
|
traceRoutePathChange |
1.3.6.1.2.1.81.0.1 |
Info |
SNMP_TRAP_TRACE_ ROUTE_PATH_ CHANGE |
|
traceRouteTestFailed |
1.3.6.1.2.1.81.0.2 |
Info |
SNMP_TRAP_TRACE_ ROUTE_TEST_FAILED |
|
traceRouteTestCompleted |
1.3.6.1.2.1.81.0.3 |
Info |
SNMP_TRAP_TRACE_ ROUTE_TEST_ COMPLETED |
|
| RMON Alarms | ||||
RFC 2819a, RMON MIB |
fallingAlarm |
1.3.6.1.2.1.16.0.1 |
– |
– |
risingAlarm |
1.3.6.1.2.1.16.0.2 |
– |
– |
|
| Routing Notifications | ||||
BGP 4 MIB |
bgpEstablished |
1.3.6.1.2.1.15.7.1 |
– |
– |
bgpBackwardTransition |
1.3.6.1.2.1.15.7.2 |
– |
– |
|
OSPF Trap MIB |
ospfVirtIfStateChange |
1.3.6.1.2.1.14.16.2.1 |
– |
– |
ospfNbrStateChange |
1.3.6.1.2.1.14.16.2.2 |
– |
– |
|
ospfVirtNbrStateChange |
1.3.6.1.2.1.14.16.2.3 |
– |
– |
|
ospfIfConfigError |
1.3.6.1.2.1.14.16.2.4 |
– |
– |
|
ospfVirtIfConfigError |
1.3.6.1.2.1.14.16.2.5 |
– |
– |
|
ospfIfAuthFailure |
1.3.6.1.2.1.14.16.2.6 |
– |
– |
|
ospfVirtIfAuthFailure |
1.3.6.1.2.1.14.16.2.7 |
– |
– |
|
ospfIfRxBadPacket |
1.3.6.1.2.1.14.16.2.8 |
– |
– |
|
ospfVirtIfRxBadPacket |
1.3.6.1.2.1.14.16.2.9 |
– |
– |
|
ospfTxRetransmit |
1.3.6.1.2.1.14.16.2.10 |
– |
– |
|
ospfVirtIfTxRetransmit |
1.3.6.1.2.1.14.16.2.11 |
– |
– |
|
ospfMaxAgeLsa |
1.3.6.1.2.1.14.16.2.13 |
– |
– |
|
ospfIfStateChange |
1.3.6.1.2.1.14.16.2.16 |
– |
– |
|
| 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 |
warmStart |
1.3.6.1.6.3.1.1.5.2 |
Error |
SNMPD_TRAP_ WARM_START |
|
authenticationFailure |
1.3.6.1.6.3.1.1.5.5 |
Notice |
SNMPD_TRAP_ GEN_FAILURE |
|
| 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 |
vrrpTrapAuthFailure |
1.3.6.1.2.1.68.0.2 |
Warning |
VRRPD_AUTH_ FAILURE_ TRAP |
|
Source MIB |
Trap Name |
SNMP Trap OID |
System Logging Severity Level |
System Log Tag |
|---|---|---|---|---|
| Chassis (Alarm Conditions) Notifications | ||||
Chassis MIB (mib-jnx-chassis) |
jnxPowerSupplyFailure |
1.3.6.1.4.1.2636.4.1.1 |
Alert |
CHASSISD_ SNMP_ TRAP |
jnxFanFailure |
1.3.6.1.4.1.2636.4.1.2 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxOverTemperature |
1.3.6.1.4.1.2636.4.1.3 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxFruRemoval |
1.3.6.1.4.1.2636.4.1.5 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruInsertion |
1.3.6.1.4.1.2636.4.1.6 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruPowerOff |
1.3.6.1.4.1.2636.4.1.7 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruPowerOn |
1.3.6.1.4.1.2636.4.1.8 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruFailed |
1.3.6.1.4.1.2636.4.1.9 |
Warning |
CHASSISD_ SNMP_ TRAP |
|
jnxFruOffline |
1.3.6.1.4.1.2636.4.1.10 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruOnline |
1.3.6.1.4.1.2636.4.1.11 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxFruCheck |
1.3.6.1.4.1.2636.4.1.12 |
Notice |
CHASSISD_ SNMP_ TRAP |
|
jnxPowerSupplyOK |
1.3.6.1.4.1.2636.4.2.1 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxFanOK |
1.3.6.1.4.1.2636.4.2.2 |
Critical |
CHASSISD_ SNMP_ TRAP |
|
jnxTemperatureOK |
1.3.6.1.4.1.2636.4.2.3 |
Alert |
CHASSISD_ SNMP_ TRAP |
|
| Configuration Notifications | ||||
Configuration Management MIB (mib-jnx-cfgmgmt) |
jnxCmCfgChange |
1.3.6.1.4.1.2636.4.5.0.1 |
– |
– |
jnxCmRescueChange |
1.3.6.1.4.1.2636.4.5.0.2 |
– |
– |
|
| Remote Operations Notifications | ||||
Ping MIB (mib-jnx-ping) |
jnxPingRttThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.1 |
– |
– |
jnxPingRttStdDevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.2 |
– |
– |
|
jnxPingRttJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.3 |
– |
– |
|
jnxPingEgressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.4 |
– |
– |
|
jnxPingEgressStdDevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.5 |
– |
– |
|
jnxPingEgressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.6 |
– |
– |
|
jnxPingIngressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.7 |
– |
– |
|
jnxPingIngressStddevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.8 |
– |
– |
|
jnxPingIngressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.9 |
– |
– |
|
| RMON Alarms | ||||
RMON MIB (mib-jnx-rmon) |
jnxRmonAlarmGetFailure |
1.3.6.1.4.1.2636.4. 3.0.1 |
– |
– |
jnxRmonGetOk |
1.3.6.1.4.1.2636.4. 3.0.2 |
– |
– |
|
SNMP Traps Supported on QFabric Systems
QFabric systems support standard SNMPv2 traps and Juniper Networks enterprise-specific SNMPv2 traps.
QFabric systems do not support SNMPv1 traps.
For more information, see:
Defined in |
Trap Name |
SNMP Trap OID |
System Logging Severity Level |
Syslog Tag |
|---|---|---|---|---|
| Link Notifications | ||||
RFC 2863, The Interfaces Group MIB |
linkDown |
1.3.6.1.6.3.1.1.5.3 |
Warning |
SNMP_TRAP_ LINK_DOWN |
linkUp |
1.3.6.1.6.3.1.1.5.4 |
Info |
SNMP_TRAP_ LINK_UP |
|
| 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 |
warmStart |
1.3.6.1.6.3.1.1.5.2 |
Error |
SNMPD_TRAP_ WARM_START |
|
authenticationFailure |
1.3.6.1.6.3.1.1.5.5 |
Notice |
SNMPD_TRAP_ GEN_FAILURE |
|
Source MIB |
Trap Name |
SNMP Trap OID |
System Logging Severity Level |
System Log Tag |
|---|---|---|---|---|
Fabric Chassis MIB (mib-jnx-fabric- chassis) |
Fabric Chassis (Alarm Conditions) Notifications | |||
jnxFabricPowerSupplyFailure |
1.3.6.1.4.1.2636.4.19.1 |
Warning |
– |
|
jnxFabricFanFailure |
1.3.6.1.4.1.2636.4.19.2 |
Critical |
– |
|
jnxFabricOverTemperature |
1.3.6.1.4.1.2636.4.19.3 |
Alert |
– |
|
jnxFabricRedundancySwitchover |
1.3.6.1.4.1.2636.4.19.4 |
Notice |
– |
|
jnxFabricFruRemoval |
1.3.6.1.4.1.2636.4.19.5 |
Notice |
– |
|
jnxFabricFruInsertion |
1.3.6.1.4.1.2636.4.19.6 |
Notice |
– |
|
jnxFabricFruPowerOff |
1.3.6.1.4.1.2636.4.19.7 |
Notice |
– |
|
jnxFabricFruPowerOn |
1.3.6.1.4.1.2636.4.19.8 |
Notice |
– |
|
jnxFabricFruFailed |
1.3.6.1.4.1.2636.4.19.9 |
Warning |
– |
|
jnxFabricFruOffline |
1.3.6.1.4.1.2636.4.19.10 |
Notice |
– |
|
jnxFabricFruOnline |
1.3.6.1.4.1.2636.4.19.11 |
Notice |
– |
|
jnxFabricFruCheck |
1.3.6.1.4.1.2636.4.19.12 |
Warning |
– |
|
jnxFabricFEBSwitchover |
1.3.6.1.4.1.2636.4.19.13 |
Warning |
– |
|
jnxFabricHardDiskFailed |
1.3.6.1.4.1.2636.4.19.14 |
Warning |
– |
|
jnxFabricHardDiskMissing |
1.3.6.1.4.1.2636.4.19.15 |
Warning |
– |
|
jnxFabricBootFromBackup |
1.3.6.1.4.1.2636.4.19.16 |
Warning |
– |
|
| Fabric Chassis (Alarm Cleared Conditions) Notifications | ||||
jnxFabricPowerSupplyOK |
1.3.6.1.4.1.2636.4.20.1 |
Critical |
– |
|
jnxFabricFanOK |
1.3.6.1.4.1.2636.4.20.2 |
Critical |
– |
|
jnxFabricTemperatureOK |
1.3.6.1.4.1.2636.4.20.3 |
Alert |
– |
|
jnxFabricFruOK |
1.3.6.1.4.1.2636.4.20.4 |
– |
– |
|
QFabric MIB (mib-jnx-qf-smi) |
QFabric MIB Notifications | |||
jnxQFabricDownloadIssued |
1.3.6.1.4.1.2636.3.42.1.0.1 |
– |
– |
|
jnxQFabricDownloadFailed |
1.3.6.1.4.1.2636.3.42.1.0.2 |
– |
– |
|
jnxQFabricDownloadSucceeded |
1.3.6.1.4.1.2636.3.42.1.0.3 |
– |
– |
|
jnxQFabricUpgradeIssued |
1.3.6.1.4.1.2636.3.42.1.0.4 |
– |
– |
|
jnxQFabricUpgradeFailed |
1.3.6.1.4.1.2636.3.42.1.0.5 |
– |
– |
|
jnxQFabricUpgradeSucceeded |
1.3.6.1.4.1.2636.3.42.1.0.6 |
– |
– |
|
| Configuration Notifications | ||||
Configuration Management MIB (mib-jnx-cfgmgmt) |
jnxCmCfgChange |
1.3.6.1.4.1.2636.4.5.0.1 |
– |
– |
jnxCmRescueChange |
1.3.6.1.4.1.2636.4.5.0.2 |
– |
– |
|
| Remote Operations Notifications | ||||
Ping MIB (mib-jnx-ping) |
jnxPingRttThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.1 |
– |
– |
jnxPingRttStdDevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.2 |
– |
– |
|
jnxPingRttJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.3 |
– |
– |
|
jnxPingEgressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.4 |
– |
– |
|
jnxPingEgressStdDevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.5 |
– |
– |
|
jnxPingEgressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.6 |
– |
– |
|
jnxPingIngressThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.7 |
– |
– |
|
jnxPingIngressStddevThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.8 |
– |
– |
|
jnxPingIngressJitterThreshold Exceeded |
1.3.6.1.4.1.2636.4.9.0.9 |
– |
– |
|
See Also
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 17 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.
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 |
|
1.3.6.1.4.1.2636 |
4 |
0 |
Notice |
SNMPD_ TRAP_ GEN_FAILURE |
All devices running Junos OS. |
|
1.3.6.1.4.1.2636 |
0 |
0 |
Critical |
SNMPD_TRAP_ COLD_START |
All devices running Junos OS. |
|
|
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 |
|
1.3.6.1.4.1.2636 |
2 |
0 |
Warning |
SNMP_ TRAP_ LINK_DOWN |
All devices running Junos OS. |
|
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 |
|
1.3.6.1.2.1.80.0 |
6 |
1 |
Info |
SNMP_TRAP _PING_ PROBE_ FAILED |
All devices running Junos OS. |
|
1.3.6.1.2.1.80.0 |
6 |
2 |
Info |
SNMP_TRAP_ PING_TEST _FAILED |
All devices running Junos OS. |
|
|
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 |
|
1.3.6.1.2.1.16 |
6 |
2 |
– |
– |
All devices running Junos OS. |
|
1.3.6.1.2.1.16 |
6 |
1 |
– |
– |
All devices running Junos OS. |
|
| Routing Notifications | |||||||
BGP 4 MIB |
|
1.3.6.1.2.1.15.7 |
6 |
1 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
1.3.6.1.2.1.15.7 |
6 |
2 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
OSPF TRAP MIB |
|
1.3.6.1.2.1.14.16.2 |
6 |
1 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
1.3.6.1.2.1.14.16.2 |
6 |
2 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
3 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
4 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
5 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
6 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
7 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
8 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
9 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
10 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
11 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
13 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
|
1.3.6.1.2.1.14.16.2 |
6 |
16 |
– |
– |
M, T, MX, J, EX, and SRX Series Firewalls. |
|
| VRRP Notifications | |||||||
RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol |
|
1.3.6.1.2.1.68 |
6 |
1 |
Warning |
VRRPD_NEW MASTER_TRAP |
All devices running Junos OS. |
|
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) |
|
1.3.6.1.2.1.207 |
6 |
1 |
Warning |
VRRPD_NEW_MASTER |
M and MX |
|
1.3.6.1.2.1.207 |
6 |
2 |
Warning |
VRRPD_V3_PROTO_ERROR |
M and MX |
|
Standard SNMP Version 2 Traps
Table 18 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.
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) |
|
1.3.6.1.6.3.1.1.5.1 |
Critical |
SNMPD_TRAP_ COLD_START |
All devices running Junos OS. |
|
1.3.6.1.6.3.1.1.5.2 |
Error |
SNMPD_TRAP_ WARM_START |
All devices running Junos OS. |
|
|
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 |
|
1.3.6.1.6.3.1.1.5.3 |
Warning |
SNMP_TRAP_ LINK_DOWN |
All devices running Junos OS. |
|
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 |
|
1.3.6.1.2.1.80.0.1 |
Info |
SNMP_TRAP_ PING_PROBE_ FAILED |
All devices running Junos OS. |
|
1.3.6.1.2.1.80.0.2 |
Info |
SNMP_TRAP_PING_ TEST_FAILED |
All devices running Junos OS. |
|
|
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 |
|
1.3.6.1.2.1.16.0.1 |
– |
– |
All devices running Junos OS. |
|
1.3.6.1.2.1.16.0.2 |
– |
– |
All devices running Junos OS. |
|
| Routing Notifications | |||||
BGP 4 MIB |
|
1.3.6.1.2.1.15.7.1 |
– |
– |
All devices running Junos OS. |
|
1.3.6.1.2.1.15.7.2 |
– |
– |
All devices running Junos OS. |
|
OSPF Trap MIB |
|
1.3.6.1.2.1.14.16.2.1 |
– |
– |
All devices running Junos OS. |
|
1.3.6.1.2.1.14.16.2.2 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.3 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.4 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.5 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.6 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.7 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.8 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.9 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.10 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.11 |
– |
– |
All devices running Junos OS. |
|
|
1.3.6.1.2.1.14.16.2.13 |
– |
– |
All devices running Junos OS. |
|
|
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 |
|
||||
|
|||||
|
|||||
|
|||||
| Entity State MIB Notifications | |||||
RFC 4268, Entity State MIB |
|
1.3.6.1.2.1.131.0.1 |
Notice |
CHASSISD_SNMP_TRAP3 |
MX240, MX480, and MX960 |
|
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) |
|
||||
|
|||||
|
|||||
|
|||||
|
|||||
| VRRP Notifications | |||||
RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol |
|
1.3.6.1.2.1.68.0.1 |
Warning |
VRRPD_ NEWMASTER_ TRAP |
All devices running Junos OS. |
|
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) |
|
1.3.6.1.2.1.207.0.1 |
Warning |
VRRPD_NEW_MASTER |
M and MX |
|
1.3.6.1.2.1.207.0.2 |
Warning |
VRRPD_V3_PROTO_ERROR |
M and MX |
|
See Also
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
- Defining a Custom MIB for a Syslog Trap
- Limitations of Using Custom SNMP Traps
- Example Custom Syslog Trap
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 19.
Root |
Description |
OID |
|---|---|---|
|
Custom MIB module |
.1.3.6.1.4.1.2636.3.86 |
|
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:
user@host> request system yang add snmp module yang-filename package package-name
The yang-filename includes the
absolute path.
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.
See Also
Defining a Custom MIB for a Syslog Trap
In this procedure, we use the following example files:
MIB file to convert
output
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:
mib-jnx-example-custom-syslog.txt
-- *******************************************************************
-- Juniper enterprise specific custom syslog MIB.
--
-- Copyright (c) 2002-2004, 2006, Juniper Networks, Inc.
-- All rights reserved.
--
-- The contents of this document are subject to change without notice.
-- *******************************************************************
JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32
FROM SNMPv2-SMI
jnxCustomMibRoot, jnxCustomSyslogNotifications
FROM JUNIPER-SMI
ifName
FROM IF-MIB
;
jnxExampleCustomSyslog MODULE-IDENTITY
LAST-UPDATED "201711270000Z"
ORGANIZATION "Juniper Networks, Inc."
CONTACT-INFO
"Juniper Technical Assistance Center
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, CA 94089
E-mail: support@juniper.net"
DESCRIPTION
"Example MIB objects for custom syslog"
REVISION "201711270000Z"
DESCRIPTION
"Initial draft"
::= { jnxCustomMibRoot 1 }
jnxExampleCustomSyslogMessage OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The syslog message string."
::= { jnxExampleCustomSyslog 1 }
jnxExampleCustomSyslogInteger OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Example OID for adding custom Integer OID"
::= { jnxExampleCustomSyslog 2 }
jnxExampleSyslogTrap1 NOTIFICATION-TYPE
OBJECTS { jnxExampleCustomSyslogMessage }
STATUS current
DESCRIPTION
"This TRAP is reserved to be sent when event 1 occurs"
::= { jnxCustomSyslogNotifications 1 }
jnxExampleSyslogTrap2 NOTIFICATION-TYPE
OBJECTS { jnxExampleCustomSyslogInteger, jnxExampleCustomSyslogMessage }
STATUS current
DESCRIPTION
"This TRAP is reserved to be sent when event 2 occurs"
::= { jnxCustomSyslogNotifications 2 }
jnxExampleSyslogTrap3 NOTIFICATION-TYPE
OBJECTS { ifName, jnxExampleCustomSyslogMessage }
STATUS current
DESCRIPTION
"This TRAP is reserved to be sent when event 3 occurs"
::= { jnxCustomSyslogNotifications 3 }
END
JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang
/*
* This YANG module has been generated by smidump 0.5.0:
*
* smidump -f yang JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB
*
* Do not edit. Edit the source file instead!
*/
module JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB {
namespace "urn:ietf:params:xml:ns:yang:smiv2:JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB";
prefix "juniper-example";
import IF-MIB {
prefix "if-mib";
}
import JUNIPER-SMI {
prefix "juniper-smi";
}
import ietf-yang-smiv2 {
prefix "smiv2";
}
organization
"Juniper Networks, Inc.";
contact
"Juniper Technical Assistance Center
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, CA 94089
E-mail: support@juniper.net";
description
"Example MIB objects for custom syslog";
revision 2017-11-27 {
description
"Initial draft";
}
container JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB {
config false;
}
notification jnxExampleSyslogTrap1 {
description
"This TRAP is reserved to be sent when event 1 occurs";
smiv2:oid "1.3.6.1.4.1.2636.4.30.1";
container object-1 {
leaf jnxExampleCustomSyslogMessage {
type binary;
description
"The syslog message string.";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.1";
}
}
}
notification jnxExampleSyslogTrap2 {
description
"This TRAP is reserved to be sent when event 2 occurs";
smiv2:oid "1.3.6.1.4.1.2636.4.30.2";
container object-1 {
leaf jnxExampleCustomSyslogInteger {
type int32;
description
"Example OID for adding custom Integer OID";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.2";
}
}
container object-2 {
leaf jnxExampleCustomSyslogMessage {
type binary;
description
"The syslog message string.";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.1";
}
}
}
notification jnxExampleSyslogTrap3 {
description
"This TRAP is reserved to be sent when event 3 occurs";
smiv2:oid "1.3.6.1.4.1.2636.4.30.3";
container object-1 {
leaf ifIndex {
type leafref {
path "/if-mib:IF-MIB/if-mib:ifTable/if-mib:ifEntry/if-mib:ifIndex";
}
}
leaf ifName {
type leafref {
path "/if-mib:IF-MIB/if-mib:ifTable/if-mib:ifEntry/if-mib:ifName";
}
}
}
container object-2 {
leaf jnxExampleCustomSyslogMessage {
type binary;
description
"The syslog message string.";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.1";
}
}
}
smiv2:alias "jnxExampleCustomSyslog" {
smiv2:oid "1.3.6.1.4.1.2636.3.86.1";
}
} 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:
Sample MIB file
-- *******************************************************************
-- Juniper enterprise specific custom syslog MIB.
--
-- Copyright (c) 2002-2004, 2006, Juniper Networks, Inc.
-- All rights reserved.
--
-- The contents of this document are subject to change without notice.
-- *******************************************************************
JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
jnxCustomMibRoot, jnxCustomSyslogNotifications
FROM JUNIPER-SMI
;
jnxExampleCustomSyslog MODULE-IDENTITY
LAST-UPDATED "201806220000Z"
ORGANIZATION "Juniper Networks, Inc."
CONTACT-INFO
"Juniper Technical Assistance Center
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, CA 94089
E-mail: support@juniper.net"
DESCRIPTION
"Example MIB objects for custom syslog"
REVISION "201806220000Z"
DESCRIPTION
"Initial draft"
::= { jnxCustomMibRoot 1 }
username OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Username"
::= { jnxExampleCustomSyslog 1 }
command OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Executed command"
::= { jnxExampleCustomSyslog 2 }
comment OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Additional comment"
::= { jnxExampleCustomSyslog 3 }
enteredConfigMode NOTIFICATION-TYPE
OBJECTS { username }
STATUS current
DESCRIPTION
"This TRAP is sent when a user enteres config mode. "
::= { jnxCustomSyslogNotifications 1 }
configCommitted NOTIFICATION-TYPE
OBJECTS { username, command, comment }
STATUS current
DESCRIPTION
"This TRAP is sent when a user does config commit"
::= { jnxCustomSyslogNotifications 2 }
END
Sample YANG Converted File
/*
* This YANG module has been generated by smidump 0.5.0:
*
* smidump -f yang JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB
*
* Do not edit. Edit the source file instead!
*/
module JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB {
namespace "urn:ietf:params:xml:ns:yang:smiv2:JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB";
prefix "juniper-example";
import JUNIPER-SMI {
prefix "juniper-smi";
}
import ietf-yang-smiv2 {
prefix "smiv2";
}
organization
"Juniper Networks, Inc.";
contact
"Juniper Technical Assistance Center
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, CA 94089
E-mail: support@juniper.net";
description
"Example MIB objects for custom syslog";
revision 2018-06-22 {
description
"Initial draft";
}
container JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB {
config false;
}
notification enteredConfigMode {
description
"This TRAP is sent when a user enteres config mode. ";
smiv2:oid "1.3.6.1.4.1.2636.4.30.1";
container object-1 {
leaf username {
type binary;
description
"Username";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.1";
}
}
}
notification configCommitted {
description
"This TRAP is sent when a user does config commit";
smiv2:oid "1.3.6.1.4.1.2636.4.30.2";
container object-1 {
leaf username {
type binary;
description
"Username";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.1";
}
}
container object-2 {
leaf command {
type binary;
description
"Executed command";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.2";
}
}
container object-3 {
leaf comment {
type binary;
description
"Additional comment";
smiv2:max-access "accessible-for-notify";
smiv2:oid "1.3.6.1.4.1.2636.3.86.1.3";
}
}
}
smiv2:alias "jnxExampleCustomSyslog" {
smiv2:oid "1.3.6.1.4.1.2636.3.86.1";
}
}slax Script cutom_trap.slax (in /var/db/scripts/event)
version 1.0;
ns junos = "http://xml.juniper.net/junos/*/junos";
ns xnm = "http://xml.juniper.net/xnm/1.1/xnm";
ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0";
import "../import/junos.xsl";
match / {
<event-script-results> {
expr jcs:syslog("external.warning",event-script-input/trigger-event/id);
var $id = event-script-input/trigger-event/id;
if ($id == 'UI_DBASE_LOGIN_EVENT'){
var $committing-user = event-script-input/trigger-event/attribute-list/attribute[name=="username"]/value;
var $requestSnmpTrap = <request-snmp-spoof-trap> {
<trap> "enteredConfigMode";
<variable-bindings>
"username=" _ $committing-user;
}
var $snmpTrapResults = jcs:invoke( $requestSnmpTrap );
}
else if ($id == 'UI_COMMIT'){
var $committing-user = event-script-input/trigger-event/attribute-list/attribute[name=="username"]/value;
var $committing-command = event-script-input/trigger-event/attribute-list/attribute[name=="command"]/value;
var $committing-comment = event-script-input/trigger-event/attribute-list/attribute[name=="message"]/value;
var $requestSnmpTrap = <request-snmp-spoof-trap> {
<trap> "configCommitted";
<variable-bindings>
"username=" _ $committing-user _ ", command=" _ $committing-command _ ", comment=" _ $committing-comment;
}
var $snmpTrapResults = jcs:invoke( $requestSnmpTrap );
}
}
}