|
|
This chapter describes the individual MIB objects that comprise SNMPv2. The objects reside in the SNMPv2-MIB.my file.
Contents of this chapter include:
The system group comprises a collection of objects that is common to all managed systems.
The following is the main object identifier for the snmpMIBObjects:
::= { mib-2 1 }
The object identifier for each MIB object is listed in Table 7-1. For possible values for the system group, see Table 1-8.
| Name | Object Identifier |
|---|---|
sysDescr | ::= { system 1 } |
sysObjectID | ::= { system 2 } |
sysUpTime | ::= { system 3 } |
sysContact | ::= { system 4 } |
sysName | ::= { system 5 } |
sysLocation | ::= { system 6 } |
sysServices | ::= { system 7 } |
The MIB objects are listed inTable 7-2.
| Name | Syntax | Description | Default Value | |||
|---|---|---|---|---|---|---|
DisplayString (SIZE (0..255)) | Defines the textual description of the entity. This value includes a the full name and version identification of the system hardware type, software operating system, and networking software. Max-Access: read-only Status: current | none | ||||
OBJECT IDENTIFIER | Specifies the vendor authoritative identification of the network management subsystem that is contained in the entity. This value is allocated within the Structure of Management Information (SMI) enterprise subtree 1.3.6.1.4.1. It provides an easy and unambiguous means for determining the type of box being managed. For example, if vendor Flintstones, Inc., is assigned the subtree 1.3.6.1.4.1.4242, it can assign the identifier 1.3.6.1.4.1.4242.1.1 to Fred Router. For the possible OID values assigned to Max-Access: read-only Status: current | none | ||||
TimeTicks | Determines the time (in hundredths of a second) since the network management portion of the system is last reinitialized. Max-Access: read-only Status: current | none | ||||
DisplayString (SIZE (0..255)) | Specifies the textual identification of the contact person for this managed node along with information on how to contact this person. If no contact information is known, the value is the zero-length string. Max-Access: read-write Status: current | none | ||||
DisplayString (SIZE (0..255)) | Determines an administrative-assigned name for this managed node. By convention, this is the node fully-qualified domain name. If the name is unknown, the value is the zero-length string. Max-Access: read-write Status: current | none | ||||
DisplayString (SIZE (0..255)) | Determines the physical location of this node, for example, telephone closet, third floor. If the location is unknown, the value is the zero-length string. Max-Access: read-write Status: current | none | ||||
INTEGER (0..127) | Indicates the value for the set of services that this entity can potentially offer. The value is a sum. This sum initially takes the value zero. For each layer, L, in the range Max-Access: read-only Status: current For systems including Open System Interconnection (OSI) protocols, layers 5 and 6 can also be counted.
The following are the supported layers: | none | ||||
| Layer | Function | |||||
1 | Physical—Supports repeaters. | |||||
2 | Datalink/Subnetwork—Supports bridges. | |||||
3 | Internet—Supports Internet Protocol (IP). | |||||
4 | End-To-End—Supports Transmission Control Protocol (TCP). | |||||
7 | Application—Supports Simple Management Transfer Protocol (SMTP). | |||||
The object resource information comprises a collection of objects, which describe the SNMPv2 entity either statically or dynamically configured to support various MIB modules.
The object identifier for each MIB object is shown in Table 7-3. For the values that are used for the object resource information, see Table 1-8.
| Name | Object Identifier |
|---|---|
sysORLastChange | ::= { system 8 } |
sysORTable | ::= { system 9 } |
sysOREntry | ::= { sysORTable 1 } |
sysORIndex | ::= { sysOREntry 1 } |
sysORID | ::= { sysOREntry 2 } |
sysORDescr | ::= { sysOREntry 3 } |
sysORUpTime | ::= { sysOREntry 4 } |
The MIB objects are listed in Table 7-4.
| Name | Syntax | Description | Default Value | |
|---|---|---|---|---|
TimeStamp | Specifies the value of sysUpTime at the time of the most recent change in state or value of any instance of sysORID. Max-Access: read-only Status: current | none | ||
SEQUENCE OF SysOREntry | Lists the capabilities of the local SNMPv2 entity that acts as an agent role with respect to various MIB modules. SNMPv2 entities, which are dynamically-configured to support MIB modules, can have a dynamically-varying number of conceptual rows. Max-Access: not-accessible Status: current | none | ||
SysOREntry | Contains an entry (conceptual row) in the sysORTable. Max-Access: not-accessible Status: current The index contains sysORIndex. | none | ||
INTEGER (1..2147483647) | Specifies the auxiliary variable that is used to identify instances of the columnar objects in the sysORTable. Max-Access: not-accessible Status: current | none | ||
OBJECT IDENTIFIER | Specifies an authoritative identification of a capabilities statement with respect to various MIB modules. They are supported by the local SNMPv2 entity that acts as an agent role. Max-Access: read-only Status: current | none | ||
DisplayString | Defines a textual description of the capabilities identified by the corresponding instance of sysORID. Max-Access: read-only Status: current | none | ||
TimeStamp | Specifies the value sysUpTime at the time this conceptual row is last instantiated. Max-Access: read-only Status: current | none | ||
The SNMP group comprises a collection of objects that provides the basic instrumentation and control of an SNMP entity.
The following is the main object identifier for snmp:
::= { mib-2 11 }
The object identifier for each MIB object is listed in Table 7-5. For values that are used for the SNMP group, see Table 1-8.
| Name | Object Identifier |
|---|---|
snmpInPkts | ::= { snmp 1 } |
snmpInBadVersions | ::= { snmp 3 } |
snmpInBadCommunityNames | ::= { snmp 4 } |
snmpInBadCommunityUses | ::= { snmp 5 } |
snmpInASNParseErrs | ::= { snmp 6 } |
snmpEnableAuthenTraps | ::= { snmp 30 } |
snmpSilentDrops | ::= { snmp 31 } |
snmpProxyDrops | ::= { snmp 32 } |
The SNMP Group MIB objects are listed in Table 7-6.
| Name | Syntax | Description | Default Value | |||
|---|---|---|---|---|---|---|
Counter32 | Specifies the total number of messages delivered to the SNMP entity from the transport service. Max-Access: read-only Status: current | none | ||||
Counter32 | Determines the total number of SNMP messages delivered to the SNMP entity and used for an unsupported SNMP version. Max-Access: read-only Status: current | none | ||||
Counter32 | Determines the total number of SNMP messages delivered to the SNMP entity that used a SNMP community name not known to the said entity. Max-Access: read-only Status: current | none | ||||
Counter32 | Determines the total number of SNMP messages delivered to the SNMP entity that represented a SNMP operation. It is not allowed by the SNMP community named in the message. Max-Access: read-only Status: current | none | ||||
Counter32 | Determines the total number of ASN.1 or Basic Encoding rules (BER) errors encountered by the SNMP entity when decoding received SNMP messages. Max-Access: read-only Status: current | none | ||||
INTEGER { enabled(1), disabled(2) } | Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information. It provides a means whereby all authenticationFailure traps are disabled.
Max-Access: read-write Status: current | none | ||||
Counter32 | Determines the total number of GetRequest-PDU, GetNextRequest-PDU, GetBulkRequest-PDU, SetRequest-PDU, and InformRequest-PDU delivered to the SNMP entity. The Max-Access: read-only Status: current | none | ||||
Counter32 | Determines the total number of GetRequest-PDU, GetNextRequest-PDU, GetBulkRequest-PDU, SetRequest-PDU, and InformRequest-PDU delivered to the SNMP entity. The Max-Access: read-only Status: current | none | ||||
The notification information comprises a collection of objects, which allow the SNMPv2 entity, when acting as an agent role, to be configured to generate the SNMPv2-Trap-PDU.
The following is the main object identifier for the snmpTrap:
::= { snmpMIBObjects 4 }
The object identifier for each MIB object is listed in Table 7-7. For values that are used for the information for notification, see Table 1-8.
| Name | Object Identifier |
|---|---|
snmpTrapOID | ::= { snmpTrap 1 } |
snmpTrapEnterprise | ::= { snmpTrap 3 } |
The MIB objects are listed inTable 7-8.
| Name | Syntax | Description | Default Value | |
|---|---|---|---|---|
OBJECT IDENTIFIER | Specifies the authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2-Trap-PDU and InformRequest-PDU. Max-Access: accessible-for-notify Status: current | none | ||
OBJECT IDENTIFIER | Specifies the authoritative identification of the enterprise associated with the trap currently being sent. When a SNMPv2 proxy agent is mapping an RFC1157Trap-PDU into a SNMPv2-Trap-PDU, this variable occurs as the last varbind. Max-Access: accessible-for-notify Status: current | none | ||
The following is the main object identifier for the snmpTraps:
::= { snmpMIBObjects 5 }
 |
