2 .\" $Id: smidump.1.in 7608 2008-01-22 13:05:41Z schoenw $
4 .TH smidump 1 "August 10, 2004" "IBR" "SMI Tools"
6 smidump \- dump SMI or SPPI modules in various formats
24 The \fBsmidump\fP program is used to dump the contents of a single MIB
26 module or a collection of modules to stdout in a selectable output
27 format. This format may be a simple tree of nodes, types or imported
28 modules, but also a format fully compliant to SMIv1, SMIv2, SPPI or SMIng or
29 CORBA IDL or C source code. Smidump can thus be used to convert
30 modules from SMIv2 to SMIng and from SMIng to SMIv2, or to develop
31 template based agent code.
35 Show the smidump version and exit.
38 Show a help text and exit. The help text contains a list of all
39 supported output formats.
41 \fB-c \fIfile\fB, --config=\fIfile\fP
42 Read \fIfile\fP instead of any other (global and user)
45 \fB-f \fIformat\fB, --format=\fIformat\fP
46 Use \fIformat\fP when dumping a module. Supported output formats are described
47 below. The default output format is SMIng. The \fIformat\fP argument is
50 \fB-l \fIlevel\fB, --level=\fIlevel\fP
51 Report errors and warnings up to the given severity \fIlevel\fP. See
52 the smilint(1) manual page for a description of the error levels. The
53 default error level is 3.
56 Show the error severity in brackets before error messages.
58 \fB-m, --error-names\fP
59 Show the error names in braces before error messages.
61 \fB-o \fIname\fB, --output=\fIname\fB
62 Write the output in one or multiple files instead of stdout. The file
63 name(s) are derived from the \fIname\fP argument. Not all format
66 \fB-p \fImodule\fB, --preload=\fImodule\fP
67 Preload the module \fImodule\fP before reading the main module(s). This may
68 be helpful if an incomplete main module misses to import some definitions.
71 Suppress comments from dumped modules. What kind of information
72 gets suppressed depends on the output format.
75 Dump a unified output in case of multiple \fImodule(s)\fP instead of
76 multiple concatenated output sections. This is not supported for all
79 \fB-k, --keep-going\fP
80 Continue as much as possible after serious parse errors. Note that
81 the output generated after serious parse errors may be incomplete
82 and should be used with care.
85 These are the module(s) to be dumped. If a module argument represents a
86 path name (identified by containing at least one dot or slash character),
87 this is assumed to be the exact file to read. Otherwise, if a module is
88 identified by its plain module name, it is searched according to libsmi
89 internal rules. See \fBsmi_config(3)\fP for more details.
91 The \fBsmidump\fP program supports the following output formats:
94 SMIng compliant format as defined in the SMIng Internet-Draft.
97 SMIv2 compliant format as defined in RFC 2578, RFC 2579, RFC 2580.
100 SMIv2 compliant format as defined in RFC 1155, RFC 1212, RFC 1215.
103 SPPI compliant format as defined in RFC 3159. If the underlying module
104 is not SPPI, there might be some mandatory information missing.
107 Format generated by the mosy compiler.
110 Import hierarchy of a module.
113 Types defined in a module.
116 OID registration tree structure of a module.
119 Metrics derived from a module (experimental).
122 List of identifiers defined in a module.
125 Compliance definitions with all included objects and notifications.
128 CORBA IDL and OID definitions following the JIDM specification translation
132 C source code files for usage within the net-snmp package (experimental).
135 ANSI C manager stubs for usage within the scli package (experimental).
138 Reverse engineered conceptual model in DIA XML file format (experimental).
141 SVG diagram of a module (experimental). Use with \fB-u\fP when dumping multiple \fImodules\fP.
144 Java AgentX sub-agent classes in separate files (experimental).
147 Perl represention of the MIB module
148 (contributed by Martin Schulz <schulz@videotron.ca>).
151 Python dictionaries represention of the MIB module
152 (contributed by Pat Knight <pat@ktgroup.co.uk>).
155 SMI in XML format (experimental).
158 SMI in XML schema format (experimental).
161 SNMP best case / worst case RFC 3416 PDU sizes for typical PDUs
162 excluding SNMP message and transport headers (experimental).
165 This example converts the SMIv2 module IF-MIB in the current directory
166 to IF-MIB.sming in SMIng format. Note that the ./ prefix is used to
167 ensure reading the module from the current directory and not from a
168 place that libsmi guesses on its own.
171 $ smidump -f sming ./IF-MIB > IF-MIB.sming
176 project is documented at
177 .BR "http://www.ibr.cs.tu-bs.de/projects/libsmi/" "."
181 (C) 1999-2004 F. Strauss, TU Braunschweig, Germany <strauss@ibr.cs.tu-bs.de>
183 (C) 1999-2002 J. Schoenwaelder, TU Braunschweig, Germany <schoenw@ibr.cs.tu-bs.de>
185 (C) 2002-2003 J. Schoenwaelder, University of Osnabrueck, Germany
187 (C) 2003-2004 J. Schoenwaelder, International University Bremen, Germany
189 (C) 2001-2002 T. Klie, TU Braunschweig, Germany <tklie@ibr.cs.tu-bs.de>
191 (C) 2002 M. Bunkus, TU Braunschweig, Germany <bunkus@ibr.cs.tu-bs.de>
193 and contributions by many other people.