
Happens with latest source.
Input:
FOO DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY FROM SNMPv2-SMI; fooMIB MODULE-IDENTITY LAST-UPDATED "200006270000Z" ORGANIZATION "Carrots Inc." CONTACT-INFO "Bugs Bunny" DESCRIPTION "Testing" REVISION "200006270000Z" DESCRIPTION "1 2 3" ::= {iso(1) member-body(2) us(840) 802dot3(10006) snmpmibs(300) 43 } fooObjects OBJECT IDENTIFIER ::= { fooMIB 1 }
Output (smidump --format=mosy FOO.my):
fooMIB snmpmibs.43 %n0 fooMIB module-identity fooObjects fooMIB.1 %n0 fooObjects object-id
The ancestry of snmpmibs is clearly stated in the input, but does not appear in the output.
I have access to a mosy descendent (still called mosy) that outputs
fooMIB 1.2.840.802.10006.300.43
(Rest of output is the same)
I don't think that smidump should necessarily produce identical output, but it ought to be possible to re-create the object ID.

On Tue, May 03, 2005 at 10:03:00PM -0400, Allen McIntosh wrote:
Happens with latest source.
[...]
I don't think that smidump should necessarily produce identical output, but it ought to be possible to re-create the object ID.
Please try the attached patch. The idea is to print out the numbered list in cases where the parent node of the module OID is not a real value assignment of an invocation of a macro.
/js
participants (2)
-
Allen McIntosh
-
Juergen Schoenwaelder