Leslie,
I think the WAN problem implied in this message is one that is also fixed in
NetView 6 with the SNMP based status polling.
For complex devices, such as ATM devices, multiple virtual networks are
often modelled as multiple interfaces. Upon discovering any interface,
NetView proceeds to configure the device using SNMP and findss all of the
other interfaces. Because each interface is logically on a different
network, an ICMP Echo request (PING) fails to all of the interfaces except
for traditional LAN interfaces and the WAN interface first discovered. PING
can't be routed between different virtual networks.
This would result in a situation where a router would look yellow all of the
time (even when functioning fine) and RED whenever the single good
connection was dropped for any reason.
In NetView 6, we've addressed that with the SNMP status polling. The same
channel used to find the device originally (in this case a WAN interface) is
used to query the SNMP Agent for interface status which is synthesized into
overall host status. Two good things happen from this:
1) the status is consistently reported more correctly (green when it should
be).
2) Failure is more predictable, although you would still want to probe it
through the most reliable interfaces on the device.
This is the only thing I can think of related t this.
-jim
> -----Original Message-----
> From: lclark@US.IBM.COM [mailto:lclark@US.IBM.COM]
> Sent: Monday, June 19, 2000 6:20 PM
> To: IBM NetView Discussion
> Subject: Re: [NV-L] One Router, Multiple Interfaces Displaying Multiple
> Router Icons.
>
>
>
>
>
>
> You will be happier with V6 in this regard.
>
> Often this happens when you try to force discovery by the LAN interface,
> which is
> named, and netmon has already heard from the WAN interface, which is not.
> When
> that happens, and it makes two nodes, the solution is to delete the one
> you don't
> want and quickly demand-poll the one you do want. This usually goes
> together
> with warnings about duplicate IP addresses. Assuming you have snmp access
> to
> the router. Another thing you can do is add names for all
> interfaces (same
> name).
> This problem was at its worst in 5.1.2, I think. Netmon did not
> consistently merge
> nodes. It is a lot better in V6. Anybody know if it is also better in
> V5.1.3?
>
> That said, I don't understand your statement (and I have heard it before)
> about
> not wanting to discover by the WAN because it is more likely to
> go down and
> you
> don't want the whole router to go red due to a WAN interface being down.
> People
> have said that here before, and I don't understand it. The status of the
> router is
> the compound of all of the interfaces on the router. Each is evaluated
> individually.
> If it can be pinged, it is up, if not, it is down. If the WAN interface
> goes down and
> you have no other route to the rest of the interfaces, that router will be
> red regardless
> of which interface you discovered it by. There are lots of other things
> affected by
> which interface you discover by, like label, and which address is
> used with
> some
> of the menu functions, but the status of the router is not one of them as
> far as I
> understand it. But your goal is nonetheless correct, if only for naming
> purposes.
>
> Anybody care to straighten me out on this? I'm willing to learn...
>
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
>
>
> "Ken Karasek" <KGKARASE@hewitt.com>@tkg.com on 06/19/2000 04:38:10 PM
>
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>
> Sent by: owner-nv-l@tkg.com
>
>
> To: IBM NetView Discussion <nv-l@tkg.com>
> cc:
> Subject: [NV-L] One Router, Multiple Interfaces Displaying
> Multiple Router
> Icons.
>
>
>
>
>
> Hello all,
>
> I am running NV v5.1.2 with AIX 4.2.1. I have noticed for some
> time that NV
> is
> displaying our Bay routers on the maps with multiple router
> icons. There is
> only
> one router per office with at least three interfaces. One LAN,
> one WAN, one
> ISDN
> backup (AD). I am using a seed file that has the IP address of the LAN
> interface
> listed since it's more likely a WAN interface will go down vs. a LAN
> interface
> and I didn't want the entire router to turn red for a WAN link going down.
> There
> are also DNS names for each router, but only assigned to the WAN interface
> address. Not that it matters, but the DNS does not reside on the same
> machine as
> NV.
>
> Why is/would NV display multiple router icons for the same single
> router? I
> have
> deleted/rediscovered and ran the database cleanups. This is quite
> confusing/frustrating for our Command Center folks when it come to
> identifying
> problems with a router. Is there a configuration change(s) that I can make
> to
> correct the discovery/display?
>
>
> Thanks.
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
|