OID reference

pingCtlDataSize

1.3.6.1.2.1.80.1.2.1.5

Description

Specifies the size of the data portion to be transmitted in a ping operation in octets. A ping request is usually an ICMP message encoded into an IP packet. An IP packet has a maximum size of 65535 octets. Subtracting the size of the ICMP or UDP header (both 8 octets) and the size of the IP header (20 octets) yields a…

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

Value type
Unsigned32, Gauge
Units
octets
Maximum access defined by MIB
read-create, read-write
Status in MIB
current, mandatory
Default value
0

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — RFC Editor, MIBdepot, and others

Value type
Unsigned32
Units
octets
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
0
Allowed ranges
0–65507

Variant 2 — Cisco SMIv1

Value type
Gauge
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Default value
0
Allowed ranges
0–65507

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.

snmpwalk [connection options] DEVICE .1.3.6.1.2.1.80.1.2.1.5

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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

pingCtlDataSize · current

pingCtlDataSize OBJECT-TYPE
       SYNTAX      Unsigned32 (0..65507)
       UNITS       "octets"
       MAX-ACCESS  read-create
       STATUS      current
       DESCRIPTION
           "Specifies the size of the data portion to be
           transmitted in a ping operation, in octets.  Whether this
           value can be applied depends on the selected
           implementation method for performing a ping operation,
           indicated by pingCtlType in the same conceptual row.
           If the method used allows applying the value contained









           in this object, then it MUST be applied.  If the specified
           size is not appropriate for the chosen ping method, the
           implementation SHOULD use whatever size (appropriate to
           the method) is closest to the specified size.

           The maximum value for this object was computed by
           subtracting the smallest possible IP header size of
           20 octets (IPv4 header with no options) and the UDP
           header size of 8 octets from the maximum IP packet size.
           An IP packet has a maximum size of 65535 octets
           (excluding IPv6 Jumbograms)."
       DEFVAL { 0 }
       ::= { pingCtlEntry 5 }

pingCtlDataSize · current

pingCtlDataSize OBJECT-TYPE
       SYNTAX      Unsigned32 (0..65507)
       UNITS       "octets"
       MAX-ACCESS  read-create
       STATUS      current
       DESCRIPTION
           "Specifies the size of the data portion to be
           transmitted in a ping operation, in octets.  Whether this
           value can be applied depends on the selected
           implementation method for performing a ping operation,
           indicated by pingCtlType in the same conceptual row.
           If the method used allows applying the value contained
           in this object, then it MUST be applied.  If the specified
           size is not appropriate for the chosen ping method, the
           implementation SHOULD use whatever size (appropriate to
           the method) is closest to the specified size.

           The maximum value for this object was computed by
           subtracting the smallest possible IP header size of
           20 octets (IPv4 header with no options) and the UDP
           header size of 8 octets from the maximum IP packet size.
           An IP packet has a maximum size of 65535 octets
           (excluding IPv6 Jumbograms)."
       DEFVAL { 0 }
       ::= { pingCtlEntry 5 }

pingCtlDataSize · current

pingCtlDataSize OBJECT-TYPE
   SYNTAX      Unsigned32 (0..65507)
   UNITS       "octets"
   MAX-ACCESS  read-create
   STATUS      current
   DESCRIPTION
       "Specifies the size of the data portion to be
       transmitted in a ping operation, in octets.  Whether this
       value can be applied depends on the selected
       implementation method for performing a ping operation,
       indicated by pingCtlType in the same conceptual row.
       If the method used allows applying the value contained
       in this object, then it MUST be applied.  If the specified
       size is not appropriate for the chosen ping method, the
       implementation SHOULD use whatever size (appropriate to
       the method) is closest to the specified size.

       The maximum value for this object was computed by
       subtracting the smallest possible IP header size of
       20 octets (IPv4 header with no options) and the UDP
       header size of 8 octets from the maximum IP packet size.
       An IP packet has a maximum size of 65535 octets
       (excluding IPv6 Jumbograms)."
   DEFVAL { 0 }
   ::= { pingCtlEntry 5 }

pingCtlDataSize · current

