This is a multi-part message in MIME format.
The usual cause is network delay. This could be delay in looking accessing DNS
or searching a hosts file, it could be network congestion, it could be the
device is too busy to answer SNMP or ICMP queries, anything which will delay
the status poll NetView does every 15 minutes (default on NT, 5 minutes default
on Unix) and its retries.
Netmon originated events DO NOT tell you the status of the device, they tell
you NETMON did not get the reply to his poll. If the device is really down then
it means the same thing. If the network is slow it doesn't.
Solutions:
1. Check your name resolution - NetView hits it hard and a slow DNS is a
killer.
2. Check for network congestion.
3. Increase the timeouts for status polling. See page 151 of the NetView NT
User's Guide.
4. Find out about using the rulesets which come with NetView NT. There is one
called Downandnotupinten.rs which may do what you want. See page 105 of the
User's Guide.
Good luck.
--
Bill Evans -- Consultant in Enterprise Systems Management
reply-to: wvevans@prodigy.net (or Bill_Evans@sra.com)
Phone: 919-696-7513
Send short text messages to 9196967513@messaging.sprintpcs.com
Haswell, Pete wrote:
> Hi List,
>
> We have Netview for NT 6.0.2 configured to generate OV_Node_Down/Up events
> to TEC. We seem to get a high number of erroneous events generated. Mot of
> the time the OV_Node_Up is generated within a short period of time. Any
> ideas what causes this?
>
> Thanks
>
> Pete
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
> .
>
>
|
The usual cause is network delay. This could be delay in
looking accessing DNS or searching a hosts file, it could be network congestion,
it could be the device is too busy to answer SNMP or ICMP queries, anything
which will delay the status poll NetView does every 15 minutes (default on NT, 5
minutes default on Unix) and its retries.
Netmon originated events DO NOT tell you the status of the
device, they tell you NETMON did not get the reply to his poll. If the device is
really down then it means the same thing. If the network is slow it
doesn't.
Solutions:
1. Check your name resolution - NetView
hits it hard and a slow DNS is a killer.
2. Check for network
congestion.
3. Increase the timeouts for status polling. See page 151
of the NetView NT User's Guide.
4. Find out about using the rulesets
which come with NetView NT. There is one called Downandnotupinten.rs which
may do what you want. See page 105 of the User's Guide.
Good luck.
Haswell, Pete wrote:
> Hi List,
>
> We have Netview for NT 6.0.2
configured to generate OV_Node_Down/Up events
> to TEC. We seem to get a
high number of erroneous events generated. Mot of
> the time the
OV_Node_Up is generated within a short period of time. Any
> ideas what
causes this?
>
> Thanks
>
> Pete
>
_________________________________________________________________________
>
NV-L List information and Archives: http://www.tkg.com/nv-l
> .
>
>
|
|