DHCP scope monitoring

[talorin]

Hello,

We have quite a few DHCP servers and scopes out within our environment and, in trying to get Nagios working properly with everything, we're seeing some oddness with how we're testing it. We're using the standard check_dhcp within Nagios and have IP helpers set on our VLANs so that we can emulate client broadcasts. It seems that if Nagios has to wait for more than a few seconds (say a down server, etc.), that check will block others and we'll get multiple false negatives. Any thoughts on how best to manage large number of scopes?

[slansing]

It seems that if Nagios has to wait for more than a few seconds (say a down server, etc.), that check will block others and we'll get multiple false negatives. Any thoughts on how best to manage large number of scopes?

This is a bit confusing, what is occurring when the service goes into a critical state, and what is the service status message accompanying that state?

[talorin]

Hello,

When we see the oddness, the results of the script come back saying 'Return code of 98 is out of bounds'. Looking at the DHCP return codes, it looks like it's saying the IP address is already in use. When we run the same script against the same pool and server, it comes back fine. It's not an issue with the pool being full either as we're seeing it on pools of various levels of activity.

[abrist]

What is the full command for the dhcp check? Can you run it multiple times from the cli? I would like to see it fail and work from the cli.