DHCP-SERVER-MIB :: dhcpServBootpStatSumResponseTime

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDHCP-SERVER-MIBdhcpServBootpStatSumResponseTime

dhcpServBootpStatSumResponseTime

Module: DHCP-SERVER-MIB

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

OID (numeric): 1.3.6.1.4.1.1751.1.48.1.1.1.1.5.6

Node type: OBJECT-TYPE

Type: DhcpServTimeInterval

Access: read-only

Description: The sum of the response time intervals in milli-seconds where a response time interval is measured as the difference between the arrival of a BOOTP message at the server and the successful transmission of the response to that message. A message is received at the server when the server is able to begin processing the message. A message is transmitted after the server has no further use for the message. Note that the operating system may still have the message queued internally. The operating system queue time is not to be considered as part of the response time. Invalid messages do not cause this value to change. If no valid messages have been received, then this object contains a zero value.

What is dhcpServBootpStatSumResponseTime?

The cumulative total, in milliseconds, of every BOOTP response time recorded by the server. Dividing this by the request count gives the average BOOTP response latency, which admins can trend over time to catch gradual performance degradation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.1.48.1.1.1.1.5.6
snmpwalk -v2c -c public <target> DHCP-SERVER-MIB::dhcpServBootpStatSumResponseTime

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.1.48.1.1.1.1.5.6.1
snmpget -v2c -c public <target> DHCP-SERVER-MIB::dhcpServBootpStatSumResponseTime.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::dhcpServBootpStatSumResponseTime OID value, configure state conditions and alerts, and monitor any Lucent/Avaya IP Services access gateway/router (DHCP server) from a single console.

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.5dhcpServBootpStatisticsDHCP-SERVER-MIB
1.3.6.1.4.1.1751.1.48.1.1.1.1.5.6dhcpServBootpStatSumResponseTimeDHCP-SERVER-MIB