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
Store

Hard drives not being polled on only one server

I opened a ticket with support, but they don't seem to understand. They're in a hurry to close the ticket, so they keep telling me that "when the issue comes up again please re-open the case, not much we can do when the issue isn't happening." Ugh, SolarWinds support is very poor sometimes.

Anywho, I have one server not reporting fixed disk usage unless I poll it manually. The polling interval is set to 120 seconds on these drives, but no data is being reported for weeks at a time. The only suggestion I got is to do a repair, but that NEVER has fixed ANYTHING with Orion. Not to mention, if it were an issue with the collector or any other aspect of Orion...other devices would be affected, not just one. The server is a Windows 2008 R2 server, and we have TONS of other boxes just like this one across the WAN that don't have this issue. How do I fix this to have this server report data automatically? No other devices are having this issue, and other resources on this server are reporting normally.

Find more posts tagged with

Accepted answers

All comments

Apollo

I've noticed this on a few of our systems from time to time. My solution was to remove it from NPM then re-add it. I don't recall losing any historical information doing it this way. Simply trying the SNMP strings didn't work - never pulled automatically. As a result I've been spot checking servers frequently. My issue has been with 2008R2 boxes as well.

As far as your support experience - I've had the same issues lately. The support person was more interested in closing the ticket than helping with the issue at hand. I've run across this more often than not and have resolved to this forum or their online tools. I'm working on an alerting issue that I've gotten conflicting info on from tech support so I'm struggling thought it on my own.

ahthomas

Yeah, I dunno what's with their support lately. But it's pretty bad...

So if I remove and re-add the server, won't I lose all of my historical data?

Apollo

I don't think so. I can give it a try on my end to double check and let you know?

ahthomas

That'd be helpful, thanks!

Apollo

Yup...I did lose all historical data. I just tired it.

ahthomas

Well they're looking at diags now, so hopefully I won't get some other nonsense reply back. Why would only one device be having this problem? With 11,000 elements I'm at 52% polling engine capacity (I've throttled back my poll intervals on most devices).

Apollo

My only guess is that 2008R2 has a bug in the snmp reporter. When I've noticed the problem, Orion never showed that the server was offline and did keep historical up time going, etc. Perhaps the drive information is a subset of the MIB and gets generated as null information...don't really know. Its annoying especially when you're counting on drive space alerts which we do.

smargh

Either are you renaming the volume yourself, or is the volume ID changing? i.e. perhaps it's an iscsi volume etc?

Try renaming a volume & see if Orion continues monitoring it. See my other posts for rants on that particular issue.

Alternatively, look directly at the info returned by SNMP over time to see if the volume description changes. Maybe it is actually an OS-based root cause in your case.

Apollo

Neither in my case. We've looked into that as well. We're not renaming volumes and the iSCSI volume names do not change.

tabouda

Hi everyone,

I am running inti the same exact issue.

Has anyone found the solution to it?

adatole

A few (probably dumb) questions on this:

You say the polling interval is 120 seconds, but that's the default for ping (even though it says "polling", that is what SolarWinds calls pign). What is the statistic collection interval for disks - both in general and on that box specifically?
Is there anything about this disk that is special?
What's the OS? If it's Windows, can you confirm that the SNMP agent is configured correctly (ie: all the boxes are checked on the Agent tab, etc)
Finally, how loaded up is your poller? If it's overloaded, the newer versions of Orion (10.2 and later, IIRC) will automatically adjust polling intervals.

Again, most of those are dumb ideas, but I'm starting from the basics just to make sure we don't overlook anything.

- Leon