Well, I have done just as you state below for rediscovery, but the HSRP
addresses are never discovered at all. I'm sure the problem is during the
process of "in the course of examining the interface tables for the nodes it
will come upon the hsrp interface on whichever node it happens to be on at
that time". HSRP address are not in the "ip" SNMP table, so what MIB table
does NV look for these during discovery? I am trying to determine if the
HSRP info. is not in the MIB on the remote agent or it is in the MIB and NV
is not recognizing the data and doing correct discovery of these HSRP
addresses? Perhaps someone from direct NV support can address this
question? I am waiting from Tivoli support on a PMR for this issue, but
they have been very slow in responding. Thanks,
Joe Prokott - West Group
Network Architect
610 Opperman Drive
St. Paul, MN 55123
Phone: 651-687-4536
Fax: 651-687-6946
E-mail: joe.prokott@westgroup.com
-----Original Message-----
From: Leslie Clark [mailto:lclark@US.IBM.COM]
Sent: Wednesday, August 04, 1999 12:01 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: HSRP Address Discovery
I don't know exactly how it works, either, but I do know some things
that will give Netview trouble with it. First, you need to be at 5.1.1
because
there were problems before that. Then, netview should NOT discover
the node by the hsrp address. And there should be no name resolution
on that address as far as Netview knows. (Lately netview has been making
a lot of assumptions or guesses based on name resolution. If it is resolved,
make sure it is different from the two real nodes, and maybe exclude it
from the seedfile, so netview won't be able to make a node out of it. It
will
of course be able to add it to a node that has other allowed addresses.).
You need to get
all traces of those nodes out of the database, then forcibly discover both
of the nodes that might get that interface, but by some other address. Like
put them at the top of the seedfile, stop netmon, delete anything related to
those nodes, and restart netmon. It should discover the two nodes, then
in the course of examining the interface tables for the nodes it will come
upon the hsrp interface on whichever node it happens to be on at that time.
It will handle it as a normal interface, it won't look any different. The
only
indication you will have that it is hsrp is when it moves. Then you will get
an event indicating that an hsrp interface has moved from here to there.
I have seen it work fine as long as the discovery goes as described.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 08/04/99
12:47 PM ---------------------------
"Prokott, Joe" <Joe.Prokott@WESTGROUP.COM> on 08/03/99 06:22:44 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc:
Subject: HSRP Address Discovery
Could someone please let me know where in the MIB NetView looks at to
discover HSRP addresses and puts them into the NV map as such? We are
having problems with NV discovery of HSRP addresses and trying to determine
if it is not in the MIB of the polled router (where NetView thinks it should
be) or what? We have tried putting the HSRP addresses into the seed file,
but that has not worked either for discovery and placement of these HSRP IP
addresses into the NV database. I thought perhaps NV looks in the "at"
table for the HSRP addresses, but I'm not sure this is the case and I'm also
looking for more detail than just knowing that "NV looks at the at MIB".
Joe Prokott - West Group
Network Architect
610 Opperman Drive
St. Paul, MN 55123
Phone: 651-687-4536
Fax: 651-687-6946
E-mail: joe.prokott@westgroup.com
|