|
Brian,
One problem with your description needs to be
pointed out; If the interface on your router which communicates with
NetView goes down, or the device totally loses power, you will never get a trap
from the router. Maybe from another router between NetView will
notify you of the failure but dead devices do not send traps and dead
interfaces don't forward them. Keep the NetView polling
going.
At the risk of correcting James, my
favorite expert; five minutes is the time interval for polling on NetView
in the Unix world; the Windows world defaults to twenty minutes. James
specializes in the Unix world. You should the polling interval if notification
is time critical. If the overhead of a five minute or two minute
polling cycle is too much for the Windows system try a Linux or Unix
machine. That's not a higly probable situation; I have monitored a
couple hundred routers and switches by polling with a Windows solution and had
no problems. Big dual processor Windows server.
One more problem I've found is being swamped with
UP/DOWN traps from switches which when badly configured tell NetView every
time some turns their PC on or off.
Bill Evans
----- Original Message -----
(Right now I have turned off all polling so that I can work only
with traps and KNOW what is happening and why...we are intending on relying on
these and other backup devices to send traps when their are issues vs. just
relying on polling). In our situation, we need to know exactly
when these devices have problems, vs. waiting for a polling period to check
the device.
| 