nv-l
[Top] [All Lists]

RE: [nv-l] Interface added and deleted traps

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Interface added and deleted traps
From: "Barr, Scott" <Scott_Barr@csgsystems.com>
Date: Wed, 9 Jun 2004 10:48:37 -0500
Delivery-date: Wed, 09 Jun 2004 17:00:09 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcROOLkXehuYGleTQJeMhYf9rWWfmwAAEMnA
Thread-topic: [nv-l] Interface added and deleted traps
You probably have a duplicate IP address amongst the devices generating
those traps. Actually, NETMON is generating those traps - they are not
coming from the device. What happens is netmon discovers a device with
address xx.xx.xx.xx. When it continues discovery and finds another one
with the same address, netmon will delete the first one from topology.
Later, when discovery gets around to these devices again, the problem
will reoccur. This should not happen if the duplicate interface is an
HSRP/redundant interface.

I hope that helps. 

> -----Original Message-----
> From: owner-nv-l@lists.us.ibm.com 
> [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Brian W Green
> Sent: Wednesday, June 09, 2004 10:33 AM
> To: Netview Mailing List
> Subject: [nv-l] Interface added and deleted traps
> 
> I am seeing a lot of Interface XXX Deleted followed by 
> Interface XXX Added traps in the trapd.log file.  Our network 
> people took a look at the devices throwing these traps, and 
> they do not report any error for this.  All of these traps 
> are netmon-generated.
> 
> Does anyone have an idea on what I can do to quiet this 
> behaviour down?
> 
> Thanks,
> 
> Brian
> 
> Brian W. Green
> IBM Certified Deployment Professional
> CGI Information Systems and Management Consulting
> 275 Slater Street, 14th Floor
> Ottawa, Ontario
> K1P 5H9
> (613) 234-2155
> brian.green@cgi.com
> 
> 
> 


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web