entAliasMappingTable

1.3.6.1.2.1.47.1.3.2.1.1

entAliasLogicalIndexOrZero

Integer32{(0,2147483647)}

not-accessible

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 non-zero 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 (e.g.,

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 may exist, e.g.:

entAliasMappingIdentifier.33.0 = ifIndex.6

entAliasMappingIdentifier.33.4 = ifIndex.1

entAliasMappingIdentifier.33.5 = ifIndex.1

entAliasMappingIdentifier.33.10 = ifIndex.12

Note that entries with non-zero entAliasLogicalIndexOrZero

index values have precedence over zero-indexed entries. In

this example, all logical entities except 4, 5, and 10,

associate physical entity 33 with ifIndex.6.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.3.2.1.2

entAliasMappingIdentifier

OBJECT IDENTIFIER

read-only

The value of this object identifies a particular conceptual

row associated with the indicated entPhysicalIndex and

entLogicalIndex pair.

Because 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) may 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.

This object is implemented as defined in the corresponding MIB files.