HP StorageWorks MSA 2/8 HP StorageWorks MIB V3.1.x/4.1.x Reference Guide (AA-R - Page 323

Connectivity Unit Link Table

Page 323 highlights

Fibre Alliance MIB Objects Note: Same as the string shown in the telnet command errShow. Connectivity Unit Link Table connUnitLinkTable OID Description 1.3.6.1.3.94.1.12 A list of links know to this agent from this connectivity unit to other connectivity units. X = switch data, Y = other end. Note: 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. That is, 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 which do not directly attach to members of its agency and its discovery algorithm gives some assurance the links are recently valid, it may include these links. Link information entered by administrative action may be included even if not validated directly if the link has at least one endpoint in this agency, but 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 by using GetNext. The value 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 are defined by the size of the table For an entry to be considered to be valid, both the X (local) and the Y (remote) need to have one valid value. MIB Version 3.1.x/4.1.x Reference Guide 323

  • 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
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394

Fibre Alliance MIB Objects
323
MIB Version 3.1.x/4.1.x Reference Guide
Note:
Same as the string shown in the telnet command
errShow
.
Connectivity Unit Link Table
connUnitLinkTable
Note:
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.
That is, 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 which do not directly attach to members of its
agency and its discovery algorithm gives some assurance the links are recently valid, it
may include these links.
Link information entered by administrative action may be included even if not validated
directly if the link has at least one endpoint in this agency, but 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
by using
GetNext
. The value 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 are
defined by the size of the table
For an entry to be considered to be valid, both the X (local) and the Y (remote) need to
have one valid value.
OID
1.3.6.1.3.94.1.12
Description
A list of links know to this agent from this connectivity unit to
other connectivity units. X = switch data, Y = other end.