I am not certain what question you are asking here.

The default discovery behavior for NetView is, was, and always has been, to
reach the next network and stop.  The next network will be unmanaged.   You
can change this by managing the network from the map GUI or by adding an
address in that next network to the seedfile, but then you should take your
range out of it.  A range will limit discovery to just what is in the
seedfile.   Sounds like you might profitably read about seedfiles in the
Installation and Configuration manual.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Drew Wall <drwall AT TEKSYSTEMS DOT COM> on 02/05/99 04:55:27 PM

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)
Subject:  Ethernet port on Remote Routers?





Has anyone run into this problem?
Solaris 2.5.1
NV 5.1
Only the serial ports on the customer's remote routers (Cisco) are being
discovered.  The ethernet port on each router is identified, but labeled
unmanaged, therefore NV is not discovering anything beyond the remote
routers.  I think it may have to do with the seed file, but it appears
correct.  The relevant addresses listed are 10.*.0.* and 10.*.*.0-50.
The routers ethernet ports are 10.*.*.1 so they should get discovered.
Is there a default max. 'hops' that NV uses to limit the discovery?

Background info:
- Communities are used but they are correct.  Verified through 'spot'
checks.
--
========================================================
Drew Wall
Enterprise Management
TEKsystems
mailto:drwall AT teksystems DOT com
http://www.teksystems.com
========================================================

drwall.vcf
Description: Binary data