x-mibcompout.html

vxworks相关论文

1.3.6.1                        internet                NODE 
1.3.6.1.1                        directory                NODE 
1.3.6.1.2                        mgmt                NODE 
1.3.6.1.3                        experimental                NODE 
1.3.6.1.4                        private                NODE 
1.3.6.1.4.1                        enterprises                NODE 
1.3.6.1.4.1.731                        wrs                NODE 
1.3.6.1.4.1.731.8                        examples                NODE 
1.3.6.1.4.1.731.8.1                        ex1                NODE 
1.3.6.1.4.1.731.8.1.1                        ex1Objs                NODE 
1.3.6.1.4.1.731.8.1.1.1                        ex1Obj1                LEAF        ExampleType 
1.3.6.1.4.1.731.8.1.1.2                        ex1Obj2                LEAF        OCTET STRING 
1.3.6.1.4.1.731.8.2                        ex2                NODE 
1.3.6.1.4.1.731.8.2.1                        ex2Objs                NODE 
1.3.6.1.4.1.731.8.2.1.1                        ex2Obj1                LEAF        ExampleType 
1.3.6.1.4.1.731.8.2.1.2                        ex2Obj2                LEAF        OCTET STRING 
1.3.6.1.4.1.731.8.2.2                        ex2Traps                NODE 
1.3.6.1.4.1.731.8.2.2.1                        ex2Trap                NODE</a></b></pre>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="83531"><b class="command">-partial</b> </a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code"><b><a name="83532">mibcomp -partial -o partial.out example.mib</a></b></pre>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="83533"> </a>The <b class="command">-partial</b> output mode generates a new skeletal MIB file,suitable for compilation by <b class="command">mibcomp</b>. The new file consists of <b class="symbol_UC">OBJECT-TYPE</b> macros for every object in the MIB, even ones thatare not accessible. This file is meant to be used as the basis of a control file with <b class="symbol_UC">FORCE-INCLUDE</b>, <b class="symbol_UC">EXCLUDE</b> and <b class="symbol_UC">DEFAULT</b> keywords in it to control the implementation of the MIB.</p>
<dd><p class="Body"><a name="83536"> </a>An alternate version of this mode, <b class="command">-partialm</b>, is described in <a href="x-mibcompOut.html#83541"><i class="title">-partialm</i></a>.</p>
<dd><p class="Body"><a name="83538"> </a>Here is an example of <b class="command">mibcomp</b> output when given the <b class="command">-partial</b> option:</p>
</dl>

<dl class="margin">

<dd><pre class="Code"><b><a name="83539">-- This file was automatically generated by Wind River Systems' 
-- mibcomp SNMP MIB Compiler. 
-- This file was generated using the -partial switch. 
-- 
-- YOU MAY MODIFY THIS FILE BUT BEWARE ACCIDENTALLY OVERWRITING IT 
-- BY REGENERATING IT WITH THE MIB COMPILER. 
-- 
-- Last build date: Fri May 26 22:06:22 1995 
-- from files: 
-- example1.mib, example2.mib, examples.ctl 
 
partial-out-A 
 
-- put your FORCE-INCLUDE's here 
-- 
-- put your global DEFAULT's here 
-- 
-- put your EXCLUDE's here 
-- 
 
DEFINITIONS ::= BEGIN 
 
IMPORTS 
        OBJECT-TYPE 
                FROM SNMPv2-SMI; 
 
-- Below is an OBJECT-TYPE entry for every object in the input MIBs. 
-- You may position DEFAULT statements at any point in the MIB tree 
-- by putting them inside the appropriate OBJECT-TYPE declaration. 
-- You need not modify any to which you don't want to add DEFAULTs. 
-- (Or, you may remove any OBJECT-TYPE declaration to which you 
-- don't add DEFAULT statements, as long as you don't add DEFAULT 
-- statements to any of its descendants that reference its 
-- descriptor, directly or indirectly.) 
 
org OBJECT-TYPE 
        ::= { iso 3 } 
 
dod OBJECT-TYPE 
         { org 6 } 
 
internet OBJECT-TYPE 
         { dod 1 } 
 
directory OBJECT-TYPE 
         { internet 1 } 
 
mgmt OBJECT-TYPE 
         { internet 2 } 
 
