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

Volume Polling and Statistics Collection

Hello,

I have a Linux server with some (not all) volumes that Orion NPM (9.5.0) is no longer polling or collecting statistics. The screenshot shows the last time one of the volumes was polled/collected.

How can I get Orion to resume polling & statistics collection for the volumes in question without deleting and then re-adding them? I can't delete them because I need to keep the historical data.

Restarting SNMP doesn't help.

Thanks,
John

volume-polling-details.PNG

Find more posts tagged with

Accepted answers

All comments

smargh

NPM does this on Windows whenever the label of the volume is changed on the server itself. Perhaps it's the same on Linux in that the SNMP OIDs of the volume change after it's named or otherwise altered in some way?

I opened a ticket for this with Support a week or two ago - they confirmed that there's no workaround except removing & re-adding. It's a feature of Windows & changing OIDs which apparently cannot be worked around, which I personally find a little defeatist but never mind. I can imagine a background job where the logic is something like "if volume status is 'unknown' and node status is 'up', re-scan & if the same volume drive letter [or linux mount point] is found, then update the oid & label"

FormerMember

Thanks. This issue appears to be a bug in NPM 9.5.0. I rebooted our Orion server, and it started polling and collecting again.

I posted a question in the Alerts section asking if there is a way to send an email when Orion stops polling or collecting on a volume. If anyone has any insight into configuring this, please let me know.

Thanks,
John

FormerMember

"I opened a ticket for this with Support a week or two ago - they confirmed that there's no workaround except removing & re-adding. It's a feature of Windows & changing OIDs which apparently cannot be worked around, which I personally find a little defeatist but never mind."

I agree. I've worked with many SNMP based monitoring systems, and so far, Orion NPM is the only one that cannot handle these types of changes.

I will open a support ticket for this too. In my opinion, this is a bug because a reboot resolved the issue for me.

It would be good to know if NPM v10 behaves the same way.

Thanks,
John