Hey guys, if the UP DEPENDENCIES are set within each map pointing to a single entry point into the map (router), then only one device (router) per map will show "down (Unfortunately, I have not yet been able to find a way to set UP Dependencies between maps since I have maps set up as network segments tied together with routers). That should reduce the amount of scrubbing in the outage report to the single device and if that device is the VPN providers router, then your stuff will not show the outages <wink>.
A far better solution would be to start investigating why the VPN tunnel keeps going down (run a continuous PING test to something on the other side of the link over a period of several hours to verify it's not the WUG system that's having the problem). If you have an SLA with the VPN provider, then that's the place to start once you've confirmed with more than one tool that the VPN link is actually going down; WUG outage reports are great for getting them to investigate! Also start culling thru the outage times over a long-term view and see if you can find something that is consistent (time of day on specific days, during times of known network events like an auto-upload/download of traffic across the VPN link, etc). Also do some throughput testing using some of the free tools on the internet like Q-Check (NETIQ) which will benchmark if the SLA's are actually being met by the VPN provider. As a last comment, I find that when my WUG system starts going crazy with service down alerts, it's trying to alert me of impending network bandwidth issues... ------------------------------------------------------------ Bryan Harrell, SPII Network Transport & Administration - Tallahassee Fla. Dept of Revenue (850)-921-0700 S/C 291-0700 ------------------------------------------------------------ >>> [EMAIL PROTECTED] 01/14/2004 10:56:37 AM >>> Thanks Mark. I discounted the logging aspect. That is pretty interesting. I have thought of a cheesy way to get around that problem. It would of course be performed via a program alert. What you can do is create an extra map with one device (the firewall). When the firewall goes down, you can have a program alert trigger that calls a custom web page that disables logging on each device on the "main" map, except the firewall. You can do this with a loop using java script or vb script, and the What's Up Web Tags. When the device comes up, the program alert will trigger again. The page will determine whether to enable or disable logging by performing a conditional action based on the status of the firewall device object on the "special map". Anthony Franklin, Network Engineer Information Technology Services University of West Florida Pensacola, Florida 32514 850.474.3243 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wittke, Marc Sent: Tuesday, January 13, 2004 2:19 AM To: [EMAIL PROTECTED] Subject: AW: [WhatsUp Forum] Automatically enable/disable polling of containers and subnets Anthony, you're not quite right... yes, WUG will send one alert for the whole subnet, but when we generate an outage report, every single system was logged as unavailable. this is right for us (the external IT-service) but the customer (the internal users) met no problems at all. what we do now is manually cleaning the outagereport - would be nice, if a dependency prevented the logging of the unavailable subnet. A single line for the firewall time-out would be enough fo us greetings, marc Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
