OID Repository
OID Repository
https://oid-base.com
Display OID:

Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemmgmt(2) Action itemmib-2(1) Action itemsnanauMIB(34) Action itemappnMIB(4) Action itemappnObjects(1) Action itemappnDir(4) Action itemappnDirTable(2) Action itemappnDirEntry(1)

appnDirApparentLuOwnerName(6)


Navigating the OID tree
Separation line
OID description

 
Action itemFormat of this page
Action itemModify this OID
Action itemCreate child OID
Action itemCreate sibling OID
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

appnDirApparentLuOwnerName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0 | 3..17))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Fully qualified CP name of the node at which the LU appears to
be located. This object and the appnDirLuOwnerName object 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."



Classification:

MIB object for network management

See classes of OIDs

Information:

Automatically extracted from IETF RFC 2455.

Separation line
Short URL for this page:
Separation line

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2025
Parent OID: appnDirEntry(1) First sibling OID: appnDirLuName(1) Previous sibling OID: appnDirType(5) Separation line
Chatbot helper Webmaster Bullet 26 Dec 2019 Bullet Page top