idnits 2.17.1 draft-ietf-tn3270e-rt-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 40 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([16]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 1998) is 9509 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '17' is defined on line 2142, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 2145, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '1') ** Obsolete normative reference: RFC 1902 (ref. '3') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '4') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2271 (ref. '7') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '8') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '9') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '10') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '11') (Obsoleted by RFC 2575) ** Downref: Normative reference to an Historic RFC: RFC 1041 (ref. '14') ** Obsolete normative reference: RFC 1647 (ref. '15') (Obsoleted by RFC 2355) -- Possible downref: Non-RFC (?) normative reference: ref. '16' -- Possible downref: Non-RFC (?) normative reference: ref. '17' ** Obsolete normative reference: RFC 2028 (ref. '18') (Obsoleted by RFC 9281) Summary: 22 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 TN3270E Working Group Kenneth White 2 INTERNET DRAFT: IBM Corp. 3 Expiration Date: October, 1998 Robert Moore 4 IBM Corp. 5 April 1998 7 Definitions of Protocol and Managed Objects for 8 TN3270E Response Time Collection Using SMIv2 9 (TN3270E-RT-MIB) 10 12 Status of this Memo 14 This document is an Internet Draft. Internet Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet Drafts. 19 Internet Drafts are draft documents valid for a maximum of six months. 20 Internet Drafts may be updated, replaced, or obsoleted by other 21 documents at any time. It is not appropriate to use Internet Drafts as 22 reference material or to cite them other than as a "working draft" or 23 "work in progress." 25 Please check the I-D abstract listing contained in each Internet Draft 26 directory to learn the current status of this or any Internet Draft. 27 Distribution of this document is unlimited. 29 Copyright Notice 31 Copyright (C) The Internet Society (1998). All Rights Reserved. 33 Abstract 35 This memo defines the protocol and the Management Information Base (MIB) 36 for performing response time data collection on TN3270 and TN3270E 37 sessions by a TN3270E server. The response time data collected by a 38 TN3270E server is structured to support both validation of service level 39 agreements and performance monitoring of TN3270 and TN3270E Sessions. 40 This MIB has as a prerequisite the TN3270E-MIB, reference [16]. 42 TN3270E, defined by RFC 1647 [15], refers to the enhancements made to 43 the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC 44 1041 [14], RFC 854 [12], and RFC 860 [13] for a sample of what is meant 45 by TN3270 practices. 47 The specification of this MIB uses the Structure of Management 48 Information (SMI) for Version 2 of the Simple Network Management 49 Protocol (refer to RFC1902 [3]). 51 Table of Contents 53 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 57 3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3 58 3.1 General Response Time Collection . . . . . . . . . . . . . . . 3 59 3.2 TN3270E Server Response Time Collection . . . . . . . . . . . 5 60 3.3 Correlating TN3270E Server and Host Response Times . . . . . . 9 61 3.4 Timestamp Calculation . . . . . . . . . . . . . . . . . . . . 10 62 3.4.1 DR Usage . . . . . . . . . . . . . . . . . . . . . . . . . 10 63 3.4.2 TIMEMARK Usage . . . . . . . . . . . . . . . . . . . . . . 12 64 3.5 Performance Data Modelling . . . . . . . . . . . . . . . . . . 13 65 3.5.1 Averaging Response Times . . . . . . . . . . . . . . . . . 13 66 3.5.2 Response Time Buckets . . . . . . . . . . . . . . . . . . 16 68 4.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 17 69 4.1 tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . . . 17 70 4.2 tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . . . 20 71 4.3 Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21 72 4.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 22 74 5.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 22 76 6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38 78 7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 39 80 8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 82 9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 84 10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41 86 11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 41 88 1.0 Introduction 90 This document is a product of the TN3270E Working Group. It defines a 91 protocol and a MIB module to enable a TN3270E server to collect and keep 92 track of response time data for both TN3270 and TN3270E clients. Basis 93 for implementing this MIB: 95 o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using 96 SMIv2 [16]. 98 o TN3270E RFCs 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119, reference [19]. 104 2.0 The SNMP Network Management Framework 106 The SNMP Network Management Framework presently consists of six major 107 components. They are: 109 o the overall architecture, described in RFC 2271 [7]. 111 o the SMI, described in RFC 1902 [3], - the mechanisms used for 112 describing and naming objects for the purpose of management. 114 o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects 115 for the Internet suite of protocols. 117 o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] 118 -- the protocol for accessing managed information. 120 o the user-based security model defined in RFC 2274 [10]. 122 o the view-based access control model defined in RFC 2275 [11]. 124 Textual conventions are defined in RFC 1903 [4], and conformance 125 statements are defined in RFC 1904 [5]. Common applications are defined 126 in RFC 2273 [9]. 128 The Framework permits new objects to be defined for the purpose of 129 experimentation and evaluation. 131 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 132 conforming to the SMIv1 can be produced through the appropriate 133 translation. 135 3.0 Response Time Collection Methodology 137 This section explains the methodology and approach used by the MIB 138 defined by this memo for response time data collection by a TN3270E 139 server. 141 3.1 General Response Time Collection 143 Two primary methods exist for measuring response times in SNA networks: 145 o The Systems Network Architecture Management Services (SNA/MS) 146 Response Time Monitoring (RTM) function. 148 o Timestamping using definite response flows. 150 This memo defines an approach using definite responses to timestamp the 151 flows between a client and its TN3270E server, rather than by use of the 152 RTM method. Extensions to the SNA/MS RTM flow were considered, but this 153 approach was deemed unsuitable since not all TN3270E server 154 implementations have access to their underlying SNA stacks. The RTM 155 concepts of keeping response time buckets for service level agreements 156 and of interval-based response time collection for performance 157 monitoring are preserved in the MIB module defined in this memo. 159 As mentioned, this memo focuses on using definite responses to timestamp 160 the flows between a client and its TN3270E server for generating 161 performance data. Use of a definite response flow requires that the 162 client supports TN3270E with the RESPONSES function negotiated. The 163 TN3270 TIMEMARK option can be used instead of definite response for 164 supporting TN3270 clients or TN3270E clients that don't support 165 RESPONSES. This document focuses first on defining the protocol and 166 methods for generating performance data using definite responses, and 167 then describes how the TIMEMARK option can be used instead of definite 168 response. 170 In an SNA network, a transaction between a client Logical Unit (LU) and 171 a target host in general looks as follows: 173 ------------------------------------------------ 174 | | 175 | Client LU Target SNA Host | 176 | | 177 | Timestamps | 178 | request A | 179 | -----------------------------------------> | 180 | reply(DR) B | | 181 | <---------------------------------------< | 182 | | +/-RSP C | 183 | >---------------------------------------> | 184 | | 185 | DR: Definite Response requested | 186 | +/-RSP: Definite Response | 187 | | 188 ------------------------------------------------ 190 This transaction is a simple one, and is being used only to illustrate 191 how timestamping at a target SNA host can be used to generate response 192 times. An IBM redbook [12] provides a more detailed description of 193 response time collection for a transaction of this type. Note that for 194 the purpose of calculating an approximation for network transit time, it 195 doesn't matter if the response is positive or negative. Two response 196 time values are typically calculated: 198 o Host Transit Time: Timestamp B - Timestamp A 199 o Network Transit Time: Timestamp C - Timestamp B 201 Network transit time is an approximation for the amount of time that a 202 transaction requires to flow across a network, since the response flow 203 is being substituted for the request flow at the start of the 204 transaction. Network transit time, timestamp C - timestamp B, is the 205 amount of time that the definite response request and its response 206 required. Host time, timestamp B - timestamp A, is the actual time that 207 the host required to process the transaction. Experience has shown that 208 using the response flow to approximate network transit times is useful, 209 and does correlate well with actual network transit times. 211 A client SHOULD respond to a definite response request when it completes 212 processing the transaction. This is important since it increases the 213 accuracy of a total response time. Clients that immediately respond to 214 a definite response request will be attributed with lower total response 215 times then those that actually occurred. 217 The TN3270E-RT-MIB describes a method of collecting performance data 218 that is not appropriate for printer (LU Type 1 or LU Type 3) sessions; 219 thus collection of performance data for printer sessions is excluded 220 from this MIB. This exclusion of printer sessions is not considered a 221 problem, since these sessions are not the most important ones for 222 response time monitoring, and since historically they were excluded from 223 SNA/MS RTM collection. The tn3270eTcpConnResourceType object in a 224 tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to determine if 225 a client session is ineligible for response time data collection for 226 this reason. 228 3.2 TN3270E Server Response Time Collection 230 A TN3270E server connects a Telnet client performing 3270 emulation to a 231 target SNA host over both a client-side network (client to TN3270E 232 server) and an SNA Network (TN3270E server to target SNA host). The 233 client-side network is typicaly TCP/IP, but it need not be. For ease of 234 exposition this document uses the term "IP network" to refer to the 235 client-side network, since IP is by far the most common protocol for 236 these networks. 238 A TN3270E server can use SNA definite responses and the TN3270 239 Enhancement (RFC 1647 [15]) RESPONSES function to calculate response 240 times for a transaction, by timestamping when a client request arrives 241 at the server, when the reply arrives from the target host, and when the 242 response acknowledging this reply arrives from the client. 244 Section 3.4, Timestamp Calculation, provides specifics on when in the 245 sequence of flows between a TN3270E client and its target SNA host a 246 TN3270E server takes the required timestamps. In addition, it provides 247 information on how a TN3270 TIMEMARK request/response flow can be used 248 instead of DR for approximating IP network transit times. 250 The following figure adds a TN3270E server between the client, in this 251 case a TN3270E client and the target SNA host: 253 ------------------------------------------------ 254 | | 255 | Client TN3270E Target | 256 | Server SNA Host | 257 | Timestamps | 258 | | 259 | <---IP Network-------><---SNA Network---> | 260 | | 261 | request D | 262 | ------------------------------------------> | 263 | reply(DR) E | | 264 | <----------------------------------------< | 265 | | +/-RSP F | 266 | >-------------------- - - - - - - - - - > | 267 | | 268 ------------------------------------------------ 270 A TN3270E server can save timestamp D when it receives a client request, 271 save timestamp E when the target SNA host replies, and save timestamp F 272 when the client responds to the definite response request that flowed 273 with the reply. It doesn't matter whether the target SNA host requested 274 a definite response on its reply: if it didn't, the TN3270E server 275 makes the request on its own, to enable it to produce timestamp F. In 276 this case the TN3270E server does not forward the response to the target 277 SNA host, as the dotted line in the figure indicates. 279 In order to generate timestamp F, a TN3270E server MUST insure that the 280 transaction specifies DR, and that the TN3270E RESPONSES function has 281 been negotiated between itself and the client. Negotiation of the 282 TN3270E RESPONSES function occurs during the client's TN3270E session 283 initialization. The TN3270E servers that the authors are aware of do 284 request the RESPONSES function during client session initialization. 285 TN3270E clients either automatically support the RESPONSES function, or 286 can be configured during startup to support it. 288 Using timestamps D, E, and F the following response times can be 289 calculated by a TN3270E server: 291 o Total Response time: Timestamp F - Timestamp D 292 o IP Network Transit Time: Timestamp F - Timestamp E 294 Just as in the SNA case presented above, these response times are also 295 approximations, since the final +/- RSP from the client is being 296 substituted for the request from the client that began the transaction. 298 The MIB provides an object, tn3270eRtCollCtlType, to control several 299 aspects of response time data collection. One of the available options 300 in setting up a response time collection policy is to eliminate the 301 IP-network component altogether. This might be done because it is 302 determined either that the additional IP network traffic would not be 303 desirable, or that the IP-network component of the overall response 304 times is not significant. 306 Excluding the IP-network component from response times also has an 307 implication for the way in which response time data is aggregated. A 308 TN3270E server may find that some of its clients simply don't support 309 any of the functions necessary for the server to calculate the 310 IP-network component of response times. For these clients, the most 311 that the server can calculate is the SNA-network component of their 312 overall response times; the server records this SNA-network component as 313 the TOTAL response time each of these clients' transactions. If a 314 response time collection is aggregating data from a number of clients, 315 some of which have the support necessary for including the IP-network 316 component in their total response time calculations, and some of which 317 do not, then the server aggregates the data differently depending on 318 whether the collection has been defined to include or exclude the 319 IP-network component: 321 o If the IP-network component is included, then transactions for the 322 clients that don't support calculation of the IP-network component 323 of their response times are excluded from the aggregation 324 altogether. 326 o If the IP-network component is excluded, then total response times 327 for ALL clients include only the SNA-network component, even though 328 the server could have included an IP-network component in the 329 overall response times for some of these clients. The server does 330 this by setting timestamp F, which marks the end of a transaction's 331 total response time, equal to timestamp E, the end of the 332 transaction's SNA-network component. 334 The principle here is that all the transactions contributing their 335 response times to an aggregated value MUST make the same contribution. 336 If the aggregation specifies that an IP-network component MUST be 337 included in the aggregation's response times, then transactions for 338 which an IP-network component cannot be calculated aren't included at 339 all. If the aggregation specifies that an IP-network component is not 340 to be included, then only the SNA-network component is used, even for 341 those transactions for which an IP-network component could have been 342 calculated. 344 There is one more complication here: the MIB allows a management 345 application to enable or disable dynamic definite responses for a 346 response time collection. Once again the purpose of this option is to 347 give the network operator control over the amount of traffic introduced 348 into the IP network for response time data collection. A DYNAMIC 349 definite response is one that the TN3270E server itself adds to a reply, 350 in a transaction for which the SNA application at the target SNA host 351 did not specify DR in its reply. When the +/-RSP comes back from the 352 client, the server uses this response to calculate timestamp F, but then 353 it does not forward the response on to the SNA application (since the 354 application is not expecting a response to its reply). 356 The dynamic definite responses option is related to the option of 357 including or excluding the IP-network component of response times 358 (discussed above) as follows: 360 o If the IP-network component is excluded, then there is no reason for 361 enabling dynamic definite responses: the server always sets 362 timestamp F equal to timestamp E, so the additional IP-network 363 traffic elicited by a dynamic definite response would serve no 364 purpose. 366 o If the IP-network component is included, then enabling dynamic 367 definite responses causes MORE transactions to be included in the 368 aggregated response time values: 370 - For clients that do not support sending of responses, timestamp 371 F can never be calculated, and so their transactions are never 372 included in the aggregate. 374 - For clients that support sending of responses, timestamp F will 375 always be calculated for transactions in which the host SNA 376 application specifies DR in its reply, and so these transactions 377 will always be included in the aggregate. 379 - For clients that support sending of responses, having dynamic 380 definite responses enabled for a collection results in the 381 inclusion of additional transactions in the aggregate: 382 specifically, those for which the host SNA application did not 383 specify DR in its reply. 385 A TN3270E server also has the option of substituting TIMEMARK processing 386 for definite responses in calculating the IP-network component of a 387 transaction's response time. Once again, there is no reason for the 388 server to do this if the collection has been set up to exclude the 389 IP-network component altogether in computing response times. 391 The MIB is structured to keep counts and averages for total response 392 times (F - D) and their IP-network components (F - E). A management 393 application can obviously calculate from these two values an average 394 SNA-network component (E - D) for the response times. This SNA-network 395 component includes the SNA node processing time at both the TN3270E 396 server and at the target application. 398 A host TN3270E server refers to an implementation where the TN3270E 399 server is collocated with the Systems Network Architecture (SNA) System 400 Services Control Point (SSCP) for the dependent Secondary Logical Units 401 (SLUs) that the server makes available to its clients for connecting 402 into an SNA network. A gateway TN3270E server resides on an SNA node 403 other than an SSCP, either an SNA type 2.0 node or an APPN node acting 404 in the role of a Dependent LU Requester (DLUR). Host and gateway 405 TN3270E server implementations typically differ greatly as to their 406 internal implementation and System Definition (SYSDEF) requirements. 408 If a host TN3270E server is in the same SNA host as the target 409 application, then the SNA-network component of a transaction's response 410 time will approximately equal the host transit time (B - A) described 411 previously. A host TN3270E server implementation can, however, 412 typically support the establishment of sessions to target applications 413 in SNA hosts remote from itself. In this case the SNA-network component 414 of the response time equals the actual SNA-network transit time plus two 415 host transit times. 417 3.3 Correlating TN3270E Server and Host Response Times 419 It is possible that response time data is collected from TN3270E servers 420 at the same time as a management application is monitoring the SNA 421 sessions at a host. For example, a management application can be 422 monitoring a secondary logical unit (SLU) while retrieving data from a 423 TN3270E server. Consider the following figure: 425 ------------------------------------------------ 426 | | 427 | Client TN3270E Target | 428 | Server SNA Host | 429 | Timestamps (PLU) | 430 | (SLU) Timestamps| 431 | <---IP Network-------><---SNA Network---> | 432 | | 433 | request D A | 434 | ------------------------------------------> | 435 | reply(DR) E B | | 436 | <----------------------------------------< | 437 | | +/-RSP F C | 438 | >--------------------------------------> | 439 | | 440 ------------------------------------------------ 442 The following response times are available: 444 o Target SNA host transit time: Timestamp B - Timestamp A 445 o Target SNA host network transit time: Timestamp C - Timestamp B 446 o TN3270E server total response time: Timestamp F - Timestamp D 447 o TN3270E server IP-network component: Timestamp F - Timestamp E 449 The value added by the TN3270E server in this situation is its 450 approximation of the IP-network component of the overall response time. 451 The IP-network component can be subtracted from the total network 452 transit time (which can be captured at an SSCP monitoring SNA traffic 453 from/to the SLU) to see the actual SNA versus IP network transit times. 455 The MIB defined by this memo does not specifically address correlation 456 of the data it contains with response time data collected by direct 457 monitoring of SNA resources: its focus is exclusively response time 458 data collection from a TN3270E server perspective. It has, however, in 459 conjunction with the TN3270E-MIB [10], been structured to provide the 460 information necessary for correlation between TN3270E server-provided 461 response time information and that gathered from directly monitoring SNA 462 resources. 464 A management application attempting to correlate SNA resource usage to 465 Telnet clients can monitor either the tn3270eResMapTable or the 466 tn3270eTcpConnTable to determine resource-to-client address mappings. 467 Both of these tables are defined by the TN3270E-MIB [10]. Another 468 helpful table is the tn3270eSnaMapTable, which provides a mapping 469 between SLU names as they are known at the SSCP (VTAM) and their local 470 names at the TN3270E server. Neither the tn3270eClientGroupTable, the 471 tn3270eResPoolTable, nor the tn3270eClientResMapTable from the 472 TN3270E-MIB can be used for correlation, since the mappings defined by 473 these tables can overlap, and may not provide one-to-one mappings. 475 3.4 Timestamp Calculation 477 This section goes into more detail concerning when the various 478 timestamps can be taken as the flows between a TN3270E client and its 479 target SNA host pass through a TN3270E server. In addition, information 480 is provided on how the TN3270 TIMEMARK request/response flow can be used 481 in place of DR for approximating IP network transit times. 483 3.4.1 DR Usage 485 Consider the following flow: 487 ---------------------------------------------------------- 488 | | 489 | Client TN3270E Target SNA | 490 | Server Host | 491 | Timestamps | 492 | | 493 | <---IP Network-------><---SNA Network---> | 494 | | 495 | request D (BB,CD,OIC,ER) | 496 | -------------------------------------------> | 497 | reply (FIC,ER,EB) | | 498 | <-----------------------------------------< | 499 | reply (MIC,ER) | 500 | <-----------------------------------------< | 501 | reply (MIC,ER) | 502 | <-----------------------------------------< | 503 | reply(DR) E (LIC,DR) | 504 | <-----------------------------------------< | 505 | | +/-RSP F | 506 | >----------------------------------------> | 507 | | 508 | BB : Begin Bracket ER : Response by exception | 509 | EB : End Bracket DR : Definite Response Requested | 510 | CD : Change Direction FIC : First in chain | 511 | OIC: Only in chain MIC: Middle in chain | 512 | LIC: Last in chain | 513 ---------------------------------------------------------- 515 Timestamp D is taken at the TN3270E server when a client has sent data 516 to the server for forwarding to its target SNA host. This is most likely 517 when the server finds the end of record indicator in the TCP data 518 received from the client. The target SNA application returns its reply 519 in one or more SNA Request Units (RUs); in this example there are four 520 RUs in the reply. The first RU is marked as first in chain (FIC), the 521 next two are marked as middle in chain (MIC), and the last is marked as 522 last in chain (LIC). Timestamp E SHOULD be taken prior to sending the 523 RESPONSES request to the client; normally this is done when the server 524 receives the LIC RU. Timestamp F is taken when the RESPONSES response 525 is received from the client. 527 A target SNA application doesn't necessarily return data to a client in 528 a transaction; it may, for example, require more data from the client 529 before it can formulate a reply. In this case the application may 530 simply return to the TN3270E server a change of direction indicator. A 531 TCP connection is full duplex: data can be received and sent on it at 532 the same time. An SNA session, on the other hand, is half duplex, with 533 a change of direction indicator to alter the direction of data flow. 534 Timestamps E and F require a reply to flow to the client. A best-effort 535 approach should be followed by a TN3270E server when it attempts to 536 calculate timestamps. For cases where the target SNA application sends 537 a change of direction indicator rather than a reply, it is suggested 538 that the entire transaction be omitted from any response time 539 calculations. 541 Another consideration is a mismatch between DR requested on the SNA side 542 and DR requested by a TN3270E server. If the SNA host sends a 543 multiple-RU chain, the server does not know until the last RU is 544 received whether DR is being requested. Meanwhile, the server may have 545 forwarded the first RU in the chain to the client. In practice, 546 therefore, some servers convert ER flows to DR flows. Timestamp E can 547 be taken when the first RESPONSES request flows to the client, and 548 timestamp F when its response is received. In this instance an 549 additional timestamp G is needed when the LIC RU is received: 551 --------------------------------------------------- 552 | | 553 | Client TN3270E Target | 554 | Server SNA Host | 555 | Timestamps | 556 | | 557 | <---IP Network-------><---SNA Network---> | 558 | | 559 | request D (BB,CD,OIC,ER) | 560 | ------------------------------------------> | 561 | reply(DR) E (FIC,ER,EB) | | 562 | <----------------------------------------< | 563 | | +/-RSP F | 564 | >-------------------> | 565 | reply (MIC,ER) | 566 | <----------------------------------------< | 567 | reply (MIC,ER) | 568 | <----------------------------------------< | 569 | reply(DR) (LIC,DR) | 570 | <----------------------------------------< | 571 | | +/-RSP G | 572 | >-------------------> | 573 | | 574 --------------------------------------------------- 576 The response times can then be calculated as follows: 578 o Total response time: Timestamp G - Timestamp D 579 o IP network transit time: Timestamp F - Timestamp E 581 If DR is requested by the LIC RU, then the TN3270E server can may either 582 its response or the earlier one for approximating IP network transit 583 time. 585 3.4.2 TIMEMARK Usage 587 It is possible for a TN3270E server to use the TIMEMARK flow for 588 approximating IP network transit times. Using TIMEMARKs would make it 589 possible for a server to collect performance data for TN3270 clients, as 590 well as for TN3270E clients that do not support the RESPONSES function. 591 In order for TIMEMARKs to be used in this way, a client can't have the 592 NOP option enabled, since responses are needed to the server's TIMEMARK 593 requests. An IP network transit time approximation using a TIMEMARK is 594 basically the amount of time it takes for a TN3270 server to receive 595 from a client a response to a TIMEMARK request. 597 To get an estimate for IP network transit time, a TN3270E server sends a 598 TIMEMARK request to a client after a LIC RU has been received, as a 599 means of approximating IP network transit time: 601 --------------------------------------------------- 602 | | 603 | Client TN3270E Target | 604 | Server Host | 605 | Timestamps | 606 | | 607 | <---IP Network-------><---SNA Network---> | 608 | | 609 | request D (BB,CD,OIC,ER) | 610 | -------------------------------------------> | 611 | reply (FIC,ER,EB) | | 612 | <-----------------------------------------< | 613 | reply (MIC,ER) | 614 | <-----------------------------------------< | 615 | reply (MIC,ER) | 616 | <-----------------------------------------< | 617 | reply E (LIC,ER) | 618 | <-----------------------------------------< | 619 | TIMEMARK Rqst E' | 620 | <--------------------- | 621 | | TIMEMARK Rsp F' | 622 | >-------------------> | 623 | | 624 --------------------------------------------------- 626 The response times can then be calculated as follows: 628 o TN3270E server total response time: 629 (Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E') 631 o TN3270E server IP network time: Timestamp F' - Timestamp E' 632 If a TN3270E server is performing the TIMEMARK function (independent of 633 the response time monitoring use of the function discussed here), then 634 it most likely has a TIMEMARK interval for determining when to examine 635 client sessions for sending the TIMEMARK request. This interval, which 636 is ordinarily a global value for an entire TN3270E server, is 637 represented in the TN3270E-MIB by the tn3270eSrvrConfActivityInterval 638 object. A TIMEMARK request is sent only if, when it is examined, a 639 client session is found to have had no activity for a different fixed 640 length of time, represented in the TN3270E-MIB by the 641 tn3270eSrvrConfActivityTimeout object. 643 Servers that support a large number of client sessions should spread out 644 the TIMEMARK requests they send to these clients over the activity 645 interval, rather than sending them all in a single burst, since 646 otherwise the network may be flooded with TIMEMARK requests. When a 647 server uses TIMEMARKs for approximating response times, this tends to 648 introduce a natural spreading into its TIMEMARK requests, since the 649 requests are triggered by the arrival of traffic from an SNA host. 651 A TN3270E server MUST integrate its normal TIMEMARK processing with its 652 use of TIMEMARKs for computing response times. In particular, it MUST 653 NOT send a second TIMEMARK request to a client while waiting for the 654 first to return, since this is ruled out by the TIMEMARK protocol 655 itself. If a TIMEMARK flow has just been performed for a client shortly 656 before the LIC RU arrives, the server MAY use the interval from this 657 flow as its approximation for IP network transit time, (in other words, 658 as its (F' - E') value) when calculating its approximation for the 659 transaction's total response time, rather than sending a second TIMEMARK 660 request so soon after the preceding one. 662 Regardless of when the server sends its TIMEMARK request, the accuracy 663 of its total response time calculation depends on exactly when the 664 client responds to the TIMEMARK request. 666 3.5 Performance Data Modelling 668 The following two subsections detail how the TN3270E-RT-MIB models and 669 controls capture of two types of response time data: average response 670 times and response time buckets. 672 3.5.1 Averaging Response Times 674 Average response times play two different roles in the MIB: 676 o They are made available for management applications to retrieve. 677 o They serve as triggers for emitting notifications. 679 Sliding-window averages are used rather than straight interval-based 680 averages, because they are often more meaningful, and because they cause 681 less notification thrashing. Sliding-window average calculation can, if 682 necessary, be disabled, by setting the sample period multiplier, 683 tn3270eRtCollCtlSPMult, to 1, and setting the sample period, 684 tn3270eRtCollCtlSPeriod, to the required collection interval. 686 In order to calculate sliding-window averages, a TN3270E server MUST: 688 o Select a fixed, relatively short, sample period SPeriod; the default 689 value for SPeriod in the MIB is 20 seconds. 691 o Select an averaging period multiplier SPMult. The actual collection 692 interval will then be SPMult times SPeriod. The default value for 693 SPMult in the MIB is 30, yielding a default collection interval of 694 10 minutes. Note that the collection interval (SPMult*SPeriod) is 695 always a multiple of the sample period. 697 o Maintain the following counters to keep track of activity within the 698 current sample period; these are internal counters, not made visible 699 to a management application via the MIB. 701 - T (number of transactions in the period) 703 - TotalRts (sum of the total response times for all transactions 704 in the period) 706 - TotalIpRts (sum of the IP network transit times for all 707 transactions in the period; note that if IP network transit 708 times are being excluded from the response time collection, this 709 value will always be 0). 711 o Also maintain sliding counters, initialized to zero, for each of the 712 quantities being counted: 714 - AvgCountTrans (sliding count of transactions) 715 - TotalRtsSliding (sliding count of total response times) 716 - TotalIpRtsSliding (sliding count of IP network transit times) 718 o At the end of each sample period, update the sliding interval 719 counters, using the following floating-point calculations: 721 AvgCountTrans = AvgCountTrans + T 722 - (AvgCountTrans / SPMult) 724 TotalRtsSliding = TotalRtsSliding + TotalRts 725 - (TotalRtsSliding / SPMult) 727 TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts 728 - (TotalIpRtsSliding / SPMult) 730 Then reset T, TotalRts, and TotalIpRts to zero for use during the 731 next sample period. 733 o At the end of a collection interval, update the following MIB 734 objects as indicated; the floating-point numbers are rounded rather 735 than truncated. 737 tn3270eRtDataAvgCountTrans = AvgCountTrans 738 tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans 739 tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans 741 As expected, if IP network transit times are being excluded from 742 response time collection, then tn3270eRtDataAvgIpRt will always 743 return 0. 745 The sliding transaction counter AvgCountTrans is not used for updating 746 the MIB object tn3270eRtDataCountTrans: this object is an ordinary SMI 747 Counter32, which maintains a total count of transactions since its last 748 discontinuity event. The sliding counters are used only for calculating 749 averages. 751 Two mechanisms are present in the MIB to inhibit the generation of an 752 excessive number of notifications related to average response times. 753 First, there are high and low thresholds for average response times. A 754 tn3270eRtExceeded notification is generated the first time a 755 statistically significant average response time is found to have 756 exceeded the high threshold. (The test for statistical significance is 757 described below.) After this, no other tn3270eRtExceeded notifications 758 are generated until an average response time is found to have fallen 759 below the low threshold. 761 The other mechanism to limit notifications is the significance test for 762 a high average response time. Intuitively, the significance of an 763 average is directly related to the number of samples that go into it; so 764 we might be inclined to use a rule such as "for the purpose of 765 generating tn3270eRtExceeded notifications, ignore average response 766 times based on fewer than 20 transactions in the sample period." 768 In the case of response times, however, the number of transactions 769 sampled in a fixed sampling period is tied to these transactions' 770 response times. A few transactions with long response times can 771 guarantee that there will not be many transactions in a sample, because 772 these transactions "use up" the sampling time. Yet this case of a few 773 transactions with very poor response times should obviously be 774 classified as a problem, not as a statistical anomaly based on too small 775 a sample. 777 The solution is to make the significance level for a sample a function 778 of the average response time. A value IdleCount is specified, which is 779 used to qualify an sample as statistically significant. In order to 780 determine at a collection interval whether to generate a 781 tn3270eRtExceeded notification, a TN3270E server uses the following 782 algorithm: 784 if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) < IdleCount 785 then generate the notification, 787 where AvgRt is the value that would be returned by the object 788 tn3270eRtDataAvgRt at the end of the interval, and the "**" notation 789 indicates exponientiation. 791 Two examples illustrate how this algorithm works. Suppose that 792 IdleCount has been set to 20 transactions, and the high threshold to 200 793 msecs per transaction. If the average observed response time is 300 794 msecs, then a notification will be generated only if AvgCountTrans >= 795 80. If, however, the observed response time is 500 msecs, then a 796 notification is generated if AvgCountTrans >= 9. 798 There is no corresponding significance test for the tn3270eRtOkay 799 notification: this notification is generated based on an average 800 response time that falls below the low threshold, regardless of the 801 sample size behind that average. 803 3.5.2 Response Time Buckets 805 The MIB also supports collection of response time data into a set of 806 five buckets. This data is suitable either for verification of service 807 level agreements, or for monitoring by a management application to 808 identify performance problems. The buckets provide counts of 809 transactions whose total response times fall into a set of specified 810 ranges. 812 Like everything for a collection, the "total" response times collected 813 in the buckets are governed by the specification of whether IP network 814 transit times are to be included in the totals. Depending on how this 815 option is specified, the response times being counted in the buckets 816 will either be total response times (F - D), or only SNA network transit 817 times (effectively E - D, because when it is excluding the IP-network 818 component of transactions, a server makes timestamp F identical to 819 timestamp E). 821 Four bucket boundaries are specified for a response time collection, 822 resulting in five buckets. The first response time bucket counts those 823 transactions whose total response times were less than or equal to 824 Boundary 1, the second bucket counts those whose response times were 825 greater than Boundary 1 but less than or equal to Boundary 2, and so on. 826 The fifth bucket is unbounded on the top, counting all transactions 827 whose response times were greater than Boundary 4. 829 The four bucket boundaries have default values of: 1 second, 2 seconds, 830 5 seconds, and 10 seconds, respectively. These values are the defaults 831 in the 3174 controller's implementation of the SNA/MS RTM function, and 832 are thought to be appropriate for this MIB as well. 834 In SNA/MS the counter buckets were (by today's standards) relatively 835 small, with a maximum value of 65,535. The bucket objects in the MIB 836 are all Counter32's. 838 The following figure represents the buckets pictorially: 840 ---------------------------------------------- 841 | | 842 | Response Time Boundaries | 843 | | | | | | | | 844 | | | | | | | | 845 | | | | | | no | 846 | 0 B-1 B-2 B-3 B-4 bound| 847 | | | | | | | | 848 | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| | 849 | ----------------------------------------- | 850 | | 851 ---------------------------------------------- 853 4.0 Structure of the MIB 855 The TN3270E-RT-MIB has the following components: 857 o tn3270eRtCollCtlTable 858 o tn3270eRtDataTable 859 o Notifications 860 o Advisory Spin Lock Usage 862 4.1 tn3270eRtCollCtlTable 864 The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and 865 tn3270eClientGroupName imported from the TN3270E-MIB. 866 tn3270eSrvrConfIndex identifies within a host a particular TN3270E 867 server. tn3270eClientGroupName identifies a collection of IP clients 868 for which response time data is to be collected. The set of clients is 869 defined using the tn3270eClientGroupTable from the TN3270E-MIB. 871 A tn3270eRtCollCtlEntry contains the following objects: 873 -------------------------------------------------- 874 1st Index | tn3270eSrvrConfIndex Unsigned32 | 875 2nd Index | tn3270eClientGroupName Utf8String | 876 | tn3270eRtCollCtlType BITS | 877 | tn3270eRtCollCtlSPeriod Unsigned32 | 878 | tn3270eRtCollCtlSPMult Unsigned32 | 879 | tn3270eRtCollCtlThreshHigh Unsigned32 | 880 | tn3270eRtCollCtlThreshLow Unsigned32 | 881 | tn3270eRtCollCtlIdleCount Unsigned32 | 882 | tn3270eRtCollCtlBucketBndry1 Unsigned32 | 883 | tn3270eRtCollCtlBucketBndry2 Unsigned32 | 884 | tn3270eRtCollCtlBucketBndry3 Unsigned32 | 885 | tn3270eRtCollCtlBucketBndry4 Unsigned32 | 886 | tn3270eRtCollCtlRowStatus RowStatus | 887 -------------------------------------------------- 889 The tn3270eRtCollCtlType object controls the type(s) of response time 890 collection that occur, the granularity of the collection, whether 891 dynamic definite responses SHOULD be initiated, and whether 892 notifications SHOULD be generated. This object is of BITS SYNTAX, and 893 thus allows selection of multiple options. 895 The BITS in the tn3270eRtCollCtlType object have the following meanings: 897 o aggregate(0) - If this bit is set to 1, then data SHOULD be 898 aggregated for the whole client group. In this case there will be 899 only one row created for the collection in the tn3270eRtDataTable. 900 The first two indexes for this row, tn3270eSrvrConfIndex and 901 tn3270eClientGroupName, will have the same values as the indexes as 902 the corresponding tn3270eRtCollCtlEntry. The third and fourth 903 indexes of an aggregated tn3270eRtDataEntry have the values 904 unknown(0) (tn3270eRtDataClientAddrType) and a zero-length octet 905 string (tn3270eRtDataClientAddress). 907 If this bit is set to 0, then a separate entry is created in the 908 tn3270eRtDataTable for each member of the client group. In this 909 case the tn3270eRtDataClientAddress contains the client's actual IP 910 Address, and tn3270eRtDataClientAddrType indicates the address type. 912 o excludeIpComponent(1) - If this bit is set to 1, then the server 913 SHOULD exclude the IP-network component from all the response times 914 for this collection. If the target SNA application specifies DR in 915 any of its replies, this DR will still be passed down to the client, 916 and the client's response will still be forwarded to the 917 application. But this response will play no role in the server's 918 response time calculations. 920 If this bit is set to 0, then the server includes in the collection 921 only those transactions for which it can include an (approximate) 922 IP-network component in the total response time for the transaction. 923 This component MAY be derived from a "natural" DR (if the client 924 supports the RESPONSES function), from a dynamic DR introduced by 925 the server (if the client supports the RESPONSES function and the 926 ddr(2) bit has been set to 1), or from TIMEMARK processing (if the 927 client supports TIMEMARKs). 929 If this bit is set to 1, then the ddr(2) bit is ignored, since there 930 is no reason for the server to request additional responses from the 931 client(s) in the group. 933 o ddr(2) - If this bit is set to 1, then the server SHOULD, for those 934 clients in the group that support the RESPONSES function, add a DR 935 request to a reply in each transaction (usually, but not necessarily 936 the LIC reply), and use the client's subsequent response for 937 calculating an (approximate) IP-network component to include in the 938 transaction's total response times. 940 If this bit is set to 0, then the server does not add a DR request 941 to any replies from the target SNA application. 943 If the excludeIpComponent(1) bit is set to 1, then this bit is 944 ignored by the server. 946 o average(3) - If this bit is set to 1, then the server SHOULD 947 calculate a sliding-window average for the collection, based on the 948 parameters specified for the group. 950 If this bit is set to 0, then an average is not calculated. In this 951 case the tn3270eRtExceeded and tn3270eRtOkay notifications are not 952 generated, even if the traps(5) bit is set to 1. 954 o buckets(4) - If this bit is set to 1, then the server SHOULD create 955 and increment response time buckets for the collection, based on the 956 parameters specified for the group. 958 If this bit is set to 0, then response time buckets are not created. 960 o traps(5) - If this bit is set to 1, then a TN3270E Server is enabled 961 to generate notifications pertaining to an tn3270eCollCtlEntry. 962 tn3270CollStart and tn3270CollEnd generation is enabled simply by 963 traps(5) being set to 1. tn3270eRtExceeded and tn3270eRtOkay 964 generation enablement requires that average(3) be set to 1 in 965 addition to the traps(5) requirement. 967 If traps(5) is set to 0, then none of the notifications defined in 968 this MIB are generated for a particular tn3270eRtCollCtlEntry. 970 Either the average(3) or the buckets(4) bit MUST be set to 1 in order 971 for response time data collection to occur; both bits MAY be set to 1. 972 If the average(3) bit is set to 1, then the following objects have 973 meaning, and are used to control the calculation of the averages, as 974 well as the generation of the two notifications related to them: 976 o tn3270eRtCollCtlSPeriod 977 o tn3270eRtCollCtlSPMult 978 o tn3270eRtCollCtlThreshHigh 979 o tn3270eRtCollCtlThreshLow 980 o tn3270eRtCollCtlIdleCount 982 The previous objects' values are meaningless if the associated 983 average(3) bit is not set to 1. 985 If the buckets(4) bit is set to 1, then the following objects have 986 meaning, and specify the bucket boundaries: 988 o tn3270eRtCollCtlBucketBndry1 989 o tn3270eRtCollCtlBucketBndry2 990 o tn3270eRtCollCtlBucketBndry3 991 o tn3270eRtCollCtlBucketBndry4 993 The previous objects' values are meaningless if the associated 994 buckets(4) bit is not set to 1. 996 If an entry in the tn3270RtCollCtlTable has the value active(1) for its 997 RowStatus, then an implementation SHALL NOT allow Set operations for any 998 objects in the entry except: 1000 o tn3270eRtCollCtlThreshHigh 1001 o tn3270eRtCollCtlThreshLow 1002 o tn3270eRtCollCtlRowStatus 1003 4.2 tn3270eRtDataTable 1005 Either a single entry or multiple entries are created in the 1006 tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on whether 1007 tn3270eRtCollCtlType in the control entry has aggregate(0) selected. 1008 The contents of an entry in the tn3270eRtDataTable depend on the 1009 contents of the corresponding entry in the tn3270eRtCollCtlTable: as 1010 described above, some objects in the data entry return meaningful values 1011 only when the average(3) option is selected in the control entry, while 1012 others return meaningful values only when the buckets(4) option is 1013 selected. If both options are selected, then all the objects return 1014 meaningful values. When an object is not specified to return a 1015 meaningful value, an implementation may return any syntactically valid 1016 value in response to a Get operation. 1018 The following objects return meaningful values if and only if the 1019 average(3) option was selected in the corresponding 1020 tn3270eRtCollCtlEntry: 1022 o tn3270eRtDataAvgRt 1023 o tn3270eRtDataAvgIpRt 1024 o tn3270eRtDataAvgCountTrans 1025 o tn3270eRtDataIntTimeStamp 1026 o tn3270eRtDataTotalRts 1027 o tn3270eRtDataTotalIpRts 1028 o tn3270eRtDataCountTrans 1029 o tn3270eRtDataCountDrs 1030 o tn3270eRtDataElapsRndTrpSq 1031 o tn3270eRtDataElapsIpRtSq 1033 The first three objects in this list return values derived from the 1034 sliding-window average calculations described earlier. The time of the 1035 most recent sample for these calculations is returned in the 1036 tn3270eRtDataIntTimeStamp object. The next four objects are normal 1037 Counter32 objects, maintaining counts of total response time and total 1038 transactions. The last two objects return sum of the squares values, to 1039 enable variance calculations by a management application. 1041 The following objects return meaningful values if and only if the 1042 buckets(4) option was selected in the corresponding 1043 tn3270eRtCollCtlEntry: 1045 o tn3270eRtDataBucket1Rts 1046 o tn3270eRtDataBucket2Rts 1047 o tn3270eRtDataBucket3Rts 1048 o tn3270eRtDataBucket4Rts 1049 o tn3270eRtDataBucket5Rts 1051 A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by a 1052 management application to detect when the values of the counter objects 1053 in this table may have been reset, or otherwise experienced a 1054 discontinuity. A possible cause for such a discontinuity is the TN3270E 1055 server's being stopped or restarted. This object returns a meaningful 1056 value regardless of which collection control options were selected. 1058 An object, tn3270eRtDataRtMethod, identifies whether the IP Network Time 1059 was calculated using either the definite response or TIMEMARK approach. 1061 When an entry is created in the tn3270eRtCollCtlTable with its 1062 tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is 1063 automatically created in the tn3270eRtDataTable; this entry's 1064 tn3270eRtDataClientAddress has the value of a zero-length octet string, 1065 and its tn3270eRtDataClientAddrType has the value of unknown(0). 1067 When an entry is created in the tn3270eRtCollCtlTable with its 1068 tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is 1069 created in the tn3270eRtDataTable for each member of the client group 1070 that currently has a session with the TN3270E server. Entries are 1071 subsequently created for clients that the TN3270E server determines to 1072 be members of the client group when these clients establish sessions 1073 with the server. Entries are also created when clients with existing 1074 sessions are added to the group. 1076 All entries associated with a tn3270eRtCollCtlEntry are deleted from the 1077 tn3270eRtDataTable when that entry is deleted from the 1078 tn3270eRtCollCtlTable. An entry for an individual client in a client 1079 group is deleted when its TCP connection terminates. Once it has been 1080 created, a client's entry in the tn3270eRtDataTable remains active as 1081 long as the collection's tn3270eRtCollCtlEntry exists, even if the 1082 client is removed from the client group for the tn3270eRtCollCtlEntry. 1084 4.3 Notifications 1086 This MIB defines four notifications related to a tn3270eRtDataEntry. If 1087 the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1, 1088 then the tn3270RtCollStart and tn3270RtCollEnd notifications are 1089 generated when, respsectively, the tn3270eRtDataEntry is created and 1090 deleted. If, in addition, this tn3270eRtCollCtlType object's average(3) 1091 bit is set to 1, then the the tn3270eRtExceeded and tn3270eRtOkay 1092 notifications are generated when the conditions they report occur. 1094 The following notifications are defined by this MIB: 1096 o tn3270eRtExceeded - The purpose of this notification is to signal 1097 that a performance problem has been detected. If average(3) 1098 response time data is being collected, then this notification is 1099 generated whenever (1) an average response time is first found, on a 1100 collection interval boundary, to have exceeded the high threshold 1101 tn3270eRtCollCtlThreshHigh specified for the client group, AND (2) 1102 the sample on which the average is based is determined to have been 1103 a significant one, via the significance algorithm described earlier. 1104 This notification is not generated again for a tn3270eRtDataEntry 1105 until an average response time falling below the low threshold 1106 tn3270eRtCollCtlThreshLow specified for the client group has 1107 occurred for the entry. 1109 o tn3270eRtOkay - The purpose of this notification is to signal that a 1110 previously reported performance problem has been resolved. If 1111 average(3) response time data is being collected, then this 1112 notification is generated whenever (1) a tn3270eRtExceeded 1113 notification has already been generated, AND (2) an average response 1114 time is first found, on a collection interval boundary, to have 1115 fallen below the low threshold tn3270eRtCollCtlThreshLow specified 1116 for the client group. This notification is not generated again for 1117 a tn3270eRtDataEntry until an average response time exceeding the 1118 high threshold tn3270eRtCollCtlThreshHigh specified for the client 1119 group has occurred for the entry. 1121 Taken together, the two preceding notifications serve to minimize the 1122 generation of an excessive number of traps in the case of an average 1123 response time that oscillates about its high threshold. 1125 o tn3270eRtCollStart - This notification is generated whenever data 1126 collection begins for a client group, or when a new 1127 tn3270eRtDataEntry becomes active. The primary purpose of this 1128 notification is signal to a management application that a new client 1129 TCP session has been established, and to provide the IP-to-resource 1130 mapping for the session. This notification is not critical when 1131 average(3) data collection is not being performed for the client 1132 group. 1134 o tn3270eRtCollEnd - This notification is generated whenever a data 1135 collection ends. For an aggregate collection, this occurs when the 1136 corresponding tn3270eRtCollCtlEntry is deleted. For an individual 1137 collection, this occurs either when the tn3270eRtCollCtlEntry is 1138 deleted, or when the client's TCP connection terminates. The 1139 purpose of this notification is to enable a management application 1140 to complete a monitoring function that it was performing, by 1141 returning final values for the collection's data objects. 1143 4.4 Advisory Spin Lock Usage 1145 Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an advisory 1146 lock that allows cooperating TN3270E-RT-MIB applications to coordinate 1147 their use of the tn3270eRtCollCtlTable. When creating a new entry or 1148 altering an existing entry in the tn3270eRtCollCtlTable, an application 1149 SHOULD make use of tn3270eRtSpinLock to serialize application changes or 1150 additions. Since this is an advisory lock, its use by management 1151 applications SHALL NOT be not enforced by agents. Agents MUST, however, 1152 implement the tn3270eRtSpinLock object. 1154 5.0 Definitions 1156 TN3270E-RT-MIB DEFINITIONS ::= BEGIN 1158 IMPORTS 1159 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 1160 Counter32, Unsigned32, Gauge32 1161 FROM SNMPv2-SMI 1162 RowStatus, DateAndTime, TimeStamp, TestAndIncr 1163 FROM SNMPv2-TC 1164 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1165 FROM SNMPv2-CONF 1166 Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex, 1167 tn3270eClientGroupName, tn3270eResMapElementType 1168 FROM TN3270E-MIB 1169 snanauMIB 1170 FROM SNA-NAU-MIB; 1172 tn3270eRtMIB MODULE-IDENTITY 1173 LAST-UPDATED "9804300000Z" -- April 30, 1998 1174 ORGANIZATION "TN3270E Working Group" 1175 CONTACT-INFO 1176 "Kenneth White (kennethw@vnet.ibm.com) 1177 IBM Corp. - Dept. BRQA/Bldg. 501/G114 1178 P.O. Box 12195 1179 3039 Cornwallis 1180 RTP, NC 27709-2195 1182 Robert Moore (remoore@us.ibm.com) 1183 IBM Corp. - Dept. BRQA/Bldg. 501/G114 1184 P.O. Box 12195 1185 3039 Cornwallis 1186 RTP, NC 27709-2195 1187 (919) 254-4436" 1188 DESCRIPTION 1189 "This module defines a portion of the management 1190 information base (MIB) that enables monitoring of 1191 TN3270 and TN3270E clients' response times by a 1192 TN3270E server." 1193 ::= { snanauMIB 9 } 1194 -- snanauMIB ::= { mib-2 34 } 1196 -- Top level structure of the MIB 1198 tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 } 1199 tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 } 1200 tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 } 1202 -- MIB Objects 1204 -- Response Time Control Table 1206 tn3270eRtCollCtlTable OBJECT-TYPE 1207 SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry 1208 MAX-ACCESS not-accessible 1209 STATUS current 1210 DESCRIPTION 1211 "The response time monitoring collection control table, 1212 which allows a management application to control the 1213 types of response time data being collected, and the 1214 clients for which it is being collected. 1216 This table is indexed by tn3270eSrvrConfIndex and 1217 tn3270eClientGroupName imported from the 1218 TN3270E-MIB. tn3270eSrvrConfIndex indicates within 1219 a host which TN3270E server an entry applies to. 1220 tn3270eClientGroupName it identifies the set of IP 1221 clients for which response time data is being collected. 1223 The particular IP clients making up the set are identified 1224 in the tn3270eClientGroupTable in the TN3270E-MIB." 1225 ::= { tn3270eRtObjects 1} 1227 tn3270eRtCollCtlEntry OBJECT-TYPE 1228 SYNTAX Tn3270eRtCollCtlEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "An entry in the TN3270E response time monitoring collection 1233 control table. To handle the case of multiple TN3270E 1234 servers on the same host, the first index of this table is 1235 the tn3270eSrvrConfIndex from the TN3270E-MIB." 1236 INDEX { 1237 tn3270eSrvrConfIndex, -- Server's index 1238 tn3270eClientGroupName } -- What to collect on 1239 ::= { tn3270eRtCollCtlTable 1 } 1241 Tn3270eRtCollCtlEntry ::= SEQUENCE { 1242 tn3270eRtCollCtlType BITS, 1243 tn3270eRtCollCtlSPeriod Unsigned32, 1244 tn3270eRtCollCtlSPMult Unsigned32, 1245 tn3270eRtCollCtlThreshHigh Unsigned32, 1246 tn3270eRtCollCtlThreshLow Unsigned32, 1247 tn3270eRtCollCtlIdleRate Unsigned32, 1248 tn3270eRtCollCtlBucketBndry1 Unsigned32, 1249 tn3270eRtCollCtlBucketBndry2 Unsigned32, 1250 tn3270eRtCollCtlBucketBndry3 Unsigned32, 1251 tn3270eRtCollCtlBucketBndry4 Unsigned32, 1252 tn3270eRtCollCtlRowStatus RowStatus } 1254 -- The OID { tn3270eRtCollCtlEntry 1 } is not used 1256 tn3270eRtCollCtlType OBJECT-TYPE 1257 SYNTAX BITS { 1258 aggregate(0), 1259 excludeIpComponent(1), 1260 ddr(2), 1261 average(3), 1262 buckets(4), 1263 traps(5) 1264 } 1265 MAX-ACCESS read-create 1266 STATUS current 1267 DESCRIPTION 1268 "This object controls what types of response time data to 1269 collect, whether to summarize the data across the members 1270 of a client group or keep it individually, whether to 1271 introduce dynamic definite responses, and whether to 1272 generate traps. 1274 aggregate(0) - Aggregate response time data for 1275 the client group as a whole. If 1276 this bit is set to 0, then 1277 maintain response time data 1278 separately for each member of the 1279 client group. 1280 excludeIpComponent(1) - Do not include the IP-network 1281 component in any response times. 1282 ddr(2) - Enable dynamic definite response. 1283 average(3) - Produce an average response time 1284 based on a specified collection 1285 interval. 1286 buckets(4) - Maintain tn3270eRtDataBucket values 1287 in an corresponding 1288 tn3270eRtDataEntry, based on the 1289 bucket boundaries specified in the 1290 tn3270eRtDataBucketBndry objects. 1291 traps(5) - generate the traps specified in 1292 this MIB module. The 1293 tn3270eRtExceeded and 1294 tn3270eRtOkay are generated 1295 only if average(3) is also 1296 specified." 1297 ::= { tn3270eRtCollCtlEntry 2 } 1299 tn3270eRtCollCtlSPeriod OBJECT-TYPE 1300 SYNTAX Unsigned32 (15..86400) -- 15 second min, 24 hour max 1301 UNITS "seconds" 1302 MAX-ACCESS read-create 1303 STATUS current 1304 DESCRIPTION 1305 "The number of seconds that defines the sample period. 1306 The actual interval is defined as tn3270eRtCollCtlSPeriod 1307 times tn3270eRtCollCtlSPMult. 1309 The value of this object is used only if the corresponding 1310 tn3270eRtCollCtlType has the average(3) setting." 1311 DEFVAL {20} -- 20 seconds 1312 ::= { tn3270eRtCollCtlEntry 3 } 1314 tn3270eRtCollCtlSPMult OBJECT-TYPE 1315 SYNTAX Unsigned32 (1..5760) -- 5760 x SPeriod of 15 is 24 hours 1316 UNITS "period" 1317 MAX-ACCESS read-create 1318 STATUS current 1319 DESCRIPTION 1320 "The sample period multiplier; this value is multiplied by 1321 the sample period, tn3270eRtCollCtlSPeriod, to determine 1322 the collection interval. 1324 Sliding-window average calculation can, if necessary, be 1325 disabled, by setting the sample period multiplier, 1326 tn3270eRtCollCtlSPMult, to 1, and setting the sample 1327 period, tn3270eRtCollCtlSPeriod, to the required 1328 collection interval. 1330 The value of this object is used only if the corresponding 1331 tn3270eRtCollCtlType has the average(3) setting." 1332 DEFVAL { 30 } -- yields an interval of 10 minutes when 1333 -- used with the default SPeriod value 1334 ::= { tn3270eRtCollCtlEntry 4 } 1336 tn3270eRtCollCtlThreshHigh OBJECT-TYPE 1337 SYNTAX Unsigned32 1338 UNITS "seconds" 1339 MAX-ACCESS read-create 1340 STATUS current 1341 DESCRIPTION 1342 "The threshold for generating a tn3270eRtExceeded 1343 notification, signalling that a monitored total response 1344 time has exceeded the specified limit. A value of zero 1345 for this object suppresses generation of this notification. 1346 The value of this object is used only if the corresponding 1347 tn3270eRtCollCtlType has average(3) and traps(5) selected." 1348 DEFVAL { 0 } -- suppress notifications 1349 ::= { tn3270eRtCollCtlEntry 5 } 1351 tn3270eRtCollCtlThreshLow OBJECT-TYPE 1352 SYNTAX Unsigned32 1353 UNITS "seconds" 1354 MAX-ACCESS read-create 1355 STATUS current 1356 DESCRIPTION 1357 "The threshold for generating a tn3270eRtOkay notification, 1358 signalling that a monitored total response time has fallen 1359 below the specified limit. A value of zero for this object 1360 suppresses generation of this notification. The value of 1361 this object is used only if the corresponding 1362 tn3270eRtCollCtlType has average(3) and traps(5) selected." 1363 DEFVAL { 0 } -- suppress notifications 1364 ::= { tn3270eRtCollCtlEntry 6 } 1366 tn3270eRtCollCtlIdleRate OBJECT-TYPE 1367 SYNTAX Unsigned32 1368 UNITS "transactions" 1369 MAX-ACCESS read-create 1370 STATUS current 1371 DESCRIPTION 1372 "The value of this object is used to determine whether a 1373 sample that yields an average response time exceeding the 1374 value of tn3270eRtCollCtlThreshHigh was a statistically 1375 valid one. If the following statement is true, then the 1376 sample was statistically valid, and so a tn3270eRtExceeded 1377 notification should be generated: 1379 AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 1381 This comparison is done only if the corresponding 1382 tn3270eRtCollCtlType has average(3) and traps(5) selected." 1383 DEFVAL { 1 } 1384 ::= { tn3270eRtCollCtlEntry 7 } 1386 tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE 1387 SYNTAX Unsigned32 1388 UNITS "tenths of seconds" 1389 MAX-ACCESS read-create 1390 STATUS current 1391 DESCRIPTION 1392 "The value of this object defines the range of transaction 1393 response times counted in the Tn3270eRtDataBucket1Rts 1394 object: those less than or equal to this value." 1395 DEFVAL { 10 } 1396 ::= { tn3270eRtCollCtlEntry 8 } 1398 tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE 1399 SYNTAX Unsigned32 1400 UNITS "tenths of seconds" 1401 MAX-ACCESS read-create 1402 STATUS current 1403 DESCRIPTION 1404 "The value of this object, together with that of the 1405 tn3270eRtCollCtlBucketBndry1 object, defines the range 1406 of transaction response times counted in the 1407 Tn3270eRtDataBucket2Rts object: those greater than the 1408 value of the tn3270eRtCollCtlBucketBndry1 object, and 1409 less than or equal to the value of this object." 1410 DEFVAL { 20 } 1411 ::= { tn3270eRtCollCtlEntry 9 } 1413 tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE 1414 SYNTAX Unsigned32 1415 UNITS "tenths of seconds" 1416 MAX-ACCESS read-create 1417 STATUS current 1418 DESCRIPTION 1419 "The value of this object, together with that of the 1420 tn3270eRtCollCtlBucketBndry2 object, defines the range of 1421 transaction response times counted in the 1422 Tn3270eRtDataBucket3Rts object: those greater than the 1423 value of the tn3270eRtCollCtlBucketBndry2 object, and less 1424 than or equal to the value of this object." 1425 DEFVAL { 50 } 1426 ::= { tn3270eRtCollCtlEntry 10 } 1428 tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE 1429 SYNTAX Unsigned32 1430 UNITS "tenths of seconds" 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "The value of this object, together with that of the 1435 tn3270eRtCollCtlBucketBndry3 object, defines the range 1436 of transaction response times counted in the 1437 Tn3270eRtDataBucket4Rts object: those greater than the 1438 value of the tn3270eRtCollCtlBucketBndry3 object, and 1439 less than or equal to the value of this object. 1441 The value of this object also defines the range of 1442 transaction response times counted in the 1443 Tn3270eRtDataBucket5Rts object: those greater than the 1444 value of this object." 1445 DEFVAL { 100 } 1446 ::= { tn3270eRtCollCtlEntry 11 } 1448 tn3270eRtCollCtlRowStatus OBJECT-TYPE 1449 SYNTAX RowStatus 1450 MAX-ACCESS read-create 1451 STATUS current 1452 DESCRIPTION 1453 "This object allows entries to be created and deleted 1454 in the tn3270eRtCollCtlTable. An entry in this table 1455 is deleted by setting this object to destroy(6). 1456 Deleting an entry in this table has the side-effect 1457 of removing all entries from the tn3270eRtDataTable 1458 that are associated with the entry being deleted." 1459 ::= { tn3270eRtCollCtlEntry 12 } 1461 -- TN3270E Response Time Data Table 1463 tn3270eRtDataTable OBJECT-TYPE 1464 SYNTAX SEQUENCE OF Tn3270eRtDataEntry 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "The response time data table. Entries in this table are 1469 created based on entries in the tn3270eRtCollCtlTable." 1470 ::= { tn3270eRtObjects 2 } 1472 tn3270eRtDataEntry OBJECT-TYPE 1473 SYNTAX Tn3270eRtDataEntry 1474 MAX-ACCESS not-accessible 1475 STATUS current 1476 DESCRIPTION 1477 "An entry in this table is created based upon the 1478 tn3270eRtCollCtlTable. A single entry is created with 1479 a tn3270eRtDataClientAddrType of unknown(0) and a 1480 zero-length octet string value for 1481 tn3270eRtDataClientAddress when the corresponding 1482 tn3270eRtCollCtlType has aggregate(0) specified. 1483 When aggregate(0) is not specified, then a separate 1484 entry is created for each client in the group. 1486 Note that the following objects defined within an 1487 entry in this table can wrap: 1488 tn3270eRtDataTotalRts 1489 tn3270eRtDataTotalIpRts 1490 tn3270eRtDataCountTrans 1491 tn3270eRtDataCountDrs 1492 tn3270eRtDataElapsRnTrpSq 1493 tn3270eRtDataElapsIpRtSq 1494 tn3270eRtDataBucket1Rts 1495 tn3270eRtDataBucket2Rts 1496 tn3270eRtDataBucket3Rts 1497 tn3270eRtDataBucket4Rts 1498 tn3270eRtDataBucket5Rts" 1499 INDEX { 1500 tn3270eSrvrConfIndex, -- Server's local index 1501 tn3270eClientGroupName, -- Collection target 1502 tn3270eRtDataClientAddrType, 1503 tn3270eRtDataClientAddress } 1504 ::= { tn3270eRtDataTable 1 } 1506 Tn3270eRtDataEntry ::= SEQUENCE { 1507 tn3270eRtDataClientAddrType Tn3270eAddrType, 1508 tn3270eRtDataClientAddress Tn3270eTAddress, 1509 tn3270eRtDataDiscontinuityTime TimeStamp, 1510 tn3270eRtDataAvgRt Gauge32, 1511 tn3270eRtDataAvgIpRt Gauge32, 1512 tn3270eRtDataAvgCountTrans Gauge32, 1513 tn3270eRtDataIntTimeStamp DateAndTime, 1514 tn3270eRtDataTotalRts Counter32, 1515 tn3270eRtDataTotalIpRts Counter32, 1516 tn3270eRtDataCountTrans Counter32, 1517 tn3270eRtDataCountDrs Counter32, 1518 tn3270eRtDataElapsRndTrpSq Unsigned32, 1519 tn3270eRtDataElapsIpRtSq Unsigned32, 1520 tn3270eRtDataBucket1Rts Counter32, 1521 tn3270eRtDataBucket2Rts Counter32, 1522 tn3270eRtDataBucket3Rts Counter32, 1523 tn3270eRtDataBucket4Rts Counter32, 1524 tn3270eRtDataBucket5Rts Counter32, 1525 tn3270eRtDataRtMethod INTEGER 1526 } 1528 tn3270eRtDataClientAddrType OBJECT-TYPE 1529 SYNTAX Tn3270eAddrType 1530 MAX-ACCESS not-accessible 1531 STATUS current 1532 DESCRIPTION 1533 "Indicates the type of address represented by 1534 the value of tn3270eRtDataClientAddress." 1535 ::= { tn3270eRtDataEntry 1 } 1537 tn3270eRtDataClientAddress OBJECT-TYPE 1538 SYNTAX Tn3270eTAddress 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "Contains the IP address of the TN3270 client being 1543 monitored. A zero-length octet string is used if 1544 aggregate data is being collected for the client group." 1545 ::= { tn3270eRtDataEntry 2 } 1547 tn3270eRtDataDiscontinuityTime OBJECT-TYPE 1548 SYNTAX TimeStamp 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The value of sysUpTime on the most recent occasion at 1553 which one or more of this entry's counter objects 1554 suffered a discontinuity. This may happen if a TN3270E 1555 server is stopped and then restarted, and local methods 1556 are used to set up collection policy 1557 (tn3270eRtCollCtlTable entries)." 1558 ::= { tn3270eRtDataEntry 3 } 1560 tn3270eRtDataAvgRt OBJECT-TYPE 1561 SYNTAX Gauge32 1562 UNITS "tenths of seconds" 1563 MAX-ACCESS read-only 1564 STATUS current 1565 DESCRIPTION 1566 "The average total response time measured over the last 1567 collection interval." 1568 DEFVAL { 0 } 1569 ::= { tn3270eRtDataEntry 4 } 1571 tn3270eRtDataAvgIpRt OBJECT-TYPE 1572 SYNTAX Gauge32 1573 UNITS "tenths of seconds" 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "The average IP response time measured over the last 1578 collection interval." 1579 DEFVAL { 0 } 1580 ::= { tn3270eRtDataEntry 5 } 1582 tn3270eRtDataAvgCountTrans OBJECT-TYPE 1583 SYNTAX Gauge32 1584 UNITS "transactions" 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "The sliding transaction count used for calculating the 1589 values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt 1590 objects. The actual transaction count is available in 1591 the tn3270eRtDataCountTrans object. 1593 The initial value of this object, before any averages have 1594 been calculated, is 0." 1595 ::= { tn3270eRtDataEntry 6 } 1597 tn3270eRtDataIntTimeStamp OBJECT-TYPE 1598 SYNTAX DateAndTime 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "The date and time of the last interval that 1603 tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and 1604 tn3270eRtDataAvgCountTrans were calculated. 1606 Prior to the calculation of the first interval 1607 averages, this object returns the value 1608 0x0000000000000000000000. When this value is 1609 returned, the remaining objects in the entry have 1610 no significance." 1611 ::= { tn3270eRtDataEntry 7 } 1613 tn3270eRtDataTotalRts OBJECT-TYPE 1614 SYNTAX Counter32 1615 UNITS "tenths of seconds" 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "The count of the total response times collected. 1621 A management application can detect discontinuities in this 1622 counter by monitoring the tn3270eRtDataDiscontinuityTime 1623 object." 1624 ::= { tn3270eRtDataEntry 8 } 1626 tn3270eRtDataTotalIpRts OBJECT-TYPE 1627 SYNTAX Counter32 1628 UNITS "tenths of seconds" 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "The count of the total IP-network response times 1633 collected. 1635 A management application can detect discontinuities in this 1636 counter by monitoring the tn3270eRtDataDiscontinuityTime 1637 object." 1638 ::= { tn3270eRtDataEntry 9 } 1640 tn3270eRtDataCountTrans OBJECT-TYPE 1641 SYNTAX Counter32 1642 UNITS "transactions" 1643 MAX-ACCESS read-only 1644 STATUS current 1645 DESCRIPTION 1646 "The count of the total number of transactions detected. 1648 A management application can detect discontinuities in this 1649 counter by monitoring the tn3270eRtDataDiscontinuityTime 1650 object." 1651 ::= { tn3270eRtDataEntry 10 } 1653 tn3270eRtDataCountDrs OBJECT-TYPE 1654 SYNTAX Counter32 1655 UNITS "definite responses" 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The count of the total number of definite responses 1660 detected. 1662 A management application can detect discontinuities in this 1663 counter by monitoring the tn3270eRtDataDiscontinuityTime 1664 object." 1665 ::= { tn3270eRtDataEntry 11 } 1667 tn3270eRtDataElapsRndTrpSq OBJECT-TYPE 1668 SYNTAX Unsigned32 1669 UNITS "tenths of seconds squared" 1670 MAX-ACCESS read-only 1671 STATUS current 1672 DESCRIPTION 1673 "The sum of the elapsed round trip time squared. The sum 1674 of the squares is keep in order to enable calculation of 1675 a variance." 1676 DEFVAL { 0 } 1677 ::= { tn3270eRtDataEntry 12 } 1679 tn3270eRtDataElapsIpRtSq OBJECT-TYPE 1680 SYNTAX Unsigned32 1681 UNITS "tenths of seconds squared" 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "The sum of the elapsed IP round trip time squared. 1686 The sum of the squares is keep in order to enable 1687 calculation of a variance." 1688 DEFVAL { 0 } 1689 ::= { tn3270eRtDataEntry 13 } 1691 tn3270eRtDataBucket1Rts OBJECT-TYPE 1692 SYNTAX Counter32 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "The count of the response times falling into bucket 1. 1698 A management application can detect discontinuities in this 1699 counter by monitoring the tn3270eRtDataDiscontinuityTime 1700 object." 1701 ::= { tn3270eRtDataEntry 14 } 1703 tn3270eRtDataBucket2Rts OBJECT-TYPE 1704 SYNTAX Counter32 1705 MAX-ACCESS read-only 1706 STATUS current 1707 DESCRIPTION 1708 "The count of the response times falling into bucket 2. 1710 A management application can detect discontinuities in this 1711 counter by monitoring the tn3270eRtDataDiscontinuityTime 1712 object." 1713 ::= { tn3270eRtDataEntry 15 } 1715 tn3270eRtDataBucket3Rts OBJECT-TYPE 1716 SYNTAX Counter32 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "The count of the response times falling into bucket 3. 1722 A management application can detect discontinuities in this 1723 counter by monitoring the tn3270eRtDataDiscontinuityTime 1724 object." 1725 ::= { tn3270eRtDataEntry 16 } 1727 tn3270eRtDataBucket4Rts OBJECT-TYPE 1728 SYNTAX Counter32 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "The count of the response times falling into bucket 4. 1734 A management application can detect discontinuities in this 1735 counter by monitoring the tn3270eRtDataDiscontinuityTime 1736 object." 1737 ::= { tn3270eRtDataEntry 17 } 1739 tn3270eRtDataBucket5Rts OBJECT-TYPE 1740 SYNTAX Counter32 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "The count of the response times falling into bucket 5. 1746 A management application can detect discontinuities in this 1747 counter by monitoring the tn3270eRtDataDiscontinuityTime 1748 object." 1749 ::= { tn3270eRtDataEntry 18 } 1751 tn3270eRtDataRtMethod OBJECT-TYPE 1752 SYNTAX INTEGER { 1753 none(0), 1754 responses(1), 1755 timemark(2) 1756 } 1757 MAX-ACCESS read-only 1758 STATUS current 1759 DESCRIPTION 1760 "The value of this object indicates the method that was 1761 used in calculating the IP network time. 1763 The value 'none(0) indicates that response times were not 1764 calculated for the IP network." 1765 ::= { tn3270eRtDataEntry 19 } 1767 tn3270eRtSpinLock OBJECT-TYPE 1768 SYNTAX TestAndIncr 1769 MAX-ACCESS read-write 1770 STATUS current 1771 DESCRIPTION 1772 "An advisory lock used to allow cooperating TN3270E-RT-MIB 1773 applications to coordinate their use of the 1774 tn3270eRtCollCtlTable. 1776 When creating a new entry or altering an existing entry 1777 in the tn3270eRtCollCtlTable, an application should make 1778 use of tn3270eRtSpinLock to serialize application changes 1779 or additions. 1781 Since this is an advisory lock, the use of this lock is 1782 not enforced." 1783 ::= { tn3270eRtObjects 3 } 1785 -- Notifications 1787 tn3270eRtExceeded NOTIFICATION-TYPE 1788 OBJECTS { 1789 tn3270eRtDataIntTimeStamp, 1790 tn3270eRtDataAvgRt, 1791 tn3270eRtDataAvgIpRt, 1792 tn3270eRtDataAvgCountTrans, 1793 tn3270eRtDataRtMethod 1794 } 1795 STATUS current 1796 DESCRIPTION 1797 "This notification is generated when the average response 1798 time, tn3270eRtDataAvgRt, exceeds 1799 tn3270eRtCollCtlThresholdHigh at the end of a collection 1800 interval specified by tn3270eCollCtlSPeriod 1801 times tn3270eCollCtlSPMult. Note that the corresponding 1802 tn3270eCollCtlType must have traps(5) and average(3) set 1803 for this notification to be generated. In addition, 1804 tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and 1805 tn3270eRtDataAvgRt are algorithmically compared to 1806 tn3270eRtCollCtlIdleRate for determination if this 1807 notification will be suppressed." 1808 ::= { tn3270eRtNotifications 1 } 1810 tn3270eRtOkay NOTIFICATION-TYPE 1811 OBJECTS { 1812 tn3270eRtDataIntTimeStamp, 1813 tn3270eRtDataAvgRt, 1814 tn3270eRtDataAvgIpRt, 1815 tn3270eRtDataAvgCountTrans, 1816 tn3270eRtDataRtMethod 1817 } 1818 STATUS current 1819 DESCRIPTION 1820 "This notification is generated when the average response 1821 time, tn3270eRtDataAvgRt, falls below 1822 tn3270eRtCollCtlThresholdLow at the end of a collection 1823 interval specified by tn3270eCollCtlSPeriod times 1824 tn3270eCollCtlSPMult, after a tn3270eRtExceeded 1825 notification was generated. Note that the corresponding 1826 tn3270eCollCtlType must have traps(5) and average(3) 1827 set for this notification to be generated." 1828 ::= { tn3270eRtNotifications 2 } 1830 tn3270eRtCollStart NOTIFICATION-TYPE 1831 OBJECTS { 1832 tn3270eRtDataRtMethod, -- type of collection 1833 tn3270eResMapElementType -- type of resource 1834 } 1835 STATUS current 1836 DESCRIPTION 1837 "This notification is generated when response time data 1838 collection is enabled for a member of a client group. 1839 In order for this notification to occur the corresponding 1840 tn3270eRtCollCtlType must have traps(5) selected. 1842 tn3270eResMapElementType contains a valid value only if 1843 tn3270eRtDataClientAddress contains a valid address 1844 (rather than a zero-length octet string)." 1845 ::= { tn3270eRtNotifications 3 } 1847 tn3270eRtCollEnd NOTIFICATION-TYPE 1848 OBJECTS { 1849 tn3270eRtDataDiscontinuityTime, 1850 tn3270eRtDataAvgRt, 1851 tn3270eRtDataAvgIpRt, 1852 tn3270eRtDataAvgCountTrans, 1853 tn3270eRtDataIntTimeStamp, 1854 tn3270eRtDataTotalRts, 1855 tn3270eRtDataTotalIpRts, 1856 tn3270eRtDataCountTrans, 1857 tn3270eRtDataCountDrs, 1858 tn3270eRtDataElapsRndTrpSq, 1859 tn3270eRtDataElapsIpRtSq, 1860 tn3270eRtDataBucket1Rts, 1861 tn3270eRtDataBucket2Rts, 1862 tn3270eRtDataBucket3Rts, 1863 tn3270eRtDataBucket4Rts, 1864 tn3270eRtDataBucket5Rts, 1865 tn3270eRtDataRtMethod 1866 } 1867 STATUS current 1868 DESCRIPTION 1869 "This notification is generated when an tn3270eRtDataEntry 1870 is deleted after being active (actual data collected), in 1871 order to enable a management application monitoring an 1872 tn3270eRtDataEntry to get the entry's final values. Note 1873 that the corresponding tn3270eCollCtlType must have traps(5) 1874 set for this notification to be generated." 1875 ::= { tn3270eRtNotifications 4 } 1877 -- Conformance Statement 1879 tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 } 1880 tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 } 1881 -- Compliance statements 1883 tn3270eRtCompliance MODULE-COMPLIANCE 1884 STATUS current 1885 DESCRIPTION 1886 "The compliance statement for agents that support the 1887 TN327E-RT-MIB." 1888 MODULE -- this module 1889 MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup } 1891 OBJECT tn3270eRtCollCtlType 1892 MIN-ACCESS read-only 1893 DESCRIPTION 1894 "The agent is not required to support a SET operation to 1895 this object in the absence of adequate security." 1897 OBJECT tn3270eRtCollCtlSPeriod 1898 MIN-ACCESS read-only 1899 DESCRIPTION 1900 "The agent is not required to allow the user to change 1901 the default value of this object, and is allowed to 1902 use a different default." 1904 OBJECT tn3270eRtCollCtlSPMult 1905 MIN-ACCESS read-only 1906 DESCRIPTION 1907 "The agent is not required to support a SET operation 1908 to this object in the absence of adequate security." 1910 OBJECT tn3270eRtCollCtlThreshHigh 1911 MIN-ACCESS read-only 1912 DESCRIPTION 1913 "The agent is not required to support a SET operation 1914 to this object in the absence of adequate security." 1916 OBJECT tn3270eRtCollCtlThreshLow 1917 MIN-ACCESS read-only 1918 DESCRIPTION 1919 "The agent is not required to support a SET operation 1920 to this object in the absence of adequate security." 1922 OBJECT tn3270eRtCollCtlIdleRate 1923 MIN-ACCESS read-only 1924 DESCRIPTION 1925 "The agent is not required to support a SET operation 1926 to this object in the absence of adequate security." 1928 OBJECT tn3270eRtCollCtlBucketBndry1 1929 MIN-ACCESS read-only 1930 DESCRIPTION 1931 "The agent is not required to support a SET operation 1932 to this object in the absence of adequate security." 1934 OBJECT tn3270eRtCollCtlBucketBndry2 1935 MIN-ACCESS read-only 1936 DESCRIPTION 1937 "The agent is not required to support a SET operation 1938 to this object in the absence of adequate security." 1940 OBJECT tn3270eRtCollCtlBucketBndry3 1941 MIN-ACCESS read-only 1942 DESCRIPTION 1943 "The agent is not required to support a SET operation 1944 to this object in the absence of adequate security." 1946 OBJECT tn3270eRtCollCtlBucketBndry4 1947 MIN-ACCESS read-only 1948 DESCRIPTION 1949 "The agent is not required to support a SET operation 1950 to this object in the absence of adequate security." 1952 OBJECT tn3270eRtCollCtlRowStatus 1953 SYNTAX INTEGER { 1954 active(1) -- subset of RowStatus 1955 } 1956 MIN-ACCESS read-only 1957 DESCRIPTION 1958 "Write access is not required, and only one of the six 1959 enumerated values for the RowStatus textual convention 1960 need be supported, specifically: active(1)." 1962 ::= {tn3270eRtCompliances 1 } 1964 -- Group definitions 1966 tn3270eRtGroup OBJECT-GROUP 1967 OBJECTS { 1968 tn3270eRtCollCtlType, 1969 tn3270eRtCollCtlSPeriod, 1970 tn3270eRtCollCtlSPMult, 1971 tn3270eRtCollCtlThreshHigh, 1972 tn3270eRtCollCtlThreshLow, 1973 tn3270eRtCollCtlIdleRate, 1974 tn3270eRtCollCtlBucketBndry1, 1975 tn3270eRtCollCtlBucketBndry2, 1976 tn3270eRtCollCtlBucketBndry3, 1977 tn3270eRtCollCtlBucketBndry4, 1978 tn3270eRtCollCtlRowStatus, 1979 tn3270eRtDataDiscontinuityTime, 1980 tn3270eRtDataAvgRt, 1981 tn3270eRtDataAvgIpRt, 1982 tn3270eRtDataAvgCountTrans, 1983 tn3270eRtDataIntTimeStamp, 1984 tn3270eRtDataTotalRts, 1985 tn3270eRtDataTotalIpRts, 1986 tn3270eRtDataCountTrans, 1987 tn3270eRtDataCountDrs, 1988 tn3270eRtDataElapsRndTrpSq, 1989 tn3270eRtDataElapsIpRtSq, 1990 tn3270eRtDataBucket1Rts, 1991 tn3270eRtDataBucket2Rts, 1992 tn3270eRtDataBucket3Rts, 1993 tn3270eRtDataBucket4Rts, 1994 tn3270eRtDataBucket5Rts, 1995 tn3270eRtDataRtMethod, 1996 tn3270eRtSpinLock } 1997 STATUS current 1998 DESCRIPTION 1999 "This group is mandatory for all implementations that 2000 support the TN3270E-RT-MIB. " 2001 ::= { tn3270eRtGroups 1 } 2003 tn3270eRtNotGroup NOTIFICATION-GROUP 2004 NOTIFICATIONS { 2005 tn3270eRtExceeded, 2006 tn3270eRtOkay, 2007 tn3270eRtCollStart, 2008 tn3270eRtCollEnd 2009 } 2010 STATUS current 2011 DESCRIPTION 2012 "The notifications that must be supported when the 2013 TN3270E-RT-MIB is implemented. " 2014 ::= { tn3270eRtGroups 2 } 2016 END 2018 6.0 Security Considerations 2020 Certain management information defined in this MIB may be considered 2021 sensitive in some network environments. Therefore, authentication of 2022 received SNMP requests and controlled access to management information 2023 SHOULD be employed in such environments. An authentication protocol is 2024 defined in [10]. A protocol for access control is defined in [11]. 2026 Several objects in this MIB allow write access or provide for row 2027 creation. Allowing this support in a non-secure environment can have a 2028 negative effect on network operations. It is RECOMMENDED that 2029 implementers seriously consider whether set operations or row creation 2030 SHOULD be allowed without providing, at a minimum, authentication of 2031 request origin. It is RECOMMENDED that without such support that the 2032 following objects be implemented as read-only: 2034 o tn3270eRtCollCtlType 2035 o tn3270eRtCollCtlSPeriod 2036 o tn3270eRtCollCtlSPMult 2037 o tn3270eRtCollCtlThreshHigh 2038 o tn3270eRtCollCtlThreshLow 2039 o tn3270eRtCollCtlIdleCount 2040 o tn3270eRtCollCtlBucketBndry1 2041 o tn3270eRtCollCtlBucketBndry2 2042 o tn3270eRtCollCtlBucketBndry3 2043 o tn3270eRtCollCtlBucketBndry4 2044 o tn3270eRtCollCtlRowStatus 2045 The administrative method to use to create and manage the 2046 tn3270eRtCollCtlTable when SET support is not allowed is outside of the 2047 scope of this memo. 2049 7.0 Intellectual Property 2051 The IETF takes no position regarding the validity or scope of any 2052 intellectual property or other rights that might be claimed to pertain 2053 to the implementation or use of the technology described in this 2054 document or the extent to which any license under such rights might or 2055 might not be available; neither does it represent that it has made any 2056 effort to identify any such rights. Information on the IETF's 2057 procedures with respect to rights in standards-track and 2058 standards-related documentation can be found in BCP-11. Copies of 2059 claims of rights made available for publication and any assurances of 2060 licenses to be made available, or the result of an attempt made to 2061 obtain a general license or permission for the use of such proprietary 2062 rights by implementers or users of this specification can be obtained 2063 from the IETF Secretariat. 2065 The IETF invites any interested party to bring to its attention any 2066 copyrights, patents or patent applications, or other proprietary rights 2067 which may cover technology that may be required to practice this 2068 standard. Please address the information to the IETF Executive 2069 Director. 2071 8.0 Acknowledgments 2073 This document is a product of the TN3270E Working Group. Special thanks 2074 are due to Derek Bolton and Michael Boe of Cisco Systems for their 2075 numerous comments and suggestions for improving the structure of this 2076 MIB. Thanks also to Randy Presuhn of BMC Software for his valuable 2077 review comments on several versions of the document. 2079 9.0 References 2081 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2082 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2083 International, MIT Laboratory for Computer Science, May 1990. 2085 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2086 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2087 RFC 1213, Hughes LAN Systems, Performance Systems International, 2088 March 1991. 2090 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 2091 of Management Information for Version 2 of the Simple Network 2092 Management Protocol (SNMPv2)", RFC 1902, January 1996. 2094 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 2095 Conventions for Version 2 of the Simple Network Management Protocol 2096 (SNMPv2)", RFC 1903, January 1996. 2098 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2099 "Conformance Statements for Version 2 of the Simple Network 2100 Management Protocol (SNMPv2)", RFC 1904, January 1996. 2102 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 2103 Operations for Version 2 of the Simple Network Management Protocol 2104 (SNMPv2)", RFC 1905, January 1996. 2106 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 2107 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2108 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 2109 1998. 2111 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 2112 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2113 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 2114 Research, January 1998. 2116 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 2117 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2118 January 1998. 2120 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 2121 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2122 2274, IBM T. J. Watson Research, January 1998. 2124 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 2125 Model (VACM) for the Simple Network Management Protocol (SNMP)", 2126 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 2127 Systems, Inc., January 1998. 2129 [12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC 2130 854, May 1983. 2132 [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, 2133 May 1983. 2135 [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. 2137 [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. 2139 [16] White, K. and Moore, R., "Base Definitions of Managed Objects for 2140 TN3270E Using SMIv2", Internet-Draft Work in progress, April 1998. 2142 [17] IBM, International Technical Support Centers, "Response Time Data 2143 Gathering", GG24-3212-01, November 1990. 2145 [18] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 2146 Standards Process", BCP 11, RFC 2028, October 1996. 2148 [19] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2149 Levels", BCP 14, RFC 2119, March 1997. 2151 10.0 Authors' Addresses 2153 Kenneth D. White 2154 Dept. BRQA/Bldg. 501/G114 2155 IBM Corporation 2156 P.O.Box 12195 2157 3039 Cornwallis 2158 Research Triangle Park, NC 27709, USA 2159 E-mail: kennethw@vnet.ibm.com 2161 Robert Moore 2162 Dept. BRQA/Bldg. 501/G114 2163 IBM Corporation 2164 P.O.Box 12195 2165 3039 Cornwallis 2166 Research Triangle Park, NC 27709, USA 2167 Phone: +1-919-254-7507 2168 E-mail: remoore@us.ibm.com 2170 11.0 Full Copyright Statement 2172 Copyright (C) The Internet Society (1997). All Rights Reserved. 2174 This document and translations of it may be copied and furnished to 2175 others, and derivative works that comment on or otherwise explain it or 2176 assist in its implementation may be prepared, copied, published and 2177 distributed, in whole or in part, without restriction of any kind, 2178 provided that the above copyright notice and this paragraph are included 2179 on all such copies and derivative works. However, this document itself 2180 may not be modified in any way, such as by removing the copyright notice 2181 or references to the Internet Society or other Internet organizations, 2182 except as needed for the purpose of developing Internet standards in 2183 which case the procedures for copyrights defined in the Internet 2184 Standards process must be followed, or as required to translate it into 2185 languages other than English. 2187 The limited permissions granted above are perpetual and will not be 2188 revoked by the Internet Society or its successors or assigns. 2190 This document and the information contained herein is provided on an "AS 2191 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2192 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2193 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2194 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2195 FITNESS FOR A PARTICULAR PURPOSE.