TCP-ESTATS-MIB

File: TCP-ESTATS-MIB.mib (108146 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF RMON2-MIB
HCNUM-TC SNMPv2-TC TCP-MIB

Imported symbols

MODULE-IDENTITY Counter32 Integer32
Unsigned32 Gauge32 OBJECT-TYPE
mib-2 NOTIFICATION-TYPE MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP ZeroBasedCounter32
ZeroBasedCounter64 TEXTUAL-CONVENTION DateAndTime
TruthValue TimeStamp tcpListenerEntry
tcpConnectionEntry

Defined Types

TcpEStatsNegotiated  
Indicates if some optional TCP feature was negotiated. Enabled(1) indicates that the feature was successfully negotiated on, which generally requires both hosts to agree to use the feature. selfDisabled(2) indicates that the local host refused the feature because it is not implemented, configured off, or refused for some other reason, such as the lack of resources. peerDisabled(3) indicates that the local host was willing to negotiate the feature, but the remote host did not do so.
TEXTUAL-CONVENTION    
  INTEGER enabled(1), selfDisabled(2), peerDisabled(3)  

TcpEStatsListenerEntry  
SEQUENCE    
  tcpEStatsListenerStartTime TimeStamp
  tcpEStatsListenerSynRcvd ZeroBasedCounter32
  tcpEStatsListenerInitial ZeroBasedCounter32
  tcpEStatsListenerEstablished ZeroBasedCounter32
  tcpEStatsListenerAccepted ZeroBasedCounter32
  tcpEStatsListenerExceedBacklog ZeroBasedCounter32
  tcpEStatsListenerHCSynRcvd ZeroBasedCounter64
  tcpEStatsListenerHCInitial ZeroBasedCounter64
  tcpEStatsListenerHCEstablished ZeroBasedCounter64
  tcpEStatsListenerHCAccepted ZeroBasedCounter64
  tcpEStatsListenerHCExceedBacklog ZeroBasedCounter64
  tcpEStatsListenerCurConns Gauge32
  tcpEStatsListenerMaxBacklog Unsigned32
  tcpEStatsListenerCurBacklog Gauge32
  tcpEStatsListenerCurEstabBacklog Gauge32

TcpEStatsConnectIdEntry  
SEQUENCE    
  tcpEStatsConnectIndex Unsigned32

TcpEStatsPerfEntry  
SEQUENCE    
  tcpEStatsPerfSegsOut ZeroBasedCounter32
  tcpEStatsPerfDataSegsOut ZeroBasedCounter32
  tcpEStatsPerfDataOctetsOut ZeroBasedCounter32
  tcpEStatsPerfHCDataOctetsOut ZeroBasedCounter64
  tcpEStatsPerfSegsRetrans ZeroBasedCounter32
  tcpEStatsPerfOctetsRetrans ZeroBasedCounter32
  tcpEStatsPerfSegsIn ZeroBasedCounter32
  tcpEStatsPerfDataSegsIn ZeroBasedCounter32
  tcpEStatsPerfDataOctetsIn ZeroBasedCounter32
  tcpEStatsPerfHCDataOctetsIn ZeroBasedCounter64
  tcpEStatsPerfElapsedSecs ZeroBasedCounter32
  tcpEStatsPerfElapsedMicroSecs ZeroBasedCounter32
  tcpEStatsPerfStartTimeStamp DateAndTime
  tcpEStatsPerfCurMSS Gauge32
  tcpEStatsPerfPipeSize Gauge32
  tcpEStatsPerfMaxPipeSize Gauge32
  tcpEStatsPerfSmoothedRTT Gauge32
  tcpEStatsPerfCurRTO Gauge32
  tcpEStatsPerfCongSignals ZeroBasedCounter32
  tcpEStatsPerfCurCwnd Gauge32
  tcpEStatsPerfCurSsthresh Gauge32
  tcpEStatsPerfTimeouts ZeroBasedCounter32
  tcpEStatsPerfCurRwinSent Gauge32
  tcpEStatsPerfMaxRwinSent Gauge32
  tcpEStatsPerfZeroRwinSent ZeroBasedCounter32
  tcpEStatsPerfCurRwinRcvd Gauge32
  tcpEStatsPerfMaxRwinRcvd Gauge32
  tcpEStatsPerfZeroRwinRcvd ZeroBasedCounter32
  tcpEStatsPerfSndLimTransRwin ZeroBasedCounter32
  tcpEStatsPerfSndLimTransCwnd ZeroBasedCounter32
  tcpEStatsPerfSndLimTransSnd ZeroBasedCounter32
  tcpEStatsPerfSndLimTimeRwin ZeroBasedCounter32
  tcpEStatsPerfSndLimTimeCwnd ZeroBasedCounter32
  tcpEStatsPerfSndLimTimeSnd ZeroBasedCounter32

TcpEStatsPathEntry  
SEQUENCE    
  tcpEStatsPathRetranThresh Gauge32
  tcpEStatsPathNonRecovDAEpisodes ZeroBasedCounter32
  tcpEStatsPathSumOctetsReordered ZeroBasedCounter32
  tcpEStatsPathNonRecovDA ZeroBasedCounter32
  tcpEStatsPathSampleRTT Gauge32
  tcpEStatsPathRTTVar Gauge32
  tcpEStatsPathMaxRTT Gauge32
  tcpEStatsPathMinRTT Gauge32
  tcpEStatsPathSumRTT ZeroBasedCounter32
  tcpEStatsPathHCSumRTT ZeroBasedCounter64
  tcpEStatsPathCountRTT ZeroBasedCounter32
  tcpEStatsPathMaxRTO Gauge32
  tcpEStatsPathMinRTO Gauge32
  tcpEStatsPathIpTtl Unsigned32
  tcpEStatsPathIpTosIn OCTET STRING
  tcpEStatsPathIpTosOut OCTET STRING
  tcpEStatsPathPreCongSumCwnd ZeroBasedCounter32
  tcpEStatsPathPreCongSumRTT ZeroBasedCounter32
  tcpEStatsPathPostCongSumRTT ZeroBasedCounter32
  tcpEStatsPathPostCongCountRTT ZeroBasedCounter32
  tcpEStatsPathECNsignals ZeroBasedCounter32
  tcpEStatsPathDupAckEpisodes ZeroBasedCounter32
  tcpEStatsPathRcvRTT Gauge32
  tcpEStatsPathDupAcksOut ZeroBasedCounter32
  tcpEStatsPathCERcvd ZeroBasedCounter32
  tcpEStatsPathECESent ZeroBasedCounter32

TcpEStatsStackEntry  
SEQUENCE    
  tcpEStatsStackActiveOpen TruthValue
  tcpEStatsStackMSSSent Unsigned32
  tcpEStatsStackMSSRcvd Unsigned32
  tcpEStatsStackWinScaleSent Integer32
  tcpEStatsStackWinScaleRcvd Integer32
  tcpEStatsStackTimeStamps TcpEStatsNegotiated
  tcpEStatsStackECN TcpEStatsNegotiated
  tcpEStatsStackWillSendSACK TcpEStatsNegotiated
  tcpEStatsStackWillUseSACK TcpEStatsNegotiated
  tcpEStatsStackState INTEGER
  tcpEStatsStackNagle TruthValue
  tcpEStatsStackMaxSsCwnd Gauge32
  tcpEStatsStackMaxCaCwnd Gauge32
  tcpEStatsStackMaxSsthresh Gauge32
  tcpEStatsStackMinSsthresh Gauge32
  tcpEStatsStackInRecovery INTEGER
  tcpEStatsStackDupAcksIn ZeroBasedCounter32
  tcpEStatsStackSpuriousFrDetected ZeroBasedCounter32
  tcpEStatsStackSpuriousRtoDetected ZeroBasedCounter32
  tcpEStatsStackSoftErrors ZeroBasedCounter32
  tcpEStatsStackSoftErrorReason INTEGER
  tcpEStatsStackSlowStart ZeroBasedCounter32
  tcpEStatsStackCongAvoid ZeroBasedCounter32
  tcpEStatsStackOtherReductions ZeroBasedCounter32
  tcpEStatsStackCongOverCount ZeroBasedCounter32
  tcpEStatsStackFastRetran ZeroBasedCounter32
  tcpEStatsStackSubsequentTimeouts ZeroBasedCounter32
  tcpEStatsStackCurTimeoutCount Gauge32
  tcpEStatsStackAbruptTimeouts ZeroBasedCounter32
  tcpEStatsStackSACKsRcvd ZeroBasedCounter32
  tcpEStatsStackSACKBlocksRcvd ZeroBasedCounter32
  tcpEStatsStackSendStall ZeroBasedCounter32
  tcpEStatsStackDSACKDups ZeroBasedCounter32
  tcpEStatsStackMaxMSS Gauge32
  tcpEStatsStackMinMSS Gauge32
  tcpEStatsStackSndInitial Unsigned32
  tcpEStatsStackRecInitial Unsigned32
  tcpEStatsStackCurRetxQueue Gauge32
  tcpEStatsStackMaxRetxQueue Gauge32
  tcpEStatsStackCurReasmQueue Gauge32
  tcpEStatsStackMaxReasmQueue Gauge32

TcpEStatsAppEntry  
SEQUENCE    
  tcpEStatsAppSndUna Counter32
  tcpEStatsAppSndNxt Unsigned32
  tcpEStatsAppSndMax Counter32
  tcpEStatsAppThruOctetsAcked ZeroBasedCounter32
  tcpEStatsAppHCThruOctetsAcked ZeroBasedCounter64
  tcpEStatsAppRcvNxt Counter32
  tcpEStatsAppThruOctetsReceived ZeroBasedCounter32
  tcpEStatsAppHCThruOctetsReceived ZeroBasedCounter64
  tcpEStatsAppCurAppWQueue Gauge32
  tcpEStatsAppMaxAppWQueue Gauge32
  tcpEStatsAppCurAppRQueue Gauge32
  tcpEStatsAppMaxAppRQueue Gauge32

TcpEStatsTuneEntry  
SEQUENCE    
  tcpEStatsTuneLimCwnd Unsigned32
  tcpEStatsTuneLimSsthresh Unsigned32
  tcpEStatsTuneLimRwin Unsigned32
  tcpEStatsTuneLimMSS Unsigned32

Defined Values

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.
MODULE-IDENTITY    

tcpEStatsNotifications 1.3.6.1.2.1.156.0
OBJECT IDENTIFIER    

tcpEStatsMIBObjects 1.3.6.1.2.1.156.1
OBJECT IDENTIFIER    

tcpEStatsConformance 1.3.6.1.2.1.156.2
OBJECT IDENTIFIER    

tcpEStats 1.3.6.1.2.1.156.1.1
OBJECT IDENTIFIER    

tcpEStatsControl 1.3.6.1.2.1.156.1.2
OBJECT IDENTIFIER    

tcpEStatsScalar 1.3.6.1.2.1.156.1.3
OBJECT IDENTIFIER    

tcpEStatsListenerTableLastChange 1.3.6.1.2.1.156.1.3.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  TimeStamp  

tcpEStatsControlPath 1.3.6.1.2.1.156.1.2.1
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

tcpEStatsControlStack 1.3.6.1.2.1.156.1.2.2
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

tcpEStatsControlApp 1.3.6.1.2.1.156.1.2.3
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

tcpEStatsControlTune 1.3.6.1.2.1.156.1.2.4
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

tcpEStatsControlNotify 1.3.6.1.2.1.156.1.2.5
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

tcpEStatsConnTableLatency 1.3.6.1.2.1.156.1.2.6
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
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

tcpEStatsListenerTable 1.3.6.1.2.1.156.1.1.1
This table contains information about TCP Listeners, in addition to the information maintained by the tcpListenerTable RFC 4022.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsListenerEntry

tcpEStatsListenerEntry 1.3.6.1.2.1.156.1.1.1.1
Each entry in the table contains information about a specific TCP Listener.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsListenerEntry  

tcpEStatsListenerStartTime 1.3.6.1.2.1.156.1.1.1.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  TimeStamp  

tcpEStatsListenerSynRcvd 1.3.6.1.2.1.156.1.1.1.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsListenerInitial 1.3.6.1.2.1.156.1.1.1.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsListenerEstablished 1.3.6.1.2.1.156.1.1.1.1.4
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).
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsListenerAccepted 1.3.6.1.2.1.156.1.1.1.1.5
The total number of connections for which the Listener has successfully issued an accept, removing the connection from the backlog.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsListenerExceedBacklog 1.3.6.1.2.1.156.1.1.1.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsListenerHCSynRcvd 1.3.6.1.2.1.156.1.1.1.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsListenerHCInitial 1.3.6.1.2.1.156.1.1.1.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsListenerHCEstablished 1.3.6.1.2.1.156.1.1.1.1.9
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsListenerHCAccepted 1.3.6.1.2.1.156.1.1.1.1.10
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsListenerHCExceedBacklog 1.3.6.1.2.1.156.1.1.1.1.11
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsListenerCurConns 1.3.6.1.2.1.156.1.1.1.1.12
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsListenerMaxBacklog 1.3.6.1.2.1.156.1.1.1.1.13
The maximum number of connections allowed in the backlog at one time.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsListenerCurBacklog 1.3.6.1.2.1.156.1.1.1.1.14
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsListenerCurEstabBacklog 1.3.6.1.2.1.156.1.1.1.1.15
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsConnectIdTable 1.3.6.1.2.1.156.1.1.2
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsConnectIdEntry

