draft-ietf-tn3270e-rt-mib-01.txt   draft-ietf-tn3270e-rt-mib-02.txt 
TN3270E Working Group TN3270E Working Group
INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-01.txt> Kenneth White INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-02.txt> Kenneth White
Expiration Date: September 1998 Robert Moore Expiration Date: May 1998 Robert Moore
IBM Corp. IBM Corp.
September 1997 November 1997
Definitions of Managed Objects for TN3270E Definitions of Managed Objects for TN3270E
Response Time Collection Using SMIv2 Response Time Collection Using SMIv2
(TN3270E-RT-MIB) (TN3270E-RT-MIB)
<draft-ietf-tn3270e-rt-mib-01.txt> <draft-ietf-tn3270e-rt-mib-02.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 its Working Groups. Note that other groups may also distribute and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts. working 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. Internet Drafts may be updated, replaced, or obsoleted by months. Internet Drafts may be updated, replaced, or obsoleted by
skipping to change at line 43 skipping to change at line 43
The purpose of this memo is to define the protocol and the Management The purpose of this memo is to define the protocol and the Management
Information Base (MIB) for performing response time data collection Information Base (MIB) for performing response time data collection
on TN3270 and TN3270E on TN3270 and TN3270E
sessions by a TN3270E Server. The response time data sessions by a TN3270E Server. The response time data
collected by a TN3270E Server is structured to support both validation collected by a TN3270E Server is structured to support both validation
of service level agreements and performance monitoring of of service level agreements and performance monitoring of
TN3270 and TN3270E TN3270 and TN3270E
Sessions. This MIB has as a prerequisite the TN3270E-MIB Sessions. This MIB has as a prerequisite the TN3270E-MIB
reference [10]. reference [10].
Expires March 1998 [Page 1]~ Expires May 1998 [Page 1]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
Table of Contents Table of Contents
1.0 Introduction............................................. 2 1.0 Introduction............................................. 2
2.0 The SNMPv2 Network Management Framework.................. 2 2.0 The SNMPv2 Network Management Framework.................. 2
2.1 Object Definitions....................................... 3 2.1 Object Definitions....................................... 3
3.0 Response Time Collection Methodology..................... 3 3.0 Response Time Collection Methodology..................... 3
3.1 General Response Time Collection......................... 4 3.1 General Response Time Collection......................... 4
3.2 TN3270E Server Response Time Collection.................. 5 3.2 TN3270E Server Response Time Collection.................. 5
3.3 Correlating TN3270E Server and Host Response Times....... 9 3.3 Correlating TN3270E Server and Host Response Times....... 9
3.4 Timestamp Calculation....................................10 3.4 Timestamp Calculation....................................10
3.4.1 DR Usage...............................................11 3.4.1 DR Usage...............................................11
3.4.2 TIMEMARK Usage.........................................13 3.4.2 TIMEMARK Usage.........................................13
3.5 Performance Data Modelling...............................14 3.5 Performance Data Modelling...............................15
3.5.1 Averaging Response Times...............................15 3.5.1 Averaging Response Times...............................15
3.5.2 Response Time Buckets..................................17 3.5.2 Response Time Buckets..................................17
4.0 Structure of the MIB.....................................18 4.0 Structure of the MIB.....................................18
4.1 tn3270eRtCollCtlTable....................................18 4.1 tn3270eRtCollCtlTable....................................18
4.2 tn3270eRtDataTable.......................................21 4.2 tn3270eRtDataTable.......................................21
4.3 Notifications............................................23 4.3 Notifications............................................23
5.0 Definitions..............................................24 5.0 Definitions..............................................24
6.0 Security Considerations..................................39 6.0 Security Considerations..................................40
7.0 Acknowledgments..........................................40 7.0 Acknowledgments..........................................41
8.0 References...............................................40 8.0 References...............................................41
9.0 Authors' Addresses.......................................42 9.0 Authors' Addresses.......................................42
1. Introduction 1. Introduction
This document is a product of the TN3270E Working Group. Its purpose This document is a product of the TN3270E Working Group. Its purpose
is to define a protocol and a MIB module to enable a TN3270E server to is to define a protocol and a MIB module to enable a TN3270E server to
collect response time data for both TN3270 and TN3270E clients. collect response time data for both TN3270 and TN3270E clients.
Prerequisites for implementing this MIB are: Prerequisites for implementing this MIB are:
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E
skipping to change at line 92 skipping to change at line 92
o TN3270E RFCs o TN3270E RFCs
o SYSAPPL-MIB, import Utf8String Textual Convention for o SYSAPPL-MIB, import Utf8String Textual Convention for
international text string support, reference [13]. international text string support, reference [13].
2. The SNMPv2 Network Management Framework 2. The SNMPv2 Network Management Framework
The SNMP Network Management Framework presently consists of three The SNMP Network Management Framework presently consists of three
major components. They are: major components. They are:
Expires March 1998 [Page 2]~ Expires May 1998 [Page 2]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
o the SMI, described in RFC 1902 [1], - the mechanisms used for o the SMI, described in RFC 1902 [1], - the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed
objects for the Internet suite of protocols. objects for the Internet suite of protocols.
o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol
for accessing managed information. for accessing managed information.
skipping to change at line 140 skipping to change at line 140
specific instantiation of the object. For human convenience, we often specific instantiation of the object. For human convenience, we often
use a textual string, termed the descriptor, to refer to the object use a textual string, termed the descriptor, to refer to the object
type. type.
3. Response Time Collection Methodology 3. 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.
Expires March 1998 [Page 3]~ Expires May 1998 [Page 3]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
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 SNA Management Services (SNA/MS) Response Time o The SNA Management Services (SNA/MS) Response Time
Monitoring (RTM) function Monitoring (RTM) function
o Timestamping using definite response flows. o Timestamping using definite response flows.
skipping to change at line 193 skipping to change at line 193
| reply(DR) B | | | reply(DR) B | |
| <---------------------------------------< | | <---------------------------------------< |
| | +/-RSP C | | | +/-RSP C |
| >---------------------------------------> | | >---------------------------------------> |
| | | |
| DR: Definite Response requested | | DR: Definite Response requested |
| DR +/-: Definite Response | | DR +/-: Definite Response |
| | | |
------------------------------------------------ ------------------------------------------------
Expires March 1998 [Page 4]~ Expires May 1998 [Page 4]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
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 the purpose of calculating an approximation for network transit for the purpose of calculating an approximation for network transit
time, is doesn't matter if the response is positive or negative. Two time, is doesn't matter if the response is positive or negative. Two
response time values are typically calculated: response time values are typically calculated:
o Host Transit Time: Timestamp B - A o Host Transit Time: Timestamp B - A
skipping to change at line 218 skipping to change at line 218
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 - B, is the amount of transaction. Network transit time, timestamp C - B, is the amount of
time that the definite response request and its response required. time that the definite response request and its response required.
Host time, timestamp B - A, is the actual time that the host required Host time, timestamp B - A, is the actual time that the host required
to process the transaction. Experience has shown that using the to process the transaction. Experience has shown that using the
response flow to approximate network transit times is useful, and does response flow to approximate network transit times is useful, and does
correlate well with actual network transit times. correlate well with actual network transit times.
A client should respond to a definite response request when it
completes processing the transaction. This is important since it
increases the accuracy of a total response time. Clients that
immediately respond to a definite response request will end up 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 SNA/MS RTM collection. The tn3270eTcpConnResourceType object in from SNA/MS RTM collection. The tn3270eTcpConnResourceType object in
a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to
determine if a client session is ineligible for response time data determine if a client session is ineligible for response time data
collection. collection.
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 an IP client performing 3270 emulation to a
target SNA host over both an IP network (IP client to TN3270E server) target SNA host over both an IP network (IP client to TN3270E server)
and an SNA Network (TN3270E server to target SNA host). A TN3270E and an SNA Network (TN3270E server to target SNA host). A TN3270E
server can use SNA definite responses and the TN3270 Enhancement (RFC server can use SNA definite responses and the TN3270 Enhancement (RFC
1647 [11]) RESPONSES function to calculate response times for a 1647 [11]) RESPONSES function to calculate response times for a
transaction, by timestamping when a client sends a request, when the transaction, by timestamping when a client sends a request, when the
reply arrives from the target host, and when the response reply arrives from the target host, and when the response
Expires May 1998 [Page 5]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
acknowledging this reply arrives from the client. 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 information TN3270E server takes its timestamps. In addition, there is information
on how the TN3270 TIMEMARK request/response flow can be used instead on how the TN3270 TIMEMARK request/response flow can be used instead
Expires March 1998 [Page 5]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
of DR for approximating IP network transit times. of DR for approximating IP network transit times.
The following figure adds a TN3270E server between the client, in this The following figure adds a TN3270E server between the client, in 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 line 290 skipping to change at line 296
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 transaction specifies DR, and that the TN3270E RESPONSES function the transaction specifies DR, and that the TN3270E RESPONSES function
has been negotiated between itself and the client. Negotiation of the has 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 can be configured during startup to support it. or can be configured during startup to support it.
Expires May 1998 [Page 6]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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: F - D o Total Response time: F - D
o IP Network Transit Time: F - E o IP Network Transit Time: F - E
Expires March 1998 [Page 6]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
The MIB provides an object, tn3270eRtCollCtlType, to control several The MIB provides an object, tn3270eRtCollCtlType, to control several
aspects of response time data collection. One of the available aspects of response time data collection. One of the available
options in setting up a response time collection policy is to options in setting up a response time collection policy is to
eliminate the IP-network component altogether. This might be done eliminate the IP-network component altogether. This might be done
because it is determined either that the additional IP network traffic because it is determined either that the additional IP network traffic
would not be desirable, or that the IP-network components of the would not be desirable, or that the IP-network components of the
overall response times are not significant. overall response times are 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
skipping to change at line 342 skipping to change at line 348
marks the end of a transaction's total response time, equal marks the end of a transaction's total response time, equal
to timestamp E, the end of the transaction's SNA-network to timestamp E, the end of the transaction's SNA-network
component. 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
Expires May 1998 [Page 7]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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
Expires March 1998 [Page 7]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
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 introduced into the IP network for response time data collection. A
DYNAMIC definite response is one that the TN3270E server itself adds DYNAMIC definite response is one that the TN3270E server itself adds
to a reply, in a transaction for which the SNA application at the to a reply, in a transaction for which the SNA application at the
target SNA host did not specify DR in its reply. When the +/-RSP target SNA host did not specify DR in its reply. When the +/-RSP
comes back from the client, the server uses this response to calculate comes back from the client, the server uses this response to calculate
timestamp F, but then it does not forward it on to the SNA application timestamp F, but then it does not forward it on to the SNA application
(since the application is not expecting a response to its reply). (since the application is not expecting a response to its reply).
skipping to change at line 395 skipping to change at line 401
having dynamic definite responses enabled for a having dynamic definite responses enabled for a
collection results in the inclusion of additional collection results in the inclusion of additional
transactions in the aggregate: specifically, those transactions in the aggregate: specifically, those
for which the host SNA application did not specify for which the host SNA application did not specify
DR in its reply. DR in its reply.
A TN3270E server also has the option of substituting TIMEMARK A TN3270E server also has the option of substituting TIMEMARK
processing for definite responses in calculating the IP-network processing for definite responses in calculating the IP-network
component of a transaction's response time. Once again, there is no component of a transaction's response time. Once again, there is no
reason for the server to do this if the collection has been set up to reason for the server to do this if the collection has been set up to
Expires May 1998 [Page 8]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
exclude the IP-network component altogether in computing response exclude the IP-network component altogether in computing response
times. times.
The MIB is structured to keep for each response time the total time (F The MIB is structured to keep for each response time the total time (F
- D) and the IP-network component (F - E). A management application - D) and the IP-network component (F - E). A management application
can obviously calculate from these two values a response time's SNA- can obviously calculate from these two values a response time's SNA-
Expires March 1998 [Page 8]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
network component (E - D). The SNA-network component would also network component (E - D). The SNA-network component would also
contain the host processing time at both the TN3270E Server and at the contain the host processing time at both the TN3270E Server and at the
target application. As in the IP case, these response times are only target application. As in the IP case, these response times are only
approximations, because the +/-RSP's crossing of the IP network is approximations, because the +/-RSP's crossing of the IP network is
substituted for that of the request that started the transaction. substituted for that of the request that started the transaction.
When a TN3270E server is in the same SNA host as the target When a 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 time will approximately equal the host transit time (B - A) response time will approximately equal the host transit time (B - A)
described previously. A host (as opposed to a gateway) TN3270E server described previously. A host (as opposed to a gateway) TN3270E server
skipping to change at line 448 skipping to change at line 454
| ------------------------------------------> | | ------------------------------------------> |
| reply(DR) E B | | | reply(DR) E B | |
| <----------------------------------------< | | <----------------------------------------< |
| | +/-RSP F C | | | +/-RSP F C |
| >--------------------------------------> | | >--------------------------------------> |
| | | |
------------------------------------------------ ------------------------------------------------
The following response times are available: The following response times are available:
Expires May 1998 [Page 9]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
o Target SNA host transit time: B - A o Target SNA host transit time: B - A
o Target SNA host (total) network transit time: C - B o Target SNA host (total) network transit time: C - B
o TN3270E server total response time: F - D o TN3270E server total response time: F - D
o TN3270E server IP-network component: F - E o TN3270E server IP-network component: F - E
Expires March 1998 [Page 9]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
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. The IP-network component can be subtracted from the total time. The IP-network component can be subtracted from the total
network transit time determined by monitoring the SLU to see the network transit time determined by monitoring the SLU to see the
actual SNA versus IP network transit times. actual SNA versus IP network transit times.
The MIB defined by this memo does not specifically address correlation The MIB defined by this memo does not specifically address 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,
skipping to change at line 492 skipping to change at line 498
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 is provided on how the TN3270 TIMEMARK request/response information is provided on how the TN3270 TIMEMARK request/response
flow can be used in place of DR for approximating IP network transit flow can be used in place of DR for approximating IP network transit
times. times.
Expires March 1998 [Page 10]~ Expires May 1998 [Page 10]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
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 |
skipping to change at line 545 skipping to change at line 551
last in chain (LIC). Timestamp E should be taken prior to sending the 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 RESPONSES request to the client; normally this is done when the server
receives the LIC RU. Timestamp F is taken when the RESPONSES response receives the LIC RU. Timestamp F is taken when the RESPONSES response
is received from the client. 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 a transaction; it may, for example, require more data from the in a transaction; it may, for example, require more data from the
client before it can formulate a reply. In this case the application client before it can formulate a reply. In this case the application
may simply return to the TN3270E server a change of direction may simply return to the TN3270E server a change of direction
Expires March 1998 [Page 11]~ Expires May 1998 [Page 11]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
indicator. A TCP connection is full duplex: data can be received and indicator. A TCP connection is full duplex: data can be received and
sent on it at the same time. An SNA session, on the other hand, is sent on it at the same time. An SNA session, on the other hand, is
half duplex, with a change of direction indicator to alter the half duplex, with a change of direction indicator to alter the
direction of data flow. Timestamps E and F require a reply to flow to direction of data flow. Timestamps E and F require a reply to flow to
the client. A best-effort approach should be followed by a TN3270E the client. A best-effort approach should be followed by a TN3270E
server when it attempts to calculate timestamps. For cases where the server when it attempts to calculate timestamps. For cases where the
target SNA application sends a change of direction indicator rather target SNA application sends a change of direction indicator rather
than a reply, it is suggested that the entire transaction be omitted than a reply, it is suggested that the entire transaction be omitted
from any response time calculations. from any response time calculations.
skipping to change at line 598 skipping to change at line 604
| <----------------------------------------< | | <----------------------------------------< |
| | +/-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: G - D o Total response time: G - D
Expires March 1998 [Page 12]~ Expires May 1998 [Page 12]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
o IP network transit time: F - E o IP network transit time: F - 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 use
either its response or the earlier one for approximating IP network either its response or the earlier one for approximating IP network
transit time. transit 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
skipping to change at line 639 skipping to change at line 645
tn3270eSrvrConfActivityTimeout object. tn3270eSrvrConfActivityTimeout object.
If a TN3270E server sends a TIMEMARK request to every client with no If a TN3270E server sends a TIMEMARK request to every client with no
session activity, based solely on the server's TIMEMARK interval, then session activity, based solely on the server's TIMEMARK interval, then
network flooding may result, since a server may be supporting network flooding may result, since a server may be supporting
thousands of client sessions. The use of TIMEMARKs for response time thousands of client sessions. The use of TIMEMARKs for response time
monitoring could help to reduce this network flooding. Suppose a monitoring could help to reduce this network flooding. Suppose a
server sends a TIMEMARK request to a client after a LIC RU has been server sends a TIMEMARK request to a client after a LIC RU has been
received, as a means of approximating IP network transit time: received, as a means of approximating IP network transit time:
Expires March 1998 [Page 13]~ Expires May 1998 [Page 13]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997 White, Moore TN3270E Response Time Collection MIB 19 November 1997
--------------------------------------------------- ---------------------------------------------------
| | | |
| 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 line 683 skipping to change at line 689
A TN3270E server would need to consider its normal TIMEMARK processing A TN3270E server would need to consider its normal TIMEMARK processing
when using TIMEMARKs for this purpose. For example, it must not send a when using TIMEMARKs for this purpose. For example, it must not send a
second TIMEMARK request to a client while waiting for the first to second TIMEMARK request to a client while waiting for the first to
return. Also, if a TIMEMARK flow has just been performed for a client return. Also, if a TIMEMARK flow has just been performed for a client
shortly before the LIC RU arrives, the server might use the interval shortly before the LIC RU arrives, the server might use the interval
from this flow as its approximation for IP network transit time; in from this flow as its approximation for IP network transit time; in
this case the server would have to remember to add the interval from this case the server would have to remember to add the interval from
this TIMEMARK flow (F' - E') to the interval from the transaction (E - this TIMEMARK flow (F' - E') to the interval from the transaction (E -
D) to get its approximation for the transaction's total response time. D) to get its approximation for the transaction's total response time.
The most accurate approach would be to send the TIMEMARK request after
the last RU was sent to the client since the resulting total response
time should include any transaction processing time at the client.
The actually accuracy of the total response time depends on when the
client responds to the TIMEMARK request.
Expires May 1998 [Page 14]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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.
Expires March 1998 [Page 14]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
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 less notification thrashing. Sliding-window average calculation cause less notification thrashing. Sliding-window average calculation
skipping to change at line 734 skipping to change at line 746
- TotalRt (sum of the total response times for all - TotalRt (sum of the total response times for all
transactions in the period) transactions in the period)
- TotalIpRt (sum of the IP network transit times for - TotalIpRt (sum of the IP network transit times for
all transactions in the period; note that if IP all transactions in the period; note that if IP
network transit times are being excluded from the network transit times are being excluded from the
response time collection, this value will always be 0). 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 quantities being counted: of the quantities being counted:
Expires May 1998 [Page 15]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
- AvgTransCount (sliding count of transactions) - AvgTransCount (sliding count of transactions)
- TotalRtSliding (sliding count of total response times) - TotalRtSliding (sliding count of total response times)
- TotalIpRtSliding (sliding count of IP network transit times) - TotalIpRtSliding (sliding count of IP network transit times)
o At the end of each sample period, update the sliding counters: o At the end of each sample period, update the sliding counters:
AvgTransCount = AvgTransCount + T AvgTransCount = AvgTransCount + T
Expires March 1998 [Page 15]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
- (AvgTransCount / SPMult) - (AvgTransCount / SPMult)
TotalRtSliding = TotalRtSliding + TotalRt TotalRtSliding = TotalRtSliding + TotalRt
- (TotalRtSliding / SPMult) - (TotalRtSliding / SPMult)
TotalIpRtSliding = TotalIpRtSliding + TotalIpRt TotalIpRtSliding = TotalIpRtSliding + TotalIpRt
- (TotalIpRtSliding / SPMult) - (TotalIpRtSliding / SPMult)
Then reset T, TotalRt, and TotalIpRt to zero for use during the Then reset T, TotalRt, and TotalIpRt to zero for use during the
next sample period. next sample period.
skipping to change at line 787 skipping to change at line 798
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. After this, no other tn3270eRtExceeded
notifications are generated until an average response time is found to notifications are generated until an average response time is found to
have fallen below the low threshold. 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 a high average response time. Intuitively, the significance of an for 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 we might be inclined to use a rule such as "for the purpose of so we might be inclined to use a rule such as "for the purpose of
Expires May 1998 [Page 16]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
generating tn32709eRtExceeded notifications, ignore average response generating tn32709eRtExceeded 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,
Expires March 1998 [Page 16]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
because these transactions "use up" the sampling time. Yet this case because these transactions "use up" the sampling time. Yet this case
of a few transactions with very poor response times should obviously of a few transactions with very poor response times should obviously
be classified as a problem, not as a statistical anomaly based on too be classified as a problem, not as a statistical anomaly based on too
small a sample. small a sample.
The solution is to make the significance level for a sample a function The solution is to make the significance level for a sample a function
of the average response time. In order to determine at a collection of the average response time. In order to determine at a collection
interval whether to generate a tn3270eRtExceeded notification, a interval whether to generate a tn3270eRtExceeded notification, a
TN3270E server uses the following algorithm: TN3270E server uses the following algorithm:
skipping to change at line 839 skipping to change at line 850
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 times (effectively E - D, because when it is excluding the transit times (effectively E - D, because when it is excluding the
Expires May 1998 [Page 17]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
IP-network component of transactions, a server makes timestamp F IP-network component of transactions, a server makes timestamp F
identical to timestamp E). identical to 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 those resulting in five buckets. The first response time bucket counts those
transactions whose total response times were less than or equal to transactions whose total response times were less than or equal to
Boundary 1, the second bucket counts those whose response times were Boundary 1, the second bucket counts those whose response times were
greater than Boundary 1 but less than or equal to Boundary 2, and so greater than Boundary 1 but less than or equal to Boundary 2, and so
Expires March 1998 [Page 17]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
on. The fifth bucket is unbounded on the top, counting all on. The fifth bucket is unbounded on the top, counting all
transactions whose response times were greater than Boundary 4. transactions 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, 5 seconds, and 10 seconds, respectively. These values are seconds, 5 seconds, and 10 seconds, respectively. These values are
the defaults in the 3174 controller's implementation of the SNA/MS RTM the defaults in the 3174 controller's implementation of the SNA/MS RTM
function, and were thought to be appropriate for this MIB as well. function, and were 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
skipping to change at line 890 skipping to change at line 901
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
4.1. tn3270eRtCollCtlTable 4.1. tn3270eRtCollCtlTable
The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex, imported The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex, imported
from the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. from the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName.
Expires May 1998 [Page 18]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eSrvrConfIndex identifies within a host a particular TN3270E tn3270eSrvrConfIndex identifies within a host a particular TN3270E
server. tn3270eRtCollCtlClientGroupName identifies a collection of IP server. tn3270eRtCollCtlClientGroupName identifies a collection of IP
clients for which response time data is to be collected. The clients for which response time data is to be collected. The
collection itself is defined using the tn3270eClientGroupTable from collection itself is defined using the tn3270eClientGroupTable from
the TN3270E-MIB. The index from the tn3270eClientGroupTable, the TN3270E-MIB. The index from the tn3270eClientGroupTable,
tn3270eClientGroupName, was not used directly, since doing so causes tn3270eClientGroupName, was not used directly, since doing so causes
an inconsistent indexing scheme error in some MIB compilers. To avoid an inconsistent indexing scheme error in some MIB compilers. To avoid
Expires March 1998 [Page 18]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
this error, tn3270eRtCollCtlClientGroupName was defined directly in this error, tn3270eRtCollCtlClientGroupName was defined directly in
the tn3270eRtCollCtlEntry. the tn3270eRtCollCtlEntry.
A tn3270eRtCollCtlEntry contains the following objects: A tn3270eRtCollCtlEntry contains the following objects:
-------------------------------------------------- --------------------------------------------------
1st Index | tn3270eSrvrConfIndex Unsigned32 | 1st Index | tn3270eSrvrConfIndex Unsigned32 |
2nd Index | tn3270eRtCollCtlClientGroupName Utf8String | 2nd Index | tn3270eRtCollCtlClientGroupName Utf8String |
| tn3270eRtCollCtlType BITS | | tn3270eRtCollCtlType BITS |
| tn3270eRtCollCtlSPeriod Unsigned32 | | tn3270eRtCollCtlSPeriod Unsigned32 |
skipping to change at line 943 skipping to change at line 954
aggregated for the whole client group. In this case there will aggregated for the whole client group. In this case there will
be only one row created for the collection in the be only one row created for the collection in the
tn3270eRtDataTable. The first two indexes for this row, tn3270eRtDataTable. The first two indexes for this row,
tn3270eSrvrConfIndex and tn3270eRtCollCtlClientGroupName, will tn3270eSrvrConfIndex and tn3270eRtCollCtlClientGroupName, will
have the same values as the indexes for this row in the have the same values as the indexes for this row in the
tn3270eRtCollCtlTable. The third and fourth indexes for an tn3270eRtCollCtlTable. The third and fourth indexes for an
aggregated tn3270eRtDataEntry have the values 'unknown(0)' aggregated tn3270eRtDataEntry have the values 'unknown(0)'
(for tn3270eRtDataClientAddrType) and a null octet string (for tn3270eRtDataClientAddrType) and a null octet string
(for tn3270eRtDataClientAddress). (for tn3270eRtDataClientAddress).
Expires May 1998 [Page 19]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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 Address, and tn3270eRtDataClientAddrType indicates the type IP Address, and tn3270eRtDataClientAddrType indicates the type
of this address. of this address.
o excludeIpComponent(1) - If this bit is set to 1, then the o excludeIpComponent(1) - If this bit is set to 1, then the
Expires March 1998 [Page 19]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
server should exclude the IP-network component from all the server should exclude the IP-network component from all the
response times for this collection. If the target SNA response times for this collection. If the target SNA
application specifies DR in any of its replies, this DR will application specifies DR in any of its replies, this DR will
still be passed down to the client, and the client's response still be passed down to the client, and the client's response
will still be forwarded to the application. But this response will still be forwarded to the application. But this response
will play no role in the server's response time calculations. 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 only those transactions for which it can include an collection only those transactions for which it can include an
(approximate) IP-network component in the total response time (approximate) IP-network component in the total response time
skipping to change at line 997 skipping to change at line 1007
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 parameters specfied for the group. on the parameters specfied for the group.
If this bit is set to 0, then an average is not calculated. In If this bit is set to 0, then an average is not calculated. In
this case the tn3270eRtExceeded and tn3270eRtOkay notifications this case the tn3270eRtExceeded and tn3270eRtOkay notifications
are not generated, even if the traps(5) bit is set to 1. are not generated, even if the traps(5) bit is set to 1.
Expires May 1998 [Page 20]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
o buckets(4) - If this bit is set to 1, then the server should o buckets(4) - If this bit is set to 1, then the server should
create and increment response time buckets for the collection, create and increment response time buckets for the collection,
based on the parameters specified for the group. based on the parameters specified for the group.
If this bit is set to 0, then response time buckets are not If this bit is set to 0, then response time buckets are not
created. created.
Expires March 1998 [Page 20]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
o traps(5) - If this bit is set to 1, then the server generates o traps(5) - If this bit is set to 1, then the server generates
the notifications defined in this MIB. The tn3270CollStart and the notifications defined in this MIB. The tn3270CollStart and
tn3270CollEnd notifications are always generated when this bit tn3270CollEnd notifications are always generated when this bit
is set to 1; the tn3270eRtExceeded and tn3270eRtOkay is set to 1; the tn3270eRtExceeded and tn3270eRtOkay
notifications are generated only if the average(3) bit is also notifications are generated only if the average(3) bit is also
set to 1. set to 1.
If this bit is set to 0, then none of the notifications defined If this bit is set to 0, then none of the notifications defined
in this MIB are generated by the server. in this MIB are generated by the server.
skipping to change at line 1047 skipping to change at line 1057
4.2. tn3270eRtDataTable 4.2. tn3270eRtDataTable
Either a single entry or multiple entries are created in the Either a single entry or multiple entries are created in the
tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on
whether tn3270eRtCollCtlType in the control entry has aggregate(0) whether tn3270eRtCollCtlType in the control entry has aggregate(0)
selected. The contents of an entry in the tn3270eRtDataTable depend selected. The contents of an entry in the tn3270eRtDataTable depend
on the contents of the corresponding entry in the on the contents of the corresponding entry in the
tn3270eRtCollCtlTable: some objects in the data entry return tn3270eRtCollCtlTable: some objects in the data entry return
meaningful values only when the average(3) option is selected in the meaningful values only when the average(3) option is selected in the
Expires May 1998 [Page 21]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
control entry, while others return meaningful values only when the control entry, while others return meaningful values only when the
buckets(4) option is selected. If both options are selected, then all buckets(4) option is selected. If both options are selected, then all
the objects return meaningful values. When an object is not specified the objects return meaningful values. When an object is not specified
to return a meaningful value, an implementation may return any value to return a meaningful value, an implementation may return any value
in response to a Get operation. 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
Expires March 1998 [Page 21]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
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 tn3270eRtDataAvgTransCount o tn3270eRtDataAvgTransCount
o tn3270eRtDataIntTimeStamp o tn3270eRtDataIntTimeStamp
o tn3270eRtDataTotalRt o tn3270eRtDataTotalRt
o tn3270eRtDataTotalIpRt o tn3270eRtDataTotalIpRt
o tn3270eRtDataTransCount o tn3270eRtDataTransCount
skipping to change at line 1081 skipping to change at line 1091
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 most recent sample for these calculations is returned in the the most recent sample for these calculations is returned in the
tn3270eRtDaraIntTimeStamp object. The next four objects are normal tn3270eRtDaraIntTimeStamp 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 enable variance calculations by a management application. to enable variance calculations by a management application.
o tn3270eRtDataElapsRndTrpSq
o tn3270eRtDataElapsIpRtSq
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 tn3270eRtDataBucket1 o tn3270eRtDataBucket1
o tn3270eRtDataBucket2 o tn3270eRtDataBucket2
o tn3270eRtDataBucket3 o tn3270eRtDataBucket3
o tn3270eRtDataBucket4 o tn3270eRtDataBucket4
o tn3270eRtDataBucket5 o tn3270eRtDataBucket5
A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by
a management application to detect when the values of the counter a management application to detect when the values of the counter
objects in this table may have been reset, or otherwise experienced a objects in this table may have been reset, or otherwise experienced a
discontinuity. A possible cause for such a discontinuity is the discontinuity. A possible cause for such a discontinuity is the
TN3270E server's being stopped or restarted. This object returns a TN3270E server's being stopped or restarted. This object returns a
meaningful value regardless of which collection control options were meaningful value regardless of which collection control options were
selected. selected.
An object, tn3270eRtDataRtMethod, identifies whether the IP Network
Expires May 1998 [Page 22]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
Time was calculated using either the definite response or TIMEMARK
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 null octet string, and tn3270eRtDataClientAddress has the value of a null octet string, and
Expires March 1998 [Page 22]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
its tn3270eRtDataClientAddrType has the value of unknown(0). its tn3270eRtDataClientAddrType has the value of 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.
skipping to change at line 1151 skipping to change at line 1162
average(3) response time data is being collected, then this average(3) response time data is being collected, then this
notification is generated whenever (1) an average response notification is generated whenever (1) an average response
time is first found, on a collection interval boundary, to time is first found, on a collection interval boundary, to
have exceeded the high threshold tn3270eRtCollCtlThreshHigh have exceeded the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group, AND (2) the sample on which the specified for the client group, AND (2) the sample on which the
average is based is determined to have been a significant one, average is based is determined to have been a significant one,
via the significance algorithm described earlier. This via the significance algorithm described earlier. This
notification is not generated again for a tn3270eRtDataEntry notification is not generated again for a tn3270eRtDataEntry
until an average response time falling below the low until an average response time falling below the low
threshold tn3270eRtCollCtlThreshLow specified for the client threshold tn3270eRtCollCtlThreshLow specified for the client
Expires May 1998 [Page 23]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
group has occured for the entry. group has occured for the entry.
o tn3270eRtOkay - The purpose of this notification is to signal o tn3270eRtOkay - The purpose of this notification is to signal
that a previously reported performance problem has been that a previously reported performance problem has been
resolved. If average(3) response time data is being collected, resolved. If average(3) response time data is being collected,
then this notification is generated whenever (1) a then this notification is generated whenever (1) a
tn3270eRtExceeded notification has already been generated, AND tn3270eRtExceeded notification has already been generated, AND
Expires March 1998 [Page 23]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
(2) an average response time is first found, on a collection (2) an average response time is first found, on a collection
interval boundary, to have fallen below the low threshold interval boundary, to have fallen below the low threshold
tn3270eRtCollCtlThreshLow specified for the client group. tn3270eRtCollCtlThreshLow specified for the client group.
This notification is not generated again for a This notification is not generated again for a
tn3270eRtDataEntry until an average response time tn3270eRtDataEntry until an average response time
exceeding the high threshold tn3270eRtCollCtlThreshHigh exceeding the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group has occurred for the entry. 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
skipping to change at line 1199 skipping to change at line 1210
client's TCP connection terminates. The purpose of this client's TCP connection terminates. The purpose of this
notification is to enable a management application to notification is to enable a management application 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.
5. Definitions 5. Definitions
TN3270E-RT-MIB DEFINITIONS ::= BEGIN TN3270E-RT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
-- Some MIB Compilers require BITS to be imported from
-- the SNMPv2-SMI
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Counter32, BITS, Unsigned32, Counter32, Unsigned32, Gauge32
Gauge32
Expires May 1998 [Page 24]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, DateAndTime, TimeStamp RowStatus, DateAndTime, TimeStamp
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,
tn3270eResMapElementName, tn3270eResMapElementType tn3270eResMapElementName, tn3270eResMapElementType
FROM TN3270E-MIB FROM TN3270E-MIB
snanauMIB
Expires March 1998 [Page 24]~ FROM SNA-NAU-MIB
White, Moore TN3270E Response Time Collection MIB 29 September 1997
Utf8String Utf8String
FROM SYSAPPL-MIB; FROM SYSAPPL-MIB;
tn3270eRtMIB MODULE-IDENTITY tn3270eRtMIB MODULE-IDENTITY
LAST-UPDATED "9709240000Z" -- September 24, 1997 LAST-UPDATED "9711200000Z" -- November 20, 1997
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. 503/C117 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 (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-7507" (919) 254-4436"
DESCRIPTION DESCRIPTION
"This module defines a portion of the management information "This module defines a portion of the management information
base (MIB) that enables monitoring of TN3270 and TN3270E base (MIB) that enables monitoring of TN3270 and TN3270E
clients' response times by a TN3270E server." clients' response times by a TN3270E server."
::= { experimental 81 } ::= { snanauMIB 9 }
-- 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
-- Response Time Control Table -- Response Time Control Table
tn3270eRtCollCtlTable OBJECT-TYPE tn3270eRtCollCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry
Expires May 1998 [Page 25]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The response time monitoring collection control table, which "The response time monitoring collection control table, which
allows a management application to control the types of allows a management application to control the types of
response time data being collected, and the clients for which response time data being collected, and the clients for which
it is being collected. it is being collected.
This table is indexed by tn3270eSrvrConfIndex, imported from This table is indexed by tn3270eSrvrConfIndex, imported from
the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName.
Expires March 1998 [Page 25]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
tn3270eSrvrConfIndex indicates within a host which TN3270E tn3270eSrvrConfIndex indicates within a host which TN3270E
server an entry applied to. server an entry applied to.
tn3270eRtCollCtlClientGroupName is equivalent to the tn3270eRtCollCtlClientGroupName is equivalent to the
tn3270eClientGroupName index in the TN3270E-MIB; it identifies tn3270eClientGroupName index in the TN3270E-MIB; it identifies
the collection of IP clients for which response time data the collection of IP clients for which response time data
is being collectedr. The particular IP clients making up the is being collectedr. The particular IP clients making up the
collection are identified in the tn3270eClientGroupTable in collection are identified in the tn3270eClientGroupTable in
the TN3270E-MIB." the TN3270E-MIB."
::= { tn3270eRtObjects 1} ::= { tn3270eRtObjects 1}
skipping to change at line 1307 skipping to change at line 1321
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 }
Expires May 1998 [Page 26]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eRtCollCtlClientGroupName OBJECT-TYPE tn3270eRtCollCtlClientGroupName OBJECT-TYPE
SYNTAX Utf8String (SIZE(1..24)) SYNTAX Utf8String (SIZE(1..24))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of a client group. Membership in a client group is "The name of a client group. Membership in a client group is
specified via the TN3270E-MIB's tn3270eClientGroupTable. specified via the TN3270E-MIB's tn3270eClientGroupTable.
The index for that table, tn3270eClientGroupName, is The index for that table, tn3270eClientGroupName, is
equivalent to this object; it was not imported because equivalent to this object; it was not imported because
Expires March 1998 [Page 26]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
doing so results in MIB compiler errors." doing so results in MIB compiler errors."
::= { tn3270eRtCollCtlEntry 1 } ::= { tn3270eRtCollCtlEntry 1 }
tn3270eRtCollCtlType OBJECT-TYPE tn3270eRtCollCtlType OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
aggregate(0), aggregate(0),
excludeIpComponent(1), excludeIpComponent(1),
ddr(2), ddr(2),
average(3), average(3),
skipping to change at line 1360 skipping to change at line 1373
ddr(2) - Enable dynamic definite response. ddr(2) - Enable dynamic definite response.
average(3) - Produce an average response time based average(3) - Produce an average response time based
on a specified collection interval. on a specified collection interval.
buckets(4) - Maintain tn3270eRtDataBucket values in buckets(4) - Maintain tn3270eRtDataBucket values in
a corresponding tn3270eRtDataEntry, a corresponding tn3270eRtDataEntry,
based on the bucket boundaries based on the bucket boundaries
specified in the specified in the
tn3270eRtDataBucketBndry objects. tn3270eRtDataBucketBndry objects.
traps(5) - generate the traps specified in this traps(5) - generate the traps specified in this
MIB module. The tn3270eRtExceeded and MIB module. The tn3270eRtExceeded and
Expires May 1998 [Page 27]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eRtOkay are generated only if tn3270eRtOkay are generated only if
average(3) is also specified." average(3) is also specified."
::= { tn3270eRtCollCtlEntry 2 } ::= { tn3270eRtCollCtlEntry 2 }
tn3270eRtCollCtlSPeriod OBJECT-TYPE tn3270eRtCollCtlSPeriod OBJECT-TYPE
SYNTAX Unsigned32 -- 15 second minimum to 24 hour max SYNTAX Unsigned32 -- 15 second minimum to 24 hour max
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
Expires March 1998 [Page 27]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
DESCRIPTION DESCRIPTION
"The number of seconds that defines the sample period. "The number of seconds that defines the sample period.
The actual interval is defined as tn3270eRtCollCtlSPeriod The actual interval is defined as tn3270eRtCollCtlSPeriod
times tn3270eRtCollCtlSPMult. times tn3270eRtCollCtlSPMult.
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 {20} -- 20 seconds DEFVAL {20} -- 20 seconds
::= { tn3270eRtCollCtlEntry 3 } ::= { tn3270eRtCollCtlEntry 3 }
skipping to change at line 1414 skipping to change at line 1427
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtExceeded notification, "The threshold for generating a tn3270eRtExceeded notification,
signalling that a monitored total response time has exceeded the signalling that a monitored total response time has exceeded the
specified limit. A value of zero for this object suppresses specified limit. A value of zero for this object suppresses
generation of this notification. The value of this object is generation of this notification. The value of this object is
used only if the corresponding tn3270eRtCollCtlType has used only if the corresponding tn3270eRtCollCtlType has
average(3) and traps(5) selected." average(3) and traps(5) selected."
::= { tn3270eRtCollCtlEntry 5 } ::= { tn3270eRtCollCtlEntry 5 }
Expires May 1998 [Page 28]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eRtCollCtlThreshLow OBJECT-TYPE tn3270eRtCollCtlThreshLow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtOkay notification, "The threshold for generating a tn3270eRtOkay notification,
signalling that a monitored total response time has fallen below signalling that a monitored total response time has fallen below
Expires March 1998 [Page 28]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
the specified limit. A value of zero for this object suppresses the specified limit. A value of zero for this object suppresses
generation of this notification. The value of this object is generation of this notification. The value of this object is
used only if the corresponding tn3270eRtCollCtlType has used only if the corresponding tn3270eRtCollCtlType has
average(3) and traps(5) selected." average(3) and traps(5) selected."
::= { tn3270eRtCollCtlEntry 6 } ::= { tn3270eRtCollCtlEntry 6 }
tn3270eRtCollCtlIdleRate OBJECT-TYPE tn3270eRtCollCtlIdleRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "transaction count" UNITS "transaction count"
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at line 1467 skipping to change at line 1479
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 Tn3270eRtDataBucket1 object: response times counted in the Tn3270eRtDataBucket1 object:
those less than or equal to this value." those less than or equal to this value."
DEFVAL { 10 } DEFVAL { 10 }
::= { tn3270eRtCollCtlEntry 8 } ::= { tn3270eRtCollCtlEntry 8 }
tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
Expires May 1998 [Page 29]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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
tn3270eRtCollCtlBucketBndry1 object, defines the range of tn3270eRtCollCtlBucketBndry1 object, defines the range of
transaction response times counted in the Tn3270eRtDataBucket2 transaction response times counted in the Tn3270eRtDataBucket2
object: those greater than the value of the object: those greater than the value of the
Expires March 1998 [Page 29]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
tn3270eRtCollCtlBucketBndry1 object, and less than or equal to tn3270eRtCollCtlBucketBndry1 object, and less than or equal to
the value of this object." the value of this object."
DEFVAL { 20 } DEFVAL { 20 }
::= { tn3270eRtCollCtlEntry 9 } ::= { tn3270eRtCollCtlEntry 9 }
tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE tn3270eRtCollCtlBucketBndry3 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
skipping to change at line 1520 skipping to change at line 1532
tn3270eRtCollCtlBucketBndry3 object, and less than or equal to tn3270eRtCollCtlBucketBndry3 object, and less than or equal to
the value of this object. the value of this object.
The value of this object also defines the range of transaction The value of this object also defines the range of transaction
response times counted in the Tn3270eRtDataBucket5 object: response times counted in the Tn3270eRtDataBucket5 object:
those greater than the value of this object." those greater than the value of this object."
DEFVAL { 100 } DEFVAL { 100 }
::= { tn3270eRtCollCtlEntry 11 } ::= { tn3270eRtCollCtlEntry 11 }
tn3270eRtCollCtlRowStatus OBJECT-TYPE tn3270eRtCollCtlRowStatus OBJECT-TYPE
Expires May 1998 [Page 30]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted "This object allows entries to be created and deleted
in the tn3270eRtCollCtlTable. An entry in this table in the tn3270eRtCollCtlTable. An entry in this table
is deleted by setting this object to destroy(6). is deleted by setting this object to destroy(6).
Deleting an entry in this table has the side-effect Deleting an entry in this table has the side-effect
Expires March 1998 [Page 30]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
of removing all entries from the tn3270eRtDataTable of removing all entries from the tn3270eRtDataTable
that are associated with the entry being deleted." that are associated with the entry being deleted."
::= { tn3270eRtCollCtlEntry 12 } ::= { tn3270eRtCollCtlEntry 12 }
-- TN3270E Response Time Data Table -- TN3270E Response Time Data Table
tn3270eRtDataTable OBJECT-TYPE tn3270eRtDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eRtDataEntry SYNTAX SEQUENCE OF Tn3270eRtDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at line 1572 skipping to change at line 1584
entry in this table can wrap: entry in this table can wrap:
tn3270eRtDataTotalRt tn3270eRtDataTotalRt
tn3270eRtDataTotalIpRt tn3270eRtDataTotalIpRt
tn3270eRtDataTransCount tn3270eRtDataTransCount
tn3270eRtDataDrCount tn3270eRtDataDrCount
tn3270eRtDataElapsRnTrpSq tn3270eRtDataElapsRnTrpSq
tn3270eRtDataElapsIpRtSq tn3270eRtDataElapsIpRtSq
tn3270eRtDataBucket1 tn3270eRtDataBucket1
tn3270eRtDataBucket2 tn3270eRtDataBucket2
tn3270eRtDataBucket3 tn3270eRtDataBucket3
Expires May 1998 [Page 31]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eRtDataBucket4 tn3270eRtDataBucket4
tn3270eRtDataBucket5" tn3270eRtDataBucket5"
INDEX { INDEX {
tn3270eSrvrConfIndex, -- Server's local index tn3270eSrvrConfIndex, -- Server's local index
tn3270eRtCollCtlClientGroupName, -- Target of data collection tn3270eRtCollCtlClientGroupName, -- Target of data collection
tn3270eRtDataClientAddrType, tn3270eRtDataClientAddrType,
tn3270eRtDataClientAddress } tn3270eRtDataClientAddress }
::= { tn3270eRtDataTable 1 } ::= { tn3270eRtDataTable 1 }
Expires March 1998 [Page 31]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
Tn3270eRtDataEntry ::= SEQUENCE { Tn3270eRtDataEntry ::= SEQUENCE {
tn3270eRtDataClientAddrType Tn3270eAddrType, tn3270eRtDataClientAddrType Tn3270eAddrType,
tn3270eRtDataClientAddress Tn3270eTAddress, tn3270eRtDataClientAddress Tn3270eTAddress,
tn3270eRtDataDiscontinuityTime TimeStamp, tn3270eRtDataDiscontinuityTime TimeStamp,
tn3270eRtDataAvgRt Gauge32, tn3270eRtDataAvgRt Gauge32,
tn3270eRtDataAvgIpRt Gauge32, tn3270eRtDataAvgIpRt Gauge32,
tn3270eRtDataAvgTransCount Counter32, tn3270eRtDataAvgTransCount Counter32,
tn3270eRtDataIntTimeStamp DateAndTime, tn3270eRtDataIntTimeStamp DateAndTime,
tn3270eRtDataTotalRt Counter32, tn3270eRtDataTotalRt Counter32,
tn3270eRtDataTotalIpRt Counter32, tn3270eRtDataTotalIpRt Counter32,
tn3270eRtDataTransCount Counter32, tn3270eRtDataTransCount Counter32,
tn3270eRtDataDrCount Counter32, tn3270eRtDataDrCount Counter32,
tn3270eRtDataElapsRndTrpSq Unsigned32, tn3270eRtDataElapsRndTrpSq Unsigned32,
tn3270eRtDataElapsIpRtSq Unsigned32, tn3270eRtDataElapsIpRtSq Unsigned32,
tn3270eRtDataBucket1 Counter32, tn3270eRtDataBucket1 Counter32,
tn3270eRtDataBucket2 Counter32, tn3270eRtDataBucket2 Counter32,
tn3270eRtDataBucket3 Counter32, tn3270eRtDataBucket3 Counter32,
tn3270eRtDataBucket4 Counter32, tn3270eRtDataBucket4 Counter32,
tn3270eRtDataBucket5 Counter32 tn3270eRtDataBucket5 Counter32,
tn3270eRtDataRtMethod INTEGER
} }
tn3270eRtDataClientAddrType OBJECT-TYPE tn3270eRtDataClientAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX Tn3270eAddrType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of address that following in the "Indicates the type of address that following in the
instance OID represented by tn3270eRtDataClientAddress." instance OID represented by tn3270eRtDataClientAddress."
::= { tn3270eRtDataEntry 1 } ::= { tn3270eRtDataEntry 1 }
tn3270eRtDataClientAddress OBJECT-TYPE tn3270eRtDataClientAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the IP address of the TN3270 client being "Contains the IP address of the TN3270 client being
monitored. A null octet string is used if the aggregate monitored. A null octet string is used if the aggregate
of the Client Group is being collected " of the Client Group is being collected "
Expires May 1998 [Page 32]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
::= { tn3270eRtDataEntry 2 } ::= { tn3270eRtDataEntry 2 }
tn3270eRtDataDiscontinuityTime OBJECT-TYPE tn3270eRtDataDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which any one or more of this entry's objects which any one or more of this entry's objects
suffered a discontinuity. One possibility of this is suffered a discontinuity. One possibility of this is
Expires March 1998 [Page 32]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
when a TN3270E Server is stopped and then restarted when a TN3270E Server is stopped and then restarted
where local methods are used to setup collection where local methods are used to setup collection
policy (tn3270eRtCollCtlTable entries). policy (tn3270eRtCollCtlTable entries).
In order to prevent a TN3270E Server from caching this In order to prevent a TN3270E Server from caching this
object it is recommended that the TN3270E Server's object it is recommended that the TN3270E Server's
startup time be used as the objects initial value." startup time be used as the objects initial value."
::= { tn3270eRtDataEntry 3 } ::= { tn3270eRtDataEntry 3 }
tn3270eRtDataAvgRt OBJECT-TYPE tn3270eRtDataAvgRt OBJECT-TYPE
skipping to change at line 1676 skipping to change at line 1690
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 5 } ::= { tn3270eRtDataEntry 5 }
tn3270eRtDataAvgTransCount OBJECT-TYPE tn3270eRtDataAvgTransCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 values "The sliding transaction count used for calculating the values
Expires May 1998 [Page 33]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects. of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects.
The actual transaction count is available in the The actual transaction count is available in the
tn3270eRtDataTransCount object." tn3270eRtDataTransCount object."
::= { 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
Expires March 1998 [Page 33]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
"The date and time of the last interval that tn3270eRtDataAvgRt, "The date and time of the last interval that tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgTransCount were tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgTransCount were
calculated." calculated."
::= { tn3270eRtDataEntry 7 } ::= { tn3270eRtDataEntry 7 }
tn3270eRtDataTotalRt OBJECT-TYPE tn3270eRtDataTotalRt 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
skipping to change at line 1729 skipping to change at line 1743
DESCRIPTION DESCRIPTION
"A count of the total number of transactions detected." "A count of the total number of transactions detected."
::= { tn3270eRtDataEntry 10 } ::= { tn3270eRtDataEntry 10 }
tn3270eRtDataDrCount OBJECT-TYPE tn3270eRtDataDrCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "transactions" UNITS "transactions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Expires May 1998 [Page 34]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
"A count of the total number of definite responses detected." "A count of the total number of definite responses detected."
::= { 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. A sum of the "The sum of the elapsed round trip time squared. A sum of the
Expires March 1998 [Page 34]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
squares is keep in order to calculate a variance." squares is keep in order to calculate a variance."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 12 } ::= { tn3270eRtDataEntry 12 }
tn3270eRtDataElapsIpRtSq OBJECT-TYPE tn3270eRtDataElapsIpRtSq 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
skipping to change at line 1783 skipping to change at line 1797
::= { tn3270eRtDataEntry 15 } ::= { tn3270eRtDataEntry 15 }
tn3270eRtDataBucket3 OBJECT-TYPE tn3270eRtDataBucket3 OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the response times falling into bucket 3." "A count of the response times falling into bucket 3."
::= { tn3270eRtDataEntry 16 } ::= { tn3270eRtDataEntry 16 }
Expires May 1998 [Page 35]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eRtDataBucket4 OBJECT-TYPE tn3270eRtDataBucket4 OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the response times falling into bucket 4." "A count of the response times falling into bucket 4."
::= { tn3270eRtDataEntry 17 } ::= { tn3270eRtDataEntry 17 }
tn3270eRtDataBucket5 OBJECT-TYPE tn3270eRtDataBucket5 OBJECT-TYPE
Expires March 1998 [Page 35]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the response times falling into bucket 5." "A count of the response times falling into bucket 5."
::= { tn3270eRtDataEntry 18 } ::= { tn3270eRtDataEntry 18 }
tn3270eRtDataRtMethod OBJECT-TYPE
SYNTAX INTEGER {
none(0),
responses(1),
timemark(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object indicates the method that was used
in calculate the IP Network Time."
::= { tn3270eRtDataEntry 19 }
-- Notifications -- Notifications
tn3270eRtExceeded NOTIFICATION-TYPE tn3270eRtExceeded NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eSrvrConfIndex, -- server's local index tn3270eSrvrConfIndex, -- server's local index
tn3270eRtCollCtlClientGroupName, -- target of data collection tn3270eRtCollCtlClientGroupName, -- target of data collection
tn3270eRtDataClientAddrType, tn3270eRtDataClientAddrType,
tn3270eRtDataClientAddress, tn3270eRtDataClientAddress,
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgTransCount tn3270eRtDataAvgTransCount,
tn3270eRtDataRtMethod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the average response time, "This notification is generated when the average response time,
tn3270eRtDataAvgRt, exceeds tn3270eRtCollCtlThresholdHigh at tn3270eRtDataAvgRt, exceeds tn3270eRtCollCtlThresholdHigh at
the end of a collection interval specified by the end of a collection interval specified by
Expires May 1998 [Page 36]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult. Note that tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult. Note that
the corresponding tn3270eCollCtlType must have traps(5) and the corresponding tn3270eCollCtlType must have traps(5) and
average(3) set for this notification to be generated. In average(3) set for this notification to be generated. In
addition, tn3270eRtDataAvgTransCount, addition, tn3270eRtDataAvgTransCount,
tn3270eRtCollCtlThreshHigh and tn3270eRtDataAvgRt are tn3270eRtCollCtlThreshHigh and tn3270eRtDataAvgRt are
algorithmically compared to tn3270eRtCollCtlIdleRate for algorithmically compared to tn3270eRtCollCtlIdleRate for
determination if this will be suppressed." determination if this will be suppressed."
::= { tn3270eRtNotifications 1 } ::= { tn3270eRtNotifications 1 }
tn3270eRtOkay NOTIFICATION-TYPE tn3270eRtOkay NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eSrvrConfIndex, -- server's local index tn3270eSrvrConfIndex, -- server's local index
tn3270eRtCollCtlClientGroupName, -- target of data collection tn3270eRtCollCtlClientGroupName, -- target of data collection
tn3270eRtDataClientAddrType, tn3270eRtDataClientAddrType,
tn3270eRtDataClientAddress,-- IP Address or null octet string tn3270eRtDataClientAddress,-- IP Address or null octet string
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgTransCount tn3270eRtDataAvgTransCount,
tn3270eRtDataRtMethod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the average response time, "This notification is generated when the average response time,
Expires March 1998 [Page 36]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
tn3270eRtDataAvgRt, falls below tn3270eRtCollCtlThresholdLow at tn3270eRtDataAvgRt, falls below tn3270eRtCollCtlThresholdLow at
the end of a collection interval specified by the end of a collection interval specified by
tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult, after a tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult, after a
tn3270eRtExceeded notification was generated. Note that the tn3270eRtExceeded notification was generated. Note that the
corresponding tn3270eCollCtlType must have traps(5) and corresponding tn3270eCollCtlType must have traps(5) and
average(3) set for this notification to be generated." average(3) set for this notification to be generated."
::= { tn3270eRtNotifications 2 } ::= { tn3270eRtNotifications 2 }
tn3270eRtCollStart NOTIFICATION-TYPE tn3270eRtCollStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
skipping to change at line 1874 skipping to change at line 1902
tn3270eResMapElementName, -- IDs LU or printer association tn3270eResMapElementName, -- IDs LU or printer association
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. In order collection is enabled for a member of a client group. In order
for this notification to occur the corresponding for this notification to occur the corresponding
tn3270eRtCollCtlType must have traps(5) selected. The objects tn3270eRtCollCtlType must have traps(5) selected. The objects
tn3270eResMapElementName and tn3270eResMapElementType contains tn3270eResMapElementName and tn3270eResMapElementType contains
Expires May 1998 [Page 37]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
valid values only if tn3270eRtDataClientAddress contains a valid values only if tn3270eRtDataClientAddress contains a
valid IP address (rather than the null octet string)." valid IP address (rather than the null octet string)."
::= { tn3270eRtNotifications 3 } ::= { tn3270eRtNotifications 3 }
tn3270eRtCollEnd NOTIFICATION-TYPE tn3270eRtCollEnd NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eSrvrConfIndex, -- server's local index tn3270eSrvrConfIndex, -- server's local index
tn3270eRtCollCtlClientGroupName, -- data collection target tn3270eRtCollCtlClientGroupName, -- data collection target
tn3270eRtDataClientAddrType, tn3270eRtDataClientAddrType,
tn3270eRtDataClientAddress, tn3270eRtDataClientAddress,
skipping to change at line 1898 skipping to change at line 1931
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRt, tn3270eRtDataTotalRt,
tn3270eRtDataTotalIpRt, tn3270eRtDataTotalIpRt,
tn3270eRtDataTransCount, tn3270eRtDataTransCount,
tn3270eRtDataDrCount, tn3270eRtDataDrCount,
tn3270eRtDataElapsRndTrpSq, tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq, tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1, tn3270eRtDataBucket1,
tn3270eRtDataBucket2, tn3270eRtDataBucket2,
tn3270eRtDataBucket3, tn3270eRtDataBucket3,
Expires March 1998 [Page 37]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
tn3270eRtDataBucket4, tn3270eRtDataBucket4,
tn3270eRtDataBucket5 tn3270eRtDataBucket5,
tn3270eRtDataRtMethod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a tn3270eRtDataEntry is "This notification is generated when a tn3270eRtDataEntry is
deleted after being active (actual data collected), in order to deleted after being active (actual data collected), in order to
enable a management application monitoring a tn3270eRtDataTable enable a management application monitoring a tn3270eRtDataTable
entry to end get the entry's final values. Note that the entry to end get the entry's final values. Note that the
corresponding tn3270eCollCtlType must have traps(5) set for this corresponding tn3270eCollCtlType must have traps(5) set for this
notification to be generated." notification to be generated."
::= { tn3270eRtNotifications 4 } ::= { tn3270eRtNotifications 4 }
skipping to change at line 1926 skipping to change at line 1955
-- Conformance Statement -- Conformance Statement
tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 } tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 }
tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 } tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 }
-- Compliance statements -- Compliance statements
tn3270eRtCompliance MODULE-COMPLIANCE tn3270eRtCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Expires May 1998 [Page 38]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
"The compliance statement for agents that support the "The compliance statement for agents that support the
TN327E-RT-MIB " TN327E-RT-MIB "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup } MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup }
OBJECT tn3270eRtCollCtlSPeriod OBJECT tn3270eRtCollCtlSPeriod
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to allow the user to change "The agent is not required to allow the user to change
the default value of this object and is allowed the default value of this object and is allowed
to use a different default." to use a different default."
skipping to change at line 1951 skipping to change at line 1985
OBJECTS { OBJECTS {
tn3270eRtCollCtlType, tn3270eRtCollCtlType,
tn3270eRtCollCtlSPeriod, tn3270eRtCollCtlSPeriod,
tn3270eRtCollCtlSPMult, tn3270eRtCollCtlSPMult,
tn3270eRtCollCtlThreshHigh, tn3270eRtCollCtlThreshHigh,
tn3270eRtCollCtlThreshLow, tn3270eRtCollCtlThreshLow,
tn3270eRtCollCtlIdleRate, tn3270eRtCollCtlIdleRate,
tn3270eRtCollCtlBucketBndry1, tn3270eRtCollCtlBucketBndry1,
tn3270eRtCollCtlBucketBndry2, tn3270eRtCollCtlBucketBndry2,
tn3270eRtCollCtlBucketBndry3, tn3270eRtCollCtlBucketBndry3,
Expires March 1998 [Page 38]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
tn3270eRtCollCtlBucketBndry4, tn3270eRtCollCtlBucketBndry4,
tn3270eRtCollCtlRowStatus, tn3270eRtCollCtlRowStatus,
tn3270eRtDataDiscontinuityTime, tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgTransCount, tn3270eRtDataAvgTransCount,
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataTotalRt, tn3270eRtDataTotalRt,
tn3270eRtDataTotalIpRt, tn3270eRtDataTotalIpRt,
tn3270eRtDataTransCount, tn3270eRtDataTransCount,
tn3270eRtDataDrCount, tn3270eRtDataDrCount,
tn3270eRtDataElapsRndTrpSq, tn3270eRtDataElapsRndTrpSq,
tn3270eRtDataElapsIpRtSq, tn3270eRtDataElapsIpRtSq,
tn3270eRtDataBucket1, tn3270eRtDataBucket1,
tn3270eRtDataBucket2, tn3270eRtDataBucket2,
tn3270eRtDataBucket3, tn3270eRtDataBucket3,
tn3270eRtDataBucket4, tn3270eRtDataBucket4,
tn3270eRtDataBucket5 } tn3270eRtDataBucket5,
tn3270eRtDataRtMethod }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for all host supporting the "This group is mandatory for all host supporting the
TN3270E-RT-MIB. " TN3270E-RT-MIB. "
Expires May 1998 [Page 39]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
::= { tn3270eRtGroups 1 } ::= { tn3270eRtGroups 1 }
tn3270eRtNotGroup NOTIFICATION-GROUP tn3270eRtNotGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
tn3270eRtExceeded, tn3270eRtExceeded,
tn3270eRtOkay, tn3270eRtOkay,
tn3270eRtCollStart, tn3270eRtCollStart,
tn3270eRtCollEnd tn3270eRtCollEnd
} }
STATUS current STATUS current
skipping to change at line 2004 skipping to change at line 2039
6. Security Considerations 6. 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. The method for this
authentication is a function of the SNMP Administrative Framework, and authentication is a function of the SNMP Administrative Framework, and
has not been expanded by this MIB. has not been expanded by this MIB.
Expires March 1998 [Page 39]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
Several objects in this MIB allow write access or provide for remote Several objects in this MIB allow write access or provide for remote
creation. Allowing this support in a non-secure environment can have a creation. Allowing this support in a non-secure environment can have 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 should be implementers seriously consider whether set operations should be
allowed without providing, at a minimum, authentication of request allowed without providing, at a minimum, authentication of request
origin. It it recommended that without such support that the following origin. It it recommended that without such support that the following
objects be implemented as read-only: objects be implemented as read-only:
o tn3270eRtCollCtlType o tn3270eRtCollCtlType
o tn3270eRtCollSPeriod o tn3270eRtCollSPeriod
skipping to change at line 2030 skipping to change at line 2061
o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlThreshLow
o tn3270eRtCollCtlIdleRate o tn3270eRtCollCtlIdleRate
o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry1
o tn3270eRtCollCtlBucketBndry2 o tn3270eRtCollCtlBucketBndry2
o tn3270eRtCollCtlBucketBndry3 o tn3270eRtCollCtlBucketBndry3
o tn3270eRtCollCtlBucketBndry4 o tn3270eRtCollCtlBucketBndry4
The following object should either be implemented as read-only or not The following object should either be implemented as read-only or not
implemented when security is an issue as previously discussed: implemented when security is an issue as previously discussed:
Expires May 1998 [Page 40]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
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 scope of this memo. the scope of this memo.
7. Acknowledgments 7. Acknowledgments
This document is a product of the TN3270E Working Group. Special This document is a product of the TN3270E Working Group. Special
thanks is due to Derek Bolton and Michael Boe of Cisco Systems for thanks is due to Derek Bolton and Michael Boe of Cisco Systems for
skipping to change at line 2053 skipping to change at line 2088
8. References 8. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
Waldbusser S., "Structure of Management Information for version 2 Waldbusser S., "Structure of Management Information for version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
[2] Network Working Group, Postel, J., and Reynolds, J., "Telnet [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet
Protocol Specification", RFC 854, May 1983. Protocol Specification", RFC 854, May 1983.
Expires March 1998 [Page 40]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
[3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing
Mark Option", RFC 860, May 1983. Mark Option", RFC 860, May 1983.
[4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option",
RFC 1041, January 1988. RFC 1041, January 1988.
[5] McCloghrie, K., and M. Rose, Editors, "Management Information Base [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17, for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, Hughes LAN Systems, Performance Systems International, RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991. March 1991.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Textual Conventions for version 2 of the Simple Waldbusser, "Textual Conventions for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996. Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Expires May 1998 [Page 41]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
Waldbusser, "Protocol Operations for version 2 of the Simple Waldbusser, "Protocol Operations for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Conformance Statements for version 2 of the Simple Waldbusser, "Conformance Statements for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1904, January 1996. Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, MIT Laboratory for Computer Science, May 1990. International, MIT Laboratory for Computer Science, May 1990.
skipping to change at line 2095 skipping to change at line 2131
Managed Objects for TN3270E Using SMIv2", Internet-Draft Work in Managed Objects for TN3270E Using SMIv2", Internet-Draft Work in
progress, June 1997. progress, June 1997.
[11] Network Working Group, and Kelly, B., "TN3270 Enhancements", RFC [11] Network Working Group, and Kelly, B., "TN3270 Enhancements", RFC
1647, July 1994. 1647, July 1994.
[12] IBM, International Technical Support Centers, "Response Time Data [12] IBM, International Technical Support Centers, "Response Time Data
Gathering", GG24-3212-01, November 1990. Gathering", GG24-3212-01, November 1990.
[13] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level [13] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level
Expires March 1998 [Page 41]~
White, Moore TN3270E Response Time Collection MIB 29 September 1997
Managed Objects for Applications", April 15, 1997. Managed Objects for Applications", April 15, 1997.
9. Authors' Addresses 9. Authors' Addresses
Kenneth D. White Kenneth D. White
Dept. BRQA/Bldg. 503/C117 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 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
Expires May 1998 [Page 42]~
White, Moore TN3270E Response Time Collection MIB 19 November 1997
Phone: +1-919-254-7507 Phone: +1-919-254-7507
E-mail: remoore@us.ibm.com E-mail: remoore@us.ibm.com
Expires March 1998 [Page 42]~ Expires May 1998 [Page 43]~
 End of changes. 103 change blocks. 
197 lines changed or deleted 233 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/