Juniper-DHCP-MIB :: juniDhcpRelayBadMessages

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJuniper-DHCP-MIBjuniDhcpRelayBadMessages

juniDhcpRelayBadMessages

Module: Juniper-DHCP-MIB

OID (symbolic): Juniper-DHCP-MIB::juniDhcpRelayBadMessages

OID (numeric): 1.3.6.1.4.1.4874.2.2.22.1.1.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of received DHCP relay messages that were discarded because their message operation (e.g. BOOTREQUEST, BOOTREPLY) was unknown, possibly due to corruption.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.22.1.1.1.2
snmpwalk -v2c -c public <target> Juniper-DHCP-MIB::juniDhcpRelayBadMessages

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.22.1.1.1.2.1
snmpget -v2c -c public <target> Juniper-DHCP-MIB::juniDhcpRelayBadMessages.1

Start monitoring Juniper Networks E-series (ERX) broadband router (DHCP relay/proxy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-DHCP-MIB::juniDhcpRelayBadMessages OID value, configure state conditions and alerts, and monitor any Juniper Networks E-series (ERX) broadband router (DHCP relay/proxy) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks E-series (ERX) broadband router (DHCP relay/proxy) 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 juniDhcpRelayBadMessages into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of received DHCP relay messages that were discarded because their message operation (e.g. 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 (9 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.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.22juniDhcpMIBJuniper-DHCP-MIB
1.3.6.1.4.1.4874.2.2.22.1juniDhcpObjectsJuniper-DHCP-MIB
1.3.6.1.4.1.4874.2.2.22.1.1juniDhcpRelayJuniper-DHCP-MIB
1.3.6.1.4.1.4874.2.2.22.1.1.1juniDhcpRelayScalarsJuniper-DHCP-MIB
1.3.6.1.4.1.4874.2.2.22.1.1.1.2juniDhcpRelayBadMessagesJuniper-DHCP-MIB