tcpEStatsConnectIdEntry 1.3.6.1.2.1.156.1.1.2.1
Each entry in this table maps a TCP connection 4-tuple to a connection index.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsConnectIdEntry  

tcpEStatsConnectIndex 1.3.6.1.2.1.156.1.1.2.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 1..4294967295  

tcpEStatsPerfTable 1.3.6.1.2.1.156.1.1.3
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsPerfEntry

tcpEStatsPerfEntry 1.3.6.1.2.1.156.1.1.3.1
Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsPerfEntry  

tcpEStatsPerfSegsOut 1.3.6.1.2.1.156.1.1.3.1.1
The total number of segments sent.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfDataSegsOut 1.3.6.1.2.1.156.1.1.3.1.2
The number of segments sent containing a positive length data segment.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfDataOctetsOut 1.3.6.1.2.1.156.1.1.3.1.3
The number of octets of data contained in transmitted segments, including retransmitted data. Note that this does not include TCP headers.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfHCDataOctetsOut 1.3.6.1.2.1.156.1.1.3.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsPerfSegsRetrans 1.3.6.1.2.1.156.1.1.3.1.5
The number of segments transmitted containing at least some retransmitted data.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfOctetsRetrans 1.3.6.1.2.1.156.1.1.3.1.6
The number of octets retransmitted.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSegsIn 1.3.6.1.2.1.156.1.1.3.1.7
The total number of segments received.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfDataSegsIn 1.3.6.1.2.1.156.1.1.3.1.8
The number of segments received containing a positive length data segment.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfDataOctetsIn 1.3.6.1.2.1.156.1.1.3.1.9
The number of octets contained in received data segments, including retransmitted data. Note that this does not include TCP headers.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfHCDataOctetsIn 1.3.6.1.2.1.156.1.1.3.1.10
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsPerfElapsedSecs 1.3.6.1.2.1.156.1.1.3.1.11
The seconds part of the time elapsed between tcpEStatsPerfStartTimeStamp and the most recent protocol event (segment sent or received).
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfElapsedMicroSecs 1.3.6.1.2.1.156.1.1.3.1.12
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfStartTimeStamp 1.3.6.1.2.1.156.1.1.3.1.13
Time at which this row was created and all ZeroBasedCounters in the row were initialized to zero.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

