Reference record for OID 1.3.6.1.2.1.82.1.3.1.1


parent
1.3.6.1.2.1.82.1.3.1 (lookupCtlEntry)
node code
1
node name
lookupCtlOwnerIndex
dot oid
1.3.6.1.2.1.82.1.3.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) lookupMIB(82) lookupObjects(1) lookupCtlTable(3) lookupCtlEntry(1) lookupCtlOwnerIndex(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • /iso/identified-organization/dod/internet/mgmt/mib/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/mib-2/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/mib/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/lookupMIB/lookupObjects/lookupCtlTable/lookupCtlEntry/lookupCtlOwnerIndex
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/82/1/3/1/1

    Description by circitor

    To facilitate the provisioning of access control by a
    security administrator using the View-Based Access
    Control Model (RFC 2575, VACM) for tables in which
    multiple users may need to independently create or
    modify entries, the initial index is used as an 'owner
    index'. Such an initial index has a syntax of
    SnmpAdminString, and can thus be trivially mapped to a
    securityName or groupName as defined in VACM, in
    accordance with a security policy.

    When used in conjunction with such a security policy all
    entries in the table belonging to a particular user (or
    group) will have the same value for this initial index.
    For a given user's entries in a particular table, the
    object identifiers for the information in these entries
    will have the same subidentifiers (except for the
    'column' subidentifier) up to the end of the encoded
    owner index. To configure VACM to permit access to this
    portion of the table, one would create
    vacmViewTreeFamilyTable entries with the value of
    vacmViewTreeFamilySubtree including the owner index
    portion, and vacmViewTreeFamilyMask 'wildcarding' the
    column subidentifier. More elaborate configurations
    are possible.

    Parsed from file DISMAN-NSLOOKUP-MIB.mib
    Module: DISMAN-NSLOOKUP-MIB

    Description by cisco_v1

    To facilitate the provisioning of access control by a
    security administrator using the View-Based Access
    Control Model (RFC 2575, VACM) for tables in which
    multiple users may need to independently create or
    modify entries, the initial index is used as an 'owner
    index'. Such an initial index has a syntax of
    SnmpAdminString, and can thus be trivially mapped to a
    securityName or groupName as defined in VACM, in
    accordance with a security policy.

    When used in conjunction with such a security policy all
    entries in the table belonging to a particular user (or
    group) will have the same value for this initial index.
    For a given user's entries in a particular table, the
    object identifiers for the information in these entries
    will have the same subidentifiers (except for the
    'column' subidentifier) up to the end of the encoded
    owner index. To configure VACM to permit access to this
    portion of the table, one would create
    vacmViewTreeFamilyTable entries with the value of
    vacmViewTreeFamilySubtree including the owner index
    portion, and vacmViewTreeFamilyMask 'wildcarding' the
    column subidentifier. More elaborate configurations
    are possible.

    Description by oid_info

    lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32))
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "To facilitate the provisioning of access control by a
    security administrator using the View-Based Access
    Control Model (RFC 2575, VACM) for tables in which
    multiple users may need to independently create or
    modify entries, the initial index is used as an owner
    index. Such an initial index has a syntax of
    SnmpAdminString, and can thus be trivially mapped to a
    securityName or groupName as defined in VACM, in
    accordance with a security policy.
    When used in conjunction with such a security policy all
    entries in the table belonging to a particular user (or
    group) will have the same value for this initial index.
    For a given users entries in a particular table, the
    object identifiers for the information in these entries
    will have the same subidentifiers (except for the
    column subidentifier) up to the end of the encoded
    owner index. To configure VACM to permit access to this
    portion of the table, one would create
    vacmViewTreeFamilyTable entries with the value of
    vacmViewTreeFamilySubtree including the owner index
    portion, and vacmViewTreeFamilyMask wildcarding the
    column subidentifier. More elaborate configurations
    are possible."

    View at oid-info.com

    Description by mibdepot

    To facilitate the provisioning of access control by a
    security administrator using the View-Based Access
    Control Model (RFC 2575, VACM) for tables in which
    multiple users may need to create or
    modify entries independently, the initial index is used as
    an 'owner index'. Such an initial index has a syntax of
    SnmpAdminString and can thus be trivially mapped to a
    securityName or groupName defined in VACM, in
    accordance with a security policy.

    When used in conjunction with such a security policy all
    entries in the table belonging to a particular user (or
    group) will have the same value for this initial index.
    For a given user's entries in a particular table, the
    object identifiers for the information in these entries
    will have the same subidentifiers (except for the
    'column' subidentifier) up to the end of the encoded
    owner index. To configure VACM to permit access to this
    portion of the table, one would create
    vacmViewTreeFamilyTable entries with the value of
    vacmViewTreeFamilySubtree including the owner index
    portion, and vacmViewTreeFamilyMask 'wildcarding' the
    column subidentifier. More elaborate configurations
    are possible.

    Parsed from file rfc4560-Ping,-Traceroute,-and-Lookup.mib-3.txt
    Company: None
    Module: DISMAN-NSLOOKUP-MIB

    Description by cisco

    To facilitate the provisioning of access control by a
    security administrator using the View-Based Access
    Control Model (RFC 2575, VACM) for tables in which
    multiple users may need to independently create or
    modify entries, the initial index is used as an 'owner
    index'. Such an initial index has a syntax of
    SnmpAdminString, and can thus be trivially mapped to a
    securityName or groupName as defined in VACM, in
    accordance with a security policy.

    When used in conjunction with such a security policy all
    entries in the table belonging to a particular user (or
    group) will have the same value for this initial index.
    For a given user's entries in a particular table, the
    object identifiers for the information in these entries
    will have the same subidentifiers (except for the
    'column' subidentifier) up to the end of the encoded
    owner index. To configure VACM to permit access to this
    portion of the table, one would create
    vacmViewTreeFamilyTable entries with the value of
    vacmViewTreeFamilySubtree including the owner index
    portion, and vacmViewTreeFamilyMask 'wildcarding' the
    column subidentifier. More elaborate configurations
    are possible.

    Information by circitor

    lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible." ::= { lookupCtlEntry 1 }

    Information by cisco_v1

    lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString(SIZE(0..32)) ACCESS not-accessible STATUS mandatory DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible." ::= { lookupCtlEntry 1 }

    Information by oid_info

    Automatically extracted from RFC2925

    Information by mibdepot

    lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible." ::= { lookupCtlEntry 1 }

    Information by cisco

    lookupCtlOwnerIndex OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible." ::= { lookupCtlEntry 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (7)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.82.1.3.1.2 lookupCtlOperationName 0 0 The name of a lookup operation. This is locally unique,
    within the scope of an lookupCtlOwnerIndex.
    1.3.6.1.2.1.82.1.3.1.3 lookupCtlTargetAddressType 0 0 Specifies the type of address for either performing a
    gethostbyname or a gethostbyaddr function at a remote host.
    Specification o…
    1.3.6.1.2.1.82.1.3.1.4 lookupCtlTargetAddress 0 0 Specifies the address used for a resolver lookup at a
    remote host. The corresponding lookupCtlAddressType
    objects determines its…
    1.3.6.1.2.1.82.1.3.1.5 lookupCtlOperStatus 0 0 Reflects the operational state of an lookupCtlEntry:

    enabled(1) - Operation is active.
    notStarted(2) - Operation has not been …
    1.3.6.1.2.1.82.1.3.1.6 lookupCtlTime 0 0 Reports the number of milliseconds that a lookup
    operation required to be completed at a remote host.
    Completed means operation f…
    1.3.6.1.2.1.82.1.3.1.7 lookupCtlRc 0 0 The system-specific return code from a lookup
    operation. All implementations MUST return a value
    of 0 for this object when the r…
    1.3.6.1.2.1.82.1.3.1.8 lookupCtlRowStatus 0 0 This object allows entries to be created and deleted
    in the lookupCtlTable.

    A remote lookup operation is started when an
    entry in …