nv-l
[Top] [All Lists]

Re: NetView and HSRP

To: nv-l@lists.tivoli.com
Subject: Re: NetView and HSRP
From: James_Shanks@TIVOLI.COM
Date: Fri, 26 Jun 1998 16:16:09 -0400
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView et alia <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView et alia <NV-L@UCSBVM.UCSB.EDU>
Forgive me here but I don't see what your problem has to do with HSRP.  It
looks more like DNS.  I think you should be looking at some of the recent
appends on NetView and hostnames for routers.

The issue with HSRP is that two different routers have an interface with
the same ip address, which is technically illegal in TCP/IP.  The deal is
that only one is supposed to active at a time, but in V4 NetView, netmon
doesn't know that, and he adds the interface to the database and it gets
put on the map, only to be deleted when found again somewhere else, so you
have a phenomenon of the interfaces coming and going.  That has nothing to
do with discovering the router with a particular address so far as I can
see, since presumably the discovery address will be fixed and not HSRP
capable.

The fix you mention might be at the bottom of this if it affects TCP/IP or
DNS but otherwise I doubt that too.  According to the IBM database, U456664
, is a PTF  which accumulates current fixes for AIX 4.2.1.   Unfortunately,
I don't have the time and resources to research that for you.

I would take a look at the ones you are having trouble with and look into
hostname resolution.

James Shanks
Tivoli (NetView for UNIX) L3 Support


mburke@rpm.com on 06/24/98 11:19:16 AM

Please respond to mburke@rpm.com

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: James Shanks)
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

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web