I appreciate the replies I have received and I can see that I may not have
made myself clear. So, to clarify a few things:
I have both an HSRP and a naming issue.
I am using a seedfile which contains the loopbacks of the routers.
In DNS, the loopback address is assigned the hostname of the router (e.g.,
routera) and all of the interfaces on the router are assigned unique names
(e.g., serial 0 would be routera-ser0, token ring 4 would be routera-tok4).
Prior to installing the APAR, all of my routers would discover with the
hostname of the loopback (routera). The naming of the routers in NetView
was working the way we wanted. I still had an issue with HSRP address being
added as a third router.
After installing the APAR, almost all of my routers are discovering as
though loopbacks do not exist (i.e., routera-ser0) and the HSRP address is
discovering as a segment symbol. I am still using the same DNS server as I
used prior to the APAR install and I'm still discovering the same routers so
I can't see this as being an error in DNS.
Has anyone else running NetView 4.1 on AIX 4.2.1 with HSRP on their routers
and discovering loopbacks seen this problem after installing APAR U456664?
Again, thanks for all of your help!
Maria
-----Original Message-----
From: Houle, Stephen A [mailto:sh32829 AT IMCNAM.SBI DOT COM]
Sent: Friday, June 26, 1998 6:06 PM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: Re: NetView and HSRP
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 AT rpm DOT com]
> Reply To: mburke AT rpm DOT com
> Sent: Wednesday, June 24, 1998 11:19 AM
> To: NV-L AT UCSBVM.UCSB DOT 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
>
|
