Entlpmappingentry - HP StorageWorks MSA 2/8 - SAN Switch Reference Manual

Description

entLPMappingEntry

OID
Description
Index
MIB Version 3.1.x/4.1.x Reference Guide
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 that are used to realize that logical entity.
An agent should limit the number and nature of entries in this
table such that only meaningful and non-redundant
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.
For example, 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, on the other hand, 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.
1.3.6.1.2.1.47.1.3.1.1
Information a,t 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.
entLogicalIndex
entLPPhysicalIndex
Entity MIB Objects
183