TCP-ESTATS-MIB

All MIBs › TCP-ESTATS-MIB

Organization: IETF TSV Working Group

Last Updated: 2007-05-18

Category: IP and Core Protocols

Description: Defines extended TCP performance statistics for diagnosing whether network application bottlenecks are in the sender, receiver, or network.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring TCP-ESTATS-MIB with a free 30-day trial of IPNetwork Monitor.

What Is TCP-ESTATS-MIB?

TCP-ESTATS-MIB is a vendor-neutral IETF standards-track MIB (based on the Web100 project) that defines extended TCP performance instrumentation beyond the basic counters in the standard TCP-MIB. It exposes per-connection and per-listener performance and diagnostic data organized into control objects (path, stack, application, tuning, notification) and statistics such as connection latency and listener activity, intended to help pinpoint whether a networking bottleneck lies in the sending application, the receiving application, or the network path itself. Its monitoring value is centered on software/network performance diagnostics rather than physical hardware health: administrators use it to watch TCP connection setup timing, retransmission-related behavior, and listener socket activity to detect degraded application or network performance, and because objects mirror the underlying TCP stack's state, a device reboot clears counters and dynamic rows, reflecting current live connections only. It is explicitly layered on top of (and meant to complement) the standard TCP-MIB and the host's TCP/IP stack implementation. It is typically deployed on hosts, servers, or network appliances where deep TCP performance troubleshooting is needed, such as diagnosing slow file transfers or application throughput issues. Engineers implementing or auditing this functionality typically reference the TCP-ESTATS-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in TCP-ESTATS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
hosts, servers, and network devices running a TCP/IP stack

Monitoring Examples

An administrator troubleshooting a slow application would poll tcpEStatsListenerTable / tcpEStatsListenerEntry to check fields such as tcpEStatsListenerStartTime and tcpEStatsListenerSynRcvd, revealing how many SYNs a listening socket has received and since when, and would use tcpEStatsConnTableLatency alongside tcpEStatsControlPath and tcpEStatsControlStack to correlate connection-level latency with path and stack behavior. Tracking tcpEStatsListenerTableLastChange helps a monitoring system know when new listeners have appeared or changed without re-polling the whole table each cycle.

What Can Be Monitored

TCP listener socket activity
SYN-received counts
connection setup latency
listener start time
TCP stack/application/tuning control state
table change notifications

Imported Objects

From HCNUM-TC

ZeroBasedCounter64

From RMON2-MIB

ZeroBasedCounter32

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TCP-MIB

