nv-l
[Top] [All Lists]

Re: [NV-L] Frequently Node Down-Up events

To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Subject: Re: [NV-L] Frequently Node Down-Up events
From: James Shanks <jshanks@us.ibm.com>
Date: Tue, 24 Oct 2006 12:12:34 -0400
Delivery-date: Tue, 24 Oct 2006 17:28:07 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <AAE5533FFC029444B03EED20895088AD4EC326@MAILADRTEL.adr.it>
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com

I'd guess that is exactly the problem. The polling defaults are good for your subnet, the one NetView is on. Distant devices or ones slow to respond will require longer time-outs. You need to adjust them to what works in your network. This is a tuning issue.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
Inactive hide details for "Conosciani Mauro" <conosciani.m@adrtel.it>"Conosciani Mauro" <conosciani.m@adrtel.it>


          "Conosciani Mauro" <conosciani.m@adrtel.it>
          Sent by: nv-l-bounces@lists.ca.ibm.com

          10/24/2006 11:37 AM
          Please respond to
          Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>


To

"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>

cc


Subject

[NV-L] Frequently Node Down-Up events


Hello,

I often see DOWN-to-UP messages of my network devices lasting only for
few seconds. This applies to some Switches as well as Access Point we
are monitoring.
I can't see anything on any log files on the network devices to verify
the downtime "supposedly captured" by netview. Is this a result of the
polling-timeout-retry combination we have? Or is there already something
wrong with my netview?
Netview 7.1.4 on Linux Red Hat ES4.
I'm using the Polling default value.

Regards,

Mauro

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

GIF image

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web