Configuration Discrepancies
Posted: Wed Jul 30, 2014 6:53 am
I'm struggling to get our Nagios system to apply config changes & it appears to be hanging on to servers which have been removed...
For example, I deleted several switches from the Nagios config via the XI GUI and they're no longer searchable in the CCM, but they still show up in the running system, mostly going critical/down because we moved them to internal IP ranges and nagios can no longer see them.
There's also a server which I deleted & remains doggedly in the config but not manageable via the GUI. It's got 24 services all critical, so is very annoying to our out of hours guys, who keep seeing all the red and panicing.
How do I get around this sort of thing?
Due to another weird configuration verification error, I just checked the services in CCM and weirdly there's several of the same service, with no hosts assigned and I don't remember putting them there - we like to have a global service check, that's capable of being applied to a hostgroup or individual hosts, not a service for each host.
Looking at the CoreDNS_53 service there, that was what was causing my config verification to bork and I had to edit and save it, in order to get the config verification to finally go green, but that's when I started to poke around and found the multiple identical service checks shown above.
I am a bit worried that it's got itself (or been helped) into a mess that I don't know how to untangle. Currently, when I apply the config, it works (goes green and applies), but I still have the legacy hosts lingering. Any ideas?
For example, I deleted several switches from the Nagios config via the XI GUI and they're no longer searchable in the CCM, but they still show up in the running system, mostly going critical/down because we moved them to internal IP ranges and nagios can no longer see them.
There's also a server which I deleted & remains doggedly in the config but not manageable via the GUI. It's got 24 services all critical, so is very annoying to our out of hours guys, who keep seeing all the red and panicing.
How do I get around this sort of thing?
Due to another weird configuration verification error, I just checked the services in CCM and weirdly there's several of the same service, with no hosts assigned and I don't remember putting them there - we like to have a global service check, that's capable of being applied to a hostgroup or individual hosts, not a service for each host.
Looking at the CoreDNS_53 service there, that was what was causing my config verification to bork and I had to edit and save it, in order to get the config verification to finally go green, but that's when I started to poke around and found the multiple identical service checks shown above.
I am a bit worried that it's got itself (or been helped) into a mess that I don't know how to untangle. Currently, when I apply the config, it works (goes green and applies), but I still have the legacy hosts lingering. Any ideas?