HP StorageWorks 1606 Brocade Fabric OS MIB Reference v6.3.0 (53-1001339-01, Ju - Page 129

Entity MIB objects, SnmpEngineIdOrNone

Page 129 highlights

SnmpEngineIdOrNone 4 TABLE 10 Values port (10) stack (11) Possible values for PhysicalClass (Continued) Description The physical entity class is a networking port, capable of receiving or transmitting networking traffic. The physical entity class is a super-container (possibly virtual), intended to group together multiple chassis entities (such as a stack of multiple chassis entities). A stack might be realized by a virtual cable or a real interconnect cable attached to multiple chassis, or it can comprise multiple interconnect cables. A stack should not be modeled within any other physical entities, but a stack might be contained within another stack. Only chassis entities should be contained within a stack. SnmpEngineIdOrNone Syntax A specially formatted SnmpEngineID string for use with the Entity MIB. If an instance of an object with syntax SnmpEngineIdOrNone has a non-zero length, then the object encoding and semantics are defined by the SnmpEngineID textual convention (Refer to RFC 2571 [RFC2571]). If an instance of an object with syntax SnmpEngineIdOrNone contains a zero-length string, then no appropriate SnmpEngineID is associated with the logical entity (that is, SNMPv3 not supported). • For the Brocade 3016 or Brocade 4020 blades, the snmpEngineID takes the UUID value. For example, if the UUID value is A9914D56-1E5A-0E59-C51E-528802B06E4F, the snmpEngineID displays 80.00.06.34.B1.A9.91.4D.56.1E.5A.0E.59.C5.1E.52.88.02.B0.6E.4F (hex) • For other switches, the snmpEngineID takes the WWN. For example, if the WWN value is 10:00:00:05:1e:35:d5:ee, the snmpEngineID displays 80.00.06.34.B2.10.00.00.05.1E.35.D5.EE (hex) • If the WWN cannot be taken, the snmpEngineID takes the IP address + port number along with the private enterprise number and algorithm type used. An example of this type of snmpEngineID would be 00.00.06.34.00.00.00.A1.0A.20.93.CA (hex) OCTET STRING (SIZE(0..32)) Empty string or SnmpEngineID Entity MIB objects The Entity MIB objects are divided into the following groups: •Physical Entity group 112 •Logical Entity group 120 •Entity Mapping group 122 •General group 125 The following sections list the MIBs in each group. Fabric OS MIB Reference 111 53-1001339-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
  • 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

Fabric OS MIB Reference
111
53-1001339-01
SnmpEngineIdOrNone
4
SnmpEngineIdOrNone
A specially formatted SnmpEngineID string for use with the Entity MIB.
If an instance of an object with syntax SnmpEngineIdOrNone has a non-zero length, then the object
encoding and semantics are defined by the SnmpEngineID textual convention (Refer to RFC 2571
[RFC2571]).
If an instance of an object with syntax SnmpEngineIdOrNone contains a zero-length string, then no
appropriate SnmpEngineID is associated with the logical entity (that is, SNMPv3 not supported).
For the Brocade 3016 or Brocade 4020 blades, the snmpEngineID takes the UUID value. For
example, if the UUID value is
A9914D56-1E5A-0E59-C51E-528802B06E4F
, the snmpEngineID
displays
80.00.06.34.B1.A9.91.4D.56.1E.5A.0E.59.C5.1E.52.88.02.B0.6E.4F (hex)
For other switches, the snmpEngineID takes the WWN. For example, if the WWN value is
10:00:00:05:1e:35:d5:ee
, the snmpEngineID displays
80.00.06.34.B2.10.00.00.05.1E.35.D5.EE (hex)
If the WWN cannot be taken, the snmpEngineID takes the IP address + port number along with
the private enterprise number and algorithm type used. An example of this type of
snmpEngineID would be
00.00.06.34.00.00.00.A1.0A.20.93.CA (hex)
Syntax
OCTET STRING (SIZE(0..32))
Empty string or SnmpEngineID
Entity MIB objects
The Entity MIB objects are divided into the following groups:
Physical Entity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Logical Entity group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Entity Mapping group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
General group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
The following sections list the MIBs in each group.
port (10)
The physical entity class is a networking port, capable of receiving or transmitting networking
traffic.
stack (11)
The physical entity class is a super-container (possibly virtual), intended to group together
multiple chassis entities (such as a stack of multiple chassis entities). A stack might be
realized by a virtual cable or a real interconnect cable attached to multiple chassis, or it can
comprise multiple interconnect cables. A stack should not be modeled within any other
physical entities, but a stack might be contained within another stack. Only chassis entities
should be contained within a stack.
TABLE 10
Possible values for PhysicalClass
(Continued)
Values
Description