OID reference

pingCtlOwnerIndex

1.3.6.1.2.1.80.1.2.1.1

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 SnmpAdminSt…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.80.1.2.1 (pingCtlEntry)
Node code
1
Node name
pingCtlOwnerIndex
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.80.1.2.1.1
URN notation
urn:oid:1.3.6.1.2.1.80.1.2.1.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 80 1 2 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingCtlTable(2) pingCtlEntry(1) pingCtlOwnerIndex(1)}
OID-IRI notation
  • /1/3/6/1/2/1/80/1/2/1/1
  • /ISO/Identified-Organization/6/1/2/1/80/1/2/1/1
  • /ISO/3/6/1/2/1/80/1/2/1/1
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/identified-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/mib/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/org/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingCtlTable/pingCtlEntry/pingCtlOwnerIndex

SNMP properties

Value type
SnmpAdminString
Maximum access defined by MIB
not-accessible
Status in MIB
current, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — RFC Editor, MIBdepot, and others

Value type
SnmpAdminString
Maximum access defined by MIB
not-accessible
Status in MIB
current
Allowed size (octets)
0–32

Variant 2 — Cisco SMIv1

Value type
SnmpAdminString
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory
Allowed size (octets)
0–32

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: pingCtlOwnerIndex, pingCtlTestName.

A query example is omitted because the source variants do not establish compatible read access.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

IES3220-8T4F, IES3220-8T4F-U, IES5120-28TF, IES5120-28TS, IES5120-28TS-P, IES5120-48T4S, IES5220-30TS-3ES, IES5220-6S-3ES, N5580-32C, N5580-48Y8C, N5850-48S6Q, N5860-48SC.

Show 24 more models

N8560-32C, N8560-48BC, N8560-64C, NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH, S3100-16TF, S3410-24TS-P, S3910-24TS, S3910-48TS, S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P, S5860-20SQ, S5860-24XB-U, S5860-48SC, TSN3220-10S, TSN3220-10S-U.

A definition in a model's MIB package does not establish that the device implements it or permits access.

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

Available source records contain 4 distinct definitions; some records may not include a definition.

Show 4 published definitions

pingCtlOwnerIndex · current

pingCtlOwnerIndex 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."
       ::= { pingCtlEntry 1 }

pingCtlOwnerIndex · current

pingCtlOwnerIndex 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."
       ::= { pingCtlEntry 1 }

pingCtlOwnerIndex · current

pingCtlOwnerIndex 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."
   ::= { pingCtlEntry 1 }

pingCtlOwnerIndex · current

pingCtlOwnerIndex 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."
    ::= { pingCtlEntry 1 }

Meaning

Descriptions

5 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

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.
Original text from OID Repository
pingCtlOwnerIndex 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."
Sources for this description

OID Repository

View at oid-base.com
Automatically extracted from RFC2925

Description 2

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.
Sources for this description

Circitor

Parsed from DISMAN-PING-MIB.mib · DISMAN-PING-MIB

Source file: Download DISMAN-PING-MIB.mib

Browse all files from Circitor

Cisco

Source file: Download rfc2925-disman-ping.mib · Publisher's file

Other official packages with the same file

tsn3220-10s-u-switch-snmp-mib-files.zip

tsn3220-10s-switch-snmp-mib-files.zip

ies5220-6s-3es-switch-snmp-mib-files.zip

ies5220-30ts-3es-switch-snmp-mib-files.zip

Source file: Download rfc2925.mib · Publisher's file

Other official packages with the same file

MIB-6.5.1.22.zip

XS728T_XS748T_mib_files.zip

XS728T_XS748T_MIB_V6.5.1.59.zip

XS728T_XS748T_MIB_V6.5.1.42.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

M4250H-v13.0.4.14-mibs.zip

M4250H-v13.0.4.13-mibs.zip

M4250L-v13.0.4.14-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

XS508TM_XS516TM-v7.8.11.13-Mibs.zip

M4350-v14.0.9.10-mibs.zip

M4350-v14.0.6.9-mibs.zip

