TPLINK-DHCPSERVER-MIB :: tpDhcpServerStatisticsBootRequest

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTPLINK-DHCPSERVER-MIBtpDhcpServerStatisticsBootRequest

tpDhcpServerStatisticsBootRequest

Module: TPLINK-DHCPSERVER-MIB

OID (symbolic): TPLINK-DHCPSERVER-MIB::tpDhcpServerStatisticsBootRequest

OID (numeric): 1.3.6.1.4.1.11863.6.38.1.9.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Displays the Bootp Request packets received.

What is tpDhcpServerStatisticsBootRequest?

This read-only Counter64 tallies the number of Bootp Request packets the DHCP server has received. An operator monitors this alongside the other statistics counters to gauge overall DHCP request volume on the switch.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11863.6.38.1.9.1
snmpwalk -v2c -c public <target> TPLINK-DHCPSERVER-MIB::tpDhcpServerStatisticsBootRequest

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11863.6.38.1.9.1.1
snmpget -v2c -c public <target> TPLINK-DHCPSERVER-MIB::tpDhcpServerStatisticsBootRequest.1

Start monitoring TP-Link managed switches (built-in DHCP server enable/address-pool status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TPLINK-DHCPSERVER-MIB::tpDhcpServerStatisticsBootRequest OID value, configure state conditions and alerts, and monitor any TP-Link managed switches (built-in DHCP server enable/address-pool status) from a single console.

How to Use in IPNetwork Monitor

Select a TP-Link managed switch (built-in DHCP server enable/address-pool 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 tpDhcpServerStatisticsBootRequest into the Find box to locate it in the OID tree, then select it and click OK. Displays the Bootp Request packets received. 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 Counter64-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.11863tplinkTPLINK-MIB
1.3.6.1.4.1.11863.6tplinkMgmtTPLINK-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11863.6.38tplinkDhcpServerMIBTPLINK-DHCPSERVER-MIB
1.3.6.1.4.1.11863.6.38.1tplinkDhcpServerMIBObjectsTPLINK-DHCPSERVER-MIB
1.3.6.1.4.1.11863.6.38.1.9tpDhcpServerStatisticsTPLINK-DHCPSERVER-MIB
1.3.6.1.4.1.11863.6.38.1.9.1tpDhcpServerStatisticsBootRequestTPLINK-DHCPSERVER-MIB