pingCtlDataSize
DISMAN-PING-MIB ·
.1.3.6.1.2.1.80.1.2.1.5
Object
column r/w
octetsUnsigned32
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).
Context
- MIB
- DISMAN-PING-MIB
- OID
.1.3.6.1.2.1.80.1.2.1.5- Type
- column
- Access
- readwrite
- Status
- current
- Units
- octets
- Parent
- pingCtlEntry
- Groups
- 2
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DISMAN-PING-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-PING-MIB::pingCtlDataSize'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DISMAN-PING-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-PING-MIB::pingCtlDataSize.<pingCtlOwnerIndex>.<pingCtlTestName>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DISMAN-PING-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DISMAN-PING-MIB::pingCtlDataSize'
Syntax
octetsUnsigned32
Values & Constraints
Object Constraints
range: 0-65507
Conformance
Member of