idnits 2.17.1 draft-ietf-tn3270e-rt-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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 1 longer page, the longest (page 1) being 2516 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. ** There are 42 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([10]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (September 1997) is 9720 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: '2' is defined on line 2050, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 2057, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 2060, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1041 (ref. '4') ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '7') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1904 (ref. '8') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '9') -- Possible downref: Non-RFC (?) normative reference: ref. '10' ** Obsolete normative reference: RFC 1647 (ref. '11') (Obsoleted by RFC 2355) -- Possible downref: Non-RFC (?) normative reference: ref. '12' -- Possible downref: Non-RFC (?) normative reference: ref. '13' Summary: 17 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TN3270E Working Group 3 INTERNET DRAFT: Kenneth White 4 Expiration Date: September 1998 Robert Moore 5 IBM Corp. 7 September 1997 9 Definitions of Managed Objects for TN3270E 10 Response Time Collection Using SMIv2 11 (TN3270E-RT-MIB) 12 14 Status of this Memo 16 This document is an Internet Draft. Internet Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its Areas, 18 and its Working Groups. Note that other groups may also distribute 19 working documents as Internet Drafts. 21 Internet Drafts are draft documents valid for a maximum of six 22 months. Internet Drafts may be updated, replaced, or obsoleted by 23 other documents at any time. It is not appropriate to use Internet 24 Drafts as reference material or to cite them other than as a "working 25 draft" or "work in progress." 27 Please check the I-D abstract listing contained in each Internet 28 Draft directory to learn the current status of this or any Internet 29 Draft. Distribution of this document is unlimited. 31 Abstract 33 The purpose of this memo is to define the protocol and the Management 34 Information Base (MIB) for performing response time data collection 35 on TN3270 and TN3270E 36 sessions by a TN3270E Server. The response time data 37 collected by a TN3270E Server is structured to support both validation 38 of service level agreements and performance monitoring of 39 TN3270 and TN3270E 40 Sessions. This MIB has as a prerequisite the TN3270E-MIB 41 reference [10]. 43 Expires March 1998 [Page 1]~ 45 White, Moore TN3270E Response Time Collection MIB 29 September 1997 47 Table of Contents 49 1.0 Introduction............................................. 2 50 2.0 The SNMPv2 Network Management Framework.................. 2 51 2.1 Object Definitions....................................... 3 52 3.0 Response Time Collection Methodology..................... 3 53 3.1 General Response Time Collection......................... 4 54 3.2 TN3270E Server Response Time Collection.................. 5 55 3.3 Correlating TN3270E Server and Host Response Times....... 9 56 3.4 Timestamp Calculation....................................10 57 3.4.1 DR Usage...............................................11 58 3.4.2 TIMEMARK Usage.........................................13 59 3.5 Performance Data Modelling...............................14 60 3.5.1 Averaging Response Times...............................15 61 3.5.2 Response Time Buckets..................................17 62 4.0 Structure of the MIB.....................................18 63 4.1 tn3270eRtCollCtlTable....................................18 64 4.2 tn3270eRtDataTable.......................................21 65 4.3 Notifications............................................23 66 5.0 Definitions..............................................24 67 6.0 Security Considerations..................................39 68 7.0 Acknowledgments..........................................40 69 8.0 References...............................................40 70 9.0 Authors' Addresses.......................................42 72 1. Introduction 74 This document is a product of the TN3270E Working Group. Its purpose 75 is to define a protocol and a MIB module to enable a TN3270E server to 76 collect response time data for both TN3270 and TN3270E clients. 77 Prerequisites for implementing this MIB are: 79 o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E 80 Using SMIv2 [10]. 82 o TN3270E RFCs 84 o SYSAPPL-MIB, import Utf8String Textual Convention for 85 international text string support, reference [13]. 87 2. The SNMPv2 Network Management Framework 89 The SNMP Network Management Framework presently consists of three 90 major components. They are: 92 Expires March 1998 [Page 2]~ 94 White, Moore TN3270E Response Time Collection MIB 29 September 1997 96 o the SMI, described in RFC 1902 [1], - the mechanisms used for 97 describing and naming objects for the purpose of management. 99 o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed 100 objects for the Internet suite of protocols. 102 o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol 103 for accessing managed information. 105 It is the intent of this MIB to fully adhere to all prerequisite MIBs 106 unless explicitly stated. Deviations will be documented in 107 corresponding conformance statements. The specification of this MIB 108 uses the Structure of Management Information (SMI) for Version 2 of 109 the Simple Network Management Protocol Version (refer to RFC1902, 110 reference [1]). 112 Textual conventions are defined in RFC 1903 [6], and conformance 113 statements are defined in RFC 1904 [8]. 115 The Framework permits new objects to be defined for the purpose of 116 experimentation and evaluation. 118 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 119 A semantically identical MIB conforming to the SNMPv1 SMI can be 120 produced through the appropriate translation. 122 2.1. Object Definitions 124 Managed objects are accessed via a virtual information store, termed 125 the Management Information Base or MIB. Objects in the MIB are 126 defined using the subset of Abstract Syntax Notation One (ASN.1) 127 defined in the SMI. In particular, each object type is named by an 128 OBJECT IDENTIFIER, an administratively assigned name. The object type 129 together with an object instance serves to uniquely identify a 130 specific instantiation of the object. For human convenience, we often 131 use a textual string, termed the descriptor, to refer to the object 132 type. 134 3. Response Time Collection Methodology 136 This section explains the methodology and approach used by the MIB 137 defined by this memo for response time data collection by a TN3270E 138 Server. 140 Expires March 1998 [Page 3]~ 142 White, Moore TN3270E Response Time Collection MIB 29 September 1997 144 3.1. General Response Time Collection 146 Two primary methods exist for measuring response times in SNA 147 networks: 149 o The SNA Management Services (SNA/MS) Response Time 150 Monitoring (RTM) function 151 o Timestamping using definite response flows. 153 This memo defines an approach using definite responses to timestamp 154 the flows between a client and its TN3270E server, rather than on the 155 RTM method. Extensions to the SNA/MS RTM flow were considered, but 156 this approach was deemed unsuitable since not all TN3270E Server 157 implementations have access to their underlying SNA stacks. The RTM 158 concepts of keeping response time buckets for service level agreements 159 and of interval-based response time collection for performance 160 monitoring are preserved in the MIB module defined in this memo. 162 As mentioned, this memo focuses on using definite responses to 163 timestamp the flows between a client and its TN3270E server for 164 generating performance data. Use of a definite response flow requires 165 that the client supports TN3270E with the RESPONSES function 166 negotiated. The TN3270 TIMEMARK option can be used instead of definite 167 response for supporting TN3270 Clients or TN3270E Clients that don't 168 support RESPONSES. This document focuses on defining the protocol and 169 methods for generating performance data using definite responses and 170 then describes how the TIMEMARK option can be used instead of definite 171 response. 173 In an SNA network, a transaction between a client Logical Unit (LU) 174 and a target host in general looks as follows: 176 ------------------------------------------------ 177 | | 178 | Client LU Target SNA Host | 179 | | 180 | Timestamps | 181 | request A | 182 | -----------------------------------------> | 183 | reply(DR) B | | 184 | <---------------------------------------< | 185 | | +/-RSP C | 186 | >---------------------------------------> | 187 | | 188 | DR: Definite Response requested | 189 | DR +/-: Definite Response | 190 | | 191 ------------------------------------------------ 193 Expires March 1998 [Page 4]~ 195 White, Moore TN3270E Response Time Collection MIB 29 September 1997 197 This transaction is a simple one, and is being used only to illustrate 198 how timestamping at a target SNA host can be used to generate response 199 times. An IBM redbook [12] provides a more detailed description of 200 response time collection for a transaction of this type. Note that 201 for the purpose of calculating an approximation for network transit 202 time, is doesn't matter if the response is positive or negative. Two 203 response time values are typically calculated: 205 o Host Transit Time: Timestamp B - A 206 o Network Transit Time: Timestamp C - B 208 Network transit time is an approximation for the amount of time that a 209 transaction requires to flow across a network, since the response flow 210 is being substituted for the request flow at the start of the 211 transaction. Network transit time, timestamp C - B, is the amount of 212 time that the definite response request and its response required. 213 Host time, timestamp B - A, is the actual time that the host required 214 to process the transaction. Experience has shown that using the 215 response flow to approximate network transit times is useful, and does 216 correlate well with actual network transit times. 218 The TN3270E-RT-MIB describes a method of collecting performance data 219 that is not appropriate for printer (LU Type 1 or LU Type 3) sessions; 220 thus collection of performance data for printer sessions is excluded 221 from this MIB. This exclusion of printer sessions is not considered a 222 problem, since these sessions are not the most important ones for 223 response time monitoring, and since historically they were excluded 224 from SNA/MS RTM collection. The tn3270eTcpConnResourceType object in 225 a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to 226 determine if a client session is ineligible for response time data 227 collection. 229 3.2. TN3270E Server Response Time Collection 231 A TN3270E Server connects an IP client performing 3270 emulation to a 232 target SNA host over both an IP network (IP client to TN3270E server) 233 and an SNA Network (TN3270E server to target SNA host). A TN3270E 234 server can use SNA definite responses and the TN3270 Enhancement (RFC 235 1647 [11]) RESPONSES function to calculate response times for a 236 transaction, by timestamping when a client sends a request, when the 237 reply arrives from the target host, and when the response 238 acknowledging this reply arrives from the client. 240 Section 3.4, Timestamp Calculation, provides specifics on when in the 241 sequence of flows between a TN3270E client and its target SNA host a 242 TN3270E server takes its timestamps. In addition, there is information 243 on how the TN3270 TIMEMARK request/response flow can be used instead 245 Expires March 1998 [Page 5]~ 247 White, Moore TN3270E Response Time Collection MIB 29 September 1997 249 of DR for approximating IP network transit times. 251 The following figure adds a TN3270E server between the client, in this 252 case a TN3270E client and the target SNA host: 254 ------------------------------------------------ 255 | | 256 | Client TN3270E Target | 257 | Server SNA Host | 258 | Timestamps | 259 | | 260 | <---IP Network-------><---SNA Network---> | 261 | | 262 | request D | 263 | ------------------------------------------> | 264 | reply(DR) E | | 265 | <----------------------------------------< | 266 | | +/-RSP F | 267 | >-------------------- - - - - - - - - - > | 268 | | 269 ------------------------------------------------ 271 A TN3270E server can save timestamp D when it receives a client 272 request, save timestamp E when the target SNA host replies, and save 273 timestamp F when the client responds to the definite response request 274 that flowed with the reply. In fact, it doesn't matter whether the 275 target SNA host requested a definite response on its reply: if it 276 didn't, the TN3270E server makes the request on its own, to enable it 277 to produce timestamp F. In this case the TN3270E server does not 278 forward the response to the target SNA host, as the dotted line in the 279 figure indicates. 281 In order to generate timestamp F, a TN3270E server must insure that 282 the transaction specifies DR, and that the TN3270E RESPONSES function 283 has been negotiated between itself and the client. Negotiation of the 284 TN3270E RESPONSES function occurs during the client's TN3270E session 285 initialization. The TN3270E servers that the authors are aware of do 286 request the RESPONSES function during client session initialization. 287 TN3270E clients either automatically support the RESPONSES function, 288 or can be configured during startup to support it. 290 Using timestamps D, E, and F the following response times can be 291 calculated by a TN3270E server: 293 o Total Response time: F - D 294 o IP Network Transit Time: F - E 296 Expires March 1998 [Page 6]~ 298 White, Moore TN3270E Response Time Collection MIB 29 September 1997 300 The MIB provides an object, tn3270eRtCollCtlType, to control several 301 aspects of response time data collection. One of the available 302 options in setting up a response time collection policy is to 303 eliminate the IP-network component altogether. This might be done 304 because it is determined either that the additional IP network traffic 305 would not be desirable, or that the IP-network components of the 306 overall response times are not significant. 308 Excluding the IP-network component from response times also has an 309 implication for the way in which response time data is aggregated. A 310 TN3270E server may find that some of its clients simply don't support 311 any of the functions necessary for the server to calculate the IP- 312 network component of response times. For these clients, the most that 313 the server can calculate is the SNA-network component of their overall 314 response times; the server records this SNA-network component as the 315 TOTAL response time each of these clients' transactions. If a 316 response time collection is aggregating data from a number of clients, 317 some of which have the support necessary for including the IP-network 318 component in their total response time calculations, and some of which 319 do not, then the server aggregates the data differently depending on 320 whether the collection has been defined to include or exclude the IP- 321 network component: 323 o If the IP-network component is included, then transactions 324 for the clients that don't support calculation of the 325 IP-network component of their response times are excluded 326 from the aggregation altogether. 327 o If the IP-network component is excluded, then total response 328 times for ALL clients include only the SNA-network component, 329 even though the server could have included an IP-network 330 component in the overall response times for some of these 331 clients. The server does this by setting timestamp F, which 332 marks the end of a transaction's total response time, equal 333 to timestamp E, the end of the transaction's SNA-network 334 component. 336 The principle here is that all the transactions contributing their 337 response times to an aggregated value must make the same contribution. 338 If the aggregation specifies that an IP-network component must be 339 included in the aggregation's response times, then transactions for 340 which an IP-network component cannot be calculated aren't included at 341 all. If the aggregation specifies that an IP-network component is not 342 to be included, then only the SNA-network component is used, even for 343 those transactions for which an IP-network component could have been 344 calculated. 346 There is one more complication here: the MIB allows a management 347 application to enable or disable dynamic definite responses for a 349 Expires March 1998 [Page 7]~ 351 White, Moore TN3270E Response Time Collection MIB 29 September 1997 353 response time collection. Once again the purpose of this option is to 354 give the network operator control over the amount of traffic 355 introduced into the IP network for response time data collection. A 356 DYNAMIC definite response is one that the TN3270E server itself adds 357 to a reply, in a transaction for which the SNA application at the 358 target SNA host did not specify DR in its reply. When the +/-RSP 359 comes back from the client, the server uses this response to calculate 360 timestamp F, but then it does not forward it on to the SNA application 361 (since the application is not expecting a response to its reply). 363 This dynamic definite responses option is related to the option of 364 including or excluding the IP-network component of response times 365 (discussed above) as follows: 367 o If the IP-network component is excluded, then there is 368 no reason for enabling dynamic definite responses: the 369 server always sets timestamp F equal to timestamp E, so 370 the additional IP-network traffic elicited by a dynamic 371 definite response would serve no purpose. 372 o If the IP-network component is included, then enabling 373 dynamic definite responses causes MORE transactions to 374 be included in the aggregated response time values: 376 - For clients that do not support sending of responses, 377 timestamp F can never be calculated, and so their 378 transactions are never included in the aggregate. 379 - For clients that support sending of responses, 380 timestamp F will always be calculated for transactions 381 in which the host SNA application specifies DR in 382 its reply, and so these transactions will always be 383 included in the aggregate. 384 - For clients that support sending of responses, 385 having dynamic definite responses enabled for a 386 collection results in the inclusion of additional 387 transactions in the aggregate: specifically, those 388 for which the host SNA application did not specify 389 DR in its reply. 391 A TN3270E server also has the option of substituting TIMEMARK 392 processing for definite responses in calculating the IP-network 393 component of a transaction's response time. Once again, there is no 394 reason for the server to do this if the collection has been set up to 395 exclude the IP-network component altogether in computing response 396 times. 398 The MIB is structured to keep for each response time the total time (F 399 - D) and the IP-network component (F - E). A management application 400 can obviously calculate from these two values a response time's SNA- 402 Expires March 1998 [Page 8]~ 404 White, Moore TN3270E Response Time Collection MIB 29 September 1997 406 network component (E - D). The SNA-network component would also 407 contain the host processing time at both the TN3270E Server and at the 408 target application. As in the IP case, these response times are only 409 approximations, because the +/-RSP's crossing of the IP network is 410 substituted for that of the request that started the transaction. 412 When a TN3270E server is in the same SNA host as the target 413 application, then the SNA-network component of a transaction's 414 response time will approximately equal the host transit time (B - A) 415 described previously. A host (as opposed to a gateway) TN3270E server 416 implementation can typically support the establishment of sessions to 417 target applications in remote SNA hosts; in this case the SNA-network 418 component equals the actual SNA-network transit time plus two host 419 transit times. 421 3.3. Correlating TN3270E Server and Host Response Times 423 It is possible that response time data is collected from TN3270E 424 servers at the same time as a management application is monitoring the 425 SNA sessions at a host. For example, a management application can be 426 monitoring a secondary logical unit (SLU) while retrieving data from a 427 TN3270E server. Consider the following figure: 429 ------------------------------------------------ 430 | | 431 | Client TN3270E Target | 432 | Server SNA Host | 433 | Timestamps (PLU) | 434 | (SLU) Timestamps| 435 | <---IP Network-------><---SNA Network---> | 436 | | 437 | request D A | 438 | ------------------------------------------> | 439 | reply(DR) E B | | 440 | <----------------------------------------< | 441 | | +/-RSP F C | 442 | >--------------------------------------> | 443 | | 444 ------------------------------------------------ 446 The following response times are available: 448 o Target SNA host transit time: B - A 449 o Target SNA host (total) network transit time: C - B 450 o TN3270E server total response time: F - D 451 o TN3270E server IP-network component: F - E 453 Expires March 1998 [Page 9]~ 455 White, Moore TN3270E Response Time Collection MIB 29 September 1997 457 The value added by the TN3270E server in this situation is its 458 approximation of the IP-network component of the overall response 459 time. The IP-network component can be subtracted from the total 460 network transit time determined by monitoring the SLU to see the 461 actual SNA versus IP network transit times. 463 The MIB defined by this memo does not specifically address correlation 464 of the data it contains with response time data collected by direct 465 monitoring of SNA resources: its focus is exclusively response time 466 data collection from a TN3270E server perspective. It has, however, 467 in conjunction with the TN3270E-MIB [10], been structured to provide 468 the information necessary for correlation between TN3270E server- 469 provided response time information and that gathered from directly 470 monitoring SNA resources. 472 A management application attempting to correlate SNA resource usage to 473 IP clients can monitor either the tn3270eResMapTable or the 474 tn3270eTcpConnTable to determine resource-to-client address mappings. 475 Both of these tables are defined by the TN3270E-MIB [10]. Another 476 helpful table is the tn3270eSnaMapTable, which provides a mapping 477 between SLU names as they are known at the SSCP (VTAM) and their local 478 names at the TN3270E server. Neither the tn3270eClientGroupTable, the 479 tn3270eResPoolTable, nor the tn3270eClientResMapTable from the 480 TN3270E-MIB can be used for correlation, since the mappings defined by 481 these tables can overlap and may not provide one-to-one mappings. 483 3.4. Timestamp Calculation 485 This section goes into more detail concerning when the various 486 timestamps can be taken as the flows between a TN3270E client and its 487 target SNA host pass through a TN3270E server. In addition, 488 information is provided on how the TN3270 TIMEMARK request/response 489 flow can be used in place of DR for approximating IP network transit 490 times. 492 Expires March 1998 [Page 10]~ 494 White, Moore TN3270E Response Time Collection MIB 29 September 1997 496 3.4.1. DR Usage 498 Consider the following flow: 500 ---------------------------------------------------------- 501 | | 502 | Client TN3270E Target SNA | 503 | Server Host | 504 | Timestamps | 505 | | 506 | <---IP Network-------><---SNA Network---> | 507 | | 508 | request D (BB,CD,OIC,ER) | 509 | -------------------------------------------> | 510 | reply (FIC,ER,EB) | | 511 | <-----------------------------------------< | 512 | reply (MIC,ER) | 513 | <-----------------------------------------< | 514 | reply (MIC,ER) | 515 | <-----------------------------------------< | 516 | reply(DR) E (LIC,DR) | 517 | <-----------------------------------------< | 518 | | +/-RSP F | 519 | >----------------------------------------> | 520 | | 521 | BB : Begin Bracket ER : Response by exception | 522 | EB : End Bracket DR : Definite Response Requested | 523 | CD : Change Direction FIC : First in chain | 524 | OIC: Only in chain MIC: Middle in chain | 525 | LIC: Last in chain | 526 ---------------------------------------------------------- 528 Timestamp D is taken at the TN3270E server when a client sends data to 529 the server for forwarding to its target SNA host. This is most likely 530 when the server finds the end of record indicator in the TCP data 531 received from the client. The target SNA returns its reply in one or 532 more SNA Request Units (RUs); in this example there are four RUs in 533 the reply. The first RU is marked as first in chain (FIC), the next 534 two are marked as middle in chain (MIC), and the last is marked as 535 last in chain (LIC). Timestamp E should be taken prior to sending the 536 RESPONSES request to the client; normally this is done when the server 537 receives the LIC RU. Timestamp F is taken when the RESPONSES response 538 is received from the client. 540 A target SNA application doesn't necessarily return data to a client 541 in a transaction; it may, for example, require more data from the 542 client before it can formulate a reply. In this case the application 543 may simply return to the TN3270E server a change of direction 545 Expires March 1998 [Page 11]~ 547 White, Moore TN3270E Response Time Collection MIB 29 September 1997 549 indicator. A TCP connection is full duplex: data can be received and 550 sent on it at the same time. An SNA session, on the other hand, is 551 half duplex, with a change of direction indicator to alter the 552 direction of data flow. Timestamps E and F require a reply to flow to 553 the client. A best-effort approach should be followed by a TN3270E 554 server when it attempts to calculate timestamps. For cases where the 555 target SNA application sends a change of direction indicator rather 556 than a reply, it is suggested that the entire transaction be omitted 557 from any response time calculations. 559 Another consideration is a mismatch between DR requested on the SNA 560 side and DR requested by a TN3270E server. If the SNA host sends a 561 multiple-RU chain, the server does not know until the last RU is 562 received whether DR is being requested. Meanwhile, the server may 563 have forwarded the first RU in the chain to the client. In practice, 564 therefore, some servers convert ER flows to DR flows. Timestamp E can 565 be taken when the first RESPONSES request flows to the client, and 566 timestamp F when its response is received. In this instance an 567 additional timestamp G is needed when the LIC RU is received: 569 --------------------------------------------------- 570 | | 571 | Client TN3270E Target | 572 | Server SNA Host | 573 | Timestamps | 574 | | 575 | <---IP Network-------><---SNA Network---> | 576 | | 577 | request D (BB,CD,OIC,ER) | 578 | ------------------------------------------> | 579 | reply(DR) E (FIC,ER,EB) | | 580 | <----------------------------------------< | 581 | | +/-RSP F | 582 | >-------------------> | 583 | reply (MIC,ER) | 584 | <----------------------------------------< | 585 | reply (MIC,ER) | 586 | <----------------------------------------< | 587 | reply(DR) (LIC,DR) | 588 | <----------------------------------------< | 589 | | +/-RSP G | 590 | >-------------------> | 591 | | 592 --------------------------------------------------- 594 The response times can then be calculated as follows: 596 o Total response time: G - D 598 Expires March 1998 [Page 12]~ 600 White, Moore TN3270E Response Time Collection MIB 29 September 1997 602 o IP network transit time: F - E 604 If DR is requested by the LIC RU, then the TN3270E server can use 605 either its response or the earlier one for approximating IP network 606 transit time. 608 3.4.2. TIMEMARK Usage 610 It is possible for a TN3270E server to use the TIMEMARK flow for 611 approximating IP network transit times. Using TIMEMARKs would make it 612 possible for a server to collect performance data for TN3270 clients, 613 as well as for TN3270E clients that do not support the RESPONSES 614 function. In order for TIMEMARKs to be used in this way, a client 615 can't have the NOP option enabled, since responses are needed to the 616 server's TIMEMARK requests. An IP network transit time approximation 617 using a TIMEMARK is basically the amount of time it takes for a TN3270 618 server to receive a response from a client to a TIMEMARK request. 620 If a TN3270 server is performing the TIMEMARK function (independent of 621 the response time monitoring use of the function discussed here), then 622 it most likely has a TIMEMARK interval for determining when to examine 623 client sessions for sending the TIMEMARK request. (This interval, 624 which is ordinarily a global value for an entire TN3270E server, is 625 represented in the TN3270E-MIB by the tn3270eSrvrConfActivityInterval 626 object.) A TIMEMARK request is sent only if, when it is examined, a 627 client session is found to have had no activity for a different length 628 of time, represented in the TN3270E-MIB by the 629 tn3270eSrvrConfActivityTimeout object. 631 If a TN3270E server sends a TIMEMARK request to every client with no 632 session activity, based solely on the server's TIMEMARK interval, then 633 network flooding may result, since a server may be supporting 634 thousands of client sessions. The use of TIMEMARKs for response time 635 monitoring could help to reduce this network flooding. Suppose a 636 server sends a TIMEMARK request to a client after a LIC RU has been 637 received, as a means of approximating IP network transit time: 639 Expires March 1998 [Page 13]~ 641 White, Moore TN3270E Response Time Collection MIB 29 September 1997 643 --------------------------------------------------- 644 | | 645 | Client TN3270E Target | 646 | Server Host | 647 | Timestamps | 648 | | 649 | <---IP Network-------><---SNA Network---> | 650 | | 651 | request D (BB,CD,OIC,ER) | 652 | -------------------------------------------> | 653 | reply (FIC,ER,EB) | | 654 | <-----------------------------------------< | 655 | reply (MIC,ER) | 656 | <-----------------------------------------< | 657 | reply (MIC,ER) | 658 | <-----------------------------------------< | 659 | reply(DR) (LIC,ER) | 660 | <-----------------------------------------< | 661 | TIMEMARK Rqst E | 662 | <--------------------- | 663 | | TIMEMARK Rsp F | 664 | >-------------------> | 665 | | 666 --------------------------------------------------- 668 The response times can then be calculated as follows: 670 o TN3270E server total response time: F - D 671 o TN3270E server IP network time: F - E 673 A TN3270E server would need to consider its normal TIMEMARK processing 674 when using TIMEMARKs for this purpose. For example, it must not send a 675 second TIMEMARK request to a client while waiting for the first to 676 return. Also, if a TIMEMARK flow has just been performed for a client 677 shortly before the LIC RU arrives, the server might use the interval 678 from this flow as its approximation for IP network transit time; in 679 this case the server would have to remember to add the interval from 680 this TIMEMARK flow (F' - E') to the interval from the transaction (E - 681 D) to get its approximation for the transaction's total response time. 683 3.5. Performance Data Modelling 685 The following two subsections detail how the TN3270E-RT-MIB models and 686 controls capture of two types of response time data: average response 687 times and response time buckets. 689 Expires March 1998 [Page 14]~ 691 White, Moore TN3270E Response Time Collection MIB 29 September 1997 693 3.5.1. Averaging Response Times 695 Average response times play two different roles in the MIB: 697 o They are made available for management applications to retrieve. 698 o They serve as triggers for emitting notifications. 700 Sliding-window averages are used rather than straight interval-based 701 averages, because they are often more meaningful, and because they 702 cause less notification thrashing. Sliding-window average calculation 703 can, if necessary, be disabled, by setting the sample period 704 multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample 705 period, tn3270eRtCollCtlSPeriod, to the required collection interval. 707 In order to calculate sliding-window averages, a TN3270E server must: 709 o Select a fixed, relative short, sample period SPeriod; the 710 default value for SPeriod in the MIB is 20 seconds. 712 o Select an averaging period multiplier SPMult. The actual 713 collection interval will then be SPMult times SPeriod. The 714 default value for SPMult in the MIB is 30, yielding a default 715 collection interval of 10 minutes. Note that the collection 716 interval (SPMult*SPeriod) is always a multiple of the sample 717 period. 719 o Maintain the following counters to keep track of activity within 720 the current sample period; these are internal counters, not 721 made visible to a management application via the MIB. 723 - T (number of transactions in the period) 724 - TotalRt (sum of the total response times for all 725 transactions in the period) 726 - TotalIpRt (sum of the IP network transit times for 727 all transactions in the period; note that if IP 728 network transit times are being excluded from the 729 response time collection, this value will always be 0). 731 o Also maintain sliding counters, initialized to zero, for each 732 of the quantities being counted: 734 - AvgTransCount (sliding count of transactions) 735 - TotalRtSliding (sliding count of total response times) 736 - TotalIpRtSliding (sliding count of IP network transit times) 738 o At the end of each sample period, update the sliding counters: 740 AvgTransCount = AvgTransCount + T 742 Expires March 1998 [Page 15]~ 744 White, Moore TN3270E Response Time Collection MIB 29 September 1997 746 - (AvgTransCount / SPMult) 748 TotalRtSliding = TotalRtSliding + TotalRt 749 - (TotalRtSliding / SPMult) 751 TotalIpRtSliding = TotalIpRtSliding + TotalIpRt 752 - (TotalIpRtSliding / SPMult) 754 Then reset T, TotalRt, and TotalIpRt to zero for use during the 755 next sample period. 757 o At the end of a collection interval, update the following MIB 758 objects as indicated: 760 tn3270eRtDataAvgTransCount = AvgTransCount 761 tn3270eRtDataAvgRt = TotalRtSliding / AvgTransCount 762 tn3270eRtDataAvgIpRt = TotalIpRtSliding / AvgTransCount 764 As expected, if IP network transit times are being excluded 765 from response time collection, then tn3270eRtDataAvgIpRt 766 will always return 0. 768 The sliding transaction counter AvgTransCount is not used for updating 769 the MIB object tn3270eRtDataTransCount: this object is an ordinary 770 SMI Counter32, which maintains a total count of transactions since its 771 last discontinuity event. The sliding counters are used only for 772 calculating averages. 774 Two mechanisms are present in the MIB to inhibit the generation of an 775 excessive number of notifications related to average response times. 776 First, there are high and low thresholds for average response times. A 777 tn3270eRtExceeded notification is generated the first time a 778 statistically significant average response time is found to have 779 exceeded the high threshold. After this, no other tn3270eRtExceeded 780 notifications are generated until an average response time is found to 781 have fallen below the low threshold. 783 The other mechanism to limit notifications is the significance test 784 for a high average response time. Intuitively, the significance of an 785 average is directly related to the number of samples that go into it; 786 so we might be inclined to use a rule such as "for the purpose of 787 generating tn32709eRtExceeded notifications, ignore average response 788 times based on fewer than 20 transactions in the sample period." 790 In the case of response times, however, the number of transactions 791 sampled in a fixed sampling period is tied to these transactions' 792 response times. A few transactions with long response times can 793 guarantee that there will not be many transactions in a sample, 795 Expires March 1998 [Page 16]~ 797 White, Moore TN3270E Response Time Collection MIB 29 September 1997 799 because these transactions "use up" the sampling time. Yet this case 800 of a few transactions with very poor response times should obviously 801 be classified as a problem, not as a statistical anomaly based on too 802 small a sample. 804 The solution is to make the significance level for a sample a function 805 of the average response time. In order to determine at a collection 806 interval whether to generate a tn3270eRtExceeded notification, a 807 TN3270E server uses the following algorithm: 809 if AvgTransCount * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 810 then generate the notification 812 Two examples illustrate how this algorithm works. Suppose that 813 IdleRate has been set to 20 transactions, and the high threshold to 814 200 msecs per transaction. If the average observed response time is 815 300 msecs, then a notification will be generated only if AvgTransCount 816 >= 80. If, however, the observed response time is 500 msecs, then a 817 notification is generated if AvgTransCount >= 9. 819 There is no corresponding significance test for the tn3270eRtOkay 820 notification: this notification is generated based on an average 821 response time that falls below the low threshold, regardless of the 822 sample size behind that average. 824 3.5.2. Response Time Buckets 826 The MIB also supports collection of response time data into a set of 827 five buckets. This data is suitable either for verification of service 828 level agreements, or for monitoring by a management application to 829 identify performance problems. The buckets provide counts of 830 transactions whose total response times fall into a set of specified 831 ranges. 833 Like everything for a collection, the "total" response times collected 834 in the buckets are governed by the specification of whether IP network 835 transit times are to be included in the totals. Depending on how this 836 option is specified, the response times being counted in the buckets 837 will either be total response times (F - D), or only SNA network 838 transit times (effectively E - D, because when it is excluding the 839 IP-network component of transactions, a server makes timestamp F 840 identical to timestamp E). 841 Four bucket boundaries are specified for a response time collection, 842 resulting in five buckets. The first response time bucket counts those 843 transactions whose total response times were less than or equal to 844 Boundary 1, the second bucket counts those whose response times were 845 greater than Boundary 1 but less than or equal to Boundary 2, and so 847 Expires March 1998 [Page 17]~ 849 White, Moore TN3270E Response Time Collection MIB 29 September 1997 851 on. The fifth bucket is unbounded on the top, counting all 852 transactions whose response times were greater than Boundary 4. 854 The four bucket boundaries have default values of: 1 second, 2 855 seconds, 5 seconds, and 10 seconds, respectively. These values are 856 the defaults in the 3174 controller's implementation of the SNA/MS RTM 857 function, and were thought to be appropriate for this MIB as well. 859 In SNA/MS the counter buckets were (by today's standards) relatively 860 small, with a maximum value of 65,535. The bucket objects in the MIB 861 are all Counter32's. 863 The following figure represents the buckets pictorially: 865 ---------------------------------------------- 866 | | 867 | Response Time Boundaries | 868 | | | | | | | | 869 | | | | | | | | 870 | | | | | | no | 871 | 0 B-1 B-2 B-3 B-4 bound| 872 | | | | | | | | 873 | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| | 874 | ----------------------------------------- | 875 | | 876 ---------------------------------------------- 878 4. Structure of the MIB 880 The TN3270E-RT-MIB has the following components: 882 o tn3270eRtCollCtlTable 883 o tn3270eRtDataTable 884 o Notifications 886 4.1. tn3270eRtCollCtlTable 888 The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex, imported 889 from the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. 890 tn3270eSrvrConfIndex identifies within a host a particular TN3270E 891 server. tn3270eRtCollCtlClientGroupName identifies a collection of IP 892 clients for which response time data is to be collected. The 893 collection itself is defined using the tn3270eClientGroupTable from 894 the TN3270E-MIB. The index from the tn3270eClientGroupTable, 895 tn3270eClientGroupName, was not used directly, since doing so causes 896 an inconsistent indexing scheme error in some MIB compilers. To avoid 898 Expires March 1998 [Page 18]~ 900 White, Moore TN3270E Response Time Collection MIB 29 September 1997 902 this error, tn3270eRtCollCtlClientGroupName was defined directly in 903 the tn3270eRtCollCtlEntry. 905 A tn3270eRtCollCtlEntry contains the following objects: 907 -------------------------------------------------- 908 1st Index | tn3270eSrvrConfIndex Unsigned32 | 909 2nd Index | tn3270eRtCollCtlClientGroupName Utf8String | 910 | tn3270eRtCollCtlType BITS | 911 | tn3270eRtCollCtlSPeriod Unsigned32 | 912 | tn3270eRtCollCtlSPMult Unsigned32 | 913 | tn3270eRtCollCtlThreshHigh Unsigned32 | 914 | tn3270eRtCollCtlThreshLow Unsigned32 | 915 | tn3270eRtCollCtlIdleRate Unsigned32 | 916 | tn3270eRtCollCtlBucketBndry1 Unsigned32 | 917 | tn3270eRtCollCtlBucketBndry2 Unsigned32 | 918 | tn3270eRtCollCtlBucketBndry3 Unsigned32 | 919 | tn3270eRtCollCtlBucketBndry4 Unsigned32 | 920 | tn3270eRtCollCtlRowStatus RowStatus | 921 -------------------------------------------------- 923 The tn3270eRtCollCtlType object controls the type(s) of response time 924 collection that occur, the granularity of the collection, whether 925 dynamic definite responses should be initiated, and whether 926 notifications should be generated. This object is of BITS SYNTAX, and 927 thus allows selection of multiple options. 929 The BITS in the tn3270eRtCollCtlType object have the following 930 meanings: 932 o aggregate(0) - If this bit is set to 1, then data should be 933 aggregated for the whole client group. In this case there will 934 be only one row created for the collection in the 935 tn3270eRtDataTable. The first two indexes for this row, 936 tn3270eSrvrConfIndex and tn3270eRtCollCtlClientGroupName, will 937 have the same values as the indexes for this row in the 938 tn3270eRtCollCtlTable. The third and fourth indexes for an 939 aggregated tn3270eRtDataEntry have the values 'unknown(0)' 940 (for tn3270eRtDataClientAddrType) and a null octet string 941 (for tn3270eRtDataClientAddress). 943 If this bit is set to 0, then a separate entry is created in the 944 tn3270eRtDataTable for each member of the client group. In this 945 case the tn3270eRtDataClientAddress contains the client's actual 946 IP Address, and tn3270eRtDataClientAddrType indicates the type 947 of this address. 949 o excludeIpComponent(1) - If this bit is set to 1, then the 951 Expires March 1998 [Page 19]~ 953 White, Moore TN3270E Response Time Collection MIB 29 September 1997 955 server should exclude the IP-network component from all the 956 response times for this collection. If the target SNA 957 application specifies DR in any of its replies, this DR will 958 still be passed down to the client, and the client's response 959 will still be forwarded to the application. But this response 960 will play no role in the server's response time calculations. 962 If this bit is set to 0, then the server includes in the 963 collection only those transactions for which it can include an 964 (approximate) IP-network component in the total response time 965 for the transaction. This component may be derived from a 966 "natural" DR (if the client supports the RESPONSES function), 967 from a dynamic DR introduced by the server (if the client 968 supports the RESPONSES function and the ddr(2) bit has been 969 set to 1), or from TIMEMARK processing (if the client supports 970 TIMEMARKs). 972 If this bit is set to 1, then the ddr(2) bit is ignored, since 973 there is no reason for the server to request additional 974 responses from the client(s) in the group. 976 o ddr(2) - If this bit is set to 1, then the server should, for 977 those clients in the group that support the RESPONSES function, 978 add a DR request to a reply in each transaction (usually, but 979 not necessarily the LIC reply), and use the client's subsequent 980 response for calculating an (approximate) IP-network component 981 to include in the transaction's total response times. 983 If this bit is set to 0, then the server does not add a DR 984 request to any replies from the target SNA application. 986 If the excludeIpComponent(1) bit is set to 1, then this bit is 987 ignored by the server. 989 o average(3) - If this bit is set to 1, then the server should 990 calculate a sliding-window average for the collection, based 991 on the parameters specfied for the group. 993 If this bit is set to 0, then an average is not calculated. In 994 this case the tn3270eRtExceeded and tn3270eRtOkay notifications 995 are not generated, even if the traps(5) bit is set to 1. 997 o buckets(4) - If this bit is set to 1, then the server should 998 create and increment response time buckets for the collection, 999 based on the parameters specified for the group. 1001 If this bit is set to 0, then response time buckets are not 1002 created. 1004 Expires March 1998 [Page 20]~ 1006 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1008 o traps(5) - If this bit is set to 1, then the server generates 1009 the notifications defined in this MIB. The tn3270CollStart and 1010 tn3270CollEnd notifications are always generated when this bit 1011 is set to 1; the tn3270eRtExceeded and tn3270eRtOkay 1012 notifications are generated only if the average(3) bit is also 1013 set to 1. 1015 If this bit is set to 0, then none of the notifications defined 1016 in this MIB are generated by the server. 1018 Either the average(3) or the buckets(4) bit must be set to 1 in order 1019 for response time data collection to occur. If the average(3) bit is 1020 set to 1, then the following objects have meaning, and are used to 1021 control the calculation of the averages, as well as the generation of 1022 the two notifications related to them: 1024 o tn3270eRtCollCtlSPeriod 1025 o tn3270eRtCollCtlSPMult 1026 o tn3270eRtCollCtlThreshHigh 1027 o tn3270eRtCollCtlThreshLow 1028 o tn3270eRtCollCtlIdleRate 1030 If the buckets(4) bit is set to 1, then the following objects have 1031 meaning, and specify the bucket boundaries: 1033 o tn3270eRtCollCtlBucketBndry1 1034 o tn3270eRtCollCtlBucketBndry2 1035 o tn3270eRtCollCtlBucketBndry3 1036 o tn3270eRtCollCtlBucketBndry4 1038 4.2. tn3270eRtDataTable 1040 Either a single entry or multiple entries are created in the 1041 tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on 1042 whether tn3270eRtCollCtlType in the control entry has aggregate(0) 1043 selected. The contents of an entry in the tn3270eRtDataTable depend 1044 on the contents of the corresponding entry in the 1045 tn3270eRtCollCtlTable: some objects in the data entry return 1046 meaningful values only when the average(3) option is selected in the 1047 control entry, while others return meaningful values only when the 1048 buckets(4) option is selected. If both options are selected, then all 1049 the objects return meaningful values. When an object is not specified 1050 to return a meaningful value, an implementation may return any value 1051 in response to a Get operation. 1053 The following objects return meaningful values if and only if the 1055 Expires March 1998 [Page 21]~ 1057 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1059 average(3) option was selected in the corresponding 1060 tn3270eRtCollCtlEntry: 1062 o tn3270eRtDataAvgRt 1063 o tn3270eRtDataAvgIpRt 1064 o tn3270eRtDataAvgTransCount 1065 o tn3270eRtDataIntTimeStamp 1066 o tn3270eRtDataTotalRt 1067 o tn3270eRtDataTotalIpRt 1068 o tn3270eRtDataTransCount 1069 o tn3270eRtDataDrCount 1070 o tn3270eRtDataElapsRndTrpSq 1071 o tn3270eRtDataElapsIpRtSq 1073 The first three objects in this list return values derived from the 1074 sliding-window average calculations described earlier. The time of 1075 the most recent sample for these calculations is returned in the 1076 tn3270eRtDaraIntTimeStamp object. The next four objects are normal 1077 Counter32 objects, maintaining counts of total response time and total 1078 transactions. The last two objects return sum of the squares values, 1079 to enable variance calculations by a management application. 1081 o tn3270eRtDataElapsRndTrpSq 1082 o tn3270eRtDataElapsIpRtSq 1084 The following objects return meaningful values if and only if the 1085 buckets(4) option was selected in the corresponding 1086 tn3270eRtCollCtlEntry: 1088 o tn3270eRtDataBucket1 1089 o tn3270eRtDataBucket2 1090 o tn3270eRtDataBucket3 1091 o tn3270eRtDataBucket4 1092 o tn3270eRtDataBucket5 1094 A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by 1095 a management application to detect when the values of the counter 1096 objects in this table may have been reset, or otherwise experienced a 1097 discontinuity. A possible cause for such a discontinuity is the 1098 TN3270E server's being stopped or restarted. This object returns a 1099 meaningful value regardless of which collection control options were 1100 selected. 1102 When an entry is created in the tn3270eRtCollCtlTable with its 1103 tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is 1104 automatically created in the tn3270eRtDataTable; this entry's 1105 tn3270eRtDataClientAddress has the value of a null octet string, and 1107 Expires March 1998 [Page 22]~ 1109 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1111 its tn3270eRtDataClientAddrType has the value of unknown(0). 1113 When an entry is created in the tn3270eRtCollCtlTable with its 1114 tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is 1115 created in the tn3270eRtDataTable for each member of the client group 1116 that currently has a session with the TN3270E server. Entries are 1117 subsequently created for clients that the TN3270E server determines to 1118 be members of the client group when these clients establish sessions 1119 with the server. 1121 All entries associated with a tn3270eRtCollCtlEntry are deleted from 1122 the tn3270eRtDataTable when that entry is deleted from the 1123 tn3270eRtCollCtlTable. An entry for an individual client in a client 1124 group is deleted when its TCP connection terminates. 1126 4.3. Notifications 1128 This MIB defines four notifications related to a tn3270eRtDataEntry. 1129 If the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1130 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications are 1131 generated when, respsectively, the tn3270eRtDataEntry is created and 1132 deleted. If, in addition, this tn3270eRtCollCtlType object's 1133 average(3) bit is set to 1, then the the tn3270eRtExceeded and 1134 tn3270eRtOkay notifications are generated when the conditions they 1135 report occur. 1137 The following notifications are defined by this MIB: 1139 o tn3270eRtExceeded - The purpose of this notification is to 1140 signal that a performance problem has been detected. If 1141 average(3) response time data is being collected, then this 1142 notification is generated whenever (1) an average response 1143 time is first found, on a collection interval boundary, to 1144 have exceeded the high threshold tn3270eRtCollCtlThreshHigh 1145 specified for the client group, AND (2) the sample on which the 1146 average is based is determined to have been a significant one, 1147 via the significance algorithm described earlier. This 1148 notification is not generated again for a tn3270eRtDataEntry 1149 until an average response time falling below the low 1150 threshold tn3270eRtCollCtlThreshLow specified for the client 1151 group has occured for the entry. 1153 o tn3270eRtOkay - The purpose of this notification is to signal 1154 that a previously reported performance problem has been 1155 resolved. If average(3) response time data is being collected, 1156 then this notification is generated whenever (1) a 1157 tn3270eRtExceeded notification has already been generated, AND 1159 Expires March 1998 [Page 23]~ 1161 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1163 (2) an average response time is first found, on a collection 1164 interval boundary, to have fallen below the low threshold 1165 tn3270eRtCollCtlThreshLow specified for the client group. 1166 This notification is not generated again for a 1167 tn3270eRtDataEntry until an average response time 1168 exceeding the high threshold tn3270eRtCollCtlThreshHigh 1169 specified for the client group has occurred for the entry. 1171 Taken together, the two preceding notifications serve to minimize the 1172 generation of an excessive number of traps in the case of an average 1173 response time that oscillates about its high threshold. 1175 o tn3270eRtCollStart - This notification is generated whenever 1176 data collection begins for a client group, or when a new 1177 tn3270eRtDataEntry becomes active. The primary purpose of 1178 this notification is signal to a management application that 1179 a new client TCP session has been established, and to provide 1180 the IP-to-resource mapping for the session. This notification 1181 is not critical when average(3) data collection is not being 1182 performed for the client group. 1184 o tn3270eRtCollEnd - This notification is generated whenever 1185 a data collection ends. For an aggregate collection, this 1186 occurs when the corresponding tn3270eRtCollCtlEntry is 1187 deleted. For an individual collection, this occurs either 1188 when the tn3270eRtCollCtlEntry is deleted, or when the 1189 client's TCP connection terminates. The purpose of this 1190 notification is to enable a management application to 1191 complete a monitoring function that it was performing, by 1192 returning final values for the collection's data objects. 1194 5. Definitions 1196 TN3270E-RT-MIB DEFINITIONS ::= BEGIN 1198 IMPORTS 1199 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 1200 experimental, Counter32, BITS, Unsigned32, 1201 Gauge32 1202 FROM SNMPv2-SMI 1203 RowStatus, DateAndTime, TimeStamp 1204 FROM SNMPv2-TC 1205 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1206 FROM SNMPv2-CONF 1207 Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex, 1208 tn3270eResMapElementName, tn3270eResMapElementType 1209 FROM TN3270E-MIB 1211 Expires March 1998 [Page 24]~ 1213 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1215 Utf8String 1216 FROM SYSAPPL-MIB; 1218 tn3270eRtMIB MODULE-IDENTITY 1219 LAST-UPDATED "9709240000Z" -- September 24, 1997 1220 ORGANIZATION "TN3270E Working Group" 1221 CONTACT-INFO 1222 "Kenneth White (kennethw@vnet.ibm.com) 1223 IBM Corp. - Dept. BRQA/Bldg. 503/C117 1224 P.O. Box 12195 1225 3039 Cornwallis 1226 RTP, NC 27709-2195 1227 (919) 254-0102 1229 Robert Moore (remoore@us.ibm.com) 1230 IBM Corp. - Dept. BRQA/Bldg. 501/G114 1231 P.O. Box 12195 1232 3039 Cornwallis 1233 RTP, NC 27709-2195 1234 (919) 254-7507" 1235 DESCRIPTION 1236 "This module defines a portion of the management information 1237 base (MIB) that enables monitoring of TN3270 and TN3270E 1238 clients' response times by a TN3270E server." 1239 ::= { experimental 81 } 1241 -- Top level structure of the MIB 1243 tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 } 1244 tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 } 1245 tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 } 1247 -- MIB Objects 1249 -- Response Time Control Table 1251 tn3270eRtCollCtlTable OBJECT-TYPE 1252 SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "The response time monitoring collection control table, which 1257 allows a management application to control the types of 1258 response time data being collected, and the clients for which 1259 it is being collected. 1261 This table is indexed by tn3270eSrvrConfIndex, imported from 1262 the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. 1264 Expires March 1998 [Page 25]~ 1266 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1268 tn3270eSrvrConfIndex indicates within a host which TN3270E 1269 server an entry applied to. 1271 tn3270eRtCollCtlClientGroupName is equivalent to the 1272 tn3270eClientGroupName index in the TN3270E-MIB; it identifies 1273 the collection of IP clients for which response time data 1274 is being collectedr. The particular IP clients making up the 1275 collection are identified in the tn3270eClientGroupTable in 1276 the TN3270E-MIB." 1277 ::= { tn3270eRtObjects 1} 1279 tn3270eRtCollCtlEntry OBJECT-TYPE 1280 SYNTAX Tn3270eRtCollCtlEntry 1281 MAX-ACCESS not-accessible 1282 STATUS current 1283 DESCRIPTION 1284 "Entry in the TN3270E response time monitoring collection 1285 control table. To handle the case of multiple TN3270E servers 1286 on the same host, the first index of this table is the 1287 tn3270eSrvrConfIndex from the TN3270E-MIB." 1288 INDEX { 1289 tn3270eSrvrConfIndex, -- Server's index 1290 tn3270eRtCollCtlClientGroupName } -- What to collect on 1291 ::= { tn3270eRtCollCtlTable 1 } 1293 Tn3270eRtCollCtlEntry ::= SEQUENCE { 1294 tn3270eRtCollCtlClientGroupName Utf8String, 1295 tn3270eRtCollCtlType BITS, 1296 tn3270eRtCollCtlSPeriod Unsigned32, 1297 tn3270eRtCollCtlSPMult Unsigned32, 1298 tn3270eRtCollCtlThreshHigh Unsigned32, 1299 tn3270eRtCollCtlThreshLow Unsigned32, 1300 tn3270eRtCollCtlIdleRate Unsigned32, 1301 tn3270eRtCollCtlBucketBndry1 Unsigned32, 1302 tn3270eRtCollCtlBucketBndry2 Unsigned32, 1303 tn3270eRtCollCtlBucketBndry3 Unsigned32, 1304 tn3270eRtCollCtlBucketBndry4 Unsigned32, 1305 tn3270eRtCollCtlRowStatus RowStatus } 1307 tn3270eRtCollCtlClientGroupName OBJECT-TYPE 1308 SYNTAX Utf8String (SIZE(1..24)) 1309 MAX-ACCESS not-accessible 1310 STATUS current 1311 DESCRIPTION 1312 "The name of a client group. Membership in a client group is 1313 specified via the TN3270E-MIB's tn3270eClientGroupTable. 1314 The index for that table, tn3270eClientGroupName, is 1315 equivalent to this object; it was not imported because 1317 Expires March 1998 [Page 26]~ 1319 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1321 doing so results in MIB compiler errors." 1323 ::= { tn3270eRtCollCtlEntry 1 } 1325 tn3270eRtCollCtlType OBJECT-TYPE 1326 SYNTAX BITS { 1327 aggregate(0), 1328 excludeIpComponent(1), 1329 ddr(2), 1330 average(3), 1331 buckets(4), 1332 traps(5) 1333 } 1334 MAX-ACCESS read-create 1335 STATUS current 1336 DESCRIPTION 1337 "This object controls what types of response time data to 1338 collect, whether to summarize the data across the members 1339 of a client group or keep it individually, whether to 1340 introduce dynamic definite responses, and whether to 1341 generate traps. 1343 aggregate(0) - Aggregate response time data for the 1344 client group as a whole. If this bit is 1345 set to 0, then maintain response time 1346 data separately for each member of the 1347 client group. 1348 excludeIpComponent(1) - Do not include the IP-network component 1349 in any response times. 1350 ddr(2) - Enable dynamic definite response. 1351 average(3) - Produce an average response time based 1352 on a specified collection interval. 1353 buckets(4) - Maintain tn3270eRtDataBucket values in 1354 a corresponding tn3270eRtDataEntry, 1355 based on the bucket boundaries 1356 specified in the 1357 tn3270eRtDataBucketBndry objects. 1358 traps(5) - generate the traps specified in this 1359 MIB module. The tn3270eRtExceeded and 1360 tn3270eRtOkay are generated only if 1361 average(3) is also specified." 1362 ::= { tn3270eRtCollCtlEntry 2 } 1364 tn3270eRtCollCtlSPeriod OBJECT-TYPE 1365 SYNTAX Unsigned32 -- 15 second minimum to 24 hour max 1366 UNITS "seconds" 1367 MAX-ACCESS read-create 1368 STATUS current 1370 Expires March 1998 [Page 27]~ 1372 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1374 DESCRIPTION 1375 "The number of seconds that defines the sample period. 1376 The actual interval is defined as tn3270eRtCollCtlSPeriod 1377 times tn3270eRtCollCtlSPMult. 1379 The value of this object is used only if the corresponding 1380 tn3270eRtCollCtlType has the average(3) setting." 1381 DEFVAL {20} -- 20 seconds 1382 ::= { tn3270eRtCollCtlEntry 3 } 1384 tn3270eRtCollCtlSPMult OBJECT-TYPE 1385 SYNTAX Unsigned32 -- should be > 1 1386 UNITS "count" 1387 MAX-ACCESS read-create 1388 STATUS current 1389 DESCRIPTION 1390 "The sample period multiplier; this value is multiplied by the 1391 sample period, tn3270eRtCollCtlSPeriod, to determine the 1392 collection interval. 1394 The value of this object is used only if the corresponding 1395 tn3270eRtCollCtlType has the average(3) setting." 1396 DEFVAL { 30 } -- yields an interval of 10 minutes when 1397 -- used with the default SPeriod value 1398 ::= { tn3270eRtCollCtlEntry 4 } 1400 tn3270eRtCollCtlThreshHigh OBJECT-TYPE 1401 SYNTAX Unsigned32 1402 UNITS "seconds" 1403 MAX-ACCESS read-create 1404 STATUS current 1405 DESCRIPTION 1406 "The threshold for generating a tn3270eRtExceeded notification, 1407 signalling that a monitored total response time has exceeded the 1408 specified limit. A value of zero for this object suppresses 1409 generation of this notification. The value of this object is 1410 used only if the corresponding tn3270eRtCollCtlType has 1411 average(3) and traps(5) selected." 1412 ::= { tn3270eRtCollCtlEntry 5 } 1414 tn3270eRtCollCtlThreshLow OBJECT-TYPE 1415 SYNTAX Unsigned32 1416 UNITS "seconds" 1417 MAX-ACCESS read-create 1418 STATUS current 1419 DESCRIPTION 1420 "The threshold for generating a tn3270eRtOkay notification, 1421 signalling that a monitored total response time has fallen below 1423 Expires March 1998 [Page 28]~ 1425 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1427 the specified limit. A value of zero for this object suppresses 1428 generation of this notification. The value of this object is 1429 used only if the corresponding tn3270eRtCollCtlType has 1430 average(3) and traps(5) selected." 1431 ::= { tn3270eRtCollCtlEntry 6 } 1433 tn3270eRtCollCtlIdleRate OBJECT-TYPE 1434 SYNTAX Unsigned32 1435 UNITS "transaction count" 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "The value of this object is used to determine whether a sample 1440 that yields an average response time exceeding the value of 1441 tn3270eRtCollCtlThreshHigh was a statistically valid one. If 1442 the following statement is true, then the sample was 1443 statistically valid, and so a tn3270eRtExceeded notification 1444 should be generated: 1446 AvgTransCount * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 1448 This comparison is done only if the corresponding 1449 tn3270eRtCollCtlType has average(3) and traps(5) selected." 1450 DEFVAL { 1 } 1451 ::= { tn3270eRtCollCtlEntry 7 } 1453 tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE 1454 SYNTAX Unsigned32 1455 UNITS "tenths of seconds" 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "The value of this object defines the range of transaction 1460 response times counted in the Tn3270eRtDataBucket1 object: 1461 those less than or equal to this value." 1462 DEFVAL { 10 } 1463 ::= { tn3270eRtCollCtlEntry 8 } 1465 tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE 1466 SYNTAX Unsigned32 1467 UNITS "tenths of seconds" 1468 MAX-ACCESS read-create 1469 STATUS current 1470 DESCRIPTION 1471 "The value of this object, together with that of the 1472 tn3270eRtCollCtlBucketBndry1 object, defines the range of 1473 transaction response times counted in the Tn3270eRtDataBucket2 1474 object: those greater than the value of the 1476 Expires March 1998 [Page 29]~ 1478 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1480 tn3270eRtCollCtlBucketBndry1 object, and less than or equal to 1481 the value of this object." 1482 DEFVAL { 20 } 1483 ::= { tn3270eRtCollCtlEntry 9 } 1485 tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE 1486 SYNTAX Unsigned32 1487 UNITS "tenths of seconds" 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "The value of this object, together with that of the 1492 tn3270eRtCollCtlBucketBndry2 object, defines the range of 1493 transaction response times counted in the Tn3270eRtDataBucket3 1494 object: those greater than the value of the 1495 tn3270eRtCollCtlBucketBndry2 object, and less than or equal to 1496 the value of this object." 1497 DEFVAL { 50 } 1498 ::= { tn3270eRtCollCtlEntry 10 } 1500 tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE 1501 SYNTAX Unsigned32 1502 UNITS "tenths of seconds" 1503 MAX-ACCESS read-create 1504 STATUS current 1505 DESCRIPTION 1506 "The value of this object, together with that of the 1507 tn3270eRtCollCtlBucketBndry3 object, defines the range of 1508 transaction response times counted in the Tn3270eRtDataBucket4 1509 object: those greater than the value of the 1510 tn3270eRtCollCtlBucketBndry3 object, and less than or equal to 1511 the value of this object. 1513 The value of this object also defines the range of transaction 1514 response times counted in the Tn3270eRtDataBucket5 object: 1515 those greater than the value of this object." 1516 DEFVAL { 100 } 1517 ::= { tn3270eRtCollCtlEntry 11 } 1519 tn3270eRtCollCtlRowStatus OBJECT-TYPE 1520 SYNTAX RowStatus 1521 MAX-ACCESS read-create 1522 STATUS current 1523 DESCRIPTION 1524 "This object allows entries to be created and deleted 1525 in the tn3270eRtCollCtlTable. An entry in this table 1526 is deleted by setting this object to destroy(6). 1527 Deleting an entry in this table has the side-effect 1529 Expires March 1998 [Page 30]~ 1531 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1533 of removing all entries from the tn3270eRtDataTable 1534 that are associated with the entry being deleted." 1535 ::= { tn3270eRtCollCtlEntry 12 } 1537 -- TN3270E Response Time Data Table 1539 tn3270eRtDataTable OBJECT-TYPE 1540 SYNTAX SEQUENCE OF Tn3270eRtDataEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "The response time data table. Entries in this table are 1545 created based on entries in the tn3270eRtCollCtlTable." 1546 ::= { tn3270eRtObjects 2 } 1548 tn3270eRtDataEntry OBJECT-TYPE 1549 SYNTAX Tn3270eRtDataEntry 1550 MAX-ACCESS not-accessible 1551 STATUS current 1552 DESCRIPTION 1553 "An entry in this table is created based upon the 1554 tn3270eRtCollCtlTable. A single entry is created with a 1555 tn3270eRtDataClientAddrType of 'unknown(0)' and a null octet 1556 string value for tn3270eRtDataClientAddress when the 1557 corresponding tn3270eRtCollCtlType has aggregate(0) specified. 1558 When aggregate(0) is not specified, then a separate entry is 1559 created for each client. 1561 Note that the following objects defined within an 1562 entry in this table can wrap: 1563 tn3270eRtDataTotalRt 1564 tn3270eRtDataTotalIpRt 1565 tn3270eRtDataTransCount 1566 tn3270eRtDataDrCount 1567 tn3270eRtDataElapsRnTrpSq 1568 tn3270eRtDataElapsIpRtSq 1569 tn3270eRtDataBucket1 1570 tn3270eRtDataBucket2 1571 tn3270eRtDataBucket3 1572 tn3270eRtDataBucket4 1573 tn3270eRtDataBucket5" 1574 INDEX { 1575 tn3270eSrvrConfIndex, -- Server's local index 1576 tn3270eRtCollCtlClientGroupName, -- Target of data collection 1577 tn3270eRtDataClientAddrType, 1578 tn3270eRtDataClientAddress } 1579 ::= { tn3270eRtDataTable 1 } 1581 Expires March 1998 [Page 31]~ 1583 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1585 Tn3270eRtDataEntry ::= SEQUENCE { 1586 tn3270eRtDataClientAddrType Tn3270eAddrType, 1587 tn3270eRtDataClientAddress Tn3270eTAddress, 1588 tn3270eRtDataDiscontinuityTime TimeStamp, 1589 tn3270eRtDataAvgRt Gauge32, 1590 tn3270eRtDataAvgIpRt Gauge32, 1591 tn3270eRtDataAvgTransCount Counter32, 1592 tn3270eRtDataIntTimeStamp DateAndTime, 1593 tn3270eRtDataTotalRt Counter32, 1594 tn3270eRtDataTotalIpRt Counter32, 1595 tn3270eRtDataTransCount Counter32, 1596 tn3270eRtDataDrCount Counter32, 1597 tn3270eRtDataElapsRndTrpSq Unsigned32, 1598 tn3270eRtDataElapsIpRtSq Unsigned32, 1599 tn3270eRtDataBucket1 Counter32, 1600 tn3270eRtDataBucket2 Counter32, 1601 tn3270eRtDataBucket3 Counter32, 1602 tn3270eRtDataBucket4 Counter32, 1603 tn3270eRtDataBucket5 Counter32 1604 } 1606 tn3270eRtDataClientAddrType OBJECT-TYPE 1607 SYNTAX Tn3270eAddrType 1608 MAX-ACCESS not-accessible 1609 STATUS current 1610 DESCRIPTION 1611 "Indicates the type of address that following in the 1612 instance OID represented by tn3270eRtDataClientAddress." 1613 ::= { tn3270eRtDataEntry 1 } 1615 tn3270eRtDataClientAddress OBJECT-TYPE 1616 SYNTAX Tn3270eTAddress 1617 MAX-ACCESS not-accessible 1618 STATUS current 1619 DESCRIPTION 1620 "Contains the IP address of the TN3270 client being 1621 monitored. A null octet string is used if the aggregate 1622 of the Client Group is being collected " 1623 ::= { tn3270eRtDataEntry 2 } 1625 tn3270eRtDataDiscontinuityTime OBJECT-TYPE 1626 SYNTAX TimeStamp 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "The value of sysUpTime on the most recent occasion at 1631 which any one or more of this entry's objects 1632 suffered a discontinuity. One possibility of this is 1634 Expires March 1998 [Page 32]~ 1636 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1638 when a TN3270E Server is stopped and then restarted 1639 where local methods are used to setup collection 1640 policy (tn3270eRtCollCtlTable entries). 1642 In order to prevent a TN3270E Server from caching this 1643 object it is recommended that the TN3270E Server's 1644 startup time be used as the objects initial value." 1645 ::= { tn3270eRtDataEntry 3 } 1647 tn3270eRtDataAvgRt OBJECT-TYPE 1648 SYNTAX Gauge32 1649 UNITS "tenths of seconds" 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The average total response time measured over the last 1654 collection interval." 1655 DEFVAL { 0 } 1656 ::= { tn3270eRtDataEntry 4 } 1658 tn3270eRtDataAvgIpRt OBJECT-TYPE 1659 SYNTAX Gauge32 1660 UNITS "tenths of seconds" 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "The average IP response time measured over the last 1665 collection interval." 1666 DEFVAL { 0 } 1667 ::= { tn3270eRtDataEntry 5 } 1669 tn3270eRtDataAvgTransCount OBJECT-TYPE 1670 SYNTAX Counter32 1671 UNITS "transactions" 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "The sliding transaction count used for calculating the values 1676 of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects. 1677 The actual transaction count is available in the 1678 tn3270eRtDataTransCount object." 1679 ::= { tn3270eRtDataEntry 6 } 1681 tn3270eRtDataIntTimeStamp OBJECT-TYPE 1682 SYNTAX DateAndTime 1683 MAX-ACCESS read-only 1684 STATUS current 1685 DESCRIPTION 1687 Expires March 1998 [Page 33]~ 1689 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1691 "The date and time of the last interval that tn3270eRtDataAvgRt, 1692 tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgTransCount were 1693 calculated." 1694 ::= { tn3270eRtDataEntry 7 } 1696 tn3270eRtDataTotalRt OBJECT-TYPE 1697 SYNTAX Counter32 1698 UNITS "tenths of seconds" 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "A count of the total response time collected." 1703 ::= { tn3270eRtDataEntry 8 } 1705 tn3270eRtDataTotalIpRt OBJECT-TYPE 1706 SYNTAX Counter32 1707 UNITS "tenths of seconds" 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "A count of the total IP-network response time collected." 1712 ::= { tn3270eRtDataEntry 9 } 1714 tn3270eRtDataTransCount OBJECT-TYPE 1715 SYNTAX Counter32 1716 UNITS "transactions" 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "A count of the total number of transactions detected." 1721 ::= { tn3270eRtDataEntry 10 } 1723 tn3270eRtDataDrCount OBJECT-TYPE 1724 SYNTAX Counter32 1725 UNITS "transactions" 1726 MAX-ACCESS read-only 1727 STATUS current 1728 DESCRIPTION 1729 "A count of the total number of definite responses detected." 1730 ::= { tn3270eRtDataEntry 11 } 1732 tn3270eRtDataElapsRndTrpSq OBJECT-TYPE 1733 SYNTAX Unsigned32 1734 UNITS "tenths of seconds squared" 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "The sum of the elapsed round trip time squared. A sum of the 1740 Expires March 1998 [Page 34]~ 1742 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1744 squares is keep in order to calculate a variance." 1745 DEFVAL { 0 } 1746 ::= { tn3270eRtDataEntry 12 } 1748 tn3270eRtDataElapsIpRtSq OBJECT-TYPE 1749 SYNTAX Unsigned32 1750 UNITS "tenths of seconds squared" 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "The sum of the elapsed IP round trip time squared. A sum of 1755 the squares is keep in order to calculate a variance." 1756 DEFVAL { 0 } 1757 ::= { tn3270eRtDataEntry 13 } 1759 tn3270eRtDataBucket1 OBJECT-TYPE 1760 SYNTAX Counter32 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "A count of the response times falling into bucket 1." 1765 ::= { tn3270eRtDataEntry 14 } 1767 tn3270eRtDataBucket2 OBJECT-TYPE 1768 SYNTAX Counter32 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "A count of the response times falling into bucket 2." 1773 ::= { tn3270eRtDataEntry 15 } 1775 tn3270eRtDataBucket3 OBJECT-TYPE 1776 SYNTAX Counter32 1777 MAX-ACCESS read-only 1778 STATUS current 1779 DESCRIPTION 1780 "A count of the response times falling into bucket 3." 1781 ::= { tn3270eRtDataEntry 16 } 1783 tn3270eRtDataBucket4 OBJECT-TYPE 1784 SYNTAX Counter32 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "A count of the response times falling into bucket 4." 1789 ::= { tn3270eRtDataEntry 17 } 1791 tn3270eRtDataBucket5 OBJECT-TYPE 1793 Expires March 1998 [Page 35]~ 1795 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1797 SYNTAX Counter32 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "A count of the response times falling into bucket 5." 1802 ::= { tn3270eRtDataEntry 18 } 1804 -- Notifications 1806 tn3270eRtExceeded NOTIFICATION-TYPE 1807 OBJECTS { 1808 tn3270eSrvrConfIndex, -- server's local index 1809 tn3270eRtCollCtlClientGroupName, -- target of data collection 1810 tn3270eRtDataClientAddrType, 1811 tn3270eRtDataClientAddress, 1812 tn3270eRtDataIntTimeStamp, 1813 tn3270eRtDataAvgRt, 1814 tn3270eRtDataAvgIpRt, 1815 tn3270eRtDataAvgTransCount 1816 } 1817 STATUS current 1818 DESCRIPTION 1819 "This notification is generated when the average response time, 1820 tn3270eRtDataAvgRt, exceeds tn3270eRtCollCtlThresholdHigh at 1821 the end of a collection interval specified by 1822 tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult. Note that 1823 the corresponding tn3270eCollCtlType must have traps(5) and 1824 average(3) set for this notification to be generated. In 1825 addition, tn3270eRtDataAvgTransCount, 1826 tn3270eRtCollCtlThreshHigh and tn3270eRtDataAvgRt are 1827 algorithmically compared to tn3270eRtCollCtlIdleRate for 1828 determination if this will be suppressed." 1829 ::= { tn3270eRtNotifications 1 } 1831 tn3270eRtOkay NOTIFICATION-TYPE 1832 OBJECTS { 1833 tn3270eSrvrConfIndex, -- server's local index 1834 tn3270eRtCollCtlClientGroupName, -- target of data collection 1835 tn3270eRtDataClientAddrType, 1836 tn3270eRtDataClientAddress,-- IP Address or null octet string 1837 tn3270eRtDataIntTimeStamp, 1838 tn3270eRtDataAvgRt, 1839 tn3270eRtDataAvgIpRt, 1840 tn3270eRtDataAvgTransCount 1841 } 1842 STATUS current 1843 DESCRIPTION 1844 "This notification is generated when the average response time, 1846 Expires March 1998 [Page 36]~ 1848 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1850 tn3270eRtDataAvgRt, falls below tn3270eRtCollCtlThresholdLow at 1851 the end of a collection interval specified by 1852 tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult, after a 1853 tn3270eRtExceeded notification was generated. Note that the 1854 corresponding tn3270eCollCtlType must have traps(5) and 1855 average(3) set for this notification to be generated." 1856 ::= { tn3270eRtNotifications 2 } 1858 tn3270eRtCollStart NOTIFICATION-TYPE 1859 OBJECTS { 1860 tn3270eSrvrConfIndex, -- server's local index 1861 tn3270eRtCollCtlClientGroupName, -- Data collection target 1862 tn3270eRtDataClientAddrType, 1863 tn3270eRtDataClientAddress, -- IP Address or null octet string 1864 tn3270eResMapElementName, -- IDs LU or printer association 1865 tn3270eResMapElementType -- type of resource 1866 } 1867 STATUS current 1868 DESCRIPTION 1869 "This notification is generated when response time data 1870 collection is enabled for a member of a client group. In order 1871 for this notification to occur the corresponding 1872 tn3270eRtCollCtlType must have traps(5) selected. The objects 1873 tn3270eResMapElementName and tn3270eResMapElementType contains 1874 valid values only if tn3270eRtDataClientAddress contains a 1875 valid IP address (rather than the null octet string)." 1876 ::= { tn3270eRtNotifications 3 } 1878 tn3270eRtCollEnd NOTIFICATION-TYPE 1879 OBJECTS { 1880 tn3270eSrvrConfIndex, -- server's local index 1881 tn3270eRtCollCtlClientGroupName, -- data collection target 1882 tn3270eRtDataClientAddrType, 1883 tn3270eRtDataClientAddress, 1884 tn3270eRtDataDiscontinuityTime, 1885 tn3270eRtDataAvgRt, 1886 tn3270eRtDataAvgIpRt, 1887 tn3270eRtDataAvgTransCount, 1888 tn3270eRtDataIntTimeStamp, 1889 tn3270eRtDataTotalRt, 1890 tn3270eRtDataTotalIpRt, 1891 tn3270eRtDataTransCount, 1892 tn3270eRtDataDrCount, 1893 tn3270eRtDataElapsRndTrpSq, 1894 tn3270eRtDataElapsIpRtSq, 1895 tn3270eRtDataBucket1, 1896 tn3270eRtDataBucket2, 1897 tn3270eRtDataBucket3, 1899 Expires March 1998 [Page 37]~ 1901 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1903 tn3270eRtDataBucket4, 1904 tn3270eRtDataBucket5 1905 } 1906 STATUS current 1907 DESCRIPTION 1908 "This notification is generated when a tn3270eRtDataEntry is 1909 deleted after being active (actual data collected), in order to 1910 enable a management application monitoring a tn3270eRtDataTable 1911 entry to end get the entry's final values. Note that the 1912 corresponding tn3270eCollCtlType must have traps(5) set for this 1913 notification to be generated." 1914 ::= { tn3270eRtNotifications 4 } 1916 -- Conformance Statement 1918 tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 } 1919 tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 } 1921 -- Compliance statements 1923 tn3270eRtCompliance MODULE-COMPLIANCE 1924 STATUS current 1925 DESCRIPTION 1926 "The compliance statement for agents that support the 1927 TN327E-RT-MIB " 1928 MODULE -- this module 1929 MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup } 1930 OBJECT tn3270eRtCollCtlSPeriod 1931 MIN-ACCESS read-only 1932 DESCRIPTION 1933 "The agent is not required to allow the user to change 1934 the default value of this object and is allowed 1935 to use a different default." 1936 ::= {tn3270eRtCompliances 1 } 1938 -- Group definitions 1940 tn3270eRtGroup OBJECT-GROUP 1941 OBJECTS { 1942 tn3270eRtCollCtlType, 1943 tn3270eRtCollCtlSPeriod, 1944 tn3270eRtCollCtlSPMult, 1945 tn3270eRtCollCtlThreshHigh, 1946 tn3270eRtCollCtlThreshLow, 1947 tn3270eRtCollCtlIdleRate, 1948 tn3270eRtCollCtlBucketBndry1, 1949 tn3270eRtCollCtlBucketBndry2, 1950 tn3270eRtCollCtlBucketBndry3, 1952 Expires March 1998 [Page 38]~ 1954 White, Moore TN3270E Response Time Collection MIB 29 September 1997 1956 tn3270eRtCollCtlBucketBndry4, 1957 tn3270eRtCollCtlRowStatus, 1958 tn3270eRtDataDiscontinuityTime, 1959 tn3270eRtDataAvgRt, 1960 tn3270eRtDataAvgIpRt, 1961 tn3270eRtDataAvgTransCount, 1962 tn3270eRtDataIntTimeStamp, 1963 tn3270eRtDataTotalRt, 1964 tn3270eRtDataTotalIpRt, 1965 tn3270eRtDataTransCount, 1966 tn3270eRtDataDrCount, 1967 tn3270eRtDataElapsRndTrpSq, 1968 tn3270eRtDataElapsIpRtSq, 1969 tn3270eRtDataBucket1, 1970 tn3270eRtDataBucket2, 1971 tn3270eRtDataBucket3, 1972 tn3270eRtDataBucket4, 1973 tn3270eRtDataBucket5 } 1974 STATUS current 1975 DESCRIPTION 1976 "This group is mandatory for all host supporting the 1977 TN3270E-RT-MIB. " 1978 ::= { tn3270eRtGroups 1 } 1980 tn3270eRtNotGroup NOTIFICATION-GROUP 1981 NOTIFICATIONS { 1982 tn3270eRtExceeded, 1983 tn3270eRtOkay, 1984 tn3270eRtCollStart, 1985 tn3270eRtCollEnd 1986 } 1987 STATUS current 1988 DESCRIPTION 1989 "The notifications which must be supported when the 1990 TN3270E-RT-MIB is implemented. " 1991 ::= { tn3270eRtGroups 2 } 1993 END 1995 6. Security Considerations 1997 Certain management information defined in this MIB may be considered 1998 sensitive in some network environments. Therefore, authentication of 1999 received SNMP requests and controlled access to management information 2000 should be employed in such environments. The method for this 2001 authentication is a function of the SNMP Administrative Framework, and 2002 has not been expanded by this MIB. 2004 Expires March 1998 [Page 39]~ 2006 White, Moore TN3270E Response Time Collection MIB 29 September 1997 2008 Several objects in this MIB allow write access or provide for remote 2009 creation. Allowing this support in a non-secure environment can have a 2010 negative effect on network operations. It is recommended that 2011 implementers seriously consider whether set operations should be 2012 allowed without providing, at a minimum, authentication of request 2013 origin. It it recommended that without such support that the following 2014 objects be implemented as read-only: 2016 o tn3270eRtCollCtlType 2017 o tn3270eRtCollSPeriod 2018 o tn3270eRtCollSPMult 2019 o tn3270eRtCollCtlThreshHigh 2020 o tn3270eRtCollCtlThreshLow 2021 o tn3270eRtCollCtlIdleRate 2022 o tn3270eRtCollCtlBucketBndry1 2023 o tn3270eRtCollCtlBucketBndry2 2024 o tn3270eRtCollCtlBucketBndry3 2025 o tn3270eRtCollCtlBucketBndry4 2027 The following object should either be implemented as read-only or not 2028 implemented when security is an issue as previously discussed: 2030 o tn3270eRtCollCtlRowStatus 2032 The administrative method to use to create and manage the 2033 tn3270eRtCollCtlTable when SET support is not allowed is outside of 2034 the scope of this memo. 2036 7. Acknowledgments 2038 This document is a product of the TN3270E Working Group. Special 2039 thanks is due to Derek Bolton and Michael Boe of Cisco Systems for 2040 their numerous comments and suggestions for improving the structure of 2041 this MIB. 2043 8. References 2045 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2046 Waldbusser S., "Structure of Management Information for version 2 2047 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2048 January 1996. 2050 [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet 2051 Protocol Specification", RFC 854, May 1983. 2053 Expires March 1998 [Page 40]~ 2055 White, Moore TN3270E Response Time Collection MIB 29 September 1997 2057 [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing 2058 Mark Option", RFC 860, May 1983. 2060 [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", 2061 RFC 1041, January 1988. 2063 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2064 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2065 RFC 1213, Hughes LAN Systems, Performance Systems International, 2066 March 1991. 2068 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2069 Waldbusser, "Textual Conventions for version 2 of the Simple 2070 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 2072 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2073 Waldbusser, "Protocol Operations for version 2 of the Simple 2074 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2076 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2077 Waldbusser, "Conformance Statements for version 2 of the Simple 2078 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 2080 [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2081 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2082 International, MIT Laboratory for Computer Science, May 1990. 2084 [10] IETF TN3270E Working Group and White, K., "Base Definitions of 2085 Managed Objects for TN3270E Using SMIv2", Internet-Draft Work in 2086 progress, June 1997. 2088 [11] Network Working Group, and Kelly, B., "TN3270 Enhancements", RFC 2089 1647, July 1994. 2091 [12] IBM, International Technical Support Centers, "Response Time Data 2092 Gathering", GG24-3212-01, November 1990. 2094 [13] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 2096 Expires March 1998 [Page 41]~ 2098 White, Moore TN3270E Response Time Collection MIB 29 September 1997 2100 Managed Objects for Applications", April 15, 1997. 2102 9. Authors' Addresses 2104 Kenneth D. White 2105 Dept. BRQA/Bldg. 503/C117 2106 IBM Corporation 2107 P.O.Box 12195 2108 3039 Cornwallis 2109 Research Triangle Park, NC 27709, USA 2110 Phone: +1-919-254-0102 2111 E-mail: kennethw@vnet.ibm.com 2113 Robert Moore 2114 Dept. BRQA/Bldg. 501/G114 2115 IBM Corporation 2116 P.O.Box 12195 2117 3039 Cornwallis 2118 Research Triangle Park, NC 27709, USA 2119 Phone: +1-919-254-7507 2120 E-mail: remoore@us.ibm.com 2122 Expires March 1998 [Page 42]~