I think having wildcards in OID_TO_TYPE file would be a nice evolution, 
avoiding need to upgrade this file each time a new firmware is downloaded...

Luc Barnouin
Airsys ATM France


 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 AT USA.XEROX DOT COM> on 03/31/99 01:24:39 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: 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