TCP-ESTATS-MIB :: tcpEStatsStackWillUseSACK

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TCP-ESTATS-MIB › tcpEStatsStackWillUseSACK

tcpEStatsStackWillUseSACK

Module: TCP-ESTATS-MIB

OID (symbolic): TCP-ESTATS-MIB::tcpEStatsStackWillUseSACK

OID (numeric): 1.3.6.1.2.1.156.1.1.5.1.9

Node type: OBJECT-TYPE

Type: TcpEStatsNegotiated

Access: read-only

Description: Enabled(1) if the local host will process SACK options, selfDisabled(2) if SACK is disabled or not implemented on the local host, or peerDisabled(3) if the remote host sends

duplicate ACKs without SACK options, or the local host otherwise decides not to process received SACK options.

Unlike other TCP options, the remote data receiver cannot explicitly indicate if it is able to generate SACK options. When sending data, the local host has to deduce if the remote receiver is sending SACK options. This object can transition from Enabled(1) to peerDisabled(3) after the SYN exchange.

Note that SACK negotiation is not symmetrical. SACK can enabled on one side of the connection and not the other.

What is tcpEStatsStackWillUseSACK?

Whether this host will process SACK options received on this connection - enabled(1), selfDisabled(2), or peerDisabled(3) if the local host decides the remote side isn't actually sending them; can transition from enabled to peerDisabled mid-connection since the receiver's SACK capability can't be explicitly signaled.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.156.1.1.5.1.9
snmpwalk -v2c -c public <target> TCP-ESTATS-MIB::tcpEStatsStackWillUseSACK

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.156.1.1.5.1.9.1
snmpget -v2c -c public <target> TCP-ESTATS-MIB::tcpEStatsStackWillUseSACK.1

Start monitoring vendor-neutral, standards-based MIB, hosts/servers/network devices running a TCP/IP stack (extended TCP performance diagnostics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TCP-ESTATS-MIB::tcpEStatsStackWillUseSACK OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, hosts/servers/network devices running a TCP/IP stack (extended TCP performance diagnostics) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.156tcpEStatsMIBTCP-ESTATS-MIB
1.3.6.1.2.1.156.1tcpEStatsMIBObjectsTCP-ESTATS-MIB
1.3.6.1.2.1.156.1.1tcpEStatsTCP-ESTATS-MIB
1.3.6.1.2.1.156.1.1.5tcpEStatsStackTableTCP-ESTATS-MIB
1.3.6.1.2.1.156.1.1.5.1tcpEStatsStackEntryTCP-ESTATS-MIB
1.3.6.1.2.1.156.1.1.5.1.9tcpEStatsStackWillUseSACKTCP-ESTATS-MIB