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