We have HSRP on almost all of our router interfaces, and have never had a
problem with SNMP data collection. Make sure that you are using a REAL IP
address for router A, and not the virtual HSRP address. Also, when an HSRP
failover occurs, make sure that NetView still has IP connectivity to router
A. If you're using HSRP, then you probably have multiple routes/paths in
your network between the NetView server and router A. If that's the case,
then make sure that there is a virtual loopback interface configured on the
router, and that is the only IP address that the name for router A resolves
to. Anytime there's an HSRP failover on router A, the routing tables will
be updated to re-establish a route to router A's loopback subnet, if there
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)456-4231 * mailto:Joel.Gerber AT USAA DOT com "
From: Chance, Larry [SMTP:lchance AT sfbcic DOT com]
Sent: Thursday, May 11, 2000 13:57
To: 'NetviewListSERVERUsers nv-l AT tkg DOT com'
Subject: [NV-L] Data Collection and HSRP
I have two remote routers that are set up with HSRP,
router A is Active and router B is Standby.
I was doing data collection on frame relay mibs on router A
when it went inactive, then router B became active.
Data collection has stopped on router A, but if you do a MIB
browse on the frame relay mibs everything seems normal.
Anyone have any ideas with how do I handle data collections in situations
thanks for any help.
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l