[Top] [All Lists]

RE: [NV-L] Hsrp issue

To: "Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
Subject: RE: [NV-L] Hsrp issue
From: "Glen Warn" <Glen.Warn@pemcocorp.com>
Date: Wed, 16 May 2007 10:56:48 -0700
Delivery-date: Wed, 16 May 2007 20:05:58 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <4B7EE6C5FCFF304D9A1880844C82AE46021518F9@na1fcm08.dearborn.ford.com>
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com
Thread-index: AceX0vLHZeSdH0J5SLm3IZa8pVfZ5wADxKsw
Thread-topic: [NV-L] Hsrp issue

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

#      is the IP address of the HSRP interface that switches between two

#      routers, enter,


#         %


From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.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

NV-L mailing list
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web