SNMPTrapping

[Billy Barule]

We use a utility (ipMonitor) that traps events via SNMP for various purposes. One of the items I have been looking to use is for checking the SMART Status of a physical hard drive. The OID is 1.3.6.1.4.1.232.3.2.5.1.1.6.0.145. The last two integers of this OID define the physical drive itself.

What I would like to do is establish one monitor that traps events for all drives on a system coming from this "area" (1.3.6.1.4.1.232.3.2.5.1.1.6) that may encounter problems, rather than defining individual monitors for each physical drive, as new drives would create more labor to create the monitor, and various systems having more or fewer hard drives would create tons of work. I'm probably looking at 150-200 physical drives right now.
Any ideas, or am I stuck?
Thanks.

[David Claypool]

That totally depends on features of IPmonitor. If you were using HP SIM (a free tool for ProLiant management) it would be a simple action on events triggered by physical drive status change.

[Billy Barule]

Thanks for the sales pitch on HP products. The product I use shouldn't be an issue - this is SNMP we're talking about.
I am looking to answer the following question: Is it possible to trap events for these physical hard drives at the higher level 1.3.6.1.4.1.232.3.2.5.1.1.6?

[RaMpaNTe]

As the other guy said, SIM is the best option for this purpose. I'm not tryin to sell anything, just trying to make your work easier and that's what SIM does. Besides SIM can be downloaded for free from HP.com

[Billy Barule]

I've worked with SIM in older iterations. What ipMonitor does is basically the same concept. Again, if I have to trap on every physical drive, so be it, but I wanted to float the SNMP-centric question here first, before creating all of these monitors.
Thanks.