OID reference

myPingEntry

1.3.6.1.4.1.171.10.97.2.3.1.1.1

Description

Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration object…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.171.10.97.2.3.1.1 (myPingTable)
Node code
1
Node name
myPingEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.171.10.97.2.3.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.171.10.97.2.3.1.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 171 10 97 2 3 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) nmsGponMIB(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) nmsGponMIB(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) nmsGponMIB(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) nmsGponMIB(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) nmsGponMIB(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlink-products(10) switchMib(97) myMgmt(2) myPingMIB(3) myPingMIBObjects(1) myPingTable(1) myPingEntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/171/10/97/2/3/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/171/10/97/2/3/1/1/1
  • /ISO/3/6/1/4/1/171/10/97/2/3/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/nmsGponMIB/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/nmsGponMIB/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/company/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/company/products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/company/nmsGponMIB/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/my/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/my/products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/my/nmsGponMIB/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/nms/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/nms/products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmsGponMIB/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • /iso/identified-organization/dod/internet/private/enterprises/dlink/dlink-products/switchMib/myMgmt/myPingMIB/myPingMIBObjects/myPingTable/myPingEntry
  • Additional combinations skipped.

SNMP properties

Value type
MyPingEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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

The displayed source records contain one distinct definition. Compare its source records.

myPingEntry OBJECT-TYPE
        SYNTAX MyPingEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
                "Entry contains ping parameters and results.
                
                A management station wishing to create an entry should
                first generate a pseudo-random serial number to be used
                as the index to a ping entry.  The station should
                then create the associated entry.
                
                We must set all specifies valid values for the 
                non-defaulted configuration objects, certainly, it should
                also modify  the default values for the other configuration 
                objects if the defaults are not appropriate.
                                       
                Once the appropriate instance of all the configuration
                objects have been created or set,the row status should be set
                to active to initiate the request.  

                Once the ping sequence has been activated, it cannot be
                stopped -- it will run until the configured number of
                packets have been sent.

                Once the sequence completes, the management station should
                retrieve the values of the status objects of interest, and
                should then delete the entry.  In order to prevent old
                entries from clogging the table, entries will be aged out,
                but an entry will never be deleted within 5 minutes of
                completing." 
        INDEX { myPingIndex }
        ::= { myPingTable 1 }

Meaning

Descriptions

1 unique

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

Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.

Sources for this description

D-Link official switch MIBsD-Link MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

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

Records for description 1D-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

myPingEntry · currentD-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: myPingEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "myPingEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "MyPingEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.\"",
    "INDEX",
    "{",
    "myPingIndex",
    "}",
    "::=",
    "{",
    "myPingTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "MyPingEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "myPingIndex"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Direct children (14)