experimental OBJECT-TYPE 
         { internet 3 } 
 
private OBJECT-TYPE 
         { internet 4 } 
 
enterprises OBJECT-TYPE 
         { private 1 } 
 
wrs OBJECT-TYPE 
         { enterprises 731 } 
 
examples OBJECT-TYPE 
         { wrs 3 } 
 
ex1 OBJECT-TYPE 
         { examples 1 } 
 
ex1Objs OBJECT-TYPE 
         { ex1 1 } 
 
ex1Obj1 OBJECT-TYPE 
         { ex1Objs 1 } 
 
ex1Obj2 OBJECT-TYPE 
         { ex1Objs 2 } 
 
ex2 OBJECT-TYPE 
         { examples 2 } 
 
ex2Objs OBJECT-TYPE 
         { ex2 1 } 
 
ex2Obj1 OBJECT-TYPE 
         { ex2Objs 1 } 
 
ex2Obj2 OBJECT-TYPE 
         { ex2Objs 2 } 
 
ex2Traps OBJECT-TYPE 
         { ex2 2 } 
 
ex2Trap OBJECT-TYPE 
         { ex2Traps 1 } 
 
END</a></b></pre>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="83541"><b class="command">-partialm </b></a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code"><b><a name="83542">mibcomp -partialm EXAMPLE-SNMPv1-MIB -o partialm.out example.mib</a></b></pre>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="83543"> </a>The <b class="command">-partialm</b> output mode generates a new skeletal MIB file,suitable for compilation by <b class="command">mibcomp</b>. The new file consists of empty <b class="symbol_UC">OBJECT-TYPE</b> macros for every object in the specified MIB module (<b class="symbol_UC">EXAMPLE-MIB</b> in this example). This file is meant to be used as the basis of a control file with <b class="symbol_UC">FORCE-INCLUDE</b>, <b class="symbol_UC">EXCLUDE</b> and <b class="symbol_UC">DEFAULT</b> keywords in it to control the implementation of the MIB (see <a href="x-mibcomp4.html#83542"><i class="title">A.4.2&nbsp;mibcomp Extensions</i></a>).</p>
<dd><p class="Body"><a name="83547"> </a>If any <b class="symbol_UC">DEFAULT</b> statements are present in the input files and apply to the specified MIB module, they are included in the <b class="command">-partialm</b> output.</p>
<dd><p class="Body"><a name="83550"> </a>An alternate version of this output mode, <b class="command">-partial</b>, is described in <a href="x-mibcompOut.html#83531"><i class="title">-partial</i></a>.</p>
<dd><p class="Body"><a name="83552"> </a>Here is an example of <b class="command">mibcomp</b> output when given the <b class="command">-partialm</b> option:</p>
</dl>

<dl class="margin">

<dd><pre class="Code"><b><a name="83553">-- This file was automatically generated by Wind River Systems' 
-- <b class="command">mibcomp</b> SNMP MIB Compiler. 
-- This file was generated using the -partialm switch. 
-- 
-- YOU MAY MODIFY THIS FILE BUT BEWARE ACCIDENTALLY OVERWRITING IT 
-- BY REGENERATING IT WITH THE MIB COMPILER. 
-- 
-- Last build date: Fri May 26 22:06:23 1995 
-- from files: 
-- example1.mib, example2.mib, examples.ctl 
 
EXAMPLE-SNMPv2-MIB-A 
 
-- put your FORCE-INCLUDE's here 
- 
-- put your global DEFAULT's here 
-- 
-- put your EXCLUDE's here 
-- 
 
DEFINITIONS ::= BEGIN 
 
IMPORTS 
        enterprises, OBJECT-TYPE 
                FROM SNMPv2-SMI; 
 
-- Below is an OBJECT-TYPE entry for every object in the 
-- EXAMPLE-SNMPv2-MIB MIB module. 
-- You may position DEFAULT statements at any point in the MIB tree 
-- by putting them inside the appropriate OBJECT-TYPE declaration. 
-- You need not modify any to which you don't want to add DEFAULTs. 
-- (Or, you may remove any OBJECT-TYPE declaration to which you 
-- don't add DEFAULT statements, as long as you don't add DEFAULT 
-- statements to any of its descendants that reference its 
-- descriptor, directly or indirectly.) 
 