tcpEStatsPerfCurMSS 1.3.6.1.2.1.156.1.1.3.1.14
The current maximum segment size (MSS), in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfPipeSize 1.3.6.1.2.1.156.1.1.3.1.15
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
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfMaxPipeSize 1.3.6.1.2.1.156.1.1.3.1.16
The maximum value of tcpEStatsPerfPipeSize, for this connection.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfSmoothedRTT 1.3.6.1.2.1.156.1.1.3.1.17
The smoothed round trip time used in calculation of the RTO. See SRTT in [RFC2988].
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfCurRTO 1.3.6.1.2.1.156.1.1.3.1.18
The current value of the retransmit timer RTO.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfCongSignals 1.3.6.1.2.1.156.1.1.3.1.19
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfCurCwnd 1.3.6.1.2.1.156.1.1.3.1.20
The current congestion window, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfCurSsthresh 1.3.6.1.2.1.156.1.1.3.1.21
The current slow start threshold in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfTimeouts 1.3.6.1.2.1.156.1.1.3.1.22
The number of times the retransmit timeout has expired when the RTO backoff multiplier is equal to one.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfCurRwinSent 1.3.6.1.2.1.156.1.1.3.1.23
The most recent window advertisement sent, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfMaxRwinSent 1.3.6.1.2.1.156.1.1.3.1.24
The maximum window advertisement sent, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfZeroRwinSent 1.3.6.1.2.1.156.1.1.3.1.25
The number of acknowledgments sent announcing a zero receive window, when the previously announced window was not zero.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfCurRwinRcvd 1.3.6.1.2.1.156.1.1.3.1.26
The most recent window advertisement received, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfMaxRwinRcvd 1.3.6.1.2.1.156.1.1.3.1.27
The maximum window advertisement received, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPerfZeroRwinRcvd 1.3.6.1.2.1.156.1.1.3.1.28
The number of acknowledgments received announcing a zero receive window, when the previously announced window was not zero.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTransRwin 1.3.6.1.2.1.156.1.1.3.1.31
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTransCwnd 1.3.6.1.2.1.156.1.1.3.1.32
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTransSnd 1.3.6.1.2.1.156.1.1.3.1.33
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTimeRwin 1.3.6.1.2.1.156.1.1.3.1.34
The cumulative time spent in the 'Receiver Limited' state. See tcpEStatsPerfSndLimTransRwin.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTimeCwnd 1.3.6.1.2.1.156.1.1.3.1.35
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.)
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPerfSndLimTimeSnd 1.3.6.1.2.1.156.1.1.3.1.36
The cumulative time spent in the 'Sender Limited' state. See tcpEStatsPerfSndLimTransSnd.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathTable 1.3.6.1.2.1.156.1.1.4
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsPathEntry

