draft-ietf-tn3270e-rt-mib-03.txt   draft-ietf-tn3270e-rt-mib-04.txt 
TN3270E Working Group TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-03.txt> Kenneth White INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-04.txt> IBM Corp.
Expiration Date: July 1998 IBM Corp. Expiration Date: October, 1998 Robert Moore
Robert Moore
IBM Corp. IBM Corp.
January 1998
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-03.txt> <draft-ietf-tn3270e-rt-mib-04.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, documents of the Internet Engineering Task Force (IETF), its Areas, and
and its Working Groups. Note that other groups may also distribute its Working Groups. Note that other groups may also distribute working
working documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet Drafts are draft documents valid for a maximum of six months.
months. Internet Drafts may be updated, replaced, or obsoleted by Internet Drafts may be updated, replaced, or obsoleted by other
other documents at any time. It is not appropriate to use Internet documents at any time. It is not appropriate to use Internet Drafts as
Drafts as reference material or to cite them other than as a "working reference material or to cite them other than as a "working draft" or
draft" or "work in progress." "work in progress."
Please check the I-D abstract listing contained in each Internet Please check the I-D abstract listing contained in each Internet Draft
Draft directory to learn the current status of this or any Internet directory to learn the current status of this or any Internet Draft.
Draft. Distribution of this document is unlimited. Distribution of this document is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1997). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This memo defines the protocol and the Management Information Base This memo defines the protocol and the Management Information Base (MIB)
(MIB) for performing response time data collection on TN3270 and for performing response time data collection on TN3270 and TN3270E
TN3270E sessions by a TN3270E server. The response time data sessions by a TN3270E server. The response time data collected by a
collected by a TN3270E server is structured to support both validation TN3270E server is structured to support both validation of service level
of service level agreements and performance monitoring of TN3270 and agreements and performance monitoring of TN3270 and TN3270E Sessions.
TN3270E Sessions. This MIB has as a prerequisite the TN3270E-MIB This MIB has as a prerequisite the TN3270E-MIB, reference [16].
reference [10].
TN3270E, defined by RFC 1647 [11], refers to the enhancements made
to the Telnet 3270 (TN3270) terminal emulation practices. Refer
to: RFC 1041 [4], RFC 854 [2], and RFC 860 [3] for a sample of
White, Moore TN3270E Response Time Collection MIB 26 January 1998
what is meant by TN3270 practices. TN3270E, defined by RFC 1647 [15], refers to the enhancements made to
the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC
1041 [14], RFC 854 [12], and RFC 860 [13] for a sample of what is meant
by TN3270 practices.
The specification of this MIB uses the Structure of Management The specification of this MIB uses the Structure of Management
Information (SMI) for Version 2 of the Simple Network Management Information (SMI) for Version 2 of the Simple Network Management
Protocol Version (refer to RFC1902 [1]). Protocol (refer to RFC1902 [3]).
Table of Contents Table of Contents
1. Introduction.............................................. 2 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The SNMPv2 Network Management Framework................... 3
3. 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.................................... 11
3.4.1 DR Usage............................................... 11
3.4.2 TIMEMARK Usage......................................... 13
3.5 Performance Data Modelling............................... 15
3.5.1 Averaging Response Times............................... 15
3.5.2 Response Time Buckets.................................. 18
4. Structure of the MIB...................................... 18
4.1 tn3270eRtCollCtlTable.................................... 18
4.2 tn3270eRtDataTable....................................... 21
4.3 Notifications............................................ 23
4.4 Advisory Spin Lock Usage................................. 23
5. Definitions............................................... 24
6. Security Considerations................................... 43
7. Intellectual Property..................................... 44
8. Acknowledgments........................................... 44
9. References................................................ 44
10. Authors' Addresses........................................ 45
11. Full Copyright Statement.................................. 46
1. Introduction 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3
nh This document is a product of the TN3270E Working Group. It 3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3
defines a protocol and a MIB module to enable a TN3270E server to col- 3.1 General Response Time Collection . . . . . . . . . . . . . . . 3
lect response time data for both TN3270 and TN3270E clients. Basis 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 TIMEMARK Usage . . . . . . . . . . . . . . . . . . . . . . 12
3.5 Performance Data Modelling . . . . . . . . . . . . . . . . . . 13
3.5.1 Averaging Response Times . . . . . . . . . . . . . . . . . 13
3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . . . 16
4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 17
4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . . . 17
4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . . . 20
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
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 41
1.0 Introduction
This document is a product of the TN3270E Working Group. It defines a
protocol and a MIB module to enable a TN3270E server to collect and keep
track of response time data for both TN3270 and TN3270E clients. Basis
for implementing this MIB: for implementing this MIB:
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using
Using SMIv2 [10]. SMIv2 [16].
o TN3270E RFCs o TN3270E RFCs
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 [19].
White, Moore TN3270E Response Time Collection MIB 26 January 1998 2.0 The SNMP Network Management Framework
document are to be interpreted as described in RFC 2119, reference
[13].
2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of seven major The SNMP Network Management Framework presently consists of six major
components. They are: components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for o the overall architecture, described in RFC 2271 [7].
describing and naming objects for the purpose of management.
o RFC 1903 [6] defines textual conventions for SNMPv2. o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o RFC 1904 [8] defines conformance statements for SNMPv2. o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects
for the Internet suite of protocols.
o RFC 1905 [7] defines transport mappings for SNMPv2. o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8]
-- the protocol for accessing managed information.
o RFC 1906 [5] defines the protocol operations used for network o the user-based security model defined in RFC 2274 [10].
access to managed objects.
o RFC 1907 [9] defines the Management Information Base for SNMPv2. o the view-based access control model defined in RFC 2275 [11].
o RFC 1908 [14] specifies coexistence between SNMP and SNMPv2. Textual conventions are defined in RFC 1903 [4], and conformance
statements are defined in RFC 1904 [5]. Common applications are defined
in RFC 2273 [9].
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
This memo specifies a MIB module that is compliant to the SNMPv2 SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB
A semantically identical MIB module conforming to the SNMPv1 SMI can conforming to the SMIv1 can be produced through the appropriate
be produced through the appropriate translation. translation.
3. 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 Two primary methods exist for measuring response times in SNA networks:
networks:
o The Systems Network Architecture Management Services o The Systems Network Architecture Management Services (SNA/MS)
(SNA/MS) Response Time Monitoring (RTM) function. Response Time Monitoring (RTM) function.
o Timestamping using definite response flows.
White, Moore TN3270E Response Time Collection MIB 26 January 1998 o Timestamping using definite response flows.
This memo defines an approach using definite responses to timestamp This memo defines an approach using definite responses to timestamp the
the flows between a client and its TN3270E server, rather than by use flows between a client and its TN3270E server, rather than by use of the
of the RTM method. Extensions to the SNA/MS RTM flow were considered, RTM method. Extensions to the SNA/MS RTM flow were considered, but this
but this approach was deemed unsuitable since not all TN3270E server 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 agreements
and of interval-based response time collection for performance and of interval-based response time collection for performance
monitoring are preserved in the MIB module defined in this memo. monitoring are preserved in the MIB module defined in this memo.
As mentioned, this memo focuses on using definite responses to As mentioned, this memo focuses on using definite responses to timestamp
timestamp the flows between a client and its TN3270E server for the flows between a client and its TN3270E server for generating
generating performance data. Use of a definite response flow requires performance data. Use of a definite response flow requires that the
that the client supports TN3270E with the RESPONSES function client supports TN3270E with the RESPONSES function negotiated. The
negotiated. The TN3270 TIMEMARK option can be used instead of TN3270 TIMEMARK option can be used instead of definite response for
definite response for supporting TN3270 clients or TN3270E clients supporting TN3270 clients or TN3270E clients that don't support
that don't support RESPONSES. This document focuses first on defining RESPONSES. This document focuses first on defining the protocol and
the protocol and methods for generating performance data using methods for generating performance data using definite responses, and
definite responses, and then describes how the TIMEMARK option can be then describes how the TIMEMARK option can be used instead of definite
used instead of definite response. response.
In an SNA network, a transaction between a client Logical Unit (LU) In an SNA network, a transaction between a client Logical Unit (LU) and
and a target host in general looks as follows: 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 | |
| <---------------------------------------< | | <---------------------------------------< |
skipping to change at page 4, line 50 skipping to change at page 4, line 39
| >---------------------------------------> | | >---------------------------------------> |
| | | |
| 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 illustrate
how timestamping at a target SNA host can be used to generate response how timestamping at a target SNA host can be used to generate response
times. An IBM redbook [12] provides a more detailed description of times. An IBM redbook [12] provides a more detailed description of
response time collection for a transaction of this type. Note that response time collection for a transaction of this type. Note that for
for the purpose of calculating an approximation for network transit the purpose of calculating an approximation for network transit time, it
time, it doesn't matter if the response is positive or negative. Two doesn't matter if the response is positive or negative. Two response
response time values are typically calculated: time values are typically calculated:
White, Moore TN3270E Response Time Collection MIB 26 January 1998
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 a
transaction requires to flow across a network, since the response flow transaction requires to flow across a network, since the response flow
is being substituted for the request flow at the start of the 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 required. Host time, timestamp B - timestamp A, is the actual time that
that the host required to process the transaction. Experience has the host required to process the transaction. Experience has shown that
shown that using the response flow to approximate network transit using the response flow to approximate network transit times is useful,
times is useful, and does correlate well with actual network transit and does correlate well with actual network transit times.
times.
A client SHOULD respond to a definite response request when it A client SHOULD respond to a definite response request when it completes
completes processing the transaction. This is important since it processing the transaction. This is important since it increases the
increases the accuracy of a total response time. Clients that
immediately respond to a definite response request will be attributed accuracy of a total response time. Clients that immediately respond to
with lower total response times then those that actually occurred. a definite response request will be attributed with lower total response
times then those that actually occurred.
The TN3270E-RT-MIB describes a method of collecting performance data 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) sessions;
thus collection of performance data for printer sessions is excluded thus collection of performance data for printer sessions is excluded
from this MIB. This exclusion of printer sessions is not considered a from this MIB. This exclusion of printer sessions is not considered a
problem, since these sessions are not the most important ones for problem, since these sessions are not the most important ones for
response time monitoring, and since historically they were excluded response time monitoring, and since historically they were excluded from
from SNA/MS RTM collection. The tn3270eTcpConnResourceType object in SNA/MS RTM collection. The tn3270eTcpConnResourceType object in a
a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to determine if
determine if a client session is ineligible for response time data a client session is ineligible for response time data collection for
collection for this reason. this reason.
3.2. TN3270E Server Response Time Collection 3.2 TN3270E Server Response Time Collection
A TN3270E server connects an IP client performing 3270 emulation to a A TN3270E server connects a Telnet client performing 3270 emulation to a
target SNA host over both an IP network (IP client to TN3270E server) target SNA host over both a client-side network (client to TN3270E
and an SNA Network (TN3270E server to target SNA host). A TN3270E server) and an SNA Network (TN3270E server to target SNA host). The
server can use SNA definite responses and the TN3270 Enhancement (RFC client-side network is typicaly TCP/IP, but it need not be. For ease of
1647 [11]) RESPONSES function to calculate response times for a exposition this document uses the term "IP network" to refer to the
transaction, by timestamping when a client request arrives at the client-side network, since IP is by far the most common protocol for
server, when the reply arrives from the target host, and when the these networks.
A TN3270E server can use SNA definite responses and the TN3270
Enhancement (RFC 1647 [15]) RESPONSES function to calculate response
times for a transaction, by timestamping when a client request arrives
at the server, when the reply arrives from the target host, and when the
response acknowledging this reply arrives from the client. 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 its timestamps. In addition, there is TN3270E server takes the required timestamps. In addition, it provides
information on how the TN3270 TIMEMARK request/response flow can be information on how a TN3270 TIMEMARK request/response flow can be used
used instead of DR for approximating IP network transit times. instead of DR for approximating IP network transit times.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
The following figure adds a TN3270E server between the client, in this The following figure adds a TN3270E server between the client, in this
case a TN3270E client and the target SNA host: case a TN3270E client and the target SNA host:
------------------------------------------------ ------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server SNA Host | | Server SNA Host |
| Timestamps | | Timestamps |
| | | |
skipping to change at page 6, line 27 skipping to change at page 6, line 22
| | | |
| 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 A TN3270E server can save timestamp D when it receives a client request,
request, save timestamp E when the target SNA host replies, and save save timestamp E when the target SNA host replies, and save timestamp F
timestamp F when the client responds to the definite response request when the client responds to the definite response request that flowed
that flowed with the reply. It doesn't matter whether the target SNA with the reply. It doesn't matter whether the target SNA host requested
host requested a definite response on its reply: if it didn't, the a definite response on its reply: if it didn't, the TN3270E server
TN3270E server makes the request on its own, to enable it to produce makes the request on its own, to enable it to produce timestamp F. In
timestamp F. In this case the TN3270E server does not forward the this case the TN3270E server does not forward the response to the target
response to the target SNA host, as the dotted line in the figure SNA host, as the dotted line in the figure indicates.
indicates.
In order to generate timestamp F, a TN3270E server MUST insure that In order to generate timestamp F, a TN3270E server MUST insure that the
the transaction specifies DR, and that the TN3270E RESPONSES function transaction specifies DR, and that the TN3270E RESPONSES function has
has been negotiated between itself and the client. Negotiation of the been negotiated between itself and the client. Negotiation of the
TN3270E RESPONSES function occurs during the client's TN3270E session TN3270E RESPONSES function occurs during the client's TN3270E session
initialization. The TN3270E servers that the authors are aware of do initialization. The TN3270E servers that the authors are aware of do
request the RESPONSES function during client session initialization. request the RESPONSES function during client session initialization.
TN3270E clients either automatically support the RESPONSES function, TN3270E clients either automatically support the RESPONSES function, or
or can be configured during startup to support it. 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
The MIB provides an object, tn3270eRtCollCtlType, to control several Just as in the SNA case presented above, these response times are also
aspects of response time data collection. One of the available approximations, since the final +/- RSP from the client is being
substituted for the request from the client that began the transaction.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
options in setting up a response time collection policy is to The MIB provides an object, tn3270eRtCollCtlType, to control several
eliminate the IP-network component altogether. This might be done aspects of response time data collection. One of the available options
because it is determined either that the additional IP network traffic in setting up a response time collection policy is to eliminate the
would not be desirable, or that the IP-network component of the IP-network component altogether. This might be done because it is
overall response times is not significant. determined either that the additional IP network traffic would not be
desirable, or that the IP-network component of the overall response
times is not significant.
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 IP- any of the functions necessary for the server to calculate the
network component of response times. For these clients, the most that IP-network component of response times. For these clients, the most
the server can calculate is the SNA-network component of their overall that the server can calculate is the SNA-network component of their
response times; the server records this SNA-network component as the overall response times; the server records this SNA-network component as
TOTAL response time each of these clients' transactions. If a 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 clients,
some of which have the support necessary for including the IP-network some of which have the support necessary for including the IP-network
component in their total response time calculations, and some of which component in their total response time calculations, and some of which
do not, then the server aggregates the data differently depending on do not, then the server aggregates the data differently depending on
whether the collection has been defined to include or exclude the IP- whether the collection has been defined to include or exclude the
network component: IP-network component:
o If the IP-network component is included, then transactions o If the IP-network component is included, then transactions for the
for the clients that don't support calculation of the clients that don't support calculation of the IP-network component
IP-network component of their response times are excluded of their response times are excluded from the aggregation
from the aggregation altogether. altogether.
o If the IP-network component is excluded, then total response
times for ALL clients include only the SNA-network component, o If the IP-network component is excluded, then total response times
even though the server could have included an IP-network for ALL clients include only the SNA-network component, even though
component in the overall response times for some of these the server could have included an IP-network component in the
clients. The server does this by setting timestamp F, which overall response times for some of these clients. The server does
marks the end of a transaction's total response time, equal this by setting timestamp F, which marks the end of a transaction's
to timestamp E, the end of the transaction's SNA-network total response time, equal to timestamp E, the end of the
component. 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 contribution.
If the aggregation specifies that an IP-network component MUST be If the aggregation specifies that an IP-network component MUST be
included in the aggregation's response times, then transactions for included in the aggregation's response times, then transactions for
which an IP-network component cannot be calculated aren't included at which an IP-network component cannot be calculated aren't included at
all. If the aggregation specifies that an IP-network component is not all. If the aggregation specifies that an IP-network component is not
to be included, then only the SNA-network component is used, even for to be included, then only the SNA-network component is used, even for
those transactions for which an IP-network component could have been those transactions for which an IP-network component could have been
calculated. 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 to
give the network operator control over the amount of traffic give the network operator control over the amount of traffic introduced
into the IP network for response time data collection. A DYNAMIC
White, Moore TN3270E Response Time Collection MIB 26 January 1998 definite response is one that the TN3270E server itself adds to a reply,
in a transaction for which the SNA application at the target SNA host
introduced into the IP network for response time data collection. A did not specify DR in its reply. When the +/-RSP comes back from the
DYNAMIC definite response is one that the TN3270E server itself adds client, the server uses this response to calculate timestamp F, but then
to a reply, in a transaction for which the SNA application at the it does not forward the response on to the SNA application (since the
target SNA host did not specify DR in its reply. When the +/-RSP application is not expecting a response to its reply).
comes back from the client, the server uses this response to calculate
timestamp F, but then it does not forward the response on to the SNA
application (since the application is not expecting a response to its
reply).
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 o If the IP-network component is excluded, then there is no reason for
no reason for enabling dynamic definite responses: the enabling dynamic definite responses: the server always sets
server always sets timestamp F equal to timestamp E, so timestamp F equal to timestamp E, so the additional IP-network
the additional IP-network traffic elicited by a dynamic traffic elicited by a dynamic definite response would serve no
definite response would serve no purpose. purpose.
o If the IP-network component is included, then enabling
dynamic definite responses causes MORE transactions to
be included in the aggregated response time values:
- For clients that do not support sending of responses, o If the IP-network component is included, then enabling dynamic
timestamp F can never be calculated, and so their definite responses causes MORE transactions to be included in the
transactions are never included in the aggregate. aggregated response time values:
- For clients that support sending of responses,
timestamp F will always be calculated for transactions - For clients that do not support sending of responses, timestamp
in which the host SNA application specifies DR in F can never be calculated, and so their transactions are never
its reply, and so these transactions will always be
included in the aggregate. included in the aggregate.
- For clients that support sending of responses,
having dynamic definite responses enabled for a
collection results in the inclusion of additional
transactions in the aggregate: specifically, those
for which the host SNA application did not specify
DR in its reply.
A TN3270E server also has the option of substituting TIMEMARK - For clients that support sending of responses, timestamp F will
processing for definite responses in calculating the IP-network always be calculated for transactions in which the host SNA
component of a transaction's response time. Once again, there is no application specifies DR in its reply, and so these transactions
reason for the server to do this if the collection has been set up to will always be included in the aggregate.
exclude the IP-network component altogether in computing response
times. - For clients that support sending of responses, having dynamic
definite responses enabled for a collection results in the
inclusion of additional transactions in the aggregate:
specifically, those for which the host SNA application did not
specify DR in its reply.
A TN3270E server also has the option of substituting TIMEMARK processing
for definite responses in calculating the IP-network component of a
transaction's response time. Once again, there is no reason for the
server to do this if the collection has been set up to exclude the
IP-network component altogether in computing response times.
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- SNA-network component (E - D) for the response times. This SNA-network
component includes the SNA node processing time at both the TN3270E
White, Moore TN3270E Response Time Collection MIB 26 January 1998 server and at the target application.
network component includes the SNA host processing time at both the A host TN3270E server refers to an implementation where the TN3270E
TN3270E server and at the target application. server is collocated with the Systems Network Architecture (SNA) System
Services Control Point (SSCP) for the dependent Secondary Logical Units
(SLUs) that the server makes available to its clients for connecting
into an SNA network. A gateway TN3270E server resides on an SNA node
other than an SSCP, either an SNA type 2.0 node or an APPN node acting
in the role of a Dependent LU Requester (DLUR). Host and gateway
TN3270E server implementations typically differ greatly as to their
internal implementation and System Definition (SYSDEF) requirements.
When a 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 application, then the SNA-network component of a transaction's response
response time will approximately equal the host transit time (B - A) time will approximately equal the host transit time (B - A) described
described previously. A host (as opposed to a gateway) TN3270E server previously. A host TN3270E server implementation can, however,
implementation can typically support the establishment of sessions to typically support the establishment of sessions to target applications
target applications in remote SNA hosts; in this case the SNA-network in SNA hosts remote from itself. In this case the SNA-network component
component equals the actual SNA-network transit time plus two host
transit times.
A host TN3270E server refers to an implementation where the TN3270E of the response time equals the actual SNA-network transit time plus two
server is collocated with the Systems Network Architecture (SNA) host transit times.
System Services Control Point (SSCP) for the dependent Secondary
Logical Units (SLUs) that a server makes available to its clients for
connecting into a SNA network. A gateway TN3270E server resides on an
SNA node other than an SSCP, either an SNA type 2.0 node or an APPN
node acting in the role of a Dependent LU Requester (DLUR). Host and
gateway TN3270E server implementations typically differ greatly as to
their internal implementation and System Definition (SYSDEF)
requirements.
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 It is possible that response time data is collected from TN3270E servers
servers at the same time as a management application is monitoring the at the same time as a management application is monitoring the SNA
SNA sessions at a host. For example, a management application can be sessions at a host. For example, a management application can be
monitoring a secondary logical unit (SLU) while retrieving data from a monitoring a secondary logical unit (SLU) while retrieving data from a
TN3270E server. Consider the following figure: TN3270E server. Consider the following figure:
White, Moore TN3270E Response Time Collection MIB 26 January 1998
------------------------------------------------ ------------------------------------------------
| | | |
| 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 |
| ------------------------------------------> | | ------------------------------------------> |
skipping to change at page 10, line 32 skipping to change at page 9, line 41
------------------------------------------------ ------------------------------------------------
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 approximation of the IP-network component of the overall response time.
time. The IP-network component can be subtracted from the total The IP-network component can be subtracted from the total network
network transit time (which can be captured at an SSCP monitoring SNA transit time (which can be captured at an SSCP monitoring SNA traffic
traffic from/to the SLU) to see the actual SNA versus IP network from/to the SLU) to see the actual SNA versus IP network transit times.
transit times.
The MIB defined by this memo does not specifically address correlation The MIB defined by this memo does not specifically address correlation
of the data it contains with response time data collected by direct of the data it contains with response time data collected by direct
monitoring of SNA resources: its focus is exclusively response time monitoring of SNA resources: its focus is exclusively response time
data collection from a TN3270E server perspective. It has, however, data collection from a TN3270E server perspective. It has, however, in
in conjunction with the TN3270E-MIB [10], been structured to provide conjunction with the TN3270E-MIB [10], been structured to provide the
the information necessary for correlation between TN3270E server- information necessary for correlation between TN3270E server-provided
provided response time information and that gathered from directly response time information and that gathered from directly monitoring SNA
monitoring SNA resources. resources.
A management application attempting to correlate SNA resource usage to A management application attempting to correlate SNA resource usage to
IP clients can monitor either the tn3270eResMapTable or the 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 local
names at the TN3270E server. Neither the tn3270eClientGroupTable, the names at the TN3270E server. Neither the tn3270eClientGroupTable, the
tn3270eResPoolTable, nor the tn3270eClientResMapTable from the tn3270eResPoolTable, nor the tn3270eClientResMapTable from the
White, Moore TN3270E Response Time Collection MIB 26 January 1998
TN3270E-MIB can be used for correlation, since the mappings defined by TN3270E-MIB can be used for correlation, since the mappings defined by
these tables can overlap, and may not provide one-to-one mappings. 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, target SNA host pass through a TN3270E server. In addition, information
information is provided on how the TN3270 TIMEMARK request/response is provided on how the TN3270 TIMEMARK request/response flow can be used
flow can be used in place of DR for approximating IP network transit in place of DR for approximating IP network transit times.
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---> |
skipping to change at page 11, line 52 skipping to change at page 10, line 53
| >----------------------------------------> | | >----------------------------------------> |
| | | |
| 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 a client has sent data Timestamp D is taken at the TN3270E server when a client has sent data
to the server for forwarding to its target SNA host. This is most to the server for forwarding to its target SNA host. This is most likely
when the server finds the end of record indicator in the TCP data
White, Moore TN3270E Response Time Collection MIB 26 January 1998 received from the client. The target SNA application returns its reply
in one or more SNA Request Units (RUs); in this example there are four
RUs in the reply. The first RU is marked as first in chain (FIC), the
next two are marked as middle in chain (MIC), and the last is marked as
last in chain (LIC). Timestamp E SHOULD be taken prior to sending the
likely when the server finds the end of record indicator in the TCP RESPONSES request to the client; normally this is done when the server
data received from the client. The target SNA application returns its receives the LIC RU. Timestamp F is taken when the RESPONSES response
reply in one or more SNA Request Units (RUs); in this example there is received from the client.
are four RUs in the reply. The first RU is marked as first in chain
(FIC), the next two are marked as middle in chain (MIC), and the last
is marked as last in chain (LIC). Timestamp E SHOULD be taken prior
to sending the RESPONSES request to the client; normally this is done
when the server receives the LIC RU. Timestamp F is taken when the
RESPONSES response is received from the client.
A target SNA application doesn't necessarily return data to a client A target SNA application doesn't necessarily return data to a client in
in a transaction; it may, for example, require more data from the a transaction; it may, for example, require more data from the client
client before it can formulate a reply. In this case the application before it can formulate a reply. In this case the application may
may simply return to the TN3270E server a change of direction simply return to the TN3270E server a change of direction indicator. A
indicator. A TCP connection is full duplex: data can be received and TCP connection is full duplex: data can be received and sent on it at
sent on it at the same time. An SNA session, on the other hand, is the same time. An SNA session, on the other hand, is half duplex, with
half duplex, with a change of direction indicator to alter the a change of direction indicator to alter the direction of data flow.
direction of data flow. Timestamps E and F require a reply to flow to Timestamps E and F require a reply to flow to the client. A best-effort
the client. A best-effort approach SHOULD be followed by a TN3270E approach should be followed by a TN3270E server when it attempts to
server when it attempts to calculate timestamps. For cases where the calculate timestamps. For cases where the target SNA application sends
target SNA application sends a change of direction indicator rather a change of direction indicator rather than a reply, it is suggested
than a reply, it is suggested that the entire transaction be omitted that the entire transaction be omitted from any response time
from any response time calculations. calculations.
Another consideration is a mismatch between DR requested on the SNA Another consideration is a mismatch between DR requested on the SNA side
side and DR requested by a TN3270E server. If the SNA host sends a and DR requested by a TN3270E server. If the SNA host sends a
multiple-RU chain, the server does not know until the last RU is multiple-RU chain, the server does not know until the last RU is
received whether DR is being requested. Meanwhile, the server may received whether DR is being requested. Meanwhile, the server may have
have forwarded the first RU in the chain to the client. In practice, forwarded the first RU in the chain to the client. In practice,
therefore, some servers convert ER flows to DR flows. Timestamp E can therefore, some servers convert ER flows to DR flows. Timestamp E can
be taken when the first RESPONSES request flows to the client, and be taken when the first RESPONSES request flows to the client, and
timestamp F when its response is received. In this instance an timestamp F when its response is received. In this instance an
additional timestamp G is needed when the LIC RU is received: additional timestamp G is needed when the LIC RU is received:
White, Moore TN3270E Response Time Collection MIB 26 January 1998
--------------------------------------------------- ---------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server SNA Host | | Server SNA Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D (BB,CD,OIC,ER) | | request D (BB,CD,OIC,ER) |
| ------------------------------------------> | | ------------------------------------------> |
skipping to change at page 13, line 37 skipping to change at page 12, line 8
| | +/-RSP G | | | +/-RSP G |
| >-------------------> | | >-------------------> |
| | | |
--------------------------------------------------- ---------------------------------------------------
The response times can then be calculated as follows: The response times can then be calculated as follows:
o Total response time: Timestamp G - Timestamp D o Total response time: Timestamp G - Timestamp D
o IP network transit time: Timestamp F - Timestamp E o IP network transit time: Timestamp F - Timestamp E
If DR is requested by the LIC RU, then the TN3270E server can use If DR is requested by the LIC RU, then the TN3270E server can may either
either its response or the earlier one for approximating IP network its response or the earlier one for approximating IP network transit
transit time. time.
3.4.2. TIMEMARK Usage 3.4.2 TIMEMARK Usage
It is possible for a TN3270E server to use the TIMEMARK flow for It is possible for a TN3270E server to use the TIMEMARK flow for
approximating IP network transit times. Using TIMEMARKs would make it approximating IP network transit times. Using TIMEMARKs would make it
possible for a server to collect performance data for TN3270 clients, possible for a server to collect performance data for TN3270 clients, as
as well as for TN3270E clients that do not support the RESPONSES well as for TN3270E clients that do not support the RESPONSES function.
function. In order for TIMEMARKs to be used in this way, a client In order for TIMEMARKs to be used in this way, a client can't have the
can't have the NOP option enabled, since responses are needed to the NOP option enabled, since responses are needed to the server's TIMEMARK
server's TIMEMARK requests. An IP network transit time approximation requests. An IP network transit time approximation using a TIMEMARK is
using a TIMEMARK is basically the amount of time it takes for a TN3270 basically the amount of time it takes for a TN3270 server to receive
server to receive from a client a response to a TIMEMARK request. from a client a response to a TIMEMARK request.
If a TN3270E server is performing the TIMEMARK function (independent
White, Moore TN3270E Response Time Collection MIB 26 January 1998
of the response time monitoring use of the function discussed here),
then it most likely has a TIMEMARK interval for determining when to
examine client sessions for sending the TIMEMARK request. This
interval, which is ordinarily a global value for an entire TN3270E
server, is represented in the TN3270E-MIB by the
tn3270eSrvrConfActivityInterval object. A TIMEMARK request is sent
only if, when it is examined, a client session is found to have had no
activity for a different fixed length of time, represented in the
TN3270E-MIB by the tn3270eSrvrConfActivityTimeout object.
If a TN3270E server sends a TIMEMARK request to every client with no To get an estimate for IP network transit time, a TN3270E server sends a
session activity, based solely on the server's TIMEMARK interval, then TIMEMARK request to a client after a LIC RU has been received, as a
network flooding may result, since a server may be supporting means of approximating IP network transit time:
thousands of client sessions. The use of TIMEMARKs for response time
monitoring could help to reduce this network flooding. Suppose a
server sends a TIMEMARK request to a client after a LIC RU has been
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) |
skipping to change at page 15, line 5 skipping to change at page 12, line 58
| | TIMEMARK Rsp F' | | | TIMEMARK 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')
White, Moore TN3270E Response Time Collection MIB 26 January 1998
o TN3270E server IP network time: Timestamp F' - Timestamp E' o TN3270E server IP network time: Timestamp F' - Timestamp E'
A TN3270E server needs to consider its normal TIMEMARK processing when If a TN3270E server is performing the TIMEMARK function (independent of
using TIMEMARKs for this purpose. For example, it MUST not send a the response time monitoring use of the function discussed here), then
second TIMEMARK request to a client while waiting for the first to it most likely has a TIMEMARK interval for determining when to examine
return. Also, if a TIMEMARK flow has just been performed for a client client sessions for sending the TIMEMARK request. This interval, which
shortly before the LIC RU arrives, the server might use the interval is ordinarily a global value for an entire TN3270E server, is
from this flow as its approximation for IP network transit time, (in represented in the TN3270E-MIB by the tn3270eSrvrConfActivityInterval
other words, as its (F' - E') value) when calculating its object. A TIMEMARK request is sent only if, when it is examined, a
approximation for the transaction's total response time. client session is found to have had no activity for a different fixed
length of time, represented in the TN3270E-MIB by the
tn3270eSrvrConfActivityTimeout object.
Servers that support a large number of client sessions should spread out
the TIMEMARK requests they send to these clients over the activity
interval, rather than sending them all in a single burst, since
otherwise the network may be flooded with TIMEMARK requests. When a
server uses TIMEMARKs for approximating response times, this tends to
introduce a natural spreading into its TIMEMARK requests, since the
requests are triggered by the arrival of traffic from an SNA host.
A TN3270E server MUST integrate its normal TIMEMARK processing with its
use of TIMEMARKs for computing response times. In particular, it MUST
NOT send a second TIMEMARK request to a client while waiting for the
first to return, since this is ruled out by the TIMEMARK protocol
itself. If a TIMEMARK flow has just been performed for a client shortly
before the LIC RU arrives, the server MAY use the interval from this
flow as its approximation for IP network transit time, (in other words,
as its (F' - E') value) when calculating its approximation for the
transaction's total response time, rather than sending a second TIMEMARK
request so soon after the preceding one.
Regardless of when the server sends its TIMEMARK request, the accuracy Regardless of when the server sends its TIMEMARK request, the accuracy
of its total response time calculation depends on exactly when the of its total response time calculation depends on exactly when the
client responds to the TIMEMARK request. client responds to the TIMEMARK 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 and
controls capture of two types of response time data: average response controls capture of two types of response time data: average response
times and response time buckets. 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 averages, because they are often more meaningful, and because they cause
cause less notification thrashing. Sliding-window average calculation less notification thrashing. Sliding-window average calculation can, if
can, if necessary, be disabled, by setting the sample period necessary, be disabled, by setting the sample period multiplier,
multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample tn3270eRtCollCtlSPMult, to 1, and setting the sample period,
period, tn3270eRtCollCtlSPeriod, to the required collection interval. 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 o Select a fixed, relatively short, sample period SPeriod; the default
default value for SPeriod in the MIB is 20 seconds. value for SPeriod in the MIB is 20 seconds.
o Select an averaging period multiplier SPMult. The actual o Select an averaging period multiplier SPMult. The actual collection
collection interval will then be SPMult times SPeriod. The interval will then be SPMult times SPeriod. The default value for
default value for SPMult in the MIB is 30, yielding a default SPMult in the MIB is 30, yielding a default collection interval of
collection interval of 10 minutes. Note that the collection 10 minutes. Note that the collection interval (SPMult*SPeriod) is
interval (SPMult*SPeriod) is always a multiple of the sample always a multiple of the sample period.
White, Moore TN3270E Response Time Collection MIB 26 January 1998 o Maintain the following counters to keep track of activity within the
current sample period; these are internal counters, not made visible
to a management application via the MIB.
period. - T (number of transactions in the period)
o Maintain the following counters to keep track of activity within - TotalRts (sum of the total response times for all transactions
the current sample period; these are internal counters, not in the period)
made visible to a management application via the MIB.
- T (number of transactions in the period) - TotalIpRts (sum of the IP network transit times for all
- TotalRts (sum of the total response times for all transactions in the period; note that if IP network transit
transactions in the period) times are being excluded from the response time collection, this
- TotalIpRts (sum of the IP network transit times for value will always be 0).
all transactions in the period; note that if IP
network transit times are being excluded from the
response time collection, this value will always be 0).
o Also maintain sliding counters, initialized to zero, for each o Also maintain sliding counters, initialized to zero, for each of the
of the quantities being counted: 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: 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 Then reset T, TotalRts, and TotalIpRts to zero for use during the
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: objects as indicated; the floating-point numbers are rounded 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 response time collection, then tn3270eRtDataAvgIpRt will always
from response time collection, then tn3270eRtDataAvgIpRt return 0.
will always return 0.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
The sliding transaction counter AvgCountTrans is not used for updating The sliding transaction counter AvgCountTrans is not used for updating
the MIB object tn3270eRtDataCountTrans: this object is an ordinary the MIB object tn3270eRtDataCountTrans: this object is an ordinary SMI
SMI Counter32, which maintains a total count of transactions since its Counter32, which maintains a total count of transactions since its last
last discontinuity event. The sliding counters are used only for discontinuity event. The sliding counters are used only for calculating
calculating averages. 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. A
tn3270eRtExceeded notification is generated the first time 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. After this, no other tn3270eRtExceeded exceeded the high threshold. (The test for statistical significance is
notifications are generated until an average response time is found to described below.) After this, no other tn3270eRtExceeded notifications
have fallen below the low threshold. are generated until an average response time is found to have fallen
below the low threshold.
The other mechanism to limit notifications is the significance test The other mechanism to limit notifications is the significance test for
for a high average response time. Intuitively, the significance of an a high average response time. Intuitively, the significance of an
average is directly related to the number of samples that go into it; average is directly related to the number of samples that go into it; so
so we might be inclined to use a rule such as "for the purpose of we might be inclined to use a rule such as "for the purpose of
generating tn32709eRtExceeded 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, guarantee that there will not be many transactions in a sample, because
because these transactions "use up" the sampling time. Yet this case these transactions "use up" the sampling time. Yet this case of a few
of a few transactions with very poor response times SHOULD obviously transactions with very poor response times should obviously be
be classified as a problem, not as a statistical anomaly based on too classified as a problem, not as a statistical anomaly based on too small
small a sample. 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 function
of the average response time. In order to determine at a collection of the average response time. A value IdleCount is specified, which is
interval whether to generate a tn3270eRtExceeded notification, a used to qualify an sample as statistically significant. In order to
TN3270E server uses the following algorithm: determine at a collection interval whether to generate a
tn3270eRtExceeded notification, a TN3270E server uses the following
algorithm:
if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 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
tn3270eRtDataAvgRt at the end of the interval, and the "**" notation
indicates exponientiation.
Two examples illustrate how this algorithm works. Suppose that Two examples illustrate how this algorithm works. Suppose that
IdleRate has been set to 20 transactions, and the high threshold to IdleCount has been set to 20 transactions, and the high threshold to 200
200 msecs per transaction. If the average observed response time is msecs per transaction. If the average observed response time is 300
300 msecs, then a notification will be generated only if AvgCountTrans msecs, then a notification will be generated only if AvgCountTrans >=
>= 80. If, however, the observed response time is 500 msecs, then a
80. If, however, the observed response time is 500 msecs, then a
notification is generated if AvgCountTrans >= 9. 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
White, Moore TN3270E Response Time Collection MIB 26 January 1998
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 The MIB also supports collection of response time data into a set of
five buckets. This data is suitable either for verification of service five buckets. This data is suitable either for verification of service
level agreements, or for monitoring by a management application to level agreements, or for monitoring by a management application to
identify performance problems. The buckets provide counts of identify performance problems. The buckets provide counts of
transactions whose total response times fall into a set of specified transactions whose total response times fall into a set of specified
ranges. ranges.
Like everything for a collection, the "total" response times collected Like everything for a collection, the "total" response times collected
in the buckets are governed by the specification of whether IP network in the buckets are governed by the specification of whether IP network
transit times are to be included in the totals. Depending on how this transit times are to be included in the totals. Depending on how this
option is specified, the response times being counted in the buckets option is specified, the response times being counted in the buckets
will either be total response times (F - D), or only SNA network will either be total response times (F - D), or only SNA network transit
transit times (effectively E - D, because when it is excluding the times (effectively E - D, because when it is excluding the IP-network
IP-network component of transactions, a server makes timestamp F component of transactions, a server makes timestamp F identical to
identical to timestamp E). timestamp E).
Four bucket boundaries are specified for a response time collection, Four bucket boundaries are specified for a response time collection,
resulting in five buckets. The first response time bucket counts resulting in five buckets. The first response time bucket counts those
those transactions whose total response times were less than or equal transactions whose total response times were less than or equal to
to Boundary 1, the second bucket counts those whose response times Boundary 1, the second bucket counts those whose response times were
were greater than Boundary 1 but less than or equal to Boundary 2, and greater than Boundary 1 but less than or equal to Boundary 2, and so on.
so on. The fifth bucket is unbounded on the top, counting all The fifth bucket is unbounded on the top, counting all transactions
transactions whose response times were greater than Boundary 4. whose response times were greater than Boundary 4.
The four bucket boundaries have default values of: 1 second, 2 The four bucket boundaries have default values of: 1 second, 2 seconds,
seconds, 5 seconds, and 10 seconds, respectively. These values are 5 seconds, and 10 seconds, respectively. These values are the defaults
the defaults in the 3174 controller's implementation of the SNA/MS RTM in the 3174 controller's implementation of the SNA/MS RTM function, and
function, and were thought to be appropriate for this MIB as well. are thought to be appropriate for this MIB as well.
In SNA/MS the counter buckets were (by today's standards) relatively 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 small, with a maximum value of 65,535. The bucket objects in the MIB
are all Counter32's. are all Counter32's.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
The following figure represents the buckets pictorially: The following figure represents the buckets pictorially:
---------------------------------------------- ----------------------------------------------
| | | |
| Response Time Boundaries | | Response Time Boundaries |
| | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
| | | | | | no | | | | | | | no |
| 0 B-1 B-2 B-3 B-4 bound| | 0 B-1 B-2 B-3 B-4 bound|
| | | | | | | | | | | | | | | |
| |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| | | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| |
| ----------------------------------------- | | ----------------------------------------- |
| | | |
---------------------------------------------- ----------------------------------------------
4. 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 for which response time data is to be collected. The set of clients is
is defined using the tn3270eClientGroupTable from the TN3270E-MIB. defined using the tn3270eClientGroupTable from the TN3270E-MIB.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
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 |
| tn3270eRtCollCtlIdleRate 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, and
thus allows selection of multiple options. thus allows selection of multiple options.
The BITS in the tn3270eRtCollCtlType object have the following The BITS in the tn3270eRtCollCtlType object have the following meanings:
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 aggregated for the whole client group. In this case there will be
be only one row created for the collection in the only one row created for the collection in the tn3270eRtDataTable.
tn3270eRtDataTable. The first two indexes for this row, The first two indexes for this row, tn3270eSrvrConfIndex and
tn3270eSrvrConfIndex and tn3270eClientGroupName, will tn3270eClientGroupName, will have the same values as the indexes as
have the same values as the indexes as the corresponding the corresponding tn3270eRtCollCtlEntry. The third and fourth
tn3270eRtCollCtlEntry. The third and fourth indexes of an indexes of an aggregated tn3270eRtDataEntry have the values
aggregated tn3270eRtDataEntry have the values unknown(0) unknown(0) (tn3270eRtDataClientAddrType) and a zero-length octet
(tn3270eRtDataClientAddrType) and a zero-length octet string string (tn3270eRtDataClientAddress).
(tn3270eRtDataClientAddress).
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 for each member of the client group. In this
case the tn3270eRtDataClientAddress contains the client's actual case the tn3270eRtDataClientAddress contains the client's actual IP
IP Address, and tn3270eRtDataClientAddrType indicates the Address, and tn3270eRtDataClientAddrType indicates the address type.
address type.
o excludeIpComponent(1) - If this bit is set to 1, then the
server SHOULD exclude the IP-network component from all the
response times for this collection. If the target SNA
application specifies DR in any of its replies, this DR will
White, Moore TN3270E Response Time Collection MIB 26 January 1998
still be passed down to the client, and the client's response o excludeIpComponent(1) - If this bit is set to 1, then the server
will still be forwarded to the application. But this response SHOULD exclude the IP-network component from all the response times
will play no role in the server's response time calculations. for this collection. If the target SNA application specifies DR in
any of its replies, this DR will still be passed down to the client,
and the client's response will still be forwarded to the
application. But this response will play no role in the server's
response time calculations.
If this bit is set to 0, then the server includes in the If this bit is set to 0, then the server includes in the collection
collection only those transactions for which it can include an only those transactions for which it can include an (approximate)
(approximate) IP-network component in the total response time IP-network component in the total response time for the transaction.
for the transaction. This component MAY be derived from a This component MAY be derived from a "natural" DR (if the client
"natural" DR (if the client supports the RESPONSES function), supports the RESPONSES function), from a dynamic DR introduced by
from a dynamic DR introduced by the server (if the client the server (if the client supports the RESPONSES function and the
supports the RESPONSES function and the ddr(2) bit has been ddr(2) bit has been set to 1), or from TIMEMARK processing (if the
set to 1), or from TIMEMARK processing (if the client supports client supports TIMEMARKs).
TIMEMARKs).
If this bit is set to 1, then the ddr(2) bit is ignored, since If this bit is set to 1, then the ddr(2) bit is ignored, since there
there is no reason for the server to request additional is no reason for the server to request additional responses from the
responses from the client(s) in the group. client(s) in the group.
o ddr(2) - If this bit is set to 1, then the server SHOULD, for o ddr(2) - If this bit is set to 1, then the server SHOULD, for those
those clients in the group that support the RESPONSES function, clients in the group that support the RESPONSES function, add a DR
add a DR request to a reply in each transaction (usually, but request to a reply in each transaction (usually, but not necessarily
not necessarily the LIC reply), and use the client's subsequent the LIC reply), and use the client's subsequent response for
response for calculating an (approximate) IP-network component calculating an (approximate) IP-network component to include in the
to include in the transaction's total response times. transaction's total response times.
If this bit is set to 0, then the server does not add a DR If this bit is set to 0, then the server does not add a DR request
request to any replies from the target SNA application. to any replies 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 calculate a sliding-window average for the collection, based on the
on the parameters specified for the group. parameters specified for the group.
If this bit is set to 0, then an average is not calculated. In
this case the tn3270eRtExceeded and tn3270eRtOkay notifications
are not generated, even if the traps(5) bit is set to 1.
o buckets(4) - If this bit is set to 1, then the server SHOULD
create and increment response time buckets for the collection,
based on the parameters specified for the group.
If this bit is set to 0, then response time buckets are not If this bit is set to 0, then an average is not calculated. In this
created. case the tn3270eRtExceeded and tn3270eRtOkay notifications are not
generated, even if the traps(5) bit is set to 1.
o traps(5) - If this bit is set to 1, then a TN3270E Server o buckets(4) - If this bit is set to 1, then the server SHOULD create
is enabled to generate notifications pertaining to an and increment response time buckets for the collection, based on the
parameters specified for the group.
White, Moore TN3270E Response Time Collection MIB 26 January 1998 If this bit is set to 0, then response time buckets are not created.
tn3270eCollCtlEntry. tn3270CollStart and tn3270CollEnd o traps(5) - If this bit is set to 1, then a TN3270E Server is enabled
generation is enable simply by traps(5) being set to 1. to generate notifications pertaining to an tn3270eCollCtlEntry.
tn3270eRtExceeded and tn3270eRtOkay generation enablement tn3270CollStart and tn3270CollEnd generation is enabled simply by
requires that average(3) be set to 1 in addition to the traps(5) being set to 1. tn3270eRtExceeded and tn3270eRtOkay
traps(5) requirement. generation enablement 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 If traps(5) is set to 0, then none of the notifications defined in
in this MIB are generated for a particular this MIB are generated for a particular tn3270eRtCollCtlEntry.
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. If the average(3) bit is for response time data collection to occur; both bits MAY be set to 1.
set to 1, then the following objects have meaning, and are used to If the average(3) bit is set to 1, then the following objects have
control the calculation of the averages, as well as the generation of meaning, and are used to control the calculation of the averages, as
the two notifications related to them: 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 tn3270eRtCollCtlIdleRate o tn3270eRtCollCtlIdleCount
The previous objects' values are meaningless if the associated The previous objects' values are meaningless if the associated
average(3) bit setting is not set to 1. It is RECOMMENDED that an average(3) bit is not set to 1.
implementation return the default values for these objects when
average(3) 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 setting is not set to 1. It is RECOMMENDED that an buckets(4) bit is not set to 1.
implementation return the default values for these objects when
buckets(4) is not set to 1.
4.2. tn3270eRtDataTable If an entry in the tn3270RtCollCtlTable has the value active(1) for its
RowStatus, then an implementation SHALL NOT allow Set operations for any
objects in the entry except:
Either a single entry or multiple entries are created in the o tn3270eRtCollCtlThreshHigh
tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on o tn3270eRtCollCtlThreshLow
whether tn3270eRtCollCtlType in the control entry has aggregate(0) o tn3270eRtCollCtlRowStatus
selected. The contents of an entry in the tn3270eRtDataTable depend
White, Moore TN3270E Response Time Collection MIB 26 January 1998 4.2 tn3270eRtDataTable
on the contents of the corresponding entry in the Either a single entry or multiple entries are created in the
tn3270eRtCollCtlTable: some objects in the data entry return tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on whether
meaningful values only when the average(3) option is selected in the tn3270eRtCollCtlType in the control entry has aggregate(0) selected.
control entry, while others return meaningful values only when the The contents of an entry in the tn3270eRtDataTable depend on the
buckets(4) option is selected. If both options are selected, then all contents of the corresponding entry in the tn3270eRtCollCtlTable: as
the objects return meaningful values. When an object is not specified described above, some objects in the data entry return meaningful values
to return a meaningful value, an implementation may return any value only when the average(3) option is selected in the control entry, while
in response to a Get operation. others return meaningful values only when the buckets(4) option is
selected. If both options are selected, then all the objects return
meaningful values. When an object is not specified to return a
meaningful value, an implementation may return any syntactically valid
value in response to a Get operation.
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 sliding-window average calculations described earlier. The time of the
the most recent sample for these calculations is returned in the most recent sample for these calculations is returned in the
tn3270eRtDaraIntTimeStamp 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 total
transactions. The last two objects return sum of the squares values, transactions. The last two objects return sum of the squares values, to
to enable variance calculations by a management application. 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 discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a
a management application to detect when the values of the counter management application to detect when the values of the counter objects
objects in this table may have been reset, or otherwise experienced a in this table may have been reset, or otherwise experienced a
discontinuity. A possible cause for such a discontinuity is the discontinuity. A possible cause for such a discontinuity is the TN3270E
TN3270E server's being stopped or restarted. This object returns a server's being stopped or restarted. This object returns a meaningful
meaningful value regardless of which collection control options were value regardless of which collection control options were selected.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
selected.
An object, tn3270eRtDataRtMethod, identifies whether the IP Network An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time
Time was calculated using either the definite response or TIMEMARK was calculated using either the definite response or TIMEMARK 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 tn3270eRtDataClientAddress has the value of a zero-length octet string,
string, and its tn3270eRtDataClientAddrType has the value of and its tn3270eRtDataClientAddrType has the value of unknown(0).
unknown(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 to
be members of the client group when these clients establish sessions be members of the client group when these clients establish sessions
with the server. with the server. Entries are also created when clients with existing
sessions are added to the group.
All entries associated with a tn3270eRtCollCtlEntry are deleted from All entries associated with a tn3270eRtCollCtlEntry are deleted from the
the tn3270eRtDataTable when that entry is deleted from 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. group is deleted when its TCP connection terminates. Once it has been
created, a client's entry in the tn3270eRtDataTable remains active as
long as the collection's tn3270eRtCollCtlEntry exists, even if the
client is removed from the client group for the tn3270eRtCollCtlEntry.
4.3. Notifications 4.3 Notifications
This MIB defines four notifications related to a tn3270eRtDataEntry. This MIB defines four notifications related to a tn3270eRtDataEntry. If
If the associated tn3270eRtCollCtlType object's traps(5) bit is set to the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1,
1, then the tn3270RtCollStart and tn3270RtCollEnd notifications are then the tn3270RtCollStart and tn3270RtCollEnd notifications are
generated when, respsectively, the tn3270eRtDataEntry is created and generated when, respsectively, the tn3270eRtDataEntry is created and
deleted. If, in addition, this tn3270eRtCollCtlType object's deleted. If, in addition, this tn3270eRtCollCtlType object's average(3)
average(3) bit is set to 1, then the the tn3270eRtExceeded and bit is set to 1, then the the tn3270eRtExceeded and tn3270eRtOkay
tn3270eRtOkay notifications are generated when the conditions they notifications are generated when the conditions they report occur.
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 o tn3270eRtExceeded - The purpose of this notification is to signal
signal that a performance problem has been detected. If that a performance problem has been detected. If average(3)
average(3) response time data is being collected, then this response time data is being collected, then this notification is
notification is generated whenever (1) an average response generated whenever (1) an average response time is first found, on a
time is first found, on a collection interval boundary, to collection interval boundary, to have exceeded the high threshold
have exceeded the high threshold tn3270eRtCollCtlThreshHigh tn3270eRtCollCtlThreshHigh specified for the client group, AND (2)
specified for the client group, AND (2) the sample on which the the sample on which the average is based is determined to have been
average is based is determined to have been a significant one, a significant one, via the significance algorithm described earlier.
This notification is not generated again for a tn3270eRtDataEntry
White, Moore TN3270E Response Time Collection MIB 26 January 1998 until an average response time falling below the low threshold
tn3270eRtCollCtlThreshLow specified for the client group has
occurred for the entry.
via the significance algorithm described earlier. This o tn3270eRtOkay - The purpose of this notification is to signal that a
notification is not generated again for a tn3270eRtDataEntry previously reported performance problem has been resolved. If
until an average response time falling below the low average(3) response time data is being collected, then this
threshold tn3270eRtCollCtlThreshLow specified for the client notification is generated whenever (1) a tn3270eRtExceeded
notification has already been generated, AND (2) an average response
time is first found, on a collection interval boundary, to have
fallen below the low threshold tn3270eRtCollCtlThreshLow specified
for the client group. This notification is not generated again for
a tn3270eRtDataEntry until an average response time exceeding the
high threshold tn3270eRtCollCtlThreshHigh specified for the client
group has occurred for the entry. group has occurred for the entry.
o tn3270eRtOkay - The purpose of this notification is to signal
that a previously reported performance problem has been
resolved. If average(3) response time data is being collected,
then this notification is generated whenever (1) a
tn3270eRtExceeded notification has already been generated, AND
(2) an average response time is first found, on a collection
interval boundary, to have fallen below the low threshold
tn3270eRtCollCtlThreshLow specified for the client group.
This notification is not generated again for a
tn3270eRtDataEntry until an average response time
exceeding the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group has occurred for the entry.
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 o tn3270eRtCollStart - This notification is generated whenever data
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 tn3270eRtDataEntry becomes active. The primary purpose of this
this notification is signal to a management application that notification is signal to a management application that a new client
a new client TCP session has been established, and to provide TCP session has been established, and to provide the IP-to-resource
the IP-to-resource mapping for the session. This notification mapping for the session. This notification is not critical when
is not critical when average(3) data collection is not being average(3) data collection is not being performed for the client
performed for the client group. group.
o tn3270eRtCollEnd - This notification is generated whenever o tn3270eRtCollEnd - This notification is generated whenever a data
a data collection ends. For an aggregate collection, this collection ends. For an aggregate collection, this occurs when the
occurs when the corresponding tn3270eRtCollCtlEntry is corresponding tn3270eRtCollCtlEntry is deleted. For an individual
deleted. For an individual collection, this occurs either collection, this occurs either when the tn3270eRtCollCtlEntry is
when the tn3270eRtCollCtlEntry is deleted, or when the deleted, or when the client's TCP connection terminates. The
client's TCP connection terminates. The purpose of this purpose of this notification is to enable a management application
notification is to enable a management application to to complete a monitoring function that it was performing, by
complete a monitoring function that it was performing, by
returning final values for the collection's data objects. 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 in order to
provide an advisory lock that MAY be used to allow cooperating TN3270E-
RT-MIB applications to coordinate their use of the
White, Moore TN3270E Response Time Collection MIB 26 January 1998
tn3270eRtCollCtlTable. When creating an new entry or altering an Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory
existing entry in the tn3270eRtCollCtlTable, it MAY be necessary for lock that allows cooperating TN3270E-RT-MIB applications to coordinate
applications to make use of tn3270eRtSpinLock to serialize application their use of the tn3270eRtCollCtlTable. When creating a new entry or
changes or additions. Since this is an advisory lock, the use of this altering an existing entry in the tn3270eRtCollCtlTable, an application
lock is not enforced. SHOULD make use of tn3270eRtSpinLock to serialize application changes or
additions. Since this is an advisory lock, its use by management
applications SHALL NOT be not enforced by agents. Agents MUST, however,
implement the tn3270eRtSpinLock object.
5. 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
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex, Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex,
tn3270eClientGroupName, tn3270eResMapElementType tn3270eClientGroupName, tn3270eResMapElementType
FROM TN3270E-MIB FROM TN3270E-MIB
snanauMIB snanauMIB
FROM SNA-NAU-MIB; FROM SNA-NAU-MIB;
tn3270eRtMIB MODULE-IDENTITY tn3270eRtMIB MODULE-IDENTITY
LAST-UPDATED "9801290000Z" -- January 29, 1998 LAST-UPDATED "9804300000Z" -- April 30, 1998
ORGANIZATION "TN3270E Working Group" ORGANIZATION "TN3270E Working Group"
CONTACT-INFO CONTACT-INFO
"Kenneth White (kennethw@vnet.ibm.com) "Kenneth White (kennethw@vnet.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
(919) 254-0102
Robert Moore (remoore@us.ibm.com) Robert Moore (remoore@us.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
(919) 254-4436" (919) 254-4436"
DESCRIPTION DESCRIPTION
"This module defines a portion of the management "This module defines a portion of the management
information base (MIB) that enables monitoring of information base (MIB) that enables monitoring of
TN3270 and TN3270E clients' response times by a TN3270 and TN3270E clients' response times by a
TN3270E server." TN3270E server."
::= { snanauMIB 9 } ::= { snanauMIB 9 }
White, Moore TN3270E Response Time Collection MIB 26 January 1998
-- snanauMIB ::= { mib-2 34 } -- snanauMIB ::= { mib-2 34 }
-- Top level structure of the MIB -- Top level structure of the MIB
tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 } tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 }
tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 } tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 }
tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 } tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 }
-- MIB Objects -- MIB Objects
skipping to change at page 28, line 4 skipping to change at page 24, line 25
control table. To handle the case of multiple TN3270E control table. To handle the case of multiple TN3270E
servers on the same host, the first index of this table is servers on the same host, the first index of this table is
the tn3270eSrvrConfIndex from the TN3270E-MIB." the tn3270eSrvrConfIndex from the TN3270E-MIB."
INDEX { INDEX {
tn3270eSrvrConfIndex, -- Server's index tn3270eSrvrConfIndex, -- Server's index
tn3270eClientGroupName } -- What to collect on tn3270eClientGroupName } -- What to collect on
::= { tn3270eRtCollCtlTable 1 } ::= { tn3270eRtCollCtlTable 1 }
Tn3270eRtCollCtlEntry ::= SEQUENCE { Tn3270eRtCollCtlEntry ::= SEQUENCE {
tn3270eRtCollCtlType BITS, tn3270eRtCollCtlType BITS,
White, Moore TN3270E Response Time Collection MIB 26 January 1998
tn3270eRtCollCtlSPeriod Unsigned32, tn3270eRtCollCtlSPeriod Unsigned32,
tn3270eRtCollCtlSPMult Unsigned32, tn3270eRtCollCtlSPMult Unsigned32,
tn3270eRtCollCtlThreshHigh Unsigned32, tn3270eRtCollCtlThreshHigh Unsigned32,
tn3270eRtCollCtlThreshLow Unsigned32, tn3270eRtCollCtlThreshLow Unsigned32,
tn3270eRtCollCtlIdleRate Unsigned32, tn3270eRtCollCtlIdleRate Unsigned32,
tn3270eRtCollCtlBucketBndry1 Unsigned32, tn3270eRtCollCtlBucketBndry1 Unsigned32,
tn3270eRtCollCtlBucketBndry2 Unsigned32, tn3270eRtCollCtlBucketBndry2 Unsigned32,
tn3270eRtCollCtlBucketBndry3 Unsigned32, tn3270eRtCollCtlBucketBndry3 Unsigned32,
tn3270eRtCollCtlBucketBndry4 Unsigned32, tn3270eRtCollCtlBucketBndry4 Unsigned32,
tn3270eRtCollCtlRowStatus RowStatus } tn3270eRtCollCtlRowStatus RowStatus }
skipping to change at page 29, line 4 skipping to change at page 25, line 17
component in any response times. component in any response times.
ddr(2) - Enable dynamic definite response. ddr(2) - Enable dynamic definite response.
average(3) - Produce an average response time average(3) - Produce an average response time
based on a specified collection based on a specified collection
interval. interval.
buckets(4) - Maintain tn3270eRtDataBucket values buckets(4) - Maintain tn3270eRtDataBucket values
in an corresponding in an corresponding
tn3270eRtDataEntry, based on the tn3270eRtDataEntry, based on the
bucket boundaries specified in the bucket boundaries specified in the
tn3270eRtDataBucketBndry objects. tn3270eRtDataBucketBndry objects.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
traps(5) - generate the traps specified in traps(5) - generate the traps specified in
this MIB module. The this MIB module. The
tn3270eRtExceeded and tn3270eRtExceeded and
tn3270eRtOkay are generated tn3270eRtOkay are generated
only if average(3) is also only if average(3) is also
specified." specified."
::= { tn3270eRtCollCtlEntry 2 } ::= { tn3270eRtCollCtlEntry 2 }
tn3270eRtCollCtlSPeriod OBJECT-TYPE tn3270eRtCollCtlSPeriod OBJECT-TYPE
SYNTAX Unsigned32 (15..86400) -- 15 second min, 24 hour max SYNTAX Unsigned32 (15..86400) -- 15 second min, 24 hour max
skipping to change at page 30, line 4 skipping to change at page 26, line 10
The value of this object is used only if the corresponding The value of this object is used only if the corresponding
tn3270eRtCollCtlType has the average(3) setting." tn3270eRtCollCtlType has the average(3) setting."
DEFVAL { 30 } -- yields an interval of 10 minutes when DEFVAL { 30 } -- yields an interval of 10 minutes when
-- used with the default SPeriod value -- used with the default SPeriod value
::= { tn3270eRtCollCtlEntry 4 } ::= { tn3270eRtCollCtlEntry 4 }
tn3270eRtCollCtlThreshHigh OBJECT-TYPE tn3270eRtCollCtlThreshHigh OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
White, Moore TN3270E Response Time Collection MIB 26 January 1998
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtExceeded "The threshold for generating a tn3270eRtExceeded
notification, signalling that a monitored total response notification, signalling that a monitored total response
time has exceeded the specified limit. A value of zero time has exceeded the specified limit. A value of zero
for this object suppresses generation of this notification. for this object suppresses generation of this notification.
The value of this object is used only if the corresponding The value of this object is used only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 0 } -- suppress notifications DEFVAL { 0 } -- suppress notifications
skipping to change at page 31, line 4 skipping to change at page 26, line 58
notification should be generated: notification should be generated:
AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate
This comparison is done only if the corresponding This comparison is done only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 1 } DEFVAL { 1 }
::= { tn3270eRtCollCtlEntry 7 } ::= { tn3270eRtCollCtlEntry 7 }
tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE
White, Moore TN3270E Response Time Collection MIB 26 January 1998
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object defines the range of transaction "The value of this object defines the range of transaction
response times counted in the Tn3270eRtDataBucket1Rts response times counted in the Tn3270eRtDataBucket1Rts
object: those less than or equal to this value." object: those less than or equal to this value."
DEFVAL { 10 } DEFVAL { 10 }
::= { tn3270eRtCollCtlEntry 8 } ::= { tn3270eRtCollCtlEntry 8 }
skipping to change at page 32, line 4 skipping to change at page 27, line 51
DEFVAL { 50 } DEFVAL { 50 }
::= { tn3270eRtCollCtlEntry 10 } ::= { tn3270eRtCollCtlEntry 10 }
tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object, together with that of the "The value of this object, together with that of the
White, Moore TN3270E Response Time Collection MIB 26 January 1998
tn3270eRtCollCtlBucketBndry3 object, defines the range tn3270eRtCollCtlBucketBndry3 object, defines the range
of transaction response times counted in the of transaction response times counted in the
Tn3270eRtDataBucket4Rts object: those greater than the Tn3270eRtDataBucket4Rts object: those greater than the
value of the tn3270eRtCollCtlBucketBndry3 object, and value of the tn3270eRtCollCtlBucketBndry3 object, and
less than or equal to the value of this object. less than or equal to the value of this object.
The value of this object also defines the range of The value of this object also defines the range of
transaction response times counted in the transaction response times counted in the
Tn3270eRtDataBucket5Rts object: those greater than the Tn3270eRtDataBucket5Rts object: those greater than the
value of this object." value of this object."
skipping to change at page 33, line 4 skipping to change at page 28, line 43
tn3270eRtDataEntry OBJECT-TYPE tn3270eRtDataEntry OBJECT-TYPE
SYNTAX Tn3270eRtDataEntry SYNTAX Tn3270eRtDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created based upon the "An entry in this table is created based upon the
tn3270eRtCollCtlTable. A single entry is created with tn3270eRtCollCtlTable. A single entry is created with
a tn3270eRtDataClientAddrType of unknown(0) and a a tn3270eRtDataClientAddrType of unknown(0) and a
zero-length octet string value for zero-length octet string value for
tn3270eRtDataClientAddress when the corresponding tn3270eRtDataClientAddress when the corresponding
White, Moore TN3270E Response Time Collection MIB 26 January 1998
tn3270eRtCollCtlType has aggregate(0) specified. tn3270eRtCollCtlType has aggregate(0) specified.
When aggregate(0) is not specified, then a separate When aggregate(0) is not specified, then a separate
entry is created for each client. entry is created for each client in the group.
Note that the following objects defined within an Note that the following objects defined within an
entry in this table can wrap: entry in this table can wrap:
tn3270eRtDataTotalRts tn3270eRtDataTotalRts
tn3270eRtDataTotalIpRts tn3270eRtDataTotalIpRts
tn3270eRtDataCountTrans tn3270eRtDataCountTrans
tn3270eRtDataCountDrs tn3270eRtDataCountDrs
tn3270eRtDataElapsRnTrpSq tn3270eRtDataElapsRnTrpSq
tn3270eRtDataElapsIpRtSq tn3270eRtDataElapsIpRtSq
tn3270eRtDataBucket1Rts tn3270eRtDataBucket1Rts
skipping to change at page 34, line 4 skipping to change at page 29, line 37
tn3270eRtDataBucket1Rts Counter32, tn3270eRtDataBucket1Rts Counter32,
tn3270eRtDataBucket2Rts Counter32, tn3270eRtDataBucket2Rts Counter32,
tn3270eRtDataBucket3Rts Counter32, tn3270eRtDataBucket3Rts Counter32,
tn3270eRtDataBucket4Rts Counter32, tn3270eRtDataBucket4Rts Counter32,
tn3270eRtDataBucket5Rts Counter32, tn3270eRtDataBucket5Rts Counter32,
tn3270eRtDataRtMethod INTEGER tn3270eRtDataRtMethod INTEGER
} }
tn3270eRtDataClientAddrType OBJECT-TYPE tn3270eRtDataClientAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX Tn3270eAddrType
White, Moore TN3270E Response Time Collection MIB 26 January 1998
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of address represented by "Indicates the type of address represented by
the value of tn3270eRtDataClientAddress." the value of tn3270eRtDataClientAddress."
::= { tn3270eRtDataEntry 1 } ::= { tn3270eRtDataEntry 1 }
tn3270eRtDataClientAddress OBJECT-TYPE tn3270eRtDataClientAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 35, line 4 skipping to change at page 30, line 30
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 4 } ::= { tn3270eRtDataEntry 4 }
tn3270eRtDataAvgIpRt OBJECT-TYPE tn3270eRtDataAvgIpRt OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average IP response time measured over the last "The average IP response time measured over the last
White, Moore TN3270E Response Time Collection MIB 26 January 1998
collection interval." collection interval."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 5 } ::= { tn3270eRtDataEntry 5 }
tn3270eRtDataAvgCountTrans OBJECT-TYPE tn3270eRtDataAvgCountTrans OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "transactions" UNITS "transactions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sliding transaction count used for calculating the "The sliding transaction count used for calculating the
values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt
objects. The actual transaction count is available in objects. The actual transaction count is available in
the tn3270eRtDataCountTrans object." the tn3270eRtDataCountTrans object.
The initial value of this object, before any averages have
been calculated, is 0."
::= { tn3270eRtDataEntry 6 } ::= { tn3270eRtDataEntry 6 }
tn3270eRtDataIntTimeStamp OBJECT-TYPE tn3270eRtDataIntTimeStamp OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The date and time of the last interval that "The date and time of the last interval that
tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and
tn3270eRtDataAvgCountTrans were calculated." tn3270eRtDataAvgCountTrans were calculated.
Prior to the calculation of the first interval
averages, this object returns the value
0x0000000000000000000000. When this value is
returned, the remaining objects in the entry have
no significance."
::= { tn3270eRtDataEntry 7 } ::= { tn3270eRtDataEntry 7 }
tn3270eRtDataTotalRts OBJECT-TYPE tn3270eRtDataTotalRts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the total response times collected." "The count of the total response times collected.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 8 } ::= { tn3270eRtDataEntry 8 }
tn3270eRtDataTotalIpRts OBJECT-TYPE tn3270eRtDataTotalIpRts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the total IP-network response times "The count of the total IP-network response times
collected." collected.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 9 } ::= { tn3270eRtDataEntry 9 }
tn3270eRtDataCountTrans OBJECT-TYPE tn3270eRtDataCountTrans OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "transactions" UNITS "transactions"
White, Moore TN3270E Response Time Collection MIB 26 January 1998
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the total number of transactions detected." "The count of the total number of transactions detected.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 10 } ::= { tn3270eRtDataEntry 10 }
tn3270eRtDataCountDrs OBJECT-TYPE tn3270eRtDataCountDrs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "transactions" UNITS "definite responses"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the total number of definite responses "The count of the total number of definite responses
detected." detected.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 11 } ::= { tn3270eRtDataEntry 11 }
tn3270eRtDataElapsRndTrpSq OBJECT-TYPE tn3270eRtDataElapsRndTrpSq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of seconds squared" UNITS "tenths of seconds squared"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the elapsed round trip time squared. The sum "The sum of the elapsed round trip time squared. The sum
of the squares is keep in order to enable calculation of of the squares is keep in order to enable calculation of
skipping to change at page 36, line 52 skipping to change at page 32, line 39
The sum of the squares is keep in order to enable The sum of the squares is keep in order to enable
calculation of a variance." calculation of a variance."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 13 } ::= { tn3270eRtDataEntry 13 }
tn3270eRtDataBucket1Rts OBJECT-TYPE tn3270eRtDataBucket1Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 1." "The count of the response times falling into bucket 1.
::= { tn3270eRtDataEntry 14 }
White, Moore TN3270E Response Time Collection MIB 26 January 1998 A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 14 }
tn3270eRtDataBucket2Rts OBJECT-TYPE tn3270eRtDataBucket2Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 2." "The count of the response times falling into bucket 2.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 15 } ::= { tn3270eRtDataEntry 15 }
tn3270eRtDataBucket3Rts OBJECT-TYPE tn3270eRtDataBucket3Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 3." "The count of the response times falling into bucket 3.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 16 } ::= { tn3270eRtDataEntry 16 }
tn3270eRtDataBucket4Rts OBJECT-TYPE tn3270eRtDataBucket4Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 4." "The count of the response times falling into bucket 4.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 17 } ::= { tn3270eRtDataEntry 17 }
tn3270eRtDataBucket5Rts OBJECT-TYPE tn3270eRtDataBucket5Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 5." "The count of the response times falling into bucket 5.
A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime
object."
::= { tn3270eRtDataEntry 18 } ::= { tn3270eRtDataEntry 18 }
tn3270eRtDataRtMethod OBJECT-TYPE tn3270eRtDataRtMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(0),
responses(1), responses(1),
timemark(2) timemark(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates the method that was "The value of this object indicates the method that was
used in calculating the IP network time." used in calculating the IP network time.
The value 'none(0) indicates that response times were not
calculated for the IP network."
::= { tn3270eRtDataEntry 19 } ::= { tn3270eRtDataEntry 19 }
tn3270eRtSpinLock OBJECT-TYPE tn3270eRtSpinLock OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
White, Moore TN3270E Response Time Collection MIB 26 January 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An advisory lock used to allow cooperating TN3270E-RT-MIB "An advisory lock used to allow cooperating TN3270E-RT-MIB
applications to coordinate their use of the applications to coordinate their use of the
tn3270eRtCollCtlTable. tn3270eRtCollCtlTable.
When creating an new entry or altering an existing entry When creating a new entry or altering an existing entry
in the tn3270eRtCollCtlTable, it may be necessary for in the tn3270eRtCollCtlTable, an application should make
applications to make use of tn3270eRtSpinLock to serialize use of tn3270eRtSpinLock to serialize application changes
application changes or additions. or additions.
Since this is an advisory lock, the use of this lock is Since this is an advisory lock, the use of this lock is
not enforced." not enforced."
::= { tn3270eRtObjects 3 } ::= { tn3270eRtObjects 3 }
-- Notifications -- Notifications
tn3270eRtExceeded NOTIFICATION-TYPE tn3270eRtExceeded NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
skipping to change at page 39, line 4 skipping to change at page 34, line 50
::= { tn3270eRtNotifications 1 } ::= { tn3270eRtNotifications 1 }
tn3270eRtOkay NOTIFICATION-TYPE tn3270eRtOkay NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans, tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod tn3270eRtDataRtMethod
} }
White, Moore TN3270E Response Time Collection MIB 26 January 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the average response "This notification is generated when the average response
time, tn3270eRtDataAvgRt, falls below time, tn3270eRtDataAvgRt, falls below
tn3270eRtCollCtlThresholdLow at the end of a collection tn3270eRtCollCtlThresholdLow at the end of a collection
interval specified by tn3270eCollCtlSPeriod times interval specified by tn3270eCollCtlSPeriod times
tn3270eCollCtlSPMult, after a tn3270eRtExceeded tn3270eCollCtlSPMult, after a tn3270eRtExceeded
notification was generated. Note that the corresponding notification was generated. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3) tn3270eCollCtlType must have traps(5) and average(3)
set for this notification to be generated." set for this notification to be generated."
skipping to change at page 39, line 32 skipping to change at page 35, line 20
tn3270eResMapElementType -- type of resource tn3270eResMapElementType -- type of resource
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when response time data "This notification is generated when response time data
collection is enabled for a member of a client group. collection is enabled for a member of a client group.
In order for this notification to occur the corresponding In order for this notification to occur the corresponding
tn3270eRtCollCtlType must have traps(5) selected. tn3270eRtCollCtlType must have traps(5) selected.
tn3270eResMapElementType contains a valid value only if tn3270eResMapElementType contains a valid value only if
tn3270eRtDataClientAddress contains a valid IP address tn3270eRtDataClientAddress contains a valid address
(rather than a zero-length octet string)." (rather than a zero-length octet string)."
::= { tn3270eRtNotifications 3 } ::= { tn3270eRtNotifications 3 }
tn3270eRtCollEnd NOTIFICATION-TYPE tn3270eRtCollEnd NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eRtDataDiscontinuityTime, tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans, tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
skipping to change at page 40, line 4 skipping to change at page 35, line 43
tn3270eRtDataCountTrans, tn3270eRtDataCountTrans,
tn3270eRtDataCountDrs, tn3270eRtDataCountDrs,
tn3270eRtDataElapsRndTrpSq, tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq, tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1Rts, tn3270eRtDataBucket1Rts,
tn3270eRtDataBucket2Rts, tn3270eRtDataBucket2Rts,
tn3270eRtDataBucket3Rts, tn3270eRtDataBucket3Rts,
tn3270eRtDataBucket4Rts, tn3270eRtDataBucket4Rts,
tn3270eRtDataBucket5Rts, tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod tn3270eRtDataRtMethod
White, Moore TN3270E Response Time Collection MIB 26 January 1998
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when an tn3270eRtDataEntry "This notification is generated when an tn3270eRtDataEntry
is deleted after being active (actual data collected), in is deleted after being active (actual data collected), in
order to enable a management application monitoring an order to enable a management application monitoring an
tn3270eRtDataEntry to get the entry's final values. Note tn3270eRtDataEntry to get the entry's final values. Note
that the corresponding tn3270eCollCtlType must have traps(5) that the corresponding tn3270eCollCtlType must have traps(5)
set for this notification to be generated." set for this notification to be generated."
::= { tn3270eRtNotifications 4 } ::= { tn3270eRtNotifications 4 }
skipping to change at page 41, line 4 skipping to change at page 36, line 36
OBJECT tn3270eRtCollCtlSPMult OBJECT tn3270eRtCollCtlSPMult
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlThreshHigh OBJECT tn3270eRtCollCtlThreshHigh
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
White, Moore TN3270E Response Time Collection MIB 26 January 1998
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlThreshLow OBJECT tn3270eRtCollCtlThreshLow
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlIdleRate OBJECT tn3270eRtCollCtlIdleRate
skipping to change at page 42, line 5 skipping to change at page 37, line 30
OBJECT tn3270eRtCollCtlRowStatus OBJECT tn3270eRtCollCtlRowStatus
SYNTAX INTEGER { SYNTAX INTEGER {
active(1) -- subset of RowStatus active(1) -- subset of RowStatus
} }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one of the six "Write access is not required, and only one of the six
enumerated values for the RowStatus textual convention enumerated values for the RowStatus textual convention
need be supported, specifically: active(1)." need be supported, specifically: active(1)."
White, Moore TN3270E Response Time Collection MIB 26 January 1998
OBJECT tn3270eRtSpinLock
MIN-ACCESS not-accessible
DESCRIPTION
"The agent is not required to support this object,
since it provides an advisory spin lock capability."
::= {tn3270eRtCompliances 1 } ::= {tn3270eRtCompliances 1 }
-- Group definitions -- Group definitions
tn3270eRtGroup OBJECT-GROUP tn3270eRtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eRtCollCtlType, tn3270eRtCollCtlType,
tn3270eRtCollCtlSPeriod, tn3270eRtCollCtlSPeriod,
tn3270eRtCollCtlSPMult, tn3270eRtCollCtlSPMult,
tn3270eRtCollCtlThreshHigh, tn3270eRtCollCtlThreshHigh,
skipping to change at page 43, line 4 skipping to change at page 38, line 17
tn3270eRtDataBucket5Rts, tn3270eRtDataBucket5Rts,
tn3270eRtDataRtMethod, tn3270eRtDataRtMethod,
tn3270eRtSpinLock } tn3270eRtSpinLock }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for all implementations that "This group is mandatory for all implementations that
support the TN3270E-RT-MIB. " support the TN3270E-RT-MIB. "
::= { tn3270eRtGroups 1 } ::= { tn3270eRtGroups 1 }
tn3270eRtNotGroup NOTIFICATION-GROUP tn3270eRtNotGroup NOTIFICATION-GROUP
White, Moore TN3270E Response Time Collection MIB 26 January 1998
NOTIFICATIONS { NOTIFICATIONS {
tn3270eRtExceeded, tn3270eRtExceeded,
tn3270eRtOkay, tn3270eRtOkay,
tn3270eRtCollStart, tn3270eRtCollStart,
tn3270eRtCollEnd tn3270eRtCollEnd
} }
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. 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 information
SHOULD be employed in such environments. The method for this SHOULD be employed in such environments. An authentication protocol is
authentication is a function of the SNMP Administrative Framework, and defined in [10]. A protocol for access control is defined in [11].
has not been expanded by this MIB.
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 creation. Allowing this support in a non-secure environment can have a
a negative effect on network operations. It is RECOMMENDED that 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 creation
SHOULD be allowed without providing, at a minimum, authentication of SHOULD be allowed without providing, at a minimum, authentication of
request origin. It is RECOMMENDED that without such support that the request origin. It is RECOMMENDED that without such support that the
following objects be implemented as read-only: 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 tn3270eRtCollCtlIdleRate 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 tn3270eRtCollCtlTable when SET support is not allowed is outside of the
the scope of this memo. scope of this memo.
White, Moore TN3270E Response Time Collection MIB 26 January 1998
7. 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 pertain
to the implementation or use of the technology described in this to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards- procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards-related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses claims of rights made available for publication and any assurances of
to be made available, or the result of an attempt made to obtain a licenses to be made available, or the result of an attempt made to
general license or permission for the use of such proprietary rights obtain a general license or permission for the use of such proprietary
by implementers or users of this specification can be obtained from rights by implementers or users of this specification can be obtained
the IETF Secretariat. 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 copyrights, patents or patent applications, or other proprietary rights
rights which may cover technology that may be required to practice which may cover technology that may be required to practice this
this standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. Director.
8. Acknowledgments 8.0 Acknowledgments
This document is a product of the TN3270E Working Group. Special This document is a product of the TN3270E Working Group. Special thanks
thanks is due to Derek Bolton and Michael Boe of Cisco Systems for are due to Derek Bolton and Michael Boe of Cisco Systems for their
their numerous comments and suggestions for improving the structure of numerous comments and suggestions for improving the structure of this
this MIB. MIB. Thanks also to Randy Presuhn of BMC Software for his valuable
review comments on several versions of the document.
9. References 9.0 References
[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure
of Management Information for Version 2 of the Simple Network of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, January 1996. Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual
854, May 1983. Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, January 1996.
[3] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
May 1983. "Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996.
White, Moore TN3270E Response Time Collection MIB 26 January 1998 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, BMC Software, Inc., IBM T.J. Watson Research, January
1998.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and
Mappings for Version 2 of the Simple Network Management Protocol Dispatching for the Simple Network Management Protocol (SNMP)", RFC
(SNMPv2)", RFC 1906, January 1996. 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson
Research, January 1998.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273,
Conventions for Version 2 of the Simple Network Management Protocol SNMP Research, Inc., Secure Computing Corporation, Cisco Systems,
(SNMPv2)", RFC 1903, January 1996. January 1998.
[7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for
Operations for Version 2 of the Simple Network Management Protocol version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
(SNMPv2)", RFC 1905, January 1996. 2274, IBM T. J. Watson Research, January 1998.
[8] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control
"Conformance Statements for Version 2 of the Simple Network Model (VACM) for the Simple Network Management Protocol (SNMP)",
Management Protocol (SNMPv2)", RFC 1904, January 1996. RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco
Systems, Inc., January 1998.
[9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management [12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
Information Base for Version 2 of the Simple Network Management 854, May 1983.
Protocol (SNMPv2)", RFC 1907, January 1996.
[10] White, K., "Base Definitions of Managed Objects for TN3270E Using [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
SMIv2", Internet-Draft Work in progress, January 1998. May 1983.
[11] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
[12] IBM, International Technical Support Centers, "Response Time Data [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994.
Gathering", GG24-3212-01, November 1990.
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement [16] White, K. and Moore, R., "Base Definitions of Managed Objects for
Levels", BCP 14, RFC 2119, March 1997. TN3270E Using SMIv2", Internet-Draft Work in progress, April 1998.
[14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [17] IBM, International Technical Support Centers, "Response Time Data
"Coexistence between Version 1 and Version 2 of the Internet- Gathering", GG24-3212-01, November 1990.
standard Network Management Framework", RFC 1908, January 1996.
10. Authors' Addresses [18] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF
Standards Process", BCP 11, RFC 2028, October 1996.
Kenneth D. White [19] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
White, Moore TN3270E Response Time Collection MIB 26 January 1998 10.0 Authors' Addresses
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-0102
E-mail: kennethw@vnet.ibm.com E-mail: kennethw@vnet.ibm.com
Robert Moore Robert Moore
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 Phone: +1-919-254-7507
E-mail: remoore@us.ibm.com E-mail: remoore@us.ibm.com
11. Full Copyright Statement 11.0 Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved. Copyright (C) The Internet Society (1997). 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 others, and derivative works that comment on or otherwise explain it or
or assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are included
included on all such copies and derivative works. However, this on all such copies and derivative works. However, this document itself
document itself may not be modified in any way, such as by removing may not be modified in any way, such as by removing the copyright notice
the copyright notice or references to the Internet Society or other or references to the Internet Society or other Internet organizations,
Internet organizations, except as needed for the purpose of developing except as needed for the purpose of developing Internet standards in
Internet standards in which case the procedures for copyrights defined which case the procedures for copyrights defined in the Internet
in the Internet Standards process must be followed, or as required to Standards process must be followed, or as required to translate it into
translate it into languages other than English. 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 This document and the information contained herein is provided on an "AS
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 224 change blocks. 
769 lines changed or deleted 735 lines changed or added

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