Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Many nodes loose SNMP when..

With Orion v9.1.0 SLX, I monitor all kinds of nodes. Ciscos, Unix, Linux, Windows Servers (2000, 2003), UPS, AS400s, etc.. Some are in my LAN or my department's WAN and some (mostly Windows nodes) are in other LANs in the corporate MAN.

I have problems with some of those that are in other parts of the MAN. We recently had a DR test where we turn off some key interfaces on Cisco routers, to isolate the building being tested. By doing this, it also cuts my monitoring server from them. That's fine, it is expected. The problem is that when we restore connectivity, more than 75% of the nodes monitored in the MAN do not respond to Orino's SNMP requests. The SysAdmins have to "stop/start" the SNMP services on all the non-responsive nodes. But, there are some nodes that still work fine, even in the same subnet.

What could be causing SNMP to stop replying?

Find more posts tagged with

Accepted answers

All comments

netlogix

I have the same problem and I think it has to do with dns.

I have hostnames in the "Accespt SNMP packets from these hosts" for some nodes and those are the ones that tend to have the most issues like that for me.

Dominic

Thanks for adding to the thread!

The dns thing could be your problem but I don't see how the dns would affect this on my end as I only use ip addresses when adding a host in the "Accept SNMP packets..." field and, right now, on the servers with the problem, there isn't any ip in that field.

grantsewell

What type of message do you get, if any? Is it something like "Node is in an Unknown State"? Or is it just down?

Dominic

This is what I get. Pinging is still fine. When trying to "Validate SNMP" it just never works (unless there is a start/stop of the SNMP service on the server). Once that's done, Orion picks it up normally.

cnorborg

I had a similar problem with some unix boxes awhile back. Upgraded the SNMP daemon and the problem went away...

mhh351

Have you tried putting a scope on a span port to see what one of these servers is doing? Try putting Wireshark on a PC that is on a spanned port and see if Orion is sending an SNMP poll and/or the server replies.

If there is a reply, what is the update time for the web page? Also, check on the polling time that Orion cycles on. Also, if the device is a downline member of an alert group where device 1 is down therefore device 1.a will not even be looked at, is happening.

It might just be a matter of timing in Orion.

grantsewell

If there is a reply, what is the update time for the web page? Also, check on the polling time that Orion cycles on. Also, if the device is a downline member of an alert group where device 1 is down therefore device 1.a will not even be looked at, is happening.
It might just be a matter of timing in Orion.

There is no reply. It's as if something has overrun the buffer of the SNMP service and caused it to fail. It's possible it could be a timing issue in Orion, as most of my devices are high-latency, however that can't really be justified if they never come back and they don't respond to a local SNMP query ever.

Dominic

I've had no success with another SNMP poller but, I was able to find out that, all my Linux servers are still responding to SNMP queries but none of the Win2K3 servers are returning any SNMP data. I tested 4 different subnets and they all behave the same.

So, it looks like it might be Windows problems.. I'll concentrate on that with the sysadmins..