tcpEStatsPathEntry 1.3.6.1.2.1.156.1.1.4.1
Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsPathEntry  

tcpEStatsPathRetranThresh 1.3.6.1.2.1.156.1.1.4.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathNonRecovDAEpisodes 1.3.6.1.2.1.156.1.1.4.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathSumOctetsReordered 1.3.6.1.2.1.156.1.1.4.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathNonRecovDA 1.3.6.1.2.1.156.1.1.4.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathSampleRTT 1.3.6.1.2.1.156.1.1.4.1.11
The most recent raw round trip time measurement used in calculation of the RTO.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathRTTVar 1.3.6.1.2.1.156.1.1.4.1.12
The round trip time variation used in calculation of the RTO. See RTTVAR in [RFC2988].
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathMaxRTT 1.3.6.1.2.1.156.1.1.4.1.13
The maximum sampled round trip time.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathMinRTT 1.3.6.1.2.1.156.1.1.4.1.14
The minimum sampled round trip time.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathSumRTT 1.3.6.1.2.1.156.1.1.4.1.15
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathHCSumRTT 1.3.6.1.2.1.156.1.1.4.1.16
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsPathCountRTT 1.3.6.1.2.1.156.1.1.4.1.17
The number of round trip time samples included in tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathMaxRTO 1.3.6.1.2.1.156.1.1.4.1.18
The maximum value of the retransmit timer RTO.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathMinRTO 1.3.6.1.2.1.156.1.1.4.1.19
The minimum value of the retransmit timer RTO.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathIpTtl 1.3.6.1.2.1.156.1.1.4.1.20
The value of the TTL field carried in the most recently received IP header. This is sometimes useful to detect changing or unstable routes.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsPathIpTosIn 1.3.6.1.2.1.156.1.1.4.1.21
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.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1)  

