Ok, forgot:

There is no Action in the Device "Action" Tab but there are actions on every singe Active Monitor.

William,

Can you post a screen capture of the critical monitor configuration on the device?

Hi Jason

Sorry, was not at work last day,
Here the Screenshots

The Sripts are JScripts using SNMP gets to calulate Diskspace

Thanks
Willem

Willem,

Can you post a screenshot of how you have your ping critical monitor configured?

Here you go..

What does the machine look like when the ping monitor goes down?  Can you set up a critical test monitor that will fail?  The icon should go gray with a small yellow square when a single critical monitor fails.

If a non-critical Monitor is down, the Icon is green with a red star in the lower right corner,
I Changed a Device (not the one in question) with a Failing non-critical Monitor, so that the failing Monitor is Critical -> The device changes to Gray with a red star at the lower right corner. so far so good.

The Explanation for Critalcal Monitors is:
The polling of serverXY's non-critical monitors depends on the 'Up' state of each its critical monitors (Ping). If any one of the critical monitors go 'Down', polling will not continue.

The Failing ServerXY has been shutdown at Apr. 18. @ 13:59.
the first Ping failed @ 13:59:51
From this time on, I expected the other Monitors to go in state Unknown.

For me, there is one thing not clear. For me there are some states between UP (green) and realy DOWN (red).
Whats meens :If any one of the critical monitors go 'Down', polling will not continue.
1. Polling will not continue after ping went red - or -
2. Polling will not continue after ping went yellow?

Thanks
Willem

I am playing around with mine, to see how it behaves.  In the mean time, when was the last time you restarted your SQL service?

about 2  weeks ago

I was not able to replicate the issue.  When my test critical monitor goes down my polling stops.  Even with an action policy attached directly to another down monitor it still was not reporting.  If you can, try restarting your SQL server.  This might help to get everything back in line.

Hi Bryan,
I treid to reproduce the problem by changeing the IP address of the Monitored Device (in WuG).
That way, the dependencies worked fine (This device is in producktion, so I can't shut it down).
So  I treid an other device. Shotdown the Device -> Seems to work fine!
I'll keep an Eye on it

Thanks
Willem

I've had this problem for quite some time now. WUG support has told me on two occasions that there is a bug that causes this problem. I've been told it won't be fixed in v15 but will be fixed in v16.

For me, the problem happens often but not all the time.

Hi Willem,

Same issue here.
I was told by the support that there is a bug in the system whereby you have many  monitors of a similar type, WuG tends to miss the monitor that is set as critical and sends out staus of all active monitors that are configured when the server is rebooted or is down for any reason.
haven't seen a fix for this to date.
Hopefull v16 has something better to offer.

Hey All,

I have this issue aswell, I have almost 700 devices and when PING goes down I have a large number of SNMP down messages...its very annoying.

Has anyone found a way to fix this ? or do we wait till v16 ?

Cheers

@Jon:
I've made a custom script in this thread that does the same thing, but it disables all monitors except ping untill ping responds again:
http://community.whatsupgold.com/forums/whatsupgoldeditionsstandardandpremiumeditions/wug-v15-active-scripts

It might be what your after :)

//Robin

 

I had this 'issue' until I realized that the critical monitors were not setup properly. Not sure why it seems to work for some and not others. I'm using v15.0.1 -- how about the people who say it's not working for them?