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

Tables

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 5 highlights

Send documentation comments to [email protected] Tables When network management protocols use names of MIB objects in messages, each name has an appended suffix. This suffix is called an instance identifier. It identifies one occurrence of the associated MIB object. For simple scalar objects, the instance identifier 0 refers to the instance of the object with that name (for example, sysUpTime.0). A MIB also can contain tables of related objects. For example, ifOperStatus is a MIB object inside the ifTable from the IF-MIB. It reports the operational state for an interface on a device. Because devices may have more than one interface, it is necessary to have more than one instance of ifOperStatus. This instance value is added to the end of the MIB object as the instance identifier (for example, ifOperStatus.2 reports the operational state for interface number 2). Each object in a table is constructed with a set of clauses defined by the SMI. These clauses include the SYNTAX clause, MAX-ACCESS clause, STATUS clause, and DESCRIPTION clause. An excerpt of the information in the VSAN table (known as vsanTable) from CISCO-VSAN-MIB follows: vsanTable OBJECT-TYPE SYNTAX SEQUENCE OF VsanEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of VSANs configured on this device." ::= { vsanConfiguration 3 } vsanEntry OBJECT-TYPE SYNTAX VsanEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) in the vsanTable." INDEX { vsanIndex } ::= { vsanTable 1 } VsanEntry ::= SEQUENCE { vsanIndex VsanIndex, vsanName SnmpAdminString, } In the example, vsanTable contains two variables: vsanIndex and vsanName. (There are more values in the actual vsanTable.) The index for this table is the ID of the VSAN, or vsanIndex. With n number of VSANs configured, n rows are present in the table. If you want to retrieve the vsanName that matches VSAN ID 3 (vsanIndex is 3), then you would issue an SNMP get for vsanName.3. 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
Tables
When network management protocols use names of MIB objects in messages, each name has an
appended suffix. This suffix is called an
instance identifier
. It identifies one occurrence of the associated
MIB object. For simple scalar objects, the instance identifier 0 refers to the instance of the object with
that name (for example, sysUpTime.0).
A MIB also can contain tables of related objects. For example, ifOperStatus is a MIB object inside the
ifTable from the IF-MIB. It reports the operational state for an interface on a device. Because devices
may have more than one interface, it is necessary to have more than one instance
of ifOperStatus
.
This
instance value is added to the end of the MIB object as the instance identifier (for example,
ifOperStatus.2 reports the operational state for interface number 2).
Each object in a table is constructed with a set of clauses defined by the SMI. These clauses include the
SYNTAX clause, MAX-ACCESS clause, STATUS clause, and DESCRIPTION clause.
An excerpt of the information in the VSAN table (known as vsanTable) from CISCO-VSAN-MIB
follows:
vsanTable OBJECT-TYPE
SYNTAX
SEQUENCE OF VsanEntry
MAX-ACCESS not-accessible
STATUS
current
DESCRIPTION
"A table of VSANs configured on this device."
::= { vsanConfiguration 3 }
vsanEntry OBJECT-TYPE
SYNTAX
VsanEntry
MAX-ACCESS not-accessible
STATUS
current
DESCRIPTION
"An entry (conceptual row) in the vsanTable."
INDEX { vsanIndex }
::= { vsanTable 1 }
VsanEntry ::= SEQUENCE {
vsanIndex
VsanIndex,
vsanName
SnmpAdminString,
}
In the example, vsanTable contains two variables: vsanIndex and vsanName. (There are more values in
the actual vsanTable.) The index for this table is the ID of the VSAN, or vsanIndex. With
n
number of
VSANs configured,
n
rows are present in the table. If you want to retrieve the vsanName that matches
VSAN ID 3 (vsanIndex is 3), then you would issue an SNMP
get
for vsanName.3
.