I'm no expert here, but I can describe what I (think) I've seen so far with
WUG Ver 6.02 -- YMMV on others. When I was writing custom services
plugins, the docs made sure to notify you that your plugin needed to be
thread-safe. I never figured out exactly why until playing around with it a
bit more... I believe that a (very very rough) description of how the
polling engine works would be:
1. Wait for the poll timer on a map to make it to 0. When it gets there,
start a poll and reset it
2. Go through the devices on a map, one by one adding them to a 'ping
request queue'
3. As you go through the request queue, send out an echo request. This
causes a flurry of ping requests to go out at the beginning of a poll
cycle.
3. When a device returns a ping, kick off a new thread to do all of the
'higher' service polls defined. (Like HTTP, FTP etc)
4. If a device's timeout happens before you get the ping response back,
mark it as missed. If it's the 1st missed one, send out another ping
request as almost a 'mercy poll'
Of course, this is all theoretical - based on my attempts at plugin
development and watching a protocol analyzer. But, if it's at least mostly
true there is some good to be gained from it.
1. If all of your maps are starting their poll cycle at the same time [ie
all on 60 seconds] then you're gonna dump a boatload of ICMP traffic all
onto the net at once. I don't think it matter if you have 5 maps at 20
nodes each or one 100 node map (from a polling standpoint). If you can
stand to stagger some maps (poll important things every minute, things less
important every 2.5 minutes) that could distribute the ICMP load a little.
2. Use the up and down dependencies to make sure that you don't poll
unnecessarily.
The big question in my mind is how close did I get to how it _really_
works?
--D
Duane Waddle
[EMAIL PROTECTED]
"With sufficient thrust, pigs fly just fine..." -- RFC1925
Christopher_J_Powers@Keane.
com To:
[EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: RE: [WhatsUp Forum]
False alarms
switch.com
08/27/01 11:37 PM
Please respond to
WhatsUp_Forum
Hopefully, Chris, one of the WUG pros will educate us again, but here's my
take based on 5 months experience with it:
800 devices on one map. A new poll on those 800 devices every minute.
Take your polling timeout value into consideration, as well. You didn't
answer as to whether the web view eventually shows the device as coming
back on-line. You said it appears as down, then you can ping it, but then
the device doesn't appear as up again. Is that the case? The device in
the web view never appears green, or does it take a wicked long time to do
so? There is a refresh timer setting in configure-web options for updating
the web view. Mine is set for the default, I think 30 seconds or so. If
your device does eventually show as on-line in the web view, then I'd bet
that your numbers and arrangement are the culprit.
I have about 350 devices in 60+ maps. Every 2.5 minutes WUG polls all the
devices. My polling timeout value of 10 seconds means that if there is a
slow link somewhere, the polling of an individual device will wait 10
seconds for a successful reply. After 10 seconds, the device is reported
as not responding to the poll and WUG moves on to the next device to be
polled. Are all of your devices in close proximity? Mine are all over the
country and in UK, across many different WAN links. If a device is down
for 10 minutes, then a notification goes out (thus 2.5 minutes times a
notification trigger value of 4 missed polls equals 10 minutes). My guess
on how it works is that because I only have an average of 6 devices per
map, as soon as the 6 devices successfully answer the poll, the branch
office subnet icon (ex. NYC) as a whole is reported as up to the
application. While WUG has continued to poll other devices on other maps
during the same polling period of 2.5 minutes, the mentioned NYC branch
office subnet icon is now shown to be up, or on-line, in the web view
during the next refresh (30 seconds) of the web page.
But I could be wrong. Maybe you just have some corrupt data in there
somewhere. How is your poll going out? ICMP? If not, then maybe that is
a factor?? I hope I was at least able to help you better
understandsomething about WUG. Later..........
Chris Powers
Network Systems Engineer
MCSE, CNA, Network+, A+
Keane IT Technical Services
x1730
"Chris Allen"
<[EMAIL PROTECTED]> To:
"'[EMAIL PROTECTED]'"
Sent by:
<[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc:
switch.com Subject: RE:
[WhatsUp Forum] False alarms
08/27/2001 01:37 PM
Please respond to
WhatsUp_Forum
Well, Chris, I unfortunately inherited the What's UP Gold server and the
person who first implemented did not organize it too well. He created one
map via a hosts file and did not break the devices out in any kind of
order.
I am in the process of creating new maps based on which devices are on
which
Frame Relay host port.
I do believe that 60 seconds is not long enough for 800 devices but haven't
found any information regarding limitations and recommendations. By the
way,
how many times does WUG ping the device during a poll? once, twice, three
times ???
Thanks,
Chris
p.s. Feel free to share your salary. LOL It would be interesting to see
what
people are making in other parts of the country.
> -----Original Message-----
> From: [EMAIL PROTECTED]@INTERNET@HHC
> Sent: Monday, August 27, 2001 11:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [WhatsUp Forum] False alarms
>
>
>
> I'm curious, Chris. How f&#%ing big is your monitor that you have 801
> devices on ONE map?!?!
>
> Also, you DO know that if a device is shown to be down, then comes back
> up,
> it won't show as being up until the poll makes its way back to the device
> again. I suppose the # of devices could be a factor there. Isn't a
60-90
> second poll for 800 devices generating a boatload of network traffic for
> you? I have 300-350 devices over 60+ maps and I'm currently polling at
> 150
> seconds and sending notifications after 10 down minutes. We're going to
> bump up the notification time to after 15 or 20 minutes, though, to cut
> down on all the network fluctuation that we're getting notified on.
Links
> are going down and up across the country and world all the time for short
> periods and the e-mails to our pagers are getting annoying for links that
> go down for 15 or 20 minutes. Especially since Motorola is monitoring
all
> our links and goes to work on them immediately. Gee, should I disclose
my
> salary, too? HAHA!! Later..........
>
> Chris Powers
> Network Systems Engineer
> MCSE, CNA, Network+, A+
> Keane IT Technical Services
> x1730
>
>
>
> "Chris Allen"
> <[EMAIL PROTECTED]> To:
> "'[EMAIL PROTECTED]'"
> Sent by:
> <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] cc:
> switch.com Subject:
> [WhatsUp Forum] False alarms
>
>
> 08/27/2001 11:47 AM
> Please respond to
> WhatsUp_Forum
>
>
>
>
>
>
> I am using What's UP Gold 6.02 with the web interface. I am experiencing
> problems with sites showing down yet can be pinged. From the web
> interface\tools menu I can successfully ping the IP address but WUG will
> not
> update the device status. I am monitoring 801 devices on one map with a
60
> second poll timer. I have recently changed it to 90 seconds but still
does
> not update the device status. Do I have too many devices on one map or is
> there a bug in the software? Please someone help...
>
> Thanks for any help in advance!!!
> Chris
>
>
> 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/
>
(See attached file: attkfgkg.dat)
#### attkfgkg.dat has been removed from this note on August 28 2001 by
Duane Waddle
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/