tcpEStatsPathIpTosOut 1.3.6.1.2.1.156.1.1.4.1.22
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.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1)  

tcpEStatsPathPreCongSumCwnd 1.3.6.1.2.1.156.1.1.4.1.23
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathPreCongSumRTT 1.3.6.1.2.1.156.1.1.4.1.24
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathPostCongSumRTT 1.3.6.1.2.1.156.1.1.4.1.25
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathPostCongCountRTT 1.3.6.1.2.1.156.1.1.4.1.26
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathECNsignals 1.3.6.1.2.1.156.1.1.4.1.27
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathDupAckEpisodes 1.3.6.1.2.1.156.1.1.4.1.28
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathRcvRTT 1.3.6.1.2.1.156.1.1.4.1.29
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsPathDupAcksOut 1.3.6.1.2.1.156.1.1.4.1.30
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathCERcvd 1.3.6.1.2.1.156.1.1.4.1.31
The number of segments received with IP headers bearing Congestion Experienced (CE) markings.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsPathECESent 1.3.6.1.2.1.156.1.1.4.1.32
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackTable 1.3.6.1.2.1.156.1.1.5
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsStackEntry

tcpEStatsStackEntry 1.3.6.1.2.1.156.1.1.5.1
Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsStackEntry  

tcpEStatsStackActiveOpen 1.3.6.1.2.1.156.1.1.5.1.1
True(1) if the local connection traversed the SYN-SENT state, else false(2).
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

