Windows DHCP Server Sensor
Monitors a Windows DHCP Server and its scopes, tracking address pool usage and lease health, and alerting before a scope runs out of addresses.
Node SettingsMonitoringAdd Monitoring Sensor
The sensor monitors the status of the DHCP Server and its scopes. It collects scope statistics — available addresses, percentage of addresses in use — along with general server health indicators.
Two situations account for most DHCP incidents, and the sensor alerts on both by default:
- A scope is running low on free addresses, and is heading for exhaustion
- A lease has been marked Declined, which indicates a probable IP address conflict
This sensor monitors a DHCP server through WMI. It is not the same as the DHCP network service check, which verifies that a server answers a DHCP inform request from the NetCrunch machine. See Network Services Monitoring for that check and its restrictions.
Options
You can configure Windows credentials to access the DHCP server data.
Access to the WMI namespace root\Microsoft\Windows\DHCP is required.
Alerts:
- Low Available Addresses in DHCP Scope
- DHCP scope exhaustion risk
- Possible IP Address Conflict
- Alert on Monitoring Sensor counter
Sensor Views
- DHCP Server Scopes
- Displays all defined IPv4 and IPv6 scopes, their IP ranges, and usage levels.
- DHCP Server Leases
- Lists all current leases, including reservation status and expiration time. You can modify reservations or delete leases directly from this view.
- DHCP Server MAC Filtering
- Shows allowed and denied MAC addresses. You can remove entries as needed.
Performance Metrics:
Scope usage is counted per scope, with one instance per scope:
- Windows DHCP Server.IPv4 Scope | % Available Addresses
- Windows DHCP Server.IPv6 Scope | % Available Addresses
The default alerts are thresholds on these two — a warning as a scope runs low, and a critical as it approaches exhaustion. Both IPv4 and IPv6 scopes are covered separately.