nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
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

Volume Index Changes, then monitoring of the volume stops.

veryloudguitar

I Have a number od disk volumes being monitord on a particular win2k3 server. Sometimes i get a error logged that the volume index has changed from 6 to 7, then later on back from 7 to 6.

The problem is that once this happens, graphing of that volume's usage stops, there are gaps in the data. The only way to get it working again is to reboot the Orion server.

This error seems to coincide with creating a snapshot of a volume.. But a snapshot operation shouldnt change the volume index should it? If orion knows that the index has changed - why does it stop monitoring?

Is this a bug with orion, or is there a better way to monitor disk usage on a system?

Find more posts tagged with

volume_monitoring

Accepted answers

All comments

FormerMember

I would say that usually the only time i see index numbers change on servers is when the cluster servers swap over.

Is your setup a clustered server?

veryloudguitar

The volume is a polyserve clustered filesystem across three nodes.

But P.S. is active/active; so no swapping of volumes. all nodes have access all the time.

The cluster does pause the filesystem while the snap takes place (about 5s) - maybe if polling happens at the same time, the index is different?

Any ideas on why orion wouldn't simply resume graphing once the index returns to normal?

FormerMember

dont know if these are windows boxes but do you monitor the MS TCP loopback on the servers?

if so do they go into an unknown state when you loose the volume?

veryloudguitar

they are windows 2003 std servers, i'm not monitoring loopback. but i dont seem to loose connectivity to any other process or interface. i'm monitoring 3 network interfaces, mem & cpu and a backupexec service with app monitor, these have no problems....

FormerMember

try monitoring the loopback and see if it goes unknown when your volumes stop.

If this is the case then you would be falling prey to the same issue that many others of us are dealing with in that interfaces/volumes go unknow state for no reason and we have all developed a bandaid to get past it and continue monitoring. A few of us have put in tickets on this issue and we have not got a reason behind it as of yet.

you can take a look at this other thread and see basically all SNMP is stopping for some reason.