Brocade Fabric OS MIB Reference (53-1000241-01, November 2006)

4-16 Fabric OS MIB Reference

Publication Number: 53-1000241-01

entLPMappingEntry 1.3.6.1.2.1.47.1.3.1.1

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.

entAliasMappingEntry 1.3.6.1.2.1.47.1.3.2.1

Information about a particular physical equipment, logical entity to external identifier binding. Each

logical entity/physical component pair might be associated with one alias mapping. The logical entity

index might also be used as a wildcard (see “entAliasLogicalIndexOrZero 1.3.6.1.2.1.47.1.3.2.1.1” on

page 4-16 for details.)

Note that only entPhysicalIndex values that represent physical ports (that is, associated

entPhysicalClass value is “port(10)”) are permitted to exist in this table.

Index entPhysicalIndex

entAliasLogicalIndexOrZero

entAliasLogicalIndexOrZero 1.3.6.1.2.1.47.1.3.2.1.1

The value of this object identifies the logical entity that defines the naming scope for the associated

instance of the entAliasMappingIdentifier object.