Have you modified your netmon.seed file to
define those IP addresses as HSRP?
# Hot Standby Routing
Protocol (HSRP) Support
#
# HSRP
interfaces may be specified here for netmon to acknowledge them.
# Only the public
IP address need be entered.
#
# Use the
prefix '%', and use the same syntax for ranges and wildcards
# described
above for positive seed entries. For instance, if 1.1.1.1
# is the IP
address of the HSRP interface that switches between two
# routers,
enter,
#
#
%1.1.1.1
From:
nv-l-bounces AT lists.ca.ibm DOT com [mailto:nv-l-bounces AT lists.ca.ibm DOT com] On Behalf Of Kain, Becki (B.)
Sent: Wednesday, May 16, 2007 8:58
AM
To: Tivoli NetView Discussions
Subject: [NV-L] Hsrp issue
we
continue to have this issue about hsrp. everytime a router, with hsrp,
fails over, netview creates a new fake device, for each interface, in the
map. then netview polls each of these fake devices, which is really on
the same router, and could be 30-40 times, and pegging 100% cpu on the router,
and taking them down. This is on netview 7.1.4 fp 4. we've been
told going to fp5 would probably fix this but it would probably break
everything else that we have
Ideas?
Thanks