tcpConnectionEntry	OBJECT-TYPE
tcpListenerEntry	OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
tcpEStatsMIB	1.3.6.1.2.1.156			Documentation of TCP Extended Performance Instrumentation variables from the Web100 project. [Web100] All of the objects in this MIB MUST have the same persistence properties as the underlying TCP implementation. On a reboot, all zero-based counters MUST be cleared, all dynamically created table rows MUST be deleted, and all read-write objects MUST be restored to their default values. It is assumed that all TCP implementation have some initialization code (if nothing else to set IP addresses) that has the opportunity to adjust tcpEStatsConnTableLatency and other read-write scalars controlling the creation of the various tables, before establishing the first TCP connection. Implementations MAY also choose to make these control scalars persist across reboots. Copyright (C) The IETF Trust (2007). This version of this MIB module is a part of RFC 4898; see the RFC itself for full legal notices.
tcpEStatsNotifications	1.3.6.1.2.1.156.0
NTF tcpEStatsEstablishNotification	1.3.6.1.2.1.156.0.1			The indicated connection has been accepted (or alternatively entered the established state).
NTF tcpEStatsCloseNotification	1.3.6.1.2.1.156.0.2			The indicated connection has left the established state
tcpEStatsMIBObjects	1.3.6.1.2.1.156.1
tcpEStats	1.3.6.1.2.1.156.1.1
tcpEStatsListenerTable	1.3.6.1.2.1.156.1.1.1		not-accessible	This table contains information about TCP Listeners, in addition to the information maintained by the tcpListenerTable RFC 4022.
tcpEStatsListenerEntry	1.3.6.1.2.1.156.1.1.1.1		not-accessible	Each entry in the table contains information about a specific TCP Listener.
TIM tcpEStatsListenerStartTime	1.3.6.1.2.1.156.1.1.1.1.1	TimeStamp	read-only	The value of sysUpTime at the time this listener was established. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
NUM tcpEStatsListenerSynRcvd	1.3.6.1.2.1.156.1.1.1.1.2	ZeroBasedCounter32	read-only	The number of SYNs which have been received for this listener. The total number of failed connections for all reasons can be estimated to be tcpEStatsListenerSynRcvd minus tcpEStatsListenerAccepted and tcpEStatsListenerCurBacklog.
NUM tcpEStatsListenerInitial	1.3.6.1.2.1.156.1.1.1.1.3	ZeroBasedCounter32	read-only	The total number of connections for which the Listener has allocated initial state and placed the connection in the backlog. This may happen in the SYN-RCVD or ESTABLISHED states, depending on the implementation.
NUM tcpEStatsListenerEstablished	1.3.6.1.2.1.156.1.1.1.1.4	ZeroBasedCounter32	read-only	The number of connections that have been established to this endpoint (e.g., the number of first ACKs that have been received for this listener).
NUM tcpEStatsListenerAccepted	1.3.6.1.2.1.156.1.1.1.1.5	ZeroBasedCounter32	read-only	The total number of connections for which the Listener has successfully issued an accept, removing the connection from the backlog.
NUM tcpEStatsListenerExceedBacklog	1.3.6.1.2.1.156.1.1.1.1.6	ZeroBasedCounter32	read-only	The total number of connections dropped from the backlog by this listener due to all reasons. This includes all connections that are allocated initial resources, but are not accepted for some reason.
NUM tcpEStatsListenerHCSynRcvd	1.3.6.1.2.1.156.1.1.1.1.7	ZeroBasedCounter64	read-only	The number of SYNs that have been received for this listener on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerSynRcvd.
NUM tcpEStatsListenerHCInitial	1.3.6.1.2.1.156.1.1.1.1.8	ZeroBasedCounter64	read-only	The total number of connections for which the Listener has allocated initial state and placed the connection in the backlog on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerInitial.
NUM tcpEStatsListenerHCEstablished	1.3.6.1.2.1.156.1.1.1.1.9	ZeroBasedCounter64	read-only	The number of connections that have been established to this endpoint on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerEstablished.
NUM tcpEStatsListenerHCAccepted	1.3.6.1.2.1.156.1.1.1.1.10	ZeroBasedCounter64	read-only	The total number of connections for which the Listener has successfully issued an accept, removing the connection from the backlog on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerAccepted.
NUM tcpEStatsListenerHCExceedBacklog	1.3.6.1.2.1.156.1.1.1.1.11	ZeroBasedCounter64	read-only	The total number of connections dropped from the backlog by this listener due to all reasons on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerExceedBacklog.
G32 tcpEStatsListenerCurConns	1.3.6.1.2.1.156.1.1.1.1.12	Gauge32	read-only	The current number of connections in the ESTABLISHED state, which have also been accepted. It excludes connections that have been established but not accepted because they are still subject to being discarded to shed load without explicit action by either endpoint.
U32 tcpEStatsListenerMaxBacklog	1.3.6.1.2.1.156.1.1.1.1.13	Unsigned32	read-only	The maximum number of connections allowed in the backlog at one time.
G32 tcpEStatsListenerCurBacklog	1.3.6.1.2.1.156.1.1.1.1.14	Gauge32	read-only	The current number of connections that are in the backlog. This gauge includes connections in ESTABLISHED or SYN-RECEIVED states for which the Listener has not yet issued an accept. If this listener is using some technique to implicitly represent the SYN-RECEIVED states (e.g., by cryptographically encoding the state information in the initial sequence number, ISS), it MAY elect to exclude connections in the SYN-RECEIVED state from the backlog.
G32 tcpEStatsListenerCurEstabBacklog	1.3.6.1.2.1.156.1.1.1.1.15	Gauge32	read-only	The current number of connections in the backlog that are in the ESTABLISHED state, but for which the Listener has not yet issued an accept.
tcpEStatsConnectIdTable	1.3.6.1.2.1.156.1.1.2		not-accessible	This table maps information that uniquely identifies each active TCP connection to the connection ID used by other tables in this MIB Module. It is an extension of tcpConnectionTable in RFC 4022. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsConnectIdEntry	1.3.6.1.2.1.156.1.1.2.1		not-accessible	Each entry in this table maps a TCP connection 4-tuple to a connection index.
U32 tcpEStatsConnectIndex	1.3.6.1.2.1.156.1.1.2.1.1	Unsigned32	read-only	A unique integer value assigned to each TCP Connection entry. The RECOMMENDED algorithm is to begin at 1 and increase to some implementation-specific maximum value and then start again at 1 skipping values already in use.
tcpEStatsPerfTable	1.3.6.1.2.1.156.1.1.3		not-accessible	This table contains objects that are useful for measuring TCP performance and first line problem diagnosis. Most objects in this table directly expose some TCP state variable or are easily implemented as simple functions (e.g., the maximum value) of TCP state variables. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsPerfEntry	1.3.6.1.2.1.156.1.1.3.1		not-accessible	Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
NUM tcpEStatsPerfSegsOut	1.3.6.1.2.1.156.1.1.3.1.1	ZeroBasedCounter32	read-only	The total number of segments sent.
NUM tcpEStatsPerfDataSegsOut	1.3.6.1.2.1.156.1.1.3.1.2	ZeroBasedCounter32	read-only	The number of segments sent containing a positive length data segment.
NUM tcpEStatsPerfDataOctetsOut	1.3.6.1.2.1.156.1.1.3.1.3	ZeroBasedCounter32	read-only	The number of octets of data contained in transmitted segments, including retransmitted data. Note that this does not include TCP headers.
NUM tcpEStatsPerfHCDataOctetsOut	1.3.6.1.2.1.156.1.1.3.1.4	ZeroBasedCounter64	read-only	The number of octets of data contained in transmitted segments, including retransmitted data, on systems that can transmit more than 10 million bits per second. Note that this does not include TCP headers.
NUM tcpEStatsPerfSegsRetrans	1.3.6.1.2.1.156.1.1.3.1.5	ZeroBasedCounter32	read-only	The number of segments transmitted containing at least some retransmitted data.
NUM tcpEStatsPerfOctetsRetrans	1.3.6.1.2.1.156.1.1.3.1.6	ZeroBasedCounter32	read-only	The number of octets retransmitted.
NUM tcpEStatsPerfSegsIn	1.3.6.1.2.1.156.1.1.3.1.7	ZeroBasedCounter32	read-only	The total number of segments received.
NUM tcpEStatsPerfDataSegsIn	1.3.6.1.2.1.156.1.1.3.1.8	ZeroBasedCounter32	read-only	The number of segments received containing a positive length data segment.
NUM tcpEStatsPerfDataOctetsIn	1.3.6.1.2.1.156.1.1.3.1.9	ZeroBasedCounter32	read-only	The number of octets contained in received data segments, including retransmitted data. Note that this does not include TCP headers.
NUM tcpEStatsPerfHCDataOctetsIn	1.3.6.1.2.1.156.1.1.3.1.10	ZeroBasedCounter64	read-only	The number of octets contained in received data segments, including retransmitted data, on systems that can receive more than 10 million bits per second. Note that this does not include TCP headers.
NUM tcpEStatsPerfElapsedSecs	1.3.6.1.2.1.156.1.1.3.1.11	ZeroBasedCounter32	read-only	The seconds part of the time elapsed between tcpEStatsPerfStartTimeStamp and the most recent protocol event (segment sent or received).
NUM tcpEStatsPerfElapsedMicroSecs	1.3.6.1.2.1.156.1.1.3.1.12	ZeroBasedCounter32	read-only	The micro-second part of time elapsed between tcpEStatsPerfStartTimeStamp to the most recent protocol event (segment sent or received). This may be updated in whatever time granularity is the system supports.
DAT tcpEStatsPerfStartTimeStamp	1.3.6.1.2.1.156.1.1.3.1.13	DateAndTime	read-only	Time at which this row was created and all ZeroBasedCounters in the row were initialized to zero.
G32 tcpEStatsPerfCurMSS	1.3.6.1.2.1.156.1.1.3.1.14	Gauge32	read-only	The current maximum segment size (MSS), in octets.
G32 tcpEStatsPerfPipeSize	1.3.6.1.2.1.156.1.1.3.1.15	Gauge32	read-only	The TCP senders current estimate of the number of unacknowledged data octets in the network. While not in recovery (e.g., while the receiver is not reporting missing data to the sender), this is precisely the same as 'Flight size' as defined in RFC 2581, which can be computed as SND.NXT minus SND.UNA. [RFC793] During recovery, the TCP sender has incomplete information about the state of the network (e.g., which segments are lost vs reordered, especially if the return path is also dropping TCP acknowledgments). Current TCP standards do not mandate any specific algorithm for estimating the number of unacknowledged data octets in the network. RFC 3517 describes a conservative algorithm to use SACK information to estimate the number of unacknowledged data octets in the network. tcpEStatsPerfPipeSize object SHOULD be the same as 'pipe' as defined in RFC 3517 if it is implemented. (Note that while not in recovery the pipe algorithm yields the same values as flight size). If RFC 3517 is not implemented, the data octets in flight SHOULD be estimated as SND.NXT minus SND.UNA adjusted by some measure of the data that has left the network and retransmitted data. For example, with Reno or NewReno style TCP, the number of duplicate acknowledgment is used to count the number of segments that have left the network. That is, PipeSize=SND.NXT-SND.UNA+(retransmits-dupacks)*CurMSS
G32 tcpEStatsPerfMaxPipeSize	1.3.6.1.2.1.156.1.1.3.1.16	Gauge32	read-only	The maximum value of tcpEStatsPerfPipeSize, for this connection.
G32 tcpEStatsPerfSmoothedRTT	1.3.6.1.2.1.156.1.1.3.1.17	Gauge32	read-only	The smoothed round trip time used in calculation of the RTO. See SRTT in [RFC2988].
G32 tcpEStatsPerfCurRTO	1.3.6.1.2.1.156.1.1.3.1.18	Gauge32	read-only	The current value of the retransmit timer RTO.
NUM tcpEStatsPerfCongSignals	1.3.6.1.2.1.156.1.1.3.1.19	ZeroBasedCounter32	read-only	The number of multiplicative downward congestion window adjustments due to all forms of congestion signals, including Fast Retransmit, Explicit Congestion Notification (ECN), and timeouts. This object summarizes all events that invoke the MD portion of Additive Increase Multiplicative Decrease (AIMD) congestion control, and as such is the best indicator of how a cwnd is being affected by congestion. Note that retransmission timeouts multiplicatively reduce the window implicitly by setting ssthresh, and SHOULD be included in tcpEStatsPerfCongSignals. In order to minimize spurious congestion indications due to out-of-order segments, tcpEStatsPerfCongSignals SHOULD be incremented in association with the Fast Retransmit algorithm.
G32 tcpEStatsPerfCurCwnd	1.3.6.1.2.1.156.1.1.3.1.20	Gauge32	read-only	The current congestion window, in octets.
G32 tcpEStatsPerfCurSsthresh	1.3.6.1.2.1.156.1.1.3.1.21	Gauge32	read-only	The current slow start threshold in octets.
NUM tcpEStatsPerfTimeouts	1.3.6.1.2.1.156.1.1.3.1.22	ZeroBasedCounter32	read-only	The number of times the retransmit timeout has expired when the RTO backoff multiplier is equal to one.
G32 tcpEStatsPerfCurRwinSent	1.3.6.1.2.1.156.1.1.3.1.23	Gauge32	read-only	The most recent window advertisement sent, in octets.
G32 tcpEStatsPerfMaxRwinSent	1.3.6.1.2.1.156.1.1.3.1.24	Gauge32	read-only	The maximum window advertisement sent, in octets.
NUM tcpEStatsPerfZeroRwinSent	1.3.6.1.2.1.156.1.1.3.1.25	ZeroBasedCounter32	read-only	The number of acknowledgments sent announcing a zero receive window, when the previously announced window was not zero.
G32 tcpEStatsPerfCurRwinRcvd	1.3.6.1.2.1.156.1.1.3.1.26	Gauge32	read-only	The most recent window advertisement received, in octets.
G32 tcpEStatsPerfMaxRwinRcvd	1.3.6.1.2.1.156.1.1.3.1.27	Gauge32	read-only	The maximum window advertisement received, in octets.
NUM tcpEStatsPerfZeroRwinRcvd	1.3.6.1.2.1.156.1.1.3.1.28	ZeroBasedCounter32	read-only	The number of acknowledgments received announcing a zero receive window, when the previously announced window was not zero.
NUM tcpEStatsPerfSndLimTransRwin	1.3.6.1.2.1.156.1.1.3.1.31	ZeroBasedCounter32	read-only	The number of transitions into the 'Receiver Limited' state from either the 'Congestion Limited' or 'Sender Limited' states. This state is entered whenever TCP transmission stops because the sender has filled the announced receiver window, i.e., when SND.NXT has advanced to SND.UNA + SND.WND - 1 as described in RFC 793.
NUM tcpEStatsPerfSndLimTransCwnd	1.3.6.1.2.1.156.1.1.3.1.32	ZeroBasedCounter32	read-only	The number of transitions into the 'Congestion Limited' state from either the 'Receiver Limited' or 'Sender Limited' states. This state is entered whenever TCP transmission stops because the sender has reached some limit defined by congestion control (e.g., cwnd) or other algorithms (retransmission timeouts) designed to control network traffic. See the definition of 'CONGESTION WINDOW' in RFC 2581.
NUM tcpEStatsPerfSndLimTransSnd	1.3.6.1.2.1.156.1.1.3.1.33	ZeroBasedCounter32	read-only	The number of transitions into the 'Sender Limited' state from either the 'Receiver Limited' or 'Congestion Limited' states. This state is entered whenever TCP transmission stops due to some sender limit such as running out of application data or other resources and the Karn algorithm. When TCP stops sending data for any reason, which cannot be classified as Receiver Limited or Congestion Limited, it MUST be treated as Sender Limited.
NUM tcpEStatsPerfSndLimTimeRwin	1.3.6.1.2.1.156.1.1.3.1.34	ZeroBasedCounter32	read-only	The cumulative time spent in the 'Receiver Limited' state. See tcpEStatsPerfSndLimTransRwin.
NUM tcpEStatsPerfSndLimTimeCwnd	1.3.6.1.2.1.156.1.1.3.1.35	ZeroBasedCounter32	read-only	The cumulative time spent in the 'Congestion Limited' state. See tcpEStatsPerfSndLimTransCwnd. When there is a retransmission timeout, it SHOULD be counted in tcpEStatsPerfSndLimTimeCwnd (and not the cumulative time for some other state.)
NUM tcpEStatsPerfSndLimTimeSnd	1.3.6.1.2.1.156.1.1.3.1.36	ZeroBasedCounter32	read-only	The cumulative time spent in the 'Sender Limited' state. See tcpEStatsPerfSndLimTransSnd.
tcpEStatsPathTable	1.3.6.1.2.1.156.1.1.4		not-accessible	This table contains objects that can be used to infer detailed behavior of the Internet path, such as the extent that there is reordering, ECN bits, and if RTT fluctuations are correlated to losses. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsPathEntry	1.3.6.1.2.1.156.1.1.4.1		not-accessible	Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
G32 tcpEStatsPathRetranThresh	1.3.6.1.2.1.156.1.1.4.1.1	Gauge32	read-only	The number of duplicate acknowledgments required to trigger Fast Retransmit. Note that although this is constant in traditional Reno TCP implementations, it is adaptive in many newer TCPs.
NUM tcpEStatsPathNonRecovDAEpisodes	1.3.6.1.2.1.156.1.1.4.1.2	ZeroBasedCounter32	read-only	The number of duplicate acknowledgment episodes that did not trigger a Fast Retransmit because ACK advanced prior to the number of duplicate acknowledgments reaching RetranThresh. In many implementations this is the number of times the 'dupacks' counter is set to zero when it is non-zero but less than RetranThresh. Note that the change in tcpEStatsPathNonRecovDAEpisodes divided by the change in tcpEStatsPerfDataSegsOut is an estimate of the frequency of data reordering on the forward path over some interval.
NUM tcpEStatsPathSumOctetsReordered	1.3.6.1.2.1.156.1.1.4.1.3	ZeroBasedCounter32	read-only	The sum of the amounts SND.UNA advances on the acknowledgment which ends a dup-ack episode without a retransmission. Note the change in tcpEStatsPathSumOctetsReordered divided by the change in tcpEStatsPathNonRecovDAEpisodes is an estimates of the average reordering distance, over some interval.
NUM tcpEStatsPathNonRecovDA	1.3.6.1.2.1.156.1.1.4.1.4	ZeroBasedCounter32	read-only	Duplicate acks (or SACKS) that did not trigger a Fast Retransmit because ACK advanced prior to the number of duplicate acknowledgments reaching RetranThresh. In many implementations, this is the sum of the 'dupacks' counter, just before it is set to zero because ACK advanced without a Fast Retransmit. Note that the change in tcpEStatsPathNonRecovDA divided by the change in tcpEStatsPathNonRecovDAEpisodes is an estimate of the average reordering distance in segments over some interval.
G32 tcpEStatsPathSampleRTT	1.3.6.1.2.1.156.1.1.4.1.11	Gauge32	read-only	The most recent raw round trip time measurement used in calculation of the RTO.
G32 tcpEStatsPathRTTVar	1.3.6.1.2.1.156.1.1.4.1.12	Gauge32	read-only	The round trip time variation used in calculation of the RTO. See RTTVAR in [RFC2988].
G32 tcpEStatsPathMaxRTT	1.3.6.1.2.1.156.1.1.4.1.13	Gauge32	read-only	The maximum sampled round trip time.
G32 tcpEStatsPathMinRTT	1.3.6.1.2.1.156.1.1.4.1.14	Gauge32	read-only	The minimum sampled round trip time.
NUM tcpEStatsPathSumRTT	1.3.6.1.2.1.156.1.1.4.1.15	ZeroBasedCounter32	read-only	The sum of all sampled round trip times. Note that the change in tcpEStatsPathSumRTT divided by the change in tcpEStatsPathCountRTT is the mean RTT, uniformly averaged over an enter interval.
NUM tcpEStatsPathHCSumRTT	1.3.6.1.2.1.156.1.1.4.1.16	ZeroBasedCounter64	read-only	The sum of all sampled round trip times, on all systems that implement multiple concurrent RTT measurements. Note that the change in tcpEStatsPathHCSumRTT divided by the change in tcpEStatsPathCountRTT is the mean RTT, uniformly averaged over an enter interval.
NUM tcpEStatsPathCountRTT	1.3.6.1.2.1.156.1.1.4.1.17	ZeroBasedCounter32	read-only	The number of round trip time samples included in tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT.
G32 tcpEStatsPathMaxRTO	1.3.6.1.2.1.156.1.1.4.1.18	Gauge32	read-only	The maximum value of the retransmit timer RTO.
G32 tcpEStatsPathMinRTO	1.3.6.1.2.1.156.1.1.4.1.19	Gauge32	read-only	The minimum value of the retransmit timer RTO.
U32 tcpEStatsPathIpTtl	1.3.6.1.2.1.156.1.1.4.1.20	Unsigned32	read-only	The value of the TTL field carried in the most recently received IP header. This is sometimes useful to detect changing or unstable routes.
OCT tcpEStatsPathIpTosIn	1.3.6.1.2.1.156.1.1.4.1.21	OCTET STRING	read-only	The value of the IPv4 Type of Service octet, or the IPv6 traffic class octet, carried in the most recently received IP header. This is useful to diagnose interactions between TCP and any IP layer packet scheduling and delivery policy, which might be in effect to implement Diffserv.
OCT tcpEStatsPathIpTosOut	1.3.6.1.2.1.156.1.1.4.1.22	OCTET STRING	read-only	The value of the IPv4 Type Of Service octet, or the IPv6 traffic class octet, carried in the most recently transmitted IP header. This is useful to diagnose interactions between TCP and any IP layer packet scheduling and delivery policy, which might be in effect to implement Diffserv.
NUM tcpEStatsPathPreCongSumCwnd	1.3.6.1.2.1.156.1.1.4.1.23	ZeroBasedCounter32	read-only	The sum of the values of the congestion window, in octets, captured each time a congestion signal is received. This MUST be updated each time tcpEStatsPerfCongSignals is incremented, such that the change in tcpEStatsPathPreCongSumCwnd divided by the change in tcpEStatsPerfCongSignals is the average window (over some interval) just prior to a congestion signal.
NUM tcpEStatsPathPreCongSumRTT	1.3.6.1.2.1.156.1.1.4.1.24	ZeroBasedCounter32	read-only	Sum of the last sample of the RTT (tcpEStatsPathSampleRTT) prior to the received congestion signals. This MUST be updated each time tcpEStatsPerfCongSignals is incremented, such that the change in tcpEStatsPathPreCongSumRTT divided by the change in tcpEStatsPerfCongSignals is the average RTT (over some interval) just prior to a congestion signal.
NUM tcpEStatsPathPostCongSumRTT	1.3.6.1.2.1.156.1.1.4.1.25	ZeroBasedCounter32	read-only	Sum of the first sample of the RTT (tcpEStatsPathSampleRTT) following each congestion signal. Such that the change in tcpEStatsPathPostCongSumRTT divided by the change in tcpEStatsPathPostCongCountRTT is the average RTT (over some interval) just after a congestion signal.
NUM tcpEStatsPathPostCongCountRTT	1.3.6.1.2.1.156.1.1.4.1.26	ZeroBasedCounter32	read-only	The number of RTT samples included in tcpEStatsPathPostCongSumRTT such that the change in tcpEStatsPathPostCongSumRTT divided by the change in tcpEStatsPathPostCongCountRTT is the average RTT (over some interval) just after a congestion signal.
NUM tcpEStatsPathECNsignals	1.3.6.1.2.1.156.1.1.4.1.27	ZeroBasedCounter32	read-only	The number of congestion signals delivered to the TCP sender via explicit congestion notification (ECN). This is typically the number of segments bearing Echo Congestion Experienced (ECE) bits, but should also include segments failing the ECN nonce check or other explicit congestion signals.
NUM tcpEStatsPathDupAckEpisodes	1.3.6.1.2.1.156.1.1.4.1.28	ZeroBasedCounter32	read-only	The number of Duplicate Acks Sent when prior Ack was not duplicate. This is the number of times that a contiguous series of duplicate acknowledgments have been sent. This is an indication of the number of data segments lost or reordered on the path from the remote TCP endpoint to the near TCP endpoint.
G32 tcpEStatsPathRcvRTT	1.3.6.1.2.1.156.1.1.4.1.29	Gauge32	read-only	The receiver's estimate of the Path RTT. Adaptive receiver window algorithms depend on the receiver to having a good estimate of the path RTT.
NUM tcpEStatsPathDupAcksOut	1.3.6.1.2.1.156.1.1.4.1.30	ZeroBasedCounter32	read-only	The number of duplicate ACKs sent. The ratio of the change in tcpEStatsPathDupAcksOut to the change in tcpEStatsPathDupAckEpisodes is an indication of reorder or recovery distance over some interval.
NUM tcpEStatsPathCERcvd	1.3.6.1.2.1.156.1.1.4.1.31	ZeroBasedCounter32	read-only	The number of segments received with IP headers bearing Congestion Experienced (CE) markings.
NUM tcpEStatsPathECESent	1.3.6.1.2.1.156.1.1.4.1.32	ZeroBasedCounter32	read-only	Number of times the Echo Congestion Experienced (ECE) bit in the TCP header has been set (transitioned from 0 to 1), due to a Congestion Experienced (CE) marking on an IP header. Note that ECE can be set and reset only once per RTT, while CE can be set on many segments per RTT.
tcpEStatsStackTable	1.3.6.1.2.1.156.1.1.5		not-accessible	This table contains objects that are most useful for determining how well some of the TCP control algorithms are coping with this particular path. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsStackEntry	1.3.6.1.2.1.156.1.1.5.1		not-accessible	Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
T/F tcpEStatsStackActiveOpen	1.3.6.1.2.1.156.1.1.5.1.1	TruthValue	read-only	True(1) if the local connection traversed the SYN-SENT state, else false(2).
U32 tcpEStatsStackMSSSent	1.3.6.1.2.1.156.1.1.5.1.2	Unsigned32	read-only	The value sent in an MSS option, or zero if none.
U32 tcpEStatsStackMSSRcvd	1.3.6.1.2.1.156.1.1.5.1.3	Unsigned32	read-only	The value received in an MSS option, or zero if none.
I32 tcpEStatsStackWinScaleSent	1.3.6.1.2.1.156.1.1.5.1.4	Integer32	read-only	The value of the transmitted window scale option if one was sent; otherwise, a value of -1. Note that if both tcpEStatsStackWinScaleSent and tcpEStatsStackWinScaleRcvd are not -1, then Rcv.Wind.Scale will be the same as this value and used to scale receiver window announcements from the local host to the remote host.
I32 tcpEStatsStackWinScaleRcvd	1.3.6.1.2.1.156.1.1.5.1.5	Integer32	read-only	The value of the received window scale option if one was received; otherwise, a value of -1. Note that if both tcpEStatsStackWinScaleSent and tcpEStatsStackWinScaleRcvd are not -1, then Snd.Wind.Scale will be the same as this value and used to scale receiver window announcements from the remote host to the local host.
TCP tcpEStatsStackTimeStamps	1.3.6.1.2.1.156.1.1.5.1.6	TcpEStatsNegotiated	read-only	Enabled(1) if TCP timestamps have been negotiated on, selfDisabled(2) if they are disabled or not implemented on the local host, or peerDisabled(3) if not negotiated by the remote hosts.
TCP tcpEStatsStackECN	1.3.6.1.2.1.156.1.1.5.1.7	TcpEStatsNegotiated	read-only	Enabled(1) if Explicit Congestion Notification (ECN) has been negotiated on, selfDisabled(2) if it is disabled or not implemented on the local host, or peerDisabled(3) if not negotiated by the remote hosts.
TCP tcpEStatsStackWillSendSACK	1.3.6.1.2.1.156.1.1.5.1.8	TcpEStatsNegotiated	read-only	Enabled(1) if the local host will send SACK options, selfDisabled(2) if SACK is disabled or not implemented on the local host, or peerDisabled(3) if the remote host did not send the SACK-permitted option. Note that SACK negotiation is not symmetrical. SACK can enabled on one side of the connection and not the other.
TCP tcpEStatsStackWillUseSACK	1.3.6.1.2.1.156.1.1.5.1.9	TcpEStatsNegotiated	read-only	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.
INT tcpEStatsStackState	1.3.6.1.2.1.156.1.1.5.1.10	INTEGER	read-only	An integer value representing the connection state from the TCP State Transition Diagram. The value listen(2) is included only for parallelism to the old tcpConnTable, and SHOULD NOT be used because the listen state in managed by the tcpListenerTable. The value DeleteTcb(12) is included only for parallelism to the tcpConnTable mechanism for terminating connections, although this table does not permit writing.
T/F tcpEStatsStackNagle	1.3.6.1.2.1.156.1.1.5.1.11	TruthValue	read-only	True(1) if the Nagle algorithm is being used, else false(2).
G32 tcpEStatsStackMaxSsCwnd	1.3.6.1.2.1.156.1.1.5.1.12	Gauge32	read-only	The maximum congestion window used during Slow Start, in octets.
G32 tcpEStatsStackMaxCaCwnd	1.3.6.1.2.1.156.1.1.5.1.13	Gauge32	read-only	The maximum congestion window used during Congestion Avoidance, in octets.
G32 tcpEStatsStackMaxSsthresh	1.3.6.1.2.1.156.1.1.5.1.14	Gauge32	read-only	The maximum slow start threshold, excluding the initial value.
G32 tcpEStatsStackMinSsthresh	1.3.6.1.2.1.156.1.1.5.1.15	Gauge32	read-only	The minimum slow start threshold.
INT tcpEStatsStackInRecovery	1.3.6.1.2.1.156.1.1.5.1.16	INTEGER	read-only	An integer value representing the state of the loss recovery for this connection. tcpESDataContiguous(1) indicates that the remote receiver is reporting contiguous data (no duplicate acknowledgments or SACK options) and that there are no unacknowledged retransmissions. tcpESDataUnordered(2) indicates that the remote receiver is reporting missing or out-of-order data (e.g., sending duplicate acknowledgments or SACK options) and that there are no unacknowledged retransmissions (because the missing data has not yet been retransmitted). tcpESDataRecovery(3) indicates that the sender has outstanding retransmitted data that is still unacknowledged.
NUM tcpEStatsStackDupAcksIn	1.3.6.1.2.1.156.1.1.5.1.17	ZeroBasedCounter32	read-only	The number of duplicate ACKs received.
NUM tcpEStatsStackSpuriousFrDetected	1.3.6.1.2.1.156.1.1.5.1.18	ZeroBasedCounter32	read-only	The number of acknowledgments reporting out-of-order segments after the Fast Retransmit algorithm has already retransmitted the segments. (For example as detected by the Eifel algorithm).'
NUM tcpEStatsStackSpuriousRtoDetected	1.3.6.1.2.1.156.1.1.5.1.19	ZeroBasedCounter32	read-only	The number of acknowledgments reporting segments that have already been retransmitted due to a Retransmission Timeout.
NUM tcpEStatsStackSoftErrors	1.3.6.1.2.1.156.1.1.5.1.21	ZeroBasedCounter32	read-only	The number of segments that fail various consistency tests during TCP input processing. Soft errors might cause the segment to be discarded but some do not. Some of these soft errors cause the generation of a TCP acknowledgment, while others are silently discarded.
INT tcpEStatsStackSoftErrorReason	1.3.6.1.2.1.156.1.1.5.1.22	INTEGER	read-only	This object identifies which consistency test most recently failed during TCP input processing. This object SHOULD be set every time tcpEStatsStackSoftErrors is incremented. The codes are as follows: belowDataWindow(1) - All data in the segment is below SND.UNA. (Normal for keep-alives and zero window probes). aboveDataWindow(2) - Some data in the segment is above SND.WND. (Indicates an implementation bug or possible attack). belowAckWindow(3) - ACK below SND.UNA. (Indicates that the return path is reordering ACKs) aboveAckWindow(4) - An ACK for data that we have not sent. (Indicates an implementation bug or possible attack). belowTSWindow(5) - TSecr on the segment is older than the current TS.Recent (Normal for the rare case where PAWS detects data reordered by the network). aboveTSWindow(6) - TSecr on the segment is newer than the current TS.Recent. (Indicates an implementation bug or possible attack). dataCheckSum(7) - Incorrect checksum. Note that this value is intrinsically fragile, because the header fields used to identify the connection may have been corrupted. otherSoftError(8) - All other soft errors not listed above.
NUM tcpEStatsStackSlowStart	1.3.6.1.2.1.156.1.1.5.1.23	ZeroBasedCounter32	read-only	The number of times the congestion window has been increased by the Slow Start algorithm.
NUM tcpEStatsStackCongAvoid	1.3.6.1.2.1.156.1.1.5.1.24	ZeroBasedCounter32	read-only	The number of times the congestion window has been increased by the Congestion Avoidance algorithm.
NUM tcpEStatsStackOtherReductions	1.3.6.1.2.1.156.1.1.5.1.25	ZeroBasedCounter32	read-only	The number of congestion window reductions made as a result of anything other than AIMD congestion control algorithms. Examples of non-multiplicative window reductions include Congestion Window Validation [RFC2861] and experimental algorithms such as Vegas [Bra94]. All window reductions MUST be counted as either tcpEStatsPerfCongSignals or tcpEStatsStackOtherReductions.
NUM tcpEStatsStackCongOverCount	1.3.6.1.2.1.156.1.1.5.1.26	ZeroBasedCounter32	read-only	The number of congestion events that were 'backed out' of the congestion control state machine such that the congestion window was restored to a prior value. This can happen due to the Eifel algorithm [RFC3522] or other algorithms that can be used to detect and cancel spurious invocations of the Fast Retransmit Algorithm. Although it may be feasible to undo the effects of spurious invocation of the Fast Retransmit congestion events cannot easily be backed out of tcpEStatsPerfCongSignals and tcpEStatsPathPreCongSumCwnd, etc.
NUM tcpEStatsStackFastRetran	1.3.6.1.2.1.156.1.1.5.1.27	ZeroBasedCounter32	read-only	The number of invocations of the Fast Retransmit algorithm.
NUM tcpEStatsStackSubsequentTimeouts	1.3.6.1.2.1.156.1.1.5.1.28	ZeroBasedCounter32	read-only	The number of times the retransmit timeout has expired after the RTO has been doubled. See Section 5.5 of RFC 2988.
G32 tcpEStatsStackCurTimeoutCount	1.3.6.1.2.1.156.1.1.5.1.29	Gauge32	read-only	The current number of times the retransmit timeout has expired without receiving an acknowledgment for new data. tcpEStatsStackCurTimeoutCount is reset to zero when new data is acknowledged and incremented for each invocation of Section 5.5 of RFC 2988.
NUM tcpEStatsStackAbruptTimeouts	1.3.6.1.2.1.156.1.1.5.1.30	ZeroBasedCounter32	read-only	The number of timeouts that occurred without any immediately preceding duplicate acknowledgments or other indications of congestion. Abrupt Timeouts indicate that the path lost an entire window of data or acknowledgments. Timeouts that are preceded by duplicate acknowledgments or other congestion signals (e.g., ECN) are not counted as abrupt, and might have been avoided by a more sophisticated Fast Retransmit algorithm.
NUM tcpEStatsStackSACKsRcvd	1.3.6.1.2.1.156.1.1.5.1.31	ZeroBasedCounter32	read-only	The number of SACK options received.
NUM tcpEStatsStackSACKBlocksRcvd	1.3.6.1.2.1.156.1.1.5.1.32	ZeroBasedCounter32	read-only	The number of SACK blocks received (within SACK options).
NUM tcpEStatsStackSendStall	1.3.6.1.2.1.156.1.1.5.1.33	ZeroBasedCounter32	read-only	The number of interface stalls or other sender local resource limitations that are treated as congestion signals.
NUM tcpEStatsStackDSACKDups	1.3.6.1.2.1.156.1.1.5.1.34	ZeroBasedCounter32	read-only	The number of duplicate segments reported to the local host by D-SACK blocks.
G32 tcpEStatsStackMaxMSS	1.3.6.1.2.1.156.1.1.5.1.35	Gauge32	read-only	The maximum MSS, in octets.
G32 tcpEStatsStackMinMSS	1.3.6.1.2.1.156.1.1.5.1.36	Gauge32	read-only	The minimum MSS, in octets.
U32 tcpEStatsStackSndInitial	1.3.6.1.2.1.156.1.1.5.1.37	Unsigned32	read-only	Initial send sequence number. Note that by definition tcpEStatsStackSndInitial never changes for a given connection.
U32 tcpEStatsStackRecInitial	1.3.6.1.2.1.156.1.1.5.1.38	Unsigned32	read-only	Initial receive sequence number. Note that by definition tcpEStatsStackRecInitial never changes for a given connection.
G32 tcpEStatsStackCurRetxQueue	1.3.6.1.2.1.156.1.1.5.1.39	Gauge32	read-only	The current number of octets of data occupying the retransmit queue.
G32 tcpEStatsStackMaxRetxQueue	1.3.6.1.2.1.156.1.1.5.1.40	Gauge32	read-only	The maximum number of octets of data occupying the retransmit queue.
G32 tcpEStatsStackCurReasmQueue	1.3.6.1.2.1.156.1.1.5.1.41	Gauge32	read-only	The current number of octets of sequence space spanned by the reassembly queue. This is generally the difference between rcv.nxt and the sequence number of the right most edge of the reassembly queue.
G32 tcpEStatsStackMaxReasmQueue	1.3.6.1.2.1.156.1.1.5.1.42	Gauge32	read-only	The maximum value of tcpEStatsStackCurReasmQueue
tcpEStatsAppTable	1.3.6.1.2.1.156.1.1.6		not-accessible	This table contains objects that are useful for determining if the application using TCP is limiting TCP performance. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsAppEntry	1.3.6.1.2.1.156.1.1.6.1		not-accessible	Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
C32 tcpEStatsAppSndUna	1.3.6.1.2.1.156.1.1.6.1.1	Counter32	read-only	The value of SND.UNA, the oldest unacknowledged sequence number. Note that SND.UNA is a TCP state variable that is congruent to Counter32 semantics.
U32 tcpEStatsAppSndNxt	1.3.6.1.2.1.156.1.1.6.1.2	Unsigned32	read-only	The value of SND.NXT, the next sequence number to be sent. Note that tcpEStatsAppSndNxt is not monotonic (and thus not a counter) because TCP sometimes retransmits lost data by pulling tcpEStatsAppSndNxt back to the missing data.
C32 tcpEStatsAppSndMax	1.3.6.1.2.1.156.1.1.6.1.3	Counter32	read-only	The farthest forward (right most or largest) SND.NXT value. Note that this will be equal to tcpEStatsAppSndNxt except when tcpEStatsAppSndNxt is pulled back during recovery.
NUM tcpEStatsAppThruOctetsAcked	1.3.6.1.2.1.156.1.1.6.1.4	ZeroBasedCounter32	read-only	The number of octets for which cumulative acknowledgments have been received. Note that this will be the sum of changes to tcpEStatsAppSndUna.
NUM tcpEStatsAppHCThruOctetsAcked	1.3.6.1.2.1.156.1.1.6.1.5	ZeroBasedCounter64	read-only	The number of octets for which cumulative acknowledgments have been received, on systems that can receive more than 10 million bits per second. Note that this will be the sum of changes in tcpEStatsAppSndUna.
C32 tcpEStatsAppRcvNxt	1.3.6.1.2.1.156.1.1.6.1.6	Counter32	read-only	The value of RCV.NXT. The next sequence number expected on an incoming segment, and the left or lower edge of the receive window. Note that RCV.NXT is a TCP state variable that is congruent to Counter32 semantics.
NUM tcpEStatsAppThruOctetsReceived	1.3.6.1.2.1.156.1.1.6.1.7	ZeroBasedCounter32	read-only	The number of octets for which cumulative acknowledgments have been sent. Note that this will be the sum of changes to tcpEStatsAppRcvNxt.
NUM tcpEStatsAppHCThruOctetsReceived	1.3.6.1.2.1.156.1.1.6.1.8	ZeroBasedCounter64	read-only	The number of octets for which cumulative acknowledgments have been sent, on systems that can transmit more than 10 million bits per second. Note that this will be the sum of changes in tcpEStatsAppRcvNxt.
G32 tcpEStatsAppCurAppWQueue	1.3.6.1.2.1.156.1.1.6.1.11	Gauge32	read-only	The current number of octets of application data buffered by TCP, pending first transmission, i.e., to the left of SND.NXT or SndMax. This data will generally be transmitted (and SND.NXT advanced to the left) as soon as there is an available congestion window (cwnd) or receiver window (rwin). This is the amount of data readily available for transmission, without scheduling the application. TCP performance may suffer if there is insufficient queued write data.
G32 tcpEStatsAppMaxAppWQueue	1.3.6.1.2.1.156.1.1.6.1.12	Gauge32	read-only	The maximum number of octets of application data buffered by TCP, pending first transmission. This is the maximum value of tcpEStatsAppCurAppWQueue. This pair of objects can be used to determine if insufficient queued data is steady state (suggesting insufficient queue space) or transient (suggesting insufficient application performance or excessive CPU load or scheduler latency).
G32 tcpEStatsAppCurAppRQueue	1.3.6.1.2.1.156.1.1.6.1.13	Gauge32	read-only	The current number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
G32 tcpEStatsAppMaxAppRQueue	1.3.6.1.2.1.156.1.1.6.1.14	Gauge32	read-only	The maximum number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
tcpEStatsTuneTable	1.3.6.1.2.1.156.1.1.7		not-accessible	This table contains per-connection controls that can be used to work around a number of common problems that plague TCP over some paths. All can be characterized as limiting the growth of the congestion window so as to prevent TCP from overwhelming some component in the path. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
tcpEStatsTuneEntry	1.3.6.1.2.1.156.1.1.7.1		not-accessible	Each entry in this table is a control that can be used to place limits on each active TCP connection.
U32 tcpEStatsTuneLimCwnd	1.3.6.1.2.1.156.1.1.7.1.1	Unsigned32	read-write	A control to set the maximum congestion window that may be used, in octets.
U32 tcpEStatsTuneLimSsthresh	1.3.6.1.2.1.156.1.1.7.1.2	Unsigned32	read-write	A control to limit the maximum queue space (in octets) that this TCP connection is likely to occupy during slowstart. It can be implemented with the algorithm described in RFC 3742 by setting the max_ssthresh parameter to twice tcpEStatsTuneLimSsthresh. This algorithm can be used to overcome some TCP performance problems over network paths that do not have sufficient buffering to withstand the bursts normally present during slowstart.
U32 tcpEStatsTuneLimRwin	1.3.6.1.2.1.156.1.1.7.1.3	Unsigned32	read-write	A control to set the maximum window advertisement that may be sent, in octets.
U32 tcpEStatsTuneLimMSS	1.3.6.1.2.1.156.1.1.7.1.4	Unsigned32	read-write	A control to limit the maximum segment size in octets, that this TCP connection can use.
tcpEStatsControl	1.3.6.1.2.1.156.1.2
T/F tcpEStatsControlPath	1.3.6.1.2.1.156.1.2.1	TruthValue	read-write	Controls the activation of the TCP Path Statistics table. A value 'true' indicates that the TCP Path Statistics table is active, while 'false' indicates that the table is inactive.
T/F tcpEStatsControlStack	1.3.6.1.2.1.156.1.2.2	TruthValue	read-write	Controls the activation of the TCP Stack Statistics table. A value 'true' indicates that the TCP Stack Statistics table is active, while 'false' indicates that the table is inactive.
T/F tcpEStatsControlApp	1.3.6.1.2.1.156.1.2.3	TruthValue	read-write	Controls the activation of the TCP Application Statistics table. A value 'true' indicates that the TCP Application Statistics table is active, while 'false' indicates that the table is inactive.
T/F tcpEStatsControlTune	1.3.6.1.2.1.156.1.2.4	TruthValue	read-write	Controls the activation of the TCP Tuning table. A value 'true' indicates that the TCP Tuning table is active, while 'false' indicates that the table is inactive.
T/F tcpEStatsControlNotify	1.3.6.1.2.1.156.1.2.5	TruthValue	read-write	Controls the generation of all notifications defined in this MIB. A value 'true' indicates that the notifications are active, while 'false' indicates that the notifications are inactive.
U32 tcpEStatsConnTableLatency	1.3.6.1.2.1.156.1.2.6	Unsigned32	read-write	Specifies the number of seconds that the entity will retain entries in the TCP connection tables, after the connection first enters the closed state. The entity SHOULD provide a configuration option to enable customization of this value. A value of 0 results in entries being removed from the tables as soon as the connection enters the closed state. The value of this object pertains to the following tables: tcpEStatsConnectIdTable tcpEStatsPerfTable tcpEStatsPathTable tcpEStatsStackTable tcpEStatsAppTable tcpEStatsTuneTable
tcpEStatsScalar	1.3.6.1.2.1.156.1.3
TIM tcpEStatsListenerTableLastChange	1.3.6.1.2.1.156.1.3.3	TimeStamp	read-only	The value of sysUpTime at the time of the last creation or deletion of an entry in the tcpListenerTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
tcpEStatsConformance	1.3.6.1.2.1.156.2
tcpEStatsCompliances	1.3.6.1.2.1.156.2.1
tcpEStatsCompliance	1.3.6.1.2.1.156.2.1.1			Compliance statement for all systems that implement TCP extended statistics.
tcpEStatsGroups	1.3.6.1.2.1.156.2.2
tcpEStatsListenerGroup	1.3.6.1.2.1.156.2.2.1			The tcpEStatsListener group includes objects that provide valuable statistics and debugging information for TCP Listeners.
tcpEStatsListenerHCGroup	1.3.6.1.2.1.156.2.2.2			The tcpEStatsListenerHC group includes 64-bit counters in tcpEStatsListenerTable.
tcpEStatsConnectIdGroup	1.3.6.1.2.1.156.2.2.3			The tcpEStatsConnectId group includes objects that identify TCP connections and control how long TCP connection entries are retained in the tables.
tcpEStatsPerfGroup	1.3.6.1.2.1.156.2.2.4			The tcpEStatsPerf group includes those objects that provide basic performance data for a TCP connection.
tcpEStatsPerfOptionalGroup	1.3.6.1.2.1.156.2.2.5			The tcpEStatsPerf group includes those objects that provide basic performance data for a TCP connection.
tcpEStatsPerfHCGroup	1.3.6.1.2.1.156.2.2.6			The tcpEStatsPerfHC group includes 64-bit counters in the tcpEStatsPerfTable.
tcpEStatsPathGroup	1.3.6.1.2.1.156.2.2.7			The tcpEStatsPath group includes objects that control the creation of the tcpEStatsPathTable, and provide information about the path for each TCP connection.
tcpEStatsPathOptionalGroup	1.3.6.1.2.1.156.2.2.8			The tcpEStatsPath group includes objects that provide additional information about the path for each TCP connection.
tcpEStatsPathHCGroup	1.3.6.1.2.1.156.2.2.9			The tcpEStatsPathHC group includes 64-bit counters in the tcpEStatsPathTable.
tcpEStatsStackGroup	1.3.6.1.2.1.156.2.2.10			The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsStackTable, and provide information about the operation of algorithms used within TCP.
tcpEStatsStackOptionalGroup	1.3.6.1.2.1.156.2.2.11			The tcpEStatsConnState group includes objects that provide additional information about the operation of algorithms used within TCP.
tcpEStatsAppGroup	1.3.6.1.2.1.156.2.2.12			The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsAppTable, and provide information about the operation of algorithms used within TCP.
tcpEStatsAppHCGroup	1.3.6.1.2.1.156.2.2.13			The tcpEStatsStackHC group includes 64-bit counters in the tcpEStatsStackTable.
tcpEStatsAppOptionalGroup	1.3.6.1.2.1.156.2.2.14			The tcpEStatsConnState group includes objects that provide additional information about how applications are interacting with each TCP connection.
tcpEStatsTuneOptionalGroup	1.3.6.1.2.1.156.2.2.15			The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsConnectionTable, which can be used to set tuning parameters for each TCP connection.
tcpEStatsNotificationsGroup	1.3.6.1.2.1.156.2.2.16			Notifications sent by a TCP extended statistics agent.
tcpEStatsNotificationsCtlGroup	1.3.6.1.2.1.156.2.2.17			The tcpEStatsNotificationsCtl group includes the object that controls the creation of the events in the tcpEStatsNotificationsGroup.

RFC description

IETF standard MIB (RFC 4898) providing enhanced TCP statistics and performance metrics for diagnostic analysis of TCP connections.

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. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TCP-ESTATS-MIB

What Is TCP-ESTATS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description