All MIBs › ACC-PING › accPingDataMin
accPingDataMin
Module: ACC-PING
OID (symbolic): ACC-PING::accPingDataMin
OID (numeric): 1.3.6.1.4.1.5.1.1.30.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description:
Minimum number of data bytes included in the Ping packet. The first four bytes of data always carry a timestamp, the remaining data is an incrementing byte data pattern.
What is accPingDataMin?
This OID specifies the minimum number of data bytes included in each ping packet, ranging from 4 to 1500 bytes. Engineers adjust this value to test how the network handles different payload sizes, which helps identify MTU (maximum transmission unit) issues or other size-related problems. A value of 64 means the ping packet will contain at least 64 bytes of data, with the first 4 bytes used for timing information.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5.1.1.30.3 snmpwalk -v2c -c public <target> ACC-PING::accPingDataMin
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5.1.1.30.3.1 snmpget -v2c -c public <target> ACC-PING::accPingDataMin.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.5.1.1.30.3.1 i <value>
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.5 | acc | ACC-MIB |
| 1.3.6.1.4.1.5.1 | accSBAR | ACC-MIB |
| 1.3.6.1.4.1.5.1.1 | accBRG | ACC-MIB |
| 1.3.6.1.4.1.5.1.1.30 | accPing | ACC-MIB |
| 1.3.6.1.4.1.5.1.1.30.3 | accPingDataMin | ACC-PING |