[SOLVED] devices not responding to snmp after server crash

sveno · Post by **sveno** » Wed Oct 22, 2008 3:12 am

Hi,

A really wacky thing happened. I managed to hang the cacti server with Wireshark. After the restart a couple of devices won't reply to SNMP at all, others work fine. Tried also with Paessler SNMP Tester running on the same server, no reply from device. The devices respond to ping and other servers are a able to poll them via SNMP just fine.
I'm using:
Cacti 0.8.7b
Windows server 2k3
Cacti SNMP is net-snmp

I am completely clueless. Please help.

Post by **TheWitness** » Wed Oct 22, 2008 5:57 am

They are Windows servers? Are they a member of a Domain? Has the Domain Admin changed the state of the SNMP Service? Has someone changed the SNMP Community, put an ACL in place? Maybe SNMP Service crashed, maybe it was set to start in Manual mode.

TheWitness

sveno · Post by **sveno** » Wed Oct 22, 2008 8:53 am

The machine is not part of a domain.
I believe SNMP is working on the cacti server because other 46 routers polling and graphing is ok.
Routers communities have not changed and they don't have ACL on. This is verifiable because SNMP polling from lets say, my laptop, is fine.
There are no firewalls between, one switch that is not replying to the servers SNMP packets is directly connected to it!

Thanks for your time TheWitness!

BSOD2600 · Post by **BSOD2600** » Wed Oct 22, 2008 1:53 pm

So a the problem devices are routers... and suddenly they don't respond to SNMP after your cacti server crashed? Odd. If a secondary SNMP testing tool (like net-snmp or Paessler SNMP Tester), then it would sound like there is something wrong with the device(s) which you're trying to poll. Maybe the server got a new IP which isn't in a firewall/router config for allowed SNMP?

Anyways, doesn't sound like it's an issue with Cacti.

sveno · Post by **sveno** » Mon Oct 27, 2008 7:02 am

You are right: unlikely that this would be a problem with cacti, however I googled my ass off and you guys were my last hope!

Anywho.. I figured it had something to do with the NICs. As soon as I removed the IP from the second NIC (for Wireshark packet capture) everything went back online. Shouldn't be like that. It did not have a gateway, it didn't have priority in the routing table. And it worked for 2 years. Odd. But then again we are talking about windows

Thank you everyone, appreciate it!

[SOLVED] devices not responding to snmp after server crash

[SOLVED] devices not responding to snmp after server crash

Who is online