I mean look at this:

Event Summary

Event Type      10423 Volume Remapped

Event Type      246      Volume Added

Event Type      55        Volume Disappeared

Event Type      55        Volume Reappeared

Event Type      52        Node Rebooted

Event Type      42        Node Down

Event Type      42        Node Up

Event Type      38        SAM Hardware Sensor Up

Event Type      25        Node Changed

Event Type      23        Polling Method Changed

Event Type      16        Group Members Changed

Event Type      15        Volume Removed

Event Type      9          SAM Hardware Type Up

Event Type      4          Interface Changed

Event Type      2          Group Warning

Event Type      2          Group Up

Event Type      1          Interface Added

Event Type      1          NetFlow Event

Event Type      1          SAM Hardware Undefined

Event Type      1          SAM Hardware Up

Someone has to have seen this b4 :^}

This is a see the forest for the trees kinda problem... or however that saying goes.

open a case with NetApp on their SNMP support

They should try and generate a stable index in the MIB for their volumes. The number they generate doesn't need to be sequential but they should  make it stable over time. Note: The current behavior will break almost anything that uses table index values to monitor statistics on the volume.

/RjL

Thanks Richard so much for response... I can't believe I'm the only one here with NPM and large NetApp NAS's they are trying to monitor.  Here's just one server with mounted netapp storage's event summary... this is INSANE!

Event Summary

	11305	Volume Remapped
	10	Volume Disappeared
	9	Volume Reappeared

Am I really the only one with large NetApp volumes being mapped to servers?????

This is for ONE server above.  Check out my event summary in general today:

Event Summary

	18329	Volume Remapped
	57	Volume Reappeared
	56	Volume Disappeared
	3	Interface Changed
	2	Group Warning
	2	Group Up
	2	Node Changed
	1	Node Up
	1	Node Rebooted
	1	NetFlow Event

For now my solution is to change EventTypes.Record flag from 1 to 0 for Volume Changed in the database.

I changed the flag for recording all three event types now in the database for volume remapped, volume reappeared, and volume disappeared.  Not ideal but all I can do right now until something changes with agent or the way NPM handles them.  I'm using my UnDP for netapps and custom alerts so I can monitor my NetApps without relying on this flood of events or letting them clog my event stream.  Now as long as I don't miss other non-NetApp volumes having problems since I'm effectively not recording any of these events any longer...