Brocade Fabric OS MIB Reference Guide v6.0.0 (53-1000602-01, April 2008)

Fabric OS MIB Reference 111

53-1000602-01

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.