DHCP-SERVER-MIB :: dhcpServBootpCountRequests

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDHCP-SERVER-MIBdhcpServBootpCountRequests

dhcpServBootpCountRequests

Module: DHCP-SERVER-MIB

OID (symbolic): DHCP-SERVER-MIB::dhcpServBootpCountRequests

OID (numeric): 1.3.6.1.4.1.1751.1.48.1.1.1.1.3.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

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

What is dhcpServBootpCountRequests?

Running total of BOOTREQUEST packets received that are plain BOOTP (i.e. lack DHCP's option 53 message-type field). This helps an admin gauge how much legacy BOOTP client traffic, versus DHCP traffic, the server is still handling.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.1.48.1.1.1.1.3.1
snmpwalk -v2c -c public <target> DHCP-SERVER-MIB::dhcpServBootpCountRequests

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.1.48.1.1.1.1.3.1.1
snmpget -v2c -c public <target> DHCP-SERVER-MIB::dhcpServBootpCountRequests.1

SNMPv3 example:

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

Start monitoring Lucent/Avaya IP Services access gateway/router (DHCP server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DHCP-SERVER-MIB::dhcpServBootpCountRequests OID value, configure state conditions and alerts, and monitor any Lucent/Avaya IP Services access gateway/router (DHCP server) from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (8 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.1751lucentACMIB
1.3.6.1.4.1.1751.1productsAGGREGATED-EXT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1751.1.48ipspgDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1ipspgServicesDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1ipspgDHCPDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1.1dhcpServMibDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1.1.1dhcpServMibObjectsDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1.1.1.3dhcpServBootpCountersDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1.1.1.3.1dhcpServBootpCountRequestsDHCP-SERVER-MIB