Unisphere-Data-DHCP-MIB :: usdDhcpRelayBadMessages

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUnisphere-Data-DHCP-MIBusdDhcpRelayBadMessages

usdDhcpRelayBadMessages

Module: Unisphere-Data-DHCP-MIB

OID (symbolic): Unisphere-Data-DHCP-MIB::usdDhcpRelayBadMessages

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 DHCP relay messages received by this agent, that were discarded because of apparent corruption.

What is usdDhcpRelayBadMessages?

A running count of DHCP relay messages this agent discarded because they appeared corrupted. Admins watch this counter for signs of a malfunctioning DHCP client or server, or a corrupting link, sending malformed packets.

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> Unisphere-Data-DHCP-MIB::usdDhcpRelayBadMessages

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> Unisphere-Data-DHCP-MIB::usdDhcpRelayBadMessages.1

Start monitoring Unisphere Networks ERX broadband edge routers, later Juniper E-series (DHCP relay option-82/error-counter status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-DHCP-MIB::usdDhcpRelayBadMessages OID value, configure state conditions and alerts, and monitor any Unisphere Networks ERX broadband edge routers, later Juniper E-series (DHCP relay option-82/error-counter status) from a single console.

How to Use in IPNetwork Monitor

Select an Unisphere Networks ERX broadband edge routers, later Juniper E-serie (DHCP relay option-82/error-counter status) 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 usdDhcpRelayBadMessages into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of DHCP relay messages received by this agent, that were discarded because of apparent corruption. 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 (13 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
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
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.22.1.1.1.2usdDhcpRelayBadMessagesUnisphere-Data-DHCP-MIB