DVMRP-STD-MIB-UNI :: dvmrpInterfaceRcvBadPkts

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › DVMRP-STD-MIB-UNI › dvmrpInterfaceRcvBadPkts

dvmrpInterfaceRcvBadPkts

Module: DVMRP-STD-MIB-UNI

OID (symbolic): DVMRP-STD-MIB-UNI::dvmrpInterfaceRcvBadPkts

OID (numeric): 1.3.6.1.4.1.4874.3.2.1.1.1.1.2.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: 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).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.3.2.1.1.1.1.2.1.5
snmpwalk -v2c -c public <target> DVMRP-STD-MIB-UNI::dvmrpInterfaceRcvBadPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.3.2.1.1.1.1.2.1.5.1
snmpget -v2c -c public <target> DVMRP-STD-MIB-UNI::dvmrpInterfaceRcvBadPkts.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> dvmrpInterfaceRcvBadPkts.1

Start monitoring DVMRP-capable multicast router, Unisphere/Juniper lineage (vendor-neutral IETF standard variant) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DVMRP-STD-MIB-UNI::dvmrpInterfaceRcvBadPkts OID value, configure state conditions and alerts, and monitor any DVMRP-capable multicast router, Unisphere/Juniper lineage (vendor-neutral IETF standard variant) from a single console.

How to Use in IPNetwork Monitor

Select a DVMRP-capable multicast router, Unisphere/Juniper lineage (vendor-neutral IETF standard variant) 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 dvmrpInterfaceRcvBadPkts 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.

OID Breakdown

Upper-level ancestors (15 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.3juniperUniExperimentJuniper-UNI-SMI
1.3.6.1.4.1.4874.3.2juniExperimentJuniper-Experiment
1.3.6.1.4.1.4874.3.2.1juniDvmrpExperimentJuniper-Experiment
1.3.6.1.4.1.4874.3.2.1.1junidDvmrpStdMIBDVMRP-STD-MIB-JUNI
1.3.6.1.4.1.4874.3.2.1.1.1junidDvmrpMIBObjectsDVMRP-STD-MIB-JUNI
1.3.6.1.4.1.4874.3.2.1.1.1.1junidDvmrpDVMRP-STD-MIB-JUNI
1.3.6.1.4.1.4874.3.2.1.1.1.1.2junidDvmrpInterfaceTableDVMRP-STD-MIB-JUNI
1.3.6.1.4.1.4874.3.2.1.1.1.1.2.1junidDvmrpInterfaceEntryDVMRP-STD-MIB-JUNI
Numeric OIDNameModule
1.3.6.1.4.1.4874.3.2.1.1.1.1.2.1.5dvmrpInterfaceRcvBadPktsDVMRP-STD-MIB-UNI