Juniper-DHCP-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsJuniper-DHCP-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2007-01-31

Category: Domain: Subscriber Management, Protocol: DHCP, Vendor: Juniper

Description: Provides managed objects for DHCP server pool management, lease tracking, and relay statistics on Juniper Networks E-series broadband routers.

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-DHCP-MIB?

Juniper-DHCP-MIB is a Juniper Networks enterprise MIB covering DHCP relay and proxy functionality on Juniper E-series (ERX) broadband edge routers. It exposes configuration and operational data for DHCP relay agent option-82 handling (circuit ID, remote ID, hostname, VR-name insertion) plus counters for relay errors such as bad messages, unknown messages, and gateway-address spoofing attempts. Rather than hardware health, this MIB is primarily useful for monitoring software/protocol-level status — the health of the DHCP relay/proxy service, its configuration state, and fault counters indicating malformed or malicious DHCP traffic at the network edge. It builds on standard IETF DHCP concepts (RFC 2131, option-82/RFC 3046) but defines Juniper-proprietary object identifiers rather than reusing a standard DHCP MIB. It is typically deployed by broadband/ISP operators monitoring subscriber-facing DHCP relay behavior on Juniper E-series routers. Engineers can download the Juniper-DHCP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-DHCP-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 E-series (ERX) broadband routers

Monitoring Examples

An administrator would poll juniDhcpRelayBadMessages and juniDhcpRelayUnknownMessages to detect malformed DHCP traffic arriving at a relay interface, and check juniDhcpRelayGatewayAddrSpoofs to catch spoofing attempts on subscriber-facing ports. Scalars like juniDhcpRelayAgentCircuitIdEnable and juniDhcpRelayAgentRemoteIdEnable confirm whether option-82 sub-options are inserted correctly for subscriber identification. A rising juniDhcpRelayAgentInfoAlreadyPresents counter would flag double-insertion issues from downstream relay devices.

What Can Be Monitored

  • DHCP relay agent option-82 settings
  • bad/unknown DHCP messages
  • gateway address spoofing attempts
  • circuit ID/remote ID insertion status
  • DHCP proxy forwarding counters
Imported Objects

From IF-MIB

InterfaceIndex

From Juniper-MIBs

juniMibsMODULE-IDENTITY

From Juniper-ROUTER-MIB

juniRouterNameOBJECT-TYPE

From Juniper-TC

JuniEnable
JuniInterfaceLocation
JuniLogSeverity

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
PhysAddress
RowStatus
TEXTUAL-CONVENTION
TimeInterval
TruthValue

How to Use in IPNetwork Monitor

Example using juniDhcpRelayBadMessages OID:

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.
OIDs

RFC description

Manages DHCP server and relay functions including bindings, pools, and lease intervals on Juniper platforms.

Start monitoring Juniper Networks E-series (ERX) broadband router (DHCP relay/proxy) 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-DHCP-MIB