Table of Contents
Advertisement
62
SNMP O
VERVIEW
Nodes
Object Identifiers
Relative and
Absolute Object
Identifiers
Specifying Object
Identifiers
Symbolically
The following list provides the nodes present in SNMPv2-SMI MIB:
•
org OBJECT IDENTIFIER ::= {iso 3}
dod OBJECT IDENTIFIER ::= {org 6}
•
internet OBJECT IDENTIFIER ::= {dod 1}
•
directory OBJECT IDENTIFIER ::= {internet 1}
•
mgmt OBJECT IDENTIFIER ::= {internet 2}
•
•
mib-2 OBJECT IDENTIFIER ::= {mgmt 1}
transmission OBJECT IDENTIFIER ::= {mib-2 10}
•
•
experimental OBJECT IDENTIFIER ::= {internet 3}
private OBJECT IDENTIFIER ::= {internet 4}
•
enterprises OBJECT IDENTIFIER ::= {private 1}
•
•
security OBJECT IDENTIFIER ::= {internet 5}
snmpV2 OBJECT IDENTIFIER ::= {internet 6}
•
•
snmpDomains OBJECT IDENTIFIER ::= {snmpV2 1}
snmpProxys OBJECT IDENTIFIER ::= {snmpV2 2}
•
snmpModules OBJECT IDENTIFIER ::= {snmpV2 3}
•
This section provides information on object identifiers including:
Relative and Absolute Object Identifiers
•
Specifying Object Identifiers Symbolically
•
•
Object Identifier with Instance Indexes
As previously discussed, you can access a variable using the root of the OID tree.
For example, the Q1 Labs object identifier .1.3.6.1.4.1.20212 specifies the path
from the root of the tree. These are called absolute OIDs. However, a path to the
variable may be specified relative to some node in the OID tree. For example,
2.1.1.7 specifies the sysContact object in the system group, relative to the internet
(.1.3.6.1) node in the OID tree. This is called a relative OID.
You can describe an OID using integers separated by dots, such as,
.1.3.6.1.4.1.20212. However, you can also express an OID symbolically, or by a
combination of both integers and textual symbols. A symbolic OID uses mnemonic
keywords to specify the managed object, for example,
gmt.mib-2.system.sysDescr.
The following numeric OID uses integers to specify the same managed object:
2.1.1.1
STRM SNMP Agent
Advertisement
Table of Contents
