DVMRP-STD-MIB-JUNI

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DVMRP-STD-MIB-JUNI

Organization: IETF IDMR Working Group.

Last Updated: 1999-10-19

Category: Protocol: DVMRP, Technology: Multicast

Description: Juniper vendor-specific implementation of the standard DVMRP MIB for managing multicast routing 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 DVMRP-STD-MIB-JUNI?

DVMRP-STD-MIB-JUNI is Juniper Networks' vendor-specific implementation of the standard Distance Vector Multicast Routing Protocol (DVMRP) MIB, used to manage and monitor DVMRP-based IP multicast routing on Juniper platforms. It exposes DVMRP process-level data such as protocol version string, generation ID, and route counts, plus a per-interface table covering local address, metric, administrative/operational status, and received bad-packet/bad-route error counters. Its monitoring value is in multicast routing protocol health and fault detection: the reachable/total route counts and per-interface bad-packet and bad-route counters reveal whether a DVMRP interface is functioning correctly or experiencing protocol errors, misconfiguration, or connectivity loss with multicast neighbors. As a Juniper-prefixed re-implementation of the IETF standard DVMRP-MIB (and related multicast MIB work), it is directly derived from and dependent on that standards-track MIB structure. It is typically deployed on Juniper routers in networks running legacy DVMRP multicast routing, such as older multicast research/production networks or MBone-style deployments, where DVMRP-STD-MIB-JUNI SNMP monitoring surfaces per-interface protocol errors affecting multicast reachability.

IPNetwork Monitor allows you to monitor SNMP objects defined in DVMRP-STD-MIB-JUNI. 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 routers running DVMRP multicast routing

Monitoring Examples

An operator would poll junidDvmrpInterfaceTable/junidDvmrpInterfaceEntry to check junidDvmrpInterfaceStatus and junidDvmrpInterfaceMetric per interface, then read junidDvmrpInterfaceRcvBadPkts and junidDvmrpInterfaceRcvBadRoutes to detect protocol errors. A steadily increasing junidDvmrpInterfaceRcvBadRoutes counter alongside a static or declining junidDvmrpNumRoutes/junidDvmrpReachableRoutes value would reveal a DVMRP neighbor adjacency problem or route corruption affecting multicast reachability.

What Can Be Monitored

  • DVMRP interface admin/operational status
  • received bad packets and bad routes per interface
  • total and reachable DVMRP route counts
  • DVMRP protocol generation ID/version
Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From Juniper-Experiment

juniDvmrpExperimentOBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DisplayString
RowStatus

How to Use in IPNetwork Monitor

Example using junidDvmrpInterfaceRcvBadPkts OID:

Select a Juniper router running DVMRP multicast routing 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 junidDvmrpInterfaceRcvBadPkts 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 DVMRP messages received on the interface by the DVMRP process which were subsequently discarded as invalid (e.g. invalid packet format, or a route report from an unknown neighbor). 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

RFC description

Manages Distance Vector Multicast Routing Protocol (DVMRP) for IP multicast routing on Juniper routers.

Start monitoring Juniper router running DVMRP multicast routing 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 DVMRP-STD-MIB-JUNI