All MIBs › Juniper-DISMAN-EVENT-MIB
Organization: Juniper Networks, Inc.
Last Updated: 2003-10-30
Category: Vendor: Juniper
Description: Defines managed objects for Distributed Management (DISMAN) event scripting on Juniper Networks E-series platforms.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is Juniper-DISMAN-EVENT-MIB?
Juniper-DISMAN-EVENT-MIB extends the IETF DISMAN-EVENT-MIB with Juniper-specific event triggers and actions for E-series routers, part of the Distributed Management (DISMAN) framework for scripted, condition-based network management. It exposes objects for defining triggers that watch other MIB objects and fire actions (such as notifications) when conditions like existence, threshold, or boolean tests are met. In monitoring terms it lets an operator build custom software-level health checks, for example triggers that detect when a process, interface, or counter object appears, disappears, or crosses a limit, effectively creating ad hoc fault-detection logic on the device itself. It explicitly depends on and extends the IETF DISMAN-EVENT-MIB trigger and object model. It is deployed on Juniper E-series routers where administrators want proactive, device-resident alerting rather than only external polling, and administrators can download the Juniper-DISMAN-EVENT-MIB file directly to load it into their MIB browser or compiler.
IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-DISMAN-EVENT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Juniper E-series router
Monitoring Examples
An operator configures juniMteTriggerTable/juniMteTriggerEntry rows with a juniMteTriggerContextNameLimit to scope which instances a trigger applies to, then reads juniMteExistenceTestResult to see whether a watched object (e.g., a process or interface entry) currently exists. Notifications defined under juniDismanEventMIBNotificationObjects fire through juniDismanEventMIBNotificationPrefix when a trigger condition is met, alerting on conditions such as an interface disappearing or a counter object appearing unexpectedly. This effectively turns generic MIB objects elsewhere on the device into custom fault triggers without needing external polling software.
What Can Be Monitored
- configured event triggers
- trigger existence-test results
- triggered notification events
- monitored object context scope
Imported Objects
From DISMAN-EVENT-MIB
| mteTriggerEntry | OBJECT-TYPE |
From Juniper-MIBs
| juniMibs | MODULE-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
OIDs
RFC description
Juniper Networks Distributed Management (Disman) Event MIB for defining SNMP event triggers, actions, and trap management on Juniper E-series and other Junos OS devices.
Start monitoring Juniper E-series router (DISMAN event triggers/actions) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.