nv-l
[Top] [All Lists]

Re: Not discovering non-snmp nodes

To: nv-l@lists.tivoli.com
Subject: Re: Not discovering non-snmp nodes
From: Leslie Clark <lclark@US.IBM.COM>
Date: Tue, 15 Dec 1998 08:50:20 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Put !@oid 1.3.*   in your seedfile (I'm doing this from memory so .. ) it
is just like any
other entry you would put in there to allow a particular oid, but with the
!, and make it
short enough that anything WITH snmp would pass.

I believe that this is the single greatest enhancement in Netview V5, and I
suspect it
was unintended. Either that, or the developers underestimated the need we
had for
this, since there is so little horn-blowing (and documentation) about it.

Be warned that when you use the !@oid function, whether to exclude all
non-snmp
or simply to exclude certain oids, you will still get stub objects in the
database. These
act as placeholders (I know you, I'm not supposed to discover you). This
means that
the object count goes up, and the ovwdb cache setting needs to be set high
enough
to accomodate this count, as always. Also, when you do the ovtopofix -a or
-A, you
will see lots and lots of hints and partial nodes deleted, knocking the
object count
back down again. This is normal. They will get 'found' again after a while.
But this
is all worth it, especially for customers who do not have a well-defined
adddressing
scheme.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web