Blob Blame History Raw
.\" $Id: 7608 2008-01-22 13:05:41Z schoenw $
.TH smidump 1  "August 10, 2004" "IBR" "SMI Tools"
smidump \- dump SMI or SPPI modules in various formats
.B smidump
.B "-Vhqusmk"
] [
.BI "-c " file
] [
.BI "-o " name
] [
.BI "-p " module
] [
.BI "-l " level
] [
.BI "-f " format
.I "module(s)"
The \fBsmidump\fP program is used to dump the contents of a single MIB
or PIB
module or a collection of modules to stdout in a selectable output
format.  This format may be a simple tree of nodes, types or imported
modules, but also a format fully compliant to SMIv1, SMIv2, SPPI or SMIng or
CORBA IDL or C source code. Smidump can thus be used to convert
modules from SMIv2 to SMIng and from SMIng to SMIv2, or to develop
template based agent code.
\fB-V, --version\fP
Show the smidump version and exit.
\fB-h, --help\fP
Show a help text and exit. The help text contains a list of all
supported output formats.
\fB-c \fIfile\fB, --config=\fIfile\fP
Read \fIfile\fP instead of any other (global and user)
configuration file.
\fB-f \fIformat\fB, --format=\fIformat\fP
Use \fIformat\fP when dumping a module. Supported output formats are described 
below. The default output format is SMIng. The \fIformat\fP argument is
case insensitive.
\fB-l \fIlevel\fB, --level=\fIlevel\fP
Report errors and warnings up to the given severity \fIlevel\fP. See
the smilint(1) manual page for a description of the error levels. The
default error level is 3.
\fB-s, --severity\fP
Show the error severity in brackets before error messages.
\fB-m, --error-names\fP
Show the error names in braces before error messages.
\fB-o \fIname\fB, --output=\fIname\fB
Write the output in one or multiple files instead of stdout. The file
name(s) are derived from the \fIname\fP argument.  Not all format
support this option.
\fB-p \fImodule\fB, --preload=\fImodule\fP
Preload the module \fImodule\fP before reading the main module(s). This may
be helpful if an incomplete main module misses to import some definitions.
\fB-q, --quiet\fP
Suppress comments from dumped modules. What kind of information
gets suppressed depends on the output format.
\fB-u, --unified\fP
Dump a unified output in case of multiple \fImodule(s)\fP instead of
multiple concatenated output sections. This is not supported for all
output formats.
\fB-k, --keep-going\fP
Continue as much as possible after serious parse errors. Note that
the output generated after serious parse errors may be incomplete
and should be used with care.
.I module(s)
These are the module(s) to be dumped. If a module argument represents a
path name (identified by containing at least one dot or slash character),
this is assumed to be the exact file to read. Otherwise, if a module is
identified by its plain module name, it is searched according to libsmi
internal rules. See \fBsmi_config(3)\fP for more details.
The \fBsmidump\fP program supports the following output formats:
.TP 12
SMIng compliant format as defined in the SMIng Internet-Draft.
SMIv2 compliant format as defined in RFC 2578, RFC 2579, RFC 2580.
SMIv2 compliant format as defined in RFC 1155, RFC 1212, RFC 1215.
SPPI compliant format as defined in RFC 3159. If the underlying module
is not SPPI, there might be some mandatory information missing.
Format generated by the mosy compiler.
Import hierarchy of a module.
Types defined in a module.
OID registration tree structure of a module.
Metrics derived from a module (experimental).
List of identifiers defined in a module.
Compliance definitions with all included objects and notifications.
CORBA IDL and OID definitions following the JIDM specification translation
C source code files for usage within the net-snmp package (experimental).
ANSI C manager stubs for usage within the scli package (experimental).
Reverse engineered conceptual model in DIA XML file format (experimental).
SVG diagram of a module (experimental). Use with \fB-u\fP when dumping multiple \fImodules\fP.
Java AgentX sub-agent classes in separate files (experimental).
Perl represention of the MIB module
(contributed by Martin Schulz <>).
Python dictionaries represention of the MIB module
(contributed by Pat Knight <>).
SMI in XML format (experimental).
SMI in XML schema format (experimental).
SNMP best case / worst case RFC 3416 PDU sizes for typical PDUs
excluding SNMP message and transport headers (experimental).

This example converts the SMIv2 module IF-MIB in the current directory
to IF-MIB.sming in SMIng format. Note that the ./ prefix is used to
ensure reading the module from the current directory and not from a
place that libsmi guesses on its own.

  $ smidump -f sming ./IF-MIB > IF-MIB.sming
.BR libsmi (3)
project is documented at
.BR "" "."
.BR smilint "(1)"
(C) 1999-2004 F. Strauss, TU Braunschweig, Germany <>
(C) 1999-2002 J. Schoenwaelder, TU Braunschweig, Germany <>
(C) 2002-2003 J. Schoenwaelder, University of Osnabrueck, Germany
(C) 2003-2004 J. Schoenwaelder, International University Bremen, Germany
(C) 2001-2002 T. Klie, TU Braunschweig, Germany <>
(C) 2002 M. Bunkus, TU Braunschweig, Germany <>
and contributions by many other people.