draft-ietf-tn3270e-rt-mib-04.txt   draft-ietf-tn3270e-rt-mib-05.txt 
TN3270E Working Group Kenneth White TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-04.txt> IBM Corp. INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-05.txt> IBM Corp.
Expiration Date: October, 1998 Robert Moore Expiration Date: November, 1998 Robert Moore
IBM Corp. IBM Corp.
Definitions of Protocol and Managed Objects for Definitions of Protocol and Managed Objects for
TN3270E Response Time Collection Using SMIv2 TN3270E Response Time Collection Using SMIv2
(TN3270E-RT-MIB) (TN3270E-RT-MIB)
<draft-ietf-tn3270e-rt-mib-04.txt> <draft-ietf-tn3270e-rt-mib-05.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, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other Internet Drafts may be updated, replaced, or obsoleted by other
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3
3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3 3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3
3.1 General Response Time Collection . . . . . . . . . . . . . . . 3 3.1 General Response Time Collection . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.4.1 DR Usage . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2 TIMEMARK Usage . . . . . . . . . . . . . . . . . . . . . . 12 3.4.2 TIMING-MARK Usage . . . . . . . . . . . . . . . . . . . . 11
3.5 Performance Data Modelling . . . . . . . . . . . . . . . . . . 13 3.5 Performance Data Modelling . . . . . . . . . . . . . . . . . . 13
3.5.1 Averaging Response Times . . . . . . . . . . . . . . . . . 13 3.5.1 Averaging Response Times . . . . . . . . . . . . . . . . . 13
3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . . . 16 3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . . . 15
4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 17 4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 16
4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . . . 17 4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . . . 17
4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . . . 20 4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . . . 19
4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21 4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 22 4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 22
5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38 6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38
7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 39 7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 38
8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39
9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41 10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 40
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 41 11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 41
1.0 Introduction 1.0 Introduction
This document is a product of the TN3270E Working Group. It defines a This document is a product of the TN3270E Working Group. It defines a
protocol and a MIB module to enable a TN3270E server to collect and keep protocol and a MIB module to enable a TN3270E server to collect and keep
track of response time data for both TN3270 and TN3270E clients. Basis track of response time data for both TN3270 and TN3270E clients. Basis
for implementing this MIB: for implementing this MIB:
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using
SMIv2 [16]. SMIv2 [16]
o TN3270E RFCs o TN3270E RFCs
o Telnet Timing Mark Option RFC [13].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference [19]. document are to be interpreted as described in RFC 2119, reference [19].
2.0 The SNMP Network Management Framework 2.0 The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of six major The SNMP Network Management Framework presently consists of six major
components. They are: components. They are:
o the overall architecture, described in RFC 2271 [7]. o the overall architecture, described in RFC 2271 [7].
skipping to change at page 4, line 9 skipping to change at page 4, line 15
approach was deemed unsuitable since not all TN3270E server approach was deemed unsuitable since not all TN3270E server
implementations have access to their underlying SNA stacks. The RTM implementations have access to their underlying SNA stacks. The RTM
concepts of keeping response time buckets for service level agreements concepts of keeping response time buckets for service level agreements
and of interval-based response time collection for performance and of interval-based response time collection for performance
monitoring are preserved in the MIB module defined in this memo. monitoring are preserved in the MIB module defined in this memo.
As mentioned, this memo focuses on using definite responses to timestamp As mentioned, this memo focuses on using definite responses to timestamp
the flows between a client and its TN3270E server for generating the flows between a client and its TN3270E server for generating
performance data. Use of a definite response flow requires that the performance data. Use of a definite response flow requires that the
client supports TN3270E with the RESPONSES function negotiated. The client supports TN3270E with the RESPONSES function negotiated. The
TN3270 TIMEMARK option can be used instead of definite response for TN3270 TIMING-MARK option can be used instead of definite response for
supporting TN3270 clients or TN3270E clients that don't support supporting TN3270 clients or TN3270E clients that don't support
RESPONSES. This document focuses first on defining the protocol and RESPONSES. This document focuses first on defining the protocol and
methods for generating performance data using definite responses, and methods for generating performance data using definite responses, and
then describes how the TIMEMARK option can be used instead of definite then describes how the TIMING-MARK option can be used instead of
response. definite response.
In an SNA network, a transaction between a client Logical Unit (LU) and In an SNA network, a transaction between a client Logical Unit (LU) and
a target host in general looks as follows: a target host in general looks as follows:
------------------------------------------------ ------------------------------------------------
| | | |
| Client LU Target SNA Host | | Client LU Target SNA Host |
| | | |
| Timestamps | | Timestamps |
| request A | | request A |
skipping to change at page 5, line 39 skipping to change at page 5, line 45
A TN3270E server can use SNA definite responses and the TN3270 A TN3270E server can use SNA definite responses and the TN3270
Enhancement (RFC 1647 [15]) RESPONSES function to calculate response Enhancement (RFC 1647 [15]) RESPONSES function to calculate response
times for a transaction, by timestamping when a client request arrives times for a transaction, by timestamping when a client request arrives
at the server, when the reply arrives from the target host, and when the at the server, when the reply arrives from the target host, and when the
response acknowledging this reply arrives from the client. response acknowledging this reply arrives from the client.
Section 3.4, Timestamp Calculation, provides specifics on when in the Section 3.4, Timestamp Calculation, provides specifics on when in the
sequence of flows between a TN3270E client and its target SNA host a sequence of flows between a TN3270E client and its target SNA host a
TN3270E server takes the required timestamps. In addition, it provides TN3270E server takes the required timestamps. In addition, it provides
information on how a TN3270 TIMEMARK request/response flow can be used information on how a TN3270 TIMING-MARK request/response flow can be
instead of DR for approximating IP network transit times. used instead of DR for approximating IP network transit times.
The following figure adds a TN3270E server between the client, in this The following figure adds a TN3270E server between the client, in this
case a TN3270E client and the target SNA host: case a TN3270E client and the target SNA host:
------------------------------------------------ ------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server SNA Host | | Server SNA Host |
| Timestamps | | Timestamps |
| | | |
skipping to change at page 6, line 31 skipping to change at page 6, line 31
A TN3270E server can save timestamp D when it receives a client request, A TN3270E server can save timestamp D when it receives a client request,
save timestamp E when the target SNA host replies, and save timestamp F save timestamp E when the target SNA host replies, and save timestamp F
when the client responds to the definite response request that flowed when the client responds to the definite response request that flowed
with the reply. It doesn't matter whether the target SNA host requested with the reply. It doesn't matter whether the target SNA host requested
a definite response on its reply: if it didn't, the TN3270E server a definite response on its reply: if it didn't, the TN3270E server
makes the request on its own, to enable it to produce timestamp F. In makes the request on its own, to enable it to produce timestamp F. In
this case the TN3270E server does not forward the response to the target this case the TN3270E server does not forward the response to the target
SNA host, as the dotted line in the figure indicates. SNA host, as the dotted line in the figure indicates.
Because it is a special case, a transaction in which a target SNA host
returns an UNBIND in response to a client's request, and the TN3270E
server forwards the UNBIND to the client, is not included in any
response time calculations.
In order to generate timestamp F, a TN3270E server MUST insure that the In order to generate timestamp F, a TN3270E server MUST insure that the
transaction specifies DR, and that the TN3270E RESPONSES function has transaction specifies DR, and that the TN3270E RESPONSES function has
been negotiated between itself and the client. Negotiation of the been negotiated between itself and the client. Negotiation of the
TN3270E RESPONSES function occurs during the client's TN3270E session TN3270E RESPONSES function occurs during the client's TN3270E session
initialization. The TN3270E servers that the authors are aware of do initialization. The TN3270E servers that the authors are aware of do
request the RESPONSES function during client session initialization. request the RESPONSES function during client session initialization.
TN3270E clients either automatically support the RESPONSES function, or TN3270E clients either automatically support the RESPONSES function, or
can be configured during startup to support it. can be configured during startup to support it.
Using timestamps D, E, and F the following response times can be Using timestamps D, E, and F the following response times can be
skipping to change at page 8, line 30 skipping to change at page 8, line 34
always be calculated for transactions in which the host SNA always be calculated for transactions in which the host SNA
application specifies DR in its reply, and so these transactions application specifies DR in its reply, and so these transactions
will always be included in the aggregate. will always be included in the aggregate.
- For clients that support sending of responses, having dynamic - For clients that support sending of responses, having dynamic
definite responses enabled for a collection results in the definite responses enabled for a collection results in the
inclusion of additional transactions in the aggregate: inclusion of additional transactions in the aggregate:
specifically, those for which the host SNA application did not specifically, those for which the host SNA application did not
specify DR in its reply. specify DR in its reply.
A TN3270E server also has the option of substituting TIMEMARK processing A TN3270E server also has the option of substituting TIMING-MARK
for definite responses in calculating the IP-network component of a processing for definite responses in calculating the IP-network
transaction's response time. Once again, there is no reason for the component of a transaction's response time. Once again, there is no
server to do this if the collection has been set up to exclude the reason for the server to do this if the collection has been set up to
IP-network component altogether in computing response times. exclude the IP-network component altogether in computing response times.
The MIB is structured to keep counts and averages for total response The MIB is structured to keep counts and averages for total response
times (F - D) and their IP-network components (F - E). A management times (F - D) and their IP-network components (F - E). A management
application can obviously calculate from these two values an average application can obviously calculate from these two values an average
SNA-network component (E - D) for the response times. This SNA-network SNA-network component (E - D) for the response times. This SNA-network
component includes the SNA node processing time at both the TN3270E component includes the SNA node processing time at both the TN3270E
server and at the target application. server and at the target application.
A host TN3270E server refers to an implementation where the TN3270E A host TN3270E server refers to an implementation where the TN3270E
server is collocated with the Systems Network Architecture (SNA) System server is collocated with the Systems Network Architecture (SNA) System
Services Control Point (SSCP) for the dependent Secondary Logical Units Services Control Point (SSCP) for the dependent Secondary Logical Units
(SLUs) that the server makes available to its clients for connecting (SLUs) that the server makes available to its clients for connecting
into an SNA network. A gateway TN3270E server resides on an SNA node into an SNA network. A gateway TN3270E server resides on an SNA node
other than an SSCP, either an SNA type 2.0 node or an APPN node acting other than an SSCP, either an SNA type 2.0 node, a
in the role of a Dependent LU Requester (DLUR). Host and gateway boundary-function-attached type 2.1 node, or an APPN node acting in the
TN3270E server implementations typically differ greatly as to their role of a Dependent LU Requester (DLUR). Host and gateway TN3270E
internal implementation and System Definition (SYSDEF) requirements. server implementations typically differ greatly as to their internal
implementation and System Definition (SYSDEF) requirements.
If a host TN3270E server is in the same SNA host as the target If a host TN3270E server is in the same SNA host as the target
application, then the SNA-network component of a transaction's response application, then the SNA-network component of a transaction's response
time will approximately equal the host transit time (B - A) described time will approximately equal the host transit time (B - A) described
previously. A host TN3270E server implementation can, however, previously. A host TN3270E server implementation can, however,
typically support the establishment of sessions to target applications typically support the establishment of sessions to target applications
in SNA hosts remote from itself. In this case the SNA-network component in SNA hosts remote from itself. In this case the SNA-network component
of the response time equals the actual SNA-network transit time plus two of the response time equals the actual SNA-network transit time plus two
host transit times. host transit times.
3.3 Correlating TN3270E Server and Host Response Times 3.3 Correlating TN3270E Server and Host Response Times
It is possible that response time data is collected from TN3270E servers It is possible that response time data is collected from TN3270E servers
at the same time as a management application is monitoring the SNA at the same time as a management application is monitoring the SNA
sessions at a host. For example, a management application can be sessions at a host. For example, a management application can be
monitoring a secondary logical unit (SLU) while retrieving data from a monitoring a secondary logical unit (SLU) while retrieving data from a
TN3270E server. Consider the following figure: TN3270E server. Consider the following figure:
skipping to change at page 10, line 17 skipping to change at page 10, line 21
names at the TN3270E server. Neither the tn3270eClientGroupTable, the names at the TN3270E server. Neither the tn3270eClientGroupTable, the
tn3270eResPoolTable, nor the tn3270eClientResMapTable from the tn3270eResPoolTable, nor the tn3270eClientResMapTable from the
TN3270E-MIB can be used for correlation, since the mappings defined by TN3270E-MIB can be used for correlation, since the mappings defined by
these tables can overlap, and may not provide one-to-one mappings. these tables can overlap, and may not provide one-to-one mappings.
3.4 Timestamp Calculation 3.4 Timestamp Calculation
This section goes into more detail concerning when the various This section goes into more detail concerning when the various
timestamps can be taken as the flows between a TN3270E client and its timestamps can be taken as the flows between a TN3270E client and its
target SNA host pass through a TN3270E server. In addition, information target SNA host pass through a TN3270E server. In addition, information
is provided on how the TN3270 TIMEMARK request/response flow can be used is provided on how the TN3270 TIMING-MARK request/response flow can be
in place of DR for approximating IP network transit times. used in place of DR for approximating IP network transit times.
3.4.1 DR Usage 3.4.1 DR Usage
Consider the following flow: Consider the following flow:
---------------------------------------------------------- ----------------------------------------------------------
| | | |
| Client TN3270E Target SNA | | Client TN3270E Target SNA |
| Server Host | | Server Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D (BB,CD,OIC,ER) | | request D (BB,CD,OIC,ER) |
| -------------------------------------------> | | -------------------------------------------> |
| reply (FIC,ER,EB) | | | reply(DR) (FIC,ER,EB) | |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply(DR) E (LIC,DR) | | reply E (LIC,DR) |
| <-----------------------------------------< | | <-----------------------------------------< |
| | +/-RSP F | | | +/-RSP F |
| >----------------------------------------> | | >----------------------------------------> |
| | | |
| BB : Begin Bracket ER : Response by exception | | BB : Begin Bracket ER : Response by exception |
| EB : End Bracket DR : Definite Response Requested | | EB : End Bracket DR : Definite Response Requested |
| CD : Change Direction FIC : First in chain | | CD : Change Direction FIC : First in chain |
| OIC: Only in chain MIC: Middle in chain | | OIC: Only in chain MIC: Middle in chain |
| LIC: Last in chain | | LIC: Last in chain |
---------------------------------------------------------- ----------------------------------------------------------
Timestamp D is taken at the TN3270E server when a client has sent data Timestamp D is taken at the TN3270E server when the server has received
to the server for forwarding to its target SNA host. This is most likely data from a client for forwarding to its target SNA host, and the
when the server finds the end of record indicator in the TCP data direction of the SNA session allows the server to forward the data
received from the client. The target SNA application returns its reply immediately (either the direction is inbound towards the SNA host, or
in one or more SNA Request Units (RUs); in this example there are four
RUs in the reply. The first RU is marked as first in chain (FIC), the
next two are marked as middle in chain (MIC), and the last is marked as
last in chain (LIC). Timestamp E SHOULD be taken prior to sending the
RESPONSES request to the client; normally this is done when the server the session is between brackets). This is most likely when the server
receives the LIC RU. Timestamp F is taken when the RESPONSES response finds the end of record indicator in the TCP data received from the
is received from the client. client.
The target SNA application returns its reply in one or more SNA Request
Units (RUs); in this example there are four RUs in the reply. The first
RU is marked as first in chain (FIC), the next two are marked as middle
in chain (MIC), and the last is marked as last in chain (LIC). If the
SNA host sends a multiple-RU chain, the server does not know until the
last RU is received whether DR is being requested. The server's only
chance to request DR from the client, however, comes when it forwards
the FIC RU, since this is the only time that the TN3270E header is
included. Since a server may forward the FIC RU to the client before it
receives the LIC RU from the SNA host, some servers routinely specify DR
on all FIC RUs.
If the server has specified DR on the TN3270E request for the FIC RU in
a chain, it takes timestamp E when it forwards the LIC RU to the client.
Since timestamp E is used for calculating the IP-network time for the
transaction, the server SHOULD take timestamp E as close as possible to
its "Telnet edge". The server takes timestamp F when it receives the
RESPONSES response from the client.
A target SNA application doesn't necessarily return data to a client in A target SNA application doesn't necessarily return data to a client in
a transaction; it may, for example, require more data from the client a transaction; it may, for example, require more data from the client
before it can formulate a reply. In this case the application may before it can formulate a reply. In this case the application may
simply return to the TN3270E server a change of direction indicator. A simply return to the TN3270E server a change of direction indicator. At
TCP connection is full duplex: data can be received and sent on it at this point the server must send something to the client (typically a
the same time. An SNA session, on the other hand, is half duplex, with Write operation with a WCC) to unlock the keyboard. If the server
a change of direction indicator to alter the direction of data flow. specifies DR on the request to the client triggered by its receipt of
Timestamps E and F require a reply to flow to the client. A best-effort the change of direction indicator from the SNA application, then
approach should be followed by a TN3270E server when it attempts to timestamps E and F can be taken, and the usual response times can be
calculate timestamps. For cases where the target SNA application sends calculated. When the client sends in the additional data and gets a
a change of direction indicator rather than a reply, it is suggested textual response from the SNA application, the server treats this as a
that the entire transaction be omitted from any response time separate transaction from the one involving the change of direction.
calculations.
Another consideration is a mismatch between DR requested on the SNA side
and DR requested by a TN3270E server. If the SNA host sends a
multiple-RU chain, the server does not know until the last RU is
received whether DR is being requested. Meanwhile, the server may have
forwarded the first RU in the chain to the client. In practice,
therefore, some servers convert ER flows to DR flows. Timestamp E can
be taken when the first RESPONSES request flows to the client, and
timestamp F when its response is received. In this instance an
additional timestamp G is needed when the LIC RU is received:
---------------------------------------------------
| |
| Client TN3270E Target |
| Server SNA Host |
| Timestamps |
| |
| <---IP Network-------><---SNA Network---> |
| |
| request D (BB,CD,OIC,ER) |
| ------------------------------------------> |
| reply(DR) E (FIC,ER,EB) | |
| <----------------------------------------< |
| | +/-RSP F |
| >-------------------> |
| reply (MIC,ER) |
| <----------------------------------------< |
| reply (MIC,ER) |
| <----------------------------------------< |
| reply(DR) (LIC,DR) |
| <----------------------------------------< |
| | +/-RSP G |
| >-------------------> |
| |
---------------------------------------------------
The response times can then be calculated as follows:
o Total response time: Timestamp G - Timestamp D
o IP network transit time: Timestamp F - Timestamp E
If DR is requested by the LIC RU, then the TN3270E server can may either
its response or the earlier one for approximating IP network transit
time.
3.4.2 TIMEMARK Usage 3.4.2 TIMING-MARK Usage
It is possible for a TN3270E server to use the TIMEMARK flow for It is possible for a TN3270E server to use the TIMING-MARK flow for
approximating IP network transit times. Using TIMEMARKs would make it approximating IP network transit times. Using TIMING-MARKs would make
possible for a server to collect performance data for TN3270 clients, as it possible for a server to collect performance data for TN3270 clients,
well as for TN3270E clients that do not support the RESPONSES function. as well as for TN3270E clients that do not support the RESPONSES
In order for TIMEMARKs to be used in this way, a client can't have the function. In order for TIMING-MARKs to be used in this way, a client
NOP option enabled, since responses are needed to the server's TIMEMARK can't have the NOP option enabled, since responses are needed to the
requests. An IP network transit time approximation using a TIMEMARK is server's TIMING-MARK requests. An IP network transit time approximation
basically the amount of time it takes for a TN3270 server to receive using a TIMING-MARK is basically the amount of time it takes for a
from a client a response to a TIMEMARK request. TN3270 server to receive from a client a response to a TIMING-MARK
request.
To get an estimate for IP network transit time, a TN3270E server sends a To get an estimate for IP network transit time, a TN3270E server sends a
TIMEMARK request to a client after a LIC RU has been received, as a TIMING-MARK request to a client after a LIC RU has been received, as a
means of approximating IP network transit time: means of approximating IP network transit time:
--------------------------------------------------- ---------------------------------------------------
| | | |
| Client TN3270E Target | | Client TN3270E Target |
| Server Host | | Server Host |
| Timestamps | | Timestamps |
| | | |
| <---IP Network-------><---SNA Network---> | | <---IP Network-------><---SNA Network---> |
| | | |
| request D (BB,CD,OIC,ER) | | request D (BB,CD,OIC,ER) |
| -------------------------------------------> | | -------------------------------------------> |
| reply (FIC,ER,EB) | | | reply (FIC,ER,EB) | |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply (MIC,ER) | | reply (MIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| reply E (LIC,ER) | | reply E (LIC,ER) |
| <-----------------------------------------< | | <-----------------------------------------< |
| TIMEMARK Rqst E' | | TIMING-MARK Rqst E' |
| <--------------------- | | <--------------------- |
| | TIMEMARK Rsp F' | | | TIMING-MARK Rsp F' |
| >-------------------> | | >-------------------> |
| | | |
--------------------------------------------------- ---------------------------------------------------
The response times can then be calculated as follows: The response times can then be calculated as follows:
o TN3270E server total response time: o TN3270E server total response time:
(Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E') (Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E')
o TN3270E server IP network time: Timestamp F' - Timestamp E' o TN3270E server IP network time: Timestamp F' - Timestamp E'
If a TN3270E server is performing the TIMEMARK function (independent of If a TN3270E server is performing the TIMING-MARK function (independent
the response time monitoring use of the function discussed here), then of the response time monitoring use of the function discussed here),
it most likely has a TIMEMARK interval for determining when to examine then it most likely has a TIMING-MARK interval for determining when to
client sessions for sending the TIMEMARK request. This interval, which examine client sessions for sending the TIMING-MARK request. This
is ordinarily a global value for an entire TN3270E server, is interval, which is ordinarily a global value for an entire TN3270E
represented in the TN3270E-MIB by the tn3270eSrvrConfActivityInterval server, is represented in the TN3270E-MIB by the
object. A TIMEMARK request is sent only if, when it is examined, a tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent only
client session is found to have had no activity for a different fixed if, when it is examined, a client session is found to have had no
length of time, represented in the TN3270E-MIB by the activity for a different fixed length of time, represented in the
tn3270eSrvrConfActivityTimeout object. TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object.
Servers that support a large number of client sessions should spread out Servers that support a large number of client sessions should spread out
the TIMEMARK requests they send to these clients over the activity the TIMING-MARK requests they send to these clients over the activity
interval, rather than sending them all in a single burst, since interval, rather than sending them all in a single burst, since
otherwise the network may be flooded with TIMEMARK requests. When a otherwise the network may be flooded with TIMING-MARK requests. When a
server uses TIMEMARKs for approximating response times, this tends to server uses TIMING-MARKs for approximating response times, this tends to
introduce a natural spreading into its TIMEMARK requests, since the introduce a natural spreading into its TIMING-MARK requests, since the
requests are triggered by the arrival of traffic from an SNA host. requests are triggered by the arrival of traffic from an SNA host.
A TN3270E server MUST integrate its normal TIMEMARK processing with its A TN3270E server MUST integrate its normal TIMING-MARK processing with
use of TIMEMARKs for computing response times. In particular, it MUST its use of TIMING-MARKs for computing response times. In particular, it
NOT send a second TIMEMARK request to a client while waiting for the MUST NOT send a second TIMING-MARK request to a client while waiting for
first to return, since this is ruled out by the TIMEMARK protocol the first to return, since this is ruled out by the TIMING-MARK protocol
itself. If a TIMEMARK flow has just been performed for a client shortly
before the LIC RU arrives, the server MAY use the interval from this
flow as its approximation for IP network transit time, (in other words,
as its (F' - E') value) when calculating its approximation for the
transaction's total response time, rather than sending a second TIMEMARK
request so soon after the preceding one.
Regardless of when the server sends its TIMEMARK request, the accuracy itself. If a TIMING-MARK flow has just been performed for a client
of its total response time calculation depends on exactly when the shortly before the LIC RU arrives, the server MAY use the interval from
client responds to the TIMEMARK request. this flow as its approximation for IP network transit time, (in other
words, as its (F' - E') value) when calculating its approximation for
the transaction's total response time, rather than sending a second
TIMING-MARK request so soon after the preceding one.
Regardless of when the server sends its TIMING-MARK request, the
accuracy of its total response time calculation depends on exactly when
the client responds to the TIMING-MARK request.
3.5 Performance Data Modelling 3.5 Performance Data Modelling
The following two subsections detail how the TN3270E-RT-MIB models and The following two subsections detail how the TN3270E-RT-MIB models and
controls capture of two types of response time data: average response controls capture of two types of response time data: average response
times and response time buckets. times and response time buckets.
3.5.1 Averaging Response Times 3.5.1 Averaging Response Times
Average response times play two different roles in the MIB: Average response times play two different roles in the MIB:
skipping to change at page 14, line 14 skipping to change at page 13, line 47
o Select a fixed, relatively short, sample period SPeriod; the default o Select a fixed, relatively short, sample period SPeriod; the default
value for SPeriod in the MIB is 20 seconds. value for SPeriod in the MIB is 20 seconds.
o Select an averaging period multiplier SPMult. The actual collection o Select an averaging period multiplier SPMult. The actual collection
interval will then be SPMult times SPeriod. The default value for interval will then be SPMult times SPeriod. The default value for
SPMult in the MIB is 30, yielding a default collection interval of SPMult in the MIB is 30, yielding a default collection interval of
10 minutes. Note that the collection interval (SPMult*SPeriod) is 10 minutes. Note that the collection interval (SPMult*SPeriod) is
always a multiple of the sample period. always a multiple of the sample period.
Clearlly, SPMult*SPeriod should not be thought of as literally the
averaging period. The average calculated will include contributions
older than that time, and does not weight equally all contributions
since that time. In fact, it gives a smoother result than a
traditional sliding average, as used in finance. More subtly, it is
best to think of the effective averaging period as being
2*SPMult*SPeriod. To see this, consider how long the contribution
to the result made by a particular transaction lasts. With a
traditional sliding average, it lasts exactly the averaging period.
With the aging mechanism described here, it has a half-life of
SPMult*SPeriod.
o Maintain the following counters to keep track of activity within the o Maintain the following counters to keep track of activity within the
current sample period; these are internal counters, not made visible current sample period; these are internal counters, not made visible
to a management application via the MIB. to a management application via the MIB.
- T (number of transactions in the period) - T (number of transactions in the period)
- TotalRts (sum of the total response times for all transactions - TotalRts (sum of the total response times for all transactions
in the period) in the period)
- TotalIpRts (sum of the IP network transit times for all - TotalIpRts (sum of the IP network transit times for all
skipping to change at page 15, line 47 skipping to change at page 15, line 38
classified as a problem, not as a statistical anomaly based on too small classified as a problem, not as a statistical anomaly based on too small
a sample. a sample.
The solution is to make the significance level for a sample a function The solution is to make the significance level for a sample a function
of the average response time. A value IdleCount is specified, which is of the average response time. A value IdleCount is specified, which is
used to qualify an sample as statistically significant. In order to used to qualify an sample as statistically significant. In order to
determine at a collection interval whether to generate a determine at a collection interval whether to generate a
tn3270eRtExceeded notification, a TN3270E server uses the following tn3270eRtExceeded notification, a TN3270E server uses the following
algorithm: algorithm:
if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &lt; IdleCount if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &gt;= IdleCount
then generate the notification, then generate the notification,
where AvgRt is the value that would be returned by the object where AvgRt is the value that would be returned by the object
tn3270eRtDataAvgRt at the end of the interval, and the "**" notation tn3270eRtDataAvgRt at the end of the interval, and the "**" notation
indicates exponientiation. indicates exponientiation.
Two examples illustrate how this algorithm works. Suppose that Two examples illustrate how this algorithm works. Suppose that
IdleCount has been set to 20 transactions, and the high threshold to 200 IdleCount has been set to 20 transactions, and the high threshold to 200
msecs per transaction. If the average observed response time is 300 msecs per transaction. If the average observed response time is 300
msecs, then a notification will be generated only if AvgCountTrans >= msecs, then a notification will be generated only if AvgCountTrans >=
skipping to change at page 18, line 36 skipping to change at page 18, line 16
and the client's response will still be forwarded to the and the client's response will still be forwarded to the
application. But this response will play no role in the server's application. But this response will play no role in the server's
response time calculations. response time calculations.
If this bit is set to 0, then the server includes in the collection If this bit is set to 0, then the server includes in the collection
only those transactions for which it can include an (approximate) only those transactions for which it can include an (approximate)
IP-network component in the total response time for the transaction. IP-network component in the total response time for the transaction.
This component MAY be derived from a "natural" DR (if the client This component MAY be derived from a "natural" DR (if the client
supports the RESPONSES function), from a dynamic DR introduced by supports the RESPONSES function), from a dynamic DR introduced by
the server (if the client supports the RESPONSES function and the the server (if the client supports the RESPONSES function and the
ddr(2) bit has been set to 1), or from TIMEMARK processing (if the ddr(2) bit has been set to 1), or from TIMING-MARK processing (if
client supports TIMEMARKs). the client supports TIMING-MARKs).
If this bit is set to 1, then the ddr(2) bit is ignored, since there If this bit is set to 1, then the ddr(2) bit is ignored, since there
is no reason for the server to request additional responses from the is no reason for the server to request additional responses from the
client(s) in the group. client(s) in the group.
o ddr(2) - If this bit is set to 1, then the server SHOULD, for those o ddr(2) - If this bit is set to 1, then the server SHOULD, for those
clients in the group that support the RESPONSES function, add a DR clients in the group that support the RESPONSES function, add a DR
request to a reply in each transaction (usually, but not necessarily request to the FIC reply in each transaction, and use the client's
the LIC reply), and use the client's subsequent response for subsequent response for calculating an (approximate) IP-network
calculating an (approximate) IP-network component to include in the component to include in the transaction's total response times.
transaction's total response times.
If this bit is set to 0, then the server does not add a DR request If this bit is set to 0, then the server does not add a DR request
to any replies from the target SNA application. that it was not otherwise going to add to any replies from the
target SNA application.
If the excludeIpComponent(1) bit is set to 1, then this bit is If the excludeIpComponent(1) bit is set to 1, then this bit is
ignored by the server. ignored by the server.
o average(3) - If this bit is set to 1, then the server SHOULD o average(3) - If this bit is set to 1, then the server SHOULD
calculate a sliding-window average for the collection, based on the calculate a sliding-window average for the collection, based on the
parameters specified for the group. parameters specified for the group.
If this bit is set to 0, then an average is not calculated. In this If this bit is set to 0, then an average is not calculated. In this
case the tn3270eRtExceeded and tn3270eRtOkay notifications are not case the tn3270eRtExceeded and tn3270eRtOkay notifications are not
skipping to change at page 21, line 6 skipping to change at page 20, line 40
o tn3270eRtDataBucket5Rts o tn3270eRtDataBucket5Rts
A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a
management application to detect when the values of the counter objects management application to detect when the values of the counter objects
in this table may have been reset, or otherwise experienced a in this table may have been reset, or otherwise experienced a
discontinuity. A possible cause for such a discontinuity is the TN3270E discontinuity. A possible cause for such a discontinuity is the TN3270E
server's being stopped or restarted. This object returns a meaningful server's being stopped or restarted. This object returns a meaningful
value regardless of which collection control options were selected. value regardless of which collection control options were selected.
An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time
was calculated using either the definite response or TIMEMARK approach. was calculated using either the definite response or TIMING-MARK
approach.
When an entry is created in the tn3270eRtCollCtlTable with its When an entry is created in the tn3270eRtCollCtlTable with its
tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is
automatically created in the tn3270eRtDataTable; this entry's automatically created in the tn3270eRtDataTable; this entry's
tn3270eRtDataClientAddress has the value of a zero-length octet string, tn3270eRtDataClientAddress has the value of a zero-length octet string,
and its tn3270eRtDataClientAddrType has the value of unknown(0). and 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
skipping to change at page 22, line 42 skipping to change at page 22, line 22
returning final values for the collection's data objects. returning final values for the collection's data objects.
4.4 Advisory Spin Lock Usage 4.4 Advisory Spin Lock Usage
Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory
lock that allows cooperating TN3270E-RT-MIB applications to coordinate lock that allows cooperating TN3270E-RT-MIB applications to coordinate
their use of the tn3270eRtCollCtlTable. When creating a new entry or their use of the tn3270eRtCollCtlTable. When creating a new entry or
altering an existing entry in the tn3270eRtCollCtlTable, an application altering an existing entry in the tn3270eRtCollCtlTable, an application
SHOULD make use of tn3270eRtSpinLock to serialize application changes or SHOULD make use of tn3270eRtSpinLock to serialize application changes or
additions. Since this is an advisory lock, its use by management additions. Since this is an advisory lock, its use by management
applications SHALL NOT be not enforced by agents. Agents MUST, however, applications SHALL NOT be enforced by agents. Agents MUST, however,
implement the tn3270eRtSpinLock object. implement the tn3270eRtSpinLock object.
5.0 Definitions 5.0 Definitions
TN3270E-RT-MIB DEFINITIONS ::= BEGIN TN3270E-RT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Gauge32 Counter32, Unsigned32, Gauge32
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 23, line 10 skipping to change at page 22, line 44
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex, Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex,
tn3270eClientGroupName, tn3270eResMapElementType tn3270eClientGroupName, tn3270eResMapElementType
FROM TN3270E-MIB FROM TN3270E-MIB
snanauMIB snanauMIB
FROM SNA-NAU-MIB; FROM SNA-NAU-MIB;
tn3270eRtMIB MODULE-IDENTITY tn3270eRtMIB MODULE-IDENTITY
LAST-UPDATED "9804300000Z" -- April 30, 1998 LAST-UPDATED "9805110000Z" -- May 11, 1998
ORGANIZATION "TN3270E Working Group" ORGANIZATION "TN3270E Working Group"
CONTACT-INFO CONTACT-INFO
"Kenneth White (kennethw@vnet.ibm.com) "Kenneth White (kennethw@vnet.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
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
skipping to change at page 24, line 29 skipping to change at page 24, line 7
tn3270eSrvrConfIndex, -- Server's index tn3270eSrvrConfIndex, -- Server's index
tn3270eClientGroupName } -- What to collect on tn3270eClientGroupName } -- What to collect on
::= { tn3270eRtCollCtlTable 1 } ::= { tn3270eRtCollCtlTable 1 }
Tn3270eRtCollCtlEntry ::= SEQUENCE { Tn3270eRtCollCtlEntry ::= SEQUENCE {
tn3270eRtCollCtlType BITS, tn3270eRtCollCtlType BITS,
tn3270eRtCollCtlSPeriod Unsigned32, tn3270eRtCollCtlSPeriod Unsigned32,
tn3270eRtCollCtlSPMult Unsigned32, tn3270eRtCollCtlSPMult Unsigned32,
tn3270eRtCollCtlThreshHigh Unsigned32, tn3270eRtCollCtlThreshHigh Unsigned32,
tn3270eRtCollCtlThreshLow Unsigned32, tn3270eRtCollCtlThreshLow Unsigned32,
tn3270eRtCollCtlIdleRate Unsigned32, tn3270eRtCollCtlIdleCount Unsigned32,
tn3270eRtCollCtlBucketBndry1 Unsigned32, tn3270eRtCollCtlBucketBndry1 Unsigned32,
tn3270eRtCollCtlBucketBndry2 Unsigned32, tn3270eRtCollCtlBucketBndry2 Unsigned32,
tn3270eRtCollCtlBucketBndry3 Unsigned32, tn3270eRtCollCtlBucketBndry3 Unsigned32,
tn3270eRtCollCtlBucketBndry4 Unsigned32, tn3270eRtCollCtlBucketBndry4 Unsigned32,
tn3270eRtCollCtlRowStatus RowStatus } tn3270eRtCollCtlRowStatus RowStatus }
-- The OID { tn3270eRtCollCtlEntry 1 } is not used -- The OID { tn3270eRtCollCtlEntry 1 } is not used
tn3270eRtCollCtlType OBJECT-TYPE tn3270eRtCollCtlType OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
skipping to change at page 26, line 37 skipping to change at page 26, line 16
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 signalling that a monitored total response time has fallen
below the specified limit. A value of zero for this object below the specified limit. A value of zero for this object
suppresses generation of this notification. The value of suppresses generation of this notification. The value of
this object is used only if the corresponding this object is used only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 0 } -- suppress notifications DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 6 } ::= { tn3270eRtCollCtlEntry 6 }
tn3270eRtCollCtlIdleRate OBJECT-TYPE tn3270eRtCollCtlIdleCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "transactions" UNITS "transactions"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is used to determine whether a "The value of this object is used to determine whether a
sample that yields an average response time exceeding the sample that yields an average response time exceeding the
value of tn3270eRtCollCtlThreshHigh was a statistically value of tn3270eRtCollCtlThreshHigh was a statistically
valid one. If the following statement is true, then the valid one. If the following statement is true, then the
sample was statistically valid, and so a tn3270eRtExceeded sample was statistically valid, and so a tn3270eRtExceeded
notification should be generated: notification should be generated:
AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &lt; IdleRate AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &gt;= IdleCount
This comparison is done only if the corresponding This comparison is done only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected."
DEFVAL { 1 } DEFVAL { 1 }
::= { tn3270eRtCollCtlEntry 7 } ::= { tn3270eRtCollCtlEntry 7 }
tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of seconds" UNITS "tenths of seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 32, line 17 skipping to change at page 31, line 50
object." object."
::= { tn3270eRtDataEntry 11 } ::= { tn3270eRtDataEntry 11 }
tn3270eRtDataElapsRndTrpSq OBJECT-TYPE tn3270eRtDataElapsRndTrpSq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of seconds squared" UNITS "tenths of seconds squared"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the elapsed round trip time squared. The sum "The sum of the elapsed round trip time squared. The sum
of the squares is keep in order to enable calculation of of the squares is kept in order to enable calculation of
a variance." 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
"The sum of the elapsed IP round trip time squared. "The sum of the elapsed IP round trip time squared.
The sum of the squares is keep in order to enable The sum of the squares is kept in order to enable
calculation of a variance." calculation of a variance."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eRtDataEntry 13 } ::= { tn3270eRtDataEntry 13 }
tn3270eRtDataBucket1Rts OBJECT-TYPE tn3270eRtDataBucket1Rts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of the response times falling into bucket 1. "The count of the response times falling into bucket 1.
skipping to change at page 33, line 42 skipping to change at page 33, line 20
A management application can detect discontinuities in this A management application can detect discontinuities in this
counter by monitoring the tn3270eRtDataDiscontinuityTime counter by monitoring the tn3270eRtDataDiscontinuityTime
object." object."
::= { tn3270eRtDataEntry 18 } ::= { tn3270eRtDataEntry 18 }
tn3270eRtDataRtMethod OBJECT-TYPE tn3270eRtDataRtMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(0),
responses(1), responses(1),
timemark(2) timingMark(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates the method that was "The value of this object indicates the method that was
used in calculating the IP network time. used in calculating the IP network time.
The value 'none(0) indicates that response times were not The value 'none(0) indicates that response times were not
calculated for the IP network." calculated for the IP network."
::= { tn3270eRtDataEntry 19 } ::= { tn3270eRtDataEntry 19 }
skipping to change at page 34, line 38 skipping to change at page 34, line 17
DESCRIPTION DESCRIPTION
"This notification is generated when the average response "This notification is generated when the average response
time, tn3270eRtDataAvgRt, exceeds time, tn3270eRtDataAvgRt, exceeds
tn3270eRtCollCtlThresholdHigh at the end of a collection tn3270eRtCollCtlThresholdHigh at the end of a collection
interval specified by tn3270eCollCtlSPeriod interval specified by tn3270eCollCtlSPeriod
times tn3270eCollCtlSPMult. Note that the corresponding times tn3270eCollCtlSPMult. Note that the corresponding
tn3270eCollCtlType must have traps(5) and average(3) set tn3270eCollCtlType must have traps(5) and average(3) set
for this notification to be generated. In addition, for this notification to be generated. In addition,
tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and
tn3270eRtDataAvgRt are algorithmically compared to tn3270eRtDataAvgRt are algorithmically compared to
tn3270eRtCollCtlIdleRate for determination if this tn3270eRtCollCtlIdleCount for determination if this
notification will be suppressed." notification will be suppressed."
::= { tn3270eRtNotifications 1 } ::= { tn3270eRtNotifications 1 }
tn3270eRtOkay NOTIFICATION-TYPE tn3270eRtOkay NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans, tn3270eRtDataAvgCountTrans,
tn3270eRtDataRtMethod tn3270eRtDataRtMethod
skipping to change at page 36, line 45 skipping to change at page 36, line 24
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlThreshLow OBJECT tn3270eRtCollCtlThreshLow
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlIdleRate OBJECT tn3270eRtCollCtlIdleCount
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
OBJECT tn3270eRtCollCtlBucketBndry1 OBJECT tn3270eRtCollCtlBucketBndry1
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a SET operation "The agent is not required to support a SET operation
to this object in the absence of adequate security." to this object in the absence of adequate security."
skipping to change at page 37, line 41 skipping to change at page 37, line 20
-- Group definitions -- Group definitions
tn3270eRtGroup OBJECT-GROUP tn3270eRtGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eRtCollCtlType, tn3270eRtCollCtlType,
tn3270eRtCollCtlSPeriod, tn3270eRtCollCtlSPeriod,
tn3270eRtCollCtlSPMult, tn3270eRtCollCtlSPMult,
tn3270eRtCollCtlThreshHigh, tn3270eRtCollCtlThreshHigh,
tn3270eRtCollCtlThreshLow, tn3270eRtCollCtlThreshLow,
tn3270eRtCollCtlIdleRate, tn3270eRtCollCtlIdleCount,
tn3270eRtCollCtlBucketBndry1, tn3270eRtCollCtlBucketBndry1,
tn3270eRtCollCtlBucketBndry2, tn3270eRtCollCtlBucketBndry2,
tn3270eRtCollCtlBucketBndry3, tn3270eRtCollCtlBucketBndry3,
tn3270eRtCollCtlBucketBndry4, tn3270eRtCollCtlBucketBndry4,
tn3270eRtCollCtlRowStatus, tn3270eRtCollCtlRowStatus,
tn3270eRtDataDiscontinuityTime, tn3270eRtDataDiscontinuityTime,
tn3270eRtDataAvgRt, tn3270eRtDataAvgRt,
tn3270eRtDataAvgIpRt, tn3270eRtDataAvgIpRt,
tn3270eRtDataAvgCountTrans, tn3270eRtDataAvgCountTrans,
tn3270eRtDataIntTimeStamp, tn3270eRtDataIntTimeStamp,
 End of changes. 51 change blocks. 
154 lines changed or deleted 147 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/