HP Cisco Nexus 5000 Cisco MDS 9000 Family MIB Quick Reference (OL-18087-01, Fe - Page 4

Interpreting the MIB Structure, Object Identifiers

Get HP Cisco Nexus 5000 - Converged Network Switches PDF manuals and user guides View all HP Cisco Nexus 5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 4 highlights

Send documentation comments to [email protected] Use the SNMP-TARGET-MIB to obtain more information on trap destinations and inform requests. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for more information on configuring traps and informs. Note Notifications must be enabled through SNMP, Fabric Manager, or the CLI. Refer to the Cisco MDS 9000 Family CLI Configuration Guide. Interpreting the MIB Structure A MIB presents the managed data in a logical tree hierarchy, using an IETF standard syntax called the Structure of Management Information (SMI). Branches of this MIB tree are organized into individual tables, which contain the managed data as leaf objects. Understanding these concepts is fundamental to interpreting the management information provided by the MIB. This section provides the following information: • Object Identifiers, page 4 • Tables, page 5 • SYNTAX Clause, page 6 • MAX-ACCESS Clause, page 6 • AGENT-CAPABILITIES, page 7 Object Identifiers The MIB structure is logically represented by a tree hierarchy. The root of the tree is unnamed and splits into three main branches: Consultative Committee for International Telegraph and Telephone (CCITT), International Organization for Standardization (ISO), and joint ISO/CCITT. These branches and those that fall below each category have short text strings and integers to identify them. Text strings describe object names, while integers allow computer software to create compact, encoded representations of the names. Each MIB variable is assigned an object identifier. The object identifier is the sequence of numeric labels on the nodes along a path from the root to the object. For example, the MIB variable tftpHost is indicated by the number 1. The object identifier for tftpHost is iso.org.dod.internet.private.enterprise.cisco.workgroup products.stack group.tftp group.tftpHost or .1.3.6.1.4.1.9.5.1.5.1. The last value is the number of the MIB variable tftpHost. Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA © Cisco Systems, Inc. All rights reserved.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
Send documentation comments to [email protected]
Americas Headquarters:
© <2009> Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706
USA
Use the SNMP-TARGET-MIB to obtain more information on trap destinations and inform requests.
Refer to the
Cisco MDS 9000 Family CLI Configuration Guide
for more information on configuring traps
and informs.
Note
Notifications must be enabled through SNMP, Fabric Manager, or the CLI. Refer to the
Cisco MDS 9000
Family CLI Configuration Guide.
Interpreting the MIB Structure
A MIB presents the managed data in a logical tree hierarchy, using an IETF standard syntax called the
Structure of Management Information (SMI). Branches of this MIB tree are organized into individual
tables, which contain the managed data as leaf objects. Understanding these concepts is fundamental to
interpreting the management information provided by the MIB.
This section provides the following information:
•
Object Identifiers, page 4
•
Tables, page 5
•
SYNTAX Clause, page 6
•
MAX-ACCESS Clause, page 6
•
AGENT-CAPABILITIES, page 7
Object Identifiers
The MIB structure is logically represented by a tree hierarchy. The
root
of the tree is unnamed and splits
into three main branches: Consultative Committee for International Telegraph and Telephone (CCITT),
International Organization for Standardization (ISO), and joint ISO/CCITT.
These branches and those that fall below each category have short text strings and integers to identify
them. Text strings describe
object names
, while integers allow computer software to create compact,
encoded representations of the names.
Each MIB variable is assigned an object identifier. The
object identifier
is the sequence of numeric labels
on the nodes along a path from the root to the object. For example, the MIB variable tftpHost is indicated
by the number 1. The object identifier for tftpHost is
iso.org.dod.internet.private.enterprise.cisco.workgroup products.stack group.tftp group.tftpHost or
.
1.3.6.1.4.1.9.5.1.5.1
. The last value is the number of the MIB variable tftpHost.