Network Working Group M. Mathis
Request for Comments: 4898 J. Heffner
Category: Standards Track Pittsburgh Supercomputing Center
R. Raghunarayan
Cisco Systems
May 2007
Network Working Group M. Mathis
Request for Comments: 4898 J. Heffner
Category: Standards Track Pittsburgh Supercomputing Center
R. Raghunarayan
Cisco Systems
May 2007
TCP Extended Statistics MIB
TCP扩展统计信息库
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document describes extended performance statistics for TCP. They are designed to use TCP's ideal vantage point to diagnose performance problems in both the network and the application. If a network-based application is performing poorly, TCP can determine if the bottleneck is in the sender, the receiver, or the network itself. If the bottleneck is in the network, TCP can provide specific information about its nature.
本文档介绍TCP的扩展性能统计信息。它们旨在利用TCP的理想优势诊断网络和应用程序中的性能问题。如果基于网络的应用程序性能不佳，TCP可以确定瓶颈是在发送方、接收方还是网络本身。如果瓶颈在网络中，TCP可以提供有关其性质的特定信息。
Table of Contents
目录
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Overview ........................................................2
3.1. MIB Initialization and Persistence .........................4
3.2. Relationship to TCP Standards ..............................4
3.3. Diagnosing SYN-Flood Denial-of-Service Attacks .............6
4. TCP Extended Statistics MIB .....................................7
5. Security Considerations ........................................69
6. IANA Considerations ............................................70
7. Normative References ...........................................70
8. Informative References .........................................72
9. Contributors ...................................................73
10. Acknowledgments ...............................................73
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Overview ........................................................2
3.1. MIB Initialization and Persistence .........................4
3.2. Relationship to TCP Standards ..............................4
3.3. Diagnosing SYN-Flood Denial-of-Service Attacks .............6
4. TCP Extended Statistics MIB .....................................7
5. Security Considerations ........................................69
6. IANA Considerations ............................................70
7. Normative References ...........................................70
8. Informative References .........................................72
9. Contributors ...................................................73
10. Acknowledgments ...............................................73
This document describes extended performance statistics for TCP. They are designed to use TCP's ideal vantage point to diagnose performance problems in both the network and the application. If a network-based application is performing poorly, TCP can determine if the bottleneck is in the sender, the receiver, or the network itself. If the bottleneck is in the network, TCP can provide specific information about its nature.
本文档介绍TCP的扩展性能统计信息。它们旨在利用TCP的理想优势诊断网络和应用程序中的性能问题。如果基于网络的应用程序性能不佳，TCP可以确定瓶颈是在发送方、接收方还是网络本身。如果瓶颈在网络中，TCP可以提供有关其性质的特定信息。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119中的说明进行解释。
The Simple Network Management Protocol (SNMP) objects defined in this document extend TCP MIB, as specified in RFC 4022 [RFC4022]. In addition to several new scalars and other objects, it augments two tables and makes one clarification to RFC 4022. Existing management stations for the TCP MIB are expected to be fully compatible with these clarifications.
本文档中定义的简单网络管理协议（SNMP）对象扩展了TCP MIB，如RFC 4022[RFC4022]中所述。除了几个新的标量和其他对象之外，它还增加了两个表，并对RFC4022做了一个澄清。TCP MIB的现有管理站预计与这些澄清完全兼容。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The TCP-ESTATS-MIB defined in this memo consists of two groups of scalars, seven tables, and two notifications:
本备忘录中定义的TCP-ESTATS-MIB由两组标量、七个表和两个通知组成：
* The first group of scalars contain statistics of the TCP protocol engine not covered in RFC 4022. This group consists of the single scalar tcpEStatsListenerTableLastChange, which provides management stations with an easier mechanism to validate their listener caches.
* 第一组标量包含RFC4022中未涉及的TCP协议引擎的统计信息。该组由单个标量tcpEStatsListenerTableLastChange组成，它为管理站提供了一种更简单的机制来验证其侦听器缓存。
* The second group of scalars consist of knobs to enable and disable information collection by the tables containing connection-related statistics/information. For example, the tcpEStatsControlPath object controls the activation of the tcpEStatsPathTable. The tcpEStatsConnTableLatency object determines how long connection table rows are retained after a TCP connection transitions into the closed state.
* 第二组标量由旋钮组成，用于启用和禁用包含连接相关统计信息/信息的表的信息收集。例如，tcpEStatsControlPath对象控制tcpEStatsPathTable的激活。TCPESTATSConTableLatency对象确定TCP连接转换为关闭状态后连接表行保留的时间。
* The tcpEStatsListenerTable augments tcpListenerTable in TCP-MIB [RFC4022] to provide additional information on the active TCP listeners on a device. It supports objects to monitor and diagnose SYN-flood denial-of-service attacks as described below.
* tcpEStatsListenerTable扩展了TCP-MIB[RFC4022]中的tcpListenerTable，以提供有关设备上活动TCP侦听器的附加信息。它支持监视和诊断SYN flood拒绝服务攻击的对象，如下所述。
* The tcpEStatsConnectIdTable augments the tcpConnectionTable in TCP-MIB [RFC4022] to provide a mapping between connection 4-tuples (which index tcpConnectionTable) and an integer connection index, tcpEStatsConnectIndex. The connection index is used to index into the five remaining tables in this MIB module, and is designed to facilitate rapid polling of multiple objects associated with one TCP connection.
* TCPESTATSConnectedTable扩展TCP-MIB[RFC4022]中的tcpConnectionTable，以提供连接4元组（索引tcpConnectionTable）和整数连接索引tcpEStatsConnectIndex之间的映射。连接索引用于索引此MIB模块中剩余的五个表，并设计为便于快速轮询与一个TCP连接关联的多个对象。
* The tcpEStatsPerfTable contains objects that are useful for measuring TCP performance and first check problem diagnosis.
* tcpEStatsPerfTable包含用于测量TCP性能和首次检查问题诊断的对象。
* The tcpEStatsPathTable contains objects that can be used to infer detailed behavior of the Internet path, such as the extent that there are segment losses or reordering, etc.
* tcpEStatsPathTable包含可用于推断Internet路径的详细行为的对象，例如段丢失或重新排序的程度等。
* The tcpEStatsStackTable contains objects that are most useful for determining how well the TCP control algorithms are coping with this particular path.
* tcpEStatsStackTable包含的对象对于确定TCP控制算法处理此特定路径的效果最为有用。
* The tcpEStatsAppTable provides objects that are useful for determining if the application using TCP is limiting TCP performance.
* tcpEStatsAppTable提供的对象可用于确定使用TCP的应用程序是否限制TCP性能。
* The tcpEStatsTuneTable provides per-connection controls that can be used to work around a number of common problems that plague TCP over some paths.
* TcpestatStuteTable提供了每个连接的控件，可用于解决在某些路径上困扰TCP的许多常见问题。
* The two notifications defined in this MIB module are tcpEStatsEstablishNotification, indicating that a new connection has been accepted (or established, see below), and tcpEStatsCloseNotification, indicating that an existing connection has recently closed.
* 此MIB模块中定义的两个通知是TcpestatsStablishNotification，表示新连接已被接受（或已建立，请参见下文），以及tcpEStatsCloseNotification，表示现有连接最近已关闭。
The TCP protocol itself is specifically designed not to preserve any state whatsoever across system reboots, and enforces this by requiring randomized Initial Sequence numbers and ephemeral ports under any conditions where segments from old connections might corrupt new connections following a reboot.
TCP协议本身专门设计为在系统重新启动时不保留任何状态，并通过在重新启动后旧连接的段可能损坏新连接的任何情况下要求随机初始序列号和临时端口来强制执行。
All of the objects in the 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.
MIB中的所有对象必须具有与底层TCP实现相同的持久性属性。重新启动时，必须清除所有基于零的计数器，删除所有动态创建的表行，并将所有读写对象恢复为其默认值。假设所有TCP实现都有一些初始化代码（如果没有其他代码，则设置IP地址），在建立第一个TCP连接之前，这些代码有机会调整TCPESTATSConTableLatency和其他控制各种表创建的读写标量。实现还可以选择使这些控制标量在重新启动期间保持不变。
The ZeroBasedCounter32 and ZeroBasedCounter64 objects in the listener and connection tables are initialized to zero when the table row is created.
创建表行时，侦听器表和连接表中的ZeroBasedCounter32和ZeroBasedCounter64对象初始化为零。
The tcpEStatsConnTableLatency object determines how long connection table rows are retained after a TCP connection transitions into the closed state, to permit reading final connection completion statistics. In RFC 4022 (TCP-MIB), the discussion of tcpConnectionTable row latency (page 9) the words "soon after" are understood to mean after tcpEStatsConnTableLatency, such that all rows of all tables associated with one connection are retained at least tcpEStatsConnTableLatency after connection close. This clarification to RFC 4022 only applies when TCP-ESTATS-MIB is implemented. If TCP-ESTATS-MIB is not implemented, RFC 4022 permits an unspecified delay between connection close and row deletion.
TCPESTATSConTableLatency对象确定TCP连接转换为关闭状态后连接表行保留的时间，以允许读取最终连接完成统计信息。在RFC 4022（TCP-MIB）中，对tcpConnectionTable行延迟的讨论（第9页）中的“不久之后”一词被理解为在TCPESTATSConTableLatency之后，因此与一个连接相关联的所有表的所有行在连接关闭后至少保留TCPESTATSConTableLatency。RFC 4022的澄清仅适用于实施TCP-ESTATS-MIB的情况。如果未实现TCP-ESTATS-MIB，RFC 4022允许在连接关闭和行删除之间存在未指定的延迟。
There are more than 70 RFCs and other documents that specify various aspects of the Transmission Control Protocol (TCP) [RFC4614]. While most protocols are completely specified in one or two documents, this has not proven to be feasible for TCP. TCP implements a reliable end-to-end data transport service over a very weakly constrained IP datagram service. The essential problem that TCP has to solve is balancing the applications need for fast and reliable data transport against the need to make fair, efficient, and equitable use of network resources, with only sparse information about the state of the network or its capabilities.
有70多个RFC和其他文件规定了传输控制协议（TCP）[RFC4614]的各个方面。虽然大多数协议都是在一两个文档中完全指定的，但这对于TCP来说并不可行。TCP通过非常弱约束的IP数据报服务实现可靠的端到端数据传输服务。TCP必须解决的基本问题是平衡应用程序对快速可靠数据传输的需求与公平、高效和公平地使用网络资源的需求，而网络状态或其能力的信息很少。
TCP maintains this balance through the use of many estimators and heuristics that regulate various aspects of the protocol. For example, RFC 2988 describes how to calculate the retransmission timer (RTO) from the average and variance of the network round-trip-time (RTT), as estimated from the round-trip time sampled on some data segments. Although these algorithms are standardized, they are a compromise which is optimal for only common Internet environments. Other estimators might yield better results (higher performance or more efficient use of the network) in some environments, particularly under uncommon conditions.
TCP通过使用许多调节协议各个方面的估计器和启发式来保持这种平衡。例如，RFC 2988描述了如何根据网络往返时间（RTT）的平均值和方差来计算重传定时器（RTO），如根据在一些数据段上采样的往返时间来估计的。虽然这些算法是标准化的，但它们是一种折衷方案，仅适用于常见的Internet环境。在某些环境中，特别是在不常见的情况下，其他估计器可能会产生更好的结果（更高的性能或更有效地使用网络）。
It is the consensus of the community that nearly all of the estimators and heuristics used in TCP might be improved through further research and development. For this reason, nearly all TCP documents leave some latitude for future improvements, for example, by the use of "SHOULD" instead of "MUST" [RFC2119]. Even standard algorithms that are required because they critically effect fairness or the dynamic stability of Internet congestion control, include some latitude for evolution. As a consequence, there is considerable diversity in the details of the TCP implementations actually in use today.
社区一致认为，TCP中使用的几乎所有估计器和启发式算法都可以通过进一步的研究和开发加以改进。因此，几乎所有TCP文档都为将来的改进留有一定的余地，例如，使用“应该”而不是“必须”[RFC2119]。即使是因为严重影响公平性或互联网拥塞控制的动态稳定性而需要的标准算法，也有一定的进化余地。因此，目前实际使用的TCP实现的细节有很大的差异。
The fact that the underlying algorithms are not uniform makes it difficult to tightly specify a MIB. We could have chosen the point of view that the MIB should publish precisely defined metrics of the network path, even if they are different from the estimators in use by TCP. This would make the MIB more useful as a measurement tool, but less useful for understanding how any specific TCP implementation is interacting with the network path and upper protocol layers. We chose instead to have the MIB expose the estimators and important states variables of the algorithms in use, without constraining the TCP implementation.
底层算法不统一的事实使严格指定MIB变得困难。我们可以选择这样的观点，即MIB应该发布精确定义的网络路径度量，即使它们与TCP使用的估计器不同。这将使MIB作为一种测量工具更加有用，但对于理解任何特定TCP实现如何与网络路径和上层协议层交互则不太有用。我们取而代之的是让MIB公开所用算法的估计器和重要状态变量，而不限制TCP实现。
As a consequence, the MIB objects are defined in terms of fairly abstract descriptions (e.g., round-trip time), but are intended to expose the actual estimators or other state variables as they are used in TCP implementations, possibly transformed (e.g., scaled or otherwise adjusted) to match the spirit of the object descriptions in this document.
因此，MIB对象是根据相当抽象的描述（例如往返时间）定义的，但旨在公开TCP实现中使用的实际估计器或其他状态变量，可能会进行转换（例如缩放或其他调整），以符合本文档中对象描述的精神。
This may mean that MIB objects may not be exactly comparable between two different TCP implementations. A general management station can only assume the abstract descriptions, which are useful for a general assessment of how TCP is functioning. To a TCP implementer with detailed knowledge about the TCP implementation on a specific host, this MIB might be useful for debugging or evaluating the algorithms in their implementation.
这可能意味着MIB对象在两个不同的TCP实现之间可能不完全可比。一般管理站只能采用抽象描述，这些描述对于TCP如何运行的一般评估非常有用。对于详细了解特定主机上的TCP实现的TCP实现人员来说，此MIB可能有助于调试或评估实现中的算法。
Under no conditions is this MIB intended to constrain TCP to use (or exclude) any particular estimator, heuristic, algorithm, or implementation.
在任何情况下，此MIB都不打算约束TCP使用（或排除）任何特定的估计器、启发式、算法或实现。
The tcpEStatsListenerTable is specifically designed to provide information that is useful for diagnosing SYN-flood Denial-of-Service attacks, where a server is overwhelmed by forged or otherwise malicious connection attempts. There are several different techniques that can be used to defend against SYN-flooding but none are standardized [Edd06]. These different techniques all have the same basic characteristics that are instrumentable with a common set of objects, even though the techniques differ greatly in the details.
tcpEStatsListenerTable专门设计用于提供有助于诊断SYN flood拒绝服务攻击的信息，当服务器被伪造或其他恶意连接尝试所淹没时。有几种不同的技术可用于防御SYN洪泛，但没有一种是标准化的[Edd06]。这些不同的技术都具有相同的基本特征，可以使用一组公共对象进行检测，尽管这些技术在细节上有很大差异。
All SYN-flood defenses avoid allocating significant resources (memory or CPU) to incoming (passive open) connections until the connections meet some liveness criteria (to defend against forged IP source addresses) and the server has sufficient resources to process the incoming request. Note that allocating resources is an implementation-specific event that may not correspond to an observable protocol event (e.g., segments on the wire). There are two general concepts that can be applied to all known SYN-flood defenses. There is generally a well-defined event when a connection is allocated full resources, and a "backlog" -- a queue of embryonic connections that have been allocated only partial resources.
所有SYN洪水防御都避免将大量资源（内存或CPU）分配给传入（被动打开）连接，直到连接满足某些活动性标准（以防御伪造的IP源地址），并且服务器有足够的资源来处理传入请求。注意，分配资源是一个特定于实现的事件，可能与可观察的协议事件（例如，线路上的段）不对应。有两个通用概念可应用于所有已知的SYN洪水防御。当一个连接被分配了全部资源时，通常会有一个定义良好的事件，还有一个“backlog”——只分配了部分资源的胚胎连接队列。
In many implementations, incoming TCP connections are allocated resources as a side effect of the POSIX [POSIX] accept() call. For this reason we use the terminology "accepting a connection" to refer to this event: committing sufficient network resources to process the incoming request. Accepting a connection typically entails allocating memory for the protocol control block [RFC793], the per-connection table rows described in this MIB and CPU resources, such as process table entries or threads.
在许多实现中，传入的TCP连接作为POSIX[POSIX]accept（）调用的副作用被分配资源。因此，我们使用术语“接受连接”来指代此事件：提交足够的网络资源以处理传入请求。接受连接通常需要为协议控制块[RFC793]分配内存、此MIB中描述的每个连接表行以及CPU资源，例如进程表条目或线程。
Note that it is not useful to accept connections before they are ESTABLISHED, because this would create an easy opportunity for Denial-of-Service attacks, using forged source IP addresses.
请注意，在建立连接之前接受连接是没有用的，因为这会很容易造成拒绝服务攻击，使用伪造的源IP地址。
The backlog consists of connections that are in SYN-RCVD or ESTABLISHED states, that have not been accepted. For purposes of this MIB, we assume that these connections have been allocated some resources (e.g., an embryonic protocol control block), but not full resources (e.g., do not yet have MIB table rows).
积压由处于SYN-RCVD或已建立状态的连接组成，这些连接尚未被接受。出于此MIB的目的，我们假设这些连接已经分配了一些资源（例如，一个胚胎协议控制块），但没有分配全部资源（例如，还没有MIB表行）。
Note that some SYN-Flood defenses dispense with explicit SYN-RCVD state by cryptographically encoding the state in the ISS (initial sequence number sent) of the SYN-ACK (sometimes called a syn-cookie), and then using the sequence number of the first ACK to reconstruct the SYN-RCVD state before transitioning to the ESTABLISHED state. For these implementations there is no explicit representation of the SYN-RCVD state, and the backlog only consists of connections that are ESTABLISHED and are waiting to be ACCEPTED.
注意，一些SYN洪水防御通过对SYN-ACK（有时称为SYN cookie）的ISS（发送的初始序列号）中的状态进行加密编码，然后使用第一个ACK的序列号在转换到已建立状态之前重建SYN-RCVD状态，从而免除了显式SYN-RCVD状态。对于这些实现，SYN-RCVD状态没有明确的表示，积压工作只包括已建立并等待接受的连接。
Furthermore, most SYN-flood defenses have some mechanism to throttle connections that might otherwise overwhelm this endpoint. They generally use some combination of discarding incoming SYNs and discarding connections already in the backlog. This does not cause all connections from legitimate clients to fail, as long as the clients retransmit the SYN or first ACK as specified in RFC 793. Most diversity in SYN flood defenses arise from variations in these algorithms to limit load, and therefore cannot be instrumented with a common standard MIB.
此外，大多数SYN洪水防御都有一些机制来限制连接，否则这些连接可能会压倒该端点。它们通常使用丢弃传入SYN和丢弃积压工作中已有的连接的组合。这不会导致来自合法客户端的所有连接失败，只要客户端按照RFC 793中的规定重新传输SYN或第一个ACK。SYN洪水防御的大多数多样性来自于这些算法中限制负载的变化，因此无法使用通用标准MIB进行检测。
The Listen Table instruments all passively opened TCP connections in terms of observable protocol events (e.g., sent and received segments) and resource allocation events (entering the backlog and being accepted). This approach eases generalization to SYN-flood mechanisms that use alternate TCP state transition diagrams and implicit mechanisms to encode some states.
侦听表根据可观察到的协议事件（例如，发送和接收的段）和资源分配事件（输入待办事项并被接受）来检测所有被动打开的TCP连接。这种方法简化了对synflood机制的推广，synflood机制使用备用TCP状态转换图和隐式机制对某些状态进行编码。
This MIB module IMPORTS definitions from [RFC2578], [RFC2579],
[RFC2580], [RFC2856], [RFC4022], and [RFC4502]. It uses REFERENCE
clauses to refer to [RFC791], [RFC793], [RFC1122], [RFC1191],
[RFC1323], [RFC2018], [RFC2581], [RFC2861], [RFC2883], [RFC2988],
[RFC3168], [RFC3260], [RFC3517], [RFC3522], and [RFC3742].
This MIB module IMPORTS definitions from [RFC2578], [RFC2579],
[RFC2580], [RFC2856], [RFC4022], and [RFC4502]. It uses REFERENCE
clauses to refer to [RFC791], [RFC793], [RFC1122], [RFC1191],
[RFC1323], [RFC2018], [RFC2581], [RFC2861], [RFC2883], [RFC2988],
[RFC3168], [RFC3260], [RFC3517], [RFC3522], and [RFC3742].
TCP-ESTATS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, Counter32, Integer32, Unsigned32,
Gauge32, OBJECT-TYPE, mib-2,
NOTIFICATION-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB -- [RFC4502]
ZeroBasedCounter64
FROM HCNUM-TC -- [RFC2856]
TEXTUAL-CONVENTION,
DateAndTime, TruthValue, TimeStamp
TCP-ESTATS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, Counter32, Integer32, Unsigned32,
Gauge32, OBJECT-TYPE, mib-2,
NOTIFICATION-TYPE
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB -- [RFC4502]
ZeroBasedCounter64
FROM HCNUM-TC -- [RFC2856]
TEXTUAL-CONVENTION,
DateAndTime, TruthValue, TimeStamp
FROM SNMPv2-TC -- [RFC2579] tcpListenerEntry, tcpConnectionEntry FROM TCP-MIB; -- [RFC4022]
来自SNMPv2 TC--[RFC2579]tcpListenerEntry，来自TCP-MIB的tcpConnectionEntry；--[RFC4022]
tcpEStatsMIB MODULE-IDENTITY LAST-UPDATED "200705180000Z" -- 18 May 2007 ORGANIZATION "IETF TSV Working Group" CONTACT-INFO "Matt Mathis John Heffner Web100 Project Pittsburgh Supercomputing Center 300 S. Craig St. Pittsburgh, PA 15213 Email: mathis@psc.edu, jheffner@psc.edu
tcpEStatsMIB模块标识上次更新“200705180000Z”-2007年5月18日组织“IETF TSV工作组”联系方式“Matt Mathis John Heffner Web100项目匹兹堡超级计算中心300 S.Craig St.Pittsburgh，PA 15213电子邮件：mathis@psc.edu, jheffner@psc.edu
Rajiv Raghunarayan Cisco Systems Inc. San Jose, CA 95134 Phone: 408 853 9612 Email: raraghun@cisco.com
Rajiv Raghunarayan Cisco Systems Inc.加利福尼亚州圣何塞市95134电话：408 853 9612电子邮件：raraghun@cisco.com
Jon Saperia 84 Kettell Plain Road Stow, MA 01775 Phone: 617-201-2655 Email: saperia@jdscons.com " DESCRIPTION "Documentation of TCP Extended Performance Instrumentation variables from the Web100 project. [Web100]
Jon Saperia 84 Kettell Plain Road Stow，马萨诸塞州01775电话：617-201-2655电子邮件：saperia@jdscons.comWeb100项目中TCP扩展性能检测变量的“说明”文档。[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.
此MIB中的所有对象必须具有与底层TCP实现相同的持久性属性。重新启动时，必须清除所有基于零的计数器，删除所有动态创建的表行，并将所有读写对象恢复为其默认值。
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.
假设所有TCP实现都有一些初始化代码（如果没有其他设置IP地址的代码），在建立第一个TCP连接之前，这些代码有机会调整TCPESTATSConTableLatency和控制各种表创建的其他读写标量。实现还可以选择使这些控制标量在重新启动期间保持不变。
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."
版权所有（C）IETF信托基金（2007年）。此版本的MIB模块是RFC 4898的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200705180000Z" -- 18 May 2007
DESCRIPTION
"Initial version, published as RFC 4898."
::= { mib-2 156 }
REVISION "200705180000Z" -- 18 May 2007
DESCRIPTION
"Initial version, published as RFC 4898."
::= { mib-2 156 }
tcpEStatsNotifications OBJECT IDENTIFIER ::= { tcpEStatsMIB 0 }
tcpEStatsMIBObjects OBJECT IDENTIFIER ::= { tcpEStatsMIB 1 }
tcpEStatsConformance OBJECT IDENTIFIER ::= { tcpEStatsMIB 2 }
tcpEStats OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 1 }
tcpEStatsControl OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 2 }
tcpEStatsScalar OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 3 }
tcpEStatsNotifications OBJECT IDENTIFIER ::= { tcpEStatsMIB 0 }
tcpEStatsMIBObjects OBJECT IDENTIFIER ::= { tcpEStatsMIB 1 }
tcpEStatsConformance OBJECT IDENTIFIER ::= { tcpEStatsMIB 2 }
tcpEStats OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 1 }
tcpEStatsControl OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 2 }
tcpEStatsScalar OBJECT IDENTIFIER ::= { tcpEStatsMIBObjects 3 }
-- -- Textual Conventions --
----文本约定--
TcpEStatsNegotiated ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates if some optional TCP feature was negotiated.
TcpEStatsNegotiated ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"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.
Enabled（1）表示已成功协商该功能，这通常要求两台主机都同意使用该功能。
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.
selfDisabled（2）表示本地主机拒绝该功能，因为该功能未实现、未配置为关闭，或由于其他原因（如资源不足）而被拒绝。
peerDisabled(3) indicates that the local host was willing
to negotiate the feature, but the remote host did not
do so."
SYNTAX INTEGER {
enabled(1),
selfDisabled(2),
peerDisabled(3)
}
peerDisabled(3) indicates that the local host was willing
to negotiate the feature, but the remote host did not
do so."
SYNTAX INTEGER {
enabled(1),
selfDisabled(2),
peerDisabled(3)
}
-- -- TCP Extended statistics scalars --
----TCP扩展统计标量--
tcpEStatsListenerTableLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsListenerTableLastChange对象类型语法时间戳MAX-ACCESS只读状态当前说明
"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."
::= { tcpEStatsScalar 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."
::= { tcpEStatsScalar 3 }
-- ================================================================
--
-- The tcpEStatsControl Group
--
-- ================================================================
--
-- The tcpEStatsControl Group
--
-- The scalar objects in this group are used to control the
-- activation and deactivation of the TCP Extended Statistics
-- tables and notifications in this module.
--
-- The scalar objects in this group are used to control the
-- activation and deactivation of the TCP Extended Statistics
-- tables and notifications in this module.
--
tcpEStatsControlPath OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the activation of the TCP Path Statistics table.
tcpEStatsControlPath对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION“控制TCP路径统计表的激活。
A value 'true' indicates that the TCP Path Statistics
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 1 }
A value 'true' indicates that the TCP Path Statistics
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 1 }
tcpEStatsControlStack OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the activation of the TCP Stack Statistics table.
tcpEStatsControlStack对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION“控制TCP堆栈统计表的激活。
A value 'true' indicates that the TCP Stack Statistics
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 2 }
A value 'true' indicates that the TCP Stack Statistics
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 2 }
tcpEStatsControlApp OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write
tcpEStatsControlApp对象类型语法TruthValue MAX-ACCESS读写
STATUS current DESCRIPTION "Controls the activation of the TCP Application Statistics table.
状态当前描述”控制TCP应用程序统计表的激活。
A value 'true' indicates that the TCP Application
Statistics table is active, while 'false' indicates
that the table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 3 }
A value 'true' indicates that the TCP Application
Statistics table is active, while 'false' indicates
that the table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 3 }
tcpEStatsControlTune OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the activation of the TCP Tuning table.
tcpEStatsControlTune对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION“控制TCP调优表的激活。
A value 'true' indicates that the TCP Tuning
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 4 }
A value 'true' indicates that the TCP Tuning
table is active, while 'false' indicates that the
table is inactive."
DEFVAL { false }
::= { tcpEStatsControl 4 }
tcpEStatsControlNotify OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the generation of all notifications defined in this MIB.
tcpEStatsControlNotify对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION“控制此MIB中定义的所有通知的生成。
A value 'true' indicates that the notifications
are active, while 'false' indicates that the
notifications are inactive."
DEFVAL { false }
::= { tcpEStatsControl 5 }
A value 'true' indicates that the notifications
are active, while 'false' indicates that the
notifications are inactive."
DEFVAL { false }
::= { tcpEStatsControl 5 }
tcpEStatsConnTableLatency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "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
TCPESTATSConTableLatency对象类型语法Unsigned32个单位“秒”MAX-ACCESS read-write STATUS current DESCRIPTION指定连接首次进入关闭状态后实体将在TCP连接表中保留条目的秒数。实体应提供一个配置选项以启用
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"
DEFVAL { 0 }
::= { tcpEStatsControl 6 }
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"
DEFVAL { 0 }
::= { tcpEStatsControl 6 }
-- ================================================================
--
-- Listener Table
--
-- ================================================================
--
-- Listener Table
--
tcpEStatsListenerTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpEStatsListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about TCP Listeners,
in addition to the information maintained by the
tcpListenerTable RFC 4022."
::= { tcpEStats 1 }
tcpEStatsListenerTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpEStatsListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about TCP Listeners,
in addition to the information maintained by the
tcpListenerTable RFC 4022."
::= { tcpEStats 1 }
tcpEStatsListenerEntry OBJECT-TYPE
SYNTAX TcpEStatsListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in the table contains information about
a specific TCP Listener."
AUGMENTS { tcpListenerEntry }
::= { tcpEStatsListenerTable 1 }
tcpEStatsListenerEntry OBJECT-TYPE
SYNTAX TcpEStatsListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in the table contains information about
a specific TCP Listener."
AUGMENTS { tcpListenerEntry }
::= { tcpEStatsListenerTable 1 }
TcpEStatsListenerEntry ::= SEQUENCE {
tcpEStatsListenerStartTime TimeStamp,
tcpEStatsListenerSynRcvd ZeroBasedCounter32,
tcpEStatsListenerInitial ZeroBasedCounter32,
tcpEStatsListenerEstablished ZeroBasedCounter32,
tcpEStatsListenerAccepted ZeroBasedCounter32,
tcpEStatsListenerExceedBacklog ZeroBasedCounter32,
tcpEStatsListenerHCSynRcvd ZeroBasedCounter64,
tcpEStatsListenerHCInitial ZeroBasedCounter64,
tcpEStatsListenerHCEstablished ZeroBasedCounter64,
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 }
TCPESTATSLISTENERCACCEPTED Zero-BasedCounter64，TCPESTATSLISTENERCECEDbacklog Zero-BasedCounter64，TCPESTATSLISTENERCURE采购量表32，tcpEStatsListenerCurBacklog UNSIGNED 32，TCPESTATSLISTENERCUREBACKLOG量表32，TCPESTATSLISTENERCUREBACKLOG量表32}
tcpEStatsListenerStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 1 }
tcpEStatsListenerStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 1 }
tcpEStatsListenerSynRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 2 }
tcpEStatsListenerSynRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 2 }
tcpEStatsListenerInitial OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 3 }
tcpEStatsListenerInitial OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 3 }
tcpEStatsListenerEstablished OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsListenerEstablished对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明
"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)."
::= { tcpEStatsListenerEntry 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)."
::= { tcpEStatsListenerEntry 4 }
tcpEStatsListenerAccepted OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of connections for which the Listener
has successfully issued an accept, removing the connection
from the backlog."
::= { tcpEStatsListenerEntry 5 }
tcpEStatsListenerAccepted OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of connections for which the Listener
has successfully issued an accept, removing the connection
from the backlog."
::= { tcpEStatsListenerEntry 5 }
tcpEStatsListenerExceedBacklog OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 6 }
tcpEStatsListenerExceedBacklog OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 6 }
tcpEStatsListenerHCSynRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 7 }
tcpEStatsListenerHCSynRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 7 }
tcpEStatsListenerHCInitial OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 8 }
tcpEStatsListenerHCInitial OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 8 }
tcpEStatsListenerHCEstablished OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 9 }
tcpEStatsListenerHCEstablished OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 9 }
tcpEStatsListenerHCAccepted OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 10 }
tcpEStatsListenerHCAccepted OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 10 }
tcpEStatsListenerHCExceedBacklog OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 11 }
tcpEStatsListenerHCExceedBacklog OBJECT-TYPE
SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 11 }
tcpEStatsListenerCurConns OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 12 }
tcpEStatsListenerCurConns OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 12 }
tcpEStatsListenerMaxBacklog OBJECT-TYPE
tcpEStatsListenerMaxBacklog对象类型
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of connections allowed in the
backlog at one time."
::= { tcpEStatsListenerEntry 13 }
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of connections allowed in the
backlog at one time."
::= { tcpEStatsListenerEntry 13 }
tcpEStatsListenerCurBacklog OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
TCPESTATSLIESTENERCUBACKLOG对象类型语法量表32 MAX-ACCESS只读状态当前描述“积压工作中的当前连接数。此量表包括处于已建立或SYN-RECEIVED状态的连接，侦听器尚未对其发出接受。
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."
::= { tcpEStatsListenerEntry 14 }
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."
::= { tcpEStatsListenerEntry 14 }
tcpEStatsListenerCurEstabBacklog OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 15 }
tcpEStatsListenerCurEstabBacklog OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsListenerEntry 15 }
-- ================================================================
--
-- TCP Connection ID Table
--
-- ================================================================
--
-- TCP Connection ID Table
--
tcpEStatsConnectIdTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsConnectIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table maps information that uniquely identifies each active TCP connection to the connection ID used by
TcpestatsConnectedTable对象类型TcpestatsConnectedEntry MAX-ACCESS的语法序列不可访问状态当前描述“此表将唯一标识每个活动TCP连接的信息映射到用户使用的连接ID
other tables in this MIB Module. It is an extension of tcpConnectionTable in RFC 4022.
此MIB模块中的其他表。它是RFC4022中tcpConnectionTable的扩展。
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."
::= { tcpEStats 2 }
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."
::= { tcpEStats 2 }
tcpEStatsConnectIdEntry OBJECT-TYPE
SYNTAX TcpEStatsConnectIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table maps a TCP connection
4-tuple to a connection index."
AUGMENTS { tcpConnectionEntry }
::= { tcpEStatsConnectIdTable 1 }
tcpEStatsConnectIdEntry OBJECT-TYPE
SYNTAX TcpEStatsConnectIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table maps a TCP connection
4-tuple to a connection index."
AUGMENTS { tcpConnectionEntry }
::= { tcpEStatsConnectIdTable 1 }
TcpEStatsConnectIdEntry ::= SEQUENCE {
tcpEStatsConnectIndex Unsigned32
}
TcpEStatsConnectIdEntry ::= SEQUENCE {
tcpEStatsConnectIndex Unsigned32
}
tcpEStatsConnectIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "A unique integer value assigned to each TCP Connection entry.
tcpEStatsConnectIndex对象类型语法Unsigned32（1..4294967295）MAX-ACCESS只读状态当前描述“分配给每个TCP连接项的唯一整数值。
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."
::= { tcpEStatsConnectIdEntry 1 }
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."
::= { tcpEStatsConnectIdEntry 1 }
-- ================================================================
--
-- Basic TCP Performance Statistics
--
-- ================================================================
--
-- Basic TCP Performance Statistics
--
tcpEStatsPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
tcpEStatsPerfTable对象类型语法TcpEStatsPerfEntry MAX-ACCESS的序列不可访问状态当前描述
"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.
测量TCP性能和一线问题诊断。此表中的大多数对象直接公开某些TCP状态变量，或者很容易实现为TCP状态变量的简单函数（例如，最大值）。
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."
::= { tcpEStats 3 }
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."
::= { tcpEStats 3 }
tcpEStatsPerfEntry OBJECT-TYPE
SYNTAX TcpEStatsPerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsPerfTable 1 }
tcpEStatsPerfEntry OBJECT-TYPE
SYNTAX TcpEStatsPerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsPerfTable 1 }
TcpEStatsPerfEntry ::= SEQUENCE {
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,
tcpEStatsPerfSegsOut ZeroBasedCounter32、tcpEStatsPerfDataSegsOut ZeroBasedCounter32、tcpEStatsPerfDataOctetsOut ZeroBasedCounter32、tcpEStatsPerfHCDataOctetsOut ZeroBasedCounter64、tcpEStatsPerfSegsRetrans ZeroBasedCounter32、tcpEStatsPerfOctetsRetrans ZeroBasedCounter32、TCPESTATSPERFSEGS ZeroBasedCounter32、，tcpEStatsPerfDataSegsIn ZeroBasedCounter32，tcpEStatsPerfDataOctetsIn ZeroBasedCounter32，tcpEStatsPerfDataOctetsIn ZeroBasedCounter64，tcpEStatsPerfElapsedSecs ZeroBasedCounter32，tcpEStatsPerfStartTimeStamp日期和时间，tcpEStatsPerfCurMSS量表32，TcpestatsPerfPipesPipesPipesSize量表32，tcpEStatsPerfMaxPipeSize量表32、TcpestatsPerfSmoothDrTT量表32、tcpEStatsPerfCurRTO量表32、tcpEStatsPerfCongSignals ZeroBasedCounter32、tcpEStatsPerfCurCwnd量表32、TcpestatsPerfCursThresh量表32、tcpEStatsPerfTimeouts ZeroBasedCounter32、tcpEStatsPerfCurRwinSent量表32、，
tcpEStatsPerfMaxRwinSent Gauge32, tcpEStatsPerfZeroRwinSent ZeroBasedCounter32, tcpEStatsPerfCurRwinRcvd Gauge32, tcpEStatsPerfMaxRwinRcvd Gauge32, tcpEStatsPerfZeroRwinRcvd ZeroBasedCounter32, tcpEStatsPerfSndLimTransRwin ZeroBasedCounter32, tcpEStatsPerfSndLimTransCwnd ZeroBasedCounter32, tcpEStatsPerfSndLimTransSnd ZeroBasedCounter32, tcpEStatsPerfSndLimTimeRwin ZeroBasedCounter32, tcpEStatsPerfSndLimTimeCwnd ZeroBasedCounter32, tcpEStatsPerfSndLimTimeSnd ZeroBasedCounter32 }
tcpEStatsPerfMaxRwinSent量表32、tcpEStatsPerfZeroRwinSent ZeroBasedCounter32、tcpEStatsPerfCurRwinRcvd量表32、tcpEStatsPerfMaxRwinRcvd量表32、tcpEStatsPerfZeroRwinRcvd ZeroBasedCounter32、TcpestatsPerfSndlimTranscrwin ZeroBasedCounter32、tcpEStatsPerfSndLimTransSnd ZeroBasedCounter32、，tcpEStatsPerfSndLimTimeRwin ZeroBasedCounter32，tcpEStatsPerfSndLimTimeCwnd ZeroBasedCounter32，tcpEStatsPerfSndLimTimeSnd ZeroBasedCounter32}
--
-- The following objects provide statistics on aggregate
-- segments and data sent on a connection. These provide a
-- direct measure of the Internet capacity consumed by a
-- connection.
--
--
-- The following objects provide statistics on aggregate
-- segments and data sent on a connection. These provide a
-- direct measure of the Internet capacity consumed by a
-- connection.
--
tcpEStatsPerfSegsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments sent."
::= { tcpEStatsPerfEntry 1 }
tcpEStatsPerfSegsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments sent."
::= { tcpEStatsPerfEntry 1 }
tcpEStatsPerfDataSegsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments sent containing a positive length
data segment."
::= { tcpEStatsPerfEntry 2 }
tcpEStatsPerfDataSegsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments sent containing a positive length
data segment."
::= { tcpEStatsPerfEntry 2 }
tcpEStatsPerfDataOctetsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of data contained in transmitted
segments, including retransmitted data. Note that this does
not include TCP headers."
::= { tcpEStatsPerfEntry 3 }
tcpEStatsPerfDataOctetsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of data contained in transmitted
segments, including retransmitted data. Note that this does
not include TCP headers."
::= { tcpEStatsPerfEntry 3 }
tcpEStatsPerfHCDataOctetsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 4 }
tcpEStatsPerfHCDataOctetsOut OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 4 }
tcpEStatsPerfSegsRetrans OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments transmitted containing at least some
retransmitted data."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 5 }
tcpEStatsPerfSegsRetrans OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments transmitted containing at least some
retransmitted data."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 5 }
tcpEStatsPerfOctetsRetrans OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets retransmitted."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 6 }
tcpEStatsPerfOctetsRetrans OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets retransmitted."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 6 }
tcpEStatsPerfSegsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments received."
::= { tcpEStatsPerfEntry 7 }
tcpEStatsPerfSegsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments received."
::= { tcpEStatsPerfEntry 7 }
tcpEStatsPerfDataSegsIn OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of segments received containing a positive
tcpEStatsPerfDataSegsIn对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明“接收到的包含正
length data segment."
::= { tcpEStatsPerfEntry 8 }
length data segment."
::= { tcpEStatsPerfEntry 8 }
tcpEStatsPerfDataOctetsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in received data segments,
including retransmitted data. Note that this does not
include TCP headers."
::= { tcpEStatsPerfEntry 9 }
tcpEStatsPerfDataOctetsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in received data segments,
including retransmitted data. Note that this does not
include TCP headers."
::= { tcpEStatsPerfEntry 9 }
tcpEStatsPerfHCDataOctetsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 10 }
tcpEStatsPerfHCDataOctetsIn OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 10 }
tcpEStatsPerfElapsedSecs OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The seconds part of the time elapsed between
tcpEStatsPerfStartTimeStamp and the most recent protocol
event (segment sent or received)."
::= { tcpEStatsPerfEntry 11 }
tcpEStatsPerfElapsedSecs OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The seconds part of the time elapsed between
tcpEStatsPerfStartTimeStamp and the most recent protocol
event (segment sent or received)."
::= { tcpEStatsPerfEntry 11 }
tcpEStatsPerfElapsedMicroSecs OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 12 }
tcpEStatsPerfElapsedMicroSecs OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 12 }
tcpEStatsPerfStartTimeStamp OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time at which this row was created and all
ZeroBasedCounters in the row were initialized to zero."
::= { tcpEStatsPerfEntry 13 }
tcpEStatsPerfStartTimeStamp OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time at which this row was created and all
ZeroBasedCounters in the row were initialized to zero."
::= { tcpEStatsPerfEntry 13 }
--
-- The following objects can be used to fit minimal
-- performance models to the TCP data rate.
--
--
-- The following objects can be used to fit minimal
-- performance models to the TCP data rate.
--
tcpEStatsPerfCurMSS OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current maximum segment size (MSS), in octets."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsPerfEntry 14 }
tcpEStatsPerfCurMSS OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current maximum segment size (MSS), in octets."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsPerfEntry 14 }
tcpEStatsPerfPipeSize OBJECT-TYPE SYNTAX Gauge32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The TCP senders current estimate of the number of unacknowledged data octets in the network.
tcpEStatsPerfPipeSize对象类型语法量表32单位“八位字节”最大访问只读状态当前描述“TCP发送方当前估计网络中未确认的数据八位字节数。
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]
当未处于恢复状态时（例如，当接收方未向发送方报告丢失的数据时），这与RFC 2581中定义的“航班大小”完全相同，可以计算为SND.NXT减去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.
在恢复过程中，TCP发送方关于网络状态的信息不完整（例如，哪些网段丢失或重新排序，特别是当返回路径也在丢弃TCP确认时）。当前的TCP标准不要求使用任何特定的算法来估计网络中未确认的数据八位字节数。
RFC 3517 describes a conservative algorithm to use SACK
RFC3517描述了使用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).
用于估计网络中未确认数据八位字节数的信息。tcpEStatsPerfPipeSize对象应与RFC 3517中定义的“管道”相同（如果已实现）。（请注意，虽然未处于恢复状态，但管道算法生成的值与航班大小相同）。
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"
REFERENCE
"RFC 793, RFC 2581, RFC 3517"
::= { tcpEStatsPerfEntry 15 }
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"
REFERENCE
"RFC 793, RFC 2581, RFC 3517"
::= { tcpEStatsPerfEntry 15 }
tcpEStatsPerfMaxPipeSize OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of tcpEStatsPerfPipeSize, for this
connection."
REFERENCE
"RFC 793, RFC 2581, RFC 3517"
::= { tcpEStatsPerfEntry 16 }
tcpEStatsPerfMaxPipeSize OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of tcpEStatsPerfPipeSize, for this
connection."
REFERENCE
"RFC 793, RFC 2581, RFC 3517"
::= { tcpEStatsPerfEntry 16 }
tcpEStatsPerfSmoothedRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smoothed round trip time used in calculation of the
RTO. See SRTT in [RFC2988]."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 17 }
tcpEStatsPerfSmoothedRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smoothed round trip time used in calculation of the
RTO. See SRTT in [RFC2988]."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 17 }
tcpEStatsPerfCurRTO OBJECT-TYPE SYNTAX Gauge32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsPerfCurRTO对象类型语法量表32单位“毫秒”最大访问只读状态当前说明
"The current value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 18 }
"The current value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 18 }
tcpEStatsPerfCongSignals OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
tcpEStatsPerfCongSignals对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“由于各种形式的拥塞信号（包括快速重传、显式拥塞通知（ECN））而进行的乘法向下拥塞窗口调整的次数”，和超时。此对象汇总所有调用加性增加乘性减少（AIMD）拥塞控制的MD部分的事件，因此是cwnd如何受到拥塞影响的最佳指示器。
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 19 }
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 19 }
tcpEStatsPerfCurCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current congestion window, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 20 }
tcpEStatsPerfCurCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current congestion window, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 20 }
tcpEStatsPerfCurSsthresh OBJECT-TYPE SYNTAX Gauge32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The current slow start threshold in octets." REFERENCE "RFC 2581, TCP Congestion Control"
tcpEStatsPerfCurSsthresh对象类型语法量表32单位“八位字节”最大访问只读状态当前描述“当前慢启动阈值（八位字节）”。参考“RFC 2581，TCP拥塞控制”
::= { tcpEStatsPerfEntry 21 }
::= { tcpEStatsPerfEntry 21 }
tcpEStatsPerfTimeouts OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the retransmit timeout has expired when
the RTO backoff multiplier is equal to one."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 22 }
tcpEStatsPerfTimeouts OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the retransmit timeout has expired when
the RTO backoff multiplier is equal to one."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPerfEntry 22 }
--
-- The following objects instrument receiver window updates
-- sent by the local receiver to the remote sender. These can
-- be used to determine if the local receiver is exerting flow
-- control back pressure on the remote sender.
--
--
-- The following objects instrument receiver window updates
-- sent by the local receiver to the remote sender. These can
-- be used to determine if the local receiver is exerting flow
-- control back pressure on the remote sender.
--
tcpEStatsPerfCurRwinSent OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent window advertisement sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 23 }
tcpEStatsPerfCurRwinSent OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent window advertisement sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 23 }
tcpEStatsPerfMaxRwinSent OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum window advertisement sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 24 }
tcpEStatsPerfMaxRwinSent OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum window advertisement sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 24 }
tcpEStatsPerfZeroRwinSent OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of acknowledgments sent announcing a zero
tcpEStatsPerfZeroRwinSent对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明“发送的通知零的确认数
receive window, when the previously announced window was
not zero."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 25 }
receive window, when the previously announced window was
not zero."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 25 }
--
-- The following objects instrument receiver window updates
-- from the far end-system to determine if the remote receiver
-- has sufficient buffer space or is exerting flow-control
-- back pressure on the local sender.
--
--
-- The following objects instrument receiver window updates
-- from the far end-system to determine if the remote receiver
-- has sufficient buffer space or is exerting flow-control
-- back pressure on the local sender.
--
tcpEStatsPerfCurRwinRcvd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent window advertisement received, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 26 }
tcpEStatsPerfCurRwinRcvd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent window advertisement received, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 26 }
tcpEStatsPerfMaxRwinRcvd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum window advertisement received, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 27 }
tcpEStatsPerfMaxRwinRcvd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum window advertisement received, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 27 }
tcpEStatsPerfZeroRwinRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of acknowledgments received announcing a zero
receive window, when the previously announced window was
not zero."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 28 }
tcpEStatsPerfZeroRwinRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of acknowledgments received announcing a zero
receive window, when the previously announced window was
not zero."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 28 }
--
--
-- The following optional objects can be used to quickly
-- identify which subsystems are limiting TCP performance.
-- There are three parallel pairs of instruments that measure
-- the extent to which TCP performance is limited by the
-- announced receiver window (indicating a receiver
-- bottleneck), the current congestion window or
-- retransmission timeout (indicating a path bottleneck) and
-- all others events (indicating a sender bottleneck).
--
-- These instruments SHOULD be updated every time the TCP
-- output routine stops sending data. The elapsed time since
-- the previous stop is accumulated into the appropriate
-- object as determined by the previous stop reason (e.g.,
-- stop state). The current stop reason determines which timer
-- will be updated the next time TCP output stops.
--
-- Since there is no explicit stop at the beginning of a
-- timeout, it is necessary to retroactively reclassify the
-- previous stop as 'Congestion Limited'.
--
-- The following optional objects can be used to quickly
-- identify which subsystems are limiting TCP performance.
-- There are three parallel pairs of instruments that measure
-- the extent to which TCP performance is limited by the
-- announced receiver window (indicating a receiver
-- bottleneck), the current congestion window or
-- retransmission timeout (indicating a path bottleneck) and
-- all others events (indicating a sender bottleneck).
--
-- These instruments SHOULD be updated every time the TCP
-- output routine stops sending data. The elapsed time since
-- the previous stop is accumulated into the appropriate
-- object as determined by the previous stop reason (e.g.,
-- stop state). The current stop reason determines which timer
-- will be updated the next time TCP output stops.
--
-- Since there is no explicit stop at the beginning of a
-- timeout, it is necessary to retroactively reclassify the
-- previous stop as 'Congestion Limited'.
--
tcpEStatsPerfSndLimTransRwin OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 31 }
tcpEStatsPerfSndLimTransRwin OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsPerfEntry 31 }
tcpEStatsPerfSndLimTransCwnd OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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'
tcpEStatsPerfSndLimTransCwnd对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明“从“接收方受限”或“发送方受限”状态过渡到“拥塞受限”状态的次数。每当TCP传输因发送方达到拥塞控制（例如cwnd）或其他用于控制网络流量的算法（重传超时）定义的限制而停止时，就会进入此状态。请参见“拥塞窗口”的定义
in RFC 2581."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 32 }
in RFC 2581."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPerfEntry 32 }
tcpEStatsPerfSndLimTransSnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 33 }
tcpEStatsPerfSndLimTransSnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPerfEntry 33 }
tcpEStatsPerfSndLimTimeRwin OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The cumulative time spent in the 'Receiver Limited' state.
See tcpEStatsPerfSndLimTransRwin."
::= { tcpEStatsPerfEntry 34 }
tcpEStatsPerfSndLimTimeRwin OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The cumulative time spent in the 'Receiver Limited' state.
See tcpEStatsPerfSndLimTransRwin."
::= { tcpEStatsPerfEntry 34 }
tcpEStatsPerfSndLimTimeCwnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.)"
::= { tcpEStatsPerfEntry 35 }
tcpEStatsPerfSndLimTimeCwnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.)"
::= { tcpEStatsPerfEntry 35 }
tcpEStatsPerfSndLimTimeSnd OBJECT-TYPE SYNTAX ZeroBasedCounter32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current
tcpEStatsPerfSndLimTimeSnd对象类型语法ZeroBasedCounter32单位“毫秒”最大访问只读状态当前
DESCRIPTION
"The cumulative time spent in the 'Sender Limited' state.
See tcpEStatsPerfSndLimTransSnd."
::= { tcpEStatsPerfEntry 36 }
DESCRIPTION
"The cumulative time spent in the 'Sender Limited' state.
See tcpEStatsPerfSndLimTransSnd."
::= { tcpEStatsPerfEntry 36 }
-- ================================================================
--
-- Statistics for diagnosing path problems
--
-- ================================================================
--
-- Statistics for diagnosing path problems
--
tcpEStatsPathTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsPathEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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.
TCPESTATSPATHTTABLE对象类型TcpEStatsPathEntry MAX-ACCESS不可访问状态当前描述”此表包含可用于推断Internet路径详细行为的对象，例如重新排序的程度、ECN位以及RTT波动是否与损失相关。
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."
::= { tcpEStats 4 }
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."
::= { tcpEStats 4 }
tcpEStatsPathEntry OBJECT-TYPE
SYNTAX TcpEStatsPathEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsPathTable 1 }
tcpEStatsPathEntry OBJECT-TYPE
SYNTAX TcpEStatsPathEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsPathTable 1 }
TcpEStatsPathEntry ::= SEQUENCE {
TcpEStatsPathEntry ::= SEQUENCE {
tcpEStatsPathRetranThresh Gauge32, tcpEStatsPathNonRecovDAEpisodes ZeroBasedCounter32, tcpEStatsPathSumOctetsReordered ZeroBasedCounter32, tcpEStatsPathNonRecovDA ZeroBasedCounter32, tcpEStatsPathSampleRTT Gauge32, tcpEStatsPathRTTVar Gauge32, tcpEStatsPathMaxRTT Gauge32, tcpEStatsPathMinRTT Gauge32, tcpEStatsPathSumRTT ZeroBasedCounter32,
TCPESTATSPATHNONRECOVDES零基计数器32，TCPESTATSPATHNORRECOVDES零基计数器32，TCPESTATSPATHNONRECOVDES零基计数器32，TCPESTATSPATHNONRECOVDES零基计数器32，TCPESTATSPATHNONRECOVDES采样仪32，TCPESTATSPATHNRTCVAR VAR仪表32，TCPESTATSPATHMAXRTTT零基计数器32，
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 }
tcpEStatsPathHCSumRTT零基计数器64、tcpEStatsPathCountRTT零基计数器32、tcpEStatsPathMaxRTO计量器32、TcpestatspathMumrto计量器32、TcpestatspathPumrttl无符号32、TcpestatspathPurtosin八位字节字符串、TcpestatspathPurconsumWnd零基计数器32、TcpestathPurconsumrots零基计数器32、，Tcpestatspathpostconsumt ZeroBasedCounter32，Tcpestatspathpostconsumt ZeroBasedCounter32，TcpestatspathspathegnalszerobasedCounter32，Tcpestatspathdupacks ZeroBasedCounter32，tcpEStatsPathRcvRTT仪表32，Tcpestatspatspatspathpostconsumt ZeroBasedCounter32，Tcpestatspathepresent ZeroBasedCounter32}
--
-- The following optional objects can be used to infer segment
-- reordering on the path from the local sender to the remote
-- receiver.
--
--
-- The following optional objects can be used to infer segment
-- reordering on the path from the local sender to the remote
-- receiver.
--
tcpEStatsPathRetranThresh OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 1 }
tcpEStatsPathRetranThresh OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 1 }
tcpEStatsPathNonRecovDAEpisodes OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
tcpEStatsPathNonRecovDAEpisodes对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“由于ACK在到达RENTHRESH的重复确认数之前提前，因此未触发快速重新传输的重复确认数。
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.
在许多实现中，这是当“dupacks”计数器为非零但小于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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 2 }
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 2 }
tcpEStatsPathSumOctetsReordered OBJECT-TYPE SYNTAX ZeroBasedCounter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The sum of the amounts SND.UNA advances on the acknowledgment which ends a dup-ack episode without a retransmission.
TcpestatspathsumOctetsOrdered对象类型语法ZeroBasedCounter32单元“octets”MAX-ACCESS只读状态当前描述“SND.UNA在确认时预付的金额之和，该确认结束dup ack事件而不重新传输。
Note the change in tcpEStatsPathSumOctetsReordered divided
by the change in tcpEStatsPathNonRecovDAEpisodes is an
estimates of the average reordering distance, over some
interval."
::= { tcpEStatsPathEntry 3 }
Note the change in tcpEStatsPathSumOctetsReordered divided
by the change in tcpEStatsPathNonRecovDAEpisodes is an
estimates of the average reordering distance, over some
interval."
::= { tcpEStatsPathEntry 3 }
tcpEStatsPathNonRecovDA OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Duplicate acks (or SACKS) that did not trigger a Fast Retransmit because ACK advanced prior to the number of duplicate acknowledgments reaching RetranThresh.
tcpEStatsPathNonRecovDA对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“重复确认（或SACK）未触发快速重新传输，因为确认在到达重新发送之前提前。
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.
在许多实现中，这是“dupacks”计数器的总和，正好在它被设置为零之前，因为ACK在没有快速重传的情况下提前。
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 4 }
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 4 }
--
-- The following optional objects instrument the round trip
-- time estimator and the retransmission timeout timer.
--
--
-- The following optional objects instrument the round trip
-- time estimator and the retransmission timeout timer.
--
tcpEStatsPathSampleRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent raw round trip time measurement used in
calculation of the RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 11 }
tcpEStatsPathSampleRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent raw round trip time measurement used in
calculation of the RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 11 }
tcpEStatsPathRTTVar OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The round trip time variation used in calculation of the
RTO. See RTTVAR in [RFC2988]."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 12 }
tcpEStatsPathRTTVar OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The round trip time variation used in calculation of the
RTO. See RTTVAR in [RFC2988]."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 12 }
tcpEStatsPathMaxRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum sampled round trip time."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 13 }
tcpEStatsPathMaxRTT OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum sampled round trip time."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 13 }
tcpEStatsPathMinRTT OBJECT-TYPE SYNTAX Gauge32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum sampled round trip time." REFERENCE
tcpEStatsPathMinRTT对象类型语法量表32单位“毫秒”最大访问只读状态当前描述“最小采样往返时间”。参考
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 14 }
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 14 }
tcpEStatsPathSumRTT OBJECT-TYPE SYNTAX ZeroBasedCounter32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The sum of all sampled round trip times.
tcpEStatsPathSumRTT对象类型语法ZeroBasedCounter32单位“毫秒”最大访问只读状态当前描述“所有采样往返时间之和”。
Note that the change in tcpEStatsPathSumRTT divided by the
change in tcpEStatsPathCountRTT is the mean RTT, uniformly
averaged over an enter interval."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 15 }
Note that the change in tcpEStatsPathSumRTT divided by the
change in tcpEStatsPathCountRTT is the mean RTT, uniformly
averaged over an enter interval."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 15 }
tcpEStatsPathHCSumRTT OBJECT-TYPE SYNTAX ZeroBasedCounter64 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The sum of all sampled round trip times, on all systems that implement multiple concurrent RTT measurements.
tcpEStatsPathHCSumRTT对象类型语法ZeroBasedCounter64单位“毫秒”最大访问只读状态当前描述“所有实现多个并发RTT测量的系统上所有采样往返时间的总和”。
Note that the change in tcpEStatsPathHCSumRTT divided by
the change in tcpEStatsPathCountRTT is the mean RTT,
uniformly averaged over an enter interval."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 16 }
Note that the change in tcpEStatsPathHCSumRTT divided by
the change in tcpEStatsPathCountRTT is the mean RTT,
uniformly averaged over an enter interval."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 16 }
tcpEStatsPathCountRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of round trip time samples included in
tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 17 }
tcpEStatsPathCountRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of round trip time samples included in
tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 17 }
tcpEStatsPathMaxRTO OBJECT-TYPE SYNTAX Gauge32 UNITS "milliseconds"
tcpEStatsPathMaxRTO对象类型语法量表32单位“毫秒”
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 18 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 18 }
tcpEStatsPathMinRTO OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 19 }
tcpEStatsPathMinRTO OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum value of the retransmit timer RTO."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsPathEntry 19 }
--
-- The following optional objects provide information about
-- how TCP is using the IP layer.
--
--
-- The following optional objects provide information about
-- how TCP is using the IP layer.
--
tcpEStatsPathIpTtl OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the TTL field carried in the most recently
received IP header. This is sometimes useful to detect
changing or unstable routes."
REFERENCE
"RFC 791, Internet Protocol"
::= { tcpEStatsPathEntry 20 }
tcpEStatsPathIpTtl OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the TTL field carried in the most recently
received IP header. This is sometimes useful to detect
changing or unstable routes."
REFERENCE
"RFC 791, Internet Protocol"
::= { tcpEStatsPathEntry 20 }
tcpEStatsPathIpTosIn OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the IPv4 Type of Service octet, or the IPv6 traffic class octet, carried in the most recently received IP header.
tcpEStatsPathIpTosIn对象类型语法八位字节字符串（大小（1））MAX-ACCESS只读状态当前描述“最近接收到的IP报头中携带的IPv4类型的服务八位字节或IPv6流量类八位字节的值。
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."
这有助于诊断TCP和任何IP层数据包调度和传递策略之间的交互，这可能有效地实现区分服务。”
REFERENCE
"RFC 3260, New Terminology and Clarifications for Diffserv"
::= { tcpEStatsPathEntry 21 }
REFERENCE
"RFC 3260, New Terminology and Clarifications for Diffserv"
::= { tcpEStatsPathEntry 21 }
tcpEStatsPathIpTosOut OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the IPv4 Type Of Service octet, or the IPv6 traffic class octet, carried in the most recently transmitted IP header.
tcpEStatsPathIpTosOut对象类型语法八位字节字符串（大小（1））MAX-ACCESS只读状态当前描述“最近传输的IP报头中携带的IPv4类型的服务八位字节或IPv6流量类八位字节的值。
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."
REFERENCE
"RFC 3260, New Terminology and Clarifications for Diffserv"
::= { tcpEStatsPathEntry 22 }
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."
REFERENCE
"RFC 3260, New Terminology and Clarifications for Diffserv"
::= { tcpEStatsPathEntry 22 }
--
-- The following optional objects characterize the congestion
-- feedback signals by collecting statistics on how the
-- congestion events are correlated to losses, changes in RTT
-- and other protocol events.
--
--
-- The following optional objects characterize the congestion
-- feedback signals by collecting statistics on how the
-- congestion events are correlated to losses, changes in RTT
-- and other protocol events.
--
tcpEStatsPathPreCongSumCwnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 23 }
tcpEStatsPathPreCongSumCwnd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 23 }
tcpEStatsPathPreCongSumRTT OBJECT-TYPE SYNTAX ZeroBasedCounter32 UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION
TCPESTATSPATPHPRECONGSUMRTT对象类型语法ZeroBasedCounter32单位“毫秒”最大访问只读状态当前说明
"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."
::= { tcpEStatsPathEntry 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."
::= { tcpEStatsPathEntry 24 }
tcpEStatsPathPostCongSumRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 25 }
tcpEStatsPathPostCongSumRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 25 }
tcpEStatsPathPostCongCountRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 26 }
tcpEStatsPathPostCongCountRTT OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsPathEntry 26 }
--
-- The following optional objects can be used to detect other
-- types of non-loss congestion signals such as source quench
-- or ECN.
--
--
-- The following optional objects can be used to detect other
-- types of non-loss congestion signals such as source quench
-- or ECN.
--
tcpEStatsPathECNsignals OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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
tcpEStatsPathECNsignals对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“通过显式拥塞通知（ECN）传递给TCP发送方的拥塞信号数。这通常是承载回显拥塞的段数
Experienced (ECE) bits, but
should also include segments failing the ECN nonce check or
other explicit congestion signals."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 27 }
Experienced (ECE) bits, but
should also include segments failing the ECN nonce check or
other explicit congestion signals."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 27 }
--
-- The following optional objects are receiver side
-- instruments of the path from the sender to the receiver. In
-- general, the receiver has less information about the state
-- of the path because the receiver does not have a robust
-- mechanism to infer the sender's actions.
--
--
-- The following optional objects are receiver side
-- instruments of the path from the sender to the receiver. In
-- general, the receiver has less information about the state
-- of the path because the receiver does not have a robust
-- mechanism to infer the sender's actions.
--
tcpEStatsPathDupAckEpisodes OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
TCPESTATSPATCHDUPACKSPECTIONS对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“当先前确认不重复时发送的重复确认数。这是连续重复确认序列已发送的次数。
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 28 }
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 28 }
tcpEStatsPathRcvRTT OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The receiver's estimate of the Path RTT.
tcpEStatsPathRcvRTT对象类型语法量表32 MAX-ACCESS只读状态当前描述“接收器对路径RTT的估计。
Adaptive receiver window algorithms depend on the receiver
to having a good estimate of the path RTT."
::= { tcpEStatsPathEntry 29 }
Adaptive receiver window algorithms depend on the receiver
to having a good estimate of the path RTT."
::= { tcpEStatsPathEntry 29 }
tcpEStatsPathDupAcksOut OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION
TCPESTATSPATCHDUPACKSOUT对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明
"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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsPathEntry 30 }
tcpEStatsPathCERcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments received with IP headers bearing
Congestion Experienced (CE) markings."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 31 }
tcpEStatsPathCERcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of segments received with IP headers bearing
Congestion Experienced (CE) markings."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 31 }
tcpEStatsPathECESent OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 32 }
tcpEStatsPathECESent OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsPathEntry 32 }
-- ================================================================
--
-- Statistics for diagnosing stack algorithms
--
-- ================================================================
--
-- Statistics for diagnosing stack algorithms
--
tcpEStatsStackTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsStackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains objects that are most useful for determining how well some of the TCP control algorithms are coping with this particular
TCPESTATSSTACKTACK对象类型TcpEStatsStackEntry的语法序列MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表包含最有助于确定某些TCP控制算法处理此特定问题的能力的对象
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."
::= { tcpEStats 5 }
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."
::= { tcpEStats 5 }
tcpEStatsStackEntry OBJECT-TYPE
SYNTAX TcpEStatsStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsStackTable 1 }
tcpEStatsStackEntry OBJECT-TYPE
SYNTAX TcpEStatsStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsStackTable 1 }
TcpEStatsStackEntry ::= SEQUENCE {
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,
tcpEStatsStackActiveOpen TruthValue、TcpestatssTackMssent Unsigned32、TcpestatssTackMsrcvd Unsigned32、TcpestatsTackWinScaleResent整数32、TcpestatsTackWinScalerCvd整数32、TcpestatsTackTimestacks TcpEStatsNegotiated、TcpestatsTackEcn TcpEStatsNegotiated、TcpestatsTackWillSendsack TcpEStatsNegotiated、，TCpestatssTacks将使用SACK TcpEStatsNegotiated、TCpestatsTackState INTEGER、TCpestatsTackNagle TruthValue、TCpestatsTackMaxsCwnd量表32、TCpestatsTackMaxCwnd量表32、TCpestatsTacksTacksThresh量表32、TCpestatsTacksTacksTacksThresh INTEGER、TCpestatsTacksTacksTcksTcksTcksDupAcksIn还原整数、TCpestcksTacksTacksTacksTacksDup，TcpestatssTacksSproutiousFRDetected ZeroBasedCounter32，TcpestatsTacksSproutiousRTDetected ZeroBasedCounter32，TcpestatsTacksSoftErrors ZeroBasedCounter32，TcpestatsTacksTacksTacksTother减少ZeroBasedCounter32，tcpEStatsStackCongOverCount ZeroBasedCounter32，tcpEStatsStackFastRetran ZeroBasedCounter32，TcpestatssTackSubsequentTimeout 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 }
TCPESTATSSTACKCURTIMEOUTCOUNTER32、tcpEStatsStackAbruptTimeouts ZeroBasedCounter32、tcpEStatsStackSACKsRcvd ZeroBasedCounter32、tcpEStatsStackSendStall ZeroBasedCounter32、TCPESTATSSTACKDSACKSACKDUPS ZeroBasedCounter32、TCPESTATSSTACKMAXMMSS GAUNTER32、TCPESTATSSTACKSSTACKMINMSS GAUNTER32、，TCPESTATSSTACKSNDINATIAL Unsigned32，TCPESTATSSTACKRESTACKRECIATIAL Unsigned32，TCPESTATSSTACKCURRETX队列计量器32，TCPESTATSSTACKMAXRETX队列计量器32，tcpEStatsStackCurReasmQueue计量器32，tcpEStatsStackMaxReasmQueue计量器32}
--
-- The following objects reflect TCP options carried on the
-- SYN or SYN-ACK. These options are used to provide
-- additional protocol parameters or to enable various
-- optional TCP features or algorithms.
--
-- Except as noted, the TCP protocol does not permit these
-- options to change after the SYN exchange.
--
--
-- The following objects reflect TCP options carried on the
-- SYN or SYN-ACK. These options are used to provide
-- additional protocol parameters or to enable various
-- optional TCP features or algorithms.
--
-- Except as noted, the TCP protocol does not permit these
-- options to change after the SYN exchange.
--
tcpEStatsStackActiveOpen OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"True(1) if the local connection traversed the SYN-SENT
state, else false(2)."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 1 }
tcpEStatsStackActiveOpen OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"True(1) if the local connection traversed the SYN-SENT
state, else false(2)."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 1 }
tcpEStatsStackMSSSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value sent in an MSS option, or zero if none."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 2 }
tcpEStatsStackMSSSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value sent in an MSS option, or zero if none."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 2 }
tcpEStatsStackMSSRcvd OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value received in an MSS option, or zero if none."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 3 }
tcpEStatsStackMSSRcvd OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value received in an MSS option, or zero if none."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 3 }
tcpEStatsStackWinScaleSent OBJECT-TYPE SYNTAX Integer32 (-1..14) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the transmitted window scale option if one was sent; otherwise, a value of -1.
tcpEStatsStackWinScaleSent对象类型语法整数32（-1..14）MAX-ACCESS只读状态当前描述“如果发送了窗口缩放选项，则为传输窗口缩放选项的值；否则为-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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 4 }
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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 4 }
tcpEStatsStackWinScaleRcvd OBJECT-TYPE SYNTAX Integer32 (-1..14) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the received window scale option if one was received; otherwise, a value of -1.
tcpEStatsStackWinScaleRcvd对象类型语法整数32（-1..14）MAX-ACCESS只读状态当前描述“如果接收到窗口缩放选项，则为接收窗口缩放选项的值；否则为-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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 5 }
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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 5 }
tcpEStatsStackTimeStamps OBJECT-TYPE SYNTAX TcpEStatsNegotiated MAX-ACCESS read-only
tcpEStatsStackTimeStamps对象类型语法TcpEStatsNegotiated MAX-ACCESS只读
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 6 }
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 1323, TCP Extensions for High Performance"
::= { tcpEStatsStackEntry 6 }
tcpEStatsStackECN OBJECT-TYPE
SYNTAX TcpEStatsNegotiated
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsStackEntry 7 }
tcpEStatsStackECN OBJECT-TYPE
SYNTAX TcpEStatsNegotiated
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 3168, The Addition of Explicit Congestion Notification
(ECN) to IP"
::= { tcpEStatsStackEntry 7 }
tcpEStatsStackWillSendSACK OBJECT-TYPE SYNTAX TcpEStatsNegotiated MAX-ACCESS read-only STATUS current DESCRIPTION "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.
tcpEStatsStackWillSendSACK对象类型语法TcpEStatsNegotiated MAX-ACCESS只读状态当前描述“已启用（1）如果本地主机将发送SACK选项，自禁用（2）如果SACK已禁用或未在本地主机上实现，或peerDisabled（3）如果远程主机未发送SACK允许选项。
Note that SACK negotiation is not symmetrical. SACK can
enabled on one side of the connection and not the other."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 8 }
Note that SACK negotiation is not symmetrical. SACK can
enabled on one side of the connection and not the other."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 8 }
tcpEStatsStackWillUseSACK OBJECT-TYPE SYNTAX TcpEStatsNegotiated MAX-ACCESS read-only STATUS current DESCRIPTION "Enabled(1) if the local host will process SACK options, selfDisabled(2) if SACK is disabled or not implemented on the local host, or peerDisabled(3) if the remote host sends
tcpEStatsStackWillUseSACK对象类型语法TcpEStatsNegotiated MAX-ACCESS只读状态当前描述“已启用（1）如果本地主机将处理SACK选项，自禁用（2）如果SACK已禁用或未在本地主机上实现，或peerDisabled（3）如果远程主机发送
duplicate ACKs without SACK options, or the local host otherwise decides not to process received SACK options.
复制没有SACK选项的ACK，或者本地主机决定不处理收到的SACK选项。
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.
与其他TCP选项不同，远程数据接收器无法明确指示是否能够生成SACK选项。发送数据时，本地主机必须推断远程接收器是否正在发送SACK选项。在SYN交换之后，此对象可以从启用（1）转换为对等启用（3）。
Note that SACK negotiation is not symmetrical. SACK can
enabled on one side of the connection and not the other."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 9 }
Note that SACK negotiation is not symmetrical. SACK can
enabled on one side of the connection and not the other."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 9 }
--
-- The following two objects reflect the current state of the
-- connection.
--
--
-- The following two objects reflect the current state of the
-- connection.
--
tcpEStatsStackState OBJECT-TYPE
SYNTAX 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)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An integer value representing the connection state from the
TCP State Transition Diagram.
tcpEStatsStackState OBJECT-TYPE
SYNTAX 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)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
包含值listen（2）只是为了与旧的tcpConnTable并行，不应使用，因为中的侦听状态由tcpListenerTable管理。
The value DeleteTcb(12) is included only for parallelism to the tcpConnTable mechanism for terminating connections,
DeleteTcb（12）值仅用于与用于终止连接的TCPConTable机制的并行性，
although this table does not permit writing."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 10 }
although this table does not permit writing."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 10 }
tcpEStatsStackNagle OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"True(1) if the Nagle algorithm is being used, else
false(2)."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 11 }
tcpEStatsStackNagle OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"True(1) if the Nagle algorithm is being used, else
false(2)."
REFERENCE
"RFC 1122, Requirements for Internet Hosts - Communication
Layers"
::= { tcpEStatsStackEntry 11 }
--
-- The following objects instrument the overall operation of
-- TCP congestion control and data retransmissions. These
-- instruments are sufficient to fit the actual performance to
-- an updated macroscopic performance model [RFC2581] [Mat97]
-- [Pad98].
--
--
-- The following objects instrument the overall operation of
-- TCP congestion control and data retransmissions. These
-- instruments are sufficient to fit the actual performance to
-- an updated macroscopic performance model [RFC2581] [Mat97]
-- [Pad98].
--
tcpEStatsStackMaxSsCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum congestion window used during Slow Start, in
octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 12 }
tcpEStatsStackMaxSsCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum congestion window used during Slow Start, in
octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 12 }
tcpEStatsStackMaxCaCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum congestion window used during Congestion
Avoidance, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 13 }
tcpEStatsStackMaxCaCwnd OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum congestion window used during Congestion
Avoidance, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 13 }
tcpEStatsStackMaxSsthresh OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum slow start threshold, excluding the initial
value."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 14 }
tcpEStatsStackMaxSsthresh OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum slow start threshold, excluding the initial
value."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 14 }
tcpEStatsStackMinSsthresh OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum slow start threshold."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 15 }
tcpEStatsStackMinSsthresh OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum slow start threshold."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 15 }
tcpEStatsStackInRecovery OBJECT-TYPE
SYNTAX INTEGER {
tcpESDataContiguous(1),
tcpESDataUnordered(2),
tcpESDataRecovery(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An integer value representing the state of the loss
recovery for this connection.
tcpEStatsStackInRecovery OBJECT-TYPE
SYNTAX INTEGER {
tcpESDataContiguous(1),
tcpESDataUnordered(2),
tcpESDataRecovery(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
TCPESDataContinental（1）表示远程接收器正在报告连续数据（没有重复确认或SACK选项），并且没有未确认的重新传输。
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).
tcpESDataUnordered（2）表示远程接收器正在报告丢失或无序数据（例如，发送重复确认或SACK选项），并且没有未确认的重新传输（因为丢失的数据尚未重新传输）。
tcpESDataRecovery(3) indicates that the sender has outstanding retransmitted data that is still
tcpESDataRecovery（3）表示发送方有未完成的重新传输的数据，该数据仍在传输中
unacknowledged."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 16 }
unacknowledged."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 16 }
tcpEStatsStackDupAcksIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate ACKs received."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 17 }
tcpEStatsStackDupAcksIn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate ACKs received."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 17 }
tcpEStatsStackSpuriousFrDetected OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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).'"
REFERENCE
"RFC 3522, The Eifel Detection Algorithm for TCP"
::= { tcpEStatsStackEntry 18 }
tcpEStatsStackSpuriousFrDetected OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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).'"
REFERENCE
"RFC 3522, The Eifel Detection Algorithm for TCP"
::= { tcpEStatsStackEntry 18 }
tcpEStatsStackSpuriousRtoDetected OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of acknowledgments reporting segments that have
already been retransmitted due to a Retransmission Timeout."
::= { tcpEStatsStackEntry 19 }
tcpEStatsStackSpuriousRtoDetected OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of acknowledgments reporting segments that have
already been retransmitted due to a Retransmission Timeout."
::= { tcpEStatsStackEntry 19 }
--
-- The following optional objects instrument unusual protocol
-- events that probably indicate implementation problems in
-- the protocol or path.
--
--
-- The following optional objects instrument unusual protocol
-- events that probably indicate implementation problems in
-- the protocol or path.
--
tcpEStatsStackSoftErrors OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsStackSoftErrors对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 21 }
tcpEStatsStackSoftErrorReason OBJECT-TYPE
SYNTAX INTEGER {
belowDataWindow(1),
aboveDataWindow(2),
belowAckWindow(3),
aboveAckWindow(4),
belowTSWindow(5),
aboveTSWindow(6),
dataCheckSum(7),
otherSoftError(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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:
tcpEStatsStackSoftErrorReason OBJECT-TYPE
SYNTAX INTEGER {
belowDataWindow(1),
aboveDataWindow(2),
belowAckWindow(3),
aboveAckWindow(4),
belowTSWindow(5),
aboveTSWindow(6),
dataCheckSum(7),
otherSoftError(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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).
低于数据窗口（1）-段中的所有数据低于SND.UNA。（保持有效和零窗探头正常）。
aboveDataWindow(2) - Some data in the segment is above SND.WND. (Indicates an implementation bug or possible attack).
UpperDataWindow（2）-段中的某些数据高于SND.WND。（表示存在实施缺陷或可能的攻击）。
belowAckWindow(3) - ACK below SND.UNA. (Indicates that the return path is reordering ACKs)
下方古怪窗口（3）-SND.UNA下方确认。（指示返回路径是重新排序确认）
aboveAckWindow(4) - An ACK for data that we have not sent. (Indicates an implementation bug or possible attack).
以上确认窗口（4）-我们尚未发送的数据的确认。（表示存在实施缺陷或可能的攻击）。
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).
belowTSWindow（5）-段上的TSecr早于当前TS。NEXT（PAWS检测到网络重新排序的数据的罕见情况下正常）。
aboveTSWindow(6) - TSecr on the segment is newer than the current TS.Recent. (Indicates an implementation bug or possible attack).
上TSWindow（6）-段上的TSecr比当前TS.Recent更新。（表示存在实施缺陷或可能的攻击）。
dataCheckSum(7) - Incorrect checksum. Note that this value is intrinsically fragile, because the header fields used to identify the connection may have been corrupted.
数据校验和（7）-校验和不正确。请注意，此值本质上是脆弱的，因为用于标识连接的标头字段可能已损坏。
otherSoftError(8) - All other soft errors not listed
above."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 22 }
otherSoftError(8) - All other soft errors not listed
above."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 22 }
--
-- The following optional objects expose the detailed
-- operation of the congestion control algorithms.
--
--
-- The following optional objects expose the detailed
-- operation of the congestion control algorithms.
--
tcpEStatsStackSlowStart OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the congestion window has been
increased by the Slow Start algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 23 }
tcpEStatsStackSlowStart OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the congestion window has been
increased by the Slow Start algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 23 }
tcpEStatsStackCongAvoid OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the congestion window has been
increased by the Congestion Avoidance algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 24 }
tcpEStatsStackCongAvoid OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the congestion window has been
increased by the Congestion Avoidance algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 24 }
tcpEStatsStackOtherReductions OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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].
TcpestatsStackOtherReduces对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“由于AIMD拥塞控制算法以外的任何算法而减少的拥塞窗口数量。非乘法窗口减少的示例包括拥塞窗口验证[RFC2861]以及Vegas等实验算法[Bra94]。
All window reductions MUST be counted as either
tcpEStatsPerfCongSignals or tcpEStatsStackOtherReductions."
REFERENCE
"RFC 2861, TCP Congestion Window Validation"
::= { tcpEStatsStackEntry 25 }
All window reductions MUST be counted as either
tcpEStatsPerfCongSignals or tcpEStatsStackOtherReductions."
REFERENCE
"RFC 2861, TCP Congestion Window Validation"
::= { tcpEStatsStackEntry 25 }
tcpEStatsStackCongOverCount OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
TCPESTATSSTACKCONOVERCOUNT对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“从拥塞控制状态机中“退出”以使拥塞窗口恢复到先前值的拥塞事件数。这可能是由于Eifel算法[RFC3522]造成的或其他可用于检测和取消快速重传算法的虚假调用的算法。
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."
REFERENCE
"RFC 3522, The Eifel Detection Algorithm for TCP"
::= { tcpEStatsStackEntry 26 }
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."
REFERENCE
"RFC 3522, The Eifel Detection Algorithm for TCP"
::= { tcpEStatsStackEntry 26 }
tcpEStatsStackFastRetran OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of invocations of the Fast Retransmit algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 27 }
tcpEStatsStackFastRetran OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of invocations of the Fast Retransmit algorithm."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 27 }
tcpEStatsStackSubsequentTimeouts OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the retransmit timeout has expired after
the RTO has been doubled. See Section 5.5 of RFC 2988."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsStackEntry 28 }
tcpEStatsStackSubsequentTimeouts OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the retransmit timeout has expired after
the RTO has been doubled. See Section 5.5 of RFC 2988."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsStackEntry 28 }
tcpEStatsStackCurTimeoutCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsStackEntry 29 }
tcpEStatsStackCurTimeoutCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 2988, Computing TCP's Retransmission Timer"
::= { tcpEStatsStackEntry 29 }
tcpEStatsStackAbruptTimeouts OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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.
tcpEStatsStackAbruptTimeouts对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“在没有任何重复确认或其他拥塞指示的情况下发生的超时数。突然超时表示路径丢失了整个数据或确认窗口。
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 30 }
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."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsStackEntry 30 }
tcpEStatsStackSACKsRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of SACK options received."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 31 }
tcpEStatsStackSACKsRcvd OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of SACK options received."
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 31 }
tcpEStatsStackSACKBlocksRcvd OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SACK blocks received (within SACK options)."
tcpEStatsStackSACKBlocksRcvd对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前说明“接收的SACK块数（在SACK选项内）”
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 32 }
REFERENCE
"RFC 2018, TCP Selective Acknowledgement Options"
::= { tcpEStatsStackEntry 32 }
tcpEStatsStackSendStall OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of interface stalls or other sender local
resource limitations that are treated as congestion
signals."
::= { tcpEStatsStackEntry 33 }
tcpEStatsStackSendStall OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of interface stalls or other sender local
resource limitations that are treated as congestion
signals."
::= { tcpEStatsStackEntry 33 }
tcpEStatsStackDSACKDups OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate segments reported to the local host
by D-SACK blocks."
REFERENCE
"RFC 2883, An Extension to the Selective Acknowledgement
(SACK) Option for TCP"
::= { tcpEStatsStackEntry 34 }
tcpEStatsStackDSACKDups OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate segments reported to the local host
by D-SACK blocks."
REFERENCE
"RFC 2883, An Extension to the Selective Acknowledgement
(SACK) Option for TCP"
::= { tcpEStatsStackEntry 34 }
--
-- The following optional objects instrument path MTU
-- discovery.
--
--
-- The following optional objects instrument path MTU
-- discovery.
--
tcpEStatsStackMaxMSS OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum MSS, in octets."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsStackEntry 35 }
tcpEStatsStackMaxMSS OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum MSS, in octets."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsStackEntry 35 }
tcpEStatsStackMinMSS OBJECT-TYPE SYNTAX Gauge32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsStackMinMSS对象类型语法量表32单位“八位字节”最大访问只读状态当前说明
"The minimum MSS, in octets."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsStackEntry 36 }
"The minimum MSS, in octets."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsStackEntry 36 }
--
-- The following optional initial value objects are useful for
-- conformance testing instruments on application progress and
-- consumed network resources.
--
--
-- The following optional initial value objects are useful for
-- conformance testing instruments on application progress and
-- consumed network resources.
--
tcpEStatsStackSndInitial OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Initial send sequence number. Note that by definition
tcpEStatsStackSndInitial never changes for a given
connection."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 37 }
tcpEStatsStackSndInitial OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Initial send sequence number. Note that by definition
tcpEStatsStackSndInitial never changes for a given
connection."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 37 }
tcpEStatsStackRecInitial OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Initial receive sequence number. Note that by definition
tcpEStatsStackRecInitial never changes for a given
connection."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 38 }
tcpEStatsStackRecInitial OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Initial receive sequence number. Note that by definition
tcpEStatsStackRecInitial never changes for a given
connection."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsStackEntry 38 }
--
-- The following optional objects instrument the senders
-- buffer usage, including any buffering in the application
-- interface to TCP and the retransmit queue. All 'buffer
-- memory' instruments are assumed to include OS data
-- structure overhead.
--
--
-- The following optional objects instrument the senders
-- buffer usage, including any buffering in the application
-- interface to TCP and the retransmit queue. All 'buffer
-- memory' instruments are assumed to include OS data
-- structure overhead.
--
tcpEStatsStackCurRetxQueue OBJECT-TYPE SYNTAX Gauge32 UNITS "octets" MAX-ACCESS read-only STATUS current
tcpEStatsStackCurRetxQueue对象类型语法量表32单位“八位字节”最大访问只读状态当前
DESCRIPTION
"The current number of octets of data occupying the
retransmit queue."
::= { tcpEStatsStackEntry 39 }
DESCRIPTION
"The current number of octets of data occupying the
retransmit queue."
::= { tcpEStatsStackEntry 39 }
tcpEStatsStackMaxRetxQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of octets of data occupying the
retransmit queue."
::= { tcpEStatsStackEntry 40 }
tcpEStatsStackMaxRetxQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of octets of data occupying the
retransmit queue."
::= { tcpEStatsStackEntry 40 }
tcpEStatsStackCurReasmQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsStackEntry 41 }
tcpEStatsStackCurReasmQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsStackEntry 41 }
tcpEStatsStackMaxReasmQueue OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of tcpEStatsStackCurReasmQueue"
::= { tcpEStatsStackEntry 42 }
tcpEStatsStackMaxReasmQueue OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of tcpEStatsStackCurReasmQueue"
::= { tcpEStatsStackEntry 42 }
-- ================================================================
--
-- Statistics for diagnosing interactions between
-- applications and TCP.
--
-- ================================================================
--
-- Statistics for diagnosing interactions between
-- applications and TCP.
--
tcpEStatsAppTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsAppEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains objects that are useful for determining if the application using TCP is
tcpEStatsAppTable对象类型TcpEStatsAppEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表包含用于确定使用TCP的应用程序是否可用的对象
limiting TCP performance.
限制TCP性能。
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."
::= { tcpEStats 6 }
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."
::= { tcpEStats 6 }
tcpEStatsAppEntry OBJECT-TYPE
SYNTAX TcpEStatsAppEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsAppTable 1 }
tcpEStatsAppEntry OBJECT-TYPE
SYNTAX TcpEStatsAppEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table has information about the
characteristics of each active and recently closed TCP
connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsAppTable 1 }
TcpEStatsAppEntry ::= SEQUENCE {
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 }
TCPESTATSAPSNDUNA计数器32、TCPESTATSAPSNDXT UNSIGNED 32、TCPESTATSAPSNDMAX计数器32、TCPESTATSAPSTHRUOCTETSACKED零基计数器32、tcpEStatsAppHCThruOctetsAcked零基计数器64、TCPESTATSAPPRCVNNXT计数器32、TCPESTATATSAPPTHRUOCTETSRECEIVED零基计数器32、TCPESTATSAPPHCTHRUOCTES零基计数器64、，TcpestatSappCuraPwQueue Gauge32、tcpEStatsAppMaxAppWQueue Gauge32、TcpestatSappCuraPwQueue Gauge32、tcpEStatsAppMaxAppRQueue Gauge32}
--
-- The following objects provide throughput statistics for the
-- connection including sequence numbers and elapsed
-- application data. These permit direct observation of the
-- applications progress, in terms of elapsed data delivery
-- and elapsed time.
--
--
-- The following objects provide throughput statistics for the
-- connection including sequence numbers and elapsed
-- application data. These permit direct observation of the
-- applications progress, in terms of elapsed data delivery
-- and elapsed time.
--
tcpEStatsAppSndUna OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION
TCPESTATSAPSNDUNA对象类型语法计数器32 MAX-ACCESS只读状态当前说明
"The value of SND.UNA, the oldest unacknowledged sequence number.
SND.UNA的值，最早的未确认序列号。
Note that SND.UNA is a TCP state variable that is congruent
to Counter32 semantics."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 1 }
Note that SND.UNA is a TCP state variable that is congruent
to Counter32 semantics."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 1 }
tcpEStatsAppSndNxt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 2 }
tcpEStatsAppSndNxt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 2 }
tcpEStatsAppSndMax OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 3 }
tcpEStatsAppSndMax OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 3 }
tcpEStatsAppThruOctetsAcked OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets for which cumulative acknowledgments
have been received. Note that this will be the sum of
changes to tcpEStatsAppSndUna."
::= { tcpEStatsAppEntry 4 }
tcpEStatsAppThruOctetsAcked OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets for which cumulative acknowledgments
have been received. Note that this will be the sum of
changes to tcpEStatsAppSndUna."
::= { tcpEStatsAppEntry 4 }
tcpEStatsAppHCThruOctetsAcked OBJECT-TYPE SYNTAX ZeroBasedCounter64 UNITS "octets"
tcpEStatsAppHCThruOctetsAcked对象类型语法ZeroBasedCounter64单位“八位字节”
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 5 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 5 }
tcpEStatsAppRcvNxt OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of RCV.NXT. The next sequence number expected on an incoming segment, and the left or lower edge of the receive window.
tcpEStatsAppRcvNxt对象类型语法计数器32 MAX-ACCESS只读状态当前描述“RCV.NXT的值。传入段上预期的下一个序列号，以及接收窗口的左边缘或下边缘。
Note that RCV.NXT is a TCP state variable that is congruent
to Counter32 semantics."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 6 }
Note that RCV.NXT is a TCP state variable that is congruent
to Counter32 semantics."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsAppEntry 6 }
tcpEStatsAppThruOctetsReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets for which cumulative acknowledgments
have been sent. Note that this will be the sum of changes
to tcpEStatsAppRcvNxt."
::= { tcpEStatsAppEntry 7 }
tcpEStatsAppThruOctetsReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets for which cumulative acknowledgments
have been sent. Note that this will be the sum of changes
to tcpEStatsAppRcvNxt."
::= { tcpEStatsAppEntry 7 }
tcpEStatsAppHCThruOctetsReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 8 }
tcpEStatsAppHCThruOctetsReceived OBJECT-TYPE
SYNTAX ZeroBasedCounter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 8 }
tcpEStatsAppCurAppWQueue OBJECT-TYPE
TCPESTATSAPPURAPPWQUEUE对象类型
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 11 }
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
::= { tcpEStatsAppEntry 11 }
tcpEStatsAppMaxAppWQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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)."
::= { tcpEStatsAppEntry 12 }
tcpEStatsAppMaxAppWQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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)."
::= { tcpEStatsAppEntry 12 }
tcpEStatsAppCurAppRQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of octets of application data that has
been acknowledged by TCP but not yet delivered to the
application."
::= { tcpEStatsAppEntry 13 }
tcpEStatsAppCurAppRQueue OBJECT-TYPE
SYNTAX Gauge32
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of octets of application data that has
been acknowledged by TCP but not yet delivered to the
application."
::= { tcpEStatsAppEntry 13 }
tcpEStatsAppMaxAppRQueue OBJECT-TYPE SYNTAX Gauge32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION
tcpEStatsAppMaxAppRQueue对象类型语法量表32单位“八位字节”最大访问只读状态当前说明
"The maximum number of octets of application data that has
been acknowledged by TCP but not yet delivered to the
application."
::= { tcpEStatsAppEntry 14 }
"The maximum number of octets of application data that has
been acknowledged by TCP but not yet delivered to the
application."
::= { tcpEStatsAppEntry 14 }
-- ================================================================
--
-- Controls for Tuning TCP
--
-- ================================================================
--
-- Controls for Tuning TCP
--
tcpEStatsTuneTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpEStatsTuneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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.
TcpestatStuteEntry MAX-ACCESS的TcpestatStuteTable对象类型语法序列不可访问状态当前描述“此表包含每个连接的控件，可用于解决某些路径上困扰TCP的一些常见问题。所有这些都可以被描述为限制拥塞窗口的增长，以防止TCP覆盖路径中的某些组件。
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."
::= { tcpEStats 7 }
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."
::= { tcpEStats 7 }
tcpEStatsTuneEntry OBJECT-TYPE
SYNTAX TcpEStatsTuneEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table is a control that can be used to
place limits on each active TCP connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsTuneTable 1 }
tcpEStatsTuneEntry OBJECT-TYPE
SYNTAX TcpEStatsTuneEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table is a control that can be used to
place limits on each active TCP connection."
INDEX { tcpEStatsConnectIndex }
::= { tcpEStatsTuneTable 1 }
TcpEStatsTuneEntry ::= SEQUENCE {
TcpEStatsTuneEntry ::= SEQUENCE {
tcpEStatsTuneLimCwnd Unsigned32, tcpEStatsTuneLimSsthresh Unsigned32, tcpEStatsTuneLimRwin Unsigned32, tcpEStatsTuneLimMSS Unsigned32 }
tcpEStatsTuneLimCwnd Unsigned32，TcpestatStunelimsThresh Unsigned32，TcpestatStunelimsWin Unsigned32，tcpEStatsTuneLimMSS Unsigned32}
tcpEStatsTuneLimCwnd OBJECT-TYPE SYNTAX Unsigned32
tcpEStatsTuneLimCwnd对象类型语法Unsigned32
UNITS "octets"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A control to set the maximum congestion window that may be
used, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsTuneEntry 1 }
UNITS "octets"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A control to set the maximum congestion window that may be
used, in octets."
REFERENCE
"RFC 2581, TCP Congestion Control"
::= { tcpEStatsTuneEntry 1 }
tcpEStatsTuneLimSsthresh OBJECT-TYPE SYNTAX Unsigned32 UNITS "octets" MAX-ACCESS read-write STATUS current DESCRIPTION "A control to limit the maximum queue space (in octets) that this TCP connection is likely to occupy during slowstart.
TCPESTATSTUNELIMSSTRESH对象类型语法Unsigned32单元“八位字节”MAX-ACCESS读写状态当前描述“限制此TCP连接在slowstart期间可能占用的最大队列空间（八位字节）的控件。
It can be implemented with the algorithm described in RFC 3742 by setting the max_ssthresh parameter to twice tcpEStatsTuneLimSsthresh.
通过将max_ssthresh参数设置为tcpEStatsTuneLimSsthresh的两倍，可以使用RFC 3742中描述的算法实现。
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."
REFERENCE
"RFC 3742, Limited Slow-Start for TCP with Large Congestion
Windows"
::= { tcpEStatsTuneEntry 2 }
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."
REFERENCE
"RFC 3742, Limited Slow-Start for TCP with Large Congestion
Windows"
::= { tcpEStatsTuneEntry 2 }
tcpEStatsTuneLimRwin OBJECT-TYPE
SYNTAX Unsigned32
UNITS "octets"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A control to set the maximum window advertisement that may
be sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsTuneEntry 3 }
tcpEStatsTuneLimRwin OBJECT-TYPE
SYNTAX Unsigned32
UNITS "octets"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A control to set the maximum window advertisement that may
be sent, in octets."
REFERENCE
"RFC 793, Transmission Control Protocol"
::= { tcpEStatsTuneEntry 3 }
tcpEStatsTuneLimMSS OBJECT-TYPE SYNTAX Unsigned32 UNITS "octets" MAX-ACCESS read-write
tcpEStatsTuneLimMSS对象类型语法无符号32个单位“八位字节”最大访问读写
STATUS current
DESCRIPTION
"A control to limit the maximum segment size in octets, that
this TCP connection can use."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsTuneEntry 4 }
STATUS current
DESCRIPTION
"A control to limit the maximum segment size in octets, that
this TCP connection can use."
REFERENCE
"RFC 1191, Path MTU discovery"
::= { tcpEStatsTuneEntry 4 }
-- ================================================================
--
-- TCP Extended Statistics Notifications Group
--
-- ================================================================
--
-- TCP Extended Statistics Notifications Group
--
tcpEStatsEstablishNotification NOTIFICATION-TYPE
OBJECTS {
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The indicated connection has been accepted
(or alternatively entered the established state)."
::= { tcpEStatsNotifications 1 }
tcpEStatsEstablishNotification NOTIFICATION-TYPE
OBJECTS {
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The indicated connection has been accepted
(or alternatively entered the established state)."
::= { tcpEStatsNotifications 1 }
tcpEStatsCloseNotification NOTIFICATION-TYPE
OBJECTS {
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The indicated connection has left the
established state"
::= { tcpEStatsNotifications 2 }
tcpEStatsCloseNotification NOTIFICATION-TYPE
OBJECTS {
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The indicated connection has left the
established state"
::= { tcpEStatsNotifications 2 }
-- ================================================================
--
-- Conformance Definitions
--
-- ================================================================
--
-- Conformance Definitions
--
tcpEStatsCompliances OBJECT IDENTIFIER
::= { tcpEStatsConformance 1 }
tcpEStatsGroups OBJECT IDENTIFIER
::= { tcpEStatsConformance 2 }
tcpEStatsCompliances OBJECT IDENTIFIER
::= { tcpEStatsConformance 1 }
tcpEStatsGroups OBJECT IDENTIFIER
::= { tcpEStatsConformance 2 }
-- -- Compliance Statements --
----合规声明--
tcpEStatsCompliance MODULE-COMPLIANCE
tcpEStatsCompliance模块-合规性
STATUS current
DESCRIPTION
"Compliance statement for all systems that implement TCP
extended statistics."
MODULE -- this module
MANDATORY-GROUPS {
tcpEStatsListenerGroup,
tcpEStatsConnectIdGroup,
tcpEStatsPerfGroup,
tcpEStatsPathGroup,
tcpEStatsStackGroup,
tcpEStatsAppGroup
}
GROUP tcpEStatsListenerHCGroup
DESCRIPTION
"This group is mandatory for all systems that can
wrap the values of the 32-bit counters in
tcpEStatsListenerGroup in less than one hour."
STATUS current
DESCRIPTION
"Compliance statement for all systems that implement TCP
extended statistics."
MODULE -- this module
MANDATORY-GROUPS {
tcpEStatsListenerGroup,
tcpEStatsConnectIdGroup,
tcpEStatsPerfGroup,
tcpEStatsPathGroup,
tcpEStatsStackGroup,
tcpEStatsAppGroup
}
GROUP tcpEStatsListenerHCGroup
DESCRIPTION
"This group is mandatory for all systems that can
wrap the values of the 32-bit counters in
tcpEStatsListenerGroup in less than one hour."
GROUP tcpEStatsPerfOptionalGroup DESCRIPTION "This group is optional for all systems."
组tcpEStatsPerfOptionalGroup DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsPerfHCGroup DESCRIPTION "This group is mandatory for systems that can wrap the values of the 32-bit counters in tcpEStatsPerfGroup in less than one hour.
对于组PestCfRf32，该组PestCfRfRfRf32计数器中的SpetCfRfAt值必须小于组PestCfRfRf32。
Note that any system that can attain 10 Mb/s can potentially wrap 32-Bit Octet counters in under one hour."
请注意，任何可以达到10 Mb/s的系统都可能在一小时内包装32位八位字节计数器。”
GROUP tcpEStatsPathOptionalGroup DESCRIPTION "This group is optional for all systems."
组tcpEStatsPathOptionalGroup DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsPathHCGroup DESCRIPTION "This group is mandatory for systems that can wrap the values of the 32-bit counters in tcpEStatsPathGroup in less than one hour.
组TCPESTATSPATHCGROUP DESCRIPTION“对于可以在一小时内包装tcpEStatsPathGroup中32位计数器值的系统，此组是必需的。
Note that any system that can attain 10 Mb/s can potentially wrap 32-Bit Octet counters in under one hour."
请注意，任何可以达到10 Mb/s的系统都可能在一小时内包装32位八位字节计数器。”
GROUP tcpEStatsStackOptionalGroup
组TCPESTATSSTACKOPTIONAL组
DESCRIPTION "This group is optional for all systems."
DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsAppHCGroup DESCRIPTION "This group is mandatory for systems that can wrap the values of the 32-bit counters in tcpEStatsStackGroup in less than one hour.
GROUP tcpEStatsAppHCGroup DESCRIPTION“对于可以在不到一小时内包装tcpEStatsStackGroup中32位计数器值的系统，此组是必需的。
Note that any system that can attain 10 Mb/s can potentially wrap 32-Bit Octet counters in under one hour."
请注意，任何可以达到10 Mb/s的系统都可能在一小时内包装32位八位字节计数器。”
GROUP tcpEStatsAppOptionalGroup DESCRIPTION "This group is optional for all systems."
组TCPESTATSAPoptionalGroup DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsTuneOptionalGroup DESCRIPTION "This group is optional for all systems."
GROUP TcpestatStuneOptions GROUP DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsNotificationsGroup DESCRIPTION "This group is optional for all systems."
组tcpEStatsNotificationsGroup DESCRIPTION“此组对于所有系统都是可选的。”
GROUP tcpEStatsNotificationsCtlGroup DESCRIPTION "This group is mandatory for systems that include the tcpEStatsNotificationGroup."
组tcpEStatsNotificationsCtlGroup DESCRIPTION“对于包含tcpEStatsNotificationGroup的系统，此组是必需的。”
::= { tcpEStatsCompliances 1 }
::= { tcpEStatsCompliances 1 }
-- ================================================================
--
-- Units of Conformance
--
tcpEStatsListenerGroup OBJECT-GROUP
OBJECTS {
tcpEStatsListenerTableLastChange,
tcpEStatsListenerStartTime,
tcpEStatsListenerSynRcvd,
tcpEStatsListenerInitial,
tcpEStatsListenerEstablished,
tcpEStatsListenerAccepted,
tcpEStatsListenerExceedBacklog,
tcpEStatsListenerCurConns,
tcpEStatsListenerMaxBacklog,
tcpEStatsListenerCurBacklog,
-- ================================================================
--
-- Units of Conformance
--
tcpEStatsListenerGroup OBJECT-GROUP
OBJECTS {
tcpEStatsListenerTableLastChange,
tcpEStatsListenerStartTime,
tcpEStatsListenerSynRcvd,
tcpEStatsListenerInitial,
tcpEStatsListenerEstablished,
tcpEStatsListenerAccepted,
tcpEStatsListenerExceedBacklog,
tcpEStatsListenerCurConns,
tcpEStatsListenerMaxBacklog,
tcpEStatsListenerCurBacklog,
tcpEStatsListenerCurEstabBacklog
}
STATUS current
DESCRIPTION
"The tcpEStatsListener group includes objects that
provide valuable statistics and debugging
information for TCP Listeners."
::= { tcpEStatsGroups 1 }
tcpEStatsListenerCurEstabBacklog
}
STATUS current
DESCRIPTION
"The tcpEStatsListener group includes objects that
provide valuable statistics and debugging
information for TCP Listeners."
::= { tcpEStatsGroups 1 }
tcpEStatsListenerHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsListenerHCSynRcvd,
tcpEStatsListenerHCInitial,
tcpEStatsListenerHCEstablished,
tcpEStatsListenerHCAccepted,
tcpEStatsListenerHCExceedBacklog
}
STATUS current
DESCRIPTION
"The tcpEStatsListenerHC group includes 64-bit
counters in tcpEStatsListenerTable."
::= { tcpEStatsGroups 2 }
tcpEStatsListenerHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsListenerHCSynRcvd,
tcpEStatsListenerHCInitial,
tcpEStatsListenerHCEstablished,
tcpEStatsListenerHCAccepted,
tcpEStatsListenerHCExceedBacklog
}
STATUS current
DESCRIPTION
"The tcpEStatsListenerHC group includes 64-bit
counters in tcpEStatsListenerTable."
::= { tcpEStatsGroups 2 }
tcpEStatsConnectIdGroup OBJECT-GROUP
OBJECTS {
tcpEStatsConnTableLatency,
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The tcpEStatsConnectId group includes objects that
identify TCP connections and control how long TCP
connection entries are retained in the tables."
::= { tcpEStatsGroups 3 }
tcpEStatsConnectIdGroup OBJECT-GROUP
OBJECTS {
tcpEStatsConnTableLatency,
tcpEStatsConnectIndex
}
STATUS current
DESCRIPTION
"The tcpEStatsConnectId group includes objects that
identify TCP connections and control how long TCP
connection entries are retained in the tables."
::= { tcpEStatsGroups 3 }
tcpEStatsPerfGroup OBJECT-GROUP OBJECTS { tcpEStatsPerfSegsOut, tcpEStatsPerfDataSegsOut, tcpEStatsPerfDataOctetsOut, tcpEStatsPerfSegsRetrans, tcpEStatsPerfOctetsRetrans, tcpEStatsPerfSegsIn, tcpEStatsPerfDataSegsIn, tcpEStatsPerfDataOctetsIn, tcpEStatsPerfElapsedSecs, tcpEStatsPerfElapsedMicroSecs, tcpEStatsPerfStartTimeStamp, tcpEStatsPerfCurMSS, tcpEStatsPerfPipeSize, tcpEStatsPerfMaxPipeSize, tcpEStatsPerfSmoothedRTT, tcpEStatsPerfCurRTO,
tcpEStatsPerfGroup对象组对象{tcpEStatsPerfSegsOut，tcpEStatsPerfSegsOut，TcpestatsPerfsegsTrans，TcpestatsPerfsegsTrans，tcpEStatsPerfSegsIn，tcpEStatsPerfSegsIn，tcpEStatsPerfDataSegsIn，TcpestatsPerfsecedSecs，tcpEStatsPerfStartTimeStamp，TcpestatsPerfsecurMs，TcpestatsPerfPipesSize，tcpEStatsPerfMaxPipeSize、TCPESTATSPERFSMOOTHDRTT、tcpEStatsPerfCurRTO、，
tcpEStatsPerfCongSignals, tcpEStatsPerfCurCwnd,
tcpEStatsPerfCurSsthresh, tcpEStatsPerfTimeouts,
tcpEStatsPerfCurRwinSent,
tcpEStatsPerfMaxRwinSent,
tcpEStatsPerfZeroRwinSent,
tcpEStatsPerfCurRwinRcvd,
tcpEStatsPerfMaxRwinRcvd,
tcpEStatsPerfZeroRwinRcvd
}
STATUS current
DESCRIPTION
"The tcpEStatsPerf group includes those objects that
provide basic performance data for a TCP connection."
::= { tcpEStatsGroups 4 }
tcpEStatsPerfCongSignals, tcpEStatsPerfCurCwnd,
tcpEStatsPerfCurSsthresh, tcpEStatsPerfTimeouts,
tcpEStatsPerfCurRwinSent,
tcpEStatsPerfMaxRwinSent,
tcpEStatsPerfZeroRwinSent,
tcpEStatsPerfCurRwinRcvd,
tcpEStatsPerfMaxRwinRcvd,
tcpEStatsPerfZeroRwinRcvd
}
STATUS current
DESCRIPTION
"The tcpEStatsPerf group includes those objects that
provide basic performance data for a TCP connection."
::= { tcpEStatsGroups 4 }
tcpEStatsPerfOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPerfSndLimTransRwin,
tcpEStatsPerfSndLimTransCwnd,
tcpEStatsPerfSndLimTransSnd,
tcpEStatsPerfSndLimTimeRwin,
tcpEStatsPerfSndLimTimeCwnd,
tcpEStatsPerfSndLimTimeSnd
}
STATUS current
DESCRIPTION
"The tcpEStatsPerf group includes those objects that
provide basic performance data for a TCP connection."
::= { tcpEStatsGroups 5 }
tcpEStatsPerfOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPerfSndLimTransRwin,
tcpEStatsPerfSndLimTransCwnd,
tcpEStatsPerfSndLimTransSnd,
tcpEStatsPerfSndLimTimeRwin,
tcpEStatsPerfSndLimTimeCwnd,
tcpEStatsPerfSndLimTimeSnd
}
STATUS current
DESCRIPTION
"The tcpEStatsPerf group includes those objects that
provide basic performance data for a TCP connection."
::= { tcpEStatsGroups 5 }
tcpEStatsPerfHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPerfHCDataOctetsOut,
tcpEStatsPerfHCDataOctetsIn
}
STATUS current
DESCRIPTION
"The tcpEStatsPerfHC group includes 64-bit
counters in the tcpEStatsPerfTable."
::= { tcpEStatsGroups 6 }
tcpEStatsPerfHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPerfHCDataOctetsOut,
tcpEStatsPerfHCDataOctetsIn
}
STATUS current
DESCRIPTION
"The tcpEStatsPerfHC group includes 64-bit
counters in the tcpEStatsPerfTable."
::= { tcpEStatsGroups 6 }
tcpEStatsPathGroup OBJECT-GROUP OBJECTS { tcpEStatsControlPath, tcpEStatsPathRetranThresh, tcpEStatsPathNonRecovDAEpisodes, tcpEStatsPathSumOctetsReordered,
tcpEStatsPathGroup对象组对象{tcpEStatsControlPath，tcpEStatsPathRetranThresh，TcpestatsPathNonRecovdaepisedes，TcpestatsPathSumOctets，
tcpEStatsPathNonRecovDA
}
STATUS current
DESCRIPTION
"The tcpEStatsPath group includes objects that
control the creation of the tcpEStatsPathTable,
and provide information about the path
for each TCP connection."
::= { tcpEStatsGroups 7 }
tcpEStatsPathNonRecovDA
}
STATUS current
DESCRIPTION
"The tcpEStatsPath group includes objects that
control the creation of the tcpEStatsPathTable,
and provide information about the path
for each TCP connection."
::= { tcpEStatsGroups 7 }
tcpEStatsPathOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPathSampleRTT, tcpEStatsPathRTTVar,
tcpEStatsPathMaxRTT, tcpEStatsPathMinRTT,
tcpEStatsPathSumRTT, tcpEStatsPathCountRTT,
tcpEStatsPathMaxRTO, tcpEStatsPathMinRTO,
tcpEStatsPathIpTtl, tcpEStatsPathIpTosIn,
tcpEStatsPathIpTosOut,
tcpEStatsPathPreCongSumCwnd,
tcpEStatsPathPreCongSumRTT,
tcpEStatsPathPostCongSumRTT,
tcpEStatsPathPostCongCountRTT,
tcpEStatsPathECNsignals,
tcpEStatsPathDupAckEpisodes, tcpEStatsPathRcvRTT,
tcpEStatsPathDupAcksOut, tcpEStatsPathCERcvd,
tcpEStatsPathECESent
}
STATUS current
DESCRIPTION
"The tcpEStatsPath group includes objects that
provide additional information about the path
for each TCP connection."
::= { tcpEStatsGroups 8 }
tcpEStatsPathOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPathSampleRTT, tcpEStatsPathRTTVar,
tcpEStatsPathMaxRTT, tcpEStatsPathMinRTT,
tcpEStatsPathSumRTT, tcpEStatsPathCountRTT,
tcpEStatsPathMaxRTO, tcpEStatsPathMinRTO,
tcpEStatsPathIpTtl, tcpEStatsPathIpTosIn,
tcpEStatsPathIpTosOut,
tcpEStatsPathPreCongSumCwnd,
tcpEStatsPathPreCongSumRTT,
tcpEStatsPathPostCongSumRTT,
tcpEStatsPathPostCongCountRTT,
tcpEStatsPathECNsignals,
tcpEStatsPathDupAckEpisodes, tcpEStatsPathRcvRTT,
tcpEStatsPathDupAcksOut, tcpEStatsPathCERcvd,
tcpEStatsPathECESent
}
STATUS current
DESCRIPTION
"The tcpEStatsPath group includes objects that
provide additional information about the path
for each TCP connection."
::= { tcpEStatsGroups 8 }
tcpEStatsPathHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPathHCSumRTT
}
STATUS current
DESCRIPTION
"The tcpEStatsPathHC group includes 64-bit
counters in the tcpEStatsPathTable."
::= { tcpEStatsGroups 9 }
tcpEStatsPathHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsPathHCSumRTT
}
STATUS current
DESCRIPTION
"The tcpEStatsPathHC group includes 64-bit
counters in the tcpEStatsPathTable."
::= { tcpEStatsGroups 9 }
tcpEStatsStackGroup OBJECT-GROUP OBJECTS { tcpEStatsControlStack, tcpEStatsStackActiveOpen, tcpEStatsStackMSSSent,
tcpEStatsStackGroup对象组对象{tcpEStatsControlStack，tcpEStatsStackActiveOpen，TCPESTATSSTACKMSSENT，
tcpEStatsStackMSSRcvd, tcpEStatsStackWinScaleSent,
tcpEStatsStackWinScaleRcvd,
tcpEStatsStackTimeStamps, tcpEStatsStackECN,
tcpEStatsStackWillSendSACK,
tcpEStatsStackWillUseSACK, tcpEStatsStackState,
tcpEStatsStackNagle, tcpEStatsStackMaxSsCwnd,
tcpEStatsStackMaxCaCwnd,
tcpEStatsStackMaxSsthresh,
tcpEStatsStackMinSsthresh,
tcpEStatsStackInRecovery, tcpEStatsStackDupAcksIn,
tcpEStatsStackSpuriousFrDetected,
tcpEStatsStackSpuriousRtoDetected
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsStackTable,
and provide information about the operation of
algorithms used within TCP."
::= { tcpEStatsGroups 10 }
tcpEStatsStackMSSRcvd, tcpEStatsStackWinScaleSent,
tcpEStatsStackWinScaleRcvd,
tcpEStatsStackTimeStamps, tcpEStatsStackECN,
tcpEStatsStackWillSendSACK,
tcpEStatsStackWillUseSACK, tcpEStatsStackState,
tcpEStatsStackNagle, tcpEStatsStackMaxSsCwnd,
tcpEStatsStackMaxCaCwnd,
tcpEStatsStackMaxSsthresh,
tcpEStatsStackMinSsthresh,
tcpEStatsStackInRecovery, tcpEStatsStackDupAcksIn,
tcpEStatsStackSpuriousFrDetected,
tcpEStatsStackSpuriousRtoDetected
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsStackTable,
and provide information about the operation of
algorithms used within TCP."
::= { tcpEStatsGroups 10 }
tcpEStatsStackOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsStackSoftErrors,
tcpEStatsStackSoftErrorReason,
tcpEStatsStackSlowStart, tcpEStatsStackCongAvoid,
tcpEStatsStackOtherReductions,
tcpEStatsStackCongOverCount,
tcpEStatsStackFastRetran,
tcpEStatsStackSubsequentTimeouts,
tcpEStatsStackCurTimeoutCount,
tcpEStatsStackAbruptTimeouts,
tcpEStatsStackSACKsRcvd,
tcpEStatsStackSACKBlocksRcvd,
tcpEStatsStackSendStall, tcpEStatsStackDSACKDups,
tcpEStatsStackMaxMSS, tcpEStatsStackMinMSS,
tcpEStatsStackSndInitial,
tcpEStatsStackRecInitial,
tcpEStatsStackCurRetxQueue,
tcpEStatsStackMaxRetxQueue,
tcpEStatsStackCurReasmQueue,
tcpEStatsStackMaxReasmQueue
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
provide additional information about the operation of
algorithms used within TCP."
tcpEStatsStackOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsStackSoftErrors,
tcpEStatsStackSoftErrorReason,
tcpEStatsStackSlowStart, tcpEStatsStackCongAvoid,
tcpEStatsStackOtherReductions,
tcpEStatsStackCongOverCount,
tcpEStatsStackFastRetran,
tcpEStatsStackSubsequentTimeouts,
tcpEStatsStackCurTimeoutCount,
tcpEStatsStackAbruptTimeouts,
tcpEStatsStackSACKsRcvd,
tcpEStatsStackSACKBlocksRcvd,
tcpEStatsStackSendStall, tcpEStatsStackDSACKDups,
tcpEStatsStackMaxMSS, tcpEStatsStackMinMSS,
tcpEStatsStackSndInitial,
tcpEStatsStackRecInitial,
tcpEStatsStackCurRetxQueue,
tcpEStatsStackMaxRetxQueue,
tcpEStatsStackCurReasmQueue,
tcpEStatsStackMaxReasmQueue
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
provide additional information about the operation of
algorithms used within TCP."
::= { tcpEStatsGroups 11 }
::= { tcpEStatsGroups 11 }
tcpEStatsAppGroup OBJECT-GROUP
OBJECTS {
tcpEStatsControlApp,
tcpEStatsAppSndUna, tcpEStatsAppSndNxt,
tcpEStatsAppSndMax, tcpEStatsAppThruOctetsAcked,
tcpEStatsAppRcvNxt,
tcpEStatsAppThruOctetsReceived
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsAppTable,
and provide information about the operation of
algorithms used within TCP."
::= { tcpEStatsGroups 12 }
tcpEStatsAppGroup OBJECT-GROUP
OBJECTS {
tcpEStatsControlApp,
tcpEStatsAppSndUna, tcpEStatsAppSndNxt,
tcpEStatsAppSndMax, tcpEStatsAppThruOctetsAcked,
tcpEStatsAppRcvNxt,
tcpEStatsAppThruOctetsReceived
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsAppTable,
and provide information about the operation of
algorithms used within TCP."
::= { tcpEStatsGroups 12 }
tcpEStatsAppHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsAppHCThruOctetsAcked,
tcpEStatsAppHCThruOctetsReceived
}
STATUS current
DESCRIPTION
"The tcpEStatsStackHC group includes 64-bit
counters in the tcpEStatsStackTable."
::= { tcpEStatsGroups 13 }
tcpEStatsAppHCGroup OBJECT-GROUP
OBJECTS {
tcpEStatsAppHCThruOctetsAcked,
tcpEStatsAppHCThruOctetsReceived
}
STATUS current
DESCRIPTION
"The tcpEStatsStackHC group includes 64-bit
counters in the tcpEStatsStackTable."
::= { tcpEStatsGroups 13 }
tcpEStatsAppOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsAppCurAppWQueue,
tcpEStatsAppMaxAppWQueue,
tcpEStatsAppCurAppRQueue,
tcpEStatsAppMaxAppRQueue
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
provide additional information about how applications
are interacting with each TCP connection."
::= { tcpEStatsGroups 14 }
tcpEStatsAppOptionalGroup OBJECT-GROUP
OBJECTS {
tcpEStatsAppCurAppWQueue,
tcpEStatsAppMaxAppWQueue,
tcpEStatsAppCurAppRQueue,
tcpEStatsAppMaxAppRQueue
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
provide additional information about how applications
are interacting with each TCP connection."
::= { tcpEStatsGroups 14 }
tcpEStatsTuneOptionalGroup OBJECT-GROUP OBJECTS { tcpEStatsControlTune, tcpEStatsTuneLimCwnd, tcpEStatsTuneLimSsthresh, tcpEStatsTuneLimRwin, tcpEStatsTuneLimMSS
tcpEStatsTuneOptionalGroup对象组对象{tcpEStatsControlTune，tcpEStatsTuneLimCwnd，TcpestatStuneLimShresh，tcpEStatsTuneLimRwin，tcpEStatsTuneLimMSS
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsConnectionTable,
which can be used to set tuning parameters
for each TCP connection."
::= { tcpEStatsGroups 15 }
}
STATUS current
DESCRIPTION
"The tcpEStatsConnState group includes objects that
control the creation of the tcpEStatsConnectionTable,
which can be used to set tuning parameters
for each TCP connection."
::= { tcpEStatsGroups 15 }
tcpEStatsNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
tcpEStatsEstablishNotification,
tcpEStatsCloseNotification
}
STATUS current
DESCRIPTION
"Notifications sent by a TCP extended statistics agent."
::= { tcpEStatsGroups 16 }
tcpEStatsNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
tcpEStatsEstablishNotification,
tcpEStatsCloseNotification
}
STATUS current
DESCRIPTION
"Notifications sent by a TCP extended statistics agent."
::= { tcpEStatsGroups 16 }
tcpEStatsNotificationsCtlGroup OBJECT-GROUP
OBJECTS {
tcpEStatsControlNotify
}
STATUS current
DESCRIPTION
"The tcpEStatsNotificationsCtl group includes the
object that controls the creation of the events
in the tcpEStatsNotificationsGroup."
::= { tcpEStatsGroups 17 }
tcpEStatsNotificationsCtlGroup OBJECT-GROUP
OBJECTS {
tcpEStatsControlNotify
}
STATUS current
DESCRIPTION
"The tcpEStatsNotificationsCtl group includes the
object that controls the creation of the events
in the tcpEStatsNotificationsGroup."
::= { tcpEStatsGroups 17 }
END
终止
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
* Changing tcpEStatsConnTableLatency or any of the control objects in the tcpEStatsControl group (tcpEStatsControlPath, tcpEStatsControlStack, tcpEStatsControlApp, tcpEStatsControlTune) may affect the correctness of other management applications accessing this MIB. Generally, local policy should only permit limited write access to these controls (e.g., only by one management station or only during system configuration).
* 更改TCPESTATSConTableLatency或tcpEStatsControl组中的任何控制对象（tcpEStatsControlPath、tcpEStatsControlStack、tcpEStatsControlApp、tcpEStatsControlTune）可能会影响访问此MIB的其他管理应用程序的正确性。通常，本地策略只允许对这些控件进行有限的写访问（例如，仅由一个管理站或仅在系统配置期间）。
* The objects in the tcpEStatsControlTune group (tcpEStatsTuneLimCwnd, tcpEStatsTuneLimSsthresh, tcpEStatsTuneLimRwin) can be used to limit resources consumed by TCP connections or to limit TCP throughput. An attacker might manipulate these objects to reduce performance to levels below the minimum acceptable for a particular application.
* tcpEStatsControlTune组中的对象（tcpEStatsTuneLimCwnd、TcpestatStuneLimSthresh、tcpEStatsTuneLimRwin）可用于限制TCP连接消耗的资源或限制TCP吞吐量。攻击者可能会操纵这些对象，将性能降低到低于特定应用程序可接受的最低水平。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
* All objects which expose TCP sequence numbers (tcpEStatsAppSndUna, tcpEStatsAppSndNxt, tcpEStatsAppSndMax, tcpEStatsStackSndInitial, tcpEStatsAppRcvNxt, and tcpEStatsStackRecInitial) might make it easier for an attacker to forge in sequence TCP segments to disrupt TCP connections.
* 所有暴露TCP序列号的对象（tcpEStatsAppSndUna、tcpEStatsAppSndNxt、tcpEStatsAppSndMax、TcpestatsTacksNdinInitial、tcpEStatsAppRcvNxt和TcpestatsTackRecInitial）都可能使攻击者更容易伪造顺序TCP段以中断TCP连接。
* Nearly all objects in this (or any other) MIB may be used to estimate traffic volumes, which may reveal unanticipated information about an organization to the outside world.
* 此（或任何其他）MIB中的几乎所有对象都可用于估计通信量，这可能会向外部世界透露有关组织的意外信息。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配的对象标识符值：
Descriptor OBJECT IDENTIFIER value
------------ -----------------------
tcpEStatsMIB { mib-2 156 }
Descriptor OBJECT IDENTIFIER value
------------ -----------------------
tcpEStatsMIB { mib-2 156 }
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[RFC791]Postel，J.，“互联网协议”，标准5，RFC7911981年9月。
[RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
[RFC793]Postel，J.，“传输控制协议”，标准7，RFC 793，1981年9月。
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989.
[RFC1122]Braden，R.，Ed.“互联网主机的要求-通信层”，STD 3，RFC 1122，1989年10月。
[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, November 1990.
[RFC1191]Mogul，J.和S.Deering，“MTU发现路径”，RFC1191，1990年11月。
[RFC1323] Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for High Performance", RFC 1323, May 1992.
[RFC1323]Jacobson，V.，Braden，R.，和D.Borman，“高性能TCP扩展”，RFC 1323，1992年5月。
[RFC2018] Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow, "TCP Selective Acknowledgment Options", RFC 2018, October 1996.
[RFC2018]Mathis，M.，Mahdavi，J.，Floyd，S.，和A.Romanow，“TCP选择性确认选项”，RFC 2018，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 58, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的文本约定”，RFC 2579，STD 58，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 58, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的一致性声明”，RFC 2580，STD 58，1999年4月。
[RFC2581] Allman, M., Paxson, V., and W. Stevens, "TCP Congestion Control", RFC 2581, April 1999.
[RFC2581]Allman，M.，Paxson，V.和W.Stevens，“TCP拥塞控制”，RFC 25811999年4月。
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual Conventions for Additional High Capacity Data Types", RFC 2856, June 2000.
[RFC2856]Bierman，A.，McCloghrie，K.，和R.Presohn，“附加高容量数据类型的文本约定”，RFC 28562000年6月。
[RFC2883] Floyd, S., Mahdavi, J., Mathis, M., and M. Podolsky, "An Extension to the Selective Acknowledgement (SACK) Option for TCP", RFC 2883, July 2000.
[RFC2883]Floyd，S.，Mahdavi，J.，Mathis，M.，和M.Podolsky，“TCP选择性确认（SACK）选项的扩展”，RFC 28832000年7月。
[RFC2988] Paxson, V. and M. Allman, "Computing TCP's Retransmission Timer", RFC 2988, November 2000.
[RFC2988]Paxson，V.和M.Allman，“计算TCP的重传计时器”，RFC 2988，2000年11月。
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition of Explicit Congestion Notification (ECN) to IP", RFC 3168, September 2001.
[RFC3168]Ramakrishnan，K.，Floyd，S.，和D.Black，“向IP添加显式拥塞通知（ECN）”，RFC 3168，2001年9月。
[RFC3517] Blanton, E., Allman, M., Fall, K., and L. Wang, "A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP", RFC 3517, April 2003.
[RFC3517]Blanton，E.，Allman，M.，Fall，K.，和L.Wang，“基于保守选择确认（SACK）的TCP丢失恢复算法”，RFC 3517，2003年4月。
[RFC4022] Raghunarayan, R., Ed., "Management Information Base for the Transmission Control Protocol (TCP)", RFC 4022, March 2005.
[RFC4022]Raghunarayan，R.，Ed.“传输控制协议（TCP）的管理信息库”，RFC 40222，2005年3月。
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2", RFC 4502, May 2006.
[RFC4502]Waldbusser，S.，“远程网络监控管理信息库版本2”，RFC4502，2006年5月。
[Mat97] M. Mathis, J. Semke, J. Mahdavi, T. Ott, "The Macroscopic Behavior of the TCP Congestion Avoidance Algorithm", Computer Communication Review, volume 27, number 3, July 1997.
[Mat97]M.Mathis，J.Semke，J.Mahdavi，T.Ott，“TCP拥塞避免算法的宏观行为”，《计算机通信评论》，第27卷，第3期，1997年7月。
[Bra94] Brakmo, L., O'Malley, S., "TCP Vegas, New Techniques for Congestion Detection and Avoidance", SIGCOMM'94, London, pp 24-35, October 1994.
[Bra94]Brakmo，L.，O'Malley，S.，“TCP拉斯维加斯，拥塞检测和避免的新技术”，SIGCOMM'94，伦敦，第24-35页，1994年10月。
[Edd06] Eddy, W., "TCP SYN Flooding Attacks and Common Mitigations", Work in Progress, May 2007.
[Edd06]Eddy，W.，“TCP SYN洪泛攻击和常见缓解措施”，正在进行的工作，2007年5月。
[POSIX] Portable Operating System Interface, IEEE Std 1003.1
[POSIX]便携式操作系统接口，IEEE标准1003.1
[Pad98] Padhye, J., Firoiu, V., Towsley, D., Kurose, J., "Modeling TCP Throughput: A Simple Model and its Empirical Validation", SIGCOMM'98.
[Pad98]Padhye，J.，Firoiu，V.，Towsley，D.，Kurose，J.，“TCP吞吐量建模：一个简单模型及其经验验证”，SIGCOMM'98。
[Web100] Mathis, M., J. Heffner, R. Reddy, "Web100: Extended TCP Instrumentation for Research, Education and Diagnosis", ACM Computer Communications Review, Vol 33, Num 3, July 2003.
[Web100]Mathis，M.，J.Heffner，R.Reddy，“Web100：用于研究、教育和诊断的扩展TCP仪器”，ACM计算机通信评论，第33卷，Num 3，2003年7月。
[RFC2861] Handley, M., Padhye, J., and S. Floyd, "TCP Congestion Window Validation", RFC 2861, June 2000.
[RFC2861]Handley，M.，Padhye，J.，和S.Floyd，“TCP拥塞窗口验证”，RFC 28612000年6月。
[RFC3260] Grossman, D., "New Terminology and Clarifications for Diffserv", RFC 3260, April 2002.
[RFC3260]Grossman，D.“区分服务的新术语和澄清”，RFC 3260，2002年4月。
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3522] Ludwig, R. and M. Meyer, "The Eifel Detection Algorithm for TCP", RFC 3522, April 2003.
[RFC3522]Ludwig，R.和M.Meyer，“TCP的Eifel检测算法”，RFC 3522，2003年4月。
[RFC3742] Floyd, S., "Limited Slow-Start for TCP with Large Congestion Windows", RFC 3742, March 2004.
[RFC3742]Floyd，S.，“具有大拥塞窗口的TCP有限慢启动”，RFC 3742，2004年3月。
[RFC4614] Duke M., Braden, R., Eddy, W., Blanton, E. "A Roadmap for Transmission Control Protocol (TCP) Specification Documents", RFC 4614, September 2006.
[RFC4614]Duke M.，Braden，R.，Eddy，W.，Blanton，E.“传输控制协议（TCP）规范文件的路线图”，RFC 4614，2006年9月。
The following people contributed text that was incorporated into this document:
以下人员提供了纳入本文件的文本：
Jon Saperia <saperia@jdscons.com> converted Web100 internal documentation into a true MIB.
乔恩·萨佩里亚<saperia@jdscons.com>将Web100内部文档转换为真正的MIB。
Some of the objects in this document were moved from an early version of the TCP-MIB by Bill Fenner, et al.
本文档中的一些对象是由Bill Fenner等人从早期版本的TCP-MIB中移动过来的。
Some of the object descriptions are based on an earlier unpublished document by Jeff Semke.
一些对象描述基于Jeff Semke早期未发布的文档。
This document is a product of the Web100 project (www.web100.org), a joint effort of Pittsburgh Supercomputing Center (www.psc.edu), National Center for Atmospheric Research (www.ncar.ucar.edu), and National Center for Supercomputer Applications (www.ncsa.edu).
本文件是匹兹堡超级计算中心（www.psc.edu）、国家大气研究中心（www.ncar.ucar.edu）和国家超级计算机应用中心（www.ncsa.edu）共同努力的Web100项目（www.Web100.org）的成果。
It would not have been possible without all of the hard work by the entire Web100 team, especially Peter O'Neal, who read and reread the entire document several times; Janet Brown and Marla Meehl, who patiently managed the unmanageable. The Web100 project would not have been successful without all of the early adopters who suffered our bugs to provide many good suggestions and insights into their needs for TCP instrumentation.
如果没有彼得·奥尼尔，尤其是整个团队，他不可能反复阅读100次整个文件；珍妮特·布朗和玛拉·米尔耐心地管理着这个难以驾驭的局面。Web100项目如果没有所有的早期采用者，他们遭受了我们的错误，并就他们对TCP检测的需求提供了许多好的建议和见解，就不会成功。
Web100 was supported by the National Science Foundation under Grant No. 0083285 and a research grant from Cisco Systems.
Web100是由国家科学基金会资助的第0083285号资助和思科系统的研究资助。
We would also like to thank all of the people who built experimental implementations of this MIB from early versions and provided us with constructive feedback: Glenn Turner at AARnet, Kristine Adamson at IBM, and Xinyan Zan at Microsoft.
我们还要感谢所有从早期版本构建此MIB实验实现并向我们提供建设性反馈的人：AARnet的Glenn Turner、IBM的Kristine Adamson和Microsoft的Xinyan Zan。
And last, but not least, we would like to thank Dan Romascanu, our "MIB Doctor" and Bert Wijnen, the Operations Area Director, for patiently steering us through the MIB review process.
最后，但并非最不重要的是，我们要感谢我们的“MIB医生”Dan Romascanu和运营区域总监Bert Wijnen耐心地指导我们完成MIB审查过程。
Authors' Addresses
作者地址
Matt Mathis Pittsburgh Supercomputing Center 300 S. Craig St. Pittsburgh, PA 15213 Phone: 412-268-4960 EMail: mathis@psc.edu
Matt Mathis Pittsburgh Supercomputing Center 300 S.Craig St.Pittsburgh，PA 15213电话：412-268-4960电子邮件：mathis@psc.edu
John Heffner Pittsburgh Supercomputing Center 300 S. Craig St. Pittsburgh, PA 15213 Phone: 412-268-4960 EMail: jheffner@psc.edu
约翰·赫夫纳·匹兹堡超级计算中心宾夕法尼亚州匹兹堡南克雷格街300号15213电话：412-268-4960电子邮件：jheffner@psc.edu
Rajiv Raghunarayan Cisco Systems Inc. San Jose, CA 95134 Phone: 408 853 9612 EMail: raraghun@cisco.com
Rajiv Raghunarayan Cisco Systems Inc.加利福尼亚州圣何塞市95134电话：408 853 9612电子邮件：raraghun@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。