1smidiff(1)                         SMI Tools                        smidiff(1)
2
3
4

NAME

6       smidiff - check differences between a pair of SMI or SPPI modules
7

SYNOPSIS

9       smidiff  [  -Vhsm  ] [ -c file ] [ -l level ] [ -i error-pattern ] [ -p
10       module ] oldmodule newmodule
11

DESCRIPTION

13       The smidiff program is used to check differences between a pair of  SMI
14       MIB  modules  or  SPPI  PIB  modules.   E.g.,  it can be used to detect
15       changes in updated MIB modules that can cause interoperability problems
16       with  existing implementations. SMIv1/v2 and SPPI style MIB/PIB modules
17       are supported.
18
19       Note that conformance statements are currently not checked.
20
21       Messages describing the differences are written to the standard  output
22       channel  while  error  and warning messages generated by the parser are
23       written to the standard error channel.
24

OPTIONS

26       -V, --version
27              Show the smidump version and exit.
28
29       -h, --help
30              Show a help text and exit.
31
32       -s, --severity
33              Show the error severity in brackets before error messages.
34
35       -m, --error-names
36              Show the error names in braces before error messages.
37
38       -c file, --config=file
39              Read file instead of any other (global and  user)  configuration
40              file.
41
42       -p module, --preload=module
43              Preload  the  module  module  before reading the main module(s).
44              This may be helpful if  an  incomplete  main  module  misses  to
45              import some definitions.
46
47       -l level, --level=level
48              Report  errors  and warnings up to the given severity level. See
49              the smilint(1) manual page for a description of the  error  lev‐
50              els. The default error level is 3.
51
52       -i prefix, --ignore=prefix
53              Ignore all errors that have a tag which matches prefix.
54
55       oldmodule
56              The original module.
57
58       newmodule
59              The updated module.
60
61       If  a  module argument represents a path name (identified by containing
62       at least one dot or slash character), this is assumed to be  the  exact
63       file  to read. Otherwise, if a module is identified by its plain module
64       name, it is searched according to libsmi internal rules.  See  smi_con‐
65       fig(3) for more details.
66

SEE ALSO

68       The   libsmi(3)   project   is   documented   at  http://www.ibr.cs.tu-
69       bs.de/projects/libsmi/.
70

AUTHOR

72       (C) 2001 T. Klie, TU Braunschweig, Germany <tklie@ibr.cs.tu-bs.de>
73       (C) 2001 J. Schoenwaelder, TU Braunschweig, Germany <schoenw@ibr.cs.tu-
74       bs.de>
75       and contributions by many other people.
76
77
78
79IBR                             August 10, 2004                     smidiff(1)
Impressum