Hello, We are trying to use the -f smiv1 option of smidump to create an SMIv1 version of an SMIv2 MIB module. In the SMIv1 output version, we expected that the SYNTAX of those MIB objects defined with textual conventions, would have been changed from the textual convention to the corresponding base SMIv1 syntax type. But none of the textual conventions were updated in the SMIv1 output version. Is our understanding correct of the -f smiv1 option on smidump?
Thanks,
Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com
Hi!
Kristine> We are trying to use the -f smiv1 option of smidump create Kristine> an SMIv1 version of an SMIv2 MIB module. In the SMIv1 Kristine> output version, we expected that the SYNTAX of those MIB Kristine> objects defined with textual conventions, would have been Kristine> changed from the textual convention to the corresponding Kristine> base SMIv1 syntax type. But none of the textual conventions Kristine> were updated in the SMIv1 output version. Is our Kristine> understanding correct of the -f smiv1 option on smidump?
The closest mapping of SMIv2 TC's to SMIv1 are usual ASN.1 type definitions (without changes to the OBJECT-TYPEs that use these types). This is what smidump does. If you made other observations please supply a concrete example.
-frank
participants (2)
-
Frank Strauss -
Kristine Adamson