On Wed, Jul 20, 2005 at 04:43:12PM -0400, R. Scott Baer wrote:
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.
Let me see whether I understand your question.
You have a TRAP-TYPE definition with enterprise = 1.3.6.1.4.1.4779 and a specifc trap value of 1. smidump generates the notification OID 1.3.6.1.4.1.4779.0.1 and you believe this is wrong and you expect 1.3.6.1.4.1.4779.1.
The relevant document here is RFC 3584 (which obsoletes RFC 2576) and in particular section 3.1 transformation (2):
(2) If the SNMPv1 generic-trap parameter is 'enterpriseSpecific(6)', the SNMPv2 snmpTrapOID parameter SHALL be the concatenation of the SNMPv1 enterprise parameter and two additional sub- identifiers, '0', and the SNMPv1 specific-trap parameter.
I think this text clearly supports what libsmi does.
/js