Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Windows 2012 DHCP Failover and Scope Health Check
Current Version
1.1
Last Release Date
2014-06-11
Compatible With
- Nagios 3.x
- Nagios 4.x
- Nagios XI
Owner
Website
License
GPL
Hits
25357
Files:
| File | Description |
|---|---|
| check_failover_dhcp.ps1 | check_failover_dhcp.ps1 |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Monitoring for Windows Server 2012 DHCP Failover architecture. Supports LoadBalance and Failover modes.
Monitors:
- Failover State
- Failover Mode
- Scope State of Each Scope
- Scope Statistics (PercentInUse) of Each Scope
This check was built with the expectation that all aspects of a DHCP service should be healthy, and reports accordingly. The script maintains only the most severe exit code as it runs, and exits with that value once all checks have been completed.
It should be noted that each portion of this script can easily be broken out into it's own check if desired.
Requirements:
Windows Server 2012 With DHCP Installed
NSClient++
Implementation:
- Implement as with any other NRPE check with NSClient++.
- There are no real arguments to pass, but the check_command requires one to function.
define service {
...
check_command check_nrpe!check_failover_dhcp!foo
}
Hopefully this check helps others who are also implementing the Failover architecture introduced with Windows Server 2012.
Suggestions welcome. Please leave a comment.
Monitors:
- Failover State
- Failover Mode
- Scope State of Each Scope
- Scope Statistics (PercentInUse) of Each Scope
This check was built with the expectation that all aspects of a DHCP service should be healthy, and reports accordingly. The script maintains only the most severe exit code as it runs, and exits with that value once all checks have been completed.
It should be noted that each portion of this script can easily be broken out into it's own check if desired.
Requirements:
Windows Server 2012 With DHCP Installed
NSClient++
Implementation:
- Implement as with any other NRPE check with NSClient++.
- There are no real arguments to pass, but the check_command requires one to function.
define service {
...
check_command check_nrpe!check_failover_dhcp!foo
}
Hopefully this check helps others who are also implementing the Failover architecture introduced with Windows Server 2012.
Suggestions welcome. Please leave a comment.
Reviews (0)
Be the first to review this listing!