tcpEStatsStackMSSSent 1.3.6.1.2.1.156.1.1.5.1.2
The value sent in an MSS option, or zero if none.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsStackMSSRcvd 1.3.6.1.2.1.156.1.1.5.1.3
The value received in an MSS option, or zero if none.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsStackWinScaleSent 1.3.6.1.2.1.156.1.1.5.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -1..14  

tcpEStatsStackWinScaleRcvd 1.3.6.1.2.1.156.1.1.5.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -1..14  

tcpEStatsStackTimeStamps 1.3.6.1.2.1.156.1.1.5.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  TcpEStatsNegotiated  

tcpEStatsStackECN 1.3.6.1.2.1.156.1.1.5.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  TcpEStatsNegotiated  

tcpEStatsStackWillSendSACK 1.3.6.1.2.1.156.1.1.5.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  TcpEStatsNegotiated  

tcpEStatsStackWillUseSACK 1.3.6.1.2.1.156.1.1.5.1.9
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.
Status: current Access: read-only
OBJECT-TYPE    
  TcpEStatsNegotiated  

tcpEStatsStackState 1.3.6.1.2.1.156.1.1.5.1.10
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER tcpESStateClosed(1), tcpESStateListen(2), tcpESStateSynSent(3), tcpESStateSynReceived(4), tcpESStateEstablished(5), tcpESStateFinWait1(6), tcpESStateFinWait2(7), tcpESStateCloseWait(8), tcpESStateLastAck(9), tcpESStateClosing(10), tcpESStateTimeWait(11), tcpESStateDeleteTcb(12)  

tcpEStatsStackNagle 1.3.6.1.2.1.156.1.1.5.1.11
True(1) if the Nagle algorithm is being used, else false(2).
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

tcpEStatsStackMaxSsCwnd 1.3.6.1.2.1.156.1.1.5.1.12
The maximum congestion window used during Slow Start, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMaxCaCwnd 1.3.6.1.2.1.156.1.1.5.1.13
The maximum congestion window used during Congestion Avoidance, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMaxSsthresh 1.3.6.1.2.1.156.1.1.5.1.14
The maximum slow start threshold, excluding the initial value.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMinSsthresh 1.3.6.1.2.1.156.1.1.5.1.15
The minimum slow start threshold.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackInRecovery 1.3.6.1.2.1.156.1.1.5.1.16
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER tcpESDataContiguous(1), tcpESDataUnordered(2), tcpESDataRecovery(3)  

