Hi, Please excuse me if this has been ask in the past, I did search the mailing list before writing this e-mail.
My question is when I'm trying to convert a SMIv1 mib to xml, the notification oid adds an extra 0, I believe this should only be done, if you wan the resulting xml out in SMIv2 representation. I did look up the extra 0 thing (section 3 http://www.mibdepot.com/downloads/rfcs/rfc2576.txt ), it is is valid if you want to convert a MIB from SMIv1 to SMIv2.
I'm trying to convert the following mib to xml http://www.baytech.net/downloads/gpm/bayuniv-4014.mib with the following command:
smidump -f xml ../mibs/bayuniv-4014.mib -o ./xml/bayuniv-4014.xml
header of xml: <module name="Baytech-MIB-401-4" language="SMIv1" />
the first trap:
<notifications> <notification name="communicationLost" oid="1.3.6.1.4.1.4779.0.1" status="current"> <objects> <object module="Baytech-MIB-401-4" name="mtrapargsTimeTicks" /> </objects> <description>SEVERE: Communication to the unit has been lost. Steps to reestablish communication are in progress. Argument is timeTicks when communication was lost.</description> </notification>
the oid should be: 1.3.6.1.4.1.4779.1 I know this mib has other issues, but for now, I would like to address this one. Any suggestions ???
Scott