check_dhcp_scopes

Project Notes

DESCRIPTION - This script was designed to be called by the NSClient installed on a Windows DHCP Server. It will return "Critical" if any of the DHCP scopes (or a specified DHCP scope) is above the critical threshold, "Warning" if above the warning threshhold, or "OK" if below the warning threshold. It can also run standalone with or without parameters for informational purposes.

PARAMETER scopeID (-s)
Optional - define a single scope in the format of the subnet ID, or all scopes by using "all"
Default: all
Example: 192.168.0.0
Example: all
PARAMETER warn (-w)
Optional - Percentaged of scope IPs used before returning a warning
Default: 90
PARAMETER crit (-c)
Optional - Percentage of scope IPs used before returning a critical
Default: 98
EXAMPLE
If using standalone:
>.check_dhcp_scope.ps1
This will evaluate all DHCP scopes and return a warning or critical if any of the scopes are above 90% or 98% full.

>.check_dhcp_scope.ps1 -all -w 50 -c 80
This will evaluate all DHCP scopes and return a warning or critical if any of the scopes are above 50% or 80% full.

>.check_dhcp_scope.ps1 -s 192.168.0.0
This will evaluate the 192.168.0.0 scope and return a warning or critical if is above 90% or 98% full.

>.check_dhcp_scope.ps1 -s 192.168.0.0 -w 50 -c 80
This will evaluate the 192.168.0.0 scope and return a warning or critical if is above 50% or 80% full.
If using with NRPE:
It is recommended you pass in all three arguments, even though they are optional. I have 2 checks on each DHCP server. One that checks all, and one that check a specific subnet.
NOTES
NAME: check_dhcp_scopes.ps1
AUTHOR: Rich Johnson
DATE: 2016-07-07
EMAIL: [email protected]
REQUIREMENTS:
- NSCLient++ isntalled, functioning, and correctly communicating with your monitoring server on the DHCP server to be checked
- DHCP Server role installed and functioning with at least one active and working scope
Change Log:
2016-07-07 - Initial creation