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
"Conosciani Mauro" <conosciani.m AT adrtel DOT it>

"Conosciani Mauro" <conosciani.m AT adrtel DOT it> Sent by: nv-l-bounces AT lists.ca.ibm DOT com 10/24/2006 11:37 AM Please respond to Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>

To "Tivoli NetView Discussions" <nv-l AT lists.ca.ibm DOT 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 AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

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