On Wed, Jul 20, 2005 at 05:36:35PM -0400, R. Scott Baer wrote:
I guess what I'm asking here is is there an option read and SMIv1 mib, and output the oid in the xml, in a SMIv1 style.
The reason being, is on these old devices that supported SMIv1/SNMPv1 the traps that get sent across the wire are 1.3.6.1.4.1.4779.1 not 1.3.6.1.4.1.4779.0.1
An SNMPv1 agent will send on the wire
enterprise = 1.3.6.1.4.1.4779 generic-trap = enterpriseSpecific(6) specific-trap = 1
and not the notification OID 1.3.6.1.4.1.4779.1. See RFC 1157 section 4.1.6 for the PDU format and RFC 3584 section 3 for the details. If you see "1.3.6.1.4.1.4779.1" displayed somewhere, then I suspect that you are looking at a program which gets the translation wrong.
When I'm referring to the xml doc, I'm missing the traps.... When the device was created and mib were created, RFC 2576 was not published.
The conversion procedure is actually already described in RFC 1908 section 3.1.2 which dates back to 1996 (almost 10 years now). But once again, if the device sends an SNMPv1 trap, the error is more likely on the receiving side and not on the sending side. If in doubt, check the packet on the wire using tcpdump/ethereal/you name it.
If there is not an option, thats fine, I can program around that.
The libsmi simply does the right thing. We can't fix a bug that seems to be somewhere else by making libsmi do the wrong thing.
/js