M4350-v14.0.6.19-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

mibs-m4500-48xf8c-7.0.5.6.tar.bz2

mibs-m4500-48xf8c-7.0.4.30.tar.bz2

mibs-m4500-48xf8c-7.0.4.23.tar.bz2

mibs-m4500-48xf8c-7.0.4.18.tar.bz2

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xsm72xxs-v9.0.1.46-mibs.zip

gs7xxts_tps-v5.3.0.31-mibs.zip

gs7xxts_tps-v5.3.0.29-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xs7xxt_6.6.3.2-mibs.zip

xs712t-v6.1.0.36-mibs.zip

xs712t-v6.1.0.34-mibs.zip

xs7xxt6.6.3.3-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xs7xxtv7.0.0.24-mibs.zip

xs7xxtv7.0.0.20-mibs.zip

s3300v6.6.4.26-mibs.zip

s3300v6.6.4.25-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

GSM72xxP-mibs-fwv9.0.2.2.zip

gs7xxts_tps-v5.3.0.36-mibs.zip

gs7xxts_tps-v5.3.0.35-mibs.zip

fs728tp_5.0.2.50-mibs.zip

Source file: Download rfc2925_ping.mib · Publisher's file

Other official packages with the same file

LC-YS-7154CF-5.30.0363-RU2-MIB.zip

LC-XS-6128QF-5.20.0534-RU12-MIB.zip

LC-XS-5116QF-5.20.0534-RU12-MIB.zip

LC-XS-5110F-5.20.0534-RU12-MIB.zip

Browse all files from Cisco

Description 3

Administrator name of a ping operation.

Sources for this description

H3C official MIB documentation and object descriptions

See 1 matching source record

Description 4

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.

Sources for this description

Encoded line breaks have been normalized for display; the original file is unchanged.

Huawei official enterprise MIB Query and object descriptionsMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBsD-Link official switch MIBsFS.COM official Documentation Hub native MIB packagesMIBdepotCommon and standard MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copiesRFC Editor

See 3 matching source records

Description 5

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 the SnmpAdminString syntax 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.

Sources for this description

Huawei official enterprise MIB Query and object descriptions

See 1 matching source record

Evidence

Source records

5 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 3H3C official MIB documentation and object descriptions1 record · 36 sources

Description 3

pingCtlOwnerIndex · unspecifiedH3C official MIB documentation and object descriptions36 sources

Status in source: unspecified.

Names: pingCtlOwnerIndex

Technical details
{}

Browse all 36 supporting sources

Records for description 4Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs, and others3 records · 12 sources

Description 4

pingCtlOwnerIndex · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source

Status in source: unspecified.

Names: pingCtlOwnerIndex

Technical details
{
  "syntax": "OCTET STRING{(0,32)}",
  "max_access": "not-accessible",
  "object_class": "table column"
}
pingCtlOwnerIndex · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs, and others10 sources

Status in source: current.

Names: pingCtlOwnerIndex

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pingCtlOwnerIndex",
    "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.\"",
    "::=",
    "{",
    "pingCtlEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "SnmpAdminString",
      [
        "octetStringSubType",
        [
          [
            0,
            32
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "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."
    ],
    null,
    null,
    null,
    null
  ]
}
pingCtlOwnerIndex · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source
Records for description 5Huawei official enterprise MIB Query and object descriptions1 record · 1 source

Historical records

Additional source information

Information from Circitor
pingCtlOwnerIndex 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."
    ::= { pingCtlEntry 1 }
Information from Cisco SMIv1
pingCtlOwnerIndex 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."
    ::= { pingCtlEntry 1 }
Information from MIBdepot
pingCtlOwnerIndex 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."
    ::= { pingCtlEntry 1 }
