|
I'm
not sure that I'm seeing what you are seeing. From the General Page, the
only option is to use ICMP, IPX or NetBIOS, then select either IP address or
name resolution.
On my
device, I have Telnet, ECHO, and PING as my active monitors (for example) but it
seems that ICMP packets are what causes the device to become "down" I've
tried changing the down to down for 2 minutes. That only triggers an UP
alert after it sees the device as down. I don't get the alert for down but
I get an alert for UP.
What I
did in WUG was to change the poll to use services instead of ICMP. That
worked great and I was able to see that the system was up except when it could
not get to the service (HTTP, FTP, Exchange, etc.).
I
can't seem to find that option in WUP 2005.
I believe that “ICMP”
is now listed in the “Active monitors” area for a device. Once you add the
HTTP monitor, you should be able to remove the ICMP monitor. What’s nice about
WUP is that you can select multiple monitors and there is no longer a default.
In WUG you could only log 1 “default” poller. In WUP, you can configure it to
store latency on all your monitors.
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 1:19
PM
To:
[email protected]
Subject: RE: [WhatsUp Forum] Occasional
Missed Checks....
I would
love to but in WhatsUp Pro 2005, that option is not available. In
WhatsUp v8.x there was an option to poll using other polling methods (http,
ftp, telnet, services, etc) but I can not find this option.
I
upgraded from WhatsUp v8.03 to Pro and this is one of the "missed" items that
I have not found as of yet.
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 10:50
AM
To:
[email protected]
Subject: RE: [WhatsUp Forum] Occasional
Missed Checks....
You
may want to use another protocol (such as HTTP) for primary polling on those
devices. This may work around the issues you're seeing with ICMP while
maintaining the connectivity monitoring.
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rogers, Sam
Sent: Monday, January 24, 2005 9:41
AM
To:
[email protected]
Subject: RE: [WhatsUp Forum] Occasional
Missed Checks....
ICMP,
by design, is not a reliable protocol. RFC792
states:
The
Internet Protocol is not designed to be absolutely reliable.
The
purpose of these control messages is to provide feedback
about
problems in the communication environment, not to make
IP reliable.
There are still no guarantees that a datagram
will be delivered or a
control message will be
returned. Some datagrams may still be
undelivered
without any report of their loss. The higher level
protocols that use IP must implement their own reliability
procedures
if reliable communication is
required.
A
device will not respond to an ICMP request if it is too busy to
answer. And during heavy WAN usage, ICMP requests are often
discarded. This is simply the way things work. It's a pain
(and annoying), but that's just the way it is.
You'll
can try adjusting the trigger to a higher value or set WUG to just not
monitor during known high volume times.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 8:15
AM
To:
[email protected]
Subject: RE: [WhatsUp Forum]
Occasional Missed Checks....
I'm
having the same problems with my WhatsUp 2005 as well. It's becoming
a pain to keep getting alerts when there is nothing wrong with the device
or service.
I've
been working on this problem now for about 2 weeks with no end in
sight. I've tried increasing the poling intervals as well as
limiting how many interfaces or items are checked.
The
one thing that I have noticed is that it appears to happen most with ICMP
or PING packets during times when my WAN is in it's heaviest use.
Any
help would be greatly appreciated as well.
Sr.
Network & Telecommunications Analyst
Universal Leaf
North America US, Inc
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 4:10
AM
To:
[email protected]
Subject: [WhatsUp Forum] Occasional
Missed Checks....
I've
noticed that WhatsUp will occasionally fail on it's
checking of a system. However, if you immediately check the
system, it finds all services running perfectly. With the old
version, I would mark the device to only log after 4 failed
attempts. I have not seen a similar function with the new 2005
version. Am I missing a setting someplace?
For those interested, the
errors I get in the State
Change log is
something along the lines
of "Unable to open SCM.
The RPC server is unavailable". This happens on Exchange 2000
cluster server, and on a Oracle Cluster server (specifically, the
virtual computer name)
-jb
Jason M.
Bohreer, MCSA
Network Engineer
Nastech
Pharmaceutical
3450 Monte Villa Parkway
Bothell, WA 98021
(425)
908-3657
---------------------------
This email or fax and any
attachments thereto may contain private, confidential, and privileged
material for the sole use of the intended recipient. Any review,
copying, or distribution of this email (or any attachments thereto) by
others is strictly prohibited. If you are not the intended recipient,
please contact the sender immediately and permanently delete the
original and any copies of this email and any attachments
thereto.
IMPORTANT NOTICE: The contents
of this e-mail are confidential to the ordinary user of the e-mail address
to which it was addressed and may also be privileged. If you are not the
addressee of this e-mail you may not copy, forward, disclose or otherwise
use it or any part of it in any form whatsoever. If you have received this
e-mail in error please e-mail the sender by replying to this
message.
IMPORTANT NOTICE: The contents of this e-mail are
confidential to the ordinary user of the e-mail address to which it was
addressed and may also be privileged. If you are not the addressee of this
e-mail you may not copy, forward, disclose or otherwise use it or any part of
it in any form whatsoever. If you have received this e-mail in error please
e-mail the sender by replying to this
message.
|