pingCtlDataSize OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65507)
    UNITS       "octets"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Specifies the size of the data portion to be
        transmitted in a ping operation, in octets.  Whether this
        value can be applied depends on the selected
        implementation method for performing a ping operation,
        indicated by pingCtlType in the same conceptual row.
        If the method used allows applying the value contained

        in this object, then it MUST be applied.  If the specified
        size is not appropriate for the chosen ping method, the
        implementation SHOULD use whatever size (appropriate to
        the method) is closest to the specified size.

        The maximum value for this object was computed by
        subtracting the smallest possible IP header size of
        20 octets (IPv4 header with no options) and the UDP
        header size of 8 octets from the maximum IP packet size.
        An IP packet has a maximum size of 65535 octets
        (excluding IPv6 Jumbograms)."
    DEFVAL { 0 }
    ::= { pingCtlEntry 5 }

Meaning

Descriptions

7 unique

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

Description 1

Specifies the size of the data portion to be transmitted in a ping operation in octets. A ping request is usually an ICMP message encoded into an IP packet. An IP packet has a maximum size of 65535 octets. Subtracting the size of the ICMP or UDP header (both 8 octets) and the size of the IP header (20 octets) yields a maximum size of 65507 octets.
Original text from OID Repository
pingCtlDataSize OBJECT-TYPE SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping
request is usually an ICMP message encoded
into an IP packet. An IP packet has a maximum size
of 65535 octets. Subtracting the size of the ICMP
or UDP header (both 8 octets) and the size of the IP
header (20 octets) yields a maximum size of 65507
octets."
DEFVAL { 0 }
Sources for this description

OID Repository

View at oid-base.com
Automatically extracted from RFC2925

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

Related source files and packages:

Show more related files and packages
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

Related source files and packages:

Show more related files and packages
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

Related source files and packages:

Show more related files and packages
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

Related source files and packages:

Show more related files and packages

Browse all related files for rfc2925_ping.my

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

Related source files and packages:

Show more related files and packages

Browse all related files for rfc2925_ping.my

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

Related source files and packages:

Show more related files and packages
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

Related source files and packages:

Show more related files and packages

Browse all related files for rfc2925_ping.my

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

Related source files and packages:

Show more related files and packages

Browse all related files for rfc2925_ping.my

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

Related source files and packages:

Show more related files and packages
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

Related source files and packages:

Show more related files and packages

Browse all related files for rfc2925_ping.mib

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

Cisco SMIv1

Source file: Download DISMAN-PING-MIB-V1SMI.my · Publisher's file

Browse all files from Cisco SMIv1

MIBdepot

Source file: Download DISMAN-PING-MIB.txt

Source file: Download DISMAN-PING-MIB.mib.txt

Source file: Download rfc2925-Ping,-Traceroute,-and-Lookup.mib-1.txt

Source file: Download rfc2925-disman-ping.mib.txt

Source file: Download rfc2925p.mib.txt

Source file: Download rfc2925_DISMAN-PING.mib.txt

Browse all files from MIBdepot

Description 2

Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).

Implementation notes: The value ranges from 0 to 8100.

Sources for this description

Huawei official enterprise MIB Query and object descriptions

See 4 matching source records

Description 3

Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).

Sources for this description

Multiple 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 4 matching source records

Description 4

Payload size for each probe packet.

Sources for this description

H3C official MIB documentation and object descriptions

See 1 matching source record

Description 5

Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).

Implementation notes: Size list: 0 to 8100.

Sources for this description

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

Huawei official enterprise MIB Query and object descriptions

See 4 matching source records

Description 6

Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).

Implementation notes: Size list: 0 to 8100.

Sources for this description

Huawei official enterprise MIB Query and object descriptions

See 4 matching source records

Description 7

Size list: 0 to 8100.

Implementation notes: Size list: 0 to 8100.

Sources for this description

Huawei official enterprise MIB Query and object descriptions

See 1 matching source record

Evidence

Source records

6 records

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

Records for description 2, 3, 5, 6Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs, and others4 records · 13 sources

Description 2 · Description 3 · Description 5 · Description 6

pingCtlDataSize · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source

Status in source: unspecified.

Names: pingCtlDataSize

