SNMP Status Polling

[Ayman Altounji]

Okay, since this thread seems to have been forgotten, I am re-posting it, hopefully to get some sort of an answer.

Brent

How can I receive detailed information when I receive alerts from the SNMP Status Polling task? Also, where can I get detailed info on how the SNMP Status Polling task works? I receive Critical, Major, Minor, and Normal alerts that all reference SNMP Status Polling but do not specifically say what was found.



post a reply

1. Reply From: Bingler
August 27,2002 5:10pm Rate this reply:




No offense, but I'm really glad to see that someone else is having the same problem that I am. Please, if you get a response to this, somewhere other than in this forum, email me at bingler@amgen.com. If you send me your email address, I'll do the same.
Brent


2. Reply From: curran
August 29,2002 2:00pm Rate this reply:




same problem here .Let me know if anyone figures it out.

3. Reply From: emerson1
August 30,2002 4:19am Rate this reply:




same problem for me... is there any way to get help from Compaq support. I have sent them email asking diff. problem but no reply.

4. Reply From: Bingler
August 30,2002 10:36am Rate this reply:




The "easiest" way is through the fee-based support, which is stupid. There's no guarantee that they will solve your problem, and they'll most likely charge you either way.
Brent


5. Reply From: Darrin R
September 4,2002 11:23am Rate this reply:




The way the Status Polling works is that periodically (by default every 5 minutes against servers), IM7 polls the servers and talks to the agents and says "what's your aggregated status". If you have had a hard drive failure in a RAID for instance, the status will be major. That's all the information IM7 gets from the agents. When the hard drive failed, an event should have been sent to the IM7 server to notify you of the failure. If you had a Notification Task (email/page) setup to notify against all "Critical Events' or something, then you would also get an email or page.
In IM7, we added a flag (when you create a Status Polling task) to create an event called "Status Change Event". That was added so that you can create an EVENT QUERY based on Events by Type (Status Change Event in System folder) and severity of CRITICAL, you will get notified when a particular server goes Critical - i.e. the server is no longer on the network (no ping response). The other severities are there for notification too - i.e. if you don't want to see all the traps forwarded, you can set up a notification task to notify you when a server goes MINOR, MAJOR, or CRITICAL and then you can log into IM7 to see the individual events that have been received or drill down to the agents.

Does that help?


6. Reply From: Bingler
September 4,2002 1:56pm Rate this reply:




Not really, Darrin. I think we all pretty much understand what they do. The problem is that the events give us no details. If I get a page at 2am, I would much rather get some detailed information before I either dial in to work, or drive into work, so that I can determine, for myself, the actual severity of the problem. Currently the SNMP status polling task doesn't do this. What we want is a way to either get more information out of the status messages (i.e. WHY the status is what it is) or a way to customize the messages so that we can give ourselves this information.
Now, if the polling task isn't even capable of handling this, what is? How can we get detailed information as to why a machine is critical, or more specifically why a RIBLOE is in a Minor or Major state, without having to connect to CIM to check it out? And, FYI, when connecting to CIM to figure out why a RIBLOE, for example, is in a major