tcpEStatsStackDupAcksIn 1.3.6.1.2.1.156.1.1.5.1.17
The number of duplicate ACKs received.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSpuriousFrDetected 1.3.6.1.2.1.156.1.1.5.1.18
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).'
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSpuriousRtoDetected 1.3.6.1.2.1.156.1.1.5.1.19
The number of acknowledgments reporting segments that have already been retransmitted due to a Retransmission Timeout.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSoftErrors 1.3.6.1.2.1.156.1.1.5.1.21
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSoftErrorReason 1.3.6.1.2.1.156.1.1.5.1.22
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER belowDataWindow(1), aboveDataWindow(2), belowAckWindow(3), aboveAckWindow(4), belowTSWindow(5), aboveTSWindow(6), dataCheckSum(7), otherSoftError(8)  

tcpEStatsStackSlowStart 1.3.6.1.2.1.156.1.1.5.1.23
The number of times the congestion window has been increased by the Slow Start algorithm.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackCongAvoid 1.3.6.1.2.1.156.1.1.5.1.24
The number of times the congestion window has been increased by the Congestion Avoidance algorithm.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackOtherReductions 1.3.6.1.2.1.156.1.1.5.1.25
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackCongOverCount 1.3.6.1.2.1.156.1.1.5.1.26
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackFastRetran 1.3.6.1.2.1.156.1.1.5.1.27
The number of invocations of the Fast Retransmit algorithm.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSubsequentTimeouts 1.3.6.1.2.1.156.1.1.5.1.28
The number of times the retransmit timeout has expired after the RTO has been doubled. See Section 5.5 of RFC 2988.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackCurTimeoutCount 1.3.6.1.2.1.156.1.1.5.1.29
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackAbruptTimeouts 1.3.6.1.2.1.156.1.1.5.1.30
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSACKsRcvd 1.3.6.1.2.1.156.1.1.5.1.31
The number of SACK options received.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSACKBlocksRcvd 1.3.6.1.2.1.156.1.1.5.1.32
The number of SACK blocks received (within SACK options).
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackSendStall 1.3.6.1.2.1.156.1.1.5.1.33
The number of interface stalls or other sender local resource limitations that are treated as congestion signals.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackDSACKDups 1.3.6.1.2.1.156.1.1.5.1.34
The number of duplicate segments reported to the local host by D-SACK blocks.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsStackMaxMSS 1.3.6.1.2.1.156.1.1.5.1.35
The maximum MSS, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMinMSS 1.3.6.1.2.1.156.1.1.5.1.36
The minimum MSS, in octets.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackSndInitial 1.3.6.1.2.1.156.1.1.5.1.37
Initial send sequence number. Note that by definition tcpEStatsStackSndInitial never changes for a given connection.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsStackRecInitial 1.3.6.1.2.1.156.1.1.5.1.38
Initial receive sequence number. Note that by definition tcpEStatsStackRecInitial never changes for a given connection.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsStackCurRetxQueue 1.3.6.1.2.1.156.1.1.5.1.39
The current number of octets of data occupying the retransmit queue.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMaxRetxQueue 1.3.6.1.2.1.156.1.1.5.1.40
The maximum number of octets of data occupying the retransmit queue.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackCurReasmQueue 1.3.6.1.2.1.156.1.1.5.1.41
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsStackMaxReasmQueue 1.3.6.1.2.1.156.1.1.5.1.42
The maximum value of tcpEStatsStackCurReasmQueue
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsAppTable 1.3.6.1.2.1.156.1.1.6
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsAppEntry

tcpEStatsAppEntry 1.3.6.1.2.1.156.1.1.6.1
Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsAppEntry  

tcpEStatsAppSndUna 1.3.6.1.2.1.156.1.1.6.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

tcpEStatsAppSndNxt 1.3.6.1.2.1.156.1.1.6.1.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tcpEStatsAppSndMax 1.3.6.1.2.1.156.1.1.6.1.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

