JUNIPER-RMON-MIB

All MIBs › JUNIPER-RMON-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2005-11-23

Category: Network Monitoring (RMON), Vendor: Juniper

Description: Juniper Networks MIB extending standard RMON with Juniper-specific remote network monitoring capabilities on Juniper 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-RMON-MIB?

JUNIPER-RMON-MIB is a Juniper Networks enterprise MIB that extends the standard IETF RMON-MIB with Juniper-specific remote network monitoring capabilities on Juniper platforms. It supplements standard RMON statistics, history, alarm, and event groups with Juniper-specific notification objects and prefixes for enterprise-specific traps. Its monitoring value is primarily around traffic/performance monitoring and fault notification, extending RMON's packet, error, and threshold-alarm capabilities with vendor-specific trap conditions rather than exposing new hardware sensors of its own. It has an explicit, direct dependency on the standard RMON-MIB (RFC 2819), since it is described purely as extending that MIB's object model. It is deployed on Juniper routers and switches where operators rely on JUNIPER-RMON-MIB SNMP monitoring for RMON-based traffic analysis with Juniper-specific alarm/event trap extensions layered on top.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-RMON-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 Networks routers
Juniper Networks switches

Monitoring Examples

An administrator using standard RMON alarm and event tables together with jnxRmonTrapPrefix-rooted Juniper-specific notifications would receive vendor-specific traps when Juniper-defined RMON threshold conditions are triggered, in addition to the standard RMON alarm traps. This lets an operator distinguish Juniper enterprise-specific RMON alarm conditions from generic RMON events when correlating traffic threshold breaches on a monitored interface. Because only the jnxRmonTrapPrefix object was provided as a sample, other extended object names cannot be confirmed from source.

What Can Be Monitored

RMON alarm/event trap conditions (Juniper-specific)
traffic threshold breach notifications

Imported Objects

From JUNIPER-SMI

jnxMibs	OBJECT-IDENTITY
jnxRmonTraps	OBJECT-IDENTITY

From RMON-MIB

alarmEntry	OBJECT-TYPE
alarmIndex	OBJECT-TYPE
alarmVariable	OBJECT-TYPE

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

How to Use in IPNetwork Monitor

Example using jnxRmonAlarmGetFailCnt OID:

Select a Juniper Networks router/switch (RMON extension) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxRmonAlarmGetFailCnt into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of times the internal get request for the variable monitored by this entry has failed. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxRmon	1.3.6.1.4.1.2636.3.13			The MIB modules extends the Rmon as defined in RMON-MIB.
jnxRmonAlarmTable	1.3.6.1.4.1.2636.3.13.1		not-accessible	Extensions to the rmon Alarm Table
jnxRmonAlarmEntry	1.3.6.1.4.1.2636.3.13.1.1		not-accessible	Each entry containing additional management information applicable to a particular rmon alarm entry.
C32 jnxRmonAlarmGetFailCntEx	1.3.6.1.4.1.2636.3.13.1.1.1	Counter32	read-only	The number of times the internal get request for the variable monitored by this entry has failed.
TIK jnxRmonAlarmGetFailTime	1.3.6.1.4.1.2636.3.13.1.1.2	TimeTicks	read-only	The value of sysUpTime when an internal get request for the variable monitored by this entry last failed.
INT jnxRmonAlarmGetFailReason	1.3.6.1.4.1.2636.3.13.1.1.3	INTEGER	read-only	The reason why an internal get request for the variable monitored by this entry last failed.
TIK jnxRmonAlarmGetOkTime	1.3.6.1.4.1.2636.3.13.1.1.4	TimeTicks	read-only	The value of sysUpTime when an internal get request for the variable monitored by this entry succeeded and the entry left the getFailure state.
INT jnxRmonAlarmState	1.3.6.1.4.1.2636.3.13.1.1.5	INTEGER	read-only	The current state of this rmon alarm entry. The states and their definitions are: underCreation ... entry has not been activated active ... entry is active & within thresholds startup ... entry still waiting for 1st value risingThreshold ... entry has crossed the rising threshold fallingThreshold... entry has crossed the falling threshold getFailure ... internal get request failed
jnxRmonTrapPrefix	1.3.6.1.4.1.2636.4.3.0
NTF jnxRmonAlarmGetFailure	1.3.6.1.4.1.2636.4.3.0.1			The SNMP trap that is generated when the get request for an alarm variable returns an error. The specific error is identified by jnxRmonAlarmGetFailReason.
NTF jnxRmonGetOk	1.3.6.1.4.1.2636.4.3.0.2			The SNMP trap that is generated when the get request for an alarm variable is successful. This is only sent after previous attempts were unsuccessful.

RFC description

Juniper RMON extension MIB for enhanced remote monitoring alarm management and failure reason tracking.

Start monitoring Juniper Networks router/switch (RMON extension) 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.

Download JUNIPER-RMON-MIB