Carefull with using any OID's in your seed file. If you use them, then
any and all nodes that do not fit your OID seed entries will be added
to the database in the form of a hint. Not as large of an object as a
full blown object, but an object none the less. For me it created a
hint for every nonsnmp device in my network. I went from a 40,000
object database to 120,000. The ovmapcount to remove these hints took
hours.
The hints are created so that NetView won't try to discover them on its
next autodiscovery pass.
About the only way I can think of to catch all SNMP nodes if you don't
have IP addressing standards is to allow all items in, run scripts
against your objects to weed out isSNMPEnabled=False entries, and then
generate a customized seed file using a script. Then you should
probably place your OID free seed file, and rediscover your network.
This does present a problem for new devices, though. Will they be
within your seed file range? Are you informed when new manageable
devices are added to the network?
I think I'm going to add a suggestion to the NetView suggestion mailbox.
Here is how I think it should work.....
Create a seperate database file for hints. They would not need to be
cleaned. They would not impact the boxes performance. That way, OID's
could be used in a seed file without impacting the servers performance
(and database optimization times).
Good luck!
Art DeBuigny
Bank of America Network Operations
debuigny@dallas.net
Donald Davis wrote:
>
> Ek C.
> I do not think that I would recommend using this !!!
> It is my understanding that whenever a negative OID is used in the
> seed file it causes all
> matching nodes to be populated into the object database with a "stub"
> entry containing
> the IP Address and a few other fields. That means that every non-snmp
> node would have a
> "stub" entry in the database but not appear on the map.
>
> I would have done it as indicated below in a December 15th post from
> Jane Curry.
> This "positive" seed file entry would not impact the database.
> Please get back to us (good or bad) with database impact using the
> negative (!@oid) entry.
> Thanks,
> Don Davis
>
> > To totally prevent discovery of non-SNMP nodes in NetView V5, specify as
> > a statement in the seedfile:
> > @oid 1.3.6.1.*
> >
> > This specifies the total group of SNMP-nodes with OIDs beginning with
> > 1.3.6.1. Non-SNMP-devices are not included in this group, thus they are
> > excluded from discovery.
> >
> > Cheers, Jane
> > --
> > Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
> > Tel: +44 (0)1628 782565
> > Copyright (c) 1998 Jane Curry . All rights
> > reserved.
> >
>
>
>
> > Sam Rudland wrote:
> >
> > > Does anyone know of a way to get Netmon to discover objects from a
> > > seedfile
> > > that have an SNMP Time-out problem, but put them on the IP Internet level
> > > submap in the 'new objects holding area' instead of burying them deep
> > > within a LAN object?
> > >
> > > Many thanks in advance,
> > >
> > > Sam Rudland
> >
> > You may discover only SNMP devices by putting !@oid 0 at the end of your
> > seed
> > file.
> >
> > Ek C.
> >
> --
> =================================================
> Don Davis - Consultant, Instructor
> Alliance of Professionals & Consultants, Inc.
> 8600 Caswell Court
> Raleigh, NC 27613-1100 USA Phone: 919-847-6056
> Pager: 800-759-8888 PIN# 1462396
> Email: Don@apc-services.com
> Visit our web site at http://www.apc-services.com
> =================================================
>
|