| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
TCP/IP MIB Object Descriptors and Identifiers and the Object Name Hierarchy and Name Notation (Page 4 of 4) Recursive Definition of MIB Object Identifiers An object is given a text object descriptor by putting its name at the start of the object as shown in Table 207, but the definition of numeric object identifiers is, again, more complex. It is done by defining only the number of the object within its particular subtree. This means the object identifiers are defined recursively (one based on another) and are not explicitly stated for each object. Syntactically precise, but makes it hard to see at a glance what the number is for any particular object. Consider again the example in Table 207. For this object, sysLocation is the object descriptor, and { system 6 } is the object identifier. This means it is object number 6 within the node system, which is in turn defined as { mib-2 1 }it is the first node within the mib-2 subtree. Since mib-2 is, as we said above, 1.3.6.1.2.1, this means system is 1.3.6.1.2.1.1 and sysLocation is 1.3.6.1.2.1.1.6.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||