Brocade Communications Systems 8, Справочное руководство

Страница: 152 / 382

134 Fabric OS MIB Reference
53-1001768-01
entAliasLogicalIndexOrZero 1.3.6.1.2.1.47.1.3.2.1.1
4
Index entPhysicalIndex
entAliasLogicalIndexOrZero
Not supported.
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.
If this object has a nonzero value, then it identifies the logical entity named by the same value of
entLogicalIndex.
If this object has a value of zero, then the mapping between the physical component and the alias
identifier for this entAliasMapping entry is associated with all unspecified logical entities. That is, a
value of zero (the default mapping) identifies any logical entity that does not have an explicit entry
in this table for a particular entPhysicalIndex/entAliasMappingIdentifier pair.
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.
Not supported.
entAliasMappingIdentifier 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.