IBM 2109 Service Guide - Page 91

mgmt2 experimental3, enterprise1

Get IBM 2109 - SAN Fibre Channel Switch Model S16 PDF manuals and user guides
UPC - 087944519355
View all IBM 2109 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

example, the MIB variable, sysDescr, defines the description of an agent system. The existence of a particular value for an MIB object in the agent system is known as an MIB object instance, or simply instance. Some MIB objects have only a single instance for a given agent system. For example, the system description and the instance are denoted as sysDescr.0. Other MIB objects have multiple instances, for example, the operational status of each fibre-channel port on a switch, where a particular instance can be denoted as swFCPortOperStatus.5. Figure 28 shows that MIB objects are conceptually organized in a hierarchical tree structure. Each branch in the tree has a unique name and numeric identifier. Intermediate branches of the tree serve as a way to group related MIB objects together. The leaves of the tree represent the actual MIB objects. Figure 28 illustrates the tree structure, with special attention to the internet MIB tree and the fibre-channel MIB tree. | iso(1) org(3) dod6) internet(1) directory(1) mgmt(2) experimental(3) private(4) mib-2(1) fibreChannel(42) enterprise(1) system(1) interface(2) fcFe(1) IBM 2109 sysObjectID(2) sysDescr(1) fcFabric(2) commDev(2) | Figure 28. MIB tree SJ000021 An MIB object is uniquely identified or named by its position in the tree. A full object identifier consists of each branch along the path through the tree. For example, the object sysObjectID has the full identifier of 1.3.6.1.2.1.1.2. For readability, notation can be used, for example {system 1}. The switch agent supports the following: v SNMPv1 and SNMPv2c v Command line utilities to provide access to configure the agent v MIB-II system group, interface group, and SNMP group v Fabric element MIB v Vendor-specific MIBs v Standard generic traps Chapter 7. Management tools 75

  • 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
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
example, the MIB variable,
sysDescr
, defines the description of an agent system.
The existence of a particular value for an MIB object in the agent system is known
as an MIB object instance, or simply instance. Some MIB objects have only a single
instance for a given agent system. For example, the system description and the
instance are denoted as
sysDescr.0
. Other MIB objects have multiple instances, for
example, the operational status of each fibre-channel port on a switch, where a
particular instance can be denoted as
swFCPortOperStatus.5
.
Figure 28 shows that MIB objects are conceptually organized in a hierarchical tree
structure. Each branch in the tree has a unique name and numeric identifier.
Intermediate branches of the tree serve as a way to group related MIB objects
together. The leaves of the tree represent the actual MIB objects. Figure 28
illustrates the tree structure, with special attention to the internet MIB tree and the
fibre-channel MIB tree.
An MIB object is uniquely identified or named by its position in the tree. A full object
identifier consists of each branch along the path through the tree. For example, the
object
sysObjectID
has the full identifier of
1.3.6.1.2.1.1.2
. For readability,
notation can be used, for example
{system 1}
.
The switch agent supports the following:
v
SNMPv1 and SNMPv2c
v
Command line utilities to provide access to configure the agent
v
MIB-II system group, interface group, and SNMP group
v
Fabric element MIB
v
Vendor-specific MIBs
v
Standard generic traps
SJ000021
iso(1)
org(3)
dod6)
internet(1)
directory(1)
iso(1)
mgmt(2) experimental(3)
private(4)
mib-2(1)
fibreChannel(42)
enterprise(1)
system(1)
interface(2)
fcFe(1)
IBM 2109
commDev(2)
fcFabric(2)
sysDescr(1)
sysObjectID(2)
Figure 28. MIB tree
Chapter 7. Management tools
75
|
|