Some other causes for this are self-inflicted. You can
trick Netview into an incorrect discovery by putting more
than one interface in the seedfile for the same device. Or
by having name resolution that gives different names to
different  interfaces on the same device. Netview will
eventually figure it out and give some error messages
in the events display or in netmon.trace, but you will have
to delete the extra nodes and demandpoll the good nodes
to correct the problem. So only put a single, snmp-capable
address per node in the seedfile, and put the routers first,
is my advice.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking


Once NetView discovers a device by one interface he uses SNMP to get the
configuration and learn about other interfaces on that box.  So if you are
seeing duplicate routers with different interfaces on them, then most likely
your router is not responding to SNMP requests.  You should check the community
name among other things.

This information is covered in the NetView Diagnosis manual

James Shanks
Tivoli (NetView for UNIX) L3 Support



Seldom Seen <smokew AT HOTMAIL DOT COM> on 10/01/99 07:01:18 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Duplicate router discovery




Morning all

I've noticed during a large discover of the customer's network that
duplicate routers are being discovered with different interfaces on each.
Why is this happening and how can I remedy the problem?

THX in advance
Steyland

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com