Try using the -v option in NETMON start up to find the HSRP addresses rather
than the seed file. There is also some bugs related to HSRP addresses on
v6.02. I don't believe the bugs are related to discovery, but to status
monitoring. Hope that helps.
-----Original Message-----
From: awatthey@mmm.com [mailto:awatthey@mmm.com]
Sent: Friday, November 16, 2001 9:37 AM
To: IBM NetView Discussion
Subject: [NV-L] HSRP on NT
I am on NT4 and Netview 6.0.2 and am having a problem with HSRP
definitions.
I have tried this several times thinking it was me but cannot see anything
wrong. I define a few of my HSRP addresses in the netmon.seed file
(discovering local network only with seed file), clear the database and
start netview off. It keeps finding an address on one of my routers that
is in fact somewhere else (it finds 12 interfaces instead of 11). I ask
for object properties and it says it is a card. If I do a locate route on
it, it goes through this router to get there but it is in fact a mainframe
on the next token ring along. Netview says this router has two cards on
this ring at addresses xx.xx.3.147 and xx.xx.3.3 (the 3.3 is the mainframe,
the 3.147 is correct).
If I go into properties for the router and look at the interfaces, it has
both IP addresses assigned to TKR/2 with the same MAC address.
If I clear the databases and restart Netview it comes back the same. If I
comment out my HSRP addresses in netmon seed and do likewise it does not
find the extra address.
I have 4 HSRP definitions (using the %) in my netmon.seed. This 3.3
address is not one of them (although I have 3.1 and 3.11 specified),
neither of which are currrently on 3.3.
Should I be using HSRP for these addresses which are in fact VIPAs (virtual
addresses that can come up on any mainframe)? I don't see what else I can
use. Surely this would not be confusing it?
Any info would greatly help.
Thanks,
Alan.
|