DHCP-SERVER-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsDHCP-SERVER-MIB

Organization: Lucent Technologies

Last Updated: 2006-06-22

Category: Protocol: DHCP, Standard: IETF

Description: DHCP server management MIB providing objects to configure address pools, lease management, and monitor server statistics.

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

The DHCP-SERVER-MIB (under the Lucent "ipspg"/"ipspgDHCP" OID branch) is a vendor-specific module for devices implementing the server side of BOOTP and DHCP for IPv4, originally developed for Lucent's IP Services Product Group access/gateway platforms. It exposes objects for configuring DHCP address pools and lease parameters as well as monitoring server-side operational statistics related to how leases are allocated and consumed. Its monitoring value is primarily software/service-state focused: administrators watch pool utilization and lease statistics to detect address-pool exhaustion, misconfigured scopes, or a DHCP service that has stopped responding to client requests. It is grounded in the standards-based DHCP (RFC 2131) and BOOTP protocols but implemented as a private vendor MIB rather than a formally standardized IETF DHCP server MIB. It is deployed on Lucent/Avaya-descended broadband access gateways or routers that provide integrated DHCP server functionality to downstream subscriber or LAN clients.

IPNetwork Monitor allows you to monitor SNMP objects defined in DHCP-SERVER-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

  • Lucent/Avaya IP Services access gateways/routers with integrated DHCP server

Monitoring Examples

The sample objects available are limited to top-level OID branch names (lucent, ipspg, ipspgDHCP) rather than leaf objects, so specific pool/lease table names cannot be confirmed from the source. An operator would typically expect to poll an address-pool table for allocated-versus-available lease counts and a statistics group for requests, offers, acks, and naks to detect pool exhaustion or a misbehaving DHCP relay. This description is necessarily general given the limited object detail available.

What Can Be Monitored

  • DHCP address pool utilization
  • lease allocation/expiration
  • DHCP request/offer/ack/nak statistics
Imported Objects

From RFC1155-SMI

TimeTicks
enterprises

From RFC1213-MIB

DisplayString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

DateAndTime
RowStatus
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using dhcpServBootpCountRequests OID:

Select a Lucent/Avaya IP Services access gateway/router (DHCP server) 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 dhcpServBootpCountRequests into the Find box to locate it in the OID tree, then select it and click OK. The number of packets received that contain a Message Type of 1 (BOOTREQUEST) in the first octet and do not contain option number 53 (DHCP Message Type) in the options. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Vendor-specific DHCP and BOOTP server MIB for managing IPv4 dynamic host configuration protocol implementation.

Start monitoring Lucent/Avaya IP Services access gateway/router (DHCP server) 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 DHCP-SERVER-MIB