Thanks for this advice. However, now that I've upped the "trigger" to 3 I find I'm still getting "SVCDOWN .. missed 1" entries inthe log. Is there something I have to do to apply the change properly? I tried shutting down and restarting the program, but I'm still getting these entries.
Toby -----Original Message----- From: Mark Symons [mailto:[EMAIL PROTECTED]] Sent: 28 February 2002 14:36 To: [EMAIL PROTECTED] Subject: RE: [WhatsUp Forum] Monitoring and Service Interfaces I went back to your original email on this subject and saw that you are running WhatsUp Gold v7.01. This version introduced a new feature that might help you solve your problem. Configure -> Monitors and Services -> Interface -> Edit The "Test fails when exceeded x consecutive times" is what is new in v7.01 - at least for "Constant Value" checks... it was present in v7.0 for the other two check types. Try increasing the value of x from 1 to some higher figure. This will help you avoid the situation where single dropped packets cause SVCDOWN log entries. If you decide that only certain devices require this "desensitization", then you could also create a copy of the Interface monitor, such that the original definition uses the default value of x =1 and the copy (reserved for monitoring your problem devices) uses a larger value of x. Mark Symons Ipswitch, Inc Augusta GA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Toby Rodwell Sent: Thursday, February 28, 2002 06:50 To: '[EMAIL PROTECTED]' Subject: [WhatsUp Forum] Monitoring and Service Interfaces Several of you have been kind enough to offer advice about the repeated "SVCDOWN ... Interface(x) .... missed 1" I get from several of my Cisco routers. I have been asked for more specific details about the affected machines: the models include 2501, 2610 and 3640, running a range IOSs from 10.3 to 12.2. The interfaces affected include Ethernet, Serial (leased line) and Serial (frame-relay) . Thus there seems to be no common link between the devices. Also, all interfaces were successfully "auto discovered" by WUG during initial configuration. In a bid to better understand the Service Interface mechanism I have begun to look at the debug log (which provides a wealth of information). It seems to me (and this is borne out in the Help Manual) that when a device is polled, the specified interfaces' MIBs are checked to determine whether the given interface is up or down. For some reason, at regular intervals, when polled these machines appear to be asserting that certain interfaces are down. However, a check of the devices' Syslog logs shows quite clearly there was no such outage. Furthermore, I've started ICMP polling individual interfaces, and they show no pings being missed. This is all most annoying , because it means my logs fill up with spurious SVCDOWN messages and I am rather losing faith in what is or isn't an alarm. I would rather not have to disable interface monitoring but at the moment I don't see any other option. Has anyone else experienced similar problems with Service Monitoring interfaces? -- 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/ -- NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected. 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/