Information from Cisco
pingCtlOwnerIndex 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." 
    ::= { pingCtlEntry 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (22)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.80.1.2.1.2 pingCtlTestName00 The name of the ping test. This is locally unique, within
the scope of an pingCtlOwnerIndex.
1.3.6.1.2.1.80.1.2.1.3 pingCtlTargetAddressType00 Specifies the type of host address to be used at a remote
host for performing a ping operation.
1.3.6.1.2.1.80.1.2.1.4 pingCtlTargetAddress00 Specifies the host address to be used at a remote host for
performing a ping operation. The host address type is
determined by t…
1.3.6.1.2.1.80.1.2.1.5 pingCtlDataSize00 Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping
request is usually an ICMP messag…
1.3.6.1.2.1.80.1.2.1.6 pingCtlTimeOut00 Specifies the time-out value, in seconds, for a
remote ping operation.
1.3.6.1.2.1.80.1.2.1.7 pingCtlProbeCount00 Specifies the number of times to perform a ping
operation at a remote host.
1.3.6.1.2.1.80.1.2.1.8 pingCtlAdminStatus00 Reflects the desired state that a pingCtlEntry should be
in:

enabled(1) - Attempt to activate the test as defined by
this pingCtl…
1.3.6.1.2.1.80.1.2.1.9 pingCtlDataFill00 The content of this object is used together with the
corresponding pingCtlDataSize value to determine how to
fill the data portio…
1.3.6.1.2.1.80.1.2.1.10 pingCtlFrequency00 The number of seconds to wait before repeating a ping test
as defined by the value of the various objects in the
corresponding ro…
1.3.6.1.2.1.80.1.2.1.11 pingCtlMaxRows00 The maximum number of entries allowed in the
pingProbeHistoryTable. An implementation of this
MIB will remove the oldest entry i…
1.3.6.1.2.1.80.1.2.1.12 pingCtlStorageType00 The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columna…
1.3.6.1.2.1.80.1.2.1.13 pingCtlTrapGeneration00 The value of this object determines when and if
to generate a notification for this entry:

probeFailure(0) - Generate a pingPro…
1.3.6.1.2.1.80.1.2.1.14 pingCtlTrapProbeFailureFilter, pingCtlTrapFilter00 The value of this object is used to determine when
to generate a pingProbeFailed NOTIFICATION.

Setting pingCtlTrapGeneration
to pr…
1.3.6.1.2.1.80.1.2.1.15 pingCtlTrapTestFailureFilter, pingCtlType00 The value of this object is used to determine when
to generate a pingTestFailed NOTIFICATION.

Setting pingCtlTrapGeneration to te…
1.3.6.1.2.1.80.1.2.1.16 pingCtlType, pingCtlDescr00 The value of this object is used to either report or
select the implementation method to be used for
calculating a ping response …
1.3.6.1.2.1.80.1.2.1.17 pingCtlDescr, pingCtlSourceAddress00 The purpose of this object is to provide a
descriptive name of the remote ping test.
1.3.6.1.2.1.80.1.2.1.18 pingCtlSourceAddressType, pingCtlIfIndex00 Specifies the type of the source address,
pingCtlSourceAddress, to be used at a remote host
when performing a ping operation.
1.3.6.1.2.1.80.1.2.1.19 pingCtlSourceAddress, pingCtlByPassRouteTable00 Use the specified IP address (which must be given
in numeric form, not as a hostname) as the source
address in outgoing probe pac…
1.3.6.1.2.1.80.1.2.1.20 pingCtlIfIndex, pingCtlDSField00 Setting this object to an interface's ifIndex prior
to starting a remote ping operation directs
the ping probes to be transmitted…
1.3.6.1.2.1.80.1.2.1.21 pingCtlByPassRouteTable, pingCtlRowStatus00 The purpose of this object is to optionally enable
bypassing the route table. If enabled, the remote
host will bypass the normal…
1.3.6.1.2.1.80.1.2.1.22 pingCtlDSField00 Specifies the value to store in the Differentiated
Services (DS) Field in the IP packet used to
encapsulate the ping probe. The …
1.3.6.1.2.1.80.1.2.1.23 pingCtlRowStatus00 This object allows entries to be created and deleted
in the pingCtlTable. Deletion of an entry in this
table results in all corr…