HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 246

connUnitLinkTable 1.3.6.1.3.94.1.12

Page 246 highlights

8 connUnitLinkTable 1.3.6.1.3.94.1.12 connUnitLinkTable 1.3.6.1.3.94.1.12 A list of links known to this agent from this connectivity unit to other connectivity units: X is switch data and Y is other end. The link table is intended to organize and communicate any information the agent has that might assist a management application to discover the connectivity units in the framework and the topology of their interconnect: the goal is to assist the management application by mapping the elements of the framework in addition to listing them. With this goal, the agent should include as much as it possesses about any links from its own connectivity units to others, including links among its own units. An agent should include partial information about links if it is not able to fully define them in accord with the following structure; however, the information must include either a nonzero connUnitNodeId-or a nonzero connUnitPortWwn-for each end of the link. If the agent is able to discover links that do not directly attach to members of its agency and its discovery algorithm gives some assurance that the links are recently valid, it might include these links. Link information entered by administrative action might be included even if not validated directly if the link has at least one endpoint in this agency, but it should not be included otherwise. A connectivity unit should fill the table in as best it can. One of the methods to fill this in would be to use the RNID ELS command (ANSI document 99-422v0). This command queries a port for the information needed for the link table. This table is accessed either directly, if the management software has an index value, or using getNext. The values of the indexes are not required to be contiguous. Each entry created in this table is assigned an index. This relationship is kept persistent until the entry is removed from the table or the system is reset. The total number of entries is defined by the size of the table. For an entry to be considered valid, both the X (local) and the Y (remote) values need to have one valid value. A Brocade Access Gateway has no ISLs (InterSwitch Links); therefore all F_Port and N_Port connections display in ag --show for online F_Ports. connUnitLinkEntry 1.3.6.1.3.94.1.12.1 Index An entry describing a particular link to another. connUnitLinkUnitId connUnitLinkIndex connUnitLinkUnitId 1.3.6.1.3.94.1.12.1.1 Values The connUnitId of the connectivity unit that contains this link table. Set to WWN of the local switch. 230 Fabric OS MIB Reference 53-1000439-01

  • 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
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296

230
Fabric OS MIB Reference
53-1000439-01
connUnitLinkTable 1.3.6.1.3.94.1.12
8
connUnitLinkTable 1.3.6.1.3.94.1.12
A list of links known to this agent from this connectivity unit to other connectivity units: X is switch
data and Y is other end.
The link table is intended to organize and communicate any information the agent has that might
assist a management application to discover the connectivity units in the framework and the
topology of their interconnect: the goal is to assist the management application by mapping the
elements of the framework in addition to listing them.
With this goal, the agent should include as much as it possesses about any links from its own
connectivity units to others, including links among its own units.
An agent should include partial information about links if it is not able to fully define them in accord
with the following structure; however, the information must include either a nonzero
connUnitNodeId—or a nonzero connUnitPortWwn—for each end of the link.
If the agent is able to discover links that do not directly attach to members of its agency and its
discovery algorithm gives some assurance that the links are recently valid, it might include these
links.
Link information entered by administrative action might be included even if not validated directly if
the link has at least one endpoint in this agency, but it should not be included otherwise.
A connectivity unit should fill the table in as best it can. One of the methods to fill this in would be to
use the RNID ELS command (ANSI document 99-422v0). This command queries a port for the
information needed for the link table.
This table is accessed either directly, if the management software has an index value, or using
getNext
. The values of the indexes are not required to be contiguous. Each entry created in this
table is assigned an index. This relationship is kept persistent until the entry is removed from the
table or the system is reset. The total number of entries is defined by the size of the table.
For an entry to be considered valid, both the X (local) and the Y (remote) values need to have one
valid value.
A Brocade Access Gateway has no ISLs (InterSwitch Links); therefore all F_Port and N_Port
connections display in ag --show for online F_Ports.
connUnitLinkEntry 1.3.6.1.3.94.1.12.1
An entry describing a particular link to another.
Index
connUnitLinkUnitId
connUnitLinkIndex
connUnitLinkUnitId 1.3.6.1.3.94.1.12.1.1
The connUnitId of the connectivity unit that contains this link table.
Values
Set to WWN of the local switch.