📄 x-snmpgloss.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> SNMP General Glossary </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a></a><img border="0" src="icons/blank.gif"><a href="x-snmpErrors.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-snmpRefList.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h1 class="H1num" align="right"><i><a name="83417">D</a></i></h1></font><font face="Helvetica, sans-serif" class="sans"><h1 class="H1name" align="right"><i><a name="83419"> SNMP General Glossary</a></i></h1></font><dl class="margin"></dl><h4 class="Subtitle" align="right"><font face="Helvetica, sans-serif" size="-1" class="sans"><i></i></font></h4><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="83804"> </a></p><dd><p class="Body"><a name="83813"> </a></p><dd><p class="Body"><a name="83420"> </a>The following glossary includes general terms and their definitions useful in understanding SNMP.</p></dl></dl><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83421">ASN.1 (Abstract Syntax Notation One)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83422"> </a>A description language used to describe SNMP data types in a machine architecture-independent format.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83423">Basic Encoding Rules (BER)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83424"> </a>The Basic Encoding Rules describe how SNMP data should be encoded "on the wire," in such a way that machines with potentially very different architectures can understand it.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83425">CMIP (Common Management Information Protocol)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83426"> </a>The ISO-OSI network management protocol.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83427">connectionless protocols</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83428"> </a>Connectionless protocols allow packets between network correspondents to be routed individually rather than through a pre-established "connection," for example, IP.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83429">connection-oriented protocols</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83430"> </a>Connection-oriented protocols transmit packets between network correspondents along predetermined routes established at connection setup.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83431">Domain Name System (DNS)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83432"> </a>A networked database primarily used to identify mail handlers and resolve IP addresses from symbolic names.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83433">Internet Engineering Task Force (IETF)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83434"> </a>The Internet Engineering Task Force. A standards body responsible for standards development in the Internet community.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83435">instrumentation</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83610"> </a>Instrumentation refers to the system-dependent program code written by an agent developer to gather the information that can be accessed using SNMP. For example, the number of packets in and out of an interface must be counted so this information can be retrieved. The instrumentation does the counting.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83436">Internet Protocol (IP)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83437"> </a>IP is a connectionless network-layer protocol.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83438">ISO (International Standards Organization)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83439"> </a>A standards body responsible for many different kinds of standards. The "networking branch" of standards is usually referred to as the OSI.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83440">Management Information Base (MIB)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83441"> </a>Each SNMP agent implements a set of "managed objects." These objects are described in MIB documents written in the ASN.1 data description language.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83442">Method Routines</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83443"> </a>Routines which make up the interface between the Management Information Base (MIB) and the system routines that alter the variables which the MIB represents.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83444">MIB family</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83586"> </a>For the purpose of writing method routines, SNMP variables are separated into families. A family consists of all the leaf MIB variables with the same immediate parent node or root (the Object Identifier without the instance information). For example, in MIB-II, the following variables form a single family since they are all children of ifEntry (1.3.6.1.2.1.2.2.1):</p><dl class="margin"><dd><pre class="Code2"><b><a name="83445"></b><tt class="output">ifIndex 1.3.6.1.2.1.2.2.1.1</tt><b></a></b><dd> <b><a name="83446"></b><tt class="output">ifDescr 1.3.6.1.2.1.2.2.1.2 </tt><b></a></b><dd> <b><a name="83447"></b><tt class="output">...skipping entries between... </tt><b></a></b><dd> <b><a name="83448"></b><tt class="output">ifOutQLen 1.3.6.1.2.1.2.2.1.21 </tt><b></a></b><dd> <b><a name="83449"></b><tt class="output">ifSpecific 1.3.6.1.2.1.2.2.1.22</tt><b></a></b></pre></dl><dd><p class="Body"><a name="83450"> </a>Note that <b class="symbol_lc">ifNumber</b> (1.3.6.1.2.1.2.1) is also a member of the interfaces group; but it is not a member of the same family because it is not a child of <b class="symbol_lc">ifEntry</b>.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83451">MIB view</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83590"> </a>A MIB view is a collection of MIB subtrees that are either included or excluded from that particular view. That is, it defines a subset of all the managed objects at an SNMP entity.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83452">Object Identifier (OID)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83453"> </a>Each object in an SNMP MIB has an associated Object Identifier that uniquely identifies the object in a global tree of objects.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83454">Open Systems Interconnect (OSI)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83455"> </a>A set of networking standards endorsed by the ISO.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83456">RFC (Request for Comment)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83457"> </a>Documents maintained by the IETF standards body contain standards in various stages of completion. RFC documents are available over the Internet for no fee, and in printed form for a nominal printing charge.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83458">TCP (Transmission Control Protocol)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83459"> </a>The Transmission Control Protocol is a connection-oriented transport-layer protocol. It attempts to achieve reliability through retransmission.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83460">UDP (User Datagram Protocol)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83461"> </a>The User Datagram Protocol is a connectionless end-to-end transport-layer protocol.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83462">VarBind</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83597"> </a>An SNMP variable binding that includes the OID and the value (which may be NULL).</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="83463">VarBindList</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="83601"> </a>A list of instances of VarBind.</p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a></a><img border="0" src="icons/blank.gif"><a href="x-snmpErrors.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-snmpRefList.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -