For devices with more than one address, I see this quite a bit when name
resolution is incomplete. This is most prevalent at current maintenance
levels. It finds a router by an unnamed address, then finds it by a named
address, and makes two devices, and when it tries to complete the
discovery by pulling the address table, it complains about duplicate
addresses. You won't have this problem if you are excruciatingly tidy about
name resolution, or if you have no name resolution at all. If you name them
in DNS, make sure the name resolution works in both directions.
If this is what is going on, the two symbols will have different object ids
in Tools...Display Object Info). If they are two symbols for the SAME
you have something that I would call a clear defect and should call
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
When I have an new object discovered that is in fact a duplicate of an
object, I always check the subnetwork mask of the object. In our
this is usually the cause. If a device gets setup with the wrong mask,
show up in NetView in the areas of map placement and re-discovery.
I do have one router that continually re-discovers as a duplicate resource.
the masks are set correctly, so this is not always the problem. I plan to
problem with support when I get a chance.
Hope this helps,
Ahold Information Services
Marcos Pezzutti <pezzutti AT BANESPA.COM DOT BR> on 12/28/99 11:26:34 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
<NV-L AT UCSBVM.ucsb DOT edu>
To: NV-L AT UCSBVM.ucsb DOT edu
cc: (bcc: Dean Grant/AIS/US/Ahold)
Subject: Models duplicated
Anyone could explain what causes the re-appearance (re-discovery) of a
resource if it is already in database (topology and object) ?
We are observing the re-discovery of some objects besides they are already
modeled on both databases and located on some views (maps)
What could be wrong in our environment ?
Marcos Antonio Pezzutti Filho
Analista de Sistemas
e-mail: pezzutti AT banespa.com DOT br