Technical details
{
  "syntax": "Unsigned32 (0..65507)",
  "max_access": "read-create",
  "object_class": "table column",
  "implementation_notes": "The value ranges from 0 to 8100."
}
pingCtlDataSize · 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: pingCtlDataSize

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pingCtlDataSize",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "(",
    "0",
    ".",
    ".",
    "65507",
    ")",
    "UNITS",
    [
      "literal",
      "226f637465747322"
    ],
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "pingCtlEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32",
      [
        "integerSubType",
        [
          [
            0,
            65507
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "octets"
    ],
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms)."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}
pingCtlDataSize · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source

Status in source: unspecified.

Names: pingCtlDataSize

Technical details
{
  "syntax": "Unsigned32{(0,65507)}",
  "max_access": "read-create",
  "object_class": "table column",
  "implementation_notes": "Size list: 0 to 8100."
}
pingCtlDataSize · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source

Status in source: unspecified.

Names: pingCtlDataSize

Technical details
{
  "syntax": "Unsigned32{(0,65507)}",
  "max_access": "read-create",
  "object_class": "table column",
  "implementation_notes": "Size list: 0 to 8100."
}
Records for description 4H3C official MIB documentation and object descriptions1 record · 36 sources

Description 4

pingCtlDataSize · unspecifiedH3C official MIB documentation and object descriptions36 sources

Status in source: unspecified.

Names: pingCtlDataSize

Technical details
{}

Browse all 36 supporting sources

Records for description 7Huawei official enterprise MIB Query and object descriptions1 record · 1 source

Description 7

pingCtlDataSize · unspecifiedHuawei official enterprise MIB Query and object descriptions1 source

Status in source: unspecified.

Names: pingCtlDataSize

Technical details
{
  "syntax": "Unsigned32{(0,65507)}",
  "max_access": "read-create",
  "object_class": "table column",
  "implementation_notes": "Size list: 0 to 8100."
}

Historical records

Additional source information

Information from Circitor 
pingCtlDataSize OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65507)
    UNITS       "octets"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Specifies the size of the data portion to be
        transmitted in a ping operation in octets.  A ping
        request is usually an ICMP message encoded
        into an IP packet.  An IP packet has a maximum size
        of 65535 octets.  Subtracting the size of the ICMP
        or UDP header (both 8 octets) and the size of the IP
        header (20 octets) yields a maximum size of 65507
        octets."
    DEFVAL { 0 }
    ::= { pingCtlEntry 5 }
Information from Cisco SMIv1 
pingCtlDataSize OBJECT-TYPE
    SYNTAX Gauge(0..65507)


    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "Specifies the size of the data portion to be
        transmitted in a ping operation in octets.  A ping
        request is usually an ICMP message encoded
        into an IP packet.  An IP packet has a maximum size
        of 65535 octets.  Subtracting the size of the ICMP
        or UDP header (both 8 octets) and the size of the IP
        header (20 octets) yields a maximum size of 65507
        octets."
    DEFVAL { 0 }
    ::= { pingCtlEntry 5 }
Information from MIBdepot 
pingCtlDataSize OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65507)
    UNITS       "octets"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "Specifies the size of the data portion to be
        transmitted in a ping operation in octets.  A ping
        request is usually an ICMP message encoded
        into an IP packet.  An IP packet has a maximum size
        of 65535 octets.  Subtracting the size of the ICMP
        or UDP header (both 8 octets) and the size of the IP
        header (20 octets) yields a maximum size of 65507
        octets."
    DEFVAL { 0 }
    ::= { pingCtlEntry 5 }
Information from Cisco 
pingCtlDataSize OBJECT-TYPE
    SYNTAX          Unsigned32 (0..65507)
    UNITS           "octets"
    MAX-ACCESS      read-create
    STATUS          current
    DESCRIPTION
        "Specifies the size of the data portion to be
        transmitted in a ping operation in octets.  A ping
        request is usually an ICMP message encoded
        into an IP packet.  An IP packet has a maximum size
        of 65535 octets.  Subtracting the size of the ICMP
        or UDP header (both 8 octets) and the size of the IP
        header (20 octets) yields a maximum size of 65507
        octets."
    DEFVAL          { 0 } 
    ::= { pingCtlEntry 5 }

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.1 pingCtlOwnerIndex00 To facilitate the provisioning of access control by a
security administrator using the View-Based Access
Control Model (RFC 2575,…
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.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…