When you see rapid status changes, it is usually caused by the
Router Fault Isolation processing of netmon. When RFI finds something
is down, it changes netmon's planned polling sequence to investigate the
area to determine the extent of the outage. I think this rapid change in
status
can happen in cases when all routes to a subnet are not included on your
map.
For instance, you might not have snmp access to one or more routers on that
subnet, so Netview does not know that it has a way to get to the subnet,
yet
when it pings things there, it gets through. Very confusing for netmon. You
should
either complete the map, or disable RFI. That's what I think is probably
going
on. Others may have other ideas.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Bernard Disselborg <bdisselb AT triple-p DOT nl>@tkg.com on 06/28/2001 01:21:12
PM
Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
Sent by: owner-nv-l AT tkg DOT com
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc:
Subject: [NV-L] Node Down immediately followed by Node Up
Hello,
Environment: NetView 6.0.2 on AIX 4.3.3
I'm getting a lot of Node Down alarms which are almost immeditately (1-4
seconds) followed by a Node Up.
My status polling is default: 2.0 secs timeout, 3 retries.
It looks like if a Node Down is generated immediately after the first
failed ping, and a Node Up is generated after the first retry.
I'v tried increasing timeout and retry numbers, but this doesn't help.
Has anybody seen this ?
Thanks in advance,
Bernard
____________________________________________________________________
Bernard Disselborg - Consultant
Triple P Nederland B.V. - Enterprise Management
PO Box 245
4130 EE Vianen - The Netherlands
e-mail: bdisselb AT triple-p DOT nl
telephone: +31 (0)347 353317
mobile ph: +31 (0)655 833355
____________________________________________________________________
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|
