question about EVENTS

Question

can someone explain to me the importance of these events (Volume Index)? especially when i see their values either go higher or go lower like these examples shown below.

what should i be concerned about when i see these?

thanks.

Virtual Memory- Volume Index changed from 5 to 6

Physical Memory- Volume Index changed from 7 to 8

Virtual Memory- Volume Index changed from 7 to 5

ecklerwr1 · Answer

with the massive netapp storage I have I'm getting literally thousands of these Volume Index Changed messages all day long...  this really causes information overflow in the events list masking other information you might want to see... trying to decide how to deal with this:

1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 431 to 429    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 430 to 428    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 429 to 427    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 428 to 426    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 427 to 425    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 426 to 424    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 425 to 423    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 423 to 421    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 422 to 420    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 421 to 419    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 420 to 418    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 397 to 395    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 396 to 394    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 419 to 417    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 418 to 416    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 417 to 415    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 416 to 414    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 415 to 413    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 410 to 408    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 409 to 407    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 387 to 385    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 386 to 384    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 385 to 383    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 384 to 382    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 383 to 381    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 382 to 380    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 381 to 379    1/10/2013 10:20 AM  servername-/vobstore/****- Volume index changed from 380 to 378

Note servername and volume names have been removed.  This is such a small sample of how much this happens all day long and fills the database which it's handling but geesh this is insane!!!

See   I created a new question for this topic.

Akeap · Answer

Would this mean then that the server is perhaps part of a cluster and when it fails over orion recognises that new volumes are now assigned to this server?

But I see these types of messages up to 4/5 times a day and I know the cluster is not failing over.....

Anyone have any other ideas?

tdanner · Answer

The index for volumes and interfaces is just an snmp bookkeeping detail. It might mean that a volume was added or removed from the device, or it might mean nothing.