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

Entity Mapping Group, entLPMappingTable 1.3.6.1.2.1.47.1.3.1

Page 127 highlights

Entity Mapping Group 4 Entity Mapping Group entLPMappingTable 1.3.6.1.2.1.47.1.3.1 This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources used to realize that logical entity. An agent should limit the number and nature of entries in this table such that only meaningful and nonredundant information is returned. For example, in a system that contains a single power supply, mappings between logical entities and the power supply are not useful and should not be included. Also, only the most appropriate physical component that is closest to the root of a particular containment tree should be identified in an entLPMapping entry. Suppose a bridge is realized on a particular module and all ports on that module are ports on this bridge. A mapping between the bridge and the module would be useful, but additional mappings between the bridge and each of the ports on that module would be redundant (since the entPhysicalContainedIn hierarchy can provide the same information). If, however, more than one bridge was utilizing ports on this module, then mappings between each bridge and the ports it used would be appropriate. Also, in the case of a single backplane repeater, a mapping for the backplane to the single repeater entity is not necessary. entLPMappingEntry 1.3.6.1.2.1.47.1.3.1.1 Information about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized. Index entLogicalIndex entLPPhysicalIndex entLPPhysicalIndex 1.3.6.1.2.1.47.1.3.1.1.1 The value of this object identifies the index value of a particular entPhysicalEntry associated with the indicated entLogicalEntity. entAliasMappingTable 1.3.6.1.2.1.47.1.3.2 This table contains zero or more rows, representing mappings of logical entity and physical component to external MIB identifiers. Each physical port in the system might be associated with a mapping to an external identifier, which itself is associated with a particular logical entity's naming scope. A wildcard mechanism is provided to indicate that an identifier is associated with more than one logical entity. Fabric OS MIB Reference 111 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

Fabric OS MIB Reference
111
53-1000439-01
Entity Mapping Group
4
Entity Mapping Group
entLPMappingTable 1.3.6.1.2.1.47.1.3.1
This table contains zero or more rows of logical entity to physical equipment associations. For each
logical entity known by this agent, there are zero or more mappings to the physical resources used
to realize that logical entity.
An agent should limit the number and nature of entries in this table such that only meaningful and
nonredundant information is returned. For example, in a system that contains a single power
supply, mappings between logical entities and the power supply are not useful and should not be
included.
Also, only the most appropriate physical component that is closest to the root of a particular
containment tree should be identified in an entLPMapping entry.
Suppose a bridge is realized on a particular module and all ports on that module are ports on this
bridge. A mapping between the bridge and the module would be useful, but additional mappings
between the bridge and each of the ports on that module would be redundant (since the
entPhysicalContainedIn hierarchy can provide the same information). If, however, more than one
bridge was utilizing ports on this module, then mappings between each bridge and the ports it
used would be appropriate.
Also, in the case of a single backplane repeater, a mapping for the backplane to the single repeater
entity is not necessary.
entLPMappingEntry
1.3.6.1.2.1.47.1.3.1.1
Information about a particular logical entity to physical equipment association. Note that the
nature of the association is not specifically identified in this entry. It is expected that sufficient
information exists in the MIBs used to manage a particular logical entity to infer how physical
component information is utilized.
Index
entLogicalIndex
entLPPhysicalIndex
entLPPhysicalIndex 1.3.6.1.2.1.47.1.3.1.1.1
The value of this object identifies the index value of a particular entPhysicalEntry associated with
the indicated entLogicalEntity.
entAliasMappingTable 1.3.6.1.2.1.47.1.3.2
This table contains zero or more rows, representing mappings of logical entity and physical
component to external MIB identifiers.
Each physical port in the system might be associated with a
mapping to an external identifier, which itself is associated with a particular logical entity’s naming
scope.
A wildcard mechanism is provided to indicate that an identifier is associated with more than
one logical entity.