Jim;

Be very careful in using OID's in your seed file.  When an OID is contained in a
seed file, NetView will create a stub object in your database for EACH and EVERY
device it finds on your network.  These objects are not real objects, but a sort
of a marker telling NetView not to consider that device again in autodiscovery.
Still, depending on the size of your network, you are talking about a very huge
database just to keep all those stubs lying around.

If your going to use OID's, you might as well use only OID's.  That way, you
will only discover the OID's in your seed file, and you don't have to worry
about IP address ranges at all.

But what I would do is try and document your hubs and add them manually using
the loadhosts command.  We have found that if you can't define a range of ip
addresses for a particular type of object, it is a big hassle trying to keep the
NetView database clean of extraneous devices.

Art DeBuigny
Bank of America Network Operations
debuigny AT dallas DOT net
art.debuigny AT bankofamerica DOT com

"Brunke, Jim (FUSA)" wrote:

> We are building a Netview server which will exclusively manage routers,
> switches and hubs on our network - and I need some advice on the best way to
> setup for initial discovery.
>
> We have build a seedfile which contains an entry for each our routers &
> switches.  The first 5 address of a subnet is reserved for router interfaces
> so we limit discovery of other nodes in the network (servers and
> workstations) by excluding all other addresses, ie:
>
> !167.85.*.6-254
> !168.118.*.6-254
>
> One problem is that we do not have a well defined list of IP addresses for
> all of the hubs on the network.  They are a combination of Cisco and Bay
> hubs.  Could I also add two @OID entries into the seedfile to discover these
> nodes?  I know if you list an snmp reachable IP address in the seedfile, it
> will ignore the ! range exclusion and discover the node.  Does the @OID work
> similarly?
>
> Thanks, in advance