Entaliasmappingidentifier; Entphysicalcontainstable; Entphysicalcontainsentry - HP StorageWorks 2/64 - Core Switch Reference Manual

entAliasMappingIdentifier

OID
Description

entPhysicalContainsTable

OID
Description

entPhysicalContainsEntry

OID
Description
Index
For example, to indicate that a particular interface (such as physical component 33) is
identified by the same value of ifIndex for all logical entities, the following instance might
exist:
entAliasMappingIdentifier.33.0 = ifIndex.5
In the event an entPhysicalEntry is associated differently for some logical entities,
additional entAliasMapping entries might exist:
entAliasMappingIdentifier.33.0 = ifIndex.6
entAliasMappingIdentifier.33.4 = ifIndex.1
entAliasMappingIdentifier.33.5 = ifIndex.1
entAliasMappingIdentifier.33.10 = ifIndex.12
Note that entries with nonzero entAliasLogicalIndexOrZero index values have precedence
over any zero-indexed entry. In this example, all logical entities except 4, 5, and 10
associate physical entity 33 with ifIndex.6.
1.3.6.1.2.1.47.1.3.2.1.2
The value of this object identifies a particular conceptual row associated with the
indicated entPhysicalIndex and entLogicalIndex pair.
Since only physical ports are modeled in this table, only entries that represent interfaces
or ports are allowed. If an ifEntry exists on behalf of a particular physical port, then this
object should identify the associated ifEntry. For repeater ports, the appropriate row in the
rptrPortGroupTable should be identified instead.
For example, suppose a physical port was represented by entPhysicalEntry.3,
entLogicalEntry.15 existed for a repeater, and entLogicalEntry.22 existed for a bridge.
Then there might be two related instances of entAliasMappingIdentifier:
entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
entAliasMappingIdentifier.3.22 == ifIndex.17
It is possible that other mappings (besides interfaces and repeater ports) might be defined
in the future, as required.
Bridge ports are identified by examining the Bridge MIB and appropriate ifEntries
associated with each dot1dBasePort and are thus not represented in this table.
1.3.6.1.2.1.47.1.3.3
A table that exposes the container/containee relationships between physical entities. This
table provides all the information found by constructing the virtual containment tree for a
given entPhysicalTable, but in a more direct format.
In the event a physical entity is contained by more than one other physical entity (for
example, double-wide modules), this table should include these additional mappings,
which cannot be represented in the entPhysicalTable virtual containment tree.
1.3.6.1.2.1.47.1.3.3.1
A single container/containee relationship.
entPhysicalIndex
entPhysicalChildIndex
Fabric OS 5.x MIB reference guide 127