tcpEStatsAppThruOctetsAcked 1.3.6.1.2.1.156.1.1.6.1.4
The number of octets for which cumulative acknowledgments have been received. Note that this will be the sum of changes to tcpEStatsAppSndUna.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsAppHCThruOctetsAcked 1.3.6.1.2.1.156.1.1.6.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsAppRcvNxt 1.3.6.1.2.1.156.1.1.6.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

tcpEStatsAppThruOctetsReceived 1.3.6.1.2.1.156.1.1.6.1.7
The number of octets for which cumulative acknowledgments have been sent. Note that this will be the sum of changes to tcpEStatsAppRcvNxt.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter32  

tcpEStatsAppHCThruOctetsReceived 1.3.6.1.2.1.156.1.1.6.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  ZeroBasedCounter64  

tcpEStatsAppCurAppWQueue 1.3.6.1.2.1.156.1.1.6.1.11
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsAppMaxAppWQueue 1.3.6.1.2.1.156.1.1.6.1.12
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).
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsAppCurAppRQueue 1.3.6.1.2.1.156.1.1.6.1.13
The current number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsAppMaxAppRQueue 1.3.6.1.2.1.156.1.1.6.1.14
The maximum number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

tcpEStatsTuneTable 1.3.6.1.2.1.156.1.1.7
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TcpEStatsTuneEntry

tcpEStatsTuneEntry 1.3.6.1.2.1.156.1.1.7.1
Each entry in this table is a control that can be used to place limits on each active TCP connection.
Status: current Access: not-accessible
OBJECT-TYPE    
  TcpEStatsTuneEntry  

tcpEStatsTuneLimCwnd 1.3.6.1.2.1.156.1.1.7.1.1
A control to set the maximum congestion window that may be used, in octets.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

tcpEStatsTuneLimSsthresh 1.3.6.1.2.1.156.1.1.7.1.2
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.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

tcpEStatsTuneLimRwin 1.3.6.1.2.1.156.1.1.7.1.3
A control to set the maximum window advertisement that may be sent, in octets.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

tcpEStatsTuneLimMSS 1.3.6.1.2.1.156.1.1.7.1.4
A control to limit the maximum segment size in octets, that this TCP connection can use.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

tcpEStatsEstablishNotification 1.3.6.1.2.1.156.0.1
The indicated connection has been accepted (or alternatively entered the established state).
Status: current Access: read-write
NOTIFICATION-TYPE    

tcpEStatsCloseNotification 1.3.6.1.2.1.156.0.2
The indicated connection has left the established state
Status: current Access: read-write
NOTIFICATION-TYPE    

tcpEStatsCompliances 1.3.6.1.2.1.156.2.1
OBJECT IDENTIFIER    

tcpEStatsGroups 1.3.6.1.2.1.156.2.2
OBJECT IDENTIFIER    

tcpEStatsCompliance 1.3.6.1.2.1.156.2.1.1
Compliance statement for all systems that implement TCP extended statistics.
Status: current Access: read-write
MODULE-COMPLIANCE    

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.
Status: current Access: read-write
OBJECT-GROUP    

tcpEStatsListenerHCGroup 1.3.6.1.2.1.156.2.2.2
The tcpEStatsListenerHC group includes 64-bit counters in tcpEStatsListenerTable.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

tcpEStatsPerfHCGroup 1.3.6.1.2.1.156.2.2.6
The tcpEStatsPerfHC group includes 64-bit counters in the tcpEStatsPerfTable.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

tcpEStatsPathHCGroup 1.3.6.1.2.1.156.2.2.9
The tcpEStatsPathHC group includes 64-bit counters in the tcpEStatsPathTable.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

tcpEStatsAppHCGroup 1.3.6.1.2.1.156.2.2.13
The tcpEStatsStackHC group includes 64-bit counters in the tcpEStatsStackTable.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP    

tcpEStatsNotificationsGroup 1.3.6.1.2.1.156.2.2.16
Notifications sent by a TCP extended statistics agent.
Status: current Access: read-write
NOTIFICATION-GROUP    

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.
Status: current Access: read-write
OBJECT-GROUP