nv-l
[Top] [All Lists]

Re: Regarding the OID_TO_TYPE file and discovery of device!!!!

To: nv-l@lists.tivoli.com
Subject: Re: Regarding the OID_TO_TYPE file and discovery of device!!!!
From: "Sharma, Sanjeev" <Sanjeev.Sharma@USA.XEROX.COM>
Date: Thu, 1 Apr 1999 05:34:57 -0800
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>
thanks a lot for your all helps and suggestions.
sanjeev

-----Original Message-----
From: Leslie Clark [mailto:lclark@US.IBM.COM]
Sent: Wednesday, March 31, 1999 11:17 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: Regarding the OID_TO_TYPE file and discovery of device!!!!


You can edit the file, which I find to be quicker than using the eui, but I
only do that if I
am going to use the exact same vendor and agent values.

To find all of the needed entries at once, here's what I do (and I do about
one install a week).
Make a collection of snmp supported devices for which vendor is unset.
After an initial,
wide-ranging discovery, pick through the members of the collection, noting
the exact oid,
and figuring out the vendor and agent from the description. To handle
multiples, I use Locate
by oid, view...highlights...select highlights, Options..ack. If it is an
oid for something I may want
to exclude, I make a note of that, too (those can be wildcarded in the
seedfile, fortunately).
After I've updated the oid_to_type file, I go back to the collection and
delete all of the nodes
so that they are rediscovered with the vendor set. You can check that
collection from time to
time to see if there are any new oids to handle.

The oid_to_type for 5.1, I was pleased to see, has lots and lots of devices
in it that I used to
have to put in by hand. Especially Cisco. Still, everywhere I go there are
a bunch of different
ones, and some vendors sure can proliferate oids!

Cordially,

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



 Netview look for the whole sysObjectID.
>Is there any other way around to fix these kind of repeatation?
Not currently.


Tivoli Verification - RTP



"Sharma, Sanjeev" <Sanjeev.Sharma@USA.XEROX.COM> on 03/31/99 01:24:39 PM

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

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: Mark Sklenarik)
Subject:  Regarding the OID_TO_TYPE file and discovery of device!!!!





hi to all
My question is related to the sysObjectID of the device which we used to
entered in the oid_to_type file.
In my case  e.g sysObjectID is 1.3.6.1.4.1.253.8.62.1.3.2.3.1 for one
version of printer firmware.
The last octet in the sysObjectID change according to the version of next
printer firmware so may be nxt time it will be
"1.3.6.1.4.1.253.8.62.1.3.2.3.2". So in this case i will have to enter all
the different OIDs for each and every type of version.
So tell me at the time of discovery, Netview look for whole sysObjectID or
portion of it.
Is there any other way around to fix these kind of repeatation?
thanks a lot for any type of help....

regards
sanjeev

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Regarding the OID_TO_TYPE file and discovery of device!!!!, Sharma, Sanjeev <=

Archive operated by Skills 1st Ltd

See also: The NetView Web