SNMP v WMI - Drive Space Monitoring/Alerting

This maybe a dumb question that somehow I overlooked. I have a Group of servers that all are set to WMI for monitoring and I have a disk alert to send out an email if it goes over 80%. One of these servers is using SNMP and I need to use SNMP for it to monitor an application on it which works fine. The problem is with SNMP the node is not getting its drive monitored - the problem is I can't flip the node to WMI because then the Application will stop monitoring because it is SNMP. I tried setting up a new custom SAM module but it won't work I am stuck on SNMP. What am I missing here? And if there are some reading materials around this that would be great as well. Thanks -Dave (and sorry if this sounds like such a basic question that I should know the answer to)

Find more posts tagged with

drive alerts

WMI

Alerting

snmp polling

Accepted answers

dodo123

do you have a screenshot of the alert trigger page so we can investigate maybe something overlooked.

Bit like when someone looks over your shoulder and points out the obvious mistake

All comments

vinay.by

Do you have additional pollers in your environment? If you do, you could go ahead and add this node again on a different poller as a WMI node (its just a work around) hope it helps.

But if you have a single main poller the above statement will not hold good.

aLTeReGo

It sounds like your application's SNMP Daemon has taken over UDP port 161 from the SNMP Daemon included with the operating system. In this case, you need to move one of them to an alternative port. Next, I would add the 'node' using whatever port the SNMP daemon provided by the operating system is using. Then I would configure a SAM SNMP Component Monitor to monitor the appropriate OIDs on the application's SNMP daemon by specifying the port number that application's SNMP daemon is running on.

martian_monster

So why is it not monitoring the hard drive volumes? When I ran a test of the alert none of the drives would show up as needing an alert. This is a bit of an issue because the drive ran out of space and no one was alerted.

martian_monster

Yeah we just have one poller right now.

martian_monster

To get around this I created an alert for just this server to monitor the drive space and it works. Not sure why it would not work with the rest of the servers in the group but I think it has something to do with WMI v SNMP.

aLTeReGo

If my assumption is correct, the application's SNMP Damon is unaware of the operating system and does not support the HOST-RESOURCES-MIB.

martian_monster

And the other part of my problem is I should have stated the OS - I doubt this MIB is included in Server 2003.

dodo123

do you have a screenshot of the alert trigger page so we can investigate maybe something overlooked.

Bit like when someone looks over your shoulder and points out the obvious mistake

martian_monster

And because of your post I figured out the problem - Node Starts With - and the node does not start with that but it contains the 3rd line. I bet the Node Name Starts with is the problem. Thanks dodo123 for looking over my shoulder!!

dodo123

No problem the wife does it to me all the time.

all I would suggest is try using the box above your screenshot so the static stuff like node name starts with. Then have the actual trigger like hit 80 that way it will be easier to notice the mistakes