Hi Scott,
We have certain situations where this is
the case for us too (typically behind firewalls) In our case, we either used
NAT on a router or firewall to advertise the duplicated address as something
unique to netview– or set the duplicate address to permanently unmanaged
(per advice from another user – see below) and then use snmp status
checking instead (on a uniquely addressed interface also on that device)
Hope this helps,
Glen
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On Behalf Of Paul
Sent: Thursday, May 12, 2005 9:28 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] How to permanently set nodes
to unmanged state
Glen,
If its a range of addresses you can add something
like this to the
seedfile:
!10.10.10.25-200 #Workstations
Or something like that. Im not sure how the
"limit discovery" puts it
in the seedfile off the top of my head.
Paul
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Bursik, Scott {PBSG}
Sent: Thursday, March 09, 2006
12:01 PM
To: nv-l@lists.us.ibm.com
Subject: [nv-l]Private Interfaces
and Duplicate IP addresses
NetView 7.1.4 AIX 5.2
We have a very large environment and we
are running into problems with duplicate IP addresses on private networks that
are being discovered by NetView through SNMP. Addresses like 192.168.1.x and 10.10.10.x
are being used in several areas and causing trouble with Node Down events
because of the duplication of addresses.
I was wondering what the community is
doing to combat this issue? We have been making the teams readdress the private
networks using NetView as the authoritative source for what private addresses
are being used but I was wondering if there is a better way to manage these
interfaces?
Thanks!
Scott Bursik
PepsiCo