Maria,
It doesn't sound like you are using a seed file. Or U456664 turned the
seedfile off.
You must be using a seedfile, since router loopbacks never show up in the
arp or interface tables of other routers.
Also, name conflicts, involving DNS, /etc/hosts, or both, can cause this.
If an otherwise correctly discovered router has a loopback interface that
sufferes a name change to that of another router, Netview will sometimes
move just that loopback to the other router. That will cause the next
interface in the interface list of that first router to become the selection
name of the router, and the symbol name will change too.
HSRP will only cause a problem only if a router gets discovered by an HSRP
interface. You should never let Netview discover routers by HSRP
interfaces.
Steve Houle
> ----------
> From: Maria Burke[SMTP:mburke@rpm.com]
> Reply To: mburke@rpm.com
> Sent: Wednesday, June 24, 1998 11:19 AM
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: NetView and HSRP
>
> We are running NetView 4.1 and Cisco's HSRP on our routers. About a month
> ago, I deleted the database and did a fresh discovery several times while
> testing the use of loopbacks on the routers (NetView is configured to
> discover loopbacks). In DNS, the loopback is the hostname of the router
> (and thereby the name I want as my selection name in NetView). At this
> time, I was discovering all of my routers correctly -- by loopback and
> therefore by the correct hostname. I've since applied APAR U456664 and
> this
> is no longer working; some of my routers discover by the loopback address
> and some do not. I can only assume the APAR caused this problem because I
> had tested the use of loopbacks many times before this one final database
> deletion. Has anyone else experienced this problem or is there a
> workaround
> to managing HSRP in NetView? I've seen emails about adding the routers to
> a
> host file but we prefer not to use a host file. Any suggestions would be
> appreciated. Thanks!
>
> Maria Burke
>
|