Note Both linkDown (::= { snmpTraps 3 })and linkUp (::= { snmpTraps 4 }) traps are defined in RFC 1573. RFC 1213 defines egpNeighborLoss (::= { snmpTraps 6 }). |
The object identifier for each MIB object is listed in Table 7-9. For possible values for the traps, see Table 1-8.
| Name | Object Identifier |
|---|---|
coldStart | ::= { snmpTraps 1 } |
warmStart | ::= { snmpTraps 2 } |
authenticationFailure | ::= { snmpTraps 5 } |
The MIB objects are listed inTable 7-10.
| Name | Syntax | Description | Default Value | |
|---|---|---|---|---|
none | Signifies the SNMPv2 entity acts as an agent role. This trap reinitializes itself so the configuration is altered. Status: current | none | ||
none | Signifies the SNMPv2 entity acts as an agent role This trap reintializes itself so the configuration is unaltered. Status: current | none | ||
none | Signifies the SNMPv2 entity acts as an agent role. This trap receives a protocol message that is not properly authenticated. While all implementations of the SNMPv2 must be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap is generated. Status: current | none | ||
The set group comprises a collection of objects, which allow several cooperating SNMPv2 entities, all acting as a manager role, to coordinate their use of the SNMPv2 set operation.
The following is the main object identifier for snmpSet:
::= { snmpMIBObjects 6 }
The object identifier for the MIB object is listed in Table 7-11. For values that are used for the set group, see Table 1-8.
| Name | Object Identifier |
|---|---|
snmpSetSerialNo | ::= { snmpSet 1 } |
One MIB object is listed inTable 7-12 for the set group.
| Name | Syntax | Description | Default Value | |
|---|---|---|---|---|
TestAndIncr | Specifies an advisory lock used to allow several cooperating SNMPv2 entities, which all act as a manager role, to coordinate their use of the SNMPv2 set operation. This object is used for coarse-grain coordination. To achieve fine-grain coordination, one or more similar objects are appropriately defined within each MIB group. Max-Access: read-write Status: current | none | ||
The information on conformance is specific to SNMPv2. Table 7-13 lists the groups.
| Name | Object Identifier |
|---|---|
snmpMIBConformance | ::= { snmpMIB 2 } |
snmpMIBCompliances | ::= { snmpMIBConformance 1 } |
snmpMIBGroups | ::= { snmpMIBConformance 2 } |
The compliance statement is used to support SNMPv2. The following are the mandatory groups:
The compliance object identifier is listed in Table 7-14.
| Name | Object Identifier |
|---|---|
snmpCommunityGroup | ::= { snmpMIBCompliances 2 } |
A list of the MIB objects is listed in Table 7-15.
| Name | Syntax | Description | Default Value | |
|---|---|---|---|---|
none | Specifies the compliance statement for the SNMPv2 entities that implement the SNMPv2 MIB. Status: current | none | ||
none | Supports community-based authentication. This group is mandatory for SNMPv2 entities. | none | ||
The object identifiers for each MIB object is listed in Table 7-16.
| Name | Object Identifier |
|---|---|
snmpGroup | ::= { snmpMIBGroups 8 } |
snmpCommunityGroup | ::= { snmpMIBGroups 9 } |
snmpSetGroup | ::= { snmpMIBGroups 5 } |
systemGroup | ::= { snmpMIBGroups 6 } |
snmpBasicNotificationsGroup | ::= { snmpMIBGroups 7 } |
The SNMPv2 units of conformance objects are listed in Table 7-17.
| Name | Objects | Description | Default Value | |
|---|---|---|---|---|
snmpInPkts, | Specifies a collection of objects that provides instrumentation and control of an SNMPv2 entity. Status: current | none | ||
snmpInBadCommunity | Specifies a collection of objects that provides basic instrumentation of a SNMPv2 entity that supports community-based authentication. Status: current | none | ||
snmpSetSerialNo | Specifies a collection of objects that allows several cooperating SNMPv2 entities, which all act as a manager role to coordinate their use of the SNMPv2 set operation. Status: current | none | ||
sysDescr, | Defines objects that are common to all managed systems for the system group. Status: current | none | ||
coldStart, authenticationFailure | Specifies the two notifications that an SNMPv2 entity is required to implement. Status: current | none | ||
Posted: Fri Sep 15 12:03:37 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.