I'm not sure what you are asking. /usr/OV/bin/mib2trap already understands the NOTIFICATION-TYPE construct, as does xnmloadmib2, though the latter does nothing with it. But mib2trap will create addtrap scripts for SNMP V2 MIBS which contain NOTIFICATION-TYPE statements. And trapd will parse SNMP V2 traps, so you can use mib2trap to create definitions for them if you have the MIBs.
As for your second question, there are conversion programs available on the web if your vendor is stubborn enough not to offer an SNMP V1 version of its V2 MIBs. Others, such as Cisco, offer both routinely. But I still have to ask, just what are you trying to accomplish here? As far as interpreting traps go, you don't need a conversion, unless you are looking for a verbal conversion of the MIB OID in trapd.log. The data will be fine.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group "Christopher J Petrina" <cjp8 AT meadwestvaco DOT com>
"Christopher J Petrina" <cjp8 AT meadwestvaco DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com
01/28/04 09:53 AM
Please respond to nv-l
To: nv-l AT lists.us.ibm DOT com
cc:
Subject: [nv-l] SNMPv2
Question. Is there no intention of Netview being able to support SMI-V2 structure. Mainly in the regards of NOTIFICATION-TYPE? And if not who has a suggestion about how to convert SMI-V2 style mibs back into a readable format for Netview.
