Nagios causes 3750 stack to fail
Posted: Tue May 27, 2014 1:42 pm
Hello,
I am working with a Nagios system that was setup by another tech who is no longer with the company. after we changed our core switch from a stack of 3750G's to a stack of 3750X's every time we connect the Nagios to the network the core switch starts to perform irregular. one of the routers connected to the core losses communication (cisco 1800, unable to ping in or out), and our cisco wireless controller has the same issue. all other devices seem to act normally but performance seems to be slightly compromised. after disconnecting the Nagios box the router comes back but the issues with performance and the wireless controller remain.
we did realize that nagios was configured to monitor the old stack which has the same IP as the new stack so nagios was reaching out to the stack. we have found that restarting the stack resolves the issues until nagios is reconnected. several debugs on the stack show no errors.
so my question is this:
What could Nagios be doing to the stack to cause this behavior?
thanks for any help you can give.
I am working with a Nagios system that was setup by another tech who is no longer with the company. after we changed our core switch from a stack of 3750G's to a stack of 3750X's every time we connect the Nagios to the network the core switch starts to perform irregular. one of the routers connected to the core losses communication (cisco 1800, unable to ping in or out), and our cisco wireless controller has the same issue. all other devices seem to act normally but performance seems to be slightly compromised. after disconnecting the Nagios box the router comes back but the issues with performance and the wireless controller remain.
we did realize that nagios was configured to monitor the old stack which has the same IP as the new stack so nagios was reaching out to the stack. we have found that restarting the stack resolves the issues until nagios is reconnected. several debugs on the stack show no errors.
so my question is this:
What could Nagios be doing to the stack to cause this behavior?
thanks for any help you can give.