HP StorageWorks Fabric OS 5.0.0 MIB Reference Guide (AA-RW1QA-TE, May 2005)

Fabric OS 5.0.0 MIB reference guide 129
entLogicalContextName
OID 1.3.6.1.2.1.47.1.2.1.1.8
Description The contextName that can be used to send an SNMP message concerning information
held by this logical entity to the address specified by the associated
entLogicalTAddress/entLogicalTDomain pair.
This object, together with the associated entLogicalContextEngineID object, defines the
context associated with a particular logical entity and allows access to SNMP engines
identified by a contextEngineId and contextName pair.
If no value has been configured by the agent, a zero-length string is returned, or the
agent may choose not to instantiate this object at all.
Entity mapping group
This section lists the entityMapping MIBs.
entLPMappingTable
OID 1.3.6.1.2.1.47.1.3.1
Description 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.
Only the most appropriate physical component that is closest to the root of a particular
containment tree should be identified in an entLPMappingEntry.
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, however, more than one bridge was utilizing ports on this module,
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
OID 1.3.6.1.2.1.47.1.3.1.1
Description Information about a particular logical entity to physical equipment association. Note that
the nature of the association is not specifically identified in this entry. Sufficient
information exists in the MIBs used to manage a particular logical entity to infer how
physical component information is utilized.
Index entLogicalIndex, entPhysicalIndex
entLPPhysicalIndex
OID 1.3.6.1.2.1.47.1.3.1.1.1
Description The value of this object identifies the index value of a particular entPhysicalEntry
associated with the indicated entLogicalEntry.