All MIBs › IBMBNA-MIB › ibmBnaDirApparentLuOwnerName
ibmBnaDirApparentLuOwnerName
Module: IBMBNA-MIB
OID (symbolic): IBMBNA-MIB::ibmBnaDirApparentLuOwnerName
OID (numeric): 1.3.6.1.4.1.2.5.21.1.4.1.2
Node type: OBJECT-TYPE
Type: DisplayString
Access: read-only
Description: Fully qualified CP name of the node at which the LU appears to be located. This object and the appnDirLuOwnerName object in the APPN MIB are related as follows:
Implementations that support this object save in their directory database information about an LU's owning control point that was communicated in two control vectors:
- an Associated Resource Entry (X'3C') CV with resource type X'00F4' (ENCP)
- a Real Owning Control Point (X'4A') CV.
The X'4A' CV is created by a branch network node to preserve the name of the real owning control point for an LU below the branch network node, before it overwrites this name with its own name in the X'3C' CV. The X'4A' CV is not present for LUs that are not below branch network nodes.
If the information a node has about an LU's owning CP came only in a X'3C' CV, then the name from the X'3C' is returned in the appnDirLuOwnerName object, and a null string is returned in this object.
If the information a node has about an LU's owning CP came in both X'3C' and X'4A' CVs, then the name from the X'4A' is returned in the appnDirLuOwnerName object, and the name from the X'3C' (which will be the branch network node's name) is returned in this object.
What is ibmBnaDirApparentLuOwnerName?
This object gives the fully qualified name of the node at which an LU appears to be located, distinct from the real owning control point captured separately when a branch network node has substituted its own name in the standard directory data. Admins use it, alongside the related appnDirLuOwnerName object, to see whether an LU's apparent owner (as branch network nodes report it) differs from its true underlying owning control point, which matters for troubleshooting session routing in branch-aware topologies. For example, an LU actually owned by an end node below a branch network node might show that branch network node's name here, while the true owning CP name is recorded separately in appnDirLuOwnerName.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.5.21.1.4.1.2 snmpwalk -v2c -c public <target> IBMBNA-MIB::ibmBnaDirApparentLuOwnerName
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.5.21.1.4.1.2.1 snmpget -v2c -c public <target> IBMBNA-MIB::ibmBnaDirApparentLuOwnerName.1
Start monitoring IBM SNA/APPN networking equipment (Branch Network Architecture topology) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IBMBNA-MIB::ibmBnaDirApparentLuOwnerName OID value, configure state conditions and alerts, and monitor any IBM SNA/APPN networking equipment (Branch Network Architecture topology) from a single console.
OID Breakdown
Upper-level ancestors (8 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.2 | ibm | ATM-ADAPTER-MIB |
| 1.3.6.1.4.1.2.5 | ibmArchitecture | IBM-FEATURE-ACTIVATION-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.5.21 | ibmBna | IBMBNA-MIB |
| 1.3.6.1.4.1.2.5.21.1 | ibmBnaObjects | IBMBNA-MIB |
| 1.3.6.1.4.1.2.5.21.1.4 | ibmBnaDirTable | IBMBNA-MIB |
| 1.3.6.1.4.1.2.5.21.1.4.1 | ibmBnaDirEntry | IBMBNA-MIB |
| 1.3.6.1.4.1.2.5.21.1.4.1.2 | ibmBnaDirApparentLuOwnerName | IBMBNA-MIB |