Network Working Group K. White
Request for Comments: 2562 IBM Corp.
Category: Standards Track R. Moore
IBM Corp.
April 1999
Network Working Group K. White
Request for Comments: 2562 IBM Corp.
Category: Standards Track R. Moore
IBM Corp.
April 1999
Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)
使用SMIv2（TN3270E-RT-MIB）为TN3270E响应时间收集定义协议和托管对象
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 Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This memo defines the protocol and the Management Information Base (MIB) for performing response time data collection on TN3270 and TN3270E sessions by a TN3270E server. The response time data collected by a TN3270E server is structured to support both validation of service level agreements and performance monitoring of TN3270 and TN3270E Sessions. This MIB has as a prerequisite the TN3270E-MIB, reference [20].
此备忘录定义了协议和管理信息库（MIB），用于通过TN3270E服务器在TN3270和TN3270E会话上执行响应时间数据收集。TN3270E服务器收集的响应时间数据的结构可支持服务级别协议的验证以及TN3270和TN3270E会话的性能监控。该MIB的先决条件是TN3270E-MIB，参考文献[20]。
TN3270E, defined by RFC 2355 [19], refers to the enhancements made to the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC 1041 [18], STD 8, RFC 854 [16], and STD 31, RFC 860 [17] for a sample of what is meant by TN3270 practices.
RFC 2355[19]定义的TN3270E是指对Telnet 3270（TN3270）终端仿真实践的增强。参考RFC 1041[18]、STD 8、RFC 854[16]和STD 31、RFC 860[17]了解TN3270实践的示例。
Table of Contents
目录
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Response Time Collection Methodology . . . . . . . . . . . 3
3.1 General Response Time Collection . . . . . . . . . . . . . 3
3.2 TN3270E Server Response Time Collection . . . . . . . . . 5
3.3 Correlating TN3270E Server and Host Response Times . . . . 10
3.4 Timestamp Calculation . . . . . . . . . . . . . . . . . . 11
3.4.1 DR Usage . . . . . . . . . . . . . . . . . . . . . . . 12
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Response Time Collection Methodology . . . . . . . . . . . 3
3.1 General Response Time Collection . . . . . . . . . . . . . 3
3.2 TN3270E Server Response Time Collection . . . . . . . . . 5
3.3 Correlating TN3270E Server and Host Response Times . . . . 10
3.4 Timestamp Calculation . . . . . . . . . . . . . . . . . . 11
3.4.1 DR Usage . . . . . . . . . . . . . . . . . . . . . . . 12
3.4.2 TIMING-MARK Usage . . . . . . . . . . . . . . . . . . 13
3.5 Performance Data Modelling . . . . . . . . . . . . . . . . 15
3.5.1 Averaging Response Times . . . . . . . . . . . . . . . 15
3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . 18
4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . 19
4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . 19
4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . 23
4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . 26
5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 26
6.0 Security Considerations . . . . . . . . . . . . . . . . . 45
7.0 Intellectual Property . . . . . . . . . . . . . . . . . . 45
8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 46
9.0 References . . . . . . . . . . . . . . . . . . . . . . . . 46
10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . 48
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . 49
3.4.2 TIMING-MARK Usage . . . . . . . . . . . . . . . . . . 13
3.5 Performance Data Modelling . . . . . . . . . . . . . . . . 15
3.5.1 Averaging Response Times . . . . . . . . . . . . . . . 15
3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . 18
4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . 19
4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . 19
4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . 23
4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . 26
5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 26
6.0 Security Considerations . . . . . . . . . . . . . . . . . 45
7.0 Intellectual Property . . . . . . . . . . . . . . . . . . 45
8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 46
9.0 References . . . . . . . . . . . . . . . . . . . . . . . . 46
10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . 48
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . 49
This document is a product of the TN3270E Working Group. It defines a protocol and a MIB module to enable a TN3270E server to collect and keep track of response time data for both TN3270 and TN3270E clients. Basis for implementing this MIB:
本文件是TN3270E工作组的产品。它定义了协议和MIB模块，使TN3270E服务器能够收集和跟踪TN3270和TN3270E客户端的响应时间数据。实施本MIB的依据：
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using SMIv2 [20]
o TN3270E-MIB，使用SMIv2的TN3270E托管对象的基本定义[20]
o TN3270E RFCs
o TN3270E RFC
o Telnet Timing Mark Option RFC [17].
o Telnet定时标记选项RFC[17]。
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, reference [23].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119，参考文献[23]中的描述进行解释。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2271 [1].
o RFC 2271[1]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in RFC 1902 [5], RFC
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在RFC 1902[5]中描述，RFC
1903 [6] and RFC 1904 [7].
1903[6]和RFC 1904[7]。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2272[11]和RFC 2274[12]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2273 [14] and the view-based access control mechanism described in RFC 2275 [15].
o RFC 2273[14]中描述的一组基本应用程序和RFC 2275[15]中描述的基于视图的访问控制机制。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
This section explains the methodology and approach used by the MIB defined by this memo for response time data collection by a TN3270E server.
本节解释了本备忘录定义的MIB用于TN3270E服务器收集响应时间数据的方法和方法。
Two primary methods exist for measuring response times in SNA networks:
测量SNA网络中的响应时间有两种主要方法：
o The Systems Network Architecture Management Services (SNA/MS) Response Time Monitoring (RTM) function.
o 系统网络体系结构管理服务（SNA/MS）响应时间监控（RTM）功能。
o Timestamping using definite response flows.
o 使用确定响应流的时间戳。
This memo defines an approach using definite responses to timestamp the flows between a client and its TN3270E server, rather than by use of the RTM method. Extensions to the SNA/MS RTM flow were considered, but this approach was deemed unsuitable since not all TN3270E server implementations have access to their underlying SNA stacks. The RTM concepts of keeping response time buckets for service level agreements and of interval-based response time collection for performance monitoring are preserved in the MIB module defined in this memo.
本备忘录定义了一种方法，该方法使用明确的响应对客户机与其TN3270E服务器之间的流进行时间戳，而不是使用RTM方法。考虑了对SNA/MS RTM流的扩展，但这种方法被认为不合适，因为并非所有TN3270E服务器实现都可以访问其底层SNA堆栈。在本备忘录中定义的MIB模块中保留了RTM概念，即为服务级别协议保留响应时间段，以及为性能监控保留基于间隔的响应时间收集。
As mentioned, this memo focuses on using definite responses to timestamp the flows between a client and its TN3270E server for generating performance data. Use of a definite response flow requires that the client supports TN3270E with the RESPONSES function negotiated. The TN3270 TIMING-MARK option can be used instead of definite response for supporting TN3270 clients or TN3270E clients that don't support RESPONSES. This document focuses first on defining the protocol and methods for generating performance data using definite responses, and then describes how the TIMING-MARK option can be used instead of definite response.
如前所述，本备忘录的重点是使用明确的响应对客户机与其TN3270E服务器之间的流进行时间戳，以生成性能数据。使用明确的响应流需要客户端支持TN3270E，并协商响应函数。对于支持不支持响应的TN3270客户端或TN3270E客户端，可以使用TN3270 TIMING-MARK选项代替确定响应。本文档首先侧重于定义使用明确响应生成性能数据的协议和方法，然后描述如何使用TIMING-MARK选项代替明确响应。
In an SNA network, a transaction between a client Logical Unit (LU) and a target host in general looks as follows:
在SNA网络中，客户机逻辑单元（LU）和目标主机之间的事务通常如下所示：
------------------------------------------------
| |
| Client LU Target SNA Host |
| |
| Timestamps |
| request A |
| -----------------------------------------> |
| reply(DR) B | |
| <---------------------------------------< |
| | +/-RSP C |
| >---------------------------------------> |
| |
| DR: Definite Response requested |
| +/-RSP: Definite Response |
| |
------------------------------------------------
------------------------------------------------
| |
| Client LU Target SNA Host |
| |
| Timestamps |
| request A |
| -----------------------------------------> |
| reply(DR) B | |
| <---------------------------------------< |
| | +/-RSP C |
| >---------------------------------------> |
| |
| DR: Definite Response requested |
| +/-RSP: Definite Response |
| |
------------------------------------------------
This transaction is a simple one, and is being used only to illustrate how timestamping at a target SNA host can be used to generate response times. An IBM redbook [12] provides a more detailed description of response time collection for a transaction of this type. Note that for the purpose of calculating an approximation
此事务非常简单，仅用于说明如何使用目标SNA主机上的时间戳来生成响应时间。IBM红皮书[12]对此类事务的响应时间集合提供了更详细的描述。请注意，为了计算近似值
for network transit time, it doesn't matter if the response is positive or negative. Two response time values are typically calculated:
对于网络传输时间，响应是肯定的还是否定的并不重要。通常计算两个响应时间值：
o Host Transit Time: Timestamp B - Timestamp A o Network Transit Time: Timestamp C - Timestamp B
o 主机传输时间：时间戳B-时间戳A o网络传输时间：时间戳C-时间戳B
Network transit time is an approximation for the amount of time that a transaction requires to flow across a network, since the response flow is being substituted for the request flow at the start of the transaction. Network transit time, timestamp C - timestamp B, is the amount of time that the definite response request and its response required. Host time, timestamp B - timestamp A, is the actual time that the host required to process the transaction. Experience has shown that using the response flow to approximate network transit times is useful, and does correlate well with actual network transit times.
网络传输时间是事务在网络上流动所需时间的近似值，因为响应流在事务开始时被请求流取代。网络传输时间，timestamp C-timestamp B是确定响应请求及其响应所需的时间量。主机时间，时间戳B-时间戳A，是主机处理事务所需的实际时间。经验表明，使用响应流来近似网络传输时间是有用的，并且与实际网络传输时间有很好的相关性。
A client SHOULD respond to a definite response request when it completes processing the transaction. This is important since it increases the accuracy of a total response time. Clients that immediately respond to a definite response request will be attributed with lower total response times then those that actually occurred.
客户机应在完成事务处理后响应明确的响应请求。这很重要，因为它提高了总响应时间的准确性。立即响应明确响应请求的客户端的总响应时间将低于实际发生的客户端。
The TN3270E-RT-MIB describes a method of collecting performance data that is not appropriate for printer (LU Type 1 or LU Type 3) sessions; thus collection of performance data for printer sessions is excluded from this MIB. This exclusion of printer sessions is not considered a problem, since these sessions are not the most important ones for response time monitoring, and since historically they were excluded from SNA/MS RTM collection. The tn3270eTcpConnResourceType object in a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to determine if a client session is ineligible for response time data collection for this reason.
TN3270E-RT-MIB描述了一种不适用于打印机（LU类型1或LU类型3）会话的性能数据收集方法；因此，打印机会话的性能数据收集不在此MIB中。排除打印机会话不被认为是一个问题，因为这些会话不是响应时间监控最重要的会话，而且从历史上看，它们被排除在SNA/MS RTM集合之外。可以检查tn3270eTcpConnEntry（在TN3270E-MIB中）中的tn3270eTcpConnResourceType对象，以确定客户端会话是否因此不符合响应时间数据收集的条件。
A TN3270E server connects a Telnet client performing 3270 emulation to a target SNA host over both a client-side network (client to TN3270E server) and an SNA Network (TN3270E server to target SNA host). The client-side network is typically TCP/IP, but it need not be. For ease of exposition this document uses the term "IP network" to refer to the client-side network, since IP is by far the most common protocol for these networks.
TN3270E服务器通过客户端网络（客户端到TN3270E服务器）和SNA网络（TN3270E服务器到目标SNA主机），将执行3270仿真的Telnet客户端连接到目标SNA主机。客户端网络通常是TCP/IP，但不需要。为了便于说明，本文档使用术语“IP网络”来指代客户端网络，因为IP是这些网络最常用的协议。
A TN3270E server can use SNA definite responses and the TN3270 Enhancement (RFC 2355 [19]) RESPONSES function to calculate response times for a transaction, by timestamping when a client request
TN3270E服务器可以使用SNA明确响应和TN3270增强（RFC 2355[19]）响应函数，通过在客户端请求时添加时间戳来计算事务的响应时间
arrives at the server, when the reply arrives from the target host, and when the response acknowledging this reply arrives from the client.
当应答从目标主机到达时，以及当确认此应答的应答从客户端到达时，到达服务器。
Section 3.4, Timestamp Calculation, provides specifics on when in the sequence of flows between a TN3270E client and its target SNA host a TN3270E server takes the required timestamps. In addition, it provides information on how a TN3270 TIMING-MARK request/response flow can be used instead of DR for approximating IP network transit times.
第3.4节“时间戳计算”详细说明了在TN3270E客户机与其目标SNA主机之间的流序列中，TN3270E服务器何时使用所需的时间戳。此外，它还提供了关于如何使用TN3270定时标记请求/响应流代替DR来近似IP网络传输时间的信息。
The following figure adds a TN3270E server between the client, in this case a TN3270E client and the target SNA host:
下图在客户端（在本例中为TN3270E客户端）和目标SNA主机之间添加了TN3270E服务器：
------------------------------------------------
| |
| Client TN3270E Target |
| Server SNA Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D |
| ------------------------------------------> |
| reply(DR) E | |
| <----------------------------------------< |
| | +/-RSP F |
| >-------------------- - - - - - - - - - > |
| |
------------------------------------------------
------------------------------------------------
| |
| Client TN3270E Target |
| Server SNA Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D |
| ------------------------------------------> |
| reply(DR) E | |
| <----------------------------------------< |
| | +/-RSP F |
| >-------------------- - - - - - - - - - > |
| |
------------------------------------------------
A TN3270E server can save timestamp D when it receives a client request, save timestamp E when the target SNA host replies, and save timestamp F when the client responds to the definite response request that flowed with the reply. It doesn't matter whether the target SNA host requested a definite response on its reply: if it didn't, the TN3270E server makes the request on its own, to enable it to produce timestamp F. In this case the TN3270E server does not forward the response to the target SNA host, as the dotted line in the figure indicates.
TN3270E服务器可以在接收到客户机请求时保存时间戳D，在目标SNA主机应答时保存时间戳E，并在客户机应答与应答一起流动的确定应答请求时保存时间戳F。目标SNA主机是否在其答复中请求了明确的响应并不重要：如果没有，则TN3270E服务器自行发出请求，以使其能够生成时间戳F。在这种情况下，TN3270E服务器不会将响应转发给目标SNA主机，如图中虚线所示。
Because it is a special case, a transaction in which a target SNA host returns an UNBIND in response to a client's request, and the TN3270E server forwards the UNBIND to the client, is not included in any response time calculations.
由于这是一种特殊情况，任何响应时间计算中都不包括目标SNA主机响应客户端请求返回解除绑定，而TN3270E服务器将解除绑定转发给客户端的事务。
In order to generate timestamp F, a TN3270E server MUST insure that the transaction specifies DR, and that the TN3270E RESPONSES function has been negotiated between itself and the client. Negotiation of the TN3270E RESPONSES function occurs during the client's TN3270E session initialization. The TN3270E servers that the authors are aware of do request the RESPONSES function during client session initialization. TN3270E clients either automatically support the RESPONSES function, or can be configured during startup to support it.
为了生成时间戳F，TN3270E服务器必须确保事务指定DR，并且TN3270E响应函数已在其自身和客户端之间协商。TN3270E响应函数的协商在客户端的TN3270E会话初始化期间发生。作者知道的TN3270E服务器在客户端会话初始化期间请求响应功能。TN3270E客户端可以自动支持响应功能，也可以在启动期间配置以支持响应功能。
Using timestamps D, E, and F the following response times can be calculated by a TN3270E server:
使用时间戳D、E和F，TN3270E服务器可以计算以下响应时间：
o Total Response time: Timestamp F - Timestamp D o IP Network Transit Time: Timestamp F - Timestamp E
o 总响应时间：时间戳F-时间戳D o IP网络传输时间：时间戳F-时间戳E
Just as in the SNA case presented above, these response times are also approximations, since the final +/- RSP from the client is being substituted for the request from the client that began the transaction.
正如上文所述的SNA案例一样，这些响应时间也是近似值，因为来自客户的最终+/-RSP将替换来自启动交易的客户的请求。
The MIB provides an object, tn3270eRtCollCtlType, to control several aspects of response time data collection. One of the available options in setting up a response time collection policy is to eliminate the IP-network component altogether. This might be done because it is determined either that the additional IP network traffic would not be desirable, or that the IP-network component of the overall response times is not significant.
MIB提供了一个对象tn3270eRtCollCtlType，用于控制响应时间数据收集的几个方面。设置响应时间收集策略的一个可用选项是完全消除IP网络组件。这可能是因为确定额外的IP网络通信量不是期望的，或者总体响应时间的IP网络组件不是重要的。
Excluding the IP-network component from response times also has an implication for the way in which response time data is aggregated. A TN3270E server may find that some of its clients simply don't support any of the functions necessary for the server to calculate the IP-network component of response times. For these clients, the most that the server can calculate is the SNA-network component of their overall response times; the server records this SNA-network component as the TOTAL response time each of these clients' transactions. If a response time collection is aggregating data from a number of clients, some of which have the support necessary for including the IP-network component in their total response time calculations, and some of which do not, then the server aggregates the data differently depending on whether the collection has been defined to include or exclude the IP-network component:
从响应时间中排除IP网络组件也意味着响应时间数据的聚合方式。TN3270E服务器可能会发现其某些客户端根本不支持服务器计算响应时间的IP网络组件所需的任何功能。对于这些客户机，服务器可以计算的最大值是其总体响应时间中的SNA网络组件；服务器将此SNA网络组件记录为每个客户端事务的总响应时间。如果响应时间集合正在聚合来自多个客户端的数据，其中一些客户端具有将IP网络组件包括在其总响应时间计算中所需的支持，而另一些客户端没有，然后，服务器根据集合是否定义为包含或排除IP网络组件，以不同方式聚合数据：
o If the IP-network component is included, then transactions for the clients that don't support calculation of the IP-network component of their response times are excluded from the aggregation altogether.
o 如果包含IP网络组件，则不支持计算其响应时间的IP网络组件的客户端事务将从聚合中完全排除。
o If the IP-network component is excluded, then total response times for ALL clients include only the SNA-network component, even though the server could have included an IP-network component in the overall response times for some of these clients. The server does this by setting timestamp F, which marks the end of a transaction's total response time, equal to timestamp E, the end of the transaction's SNA-network component.
o 如果排除了IP网络组件，则所有客户端的总响应时间仅包括SNA网络组件，即使服务器可能在其中一些客户端的总响应时间中包括IP网络组件。服务器通过设置时间戳F来实现这一点，时间戳F表示事务总响应时间的结束，等于时间戳E，即事务的SNA网络组件的结束。
The principle here is that all the transactions contributing their response times to an aggregated value MUST make the same contribution. If the aggregation specifies that an IP-network component MUST be included in the aggregation's response times, then transactions for which an IP-network component cannot be calculated aren't included at all. If the aggregation specifies that an IP-network component is not to be included, then only the SNA-network component is used, even for those transactions for which an IP-network component could have been calculated.
这里的原则是，将响应时间贡献给聚合值的所有事务都必须做出相同的贡献。如果聚合指定必须在聚合的响应时间中包括IP网络组件，则根本不包括无法计算IP网络组件的事务。如果聚合指定不包括IP网络组件，则仅使用SNA网络组件，即使对于可以计算IP网络组件的事务也是如此。
There is one more complication here: the MIB allows a management application to enable or disable dynamic definite responses for a response time collection. Once again the purpose of this option is to give the network operator control over the amount of traffic introduced into the IP network for response time data collection. A DYNAMIC definite response is one that the TN3270E server itself adds to a reply, in a transaction for which the SNA application at the target SNA host did not specify DR in its reply. When the +/-RSP comes back from the client, the server uses this response to calculate timestamp F, but then it does not forward the response on to the SNA application (since the application is not expecting a response to its reply).
这里还有一个复杂问题：MIB允许管理应用程序启用或禁用响应时间集合的动态确定响应。同样，此选项的目的是让网络运营商控制引入IP网络用于响应时间数据收集的通信量。在目标SNA主机上的SNA应用程序未在其应答中指定DR的事务中，TN3270E服务器本身添加到应答中的动态明确响应。当+/-RSP从客户端返回时，服务器使用此响应计算时间戳F，但随后它不会将响应转发到SNA应用程序（因为应用程序不期望对其响应做出响应）。
The dynamic definite responses option is related to the option of including or excluding the IP-network component of response times (discussed above) as follows:
动态确定响应选项与包含或排除响应时间的IP网络组件（如上所述）的选项相关，如下所示：
o If the IP-network component is excluded, then there is no reason for enabling dynamic definite responses: the server always sets timestamp F equal to timestamp E, so the additional IP-network traffic elicited by a dynamic definite response would serve no purpose.
o 如果排除了IP网络组件，则没有理由启用动态明确响应：服务器总是将时间戳F设置为等于时间戳E，因此动态明确响应引发的额外IP网络流量将没有任何用途。
o If the IP-network component is included, then enabling dynamic definite responses causes MORE transactions to be included in the aggregated response time values:
o 如果包含IP网络组件，则启用动态确定响应将导致聚合响应时间值中包含更多事务：
- For clients that do not support sending of responses, timestamp F can never be calculated, and so their transactions are never included in the aggregate.
- 对于不支持发送响应的客户端，时间戳F永远无法计算，因此它们的事务永远不会包含在聚合中。
- For clients that support sending of responses, timestamp F will always be calculated for transactions in which the host SNA application specifies DR in its reply, and so these transactions will always be included in the aggregate.
- 对于支持发送响应的客户端，对于主机SNA应用程序在其应答中指定DR的事务，始终会计算时间戳F，因此这些事务将始终包含在聚合中。
- For clients that support sending of responses, having dynamic definite responses enabled for a collection results in the inclusion of additional transactions in the aggregate: specifically, those for which the host SNA application did not specify DR in its reply.
- 对于支持发送响应的客户端，为集合启用动态明确响应会导致在聚合中包含其他事务：具体而言，主机SNA应用程序在其响应中未指定DR的事务。
A TN3270E server also has the option of substituting TIMING-MARK processing for definite responses in calculating the IP-network component of a transaction's response time. Once again, there is no reason for the server to do this if the collection has been set up to exclude the IP-network component altogether in computing response times.
在计算事务响应时间的IP网络组件时，TN3270E服务器还可以选择用定时标记处理代替确定的响应。同样，如果已将集合设置为在计算响应时间中完全排除IP网络组件，则服务器没有理由这样做。
The MIB is structured to keep counts and averages for total response times (F - D) and their IP-network components (F - E). A management application can obviously calculate from these two values an average SNA-network component (E - D) for the response times. This SNA-network component includes the SNA node processing time at both the TN3270E server and at the target application.
MIB的结构是保持总响应时间（F-D）及其IP网络组件（F-E）的计数和平均值。管理应用程序显然可以根据这两个值计算响应时间的平均SNA网络组件（E-D）。此SNA网络组件包括TN3270E服务器和目标应用程序的SNA节点处理时间。
A host TN3270E server refers to an implementation where the TN3270E server is collocated with the Systems Network Architecture (SNA) System Services Control Point (SSCP) for the dependent Secondary Logical Units (SLUs) that the server makes available to its clients for connecting into an SNA network. A gateway TN3270E server resides on an SNA node other than an SSCP, either an SNA type 2.0 node, a boundary-function-attached type 2.1 node, or an APPN node acting in the role of a Dependent LU Requester (DLUR). Host and gateway TN3270E server implementations typically differ greatly as to their internal implementation and System Definition (SYSDEF) requirements.
主机TN3270E服务器指的是一种实现，其中TN3270E服务器与系统网络体系结构（SNA）系统服务控制点（SSCP）并置，用于服务器向其客户端提供用于连接到SNA网络的从属辅助逻辑单元（SLU）。网关TN3270E服务器位于除SSCP以外的SNA节点上，SNA类型2.0节点、边界功能附加类型2.1节点或充当从属LU请求者（DLUR）角色的APPN节点。主机和网关TN3270E服务器实现在其内部实现和系统定义（SYSDEF）要求方面通常有很大差异。
If a host TN3270E server is in the same SNA host as the target application, then the SNA-network component of a transaction's response time will approximately equal the host transit time (B - A) described previously. A host TN3270E server implementation can, however, typically support the establishment of sessions to target applications in SNA hosts remote from itself. In this case the SNA-network component of the response time equals the actual SNA-network transit time plus two host transit times.
如果主机TN3270E服务器与目标应用程序位于同一SNA主机中，则事务响应时间的SNA网络组件将大致等于前面描述的主机传输时间（B-a）。然而，主机TN3270E服务器实现通常可以支持建立会话，以在远离自身的SNA主机中的目标应用程序。在这种情况下，响应时间的SNA网络部分等于实际SNA网络传输时间加上两个主机传输时间。
It is possible that response time data is collected from TN3270E servers at the same time as a management application is monitoring the SNA sessions at a host. For example, a management application can be monitoring a secondary logical unit (SLU) while retrieving data from a TN3270E server. Consider the following figure:
在管理应用程序监视主机上的SNA会话的同时，可能从TN3270E服务器收集响应时间数据。例如，管理应用程序可以在从TN3270E服务器检索数据时监视辅助逻辑单元（SLU）。考虑下面的数字：
------------------------------------------------
| |
| Client TN3270E Target |
| Server SNA Host |
| Timestamps (PLU) |
| (SLU) Timestamps|
| <---IP Network-------><---SNA Network---> |
| |
| request D A |
| ------------------------------------------> |
| reply(DR) E B | |
| <----------------------------------------< |
| | +/-RSP F C |
| >--------------------------------------> |
| |
------------------------------------------------
------------------------------------------------
| |
| Client TN3270E Target |
| Server SNA Host |
| Timestamps (PLU) |
| (SLU) Timestamps|
| <---IP Network-------><---SNA Network---> |
| |
| request D A |
| ------------------------------------------> |
| reply(DR) E B | |
| <----------------------------------------< |
| | +/-RSP F C |
| >--------------------------------------> |
| |
------------------------------------------------
The following response times are available:
以下响应时间可用：
o Target SNA host transit time: Timestamp B - Timestamp A o Target SNA host network transit time: Timestamp C - Timestamp B o TN3270E server total response time: Timestamp F - Timestamp D o TN3270E server IP-network component: Timestamp F - Timestamp E
o 目标SNA主机传输时间：时间戳B-时间戳A o目标SNA主机网络传输时间：时间戳C-时间戳B o TN3270E服务器总响应时间：时间戳F-时间戳D o TN3270E服务器IP网络组件：时间戳F-时间戳E
The value added by the TN3270E server in this situation is its approximation of the IP-network component of the overall response time. The IP-network component can be subtracted from the total network transit time (which can be captured at an SSCP monitoring SNA traffic from/to the SLU) to see the actual SNA versus IP network transit times.
在这种情况下，TN3270E服务器增加的值是其总响应时间的IP网络组件的近似值。IP网络组件可从总网络传输时间中减去（可在监控SNA进出SLU流量的SSCP中捕获），以查看实际SNA与IP网络传输时间的对比。
The MIB defined by this memo does not specifically address correlation of the data it contains with response time data collected by direct monitoring of SNA resources: its focus is exclusively response time data collection from a TN3270E server perspective. It has, however, in conjunction with the TN3270E-MIB [10], been structured to provide the information necessary for correlation between TN3270E server-provided response time information and that gathered from directly monitoring SNA resources.
本备忘录定义的MIB并未具体说明其包含的数据与通过直接监控SNA资源收集的响应时间数据之间的相关性：其重点是从TN3270E服务器的角度专门收集响应时间数据。然而，它与TN3270E-MIB[10]结合在一起，被构造为提供必要的信息，以便在TN3270E服务器提供的响应时间信息和从直接监控SNA资源收集的响应时间信息之间进行关联。
A management application attempting to correlate SNA resource usage to Telnet clients can monitor either the tn3270eResMapTable or the tn3270eTcpConnTable to determine resource-to-client address mappings. Both of these tables are defined by the TN3270E-MIB [10]. Another helpful table is the tn3270eSnaMapTable, which provides a mapping between SLU names as they are known at the SSCP (VTAM) and their local names at the TN3270E server. Neither the tn3270eClientGroupTable, the tn3270eResPoolTable, nor the tn3270eClientResMapTable from the TN3270E-MIB can be used for correlation, since the mappings defined by these tables can overlap, and may not provide one-to-one mappings.
试图将SNA资源使用情况与Telnet客户端关联的管理应用程序可以监视tn3270eResMapTable或tn3270eTcpConnTable，以确定资源到客户端地址的映射。这两个表都由TN3270E-MIB定义[10]。另一个有用的表是tn3270eSnaMapTable，它提供了SSCP（VTAM）中已知的SLU名称与TN3270E服务器上的本地名称之间的映射。TN3270E-MIB中的tn3270eClientGroupTable、TN3270EREPoolTable和tn3270eClientResMapTable都不能用于关联，因为这些表定义的映射可能重叠，并且可能不提供一对一映射。
This section goes into more detail concerning when the various timestamps can be taken as the flows between a TN3270E client and its target SNA host pass through a TN3270E server. In addition, information is provided on how the TN3270 TIMING-MARK request/response flow can be used in place of DR for approximating IP network transit times.
本节将更详细地介绍当TN3270E客户机与其目标SNA主机之间的流通过TN3270E服务器时，各种时间戳何时可以被采用。此外，还提供了关于如何使用TN3270定时标记请求/响应流代替DR来近似IP网络传输时间的信息。
Consider the following flow:
考虑以下流程：
----------------------------------------------------------
| |
| Client TN3270E Target SNA |
| Server Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D (BB,CD,OIC,ER) |
| -------------------------------------------> |
| reply(DR) (FIC,ER,EB) | |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply E (LIC,DR) |
| <-----------------------------------------< |
| | +/-RSP F |
| >----------------------------------------> |
| |
| BB : Begin Bracket ER : Response by exception |
| EB : End Bracket DR : Definite Response Requested |
| CD : Change Direction FIC : First in chain |
| OIC: Only in chain MIC: Middle in chain |
| LIC: Last in chain |
----------------------------------------------------------
----------------------------------------------------------
| |
| Client TN3270E Target SNA |
| Server Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D (BB,CD,OIC,ER) |
| -------------------------------------------> |
| reply(DR) (FIC,ER,EB) | |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply E (LIC,DR) |
| <-----------------------------------------< |
| | +/-RSP F |
| >----------------------------------------> |
| |
| BB : Begin Bracket ER : Response by exception |
| EB : End Bracket DR : Definite Response Requested |
| CD : Change Direction FIC : First in chain |
| OIC: Only in chain MIC: Middle in chain |
| LIC: Last in chain |
----------------------------------------------------------
Timestamp D is taken at the TN3270E server when the server has received data from a client for forwarding to its target SNA host, and the direction of the SNA session allows the server to forward the data immediately (either the direction is inbound towards the SNA host, or the session is between brackets). This is most likely when the server finds the end of record indicator in the TCP data received from the client.
当服务器从客户端接收到数据以转发到其目标SNA主机时，在TN3270E服务器上获取时间戳D，并且SNA会话的方向允许服务器立即转发数据（该方向是朝向SNA主机的入站方向，或者会话在括号之间）。当服务器在从客户端接收的TCP数据中找到记录结束指示符时，最有可能出现这种情况。
The target SNA application returns its reply in one or more SNA Request Units (RUs); in this example there are four RUs in the reply. The first RU is marked as first in chain (FIC), the next two are marked as middle in chain (MIC), and the last is marked as last in chain (LIC). If the SNA host sends a multiple-RU chain, the server does not know until the last RU is received whether DR is being requested. The server's only chance to request DR from the client, however, comes when it forwards the FIC RU, since this is the only
目标SNA应用程序以一个或多个SNA请求单元（RU）返回其回复；在本例中，答复中有四个RU。第一个RU标记为链中第一个（FIC），下两个RU标记为链中中间（MIC），最后一个RU标记为链中最后一个（LIC）。如果SNA主机发送多个RU链，则在收到最后一个RU之前，服务器不知道是否正在请求DR。然而，服务器从客户端请求灾难恢复的唯一机会是在转发FIC RU时，因为这是唯一的机会
time that the TN3270E header is included. Since a server may forward the FIC RU to the client before it receives the LIC RU from the SNA host, some servers routinely specify DR on all FIC RUs.
包括TN3270E标头的时间。由于服务器可能在从SNA主机接收LIC RU之前将FIC RU转发给客户端，因此一些服务器通常在所有FIC RU上指定DR。
If the server has specified DR on the TN3270E request for the FIC RU in a chain, it takes timestamp E when it forwards the LIC RU to the client. Since timestamp E is used for calculating the IP-network time for the transaction, the server SHOULD take timestamp E as close as possible to its "Telnet edge". The server takes timestamp F when it receives the RESPONSES response from the client.
如果服务器在链中为FIC RU的TN3270E请求上指定了DR，则在将LIC RU转发到客户端时会使用时间戳E。由于时间戳E用于计算事务的IP网络时间，因此服务器应将时间戳E尽可能靠近其“Telnet边缘”。当服务器从客户端接收到响应时，它会使用时间戳F。
A target SNA application doesn't necessarily return data to a client in a transaction; it may, for example, require more data from the client before it can formulate a reply. In this case the application may simply return to the TN3270E server a change of direction indicator. At this point the server must send something to the client (typically a Write operation with a WCC) to unlock the keyboard. If the server specifies DR on the request to the client triggered by its receipt of the change of direction indicator from the SNA application, then timestamps E and F can be taken, and the usual response times can be calculated. When the client sends in the additional data and gets a textual response from the SNA application, the server treats this as a separate transaction from the one involving the change of direction.
目标SNA应用程序不一定在事务中向客户端返回数据；例如，它可能需要客户机提供更多数据，然后才能制定回复。在这种情况下，应用程序可以简单地向TN3270E服务器返回方向指示灯的改变。此时，服务器必须向客户端发送一些东西（通常是使用WCC的写入操作）以解锁键盘。如果服务器在收到来自SNA应用程序的方向指示器更改后触发的对客户机的请求中指定DR，则可以获取时间戳E和F，并计算通常的响应时间。当客户端发送附加数据并从SNA应用程序获得文本响应时，服务器将其视为与涉及方向更改的事务不同的单独事务。
It is possible for a TN3270E server to use the TIMING-MARK flow for approximating IP network transit times. Using TIMING-MARKs would make it possible for a server to collect performance data for TN3270 clients, as well as for TN3270E clients that do not support the RESPONSES function. In order for TIMING-MARKs to be used in this way, a client can't have the NOP option enabled, since responses are needed to the server's TIMING-MARK requests. An IP network transit time approximation using a TIMING-MARK is basically the amount of time it takes for a TN3270 server to receive from a client a response to a TIMING-MARK request.
TN3270E服务器可以使用定时标记流来近似IP网络传输时间。使用定时标记可以让服务器收集TN3270客户端以及不支持响应功能的TN3270E客户端的性能数据。为了以这种方式使用定时标记，客户端不能启用NOP选项，因为需要响应服务器的定时标记请求。使用时间标记的IP网络传输时间近似值基本上是TN3270服务器从客户端接收对时间标记请求的响应所需的时间量。
To get an estimate for IP network transit time, a TN3270E server sends a TIMING-MARK request to a client after a LIC RU has been received, as a means of approximating IP network transit time:
为了获得IP网络传输时间的估计值，TN3270E服务器在接收到LIC RU后向客户端发送定时标记请求，作为近似IP网络传输时间的一种方法：
---------------------------------------------------
| |
| Client TN3270E Target |
| Server Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D (BB,CD,OIC,ER) |
| -------------------------------------------> |
| reply (FIC,ER,EB) | |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply E (LIC,ER) |
| <-----------------------------------------< |
| TIMING-MARK Rqst E' |
| <--------------------- |
| | TIMING-MARK Rsp F' |
| >-------------------> |
| |
---------------------------------------------------
---------------------------------------------------
| |
| Client TN3270E Target |
| Server Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D (BB,CD,OIC,ER) |
| -------------------------------------------> |
| reply (FIC,ER,EB) | |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply (MIC,ER) |
| <-----------------------------------------< |
| reply E (LIC,ER) |
| <-----------------------------------------< |
| TIMING-MARK Rqst E' |
| <--------------------- |
| | TIMING-MARK Rsp F' |
| >-------------------> |
| |
---------------------------------------------------
The response times can then be calculated as follows:
然后，响应时间可按如下方式计算：
o TN3270E server total response time: (Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E')
o TN3270E服务器总响应时间：（时间戳E-时间戳D）+（时间戳F'-时间戳E'）
o TN3270E server IP network time: Timestamp F' - Timestamp E'
o TN3270E服务器IP网络时间：时间戳F'-时间戳E'
If a TN3270E server is performing the TIMING-MARK function (independent of the response time monitoring use of the function discussed here), then it most likely has a TIMING-MARK interval for determining when to examine client sessions for sending the TIMING-MARK request. This interval, which is ordinarily a global value for an entire TN3270E server, is represented in the TN3270E-MIB by the tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent only if, when it is examined, a client session is found to have had no activity for a different fixed length of time, represented in the TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object.
如果TN3270E服务器正在执行TIMING-MARK功能（与此处讨论的功能的响应时间监视使用无关），则它很可能具有TIMING-MARK间隔，用于确定何时检查发送TIMING-MARK请求的客户端会话。该间隔通常是整个TN3270E服务器的全局值，在TN3270E-MIB中由TN3270ESRVReconfTMNopInterval对象表示。只有在检查时发现客户机会话在不同的固定时间段内没有活动时，才会发送定时标记请求，该固定时间段在TN3270E-MIB中由tn3270eSrvrConfTmNopInactTime对象表示。
Servers that support a large number of client sessions should spread out the TIMING-MARK requests they send to these clients over the activity interval, rather than sending them all in a single burst, since otherwise the network may be flooded with TIMING-MARK requests. When a server uses TIMING-MARKs for approximating response times,
支持大量客户端会话的服务器应在活动间隔内分散发送给这些客户端的时间标记请求，而不是在一次突发中发送它们，因为否则网络可能会被时间标记请求淹没。当服务器使用计时标记来近似响应时间时，
this tends to introduce a natural spreading into its TIMING-MARK requests, since the requests are triggered by the arrival of traffic from an SNA host.
这往往会在其时间标记请求中引入自然扩展，因为请求是由来自SNA主机的流量到达触发的。
A TN3270E server MUST integrate its normal TIMING-MARK processing with its use of TIMING-MARKs for computing response times. In particular, it MUST NOT send a second TIMING-MARK request to a client while waiting for the first to return, since this is ruled out by the TIMING-MARK protocol itself. If a TIMING-MARK flow has just been performed for a client shortly before the LIC RU arrives, the server MAY use the interval from this flow as its approximation for IP network transit time, (in other words, as its (F' - E') value) when calculating its approximation for the transaction's total response time, rather than sending a second TIMING-MARK request so soon after the preceding one.
TN3270E服务器必须将其正常的定时标记处理与其用于计算响应时间的定时标记的使用相结合。特别是，在等待第一个TIMING-MARK请求返回时，它不能向客户端发送第二个TIMING-MARK请求，因为TIMING-MARK协议本身排除了这一点。如果在LIC RU到达之前不久刚刚对客户端执行了定时标记流，则服务器在计算其事务总响应时间的近似值时，可以使用来自该流的间隔作为其IP网络传输时间的近似值（换句话说，作为其（F'-E'）值），而不是在前一个时间标记请求之后这么快发送第二个时间标记请求。
Regardless of when the server sends its TIMING-MARK request, the accuracy of its total response time calculation depends on exactly when the client responds to the TIMING-MARK request.
无论服务器何时发送其TIMING-MARK请求，其总响应时间计算的准确性完全取决于客户端何时响应TIMING-MARK请求。
The following two subsections detail how the TN3270E-RT-MIB models and controls capture of two types of response time data: average response times and response time buckets.
以下两小节详细介绍了TN3270E-RT-MIB如何建模和控制两类响应时间数据的捕获：平均响应时间和响应时间桶。
Average response times play two different roles in the MIB:
平均响应时间在MIB中扮演两个不同的角色：
o They are made available for management applications to retrieve. o They serve as triggers for emitting notifications.
o 它们可供管理应用程序检索。o它们充当发出通知的触发器。
Sliding-window averages are used rather than straight interval-based averages, because they are often more meaningful, and because they cause less notification thrashing. Sliding-window average calculation can, if necessary, be disabled, by setting the sample period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample period, tn3270eRtCollCtlSPeriod, to the required collection interval.
使用滑动窗口平均值，而不是基于间隔的直线平均值，因为它们通常更有意义，并且导致较少的通知抖动。如有必要，可以通过将采样周期乘数TN3270ERTCOLLCLTSPMULT设置为1，并将采样周期TN3270ERTCOLLCLTSPRIOD设置为所需的采集间隔来禁用滑动窗口平均值计算。
In order to calculate sliding-window averages, a TN3270E server MUST:
为了计算滑动窗口平均值，TN3270E服务器必须：
o Select a fixed, relatively short, sample period SPeriod; the default value for SPeriod in the MIB is 20 seconds.
o 选择一个固定的、相对较短的采样周期；MIB中SPeriod的默认值为20秒。
o Select an averaging period multiplier SPMult. The actual collection interval will then be SPMult times SPeriod. The default value for SPMult in the MIB is 30, yielding a default collection interval of 10 minutes. Note that the collection interval (SPMult*SPeriod) is always a multiple of the sample period.
o 选择一个平均周期乘数SPMult。然后，实际采集间隔将为SPMult乘以SPeriod。MIB中SPMult的默认值为30，产生10分钟的默认收集间隔。请注意，采集间隔（SPMult*SPeriod）始终是采样周期的倍数。
Clearlly, SPMult*SPeriod should not be thought of as literally the averaging period. The average calculated will include contributions older than that time, and does not weight equally all contributions since that time. In fact, it gives a smoother result than a traditional sliding average, as used in finance. More subtly, it is best to think of the effective averaging period as being 2*SPMult*SPeriod. To see this, consider how long the contribution to the result made by a particular transaction lasts. With a traditional sliding average, it lasts exactly the averaging period. With the aging mechanism described here, it has a half-life of SPMult*SPeriod.
显然，SPMult*SPeriod不应被视为字面上的平均周期。计算的平均数将包括比该时间早的捐款，并且不会对自该时间以来的所有捐款进行同等加权。事实上，它给出了一个比传统的滑动平均更平滑的结果，如在金融中使用。更微妙的是，最好将有效平均周期视为2*SPMult*SPeriod。要了解这一点，考虑一个特定事务对结果的贡献持续了多长时间。使用传统的滑动平均法，它正好持续平均期。根据这里描述的老化机制，其半衰期为SPMult*SPeriod。
o Maintain the following counters to keep track of activity within the current sample period; these are internal counters, not made visible to a management application via the MIB.
o 维护以下计数器，以跟踪当前采样周期内的活动；这些是内部计数器，管理应用程序无法通过MIB看到。
- T (number of transactions in the period)
- T（该期间的交易数量）
- TotalRts (sum of the total response times for all transactions in the period)
- TotalRts（期间内所有事务的总响应时间之和）
- TotalIpRts (sum of the IP network transit times for all transactions in the period; note that if IP network transit times are being excluded from the response time collection, this value will always be 0).
- TotalIpRts（期间内所有事务的IP网络传输时间之和；请注意，如果从响应时间集合中排除IP网络传输时间，则该值将始终为0）。
o Also maintain sliding counters, initialized to zero, for each of the quantities being counted:
o 还应为每个正在计数的量维护初始化为零的滑动计数器：
- AvgCountTrans (sliding count of transactions) - TotalRtsSliding (sliding count of total response times) - TotalIpRtsSliding (sliding count of IP network transit times)
- AvgCountTrans（事务的滑动计数）-TotalRtsSliding（总响应时间的滑动计数）-TotalIpRtsSliding（IP网络传输时间的滑动计数）
o At the end of each sample period, update the sliding interval counters, using the following floating-point calculations:
o 在每个采样周期结束时，使用以下浮点计算更新滑动间隔计数器：
AvgCountTrans = AvgCountTrans + T
- (AvgCountTrans / SPMult)
AvgCountTrans = AvgCountTrans + T
- (AvgCountTrans / SPMult)
TotalRtsSliding = TotalRtsSliding + TotalRts
- (TotalRtsSliding / SPMult)
TotalRtsSliding = TotalRtsSliding + TotalRts
- (TotalRtsSliding / SPMult)
TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts
- (TotalIpRtsSliding / SPMult)
TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts
- (TotalIpRtsSliding / SPMult)
Then reset T, TotalRts, and TotalIpRts to zero for use during the next sample period.
然后将T、TotalRts和TotalIpRts重置为零，以便在下一个采样周期内使用。
o At the end of a collection interval, update the following MIB objects as indicated; the floating-point numbers are rounded rather than truncated.
o 在采集间隔结束时，按照指示更新以下MIB对象；浮点数是四舍五入的，而不是截断的。
tn3270eRtDataAvgCountTrans = AvgCountTrans
tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans
tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans
tn3270eRtDataAvgCountTrans = AvgCountTrans
tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans
tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans
As expected, if IP network transit times are being excluded from response time collection, then tn3270eRtDataAvgIpRt will always return 0.
正如预期的那样，如果从响应时间收集中排除IP网络传输时间，则tn3270eRtDataAvgIpRt将始终返回0。
The sliding transaction counter AvgCountTrans is not used for updating the MIB object tn3270eRtDataCountTrans: this object is an ordinary SMI Counter32, which maintains a total count of transactions since its last discontinuity event. The sliding counters are used only for calculating averages.
滑动事务计数器AvgCountTrans不用于更新MIB对象tn3270eRtDataCountTrans：此对象是一个普通SMI计数器32，它维护自上次中断事件以来的事务总数。滑动计数器仅用于计算平均值。
Two mechanisms are present in the MIB to inhibit the generation of an excessive number of notifications related to average response times. First, there are high and low thresholds for average response times. A tn3270eRtExceeded notification is generated the first time a statistically significant average response time is found to have exceeded the high threshold. (The test for statistical significance is described below.) After this, no other tn3270eRtExceeded notifications are generated until an average response time is found to have fallen below the low threshold.
MIB中存在两种机制来抑制与平均响应时间相关的过多通知的生成。首先，平均响应时间有高阈值和低阈值。首次发现统计上显著的平均响应时间超过高阈值时，生成TN3270ERT超出通知。（统计显著性检验如下所述。）此后，在发现平均响应时间低于低阈值之前，不会生成其他TN3270ERT通知。
The other mechanism to limit notifications is the significance test for a high average response time. Intuitively, the significance of an average is directly related to the number of samples that go into it; so we might be inclined to use a rule such as "for the purpose of generating tn3270eRtExceeded notifications, ignore average response times based on fewer than 20 transactions in the sample period."
另一种限制通知的机制是高平均响应时间的显著性测试。直观地说，平均值的重要性与进入平均值的样本数直接相关；因此，我们可能倾向于使用这样的规则：“为了生成TN3270通知，忽略样本期内少于20个事务的平均响应时间。”
In the case of response times, however, the number of transactions sampled in a fixed sampling period is tied to these transactions' response times. A few transactions with long response times can guarantee that there will not be many transactions in a sample, because these transactions "use up" the sampling time. Yet this case
但是，就响应时间而言，在固定的采样周期内采样的事务数与这些事务的响应时间有关。几个响应时间长的事务可以保证样本中不会有很多事务，因为这些事务“占用”了采样时间。然而这个案子
of a few transactions with very poor response times should obviously be classified as a problem, not as a statistical anomaly based on too small a sample.
对于响应时间非常差的少数事务，显然应将其归类为问题，而不是基于太小样本的统计异常。
The solution is to make the significance level for a sample a function of the average response time. A value IdleCount is specified, which is used to qualify an sample as statistically significant. In order to determine at a collection interval whether to generate a tn3270eRtExceeded notification, a TN3270E server uses the following algorithm:
解决方案是将样本的显著性水平作为平均响应时间的函数。指定了IdleCount值，该值用于将样本限定为具有统计显著性。为了在收集间隔确定是否生成TN3270E通知，TN3270E服务器使用以下算法：
if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount then generate the notification,
如果AvgCountTrans*（（AvgRt/ThreshHigh-1）**2）>=IdleCount，则生成通知，
where AvgRt is the value that would be returned by the object tn3270eRtDataAvgRt at the end of the interval, and the "**" notation indicates exponientiation.
其中，AvgRt是对象tn3270eRtDataAvgRt在间隔结束时返回的值，“**”符号表示展开。
Two examples illustrate how this algorithm works. Suppose that IdleCount has been set to 20 transactions, and the high threshold to 200 msecs per transaction. If the average observed response time is 300 msecs, then a notification will be generated only if AvgCountTrans >= 80. If, however, the observed response time is 500 msecs, then a notification is generated if AvgCountTrans >= 9.
两个例子说明了该算法的工作原理。假设IdleCount已设置为20个事务，并且高阈值为每个事务200毫秒。如果观察到的平均响应时间为300毫秒，则仅当AvgCountTrans>=80时才会生成通知。但是，如果观察到的响应时间为500毫秒，则如果AvgCountTrans>=9，则会生成通知。
There is no corresponding significance test for the tn3270eRtOkay notification: this notification is generated based on an average response time that falls below the low threshold, regardless of the sample size behind that average.
TN3270Ertook通知没有相应的显著性测试：该通知是基于低于低阈值的平均响应时间生成的，而不管该平均值后面的样本大小如何。
The MIB also supports collection of response time data into a set of five buckets. This data is suitable either for verification of service level agreements, or for monitoring by a management application to identify performance problems. The buckets provide counts of transactions whose total response times fall into a set of specified ranges.
MIB还支持将响应时间数据收集到一组五个存储桶中。此数据既适用于验证服务级别协议，也适用于由管理应用程序进行监视以识别性能问题。bucket提供总响应时间在一组指定范围内的事务计数。
Like everything for a collection, the "total" response times collected in the buckets are governed by the specification of whether IP network transit times are to be included in the totals. Depending on how this option is specified, the response times being counted in the buckets will either be total response times (F - D), or only SNA network transit times (effectively E - D, because when it is excluding the IP-network component of transactions, a server makes timestamp F identical to timestamp E).
与收集的所有内容一样，在存储桶中收集的“总”响应时间受是否将IP网络传输时间包括在总数中的规范控制。根据该选项的指定方式，存储桶中计算的响应时间要么是总响应时间（F-D），要么只是SNA网络传输时间（实际上是E-D，因为当它排除事务的IP网络组件时，服务器使时间戳F与时间戳E相同）。
Four bucket boundaries are specified for a response time collection, resulting in five buckets. The first response time bucket counts those transactions whose total response times were less than or equal to Boundary 1, the second bucket counts those whose response times were greater than Boundary 1 but less than or equal to Boundary 2, and so on. The fifth bucket is unbounded on the top, counting all transactions whose response times were greater than Boundary 4.
为响应时间集合指定了四个存储桶边界，从而产生五个存储桶。第一个响应时间桶统计总响应时间小于或等于边界1的事务，第二个桶统计响应时间大于边界1但小于或等于边界2的事务，依此类推。第五个bucket在顶部是无界的，它统计响应时间大于边界4的所有事务。
The four bucket boundaries have default values of: 1 second, 2 seconds, 5 seconds, and 10 seconds, respectively. These values are the defaults in the 3174 controller's implementation of the SNA/MS RTM function, and are thought to be appropriate for this MIB as well.
四个铲斗边界的默认值分别为：1秒、2秒、5秒和10秒。这些值是3174控制器实现SNA/MS RTM功能时的默认值，被认为也适用于此MIB。
In SNA/MS the counter buckets were (by today's standards) relatively small, with a maximum value of 65,535. The bucket objects in the MIB are all Counter32's.
在SNA/MS中，计数器桶（按照今天的标准）相对较小，最大值为65535。MIB中的bucket对象都是Counter32。
The following figure represents the buckets pictorially:
下图以图形方式表示铲斗：
----------------------------------------------
| |
| Response Time Boundaries |
| | | | | | | |
| | | | | | | |
| | | | | | no |
| 0 B-1 B-2 B-3 B-4 bound|
| | | | | | | |
| |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| |
| ----------------------------------------- |
| |
----------------------------------------------
----------------------------------------------
| |
| Response Time Boundaries |
| | | | | | | |
| | | | | | | |
| | | | | | no |
| 0 B-1 B-2 B-3 B-4 bound|
| | | | | | | |
| |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| |
| ----------------------------------------- |
| |
----------------------------------------------
The TN3270E-RT-MIB has the following components:
TN3270E-RT-MIB具有以下组件：
o tn3270eRtCollCtlTable o tn3270eRtDataTable o Notifications o Advisory Spin Lock Usage
o TN3270ERTCOLLCTLABLE o tn3270eRtDataTable o通知o建议自旋锁使用
The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and tn3270eClientGroupName imported from the TN3270E-MIB. tn3270eSrvrConfIndex identifies within a host a particular TN3270E
TN3270ERTCOLLCTLABLE由从TN3270E-MIB导入的TN3270ESRVRConIndex和tn3270eClientGroupName索引。TN3270ESRVRECONDEX在主机内标识特定的TN3270E
server. tn3270eClientGroupName identifies a collection of IP clients for which response time data is to be collected. The set of clients is defined using the tn3270eClientGroupTable from the TN3270E-MIB.
服务器tn3270eClientGroupName标识要为其收集响应时间数据的IP客户端集合。客户机集是使用TN3270E-MIB中的tn3270eClientGroupTable定义的。
A tn3270eRtCollCtlEntry contains the following objects:
tn3270eRtCollCtlEntry包含以下对象：
--------------------------------------------------
1st Index | tn3270eSrvrConfIndex Unsigned32 |
2nd Index | tn3270eClientGroupName Utf8String |
| tn3270eRtCollCtlType BITS |
| tn3270eRtCollCtlSPeriod Unsigned32 |
| tn3270eRtCollCtlSPMult Unsigned32 |
| tn3270eRtCollCtlThreshHigh Unsigned32 |
| tn3270eRtCollCtlThreshLow Unsigned32 |
| tn3270eRtCollCtlIdleCount Unsigned32 |
| tn3270eRtCollCtlBucketBndry1 Unsigned32 |
| tn3270eRtCollCtlBucketBndry2 Unsigned32 |
| tn3270eRtCollCtlBucketBndry3 Unsigned32 |
| tn3270eRtCollCtlBucketBndry4 Unsigned32 |
| tn3270eRtCollCtlRowStatus RowStatus |
--------------------------------------------------
--------------------------------------------------
1st Index | tn3270eSrvrConfIndex Unsigned32 |
2nd Index | tn3270eClientGroupName Utf8String |
| tn3270eRtCollCtlType BITS |
| tn3270eRtCollCtlSPeriod Unsigned32 |
| tn3270eRtCollCtlSPMult Unsigned32 |
| tn3270eRtCollCtlThreshHigh Unsigned32 |
| tn3270eRtCollCtlThreshLow Unsigned32 |
| tn3270eRtCollCtlIdleCount Unsigned32 |
| tn3270eRtCollCtlBucketBndry1 Unsigned32 |
| tn3270eRtCollCtlBucketBndry2 Unsigned32 |
| tn3270eRtCollCtlBucketBndry3 Unsigned32 |
| tn3270eRtCollCtlBucketBndry4 Unsigned32 |
| tn3270eRtCollCtlRowStatus RowStatus |
--------------------------------------------------
The tn3270eRtCollCtlType object controls the type(s) of response time collection that occur, the granularity of the collection, whether dynamic definite responses SHOULD be initiated, and whether notifications SHOULD be generated. This object is of BITS SYNTAX, and thus allows selection of multiple options.
tn3270eRtCollCtlType对象控制发生的响应时间收集的类型、收集的粒度、是否应启动动态确定响应以及是否应生成通知。此对象具有BITS语法，因此允许选择多个选项。
The BITS in the tn3270eRtCollCtlType object have the following meanings:
tn3270eRtCollCtlType对象中的位具有以下含义：
o aggregate(0) - If this bit is set to 1, then data SHOULD be aggregated for the whole client group. In this case there will be only one row created for the collection in the tn3270eRtDataTable. The first two indexes for this row, tn3270eSrvrConfIndex and tn3270eClientGroupName, will have the same values as the indexes for the corresponding tn3270eRtCollCtlEntry. The third and fourth indexes of an aggregated tn3270eRtDataEntry have the values unknown(0) (tn3270eRtDataClientAddrType) and a zero-length octet string (tn3270eRtDataClientAddress). The fifth index, tn3270eRtDataClientPort, has the value 0.
o 聚合（0）-如果此位设置为1，则应聚合整个客户端组的数据。在这种情况下，在tn3270eRtDataTable中只为集合创建一行。此行的前两个索引tn3270eSrvrConfIndex和tn3270eClientGroupName的值与对应tn3270eRtCollCtlEntry的索引值相同。聚合tn3270eRtDataEntry的第三和第四个索引具有未知值（0）（TN3270ErtDataClientAddressType）和零长度八位字符串（tn3270eRtDataClientAddress）。第五个索引tn3270eRtDataClientPort的值为0。
If this bit is set to 0, then a separate entry is created in the tn3270eRtDataTable from each member of the client group. In this case tn3270eRtDataClientAddress contains the client's actual IP
如果此位设置为0，则在tn3270eRtDataTable中从客户端组的每个成员创建一个单独的条目。在本例中，tn3270eRtDataClientAddress包含客户端的实际IP地址
Address, tn3270eRtDataClientAddrType indicates the address type, and tn3270eRtDataClientPort contains the number of the port the client is using for its TN3270/TN3270E session.
地址，tn3270ertDataClientAddressType表示地址类型，tn3270eRtDataClientPort包含客户端用于其TN3270/TN3270E会话的端口号。
o excludeIpComponent(1) - If this bit is set to 1, then the server SHOULD exclude the IP-network component from all the response times for this collection. If the target SNA application specifies DR in any of its replies, this DR will still be passed down to the client, and the client's response will still be forwarded to the application. But this response will play no role in the server's response time calculations.
o excludeIpComponent（1）-如果此位设置为1，则服务器应从该集合的所有响应时间中排除IP网络组件。如果目标SNA应用程序在其任何回复中指定了DR，则此DR仍将传递给客户端，客户端的响应仍将转发给应用程序。但此响应在服务器的响应时间计算中不起作用。
If this bit is set to 0, then the server includes in the collection only those transactions for which it can include an (approximate) IP-network component in the total response time for the transaction. This component MAY be derived from a "natural" DR (if the client supports the RESPONSES function), from a dynamic DR introduced by the server (if the client supports the RESPONSES function and the ddr(2) bit has been set to 1), or from TIMING-MARK processing (if the client supports TIMING-MARKs).
如果此位设置为0，则服务器仅在集合中包含那些可以在事务的总响应时间中包含（近似）IP网络组件的事务。此组件可以从“自然”DR（如果客户端支持响应功能）、从服务器引入的动态DR（如果客户端支持响应功能且ddr（2）位已设置为1）或从定时标记处理（如果客户端支持定时标记）派生而来。
If this bit is set to 1, then the ddr(2) bit is ignored, since there is no reason for the server to request additional responses from the client(s) in the group.
如果此位设置为1，则ddr（2）位将被忽略，因为服务器没有理由从组中的客户端请求其他响应。
o ddr(2) - If this bit is set to 1, then the server SHOULD, for those clients in the group that support the RESPONSES function, add a DR request to the FIC reply in each transaction, and use the client's subsequent response for calculating an (approximate) IP-network component to include in the transaction's total response times.
o ddr（2）-如果此位设置为1，则对于组中支持响应功能的客户端，服务器应在每个事务中向FIC应答添加DR请求，并使用客户端的后续响应计算（近似）IP网络组件，以包括在事务的总响应时间中。
If this bit is set to 0, then the server does not add a DR request that it was not otherwise going to add to any replies from the target SNA application.
如果此位设置为0，则服务器不会向目标SNA应用程序的任何回复中添加本来不打算添加的DR请求。
If the excludeIpComponent(1) bit is set to 1, then this bit is ignored by the server.
如果excludeIpComponent（1）位设置为1，则服务器将忽略该位。
o average(3) - If this bit is set to 1, then the server SHOULD calculate a sliding-window average for the collection, based on the parameters specified for the group.
o 平均值（3）-如果此位设置为1，则服务器应根据为组指定的参数计算集合的滑动窗口平均值。
If this bit is set to 0, then an average is not calculated. In this case the tn3270eRtExceeded and tn3270eRtOkay notifications are not generated, even if the traps(5) bit is set to 1.
如果该位设置为0，则不计算平均值。在这种情况下，即使陷阱（5）位设置为1，也不会生成TN3270ERTOK和TN3270ERTOK通知。
o buckets(4) - If this bit is set to 1, then the server SHOULD create and increment response time buckets for the collection, based on the parameters specified for the group.
o bucket（4）-如果此位设置为1，则服务器应根据为组指定的参数为集合创建并增加响应时间bucket。
If this bit is set to 0, then response time buckets are not created.
如果此位设置为0，则不会创建响应时间存储桶。
o traps(5) - If this bit is set to 1, then a TN3270E Server is enabled to generate notifications pertaining to an tn3270eCollCtlEntry. tn3270CollStart and tn3270CollEnd generation is enabled simply by traps(5) being set to 1. tn3270eRtExceeded and tn3270eRtOkay generation enablement requires that average(3) be set to 1 in addition to the traps(5) requirement.
o 陷阱（5）-如果此位设置为1，则启用TN3270E服务器以生成与tn3270eCollCtlEntry相关的通知。tn3270CollStart和tn3270CollEnd生成只需将陷阱（5）设置为1即可启用。TN3270ERTOK和TN3270ERTOK生成启用除了陷阱（5）要求外，还要求将平均值（3）设置为1。
If traps(5) is set to 0, then none of the notifications defined in this MIB are generated for a particular tn3270eRtCollCtlEntry.
如果陷阱（5）设置为0，则不会为特定TN3270ERTCOLCTL条目生成此MIB中定义的任何通知。
Either the average(3) or the buckets(4) bit MUST be set to 1 in order for response time data collection to occur; both bits MAY be set to 1. If the average(3) bit is set to 1, then the following objects have meaning, and are used to control the calculation of the averages, as well as the generation of the two notifications related to them:
平均值（3）或存储桶（4）位必须设置为1，以便进行响应时间数据采集；两个位都可以设置为1。如果平均（3）位设置为1，则以下对象具有意义，并用于控制平均值的计算以及与之相关的两个通知的生成：
o tn3270eRtCollCtlSPeriod o tn3270eRtCollCtlSPMult o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlIdleCount
o TN3270ERTCOLLCTLESPEROID o tn3270eRtCollCtlSPMult o TN3270ERTCOLLCTLESHIGH o TN3270ERTCOLLCTLESHIGH o TN3270ERTCOLLCTLESHIGH o tn3270eRtCollCtlIdleCount
The previous objects' values are meaningless if the associated average(3) bit is not set to 1.
如果关联的平均（3）位未设置为1，则先前对象的值没有意义。
If the buckets(4) bit is set to 1, then the following objects have meaning, and specify the bucket boundaries:
如果bucket（4）位设置为1，则以下对象具有含义，并指定bucket边界：
o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry2 o tn3270eRtCollCtlBucketBndry3 o tn3270eRtCollCtlBucketBndry4
o TN3270ERTCOLLCLTBACKETBNDRY1至TN3270ERTCOLLCLTBACKETBNDRY2至TN3270ERTCOLLCLTBACKETBNDRY3至TN3270ERTCOLLCLTBACKETBNDRY4
The previous objects' values are meaningless if the associated buckets(4) bit is not set to 1.
如果关联的bucket（4）位未设置为1，则先前对象的值将毫无意义。
If an entry in the tn3270RtCollCtlTable has the value active(1) for its RowStatus, then an implementation SHALL NOT allow Set operations for any objects in the entry except:
如果tn3270RtCollCtlTable中的条目的RowStatus值为active（1），则实现不允许对该条目中的任何对象执行Set操作，除非：
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlRowStatus
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlRowStatus
Either a single entry or multiple entries are created in the tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on whether tn3270eRtCollCtlType in the control entry has aggregate(0) selected. The contents of an entry in the tn3270eRtDataTable depend on the contents of the corresponding entry in the tn3270eRtCollCtlTable: as described above, some objects in the data entry return meaningful values only when the average(3) option is selected in the control entry, while others return meaningful values only when the buckets(4) option is selected. If both options are selected, then all the objects return meaningful values. When an object is not specified to return a meaningful value, an implementation may return any syntactically valid value in response to a Get operation.
根据控制项中的TN3270ERTCOLCTLTYPE是否选择了聚合（0），在tn3270eRtDataTable中为每个TN3270ERTCOLCTLENTRY创建单个项或多个项。tn3270eRtDataTable中某个条目的内容取决于tn3270eRtCollCtlTable中相应条目的内容：如上所述，数据条目中的某些对象仅在控制条目中选择“平均”（3）选项时返回有意义的值，而其他对象仅在存储桶（4）打开时返回有意义的值选项被选中。如果选择了这两个选项，则所有对象都会返回有意义的值。当一个对象没有被指定返回有意义的值时，一个实现可以返回任何语法上有效的值来响应Get操作。
The following objects return meaningful values if and only if the average(3) option was selected in the corresponding tn3270eRtCollCtlEntry:
当且仅当在相应的TN3270ERTCOLLCTLCTL条目中选择了平均值（3）选项时，以下对象才会返回有意义的值：
o tn3270eRtDataAvgRt o tn3270eRtDataAvgIpRt o tn3270eRtDataAvgCountTrans o tn3270eRtDataIntTimeStamp o tn3270eRtDataTotalRts o tn3270eRtDataTotalIpRts o tn3270eRtDataCountTrans o tn3270eRtDataCountDrs o tn3270eRtDataElapsRndTrpSq o tn3270eRtDataElapsIpRtSq
o tn3270eRtDataAvgRt o tn3270eRtDataAvgIpRt o tn3270eRtDataAvgCountTrans o tn3270eRtDataIntTimeStamp o tn3270eRtDataTotalRts o tn3270eRtDataCountTrans o tn3270eRtDataCountDrs o TN3270ErtDataElapsrndRpsq o tn3270eRtDataElapsIpRtSq
The first three objects in this list return values derived from the sliding-window average calculations described earlier. The time of the most recent sample for these calculations is returned in the tn3270eRtDataIntTimeStamp object. The next four objects are normal Counter32 objects, maintaining counts of total response time and total transactions. The last two objects return sum of the squares values, to enable variance calculations by a management application.
此列表中的前三个对象返回的值来自前面描述的滑动窗口平均值计算。这些计算的最新样本的时间在tn3270eRtDataIntTimeStamp对象中返回。接下来的四个对象是普通的Counter32对象，维护总响应时间和总事务的计数。最后两个对象返回平方和值，以启用管理应用程序的方差计算。
The following objects return meaningful values if and only if the buckets(4) option was selected in the corresponding tn3270eRtCollCtlEntry:
当且仅当在相应的TN3270ERTCOLLCTLCTL条目中选择了Bucket（4）选项时，以下对象才会返回有意义的值：
o tn3270eRtDataBucket1Rts o tn3270eRtDataBucket2Rts o tn3270eRtDataBucket3Rts o tn3270eRtDataBucket4Rts o tn3270eRtDataBucket5Rts
o TN3270ERTDABUCKET1至TN3270ERTDABUCKET2至TN3270ERTDABUCKET3RTS至TN3270ERTDABUCKET4RTS至TN3270ERTDABUCKET5RTS
A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a management application to detect when the values of the counter objects in this table may have been reset, or otherwise experienced a discontinuity. A possible cause for such a discontinuity is the TN3270E server's being stopped or restarted. This object returns a meaningful value regardless of which collection control options were selected.
管理应用程序可以使用不连续对象TN3270ERTDataInjunctionTime来检测此表中计数器对象的值何时被重置或以其他方式经历不连续。造成这种中断的一个可能原因是TN3270E服务器正在停止或重新启动。无论选择了哪个集合控件选项，此对象都会返回有意义的值。
An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time was calculated using either the definite response or TIMING-MARK approach.
对象tn3270eRtDataRtMethod确定IP网络时间是使用确定响应还是使用时间标记方法计算的。
When an entry is created in the tn3270eRtCollCtlTable with its tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is automatically created in the tn3270eRtDataTable; this entry's tn3270eRtDataClientAddress has the value of a zero-length octet string, its tn3270eRtDataClientAddrType has the value of unknown(0), and its tn3270eRtDataClientPort has the value 0.
在TN3270ERTCOLCTLTABLE中创建条目时，其TN3270ERTCOLCTLTYPE AGGRATE（0）位设置为1，则会在tn3270eRtDataTable中自动创建条目；此项的tn3270eRtDataClientAddress的值为零长度八位字符串，其TN3270ErtDataClientAddressType的值为unknown（0），其tn3270eRtDataClientPort的值为0。
When an entry is created in the tn3270eRtCollCtlTable with its tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is created in the tn3270eRtDataTable for each member of the client group that currently has a session with the TN3270E server. Entries are subsequently created for clients that the TN3270E server determines to be members of the client group when these clients establish sessions with the server. Entries are also created when clients with existing sessions are added to the group.
在TN3270ERTCOLCTLTABLE中创建条目时，其TN3270ERTCOLCTLTYPE AGGRATE（0）位设置为0，则会在tn3270eRtDataTable中为当前与TN3270E服务器有会话的客户端组的每个成员创建单独的条目。随后，当这些客户端与服务器建立会话时，会为TN3270E服务器确定为客户端组成员的客户端创建条目。将具有现有会话的客户端添加到组时，也会创建条目。
All entries associated with a tn3270eRtCollCtlEntry are deleted from the tn3270eRtDataTable when that entry is deleted from the tn3270eRtCollCtlTable. An entry for an individual client in a client group is deleted when its TCP connection terminates. Once it has been created, a client's entry in the tn3270eRtDataTable remains active as long as the collection's tn3270eRtCollCtlEntry exists, even if the client is removed from the client group for the tn3270eRtCollCtlEntry.
从tn3270eRtCollCtlEntry表中删除与tn3270eRtCollCtlEntry关联的所有条目时，该条目将从tn3270eRtDataTable中删除。客户端组中单个客户端的条目在其TCP连接终止时被删除。创建后，只要集合的tn3270eRtCollCtlEntry存在，tn3270eRtCollCtlEntry中的客户机条目就会保持活动状态，即使该客户机已从TN3270ERTCOLCTLLENTRY的客户机组中删除。
This MIB defines four notifications related to a tn3270eRtDataEntry. If the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications
此MIB定义了四个与tn3270eRtDataEntry相关的通知。如果关联的TN3270ERTCOLLCLTYPE对象的陷阱（5）位设置为1，则tn3270RtCollStart和tn3270RtCollEnd通知
are generated when, respsectively, the tn3270eRtDataEntry is created and deleted. If, in addition, this tn3270eRtCollCtlType object's average(3) bit is set to 1, then the the tn3270eRtExceeded and tn3270eRtOkay notifications are generated when the conditions they report occur.
分别在创建和删除tn3270eRtDataEntry时生成。此外，如果将此TN3270ERTCOLLCLTYPE对象的平均（3）位设置为1，则会在报告的条件发生时生成TN3270ERTEXTED和TN3270ERTOOK通知。
The following notifications are defined by this MIB:
此MIB定义了以下通知：
o tn3270eRtExceeded - The purpose of this notification is to signal that a performance problem has been detected. If average(3) response time data is being collected, then this notification is generated whenever (1) an average response time is first found, on a collection interval boundary, to have exceeded the high threshold tn3270eRtCollCtlThreshHigh specified for the client group, AND (2) the sample on which the average is based is determined to have been a significant one, via the significance algorithm described earlier. This notification is not generated again for a tn3270eRtDataEntry until an average response time falling below the low threshold tn3270eRtCollCtlThreshLow specified for the client group has occurred for the entry.
o TN32702-此通知的目的是表示已检测到性能问题。如果正在收集平均（3）响应时间数据，则每当（1）在收集间隔边界上首次发现平均响应时间超过为客户端组指定的高阈值tn3270eRtCollCtlThreshHigh，以及（2）时，将生成此通知通过前面描述的显著性算法，确定平均值所基于的样本为显著样本。在平均响应时间低于为客户端组指定的低阈值TN3270ERTCOLLCTLTHERSHELOW之前，不会为tn3270eRtDataEntry再次生成此通知。
o tn3270eRtOkay - The purpose of this notification is to signal that a previously reported performance problem has been resolved. If average(3) response time data is being collected, then this notification is generated whenever (1) a tn3270eRtExceeded notification has already been generated, AND (2) an average response time is first found, on a collection interval boundary, to have fallen below the low threshold tn3270eRtCollCtlThreshLow specified for the client group. This notification is not generated again for a tn3270eRtDataEntry until an average response time exceeding the high threshold tn3270eRtCollCtlThreshHigh specified for the client group has occurred for the entry.
o TN3270ERTOOK-此通知的目的是表示先前报告的性能问题已得到解决。如果正在收集平均（3）响应时间数据，则每当（1）已生成TN3270ERTCLThreshOversed通知，并且（2）在收集间隔边界上首次发现平均响应时间低于为客户端组指定的低阈值TN3270ERTCLThreshLow时，就会生成此通知。在平均响应时间超过为客户端组指定的高阈值tn3270eRtCollCtlThreshHigh之前，不会再次为tn3270eRtDataEntry生成此通知。
Taken together, the two preceding notifications serve to minimize the generation of an excessive number of traps in the case of an average response time that oscillates about its high threshold.
综上所述，在平均响应时间围绕其高阈值振荡的情况下，上述两个通知可最大限度地减少过多陷阱的产生。
o tn3270eRtCollStart - This notification is generated whenever data collection begins for a client group, or when a new tn3270eRtDataEntry becomes active. The primary purpose of this notification is signal to a management application that a new client TCP session has been established, and to provide the IP-to-resource mapping for the session. This notification is not critical when average(3) data collection is not being performed for the client group.
o tn3270eRtCollStart—每当客户机组的数据收集开始时，或当新的tn3270eRtDataEntry变为活动状态时，都会生成此通知。此通知的主要目的是向管理应用程序发出已建立新客户端TCP会话的信号，并为会话提供IP到资源的映射。当未对客户端组执行平均（3）次数据收集时，此通知并不重要。
o tn3270eRtCollEnd - This notification is generated whenever a data collection ends. For an aggregate collection, this occurs when the corresponding tn3270eRtCollCtlEntry is deleted. For an individual collection, this occurs either when the tn3270eRtCollCtlEntry is deleted, or when the client's TCP connection terminates. The purpose of this notification is to enable a management application to complete a monitoring function that it was performing, by returning final values for the collection's data objects.
o TN3270ERTCOLEND—每当数据收集结束时，都会生成此通知。对于聚合集合，删除相应的tn3270eRtCollCtlEntry时会发生这种情况。对于单个集合，删除tn3270eRtCollCtlEntry或客户端的TCP连接终止时会发生这种情况。此通知的目的是通过返回集合数据对象的最终值，使管理应用程序能够完成其正在执行的监视功能。
Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory lock that allows cooperating TN3270E-RT-MIB applications to coordinate their use of the tn3270eRtCollCtlTable. When creating a new entry or altering an existing entry in the tn3270eRtCollCtlTable, an application SHOULD make use of tn3270eRtSpinLock to serialize application changes or additions. Since this is an advisory lock, its use by management applications SHALL NOT be enforced by agents. Agents MUST, however, implement the tn3270eRtSpinLock object.
在TN3270E-RT-MIB中，tn3270eRtSpinLock被定义为一个咨询锁，允许协作的TN3270E-RT-MIB应用程序协调其对TN3270ERTCOLCTL表的使用。在TN3270ERTCOLLCTLABLE中创建新条目或更改现有条目时，应用程序应使用tn3270eRtSpinLock序列化应用程序更改或添加。由于这是一个咨询锁，代理不应强制管理应用程序使用它。但是，代理必须实现tn3270eRtSpinLock对象。
TN3270E-RT-MIB DEFINITIONS ::= BEGIN
TN3270E-RT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, Gauge32 FROM SNMPv2-SMI RowStatus, DateAndTime, TimeStamp, TestAndIncr FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF tn3270eSrvrConfIndex, tn3270eClientGroupName, tn3270eResMapElementType FROM TN3270E-MIB IANATn3270eAddrType, IANATn3270eAddress FROM IANATn3270eTC-MIB snanauMIB FROM SNA-NAU-MIB;
从SNMPv2 SMI RowStatus导入模块标识、对象类型、通知类型、计数器32、未签名32、仪表32、日期和时间、时间戳、测试和从SNMPv2 TC导入NCR模块符合性、对象组、通知组从SNMPv2 CONF tn3270esrvconfindex导入、从tn3270eClientGroupName导入、从TN3270E-MIB IANATn3270eAddrType导入TN3270eresmaplementtype、，IANATN3270EADRESS来自IANATn3270eTC MIB snanauMIB来自SNA-NAU-MIB；
tn3270eRtMIB MODULE-IDENTITY LAST-UPDATED "9807270000Z" -- July 27, 1998 ORGANIZATION "TN3270E Working Group" CONTACT-INFO "Kenneth White (kennethw@vnet.ibm.com) IBM Corp. - Dept. BRQA/Bldg. 501/G114 P.O. Box 12195
tn3270eRtMIB模块标识最后更新“980727000MZ”-1998年7月27日组织“TN3270E工作组”联系方式“Kenneth White”(kennethw@vnet.ibm.com)IBM公司-BRQA部/建筑501/G114邮政信箱12195
3039 Cornwallis RTP, NC 27709-2195
3039康沃利斯RTP，北卡罗来纳州27709-2195
Robert Moore (remoore@us.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195
3039 Cornwallis
RTP, NC 27709-2195
(919) 254-4436"
DESCRIPTION
"This module defines a portion of the management
information base (MIB) that enables monitoring of
TN3270 and TN3270E clients' response times by a
TN3270E server."
REVISION "9807270000Z" -- July 27, 1998
DESCRIPTION
"RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
::= { snanauMIB 9 }
-- snanauMIB ::= { mib-2 34 }
Robert Moore (remoore@us.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195
3039 Cornwallis
RTP, NC 27709-2195
(919) 254-4436"
DESCRIPTION
"This module defines a portion of the management
information base (MIB) that enables monitoring of
TN3270 and TN3270E clients' response times by a
TN3270E server."
REVISION "9807270000Z" -- July 27, 1998
DESCRIPTION
"RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
::= { snanauMIB 9 }
-- snanauMIB ::= { mib-2 34 }
-- Top level structure of the MIB
--MIB的顶层结构
tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 }
tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 }
tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 }
tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 }
tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 }
tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 }
-- MIB Objects
--MIB对象
-- Response Time Control Table
--响应时间控制表
tn3270eRtCollCtlTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The response time monitoring collection control table, which allows a management application to control the types of response time data being collected, and the clients for which it is being collected.
TN3270ERTCOLLCTLABLE Tn3270eRtCollCtlEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“响应时间监视收集控制表，它允许管理应用程序控制正在收集的响应时间数据的类型以及正在收集的客户端。
This table is indexed by tn3270eSrvrConfIndex and tn3270eClientGroupName imported from the TN3270E-MIB. tn3270eSrvrConfIndex indicates within a host which TN3270E server an entry applies to. tn3270eClientGroupName it identifies the set of IP clients for which response time data is being collected. The particular IP clients making up the set are identified in the tn3270eClientGroupTable in the TN3270E-MIB."
此表由从TN3270E-MIB导入的TN3270ESRVRConIndex和tn3270eClientGroupName索引。TN3270ESRVRECONDEX指示在主机内应用条目的TN3270E服务器。tn3270eClientGroupName它标识正在为其收集响应时间数据的IP客户端集。组成集合的特定IP客户端在TN3270E-MIB中的tn3270eClientGroupTable中标识。”
::= { tn3270eRtObjects 1}
::= { tn3270eRtObjects 1}
tn3270eRtCollCtlEntry OBJECT-TYPE
SYNTAX Tn3270eRtCollCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the TN3270E response time monitoring collection
control table. To handle the case of multiple TN3270E
servers on the same host, the first index of this table is
the tn3270eSrvrConfIndex from the TN3270E-MIB."
INDEX {
tn3270eSrvrConfIndex, -- Server's index
tn3270eClientGroupName } -- What to collect on
::= { tn3270eRtCollCtlTable 1 }
tn3270eRtCollCtlEntry OBJECT-TYPE
SYNTAX Tn3270eRtCollCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the TN3270E response time monitoring collection
control table. To handle the case of multiple TN3270E
servers on the same host, the first index of this table is
the tn3270eSrvrConfIndex from the TN3270E-MIB."
INDEX {
tn3270eSrvrConfIndex, -- Server's index
tn3270eClientGroupName } -- What to collect on
::= { tn3270eRtCollCtlTable 1 }
Tn3270eRtCollCtlEntry ::= SEQUENCE {
tn3270eRtCollCtlType BITS,
tn3270eRtCollCtlSPeriod Unsigned32,
tn3270eRtCollCtlSPMult Unsigned32,
tn3270eRtCollCtlThreshHigh Unsigned32,
tn3270eRtCollCtlThreshLow Unsigned32,
tn3270eRtCollCtlIdleCount Unsigned32,
tn3270eRtCollCtlBucketBndry1 Unsigned32,
tn3270eRtCollCtlBucketBndry2 Unsigned32,
tn3270eRtCollCtlBucketBndry3 Unsigned32,
tn3270eRtCollCtlBucketBndry4 Unsigned32,
tn3270eRtCollCtlRowStatus RowStatus }
Tn3270eRtCollCtlEntry ::= SEQUENCE {
tn3270eRtCollCtlType BITS,
tn3270eRtCollCtlSPeriod Unsigned32,
tn3270eRtCollCtlSPMult Unsigned32,
tn3270eRtCollCtlThreshHigh Unsigned32,
tn3270eRtCollCtlThreshLow Unsigned32,
tn3270eRtCollCtlIdleCount Unsigned32,
tn3270eRtCollCtlBucketBndry1 Unsigned32,
tn3270eRtCollCtlBucketBndry2 Unsigned32,
tn3270eRtCollCtlBucketBndry3 Unsigned32,
tn3270eRtCollCtlBucketBndry4 Unsigned32,
tn3270eRtCollCtlRowStatus RowStatus }
-- The OID { tn3270eRtCollCtlEntry 1 } is not used
--未使用OID{tn3270eRtCollCtlEntry 1}
tn3270eRtCollCtlType OBJECT-TYPE
SYNTAX BITS {
aggregate(0),
excludeIpComponent(1),
ddr(2),
average(3),
buckets(4),
traps(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls what types of response time data to
collect, whether to summarize the data across the members
of a client group or keep it individually, whether to
introduce dynamic definite responses, and whether to
generate traps.
tn3270eRtCollCtlType OBJECT-TYPE
SYNTAX BITS {
aggregate(0),
excludeIpComponent(1),
ddr(2),
average(3),
buckets(4),
traps(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls what types of response time data to
collect, whether to summarize the data across the members
of a client group or keep it individually, whether to
introduce dynamic definite responses, and whether to
generate traps.
aggregate(0) - Aggregate response time data for the
client group as a whole. If this bit
is set to 0, then maintain response
time data separately for each member
of the client group.
excludeIpComponent(1) - Do not include the IP-network
component in any response times.
ddr(2) - Enable dynamic definite response.
average(3) - Produce an average response time
based on a specified collection
interval.
buckets(4) - Maintain tn3270eRtDataBucket values in
a corresponding tn3270eRtDataEntry,
based on the bucket boundaries specified
in the tn3270eRtCollCtlBucketBndry
objects .
traps(5) - generate the notifications specified
in this MIB module. The
tn3270eRtExceeded and tn3270eRtOkay
notifications are generated only if
average(3) is also specified."
::= { tn3270eRtCollCtlEntry 2 }
aggregate(0) - Aggregate response time data for the
client group as a whole. If this bit
is set to 0, then maintain response
time data separately for each member
of the client group.
excludeIpComponent(1) - Do not include the IP-network
component in any response times.
ddr(2) - Enable dynamic definite response.
average(3) - Produce an average response time
based on a specified collection
interval.
buckets(4) - Maintain tn3270eRtDataBucket values in
a corresponding tn3270eRtDataEntry,
based on the bucket boundaries specified
in the tn3270eRtCollCtlBucketBndry
objects .
traps(5) - generate the notifications specified
in this MIB module. The
tn3270eRtExceeded and tn3270eRtOkay
notifications are generated only if
average(3) is also specified."
::= { tn3270eRtCollCtlEntry 2 }
tn3270eRtCollCtlSPeriod OBJECT-TYPE SYNTAX Unsigned32 (15..86400) -- 15 second min, 24 hour max UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of seconds that defines the sample period. The actual interval is defined as tn3270eRtCollCtlSPeriod times tn3270eRtCollCtlSPMult.
tn3270eRtCollCtlSPeriod对象类型语法Unsigned32（15..86400）--最小15秒，最大24小时单位“秒”最大访问读取创建状态当前描述“定义采样周期的秒数。实际间隔定义为tn3270eRtCollCtlSPeriod乘以tn3270eRtCollCtlSPMult。
The value of this object is used only if the corresponding
tn3270eRtCollCtlType has the average(3) setting."
DEFVAL {20} -- 20 seconds
::= { tn3270eRtCollCtlEntry 3 }
The value of this object is used only if the corresponding
tn3270eRtCollCtlType has the average(3) setting."
DEFVAL {20} -- 20 seconds
::= { tn3270eRtCollCtlEntry 3 }
tn3270eRtCollCtlSPMult OBJECT-TYPE SYNTAX Unsigned32 (1..5760) -- 5760 x SPeriod of 15 is 24 hours UNITS "period" MAX-ACCESS read-create STATUS current DESCRIPTION "The sample period multiplier; this value is multiplied by the sample period, tn3270eRtCollCtlSPeriod, to determine the collection interval.
tn3270eRtCollCtlSPMult对象类型语法Unsigned32（1..5760）--5760 x 15的SPeriod是24小时单位“period”MAX-ACCESS read create STATUS current DESCRIPTION“采样周期乘数”；此值乘以采样周期TN3270ERTCOLLCLSperiod，以确定采集间隔。
Sliding-window average calculation can, if necessary, be disabled, by setting the sample period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample period, tn3270eRtCollCtlSPeriod, to the required collection interval.
如有必要，可以通过将采样周期乘数TN3270ERTCOLLCLTSPMULT设置为1，并将采样周期TN3270ERTCOLLCLTSPRIOD设置为所需的采集间隔来禁用滑动窗口平均值计算。
The value of this object is used only if the corresponding
tn3270eRtCollCtlType has the average(3) setting."
DEFVAL { 30 } -- yields an interval of 10 minutes when
-- used with the default SPeriod value
::= { tn3270eRtCollCtlEntry 4 }
The value of this object is used only if the corresponding
tn3270eRtCollCtlType has the average(3) setting."
DEFVAL { 30 } -- yields an interval of 10 minutes when
-- used with the default SPeriod value
::= { tn3270eRtCollCtlEntry 4 }
tn3270eRtCollCtlThreshHigh OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The threshold for generating a tn3270eRtExceeded notification, signalling that a monitored total response time has exceeded the specified limit. A value of zero for this object suppresses generation of this notification. The value of this object is used only if the corresponding tn3270eRtCollCtlType has average(3) and traps(5) selected.
TN3270ERTCOLCTLTHERSH高对象类型语法无符号32单位“秒”最大访问读取创建状态当前说明“生成TN3270ERT超出通知的阈值，表示受监控的总响应时间已超过指定限制。此对象的值为零将禁止生成此通知。仅当选择了相应的tn3270eRtCollCtlType的平均值（3）和陷阱（5）时，才使用此对象的值。
A tn3270eRtExceeded notification is not generated again for a tn3270eRtDataEntry until an average response time falling below the low threshold tn3270eRtCollCtlThreshLow specified for the client group has occurred for the entry."
在平均响应时间低于为该条目的客户端组指定的低阈值TN3270ERTCollTltThreshLow之前，不会再次为tn3270eRtDataEntry生成TN3270ERTCollThreshLow通知。”
DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 5 }
DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 5 }
tn3270eRtCollCtlThreshLow OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The threshold for generating a tn3270eRtOkay notification, signalling that a monitored total response time has fallen below the specified limit. A value of zero for this object suppresses generation of this notification. The value of this object is used only if the corresponding tn3270eRtCollCtlType has average(3) and traps(5) selected.
tn3270eRtCollCtlThreshLow对象类型语法无符号32单位“秒”最大访问读取创建状态当前说明“生成TN3270ERTOOK通知的阈值，表示受监控的总响应时间已低于指定限制。此对象的值为零将禁止生成此通知。仅当选择了相应的tn3270eRtCollCtlType的平均值（3）和陷阱（5）时，才使用此对象的值。
A tn3270eRtOkay notification is not generated again for a tn3270eRtDataEntry until an average response time
在平均响应时间之前，不会再次为tn3270eRtDataEntry生成TN3270ERTOOK通知
exceeding the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group has occurred for the entry."
DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 6 }
exceeding the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group has occurred for the entry."
DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 6 }
tn3270eRtCollCtlIdleCount OBJECT-TYPE SYNTAX Unsigned32 UNITS "transactions" MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used to determine whether a sample that yields an average response time exceeding the value of tn3270eRtCollCtlThreshHigh was a statistically valid one. If the following statement is true, then the sample was statistically valid, and so a tn3270eRtExceeded notification should be generated:
tn3270eRtCollCtlIdleCount对象类型语法无符号32个单位“事务”最大访问权限读取创建状态当前说明“此对象的值用于确定产生平均响应时间超过TN3270ERTCOLL THERSHIGH值的样本是否为统计有效样本。如果以下陈述为真，则样本在统计上是有效的，因此应生成TN3270ERT通知：
AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount
AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount
This comparison is done only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 1 }
::= { tn3270eRtCollCtlEntry 7 }
This comparison is done only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 1 }
::= { tn3270eRtCollCtlEntry 7 }
tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object defines the range of transaction
response times counted in the Tn3270eRtDataBucket1Rts
object: those less than or equal to this value."
DEFVAL { 10 }
::= { tn3270eRtCollCtlEntry 8 }
tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object defines the range of transaction
response times counted in the Tn3270eRtDataBucket1Rts
object: those less than or equal to this value."
DEFVAL { 10 }
::= { tn3270eRtCollCtlEntry 8 }
tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE SYNTAX Unsigned32 UNITS "tenths of seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object, together with that of the tn3270eRtCollCtlBucketBndry1 object, defines the range of transaction response times counted in the Tn3270eRtDataBucket2Rts object: those greater than the value of the tn3270eRtCollCtlBucketBndry1 object, and
tn3270eRtCollCtlBucketBndry2对象类型语法无符号32单位“十分之一秒”最大访问读取创建状态当前说明“此对象的值与TN3270ErtCollCctlBucketBNDry1对象的值一起定义了Tn3270eRtDataBucket2Rts对象中计算的事务响应时间范围：大于TN3270ErtCollCctlBucketBNDry1对象的值，以及
less than or equal to the value of this object."
DEFVAL { 20 }
::= { tn3270eRtCollCtlEntry 9 }
less than or equal to the value of this object."
DEFVAL { 20 }
::= { tn3270eRtCollCtlEntry 9 }
tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object, together with that of the
tn3270eRtCollCtlBucketBndry2 object, defines the range of
transaction response times counted in the
Tn3270eRtDataBucket3Rts object: those greater than the
value of the tn3270eRtCollCtlBucketBndry2 object, and less
than or equal to the value of this object."
DEFVAL { 50 }
::= { tn3270eRtCollCtlEntry 10 }
tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object, together with that of the
tn3270eRtCollCtlBucketBndry2 object, defines the range of
transaction response times counted in the
Tn3270eRtDataBucket3Rts object: those greater than the
value of the tn3270eRtCollCtlBucketBndry2 object, and less
than or equal to the value of this object."
DEFVAL { 50 }
::= { tn3270eRtCollCtlEntry 10 }
tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE SYNTAX Unsigned32 UNITS "tenths of seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object, together with that of the tn3270eRtCollCtlBucketBndry3 object, defines the range of transaction response times counted in the Tn3270eRtDataBucket4Rts object: those greater than the value of the tn3270eRtCollCtlBucketBndry3 object, and less than or equal to the value of this object.
tn3270eRtCollCtlBucketBndry4对象类型语法无符号32单位“十分之一秒”最大访问读取创建状态当前说明“此对象的值与tn3270eRtCollCtlBucketBndry3对象的值一起定义了Tn3270eRtDataBucket4Rts对象中计算的事务响应时间范围：大于tn3270eRtCollCtlBucketBndry3对象的值，小于或等于此对象的值。
The value of this object also defines the range of
transaction response times counted in the
Tn3270eRtDataBucket5Rts object: those greater than the
value of this object."
DEFVAL { 100 }
::= { tn3270eRtCollCtlEntry 11 }
The value of this object also defines the range of
transaction response times counted in the
Tn3270eRtDataBucket5Rts object: those greater than the
value of this object."
DEFVAL { 100 }
::= { tn3270eRtCollCtlEntry 11 }
tn3270eRtCollCtlRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eRtCollCtlTable. An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table has the side-effect
TN3270ERTCOLLCLTROWSTATUS对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在TN3270ERTCOLLCLTABLE中创建和删除条目。通过将此对象设置为DISTROY（6），可以删除此表中的条目。删除此表中的条目会产生副作用
of removing all entries from the tn3270eRtDataTable
that are associated with the entry being deleted."
::= { tn3270eRtCollCtlEntry 12 }
of removing all entries from the tn3270eRtDataTable
that are associated with the entry being deleted."
::= { tn3270eRtCollCtlEntry 12 }
-- TN3270E Response Time Data Table
--TN3270E响应时间数据表
tn3270eRtDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eRtDataEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The response time data table. Entries in this table are
created based on entries in the tn3270eRtCollCtlTable."
::= { tn3270eRtObjects 2 }
tn3270eRtDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eRtDataEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The response time data table. Entries in this table are
created based on entries in the tn3270eRtCollCtlTable."
::= { tn3270eRtObjects 2 }
tn3270eRtDataEntry OBJECT-TYPE SYNTAX Tn3270eRtDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries in this table are created based upon the tn3270eRtCollCtlTable. When the corresponding tn3270eRtCollCtlType has aggregate(0) specified, a single entry is created in this table, with a tn3270eRtDataClientAddrType of unknown(0), a zero-length octet string value for tn3270eRtDataClientAddress, and a tn3270eRtDataClientPort value of 0. When aggregate(0) is not specified, a separate entry is created for each client in the group.
tn3270eRtDataEntry对象类型语法tn3270eRtDataEntry MAX-ACCESS不可访问状态当前描述“此表中的条目是基于tn3270eRtCollCtlTable创建的。当相应的tn3270eRtCollCtlType指定了聚合（0）时，将在此表中创建一个条目，其中TN3270ErtDataClientAddressType为未知（0），tn3270eRtDataClientAddress的长度为零的八位字节字符串值，tn3270eRtDataClientPort的值为0。如果未指定聚合（0），则会为组中的每个客户端创建一个单独的条目。
Note that the following objects defined within an entry in this table can wrap: tn3270eRtDataTotalRts tn3270eRtDataTotalIpRts tn3270eRtDataCountTrans tn3270eRtDataCountDrs tn3270eRtDataElapsRnTrpSq tn3270eRtDataElapsIpRtSq tn3270eRtDataBucket1Rts tn3270eRtDataBucket2Rts tn3270eRtDataBucket3Rts tn3270eRtDataBucket4Rts tn3270eRtDataBucket5Rts" INDEX { tn3270eSrvrConfIndex, -- Server's local index tn3270eClientGroupName, -- Collection target tn3270eRtDataClientAddrType, tn3270eRtDataClientAddress,
请注意，此表中的条目中定义的以下对象可以换行：tn3270eRtDataTotalRts tn3270eRtDataTotalIpRts tn3270eRtDataCountTrans tn3270eRtDataCountDrs tn3270eRtDataElapsRnTrpSq TN3270ERTDataElapisPrTSQ tn3270eRtDataBucket1Rts tn3270eRtDataBucket2Rts tn3270eRtDataBucket3Rts tn3270eRtDataBucket4Rts tn3270eRtDataBucket5Rts索引{tn3270eSrvrConfIndex，-服务器的本地索引tn3270eClientGroupName，-集合目标tn3270eRtDataClientAddress，tn3270eRtDataClientAddress，
tn3270eRtDataClientPort }
::= { tn3270eRtDataTable 1 }
tn3270eRtDataClientPort }
::= { tn3270eRtDataTable 1 }
Tn3270eRtDataEntry ::= SEQUENCE {
tn3270eRtDataClientAddrType IANATn3270eAddrType,
tn3270eRtDataClientAddress IANATn3270eAddress,
tn3270eRtDataClientPort Unsigned32,
tn3270eRtDataAvgRt Gauge32,
tn3270eRtDataAvgIpRt Gauge32,
tn3270eRtDataAvgCountTrans Gauge32,
tn3270eRtDataIntTimeStamp DateAndTime,
tn3270eRtDataTotalRts Counter32,
tn3270eRtDataTotalIpRts Counter32,
tn3270eRtDataCountTrans Counter32,
tn3270eRtDataCountDrs Counter32,
tn3270eRtDataElapsRndTrpSq Unsigned32,
tn3270eRtDataElapsIpRtSq Unsigned32,
tn3270eRtDataBucket1Rts Counter32,
tn3270eRtDataBucket2Rts Counter32,
tn3270eRtDataBucket3Rts Counter32,
tn3270eRtDataBucket4Rts Counter32,
tn3270eRtDataBucket5Rts Counter32,
tn3270eRtDataRtMethod INTEGER,
tn3270eRtDataDiscontinuityTime TimeStamp
}
Tn3270eRtDataEntry ::= SEQUENCE {
tn3270eRtDataClientAddrType IANATn3270eAddrType,
tn3270eRtDataClientAddress IANATn3270eAddress,
tn3270eRtDataClientPort Unsigned32,
tn3270eRtDataAvgRt Gauge32,
tn3270eRtDataAvgIpRt Gauge32,
tn3270eRtDataAvgCountTrans Gauge32,
tn3270eRtDataIntTimeStamp DateAndTime,
tn3270eRtDataTotalRts Counter32,
tn3270eRtDataTotalIpRts Counter32,
tn3270eRtDataCountTrans Counter32,
tn3270eRtDataCountDrs Counter32,
tn3270eRtDataElapsRndTrpSq Unsigned32,
tn3270eRtDataElapsIpRtSq Unsigned32,
tn3270eRtDataBucket1Rts Counter32,
tn3270eRtDataBucket2Rts Counter32,
tn3270eRtDataBucket3Rts Counter32,
tn3270eRtDataBucket4Rts Counter32,
tn3270eRtDataBucket5Rts Counter32,
tn3270eRtDataRtMethod INTEGER,
tn3270eRtDataDiscontinuityTime TimeStamp
}
tn3270eRtDataClientAddrType OBJECT-TYPE
SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the type of address represented by the value
of tn3270eRtDataClientAddress. The value unknown(0) is
used if aggregate data is being collected for the client
group."
::= { tn3270eRtDataEntry 1 }
tn3270eRtDataClientAddrType OBJECT-TYPE
SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the type of address represented by the value
of tn3270eRtDataClientAddress. The value unknown(0) is
used if aggregate data is being collected for the client
group."
::= { tn3270eRtDataEntry 1 }
tn3270eRtDataClientAddress OBJECT-TYPE
SYNTAX IANATn3270eAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains the IP address of the TN3270 client being
monitored. A zero-length octet string is used if
aggregate data is being collected for the client group."
::= { tn3270eRtDataEntry 2 }
tn3270eRtDataClientAddress OBJECT-TYPE
SYNTAX IANATn3270eAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains the IP address of the TN3270 client being
monitored. A zero-length octet string is used if
aggregate data is being collected for the client group."
::= { tn3270eRtDataEntry 2 }
tn3270eRtDataClientPort OBJECT-TYPE
tn3270eRtDataClientPort对象类型
SYNTAX Unsigned32(0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains the client port number of the TN3270 client being
monitored. The value 0 is used if aggregate data is being
collected for the client group, or if the
tn3270eRtDataClientAddrType identifies an address type that
does not support ports."
::= { tn3270eRtDataEntry 3 }
SYNTAX Unsigned32(0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains the client port number of the TN3270 client being
monitored. The value 0 is used if aggregate data is being
collected for the client group, or if the
tn3270eRtDataClientAddrType identifies an address type that
does not support ports."
::= { tn3270eRtDataEntry 3 }
tn3270eRtDataAvgRt OBJECT-TYPE
SYNTAX Gauge32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average total response time measured over the last
collection interval."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 4 }
tn3270eRtDataAvgRt OBJECT-TYPE
SYNTAX Gauge32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average total response time measured over the last
collection interval."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 4 }
tn3270eRtDataAvgIpRt OBJECT-TYPE
SYNTAX Gauge32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average IP response time measured over the last
collection interval."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 5 }
tn3270eRtDataAvgIpRt OBJECT-TYPE
SYNTAX Gauge32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average IP response time measured over the last
collection interval."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 5 }
tn3270eRtDataAvgCountTrans OBJECT-TYPE SYNTAX Gauge32 UNITS "transactions" MAX-ACCESS read-only STATUS current DESCRIPTION "The sliding transaction count used for calculating the values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects. The actual transaction count is available in the tn3270eRtDataCountTrans object.
tn3270eRtDataAvgCountTrans对象类型语法量表32单元“事务”MAX-ACCESS只读状态当前描述“用于计算tn3270eRtDataAvgRt和TN3270ErtDataAvgGiPrt对象值的滑动事务计数。实际事务计数在tn3270eRtDataCountTrans对象中可用。
The initial value of this object, before any averages have
been calculated, is 0."
::= { tn3270eRtDataEntry 6 }
The initial value of this object, before any averages have
been calculated, is 0."
::= { tn3270eRtDataEntry 6 }
tn3270eRtDataIntTimeStamp OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The date and time of the last interval that tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgCountTrans were calculated.
tn3270eRtDataIntTimeStamp对象类型语法DateAndTime MAX-ACCESS只读状态当前描述“计算tn3270eRtDataAvgRt、tn3270eRtDataAvgIpRt和tn3270eRtDataAvgCountTrans的最后一个间隔的日期和时间。
Prior to the calculation of the first interval
averages, this object returns the value
0x0000000000000000000000. When this value is
returned, the remaining objects in the entry have
no significance."
::= { tn3270eRtDataEntry 7 }
Prior to the calculation of the first interval
averages, this object returns the value
0x0000000000000000000000. When this value is
returned, the remaining objects in the entry have
no significance."
::= { tn3270eRtDataEntry 7 }
tn3270eRtDataTotalRts OBJECT-TYPE SYNTAX Counter32 UNITS "tenths of seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the total response times collected.
tn3270eRtDataTotalRts对象类型语法计数器32个单位“十分之一秒”MAX-ACCESS只读状态当前描述“收集的总响应时间计数。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 8 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 8 }
tn3270eRtDataTotalIpRts OBJECT-TYPE SYNTAX Counter32 UNITS "tenths of seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the total IP-network response times collected.
tn3270eRtDataTotalIpRts对象类型语法计数器32个单位“十分之一秒”MAX-ACCESS只读状态当前描述“收集的IP网络总响应时间计数。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 9 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 9 }
tn3270eRtDataCountTrans OBJECT-TYPE SYNTAX Counter32 UNITS "transactions" MAX-ACCESS read-only STATUS current
tn3270eRtDataCountTrans对象类型语法计数器32单元“事务”最大访问只读状态当前
DESCRIPTION "The count of the total number of transactions detected.
DESCRIPTION“检测到的事务总数的计数。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 10 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 10 }
tn3270eRtDataCountDrs OBJECT-TYPE SYNTAX Counter32 UNITS "definite responses" MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the total number of definite responses detected.
tn3270eRtDataCountDrs对象类型语法计数器32单元“明确响应”MAX-ACCESS只读状态当前描述“检测到的明确响应总数的计数”。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 11 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 11 }
tn3270eRtDataElapsRndTrpSq OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds squared"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the elapsed round trip time squared. The sum
of the squares is kept in order to enable calculation of
a variance."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 12 }
tn3270eRtDataElapsRndTrpSq OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds squared"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the elapsed round trip time squared. The sum
of the squares is kept in order to enable calculation of
a variance."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 12 }
tn3270eRtDataElapsIpRtSq OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds squared"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the elapsed IP round trip time squared.
The sum of the squares is kept in order to enable
calculation of a variance."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 13 }
tn3270eRtDataElapsIpRtSq OBJECT-TYPE
SYNTAX Unsigned32
UNITS "tenths of seconds squared"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the elapsed IP round trip time squared.
The sum of the squares is kept in order to enable
calculation of a variance."
DEFVAL { 0 }
::= { tn3270eRtDataEntry 13 }
tn3270eRtDataBucket1Rts OBJECT-TYPE SYNTAX Counter32
tn3270eRtDataBucket1Rts对象类型语法计数器32
MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the response times falling into bucket 1.
MAX-ACCESS只读状态当前描述“进入存储桶1的响应时间计数。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 14 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 14 }
tn3270eRtDataBucket2Rts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the response times falling into bucket 2.
TN3270ERTDABATBUCKET2RTS对象类型语法计数器32 MAX-ACCESS只读状态当前描述“落入存储桶2的响应时间计数”。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 15 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 15 }
tn3270eRtDataBucket3Rts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the response times falling into bucket 3.
tn3270eRtDataBucket3Rts对象类型语法计数器32 MAX-ACCESS只读状态当前描述“落入存储桶3的响应时间计数”。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 16 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 16 }
tn3270eRtDataBucket4Rts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the response times falling into bucket 4.
tn3270eRtDataBucket4Rts对象类型语法计数器32 MAX-ACCESS只读状态当前描述“落入存储桶4的响应时间计数”。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 17 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 17 }
tn3270eRtDataBucket5Rts OBJECT-TYPE SYNTAX Counter32
tn3270eRtDataBucket5Rts对象类型语法计数器32
MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the response times falling into bucket 5.
MAX-ACCESS只读状态当前描述“落入存储桶5的响应时间计数。
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 18 }
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 18 }
tn3270eRtDataRtMethod OBJECT-TYPE
SYNTAX INTEGER {
none(0),
responses(1),
timingMark(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object indicates the method that was
used in calculating the IP network time.
tn3270eRtDataRtMethod OBJECT-TYPE
SYNTAX INTEGER {
none(0),
responses(1),
timingMark(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object indicates the method that was
used in calculating the IP network time.
The value 'none(0) indicates that response times were not
calculated for the IP network."
::= { tn3270eRtDataEntry 19 }
The value 'none(0) indicates that response times were not
calculated for the IP network."
::= { tn3270eRtDataEntry 19 }
tn3270eRtDataDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at
which one or more of this entry's counter objects
suffered a discontinuity. This may happen if a TN3270E
server is stopped and then restarted, and local methods
are used to set up collection policy
(tn3270eRtCollCtlTable entries)."
::= { tn3270eRtDataEntry 20 }
tn3270eRtDataDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at
which one or more of this entry's counter objects
suffered a discontinuity. This may happen if a TN3270E
server is stopped and then restarted, and local methods
are used to set up collection policy
(tn3270eRtCollCtlTable entries)."
::= { tn3270eRtDataEntry 20 }
tn3270eRtSpinLock OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "An advisory lock used to allow cooperating TN3270E-RT-MIB applications to coordinate their use of the tn3270eRtCollCtlTable.
tn3270eRtSpinLock对象类型语法TestAndIncr MAX-ACCESS读写状态当前描述“用于允许协作的TN3270E-RT-MIB应用程序协调其对TN3270ERTcollctlable的使用的建议锁。
When creating a new entry or altering an existing entry in the tn3270eRtCollCtlTable, an application should make use of tn3270eRtSpinLock to serialize application changes or additions.
在TN3270ERTCOLLCTLABLE中创建新条目或更改现有条目时，应用程序应使用tn3270eRtSpinLock序列化应用程序更改或添加。
Since this is an advisory lock, the use of this lock is
not enforced."
::= { tn3270eRtObjects 3 }
Since this is an advisory lock, the use of this lock is
not enforced."
::= { tn3270eRtObjects 3 }
-- Notifications
--通知
tn3270eRtExceeded NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when the average response
time, tn3270eRtDataAvgRt, exceeds
tn3270eRtCollCtlThresholdHigh at the end of a collection
interval specified by tn3270eCollCtlSPeriod
times tn3270eCollCtlSPMult. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3) set
for this notification to be generated. In addition,
tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and
tn3270eRtDataAvgRt are algorithmically compared to
tn3270eRtCollCtlIdleCount for determination if this
notification will be suppressed."
::= { tn3270eRtNotifications 1 }
tn3270eRtExceeded NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when the average response
time, tn3270eRtDataAvgRt, exceeds
tn3270eRtCollCtlThresholdHigh at the end of a collection
interval specified by tn3270eCollCtlSPeriod
times tn3270eCollCtlSPMult. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3) set
for this notification to be generated. In addition,
tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and
tn3270eRtDataAvgRt are algorithmically compared to
tn3270eRtCollCtlIdleCount for determination if this
notification will be suppressed."
::= { tn3270eRtNotifications 1 }
tn3270eRtOkay NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when the average response
time, tn3270eRtDataAvgRt, falls below
tn3270eRtCollCtlThresholdLow at the end of a collection
interval specified by tn3270eCollCtlSPeriod times
tn3270eRtOkay NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when the average response
time, tn3270eRtDataAvgRt, falls below
tn3270eRtCollCtlThresholdLow at the end of a collection
interval specified by tn3270eCollCtlSPeriod times
tn3270eCollCtlSPMult, after a tn3270eRtExceeded
notification was generated. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3)
set for this notification to be generated."
::= { tn3270eRtNotifications 2 }
tn3270eCollCtlSPMult, after a tn3270eRtExceeded
notification was generated. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3)
set for this notification to be generated."
::= { tn3270eRtNotifications 2 }
tn3270eRtCollStart NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataRtMethod, -- type of collection
tn3270eResMapElementType -- type of resource
}
STATUS current
DESCRIPTION
"This notification is generated when response time data
collection is enabled for a member of a client group.
In order for this notification to occur the corresponding
tn3270eRtCollCtlType must have traps(5) selected.
tn3270eRtCollStart NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataRtMethod, -- type of collection
tn3270eResMapElementType -- type of resource
}
STATUS current
DESCRIPTION
"This notification is generated when response time data
collection is enabled for a member of a client group.
In order for this notification to occur the corresponding
tn3270eRtCollCtlType must have traps(5) selected.
tn3270eResMapElementType contains a valid value only if
tn3270eRtDataClientAddress contains a valid address
(rather than a zero-length octet string)."
::= { tn3270eRtNotifications 3 }
tn3270eResMapElementType contains a valid value only if
tn3270eRtDataClientAddress contains a valid address
(rather than a zero-length octet string)."
::= { tn3270eRtNotifications 3 }
tn3270eRtCollEnd NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRts,
tn3270eRtDataTotalIpRts,
tn3270eRtDataCountTrans,
tn3270eRtDataCountDrs,
tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1Rts,
tn3270eRtDataBucket2Rts,
tn3270eRtDataBucket3Rts,
tn3270eRtDataBucket4Rts,
tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when an tn3270eRtDataEntry
is deleted after being active (actual data collected), in
order to enable a management application monitoring an
tn3270eRtCollEnd NOTIFICATION-TYPE
OBJECTS {
tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRts,
tn3270eRtDataTotalIpRts,
tn3270eRtDataCountTrans,
tn3270eRtDataCountDrs,
tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1Rts,
tn3270eRtDataBucket2Rts,
tn3270eRtDataBucket3Rts,
tn3270eRtDataBucket4Rts,
tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod
}
STATUS current
DESCRIPTION
"This notification is generated when an tn3270eRtDataEntry
is deleted after being active (actual data collected), in
order to enable a management application monitoring an
tn3270eRtDataEntry to get the entry's final values. Note
that the corresponding tn3270eCollCtlType must have traps(5)
set for this notification to be generated."
::= { tn3270eRtNotifications 4 }
tn3270eRtDataEntry to get the entry's final values. Note
that the corresponding tn3270eCollCtlType must have traps(5)
set for this notification to be generated."
::= { tn3270eRtNotifications 4 }
-- Conformance Statement
--一致性声明
tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 }
tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 }
tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 }
tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 }
-- Compliance statements
--合规声明
tn3270eRtCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for agents that support the TN327E-RT-MIB." MODULE -- this module MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup }
tn3270eRtCompliance MODULE-COMPLIANCE STATUS当前描述“支持TN327E-RT-MIB的代理的符合性声明”。模块--此模块为必填的组{tn3270eRtGroup，tn3270eRtNotGroup}
OBJECT tn3270eRtCollCtlType MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象TN3270ERTCOLLCLTYPE MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlSPeriod MIN-ACCESS read-only DESCRIPTION "The agent is not required to allow the user to change the default value of this object, and is allowed to use a different default."
对象TN3270ERTCOLLCLTSPERIOD MIN-ACCESS只读说明“不要求代理允许用户更改此对象的默认值，并且允许使用其他默认值。”
OBJECT tn3270eRtCollCtlSPMult MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象TN3270ERTCOLLCLTSPMULT MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlThreshHigh MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象TN3270ERTCollThresh High MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlThreshLow MIN-ACCESS read-only DESCRIPTION
对象TN3270ERTCollThreshLow最小访问只读描述
"The agent is not required to support a SET operation to this object in the absence of adequate security."
“如果没有足够的安全性，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlIdleCount MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象tn3270eRtCollCtlIdleCount MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlBucketBndry1 MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象tn3270eRtCollCtlBucketBndry1 MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlBucketBndry2 MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象tn3270eRtCollCtlBucketBndry2 MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlBucketBndry3 MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象tn3270eRtCollCtlBucketBndry3 MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlBucketBndry4 MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a SET operation to this object in the absence of adequate security."
对象tn3270eRtCollCtlBucketBndry4 MIN-ACCESS只读说明“在缺乏足够安全性的情况下，代理不需要支持对此对象的设置操作。”
OBJECT tn3270eRtCollCtlRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and only one of the six
enumerated values for the RowStatus textual convention
need be supported, specifically: active(1)."
OBJECT tn3270eRtCollCtlRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and only one of the six
enumerated values for the RowStatus textual convention
need be supported, specifically: active(1)."
::= {tn3270eRtCompliances 1 }
::= {tn3270eRtCompliances 1 }
-- Group definitions
--组定义
tn3270eRtGroup OBJECT-GROUP
TN3270ERTGOUP对象组
OBJECTS {
tn3270eRtCollCtlType,
tn3270eRtCollCtlSPeriod,
tn3270eRtCollCtlSPMult,
tn3270eRtCollCtlThreshHigh,
tn3270eRtCollCtlThreshLow,
tn3270eRtCollCtlIdleCount,
tn3270eRtCollCtlBucketBndry1,
tn3270eRtCollCtlBucketBndry2,
tn3270eRtCollCtlBucketBndry3,
tn3270eRtCollCtlBucketBndry4,
tn3270eRtCollCtlRowStatus,
tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRts,
tn3270eRtDataTotalIpRts,
tn3270eRtDataCountTrans,
tn3270eRtDataCountDrs,
tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1Rts,
tn3270eRtDataBucket2Rts,
tn3270eRtDataBucket3Rts,
tn3270eRtDataBucket4Rts,
tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod,
tn3270eRtSpinLock }
STATUS current
DESCRIPTION
"This group is mandatory for all implementations that
support the TN3270E-RT-MIB. "
::= { tn3270eRtGroups 1 }
OBJECTS {
tn3270eRtCollCtlType,
tn3270eRtCollCtlSPeriod,
tn3270eRtCollCtlSPMult,
tn3270eRtCollCtlThreshHigh,
tn3270eRtCollCtlThreshLow,
tn3270eRtCollCtlIdleCount,
tn3270eRtCollCtlBucketBndry1,
tn3270eRtCollCtlBucketBndry2,
tn3270eRtCollCtlBucketBndry3,
tn3270eRtCollCtlBucketBndry4,
tn3270eRtCollCtlRowStatus,
tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRts,
tn3270eRtDataTotalIpRts,
tn3270eRtDataCountTrans,
tn3270eRtDataCountDrs,
tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1Rts,
tn3270eRtDataBucket2Rts,
tn3270eRtDataBucket3Rts,
tn3270eRtDataBucket4Rts,
tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod,
tn3270eRtSpinLock }
STATUS current
DESCRIPTION
"This group is mandatory for all implementations that
support the TN3270E-RT-MIB. "
::= { tn3270eRtGroups 1 }
tn3270eRtNotGroup NOTIFICATION-GROUP
NOTIFICATIONS {
tn3270eRtExceeded,
tn3270eRtOkay,
tn3270eRtCollStart,
tn3270eRtCollEnd
}
tn3270eRtNotGroup NOTIFICATION-GROUP
NOTIFICATIONS {
tn3270eRtExceeded,
tn3270eRtOkay,
tn3270eRtCollStart,
tn3270eRtCollEnd
}
STATUS current
DESCRIPTION
"The notifications that must be supported when the
TN3270E-RT-MIB is implemented. "
::= { tn3270eRtGroups 2 }
STATUS current
DESCRIPTION
"The notifications that must be supported when the
TN3270E-RT-MIB is implemented. "
::= { tn3270eRtGroups 2 }
END
终止
Certain management information defined in this MIB may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information SHOULD be employed in such environments. An authentication protocol is defined in [12]. A protocol for access control is defined in [15].
在某些网络环境中，此MIB中定义的某些管理信息可能被视为敏感信息。因此，在这样的环境中，应该对接收到的SNMP请求进行身份验证，并控制对管理信息的访问。[12]中定义了认证协议。[15]中定义了访问控制协议。
Several objects in this MIB allow write access or provide for row creation. Allowing this support in a non-secure environment can have a negative effect on network operations. It is RECOMMENDED that implementers seriously consider whether set operations or row creation SHOULD be allowed without providing, at a minimum, authentication of request origin. It is RECOMMENDED that without such support that the following objects be implemented as read-only:
此MIB中的多个对象允许写访问或提供行创建。在不安全的环境中允许这种支持可能会对网络操作产生负面影响。建议实施者认真考虑是否应该允许设置操作或行创建，而不至少提供请求源的身份验证。建议在没有此类支持的情况下，将以下对象实现为只读：
o tn3270eRtCollCtlType o tn3270eRtCollCtlSPeriod o tn3270eRtCollCtlSPMult o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlIdleCount o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry2 o tn3270eRtCollCtlBucketBndry3 o tn3270eRtCollCtlBucketBndry4 o tn3270eRtCollCtlRowStatus
o TN3270Ertcollcltype o TN3270Ertcollcltspriod o TN3270Ertcollcltspmult o TN3270ErtcollcltreshHigh o TN3270ErtcollcltreshLow o TN3270ErtcollcltlbucketbNdry1 o TN3270ErtcollcltlbucketbNdry2 o TN3270ErtcollclclclclbucketbNdry3 o TN3270ErtcollcollclclbucketbNdry4 o o tn3270ErtcollclCllcRowStatus
The administrative method to use to create and manage the tn3270eRtCollCtlTable when SET support is not allowed is outside of the scope of this memo.
不允许设置支持时用于创建和管理TN3270ERTCOLLCTLABLE的管理方法不在本备忘录的范围内。
The IETF takes no position regarding the validity or scope of any intellectual property 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
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可的范围，不采取任何立场
might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 Secretariat.
可能可用，也可能不可用；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This document is a product of the TN3270E Working Group. Special thanks are due to Derek Bolton and Michael Boe of Cisco Systems for their numerous comments and suggestions for improving the structure of this MIB. Thanks also to Randy Presuhn of BMC Software for his valuable review comments on several versions of the document.
本文件是TN3270E工作组的产品。特别感谢思科系统公司的Derek Bolton和Michael Boe对改进MIB结构提出的众多意见和建议。还要感谢BMC软件公司的Randy Presohn对该文档的几个版本提出了宝贵的评论。
[1] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, January 1998.
[1] Harrington D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2271，1998年1月。
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[5] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[6] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[7] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998.
[11] Case，J.，Harrington D.，Presuhn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 22721998年1月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 22741998年1月。
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 22731998年1月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 22751998年1月。
[16] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983.
[16] Postel，J.和J.Reynolds，“Telnet协议规范”，STD 8，RFC 854，1983年5月。
[17] Postel, J. and J. Reynolds, "Telnet Timing Mark Option", STD 31, RFC 860, May 1983.
[17] Postel，J.和J.Reynolds，“Telnet定时标记选项”，STD 31，RFC 860，1983年5月。
[18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
[18] Rekhter，J.，“Telnet 3270体制选择”，RFC 10411988年1月。
[19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
[19] Kelly，B.，“TN3270增强”，RFC 23551998年6月。
[20] White, K. and R. Moore, "Base Definitions of Managed Objects for TN3270E Using SMIv2", RFC 2561, April 1999.
[20] White，K.和R.Moore，“使用SMIv2的TN3270E托管对象的基本定义”，RFC 2561，1999年4月。
[21] IBM, International Technical Support Centers, "Response Time Data Gathering", GG24-3212-01, November 1990.
[21] IBM，国际技术支持中心，“响应时间数据收集”，GG24-3212-01，1990年11月。
[22] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[22] Hovey，R.和S.Bradner，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。
[23] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[23] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
Kenneth D. White Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
Kenneth D.White部门BRQA/Bldg.501/G114 IBM公司邮箱12195 3039美国北卡罗来纳州康沃利斯三角研究园，邮编27709
EMail: kennethw@vnet.ibm.com
EMail: kennethw@vnet.ibm.com
Robert Moore Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
美国北卡罗来纳州康沃利斯研究三角公园12195 3039号IBM公司信箱501/G114号楼BRQA/BRQA部门
Phone: +1-919-254-7507
EMail: remoore@us.ibm.com
Phone: +1-919-254-7507
EMail: remoore@us.ibm.com
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。