All MIBs › HP-ENTITY-MIB › hpEntAliasMappingIdentifier
hpEntAliasMappingIdentifier
Module: HP-ENTITY-MIB
OID (symbolic): HP-ENTITY-MIB::hpEntAliasMappingIdentifier
OID (numeric): 1.3.6.1.4.1.11.2.14.9.1.3.2.1.2
Node type: OBJECT-TYPE
Type: RowPointer
Access: read-only
Description: The value of this object identifies a particular conceptual row associated with the indicated hpEntPhysicalIndex and hpEntLogicalIndex pair.
Since only physical ports are modeled in this table, only entries which 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 hpEntPhysicalEntry.3, hpEntLogicalEntry.15 existed for a repeater, and hpEntLogicalEntry.22 existed for a bridge. Then there might be two related instances of hpEntAliasMappingIdentifier: hpEntAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2 hpEntAliasMappingIdentifier.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.
What is hpEntAliasMappingIdentifier?
This points to the specific row, such as an ifEntry or rptrPortGroupTable entry, that corresponds to a given physical port when viewed through a particular logical entity's context. Admins use this to bridge between the generic entity and physical model and protocol-specific tables like the standard Interfaces MIB, so a physical port can be tied to its ifIndex. For example, hpEntAliasMappingIdentifier.3.22 might equal ifIndex.17, linking physical port entity 3 under logical entity 22 to interface 17.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.9.1.3.2.1.2 snmpwalk -v2c -c public <target> HP-ENTITY-MIB::hpEntAliasMappingIdentifier
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.9.1.3.2.1.2.1 snmpget -v2c -c public <target> HP-ENTITY-MIB::hpEntAliasMappingIdentifier.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> hpEntAliasMappingIdentifier.1
Start monitoring HP ProCurve chassis-based network switch (early Entity MIB adaptation) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HP-ENTITY-MIB::hpEntAliasMappingIdentifier OID value, configure state conditions and alerts, and monitor any HP ProCurve chassis-based network switch (early Entity MIB adaptation) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.11 | hp | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2 | nm | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2.14 | icf | CONFIG-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.11.2.14.9 | hpEntityMIB | HP-ENTITY-MIB |
| 1.3.6.1.4.1.11.2.14.9.1 | hpEntityMIBObjects | HP-ENTITY-MIB |
| 1.3.6.1.4.1.11.2.14.9.1.3 | hpEntityMapping | HP-ENTITY-MIB |
| 1.3.6.1.4.1.11.2.14.9.1.3.2 | hpEntAliasMappingTable | HP-ENTITY-MIB |
| 1.3.6.1.4.1.11.2.14.9.1.3.2.1 | hpEntAliasMappingEntry | HP-ENTITY-MIB |
| 1.3.6.1.4.1.11.2.14.9.1.3.2.1.2 | hpEntAliasMappingIdentifier | HP-ENTITY-MIB |