nv-l

Re: Node down problem

1999-08-04 08:22:55
Subject: Re: Node down problem
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 4 Aug 1999 08:22:55 -0400
NetView determines status by the use of ICMP echo (ping).  So if everything is
as lightly loaded as you say it is, why are those pings timing out?  Does your
router to those devices throw them away?  Is there a routing problem? Find the
answer to that and your problem will be over.    How long does a ping take from
the command line?

But failing to get that answer, I would increase the timeout value and see what
happens and I would decrease your retries.  All you are doing with that many
retries is cluttering up your bandwidth more pings which are probably timing
out.  Remember that netmon actually increases the timeout with every succeeding
ping, so with 10 of them and a new cycle in 2 minutes, you could already be
causing part of the problem.  I would increase the cycle time from 2 min back to
the 5 min default.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Frantsen Christian <cf AT INTERNOC DOT SE> on 08/04/99 03:19:09 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Node down problem





Hi all

I have a problem with Netview thinking nodes go down allthough they are not
down (I checked all units uptime with SNMP after Netview has reported the
being down). I am monitoring another companys equipment across a 128kb
X-Line. Sometimes Netview looses contact with several devices on the other
side or sometimes all units, the next time it polls the status, all devices
are up again, this is the most common thing, but sometimes it can take as
long as 2-4 polls for Netview to actually discover that the devices are NOT
down. There are about 30 devices being monitored.

My SNMP Configuration looks like this

Timeout 5.0
Retry Count 10
Status Polling 2m

The problem is not because there are to much traffic on the 128kb
connection, it's only used for monitoring the network and sometimes we use
remote management software such as PC-Duo, but that's all. The 2 minute
status polling is probably to often but I will raise the once I get it to
work properly.

How high could the timeout and retry count be set in the worst scenarios?

Regards
-----------------------------------------
Christian Frantsen
Technical Operations

Internoc Scandinavia AB
Tel: +46-36-194843
Fax: +46-36-194651
http://www.internoc.se


<Prev in Thread] Current Thread [Next in Thread>