draft-ietf-tn3270e-rt-mib-07.txt   rfc2562.txt 
TN3270E Working Group Kenneth White Network Working Group K. White
INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-07.txt> IBM Corp. Request for Comments: 2562 IBM Corp.
Expiration Date: January, 1999 Robert Moore Category: Standards Track R. Moore
IBM Corp. IBM Corp.
July 1998 April 1999
Definitions of Protocol and Managed Objects for Definitions of Protocol and Managed Objects for
TN3270E Response Time Collection Using SMIv2 TN3270E Response Time Collection Using SMIv2
(TN3270E-RT-MIB) (TN3270E-RT-MIB)
<draft-ietf-tn3270e-rt-mib-07.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its Areas, and Internet community, and requests discussion and suggestions for
its Working Groups. Note that other groups may also distribute working improvements. Please refer to the current edition of the "Internet
documents as Internet Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or
"work in progress."
Please check the I-D abstract listing contained in each Internet Draft
directory to learn the current status of this or any Internet Draft.
Distribution of this document is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines the protocol and the Management Information Base (MIB) This memo defines the protocol and the Management Information Base
for performing response time data collection on TN3270 and TN3270E (MIB) for performing response time data collection on TN3270 and
sessions by a TN3270E server. The response time data collected by a TN3270E sessions by a TN3270E server. The response time data
TN3270E server is structured to support both validation of service level collected by a TN3270E server is structured to support both
agreements and performance monitoring of TN3270 and TN3270E Sessions. validation of service level agreements and performance monitoring of
This MIB has as a prerequisite the TN3270E-MIB, reference [20]. TN3270 and TN3270E Sessions. This MIB has as a prerequisite the
TN3270E-MIB, reference [20].
TN3270E, defined by RFC 2355 [19], refers to the enhancements made to TN3270E, defined by RFC 2355 [19], refers to the enhancements made to
the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC
1041 [18], RFC 854 [16], and RFC 860 [17] for a sample of what is meant 1041 [18], STD 8, RFC 854 [16], and STD 31, RFC 860 [17] for a sample
by TN3270 practices. of what is meant by TN3270 practices.
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3
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 . . . . . . 9
3.4 Timestamp Calculation . . . . . . . . . . . . . . . . . . . . 10
3.4.1 DR Usage . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2 TIMING-MARK Usage . . . . . . . . . . . . . . . . . . . . 11
3.5 Performance Data Modelling . . . . . . . . . . . . . . . . . . 13
3.5.1 Averaging Response Times . . . . . . . . . . . . . . . . . 13
3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . . . 15
4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 16
4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . . . 17
4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . . . 19
4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 22
5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38
7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 39
8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39
9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 42 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
1.0 Introduction 1.0 Introduction
This document is a product of the TN3270E Working Group. It defines a This document is a product of the TN3270E Working Group. It defines
protocol and a MIB module to enable a TN3270E server to collect and keep a protocol and a MIB module to enable a TN3270E server to collect and
track of response time data for both TN3270 and TN3270E clients. Basis keep track of response time data for both TN3270 and TN3270E clients.
for implementing this MIB: Basis for implementing this MIB:
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E
SMIv2 [20] Using SMIv2 [20]
o TN3270E RFCs o TN3270E RFCs
o Telnet Timing Mark Option RFC [17]. o Telnet Timing Mark Option RFC [17].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference [23]. document are to be interpreted as described in RFC 2119, reference
[23].
2.0 The SNMP Network Management Framework 2.0 The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC Management Information (SMI) is called SMIv1 and described in STD
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. second version, called SMIv2, is described in RFC 1902 [5], RFC
1903 [6] and RFC 1904 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
third version of the message protocol is called SNMPv3 and described 1906 [10]. The third version of the message protocol is called
in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274
[12].
o Protocol operations for accessing management information. The first o Protocol operations for accessing management information. The
set of protocol operations and associated PDU formats is described first set of protocol operations and associated PDU formats is
in RFC 1157 [8]. A second set of protocol operations and associated described in STD 15, RFC 1157 [8]. A second set of protocol
PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and the o A set of fundamental applications described in RFC 2273 [14] and
view-based access control mechanism described in RFC 2275 [15]. the view-based access control mechanism described in RFC 2275
[15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3.0 Response Time Collection Methodology 3.0 Response Time Collection Methodology
This section explains the methodology and approach used by the MIB This section explains the methodology and approach used by the MIB
defined by this memo for response time data collection by a TN3270E defined by this memo for response time data collection by a TN3270E
server. server.
3.1 General Response Time Collection 3.1 General Response Time Collection
Two primary methods exist for measuring response times in SNA networks: Two primary methods exist for measuring response times in SNA
networks:
o The Systems Network Architecture Management Services (SNA/MS) o The Systems Network Architecture Management Services (SNA/MS)
Response Time Monitoring (RTM) function. Response Time Monitoring (RTM) function.
o Timestamping using definite response flows. o Timestamping using definite response flows.
This memo defines an approach using definite responses to timestamp the This memo defines an approach using definite responses to timestamp
flows between a client and its TN3270E server, rather than by use of the the flows between a client and its TN3270E server, rather than by use
RTM method. Extensions to the SNA/MS RTM flow were considered, but this of the RTM method. Extensions to the SNA/MS RTM flow were considered,
approach was deemed unsuitable since not all TN3270E server but this approach was deemed unsuitable since not all TN3270E server
implementations have access to their underlying SNA stacks. The RTM implementations have access to their underlying SNA stacks. The RTM
concepts of keeping response time buckets for service level agreements concepts of keeping response time buckets for service level
and of interval-based response time collection for performance agreements and of interval-based response time collection for
monitoring are preserved in the MIB module defined in this memo. performance monitoring are preserved in the MIB module defined in
this memo.
As mentioned, this memo focuses on using definite responses to timestamp As mentioned, this memo focuses on using definite responses to
the flows between a client and its TN3270E server for generating timestamp the flows between a client and its TN3270E server for
performance data. Use of a definite response flow requires that the generating performance data. Use of a definite response flow
client supports TN3270E with the RESPONSES function negotiated. The requires that the client supports TN3270E with the RESPONSES function
TN3270 TIMING-MARK option can be used instead of definite response for negotiated. The TN3270 TIMING-MARK option can be used instead of
supporting TN3270 clients or TN3270E clients that don't support definite response for supporting TN3270 clients or TN3270E clients
RESPONSES. This document focuses first on defining the protocol and that don't support RESPONSES. This document focuses first on
methods for generating performance data using definite responses, and defining the protocol and methods for generating performance data
then describes how the TIMING-MARK option can be used instead of using definite responses, and then describes how the TIMING-MARK
definite response. option can be used instead of definite response.
In an SNA network, a transaction between a client Logical Unit (LU) and In an SNA network, a transaction between a client Logical Unit (LU)
a target host in general looks as follows: and a target host in general looks as follows:
------------------------------------------------ ------------------------------------------------
| | | |
| Client LU Target SNA Host | | Client LU Target SNA Host |
| | | |
| Timestamps | | Timestamps |
| request A | | request A |
| -----------------------------------------> | | -----------------------------------------> |
| reply(DR) B | | | reply(DR) B | |
| <---------------------------------------< | | <---------------------------------------< |
| | +/-RSP C | | | +/-RSP C |
| >---------------------------------------> | | >---------------------------------------> |
| | | |
| DR: Definite Response requested | | DR: Definite Response requested |
| +/-RSP: Definite Response | | +/-RSP: Definite Response |
| | | |
------------------------------------------------ ------------------------------------------------
This transaction is a simple one, and is being used only to illustrate This transaction is a simple one, and is being used only to
how timestamping at a target SNA host can be used to generate response illustrate how timestamping at a target SNA host can be used to
times. An IBM redbook [12] provides a more detailed description of generate response times. An IBM redbook [12] provides a more
response time collection for a transaction of this type. Note that for detailed description of response time collection for a transaction of
the purpose of calculating an approximation for network transit time, it this type. Note that for the purpose of calculating an approximation
doesn't matter if the response is positive or negative. Two response for network transit time, it doesn't matter if the response is
time values are typically calculated: positive or negative. Two response time values are typically
calculated:
o Host Transit Time: Timestamp B - Timestamp A o Host Transit Time: Timestamp B - Timestamp A
o Network Transit Time: Timestamp C - Timestamp B o Network Transit Time: Timestamp C - Timestamp B
Network transit time is an approximation for the amount of time that a Network transit time is an approximation for the amount of time that
transaction requires to flow across a network, since the response flow a transaction requires to flow across a network, since the response
is being substituted for the request flow at the start of the flow is being substituted for the request flow at the start of the
transaction. Network transit time, timestamp C - timestamp B, is the transaction. Network transit time, timestamp C - timestamp B, is the
amount of time that the definite response request and its response amount of time that the definite response request and its response
required. Host time, timestamp B - timestamp A, is the actual time that required. Host time, timestamp B - timestamp A, is the actual time
the host required to process the transaction. Experience has shown that that the host required to process the transaction. Experience has
using the response flow to approximate network transit times is useful, shown that using the response flow to approximate network transit
and does correlate well with actual network transit times. times is useful, and does correlate well with actual network transit
times.
A client SHOULD respond to a definite response request when it completes A client SHOULD respond to a definite response request when it
processing the transaction. This is important since it increases the completes processing the transaction. This is important since it
accuracy of a total response time. Clients that immediately respond to increases the accuracy of a total response time. Clients that
a definite response request will be attributed with lower total response immediately respond to a definite response request will be attributed
times then those that actually occurred. with lower total response times then those that actually occurred.
The TN3270E-RT-MIB describes a method of collecting performance data 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; that is not appropriate for printer (LU Type 1 or LU Type 3)
thus collection of performance data for printer sessions is excluded sessions; thus collection of performance data for printer sessions is
from this MIB. This exclusion of printer sessions is not considered a excluded from this MIB. This exclusion of printer sessions is not
problem, since these sessions are not the most important ones for considered a problem, since these sessions are not the most important
response time monitoring, and since historically they were excluded from ones for response time monitoring, and since historically they were
SNA/MS RTM collection. The tn3270eTcpConnResourceType object in a excluded from SNA/MS RTM collection. The tn3270eTcpConnResourceType
tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to determine if object in a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined
a client session is ineligible for response time data collection for to determine if a client session is ineligible for response time data
this reason. collection for this reason.
3.2 TN3270E Server Response Time Collection 3.2 TN3270E Server Response Time Collection
A TN3270E server connects a Telnet client performing 3270 emulation to a A TN3270E server connects a Telnet client performing 3270 emulation
target SNA host over both a client-side network (client to TN3270E to a target SNA host over both a client-side network (client to
server) and an SNA Network (TN3270E server to target SNA host). The TN3270E server) and an SNA Network (TN3270E server to target SNA
client-side network is typically TCP/IP, but it need not be. For ease host). The client-side network is typically TCP/IP, but it need not
of exposition this document uses the term "IP network" to refer to the be. For ease of exposition this document uses the term "IP network"
client-side network, since IP is by far the most common protocol for to refer to the client-side network, since IP is by far the most
these networks. common protocol for these networks.
A TN3270E server can use SNA definite responses and the TN3270 A TN3270E server can use SNA definite responses and the TN3270
Enhancement (RFC 2355 [19]) RESPONSES function to calculate response Enhancement (RFC 2355 [19]) RESPONSES function to calculate response
times for a transaction, by timestamping when a client request arrives times for a transaction, by timestamping when a client request
at the server, when the reply arrives from the target host, and when the arrives at the server, when the reply arrives from the target host,
response acknowledging this reply arrives from the client. and when the response acknowledging this reply arrives from the
client.
Section 3.4, Timestamp Calculation, provides specifics on when in the Section 3.4, Timestamp Calculation, provides specifics on when in the
sequence of flows between a TN3270E client and its target SNA host a sequence of flows between a TN3270E client and its target SNA host a
TN3270E server takes the required timestamps. In addition, it provides TN3270E server takes the required timestamps. In addition, it
information on how a TN3270 TIMING-MARK request/response flow can be provides information on how a TN3270 TIMING-MARK request/response
used instead of DR for approximating IP network transit times. flow can be used instead of DR for approximating IP network transit
times.
The following figure adds a TN3270E server between the client, in this The following figure adds a TN3270E server between the client, in
case a TN3270E client and the target SNA host: this case a TN3270E client and the target SNA host:
------------------------------------------------ ------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server SNA Host | | Server SNA Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D | | request D |
| ------------------------------------------> | | ------------------------------------------> |
| reply(DR) E | | | reply(DR) E | |
| <----------------------------------------< | | <----------------------------------------< |
| | +/-RSP F | | | +/-RSP F |
| >-------------------- - - - - - - - - - > | | >-------------------- - - - - - - - - - > |
| | | |
------------------------------------------------ ------------------------------------------------
A TN3270E server can save timestamp D when it receives a client request, A TN3270E server can save timestamp D when it receives a client
save timestamp E when the target SNA host replies, and save timestamp F request, save timestamp E when the target SNA host replies, and save
when the client responds to the definite response request that flowed timestamp F when the client responds to the definite response request
with the reply. It doesn't matter whether the target SNA host requested that flowed with the reply. It doesn't matter whether the target SNA
a definite response on its reply: if it didn't, the TN3270E server host requested a definite response on its reply: if it didn't, the
makes the request on its own, to enable it to produce timestamp F. In TN3270E server makes the request on its own, to enable it to produce
this case the TN3270E server does not forward the response to the target timestamp F. In this case the TN3270E server does not forward the
SNA host, as the dotted line in the figure indicates. response to the target SNA host, as the dotted line in the figure
indicates.
Because it is a special case, a transaction in which a target SNA host Because it is a special case, a transaction in which a target SNA
returns an UNBIND in response to a client's request, and the TN3270E host returns an UNBIND in response to a client's request, and the
server forwards the UNBIND to the client, is not included in any TN3270E server forwards the UNBIND to the client, is not included in
response time calculations. any response time calculations.
In order to generate timestamp F, a TN3270E server MUST insure that the In order to generate timestamp F, a TN3270E server MUST insure that
transaction specifies DR, and that the TN3270E RESPONSES function has the transaction specifies DR, and that the TN3270E RESPONSES function
been negotiated between itself and the client. Negotiation of the has been negotiated between itself and the client. Negotiation of
TN3270E RESPONSES function occurs during the client's TN3270E session the TN3270E RESPONSES function occurs during the client's TN3270E
initialization. The TN3270E servers that the authors are aware of do session initialization. The TN3270E servers that the authors are
request the RESPONSES function during client session initialization. aware of do request the RESPONSES function during client session
TN3270E clients either automatically support the RESPONSES function, or initialization. TN3270E clients either automatically support the
can be configured during startup to support it. RESPONSES function, or can be configured during startup to support
it.
Using timestamps D, E, and F the following response times can be Using timestamps D, E, and F the following response times can be
calculated by a TN3270E server: calculated by a TN3270E server:
o Total Response time: Timestamp F - Timestamp D o Total Response time: Timestamp F - Timestamp D
o IP Network Transit Time: Timestamp F - Timestamp E o IP Network Transit Time: Timestamp F - Timestamp E
Just as in the SNA case presented above, these response times are also Just as in the SNA case presented above, these response times are
approximations, since the final +/- RSP from the client is being also approximations, since the final +/- RSP from the client is being
substituted for the request from the client that began the transaction. substituted for the request from the client that began the
transaction.
The MIB provides an object, tn3270eRtCollCtlType, to control several The MIB provides an object, tn3270eRtCollCtlType, to control several
aspects of response time data collection. One of the available options aspects of response time data collection. One of the available
in setting up a response time collection policy is to eliminate the options in setting up a response time collection policy is to
IP-network component altogether. This might be done because it is eliminate the IP-network component altogether. This might be done
determined either that the additional IP network traffic would not be because it is determined either that the additional IP network
desirable, or that the IP-network component of the overall response traffic would not be desirable, or that the IP-network component of
times is not significant. the overall response times is not significant.
Excluding the IP-network component from response times also has an Excluding the IP-network component from response times also has an
implication for the way in which response time data is aggregated. A 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 TN3270E server may find that some of its clients simply don't support
any of the functions necessary for the server to calculate the any of the functions necessary for the server to calculate the IP-
IP-network component of response times. For these clients, the most network component of response times. For these clients, the most
that the server can calculate is the SNA-network component of their that the server can calculate is the SNA-network component of their
overall response times; the server records this SNA-network component as overall response times; the server records this SNA-network component
the TOTAL response time each of these clients' transactions. If a as the TOTAL response time each of these clients' transactions. If a
response time collection is aggregating data from a number of clients, response time collection is aggregating data from a number of
some of which have the support necessary for including the IP-network clients, some of which have the support necessary for including the
component in their total response time calculations, and some of which IP-network component in their total response time calculations, and
do not, then the server aggregates the data differently depending on some of which do not, then the server aggregates the data differently
whether the collection has been defined to include or exclude the depending on whether the collection has been defined to include or
IP-network component: exclude the IP-network component:
o If the IP-network component is included, then transactions for the o If the IP-network component is included, then transactions for the
clients that don't support calculation of the IP-network component clients that don't support calculation of the IP-network component
of their response times are excluded from the aggregation of their response times are excluded from the aggregation
altogether. altogether.
o If the IP-network component is excluded, then total response times o If the IP-network component is excluded, then total response times
for ALL clients include only the SNA-network component, even though for ALL clients include only the SNA-network component, even
the server could have included an IP-network component in the though the server could have included an IP-network component in
overall response times for some of these clients. The server does the overall response times for some of these clients. The server
this by setting timestamp F, which marks the end of a transaction's does this by setting timestamp F, which marks the end of a
total response time, equal to timestamp E, the end of the transaction's total response time, equal to timestamp E, the end
transaction's SNA-network component. of the transaction's SNA-network component.
The principle here is that all the transactions contributing their The principle here is that all the transactions contributing their
response times to an aggregated value MUST make the same contribution. response times to an aggregated value MUST make the same
If the aggregation specifies that an IP-network component MUST be contribution. If the aggregation specifies that an IP-network
included in the aggregation's response times, then transactions for component MUST be included in the aggregation's response times, then
which an IP-network component cannot be calculated aren't included at transactions for which an IP-network component cannot be calculated
all. If the aggregation specifies that an IP-network component is not aren't included at all. If the aggregation specifies that an IP-
to be included, then only the SNA-network component is used, even for network component is not to be included, then only the SNA-network
those transactions for which an IP-network component could have been component is used, even for those transactions for which an IP-
calculated. network component could have been calculated.
There is one more complication here: the MIB allows a management There is one more complication here: the MIB allows a management
application to enable or disable dynamic definite responses for a application to enable or disable dynamic definite responses for a
response time collection. Once again the purpose of this option is to response time collection. Once again the purpose of this option is
give the network operator control over the amount of traffic introduced to give the network operator control over the amount of traffic
into the IP network for response time data collection. A DYNAMIC introduced into the IP network for response time data collection. A
definite response is one that the TN3270E server itself adds to a reply, DYNAMIC definite response is one that the TN3270E server itself adds
in a transaction for which the SNA application at the target SNA host to a reply, in a transaction for which the SNA application at the
did not specify DR in its reply. When the +/-RSP comes back from the target SNA host did not specify DR in its reply. When the +/-RSP
client, the server uses this response to calculate timestamp F, but then comes back from the client, the server uses this response to
it does not forward the response on to the SNA application (since the calculate timestamp F, but then it does not forward the response on
application is not expecting a response to its reply). to the SNA application (since the application is not expecting a
response to its reply).
The dynamic definite responses option is related to the option of The dynamic definite responses option is related to the option of
including or excluding the IP-network component of response times including or excluding the IP-network component of response times
(discussed above) as follows: (discussed above) as follows:
o If the IP-network component is excluded, then there is no reason for o If the IP-network component is excluded, then there is no reason
enabling dynamic definite responses: the server always sets for enabling dynamic definite responses: the server always sets
timestamp F equal to timestamp E, so the additional IP-network timestamp F equal to timestamp E, so the additional IP-network
traffic elicited by a dynamic definite response would serve no traffic elicited by a dynamic definite response would serve no
purpose. purpose.
o If the IP-network component is included, then enabling dynamic o If the IP-network component is included, then enabling dynamic
definite responses causes MORE transactions to be included in the definite responses causes MORE transactions to be included in the
aggregated response time values: aggregated response time values:
- For clients that do not support sending of responses, timestamp - For clients that do not support sending of responses, timestamp
F can never be calculated, and so their transactions are never F can never be calculated, and so their transactions are never
included in the aggregate. included in the aggregate.
- For clients that support sending of responses, timestamp F will - For clients that support sending of responses, timestamp F will
always be calculated for transactions in which the host SNA always be calculated for transactions in which the host SNA
application specifies DR in its reply, and so these transactions application specifies DR in its reply, and so these
will always be included in the aggregate. transactions will always be included in the aggregate.
- For clients that support sending of responses, having dynamic - For clients that support sending of responses, having dynamic
definite responses enabled for a collection results in the definite responses enabled for a collection results in the
inclusion of additional transactions in the aggregate: inclusion of additional transactions in the aggregate:
specifically, those for which the host SNA application did not specifically, those for which the host SNA application did not
specify DR in its reply. specify DR in its reply.
A TN3270E server also has the option of substituting TIMING-MARK A TN3270E server also has the option of substituting TIMING-MARK
processing for definite responses in calculating the IP-network processing for definite responses in calculating the IP-network
component of a transaction's response time. Once again, there is no 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 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. exclude the IP-network component altogether in computing response
times.
The MIB is structured to keep counts and averages for total response The MIB is structured to keep counts and averages for total response
times (F - D) and their IP-network components (F - E). A management times (F - D) and their IP-network components (F - E). A management
application can obviously calculate from these two values an average application can obviously calculate from these two values an average
SNA-network component (E - D) for the response times. This SNA-network SNA-network component (E - D) for the response times. This SNA-
component includes the SNA node processing time at both the TN3270E network component includes the SNA node processing time at both the
server and at the target application. TN3270E server and at the target application.
A host TN3270E server refers to an implementation where the TN3270E A host TN3270E server refers to an implementation where the TN3270E
server is collocated with the Systems Network Architecture (SNA) System server is collocated with the Systems Network Architecture (SNA)
Services Control Point (SSCP) for the dependent Secondary Logical Units System Services Control Point (SSCP) for the dependent Secondary
(SLUs) that the server makes available to its clients for connecting Logical Units (SLUs) that the server makes available to its clients
into an SNA network. A gateway TN3270E server resides on an SNA node for connecting into an SNA network. A gateway TN3270E server resides
other than an SSCP, either an SNA type 2.0 node, a 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 boundary-function-attached type 2.1 node, or an APPN node acting in
role of a Dependent LU Requester (DLUR). Host and gateway TN3270E the role of a Dependent LU Requester (DLUR). Host and gateway
server implementations typically differ greatly as to their internal TN3270E server implementations typically differ greatly as to their
implementation and System Definition (SYSDEF) requirements. internal implementation and System Definition (SYSDEF) requirements.
If a host TN3270E server is in the same SNA host as the target 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 application, then the SNA-network component of a transaction's
time will approximately equal the host transit time (B - A) described response time will approximately equal the host transit time (B - A)
previously. A host TN3270E server implementation can, however, described previously. A host TN3270E server implementation can,
typically support the establishment of sessions to target applications however, typically support the establishment of sessions to target
in SNA hosts remote from itself. In this case the SNA-network component applications in SNA hosts remote from itself. In this case the SNA-
of the response time equals the actual SNA-network transit time plus two network component of the response time equals the actual SNA-network
host transit times. transit time plus two host transit times.
3.3 Correlating TN3270E Server and Host Response Times 3.3 Correlating TN3270E Server and Host Response Times
It is possible that response time data is collected from TN3270E servers It is possible that response time data is collected from TN3270E
at the same time as a management application is monitoring the SNA servers at the same time as a management application is monitoring
sessions at a host. For example, a management application can be the SNA sessions at a host. For example, a management application
monitoring a secondary logical unit (SLU) while retrieving data from a can be monitoring a secondary logical unit (SLU) while retrieving
TN3270E server. Consider the following figure: data from a TN3270E server. Consider the following figure:
------------------------------------------------ ------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server SNA Host | | Server SNA Host |
| Timestamps (PLU) | | Timestamps (PLU) |
| (SLU) Timestamps| | (SLU) Timestamps|
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D A | | request D A |
| ------------------------------------------> | | ------------------------------------------> |
| reply(DR) E B | | | reply(DR) E B | |
| <----------------------------------------< | | <----------------------------------------< |
| | +/-RSP F C | | | +/-RSP F C |
| >--------------------------------------> | | >--------------------------------------> |
| | | |
------------------------------------------------ ------------------------------------------------
The following response times are available: The following response times are available:
o Target SNA host transit time: Timestamp B - Timestamp A o Target SNA host transit time: Timestamp B - Timestamp A
o Target SNA host network transit time: Timestamp C - Timestamp B o Target SNA host network transit time: Timestamp C - Timestamp B
o TN3270E server total response time: Timestamp F - Timestamp D o TN3270E server total response time: Timestamp F - Timestamp D
o TN3270E server IP-network component: Timestamp F - Timestamp E o TN3270E server IP-network component: Timestamp F - Timestamp E
The value added by the TN3270E server in this situation is its The value added by the TN3270E server in this situation is its
approximation of the IP-network component of the overall response time. approximation of the IP-network component of the overall response
The IP-network component can be subtracted from the total network time. The IP-network component can be subtracted from the total
transit time (which can be captured at an SSCP monitoring SNA traffic network transit time (which can be captured at an SSCP monitoring SNA
from/to the SLU) to see the actual SNA versus IP network transit times. traffic from/to the SLU) to see the actual SNA versus IP network
transit times.
The MIB defined by this memo does not specifically address correlation The MIB defined by this memo does not specifically address
of the data it contains with response time data collected by direct correlation of the data it contains with response time data collected
monitoring of SNA resources: its focus is exclusively response time by direct monitoring of SNA resources: its focus is exclusively
data collection from a TN3270E server perspective. It has, however, in response time data collection from a TN3270E server perspective. It
conjunction with the TN3270E-MIB [10], been structured to provide the has, however, in conjunction with the TN3270E-MIB [10], been
information necessary for correlation between TN3270E server-provided structured to provide the information necessary for correlation
response time information and that gathered from directly monitoring SNA between TN3270E server-provided response time information and that
resources. gathered from directly monitoring SNA resources.
A management application attempting to correlate SNA resource usage to A management application attempting to correlate SNA resource usage
Telnet clients can monitor either the tn3270eResMapTable or the to Telnet clients can monitor either the tn3270eResMapTable or the
tn3270eTcpConnTable to determine resource-to-client address mappings. tn3270eTcpConnTable to determine resource-to-client address mappings.
Both of these tables are defined by the TN3270E-MIB [10]. Another Both of these tables are defined by the TN3270E-MIB [10]. Another
helpful table is the tn3270eSnaMapTable, which provides a mapping helpful table is the tn3270eSnaMapTable, which provides a mapping
between SLU names as they are known at the SSCP (VTAM) and their local between SLU names as they are known at the SSCP (VTAM) and their
names at the TN3270E server. Neither the tn3270eClientGroupTable, the local names at the TN3270E server. Neither the
tn3270eResPoolTable, nor the tn3270eClientResMapTable from the tn3270eClientGroupTable, the tn3270eResPoolTable, nor the
TN3270E-MIB can be used for correlation, since the mappings defined by tn3270eClientResMapTable from the TN3270E-MIB can be used for
these tables can overlap, and may not provide one-to-one mappings. correlation, since the mappings defined by these tables can overlap,
and may not provide one-to-one mappings.
3.4 Timestamp Calculation 3.4 Timestamp Calculation
This section goes into more detail concerning when the various This section goes into more detail concerning when the various
timestamps can be taken as the flows between a TN3270E client and its timestamps can be taken as the flows between a TN3270E client and its
target SNA host pass through a TN3270E server. In addition, information target SNA host pass through a TN3270E server. In addition,
is provided on how the TN3270 TIMING-MARK request/response flow can be information is provided on how the TN3270 TIMING-MARK
used in place of DR for approximating IP network transit times. request/response flow can be used in place of DR for approximating IP
network transit times.
3.4.1 DR Usage 3.4.1 DR Usage
Consider the following flow: Consider the following flow:
---------------------------------------------------------- ----------------------------------------------------------
| | | |
| Client TN3270E Target SNA | | Client TN3270E Target SNA |
| Server Host | | Server Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D (BB,CD,OIC,ER) | | request D (BB,CD,OIC,ER) |
| -------------------------------------------> | | -------------------------------------------> |
| reply(DR) (FIC,ER,EB) | | | reply(DR) (FIC,ER,EB) | |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply E (LIC,DR) | | reply E (LIC,DR) |
| <-----------------------------------------< | | <-----------------------------------------< |
| | +/-RSP F | | | +/-RSP F |
| >----------------------------------------> | | >----------------------------------------> |
| | | |
| BB : Begin Bracket ER : Response by exception | | BB : Begin Bracket ER : Response by exception |
| EB : End Bracket DR : Definite Response Requested | | EB : End Bracket DR : Definite Response Requested |
| CD : Change Direction FIC : First in chain | | CD : Change Direction FIC : First in chain |
| OIC: Only in chain MIC: Middle in chain | | OIC: Only in chain MIC: Middle in chain |
| LIC: Last in chain | | LIC: Last in chain |
---------------------------------------------------------- ----------------------------------------------------------
Timestamp D is taken at the TN3270E server when the server has received Timestamp D is taken at the TN3270E server when the server has
data from a client for forwarding to its target SNA host, and the received data from a client for forwarding to its target SNA host,
direction of the SNA session allows the server to forward the data and the direction of the SNA session allows the server to forward the
immediately (either the direction is inbound towards the SNA host, or data immediately (either the direction is inbound towards the SNA
the session is between brackets). This is most likely when the server host, or the session is between brackets). This is most likely when
finds the end of record indicator in the TCP data received from the the server finds the end of record indicator in the TCP data received
client. from the client.
The target SNA application returns its reply in one or more SNA Request The target SNA application returns its reply in one or more SNA
Units (RUs); in this example there are four RUs in the reply. The first Request Units (RUs); in this example there are four RUs in the reply.
RU is marked as first in chain (FIC), the next two are marked as middle The first RU is marked as first in chain (FIC), the next two are
in chain (MIC), and the last is marked as last in chain (LIC). If the marked as middle in chain (MIC), and the last is marked as last in
SNA host sends a multiple-RU chain, the server does not know until the chain (LIC). If the SNA host sends a multiple-RU chain, the server
last RU is received whether DR is being requested. The server's only does not know until the last RU is received whether DR is being
chance to request DR from the client, however, comes when it forwards requested. The server's only chance to request DR from the client,
the FIC RU, since this is the only time that the TN3270E header is however, comes when it forwards the FIC RU, since this is the only
included. Since a server may forward the FIC RU to the client before it time that the TN3270E header is included. Since a server may forward
receives the LIC RU from the SNA host, some servers routinely specify DR the FIC RU to the client before it receives the LIC RU from the SNA
on all FIC RUs. host, some servers routinely specify DR on all FIC RUs.
If the server has specified DR on the TN3270E request for the FIC RU in If the server has specified DR on the TN3270E request for the FIC RU
a chain, it takes timestamp E when it forwards the LIC RU to the client. in a chain, it takes timestamp E when it forwards the LIC RU to the
Since timestamp E is used for calculating the IP-network time for the client. Since timestamp E is used for calculating the IP-network
transaction, the server SHOULD take timestamp E as close as possible to time for the transaction, the server SHOULD take timestamp E as close
its "Telnet edge". The server takes timestamp F when it receives the as possible to its "Telnet edge". The server takes timestamp F when
RESPONSES response from the client. it receives the RESPONSES response from the client.
A target SNA application doesn't necessarily return data to a client in A target SNA application doesn't necessarily return data to a client
a transaction; it may, for example, require more data from the client in a transaction; it may, for example, require more data from the
before it can formulate a reply. In this case the application may client before it can formulate a reply. In this case the application
simply return to the TN3270E server a change of direction indicator. At may simply return to the TN3270E server a change of direction
this point the server must send something to the client (typically a indicator. At this point the server must send something to the
Write operation with a WCC) to unlock the keyboard. If the server client (typically a Write operation with a WCC) to unlock the
specifies DR on the request to the client triggered by its receipt of keyboard. If the server specifies DR on the request to the client
the change of direction indicator from the SNA application, then triggered by its receipt of the change of direction indicator from
timestamps E and F can be taken, and the usual response times can be the SNA application, then timestamps E and F can be taken, and the
calculated. When the client sends in the additional data and gets a usual response times can be calculated. When the client sends in the
textual response from the SNA application, the server treats this as a additional data and gets a textual response from the SNA application,
separate transaction from the one involving the change of direction. the server treats this as a separate transaction from the one
involving the change of direction.
3.4.2 TIMING-MARK Usage 3.4.2 TIMING-MARK Usage
It is possible for a TN3270E server to use the TIMING-MARK flow for It is possible for a TN3270E server to use the TIMING-MARK flow for
approximating IP network transit times. Using TIMING-MARKs would make approximating IP network transit times. Using TIMING-MARKs would
it possible for a server to collect performance data for TN3270 clients, make it possible for a server to collect performance data for TN3270
as well as for TN3270E clients that do not support the RESPONSES clients, as well as for TN3270E clients that do not support the
function. In order for TIMING-MARKs to be used in this way, a client RESPONSES function. In order for TIMING-MARKs to be used in this
can't have the NOP option enabled, since responses are needed to the way, a client can't have the NOP option enabled, since responses are
server's TIMING-MARK requests. An IP network transit time approximation needed to the server's TIMING-MARK requests. An IP network transit
using a TIMING-MARK is basically the amount of time it takes for a time approximation using a TIMING-MARK is basically the amount of
TN3270 server to receive from a client a response to a TIMING-MARK time it takes for a TN3270 server to receive from a client a response
request. to a TIMING-MARK request.
To get an estimate for IP network transit time, a TN3270E server sends a To get an estimate for IP network transit time, a TN3270E server
TIMING-MARK request to a client after a LIC RU has been received, as a sends a TIMING-MARK request to a client after a LIC RU has been
means of approximating IP network transit time: received, as a means of approximating IP network transit time:
--------------------------------------------------- ---------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server Host | | Server Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D (BB,CD,OIC,ER) | | request D (BB,CD,OIC,ER) |
| -------------------------------------------> | | -------------------------------------------> |
| reply (FIC,ER,EB) | | | reply (FIC,ER,EB) | |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply E (LIC,ER) | | reply E (LIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| TIMING-MARK Rqst E' | | TIMING-MARK Rqst E' |
| <--------------------- | | <--------------------- |
| | TIMING-MARK Rsp F' | | | TIMING-MARK Rsp F' |
| >-------------------> | | >-------------------> |
| | | |
--------------------------------------------------- ---------------------------------------------------
The response times can then be calculated as follows: The response times can then be calculated as follows:
o TN3270E server total response time: o TN3270E server total response time:
(Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E') (Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E')
o TN3270E server IP network time: Timestamp F' - Timestamp E' o TN3270E server IP network time: Timestamp F' - Timestamp E'
If a TN3270E server is performing the TIMING-MARK function (independent If a TN3270E server is performing the TIMING-MARK function
of the response time monitoring use of the function discussed here), (independent of the response time monitoring use of the function
then it most likely has a TIMING-MARK interval for determining when to discussed here), then it most likely has a TIMING-MARK interval for
examine client sessions for sending the TIMING-MARK request. This determining when to examine client sessions for sending the TIMING-
interval, which is ordinarily a global value for an entire TN3270E MARK request. This interval, which is ordinarily a global value for
server, is represented in the TN3270E-MIB by the an entire TN3270E server, is represented in the TN3270E-MIB by the
tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent only tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent
if, when it is examined, a client session is found to have had no only if, when it is examined, a client session is found to have had
activity for a different fixed length of time, represented in the no activity for a different fixed length of time, represented in the
TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object. TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object.
Servers that support a large number of client sessions should spread out Servers that support a large number of client sessions should spread
the TIMING-MARK requests they send to these clients over the activity out the TIMING-MARK requests they send to these clients over the
interval, rather than sending them all in a single burst, since activity interval, rather than sending them all in a single burst,
otherwise the network may be flooded with TIMING-MARK requests. When a since otherwise the network may be flooded with TIMING-MARK requests.
server uses TIMING-MARKs for approximating response times, this tends to When a server uses TIMING-MARKs for approximating response times,
introduce a natural spreading into its TIMING-MARK requests, since the this tends to introduce a natural spreading into its TIMING-MARK
requests are triggered by the arrival of traffic from an SNA host. requests, since the requests are triggered by the arrival of traffic
from an SNA host.
A TN3270E server MUST integrate its normal TIMING-MARK processing with A TN3270E server MUST integrate its normal TIMING-MARK processing
its use of TIMING-MARKs for computing response times. In particular, it with its use of TIMING-MARKs for computing response times. In
MUST NOT send a second TIMING-MARK request to a client while waiting for particular, it MUST NOT send a second TIMING-MARK request to a client
the first to return, since this is ruled out by the TIMING-MARK protocol while waiting for the first to return, since this is ruled out by the
itself. If a TIMING-MARK flow has just been performed for a client TIMING-MARK protocol itself. If a TIMING-MARK flow has just been
shortly before the LIC RU arrives, the server MAY use the interval from performed for a client shortly before the LIC RU arrives, the server
this flow as its approximation for IP network transit time, (in other MAY use the interval from this flow as its approximation for IP
words, as its (F' - E') value) when calculating its approximation for network transit time, (in other words, as its (F' - E') value) when
the transaction's total response time, rather than sending a second calculating its approximation for the transaction's total response
TIMING-MARK request so soon after the preceding one. time, rather than sending a second TIMING-MARK request so soon after
the preceding one.
Regardless of when the server sends its TIMING-MARK request, the Regardless of when the server sends its TIMING-MARK request, the
accuracy of its total response time calculation depends on exactly when accuracy of its total response time calculation depends on exactly
the client responds to the TIMING-MARK request. when the client responds to the TIMING-MARK request.
3.5 Performance Data Modelling 3.5 Performance Data Modelling
The following two subsections detail how the TN3270E-RT-MIB models and The following two subsections detail how the TN3270E-RT-MIB models
controls capture of two types of response time data: average response and controls capture of two types of response time data: average
times and response time buckets. response times and response time buckets.
3.5.1 Averaging Response Times 3.5.1 Averaging Response Times
Average response times play two different roles in the MIB: Average response times play two different roles in the MIB:
o They are made available for management applications to retrieve. o They are made available for management applications to retrieve.
o They serve as triggers for emitting notifications. o They serve as triggers for emitting notifications.
Sliding-window averages are used rather than straight interval-based Sliding-window averages are used rather than straight interval-based
averages, because they are often more meaningful, and because they cause averages, because they are often more meaningful, and because they
less notification thrashing. Sliding-window average calculation can, if cause less notification thrashing. Sliding-window average
necessary, be disabled, by setting the sample period multiplier, calculation can, if necessary, be disabled, by setting the sample
tn3270eRtCollCtlSPMult, to 1, and setting the sample period, period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the
tn3270eRtCollCtlSPeriod, to the required collection interval. sample period, tn3270eRtCollCtlSPeriod, to the required collection
interval.
In order to calculate sliding-window averages, a TN3270E server MUST: In order to calculate sliding-window averages, a TN3270E server MUST:
o Select a fixed, relatively short, sample period SPeriod; the default o Select a fixed, relatively short, sample period SPeriod; the
value for SPeriod in the MIB is 20 seconds. default value for SPeriod in the MIB is 20 seconds.
o Select an averaging period multiplier SPMult. The actual collection o Select an averaging period multiplier SPMult. The actual
interval will then be SPMult times SPeriod. The default value for collection interval will then be SPMult times SPeriod. The
SPMult in the MIB is 30, yielding a default collection interval of default value for SPMult in the MIB is 30, yielding a default
10 minutes. Note that the collection interval (SPMult*SPeriod) is collection interval of 10 minutes. Note that the collection
always a multiple of the sample period. interval (SPMult*SPeriod) is always a multiple of the sample
period.
Clearlly, SPMult*SPeriod should not be thought of as literally the Clearlly, SPMult*SPeriod should not be thought of as literally
averaging period. The average calculated will include contributions the averaging period. The average calculated will include
older than that time, and does not weight equally all contributions contributions older than that time, and does not weight equally
since that time. In fact, it gives a smoother result than a all contributions since that time. In fact, it gives a smoother
traditional sliding average, as used in finance. More subtly, it is result than a traditional sliding average, as used in finance.
best to think of the effective averaging period as being More subtly, it is best to think of the effective averaging
2*SPMult*SPeriod. To see this, consider how long the contribution period as being 2*SPMult*SPeriod. To see this, consider how long
to the result made by a particular transaction lasts. With a the contribution to the result made by a particular transaction
traditional sliding average, it lasts exactly the averaging period. lasts. With a traditional sliding average, it lasts exactly the
With the aging mechanism described here, it has a half-life of averaging period. With the aging mechanism described here, it
SPMult*SPeriod. has a half-life of SPMult*SPeriod.
o Maintain the following counters to keep track of activity within the o Maintain the following counters to keep track of activity within
current sample period; these are internal counters, not made visible the current sample period; these are internal counters, not made
to a management application via the MIB. visible to a management application via the MIB.
- T (number of transactions in the period) - T (number of transactions in the period)
- TotalRts (sum of the total response times for all transactions - TotalRts (sum of the total response times for all
in the period) transactions in the period)
- TotalIpRts (sum of the IP network transit times for all - TotalIpRts (sum of the IP network transit times for all
transactions in the period; note that if IP network transit transactions in the period; note that if IP network transit
times are being excluded from the response time collection, this times are being excluded from the response time collection,
value will always be 0). this value will always be 0).
o Also maintain sliding counters, initialized to zero, for each of the o Also maintain sliding counters, initialized to zero, for each of
quantities being counted: the quantities being counted:
- AvgCountTrans (sliding count of transactions) - AvgCountTrans (sliding count of transactions)
- TotalRtsSliding (sliding count of total response times) - TotalRtsSliding (sliding count of total response times)
- TotalIpRtsSliding (sliding count of IP network transit times) - TotalIpRtsSliding (sliding count of IP network transit times)
o At the end of each sample period, update the sliding interval o At the end of each sample period, update the sliding interval
counters, using the following floating-point calculations: counters, using the following floating-point calculations:
AvgCountTrans = AvgCountTrans + T AvgCountTrans = AvgCountTrans + T
- (AvgCountTrans / SPMult) - (AvgCountTrans / SPMult)
TotalRtsSliding = TotalRtsSliding + TotalRts TotalRtsSliding = TotalRtsSliding + TotalRts
- (TotalRtsSliding / SPMult) - (TotalRtsSliding / SPMult)
TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts
- (TotalIpRtsSliding / SPMult) - (TotalIpRtsSliding / SPMult)
Then reset T, TotalRts, and TotalIpRts to zero for use during the Then reset T, TotalRts, and TotalIpRts to zero for use during the
next sample period. next sample period.
o At the end of a collection interval, update the following MIB o At the end of a collection interval, update the following MIB
objects as indicated; the floating-point numbers are rounded rather objects as indicated; the floating-point numbers are rounded
than truncated. rather than truncated.
tn3270eRtDataAvgCountTrans = AvgCountTrans tn3270eRtDataAvgCountTrans = AvgCountTrans
tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans
tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans
As expected, if IP network transit times are being excluded from As expected, if IP network transit times are being excluded from
response time collection, then tn3270eRtDataAvgIpRt will always response time collection, then tn3270eRtDataAvgIpRt will always
return 0. return 0.
The sliding transaction counter AvgCountTrans is not used for updating The sliding transaction counter AvgCountTrans is not used for
the MIB object tn3270eRtDataCountTrans: this object is an ordinary SMI updating the MIB object tn3270eRtDataCountTrans: this object is an
Counter32, which maintains a total count of transactions since its last ordinary SMI Counter32, which maintains a total count of transactions
discontinuity event. The sliding counters are used only for calculating since its last discontinuity event. The sliding counters are used
averages. only for calculating averages.
Two mechanisms are present in the MIB to inhibit the generation of an Two mechanisms are present in the MIB to inhibit the generation of an
excessive number of notifications related to average response times. excessive number of notifications related to average response times.
First, there are high and low thresholds for average response times. A First, there are high and low thresholds for average response times.
tn3270eRtExceeded notification is generated the first time a A tn3270eRtExceeded notification is generated the first time a
statistically significant average response time is found to have statistically significant average response time is found to have
exceeded the high threshold. (The test for statistical significance is exceeded the high threshold. (The test for statistical significance
described below.) After this, no other tn3270eRtExceeded notifications is described below.) After this, no other tn3270eRtExceeded
are generated until an average response time is found to have fallen notifications are generated until an average response time is found
below the low threshold. to have fallen below the low threshold.
The other mechanism to limit notifications is the significance test for The other mechanism to limit notifications is the significance test
a high average response time. Intuitively, the significance of an for a high average response time. Intuitively, the significance of
average is directly related to the number of samples that go into it; so an average is directly related to the number of samples that go into
we might be inclined to use a rule such as "for the purpose of it; so we might be inclined to use a rule such as "for the purpose of
generating tn3270eRtExceeded notifications, ignore average response generating tn3270eRtExceeded notifications, ignore average response
times based on fewer than 20 transactions in the sample period." times based on fewer than 20 transactions in the sample period."
In the case of response times, however, the number of transactions In the case of response times, however, the number of transactions
sampled in a fixed sampling period is tied to these transactions' sampled in a fixed sampling period is tied to these transactions'
response times. A few transactions with long response times can response times. A few transactions with long response times can
guarantee that there will not be many transactions in a sample, because guarantee that there will not be many transactions in a sample,
these transactions "use up" the sampling time. Yet this case of a few because these transactions "use up" the sampling time. Yet this case
transactions with very poor response times should obviously be of a few transactions with very poor response times should obviously
classified as a problem, not as a statistical anomaly based on too small be classified as a problem, not as a statistical anomaly based on too
a sample. small a sample.
The solution is to make the significance level for a sample a function The solution is to make the significance level for a sample a
of the average response time. A value IdleCount is specified, which is function of the average response time. A value IdleCount is
used to qualify an sample as statistically significant. In order to specified, which is used to qualify an sample as statistically
determine at a collection interval whether to generate a significant. In order to determine at a collection interval whether
tn3270eRtExceeded notification, a TN3270E server uses the following to generate a tn3270eRtExceeded notification, a TN3270E server uses
algorithm: the following algorithm:
if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount
then generate the notification, then generate the notification,
where AvgRt is the value that would be returned by the object where AvgRt is the value that would be returned by the object
tn3270eRtDataAvgRt at the end of the interval, and the "**" notation tn3270eRtDataAvgRt at the end of the interval, and the "**" notation
indicates exponientiation. indicates exponientiation.
Two examples illustrate how this algorithm works. Suppose that Two examples illustrate how this algorithm works. Suppose that
IdleCount has been set to 20 transactions, and the high threshold to 200 IdleCount has been set to 20 transactions, and the high threshold to
msecs per transaction. If the average observed response time is 300 200 msecs per transaction. If the average observed response time is
msecs, then a notification will be generated only if AvgCountTrans >= 300 msecs, then a notification will be generated only if
80. If, however, the observed response time is 500 msecs, then a AvgCountTrans >= 80. If, however, the observed response time is 500
notification is generated if AvgCountTrans >= 9. msecs, then a notification is generated if AvgCountTrans >= 9.
There is no corresponding significance test for the tn3270eRtOkay There is no corresponding significance test for the tn3270eRtOkay
notification: this notification is generated based on an average notification: this notification is generated based on an average
response time that falls below the low threshold, regardless of the response time that falls below the low threshold, regardless of the
sample size behind that average. sample size behind that average.
3.5.2 Response Time Buckets 3.5.2 Response Time Buckets
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.
Like everything for a collection, the "total" response times collected The MIB also supports collection of response time data into a set of
in the buckets are governed by the specification of whether IP network five buckets. This data is suitable either for verification of
transit times are to be included in the totals. Depending on how this service level agreements, or for monitoring by a management
option is specified, the response times being counted in the buckets application to identify performance problems. The buckets provide
will either be total response times (F - D), or only SNA network transit counts of transactions whose total response times fall into a set of
times (effectively E - D, because when it is excluding the IP-network specified ranges.
component of transactions, a server makes timestamp F identical to
timestamp E).
Four bucket boundaries are specified for a response time collection, Like everything for a collection, the "total" response times
resulting in five buckets. The first response time bucket counts those collected in the buckets are governed by the specification of whether
transactions whose total response times were less than or equal to IP network transit times are to be included in the totals. Depending
Boundary 1, the second bucket counts those whose response times were on how this option is specified, the response times being counted in
greater than Boundary 1 but less than or equal to Boundary 2, and so on. the buckets will either be total response times (F - D), or only SNA
The fifth bucket is unbounded on the top, counting all transactions network transit times (effectively E - D, because when it is
whose response times were greater than Boundary 4. excluding the IP-network component of transactions, a server makes
timestamp F identical to timestamp E).
The four bucket boundaries have default values of: 1 second, 2 seconds, Four bucket boundaries are specified for a response time collection,
5 seconds, and 10 seconds, respectively. These values are the defaults resulting in five buckets. The first response time bucket counts
in the 3174 controller's implementation of the SNA/MS RTM function, and those transactions whose total response times were less than or equal
are thought to be appropriate for this MIB as well. 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.
In SNA/MS the counter buckets were (by today's standards) relatively The four bucket boundaries have default values of: 1 second, 2
small, with a maximum value of 65,535. The bucket objects in the MIB seconds, 5 seconds, and 10 seconds, respectively. These values are
are all Counter32's. 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.
The following figure represents the buckets pictorially: 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.
---------------------------------------------- The following figure represents the buckets pictorially:
| |
| Response Time Boundaries | ----------------------------------------------
| | | | | | | | | |
| | | | | | | | | Response Time Boundaries |
| | | | | | no | | | | | | | | |
| 0 B-1 B-2 B-3 B-4 bound| | | | | | | | |
| | | | | | | | | | | | | | no |
| |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| | | 0 B-1 B-2 B-3 B-4 bound|
| ----------------------------------------- | | | | | | | | |
| | | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| |
---------------------------------------------- | ----------------------------------------- |
| |
----------------------------------------------
4.0 Structure of the MIB 4.0 Structure of the MIB
The TN3270E-RT-MIB has the following components: The TN3270E-RT-MIB has the following components:
o tn3270eRtCollCtlTable o tn3270eRtCollCtlTable
o tn3270eRtDataTable o tn3270eRtDataTable
o Notifications o Notifications
o Advisory Spin Lock Usage o Advisory Spin Lock Usage
4.1 tn3270eRtCollCtlTable 4.1 tn3270eRtCollCtlTable
The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and
tn3270eClientGroupName imported from the TN3270E-MIB. tn3270eClientGroupName imported from the TN3270E-MIB.
tn3270eSrvrConfIndex identifies within a host a particular TN3270E tn3270eSrvrConfIndex identifies within a host a particular TN3270E
server. tn3270eClientGroupName identifies a collection of IP clients server. tn3270eClientGroupName identifies a collection of IP clients
for which response time data is to be collected. The set of clients is for which response time data is to be collected. The set of clients
defined using the tn3270eClientGroupTable from the TN3270E-MIB. is defined using the tn3270eClientGroupTable from the TN3270E-MIB.
A tn3270eRtCollCtlEntry contains the following objects: A tn3270eRtCollCtlEntry contains the following objects:
-------------------------------------------------- --------------------------------------------------
1st Index | tn3270eSrvrConfIndex Unsigned32 | 1st Index | tn3270eSrvrConfIndex Unsigned32 |
2nd Index | tn3270eClientGroupName Utf8String | 2nd Index | tn3270eClientGroupName Utf8String |
| tn3270eRtCollCtlType BITS | | tn3270eRtCollCtlType BITS |
| tn3270eRtCollCtlSPeriod Unsigned32 | | tn3270eRtCollCtlSPeriod Unsigned32 |
| tn3270eRtCollCtlSPMult Unsigned32 | | tn3270eRtCollCtlSPMult Unsigned32 |
| tn3270eRtCollCtlThreshHigh Unsigned32 | | tn3270eRtCollCtlThreshHigh Unsigned32 |
| tn3270eRtCollCtlThreshLow Unsigned32 | | tn3270eRtCollCtlThreshLow Unsigned32 |
| tn3270eRtCollCtlIdleCount Unsigned32 | | tn3270eRtCollCtlIdleCount Unsigned32 |
| tn3270eRtCollCtlBucketBndry1 Unsigned32 | | tn3270eRtCollCtlBucketBndry1 Unsigned32 |
| tn3270eRtCollCtlBucketBndry2 Unsigned32 | | tn3270eRtCollCtlBucketBndry2 Unsigned32 |
| tn3270eRtCollCtlBucketBndry3 Unsigned32 | | tn3270eRtCollCtlBucketBndry3 Unsigned32 |
| tn3270eRtCollCtlBucketBndry4 Unsigned32 | | tn3270eRtCollCtlBucketBndry4 Unsigned32 |
| tn3270eRtCollCtlRowStatus RowStatus | | tn3270eRtCollCtlRowStatus RowStatus |
-------------------------------------------------- --------------------------------------------------
The tn3270eRtCollCtlType object controls the type(s) of response time The tn3270eRtCollCtlType object controls the type(s) of response time
collection that occur, the granularity of the collection, whether collection that occur, the granularity of the collection, whether
dynamic definite responses SHOULD be initiated, and whether dynamic definite responses SHOULD be initiated, and whether
notifications SHOULD be generated. This object is of BITS SYNTAX, and notifications SHOULD be generated. This object is of BITS SYNTAX,
thus allows selection of multiple options. and thus allows selection of multiple options.
The BITS in the tn3270eRtCollCtlType object have the following meanings: The BITS in the tn3270eRtCollCtlType object have the following
meanings:
o aggregate(0) - If this bit is set to 1, then data SHOULD be 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 aggregated for the whole client group. In this case there will
only one row created for the collection in the tn3270eRtDataTable. be only one row created for the collection in the
The first two indexes for this row, tn3270eSrvrConfIndex and tn3270eRtDataTable. The first two indexes for this row,
tn3270eClientGroupName, will have the same values as the indexes for tn3270eSrvrConfIndex and tn3270eClientGroupName, will have the
the corresponding tn3270eRtCollCtlEntry. The third and fourth same values as the indexes for the corresponding
indexes of an aggregated tn3270eRtDataEntry have the values tn3270eRtCollCtlEntry. The third and fourth indexes of an
unknown(0) (tn3270eRtDataClientAddrType) and a zero-length octet aggregated tn3270eRtDataEntry have the values unknown(0)
string (tn3270eRtDataClientAddress). The fifth index, (tn3270eRtDataClientAddrType) and a zero-length octet string
tn3270eRtDataClientPort, has the value 0. (tn3270eRtDataClientAddress). The fifth index,
tn3270eRtDataClientPort, has the value 0.
If this bit is set to 0, then a separate entry is created in the If this bit is set to 0, then a separate entry is created in the
tn3270eRtDataTable for each member of the client group. In this tn3270eRtDataTable from each member of the client group. In this
case tn3270eRtDataClientAddress contains the client's actual IP case tn3270eRtDataClientAddress contains the client's actual IP
Address, tn3270eRtDataClientAddrType indicates the address type, and Address, tn3270eRtDataClientAddrType indicates the address type,
tn3270eRtDataClientPort contains the number of the port the client and tn3270eRtDataClientPort contains the number of the port the
is using for its TN3270/TN3270E session. client is using for its TN3270/TN3270E session.
o excludeIpComponent(1) - If this bit is set to 1, then the server o excludeIpComponent(1) - If this bit is set to 1, then the server
SHOULD exclude the IP-network component from all the response times SHOULD exclude the IP-network component from all the response
for this collection. If the target SNA application specifies DR in times for this collection. If the target SNA application
any of its replies, this DR will still be passed down to the client, specifies DR in any of its replies, this DR will still be passed
and the client's response will still be forwarded to the down to the client, and the client's response will still be
application. But this response will play no role in the server's forwarded to the application. But this response will play no
response time calculations. role in the server's response time calculations.
If this bit is set to 0, then the server includes in the collection If this bit is set to 0, then the server includes in the
only those transactions for which it can include an (approximate) collection only those transactions for which it can include an
IP-network component in the total response time for the transaction. (approximate) IP-network component in the total response time for
This component MAY be derived from a "natural" DR (if the client the transaction. This component MAY be derived from a "natural"
supports the RESPONSES function), from a dynamic DR introduced by DR (if the client supports the RESPONSES function), from a
the server (if the client supports the RESPONSES function and the dynamic DR introduced by the server (if the client supports the
ddr(2) bit has been set to 1), or from TIMING-MARK processing (if RESPONSES function and the ddr(2) bit has been set to 1), or from
the client supports TIMING-MARKs). TIMING-MARK processing (if the client supports TIMING-MARKs).
If this bit is set to 1, then the ddr(2) bit is ignored, since there If this bit is set to 1, then the ddr(2) bit is ignored, since
is no reason for the server to request additional responses from the there is no reason for the server to request additional responses
client(s) in the group. from the client(s) in the group.
o ddr(2) - If this bit is set to 1, then the server SHOULD, for those o ddr(2) - If this bit is set to 1, then the server SHOULD, for
clients in the group that support the RESPONSES function, add a DR those clients in the group that support the RESPONSES function,
request to the FIC reply in each transaction, and use the client's add a DR request to the FIC reply in each transaction, and use
subsequent response for calculating an (approximate) IP-network the client's subsequent response for calculating an (approximate)
component to include in the transaction's total response times. IP-network component to include in the transaction's total
response times.
If this bit is set to 0, then the server does not add a DR request If this bit is set to 0, then the server does not add a DR
that it was not otherwise going to add to any replies from the request that it was not otherwise going to add to any replies
target SNA application. from the target SNA application.
If the excludeIpComponent(1) bit is set to 1, then this bit is If the excludeIpComponent(1) bit is set to 1, then this bit is
ignored by the server. ignored by the server.
o average(3) - If this bit is set to 1, then the server SHOULD 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 calculate a sliding-window average for the collection, based on
parameters specified for the group. the parameters specified for the group.
If this bit is set to 0, then an average is not calculated. In this If this bit is set to 0, then an average is not calculated. In
case the tn3270eRtExceeded and tn3270eRtOkay notifications are not this case the tn3270eRtExceeded and tn3270eRtOkay notifications
generated, even if the traps(5) bit is set to 1. are not generated, even if the traps(5) bit is set to 1.
o buckets(4) - If this bit is set to 1, then the server SHOULD create o buckets(4) - If this bit is set to 1, then the server SHOULD
and increment response time buckets for the collection, based on the create and increment response time buckets for the collection,
parameters specified for the group. based on the parameters specified for the group.
If this bit is set to 0, then response time buckets are not created. If this bit is set to 0, then response time buckets are not
created.
o traps(5) - If this bit is set to 1, then a TN3270E Server is enabled o traps(5) - If this bit is set to 1, then a TN3270E Server is
to generate notifications pertaining to an tn3270eCollCtlEntry. enabled to generate notifications pertaining to an
tn3270CollStart and tn3270CollEnd generation is enabled simply by tn3270eCollCtlEntry. tn3270CollStart and tn3270CollEnd
traps(5) being set to 1. tn3270eRtExceeded and tn3270eRtOkay generation is enabled simply by traps(5) being set to 1.
generation enablement requires that average(3) be set to 1 in tn3270eRtExceeded and tn3270eRtOkay generation enablement
addition to the traps(5) requirement. requires that average(3) be set to 1 in addition to the traps(5)
requirement.
If traps(5) is set to 0, then none of the notifications defined in If traps(5) is set to 0, then none of the notifications defined
this MIB are generated for a particular tn3270eRtCollCtlEntry. in this MIB are generated for a particular tn3270eRtCollCtlEntry.
Either the average(3) or the buckets(4) bit MUST be set to 1 in order 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. for response time data collection to occur; both bits MAY be set to
If the average(3) bit is set to 1, then the following objects have 1. If the average(3) bit is set to 1, then the following objects
meaning, and are used to control the calculation of the averages, as have meaning, and are used to control the calculation of the
well as the generation of the two notifications related to them: averages, as well as the generation of the two notifications related
to them:
o tn3270eRtCollCtlSPeriod o tn3270eRtCollCtlSPeriod
o tn3270eRtCollCtlSPMult o tn3270eRtCollCtlSPMult
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshHigh
o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlThreshLow
o tn3270eRtCollCtlIdleCount o tn3270eRtCollCtlIdleCount
The previous objects' values are meaningless if the associated The previous objects' values are meaningless if the associated
average(3) bit is not set to 1. average(3) bit is not set to 1.
If the buckets(4) bit is set to 1, then the following objects have If the buckets(4) bit is set to 1, then the following objects have
meaning, and specify the bucket boundaries: meaning, and specify the bucket boundaries:
o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry1
o tn3270eRtCollCtlBucketBndry2 o tn3270eRtCollCtlBucketBndry2
o tn3270eRtCollCtlBucketBndry3 o tn3270eRtCollCtlBucketBndry3
o tn3270eRtCollCtlBucketBndry4 o tn3270eRtCollCtlBucketBndry4
The previous objects' values are meaningless if the associated The previous objects' values are meaningless if the associated
buckets(4) bit is not set to 1. buckets(4) bit is not set to 1.
If an entry in the tn3270RtCollCtlTable has the value active(1) for its If an entry in the tn3270RtCollCtlTable has the value active(1) for
RowStatus, then an implementation SHALL NOT allow Set operations for any its RowStatus, then an implementation SHALL NOT allow Set operations
objects in the entry except: for any objects in the entry except:
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshHigh
o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlThreshLow
o tn3270eRtCollCtlRowStatus o tn3270eRtCollCtlRowStatus
4.2 tn3270eRtDataTable 4.2 tn3270eRtDataTable
Either a single entry or multiple entries are created in the Either a single entry or multiple entries are created in the
tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on whether tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on
tn3270eRtCollCtlType in the control entry has aggregate(0) selected. whether tn3270eRtCollCtlType in the control entry has aggregate(0)
The contents of an entry in the tn3270eRtDataTable depend on the selected. The contents of an entry in the tn3270eRtDataTable depend
contents of the corresponding entry in the tn3270eRtCollCtlTable: as on the contents of the corresponding entry in the
described above, some objects in the data entry return meaningful values tn3270eRtCollCtlTable: as described above, some objects in the data
only when the average(3) option is selected in the control entry, while entry return meaningful values only when the average(3) option is
others return meaningful values only when the buckets(4) option is selected in the control entry, while others return meaningful values
selected. If both options are selected, then all the objects return only when the buckets(4) option is selected. If both options are
meaningful values. When an object is not specified to return a selected, then all the objects return meaningful values. When an
meaningful value, an implementation may return any syntactically valid object is not specified to return a meaningful value, an
value in response to a Get operation. implementation may return any syntactically valid value in response
to a Get operation.
The following objects return meaningful values if and only if the The following objects return meaningful values if and only if the
average(3) option was selected in the corresponding average(3) option was selected in the corresponding
tn3270eRtCollCtlEntry: tn3270eRtCollCtlEntry:
o tn3270eRtDataAvgRt o tn3270eRtDataAvgRt
o tn3270eRtDataAvgIpRt o tn3270eRtDataAvgIpRt
o tn3270eRtDataAvgCountTrans o tn3270eRtDataAvgCountTrans
o tn3270eRtDataIntTimeStamp o tn3270eRtDataIntTimeStamp
o tn3270eRtDataTotalRts o tn3270eRtDataTotalRts
o tn3270eRtDataTotalIpRts o tn3270eRtDataTotalIpRts
o tn3270eRtDataCountTrans o tn3270eRtDataCountTrans
o tn3270eRtDataCountDrs o tn3270eRtDataCountDrs
o tn3270eRtDataElapsRndTrpSq o tn3270eRtDataElapsRndTrpSq
o tn3270eRtDataElapsIpRtSq o tn3270eRtDataElapsIpRtSq
The first three objects in this list return values derived from the The first three objects in this list return values derived from the
sliding-window average calculations described earlier. The time of the sliding-window average calculations described earlier. The time of
most recent sample for these calculations is returned in the the most recent sample for these calculations is returned in the
tn3270eRtDataIntTimeStamp object. The next four objects are normal tn3270eRtDataIntTimeStamp object. The next four objects are normal
Counter32 objects, maintaining counts of total response time and total Counter32 objects, maintaining counts of total response time and
transactions. The last two objects return sum of the squares values, to total transactions. The last two objects return sum of the squares
enable variance calculations by a management application. values, to enable variance calculations by a management application.
The following objects return meaningful values if and only if the The following objects return meaningful values if and only if the
buckets(4) option was selected in the corresponding buckets(4) option was selected in the corresponding
tn3270eRtCollCtlEntry: tn3270eRtCollCtlEntry:
o tn3270eRtDataBucket1Rts o tn3270eRtDataBucket1Rts
o tn3270eRtDataBucket2Rts o tn3270eRtDataBucket2Rts
o tn3270eRtDataBucket3Rts o tn3270eRtDataBucket3Rts
o tn3270eRtDataBucket4Rts o tn3270eRtDataBucket4Rts
o tn3270eRtDataBucket5Rts o tn3270eRtDataBucket5Rts
A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used
management application to detect when the values of the counter objects by a management application to detect when the values of the counter
in this table may have been reset, or otherwise experienced a objects in this table may have been reset, or otherwise experienced a
discontinuity. A possible cause for such a discontinuity is the TN3270E discontinuity. A possible cause for such a discontinuity is the
server's being stopped or restarted. This object returns a meaningful TN3270E server's being stopped or restarted. This object returns a
value regardless of which collection control options were selected. meaningful value regardless of which collection control options were
selected.
An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time An object, tn3270eRtDataRtMethod, identifies whether the IP Network
was calculated using either the definite response or TIMING-MARK Time was calculated using either the definite response or TIMING-MARK
approach. approach.
When an entry is created in the tn3270eRtCollCtlTable with its When an entry is created in the tn3270eRtCollCtlTable with its
tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is
automatically created in the tn3270eRtDataTable; this entry's automatically created in the tn3270eRtDataTable; this entry's
tn3270eRtDataClientAddress has the value of a zero-length octet string, tn3270eRtDataClientAddress has the value of a zero-length octet
its tn3270eRtDataClientAddrType has the value of unknown(0), and its string, its tn3270eRtDataClientAddrType has the value of unknown(0),
tn3270eRtDataClientPort has the value 0. and its tn3270eRtDataClientPort has the value 0.
When an entry is created in the tn3270eRtCollCtlTable with its When an entry is created in the tn3270eRtCollCtlTable with its
tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is
created in the tn3270eRtDataTable for each member of the client group created in the tn3270eRtDataTable for each member of the client group
that currently has a session with the TN3270E server. Entries are that currently has a session with the TN3270E server. Entries are
subsequently created for clients that the TN3270E server determines to subsequently created for clients that the TN3270E server determines
be members of the client group when these clients establish sessions to be members of the client group when these clients establish
with the server. Entries are also created when clients with existing sessions with the server. Entries are also created when clients with
sessions are added to the group. existing sessions are added to the group.
All entries associated with a tn3270eRtCollCtlEntry are deleted from the All entries associated with a tn3270eRtCollCtlEntry are deleted from
tn3270eRtDataTable when that entry is deleted from the the tn3270eRtDataTable when that entry is deleted from the
tn3270eRtCollCtlTable. An entry for an individual client in a client tn3270eRtCollCtlTable. An entry for an individual client in a client
group is deleted when its TCP connection terminates. Once it has been group is deleted when its TCP connection terminates. Once it has
created, a client's entry in the tn3270eRtDataTable remains active as been created, a client's entry in the tn3270eRtDataTable remains
long as the collection's tn3270eRtCollCtlEntry exists, even if the active as long as the collection's tn3270eRtCollCtlEntry exists, even
client is removed from the client group for the tn3270eRtCollCtlEntry. if the client is removed from the client group for the
tn3270eRtCollCtlEntry.
4.3 Notifications 4.3 Notifications
This MIB defines four notifications related to a tn3270eRtDataEntry. If This MIB defines four notifications related to a tn3270eRtDataEntry.
the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1, If the associated tn3270eRtCollCtlType object's traps(5) bit is set
then the tn3270RtCollStart and tn3270RtCollEnd notifications are to 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications
generated when, respsectively, the tn3270eRtDataEntry is created and are generated when, respsectively, the tn3270eRtDataEntry is created
deleted. If, in addition, this tn3270eRtCollCtlType object's average(3) and deleted. If, in addition, this tn3270eRtCollCtlType object's
bit is set to 1, then the the tn3270eRtExceeded and tn3270eRtOkay average(3) bit is set to 1, then the the tn3270eRtExceeded and
notifications are generated when the conditions they report occur. tn3270eRtOkay notifications are generated when the conditions they
report occur.
The following notifications are defined by this MIB: The following notifications are defined by this MIB:
o tn3270eRtExceeded - The purpose of this notification is to signal o tn3270eRtExceeded - The purpose of this notification is to signal
that a performance problem has been detected. If average(3) that a performance problem has been detected. If average(3)
response time data is being collected, then this notification is response time data is being collected, then this notification is
generated whenever (1) an average response time is first found, on a generated whenever (1) an average response time is first found,
collection interval boundary, to have exceeded the high threshold on a collection interval boundary, to have exceeded the high
tn3270eRtCollCtlThreshHigh specified for the client group, AND (2) threshold tn3270eRtCollCtlThreshHigh specified for the client
the sample on which the average is based is determined to have been group, AND (2) the sample on which the average is based is
a significant one, via the significance algorithm described earlier. determined to have been a significant one, via the significance
This notification is not generated again for a tn3270eRtDataEntry algorithm described earlier. This notification is not generated
until an average response time falling below the low threshold again for a tn3270eRtDataEntry until an average response time
tn3270eRtCollCtlThreshLow specified for the client group has falling below the low threshold tn3270eRtCollCtlThreshLow
occurred for the entry. specified for the client group has occurred for the entry.
o tn3270eRtOkay - The purpose of this notification is to signal that a o tn3270eRtOkay - The purpose of this notification is to signal
previously reported performance problem has been resolved. If that a previously reported performance problem has been resolved.
average(3) response time data is being collected, then this If average(3) response time data is being collected, then this
notification is generated whenever (1) a tn3270eRtExceeded notification is generated whenever (1) a tn3270eRtExceeded
notification has already been generated, AND (2) an average response notification has already been generated, AND (2) an average
time is first found, on a collection interval boundary, to have response time is first found, on a collection interval boundary,
fallen below the low threshold tn3270eRtCollCtlThreshLow specified to have fallen below the low threshold tn3270eRtCollCtlThreshLow
for the client group. This notification is not generated again for specified for the client group. This notification is not
a tn3270eRtDataEntry until an average response time exceeding the generated again for a tn3270eRtDataEntry until an average
high threshold tn3270eRtCollCtlThreshHigh specified for the client response time exceeding the high threshold
group has occurred for the entry. tn3270eRtCollCtlThreshHigh specified for the client group has
occurred for the entry.
Taken together, the two preceding notifications serve to minimize the Taken together, the two preceding notifications serve to minimize the
generation of an excessive number of traps in the case of an average generation of an excessive number of traps in the case of an average
response time that oscillates about its high threshold. response time that oscillates about its high threshold.
o tn3270eRtCollStart - This notification is generated whenever data o tn3270eRtCollStart - This notification is generated whenever data
collection begins for a client group, or when a new collection begins for a client group, or when a new
tn3270eRtDataEntry becomes active. The primary purpose of this tn3270eRtDataEntry becomes active. The primary purpose of this
notification is signal to a management application that a new client notification is signal to a management application that a new
TCP session has been established, and to provide the IP-to-resource client TCP session has been established, and to provide the IP-
mapping for the session. This notification is not critical when to-resource mapping for the session. This notification is not
average(3) data collection is not being performed for the client critical when average(3) data collection is not being performed
group. for the client group.
o tn3270eRtCollEnd - This notification is generated whenever a data o tn3270eRtCollEnd - This notification is generated whenever a data
collection ends. For an aggregate collection, this occurs when the collection ends. For an aggregate collection, this occurs when
corresponding tn3270eRtCollCtlEntry is deleted. For an individual the corresponding tn3270eRtCollCtlEntry is deleted. For an
collection, this occurs either when the tn3270eRtCollCtlEntry is individual collection, this occurs either when the
deleted, or when the client's TCP connection terminates. The tn3270eRtCollCtlEntry is deleted, or when the client's TCP
purpose of this notification is to enable a management application connection terminates. The purpose of this notification is to
to complete a monitoring function that it was performing, by enable a management application to complete a monitoring function
returning final values for the collection's data objects. that it was performing, by returning final values for the
collection's data objects.
4.4 Advisory Spin Lock Usage 4.4 Advisory Spin Lock Usage
Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an
lock that allows cooperating TN3270E-RT-MIB applications to coordinate advisory lock that allows cooperating TN3270E-RT-MIB applications to
their use of the tn3270eRtCollCtlTable. When creating a new entry or coordinate their use of the tn3270eRtCollCtlTable. When creating a
altering an existing entry in the tn3270eRtCollCtlTable, an application new entry or altering an existing entry in the tn3270eRtCollCtlTable,
SHOULD make use of tn3270eRtSpinLock to serialize application changes or an application SHOULD make use of tn3270eRtSpinLock to serialize
additions. Since this is an advisory lock, its use by management application changes or additions. Since this is an advisory lock,
applications SHALL NOT be enforced by agents. Agents MUST, however, its use by management applications SHALL NOT be enforced by agents.
implement the tn3270eRtSpinLock object. Agents MUST, however, implement the tn3270eRtSpinLock object.
5.0 Definitions 5.0 Definitions
TN3270E-RT-MIB DEFINITIONS ::= BEGIN TN3270E-RT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Gauge32 Counter32, Unsigned32, Gauge32
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, DateAndTime, TimeStamp, TestAndIncr RowStatus, DateAndTime, TimeStamp, TestAndIncr
skipping to change at page 38, line 46 skipping to change at page 45, line 15
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notifications that must be supported when the "The notifications that must be supported when the
TN3270E-RT-MIB is implemented. " TN3270E-RT-MIB is implemented. "
::= { tn3270eRtGroups 2 } ::= { tn3270eRtGroups 2 }
END END
6.0 Security Considerations 6.0 Security Considerations
Certain management information defined in this MIB may be considered Certain management information defined in this MIB may be considered
sensitive in some network environments. Therefore, authentication of sensitive in some network environments. Therefore, authentication of
received SNMP requests and controlled access to management information received SNMP requests and controlled access to management
SHOULD be employed in such environments. An authentication protocol is information SHOULD be employed in such environments. An
defined in [12]. A protocol for access control is defined in [15]. authentication protocol is defined in [12]. A protocol for access
control is defined in [15].
Several objects in this MIB allow write access or provide for row Several objects in this MIB allow write access or provide for row
creation. Allowing this support in a non-secure environment can have a creation. Allowing this support in a non-secure environment can have
negative effect on network operations. It is RECOMMENDED that a negative effect on network operations. It is RECOMMENDED that
implementers seriously consider whether set operations or row creation implementers seriously consider whether set operations or row
SHOULD be allowed without providing, at a minimum, authentication of creation SHOULD be allowed without providing, at a minimum,
request origin. It is RECOMMENDED that without such support that the authentication of request origin. It is RECOMMENDED that without
following objects be implemented as read-only: such support that the following objects be implemented as read-only:
o tn3270eRtCollCtlType o tn3270eRtCollCtlType
o tn3270eRtCollCtlSPeriod o tn3270eRtCollCtlSPeriod
o tn3270eRtCollCtlSPMult o tn3270eRtCollCtlSPMult
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshHigh
o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlThreshLow
o tn3270eRtCollCtlIdleCount o tn3270eRtCollCtlIdleCount
o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry1
o tn3270eRtCollCtlBucketBndry2 o tn3270eRtCollCtlBucketBndry2
o tn3270eRtCollCtlBucketBndry3 o tn3270eRtCollCtlBucketBndry3
o tn3270eRtCollCtlBucketBndry4 o tn3270eRtCollCtlBucketBndry4
o tn3270eRtCollCtlRowStatus o tn3270eRtCollCtlRowStatus
The administrative method to use to create and manage the The administrative method to use to create and manage the
tn3270eRtCollCtlTable when SET support is not allowed is outside of the tn3270eRtCollCtlTable when SET support is not allowed is outside of
scope of this memo. the scope of this memo.
7.0 Intellectual Property 7.0 Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; neither does it represent that it
effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances 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 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 obtain a general license or permission for the use of such
rights by implementers or users of this specification can be obtained proprietary rights by implementers or users of this specification can
from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
which may cover technology that may be required to practice this rights which may cover technology that may be required to practice
standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
8.0 Acknowledgments 8.0 Acknowledgments
This document is a product of the TN3270E Working Group. Special thanks This document is a product of the TN3270E Working Group. Special
are due to Derek Bolton and Michael Boe of Cisco Systems for their thanks are due to Derek Bolton and Michael Boe of Cisco Systems for
numerous comments and suggestions for improving the structure of this their numerous comments and suggestions for improving the structure
MIB. Thanks also to Randy Presuhn of BMC Software for his valuable of this MIB. Thanks also to Randy Presuhn of BMC Software for his
review comments on several versions of the document. valuable review comments on several versions of the document.
9.0 References 9.0 References
[1] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T.J. Watson Research,
January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [1] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for
Management Information for TCP/IP-based Internets", RFC 1155, Describing SNMP Management Frameworks", RFC 2271, January 1998.
Performance Systems International, Hughes LAN Systems, May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Performance Systems International, Hughes LAN Systems, March 1991 Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1215, Performance Systems International, March 1991 RFC 1212, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [4] Rose, M., "A Convention for Defining Traps for use with the
of Management Information for Version 2 of the Simple Network SNMP", RFC 1215, March 1991.
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure
Conventions for Version 2 of the Simple Network Management Protocol of Management Information for Version 2 of the Simple Network
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1902, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Statements for Version 2 of the Simple Network Management Protocol Conventions for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., Protocol (SNMPv2)", RFC 1903, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Management Protocol", RFC 1157, SNMP Research, Performance Systems "Conformance Statements for Version 2 of the Simple Network
International, Performance Systems International, MIT Laboratory Management Protocol (SNMPv2)", RFC 1904, January 1996.
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, Network Management Protocol", STD 15, RFC 1157, May 1990.
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Mappings for Version 2 of the Simple Network Management Protocol "Introduction to Community-based SNMPv2", RFC 1901, January
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Processing and Dispatching for the Simple Network Management Mappings for Version 2 of the Simple Network Management Protocol
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, (SNMPv2)", RFC 1906, January 1996.
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC Processing and Dispatching for the Simple Network Management
2274, IBM T. J. Watson Research, January 1998. Protocol (SNMP)", RFC 2272, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
Operations for Version 2 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv3)", RFC 2274, January 1998.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco Operations for Version 2 of the Simple Network Management
Systems, January 1998 Protocol (SNMPv2)", RFC 1905, January 1996.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
Control Model (VACM) for the Simple Network Management Protocol 2273, January 1998.
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
854, May 1983. Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, January 1998.
[17] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [16] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
May 1983. 8, RFC 854, May 1983.
[18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [17] Postel, J. and J. Reynolds, "Telnet Timing Mark Option", STD 31,
RFC 860, May 1983.
[19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998. [18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January
1988.
[20] White, K. and Moore, R., "Base Definitions of Managed Objects for [19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
TN3270E Using SMIv2", Internet-Draft Work in progress, April 1998.
[21] IBM, International Technical Support Centers, "Response Time Data [20] White, K. and R. Moore, "Base Definitions of Managed Objects for
Gathering", GG24-3212-01, November 1990. TN3270E Using SMIv2", RFC 2561, April 1999.
[22] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF [21] IBM, International Technical Support Centers, "Response Time
Standards Process", BCP 11, RFC 2028, October 1996. Data Gathering", GG24-3212-01, November 1990.
[23] Bradner, S., "Key words for use in RFCs to Indicate Requirement [22] Hovey, R. and S. Bradner, "The Organizations Involved in the
Levels", BCP 14, RFC 2119, March 1997. IETF Standards Process", BCP 11, RFC 2028, October 1996.
[23] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
10.0 Authors' Addresses 10.0 Authors' Addresses
Kenneth D. White
Dept. BRQA/Bldg. 501/G114
IBM Corporation
P.O.Box 12195
3039 Cornwallis
Research Triangle Park, NC 27709, USA
E-mail: kennethw@vnet.ibm.com
Robert Moore Kenneth D. White
Dept. BRQA/Bldg. 501/G114 Dept. BRQA/Bldg. 501/G114
IBM Corporation IBM Corporation
P.O.Box 12195 P.O.Box 12195
3039 Cornwallis 3039 Cornwallis
Research Triangle Park, NC 27709, USA Research Triangle Park, NC 27709, USA
Phone: +1-919-254-7507
E-mail: remoore@us.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
Phone: +1-919-254-7507
EMail: remoore@us.ibm.com
11.0 Full Copyright Statement 11.0 Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it
assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are included kind, provided that the above copyright notice and this paragraph are
on all such copies and derivative works. However, this document itself included on all such copies and derivative works. However, this
may not be modified in any way, such as by removing the copyright notice document itself may not be modified in any way, such as by removing
or references to the Internet Society or other Internet organizations, the copyright notice or references to the Internet Society or other
except as needed for the purpose of developing Internet standards in Internet organizations, except as needed for the purpose of
which case the procedures for copyrights defined in the Internet developing Internet standards in which case the procedures for
Standards process must be followed, or as required to translate it into copyrights defined in the Internet Standards process must be
languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 203 change blocks. 
1085 lines changed or deleted 1093 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/