wrs OBJECT-TYPE  
        ::= { enterprises 731 } 
 
examples OBJECT-TYPE 
        DEFAULT test-function it_exists 
        DEFAULT get-function get_%n 
        DEFAULT set-function set_%n 
        DEFAULT next-function std_next 
        DEFAULT cookie (char *) &amp;var_%n 
        ::= { wrs 8 } 
 
ex2 OBJECT-TYPE 
        DEFAULT view-mask 0xDEADBEEF 
        ::= { examples 2 } 
 
ex2Objs OBJECT-TYPE 
        ::= { ex2 1 } 
 
ex2Obj1 OBJECT-TYPE 
        ::= { ex2Objs 1 } 
 
ex2Obj2 OBJECT-TYPE 
        DEFAULT cookie ((void *) 0) 
        ::= { ex2Objs 2 } 
 
ex2Traps OBJECT-TYPE 
        ::= { ex2 2 } 
 
ex2Trap OBJECT-TYPE 
        ::= { ex2Traps 1 } 
 
END</a></b></pre>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="83555"><b class="command">-readtree</b> </a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code"><b><a name="83556">mibcomp -readtree -o readtree.out example.mib</a></b></pre>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="83557"> </a>The <b class="command">-readtree</b> output mode generates an ASCII text file that a manager can load at run-time to look up object identifiers by name.This is essentially the same information that <b class="command">mibcomp</b> generates inthe <b class="command">-loadtree</b>, <b class="command">-nametree</b>, and <b class="command">-numbers</b> output modes. The only real difference is that this version is intended to be loaded at run-time by a manager that understands the text format.</p>
<dd><p class="Body"><a name="83558"> </a>The <b class="command">-readtree</b> output contains four kinds of lines:</p>
</dl>

<dl class="margin">

<p><ol class="List"><li value="1)"><a name="83559"> </a>Comment lines, which begin with a semicolon character(<b class="symbol_lc">;</b>).</li></ol></p>
<p><ol class="List"><li value="2)"><a name="83560"> </a>MIB object lines, which consist of the <b class="symbol_lc">$obj</b> token, the object's <b class="symbol_UC">OID</b>, the name of the object, and a token indicating the object's data type (unknown or useless types are represented by <b class="symbol_lc">"0"</b>).</li></ol></p>
<p><ol class="List"><li value="3)"><a name="83872"> </a>Enumeration lines for enumerated integers, which consist of the <b class="symbol_lc">$enum</b> token, the object's <b class="symbol_UC">OID</b>, and the name and value of the enumerated value in the standard MIB format.</li></ol></p>
<p><ol class="List"><li value="4)"><a name="83873"> </a>Index lines for <i class="emphasis">conceptual row objects</i>, which consist of the <b class="symbol_lc">$indx</b> token, the <b class="symbol_UC">OID</b> of the conceptual row object, and the <b class="symbol_UC">OID</b> of the object that is an index for the conceptual row; these lines are only present if you installed the <b class="symbol_UC">MIBCOMP_READTREE_INDX</b> option when you built <b class="command">mibcomp</b>.</li></ol></p>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="83563"> </a>All fields are separated by horizontal whitespace (one or more <kbd>SPACE</kbd> or <kbd>TAB</kbd> characters).</p>
<dd><p class="Body"><a name="83564"> </a>This format is intended to be simple enough that it can be parsed by ageneral purpose text processor such as the UNIX <b class="command">awk</b> utility.</p>
<dd><p class="Body"><a name="83565"> </a>If you're looking for a human-readable ASCII text representation of a MIB, please see the <b class="command">-numbers</b> output mode described in <a href="x-mibcompOut.html#83515"><i class="title">-numbers</i></a>. For a binary representation of the same information, see the descriptions of the output modes <b class="command">-loadtree</b> (<a href="x-mibcompOut.html#83448"><i class="title">-loadtree</i></a>) and <b class="command">-nametree</b> (<a href="x-mibcompOut.html#84057"><i class="title">-nametree</i></a>).</p>
<dd><p class="Body"><a name="83575"> </a>Here is an example of <b class="command">mibcomp</b> output when given the <b class="command">-readtree</b> option:</p>
</dl>

<dl class="margin">

<dd><pre class="Code"><b><a name="83576">; This file was automatically generated by Wind River Systems'