I have seen this, and I think it boils down to a special case of what is
referred to in the documentation as 'the Ambiguous Case'. The -n option
is provided for netmon to control how this case is handled. See the
/usr/OV/doc/RouterFaultIsolation.html document. The -n flag is one
you have to add manually to netmon.lrf. It changes the handling of the
ambiguous case from unreachable to down. I have not tried it. Want to
let us know if it works for this case?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Andreas.Poehlmann" <ANDREAS.POEHLMANN@Allianz.de>@tkg.com on 05/10/2001
06:50:40 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: " - *nv-l@tkg.com" <nv-l@tkg.com>
cc:
Subject: [NV-L] RFI problem
Hi out there,
we're fighting a RFI problem here...
Situation: We monitor a router of which we
- can only ping one of four interfaces and
- none of the interfaces is in a subnet with an other monitored device.
=> This router is logical "not connected" to our network, but we can ping
this interface and
we have SNMP access.
The unpingable interfaces are set to unmanaged.
In case the last pingable interface goes down, RFI assumes the
router is "unreachble", turns it to white and this status change is not
propagated.
I'd like to see this router turning red instead of white!
Having read the manpages and description of the RFI I assume that there is
no
way - but is there realy no way? Any experiences with situations like
this?
Any help appreciated
regards
Andreas Pöhlmann
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|