idnits 2.17.1 draft-ietf-tn3270e-rt-mib-02.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-20) 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 2580 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 43 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 (November 1997) is 9653 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 2085, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 2088, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 2091, 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) -- Possible downref: Non-RFC (?) normative reference: ref. '7' ** 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: 16 errors (**), 0 flaws (~~), 5 warnings (==), 6 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: May 1998 Robert Moore 5 IBM Corp. 7 November 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 May 1998 [Page 1]~ 45 White, Moore TN3270E Response Time Collection MIB 19 November 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...............................15 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..................................40 68 7.0 Acknowledgments..........................................41 69 8.0 References...............................................41 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 May 1998 [Page 2]~ 94 White, Moore TN3270E Response Time Collection MIB 19 November 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 May 1998 [Page 3]~ 142 White, Moore TN3270E Response Time Collection MIB 19 November 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 May 1998 [Page 4]~ 195 White, Moore TN3270E Response Time Collection MIB 19 November 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 A client should respond to a definite response request when it 219 completes processing the transaction. This is important since it 220 increases the accuracy of a total response time. Clients that 221 immediately respond to a definite response request will end up with 222 lower total response times then those that actually occurred. 224 The TN3270E-RT-MIB describes a method of collecting performance data 225 that is not appropriate for printer (LU Type 1 or LU Type 3) sessions; 226 thus collection of performance data for printer sessions is excluded 227 from this MIB. This exclusion of printer sessions is not considered a 228 problem, since these sessions are not the most important ones for 229 response time monitoring, and since historically they were excluded 230 from SNA/MS RTM collection. The tn3270eTcpConnResourceType object in 231 a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined to 232 determine if a client session is ineligible for response time data 233 collection. 235 3.2. TN3270E Server Response Time Collection 237 A TN3270E Server connects an IP client performing 3270 emulation to a 238 target SNA host over both an IP network (IP client to TN3270E server) 239 and an SNA Network (TN3270E server to target SNA host). A TN3270E 240 server can use SNA definite responses and the TN3270 Enhancement (RFC 241 1647 [11]) RESPONSES function to calculate response times for a 242 transaction, by timestamping when a client sends a request, when the 243 reply arrives from the target host, and when the response 245 Expires May 1998 [Page 5]~ 247 White, Moore TN3270E Response Time Collection MIB 19 November 1997 249 acknowledging this reply arrives from the client. 251 Section 3.4, Timestamp Calculation, provides specifics on when in the 252 sequence of flows between a TN3270E client and its target SNA host a 253 TN3270E server takes its timestamps. In addition, there is information 254 on how the TN3270 TIMEMARK request/response flow can be used instead 255 of DR for approximating IP network transit times. 257 The following figure adds a TN3270E server between the client, in this 258 case a TN3270E client and the target SNA host: 260 ------------------------------------------------ 261 | | 262 | Client TN3270E Target | 263 | Server SNA Host | 264 | Timestamps | 265 | | 266 | <---IP Network-------><---SNA Network---> | 267 | | 268 | request D | 269 | ------------------------------------------> | 270 | reply(DR) E | | 271 | <----------------------------------------< | 272 | | +/-RSP F | 273 | >-------------------- - - - - - - - - - > | 274 | | 275 ------------------------------------------------ 277 A TN3270E server can save timestamp D when it receives a client 278 request, save timestamp E when the target SNA host replies, and save 279 timestamp F when the client responds to the definite response request 280 that flowed with the reply. In fact, it doesn't matter whether the 281 target SNA host requested a definite response on its reply: if it 282 didn't, the TN3270E server makes the request on its own, to enable it 283 to produce timestamp F. In this case the TN3270E server does not 284 forward the response to the target SNA host, as the dotted line in the 285 figure indicates. 287 In order to generate timestamp F, a TN3270E server must insure that 288 the transaction specifies DR, and that the TN3270E RESPONSES function 289 has been negotiated between itself and the client. Negotiation of the 290 TN3270E RESPONSES function occurs during the client's TN3270E session 291 initialization. The TN3270E servers that the authors are aware of do 292 request the RESPONSES function during client session initialization. 293 TN3270E clients either automatically support the RESPONSES function, 294 or can be configured during startup to support it. 296 Expires May 1998 [Page 6]~ 298 White, Moore TN3270E Response Time Collection MIB 19 November 1997 300 Using timestamps D, E, and F the following response times can be 301 calculated by a TN3270E server: 303 o Total Response time: F - D 304 o IP Network Transit Time: F - E 306 The MIB provides an object, tn3270eRtCollCtlType, to control several 307 aspects of response time data collection. One of the available 308 options in setting up a response time collection policy is to 309 eliminate the IP-network component altogether. This might be done 310 because it is determined either that the additional IP network traffic 311 would not be desirable, or that the IP-network components of the 312 overall response times are not significant. 314 Excluding the IP-network component from response times also has an 315 implication for the way in which response time data is aggregated. A 316 TN3270E server may find that some of its clients simply don't support 317 any of the functions necessary for the server to calculate the IP- 318 network component of response times. For these clients, the most that 319 the server can calculate is the SNA-network component of their overall 320 response times; the server records this SNA-network component as the 321 TOTAL response time each of these clients' transactions. If a 322 response time collection is aggregating data from a number of clients, 323 some of which have the support necessary for including the IP-network 324 component in their total response time calculations, and some of which 325 do not, then the server aggregates the data differently depending on 326 whether the collection has been defined to include or exclude the IP- 327 network component: 329 o If the IP-network component is included, then transactions 330 for the clients that don't support calculation of the 331 IP-network component of their response times are excluded 332 from the aggregation altogether. 333 o If the IP-network component is excluded, then total response 334 times for ALL clients include only the SNA-network component, 335 even though the server could have included an IP-network 336 component in the overall response times for some of these 337 clients. The server does this by setting timestamp F, which 338 marks the end of a transaction's total response time, equal 339 to timestamp E, the end of the transaction's SNA-network 340 component. 342 The principle here is that all the transactions contributing their 343 response times to an aggregated value must make the same contribution. 344 If the aggregation specifies that an IP-network component must be 345 included in the aggregation's response times, then transactions for 346 which an IP-network component cannot be calculated aren't included at 347 all. If the aggregation specifies that an IP-network component is not 349 Expires May 1998 [Page 7]~ 351 White, Moore TN3270E Response Time Collection MIB 19 November 1997 353 to be included, then only the SNA-network component is used, even for 354 those transactions for which an IP-network component could have been 355 calculated. 357 There is one more complication here: the MIB allows a management 358 application to enable or disable dynamic definite responses for a 359 response time collection. Once again the purpose of this option is to 360 give the network operator control over the amount of traffic 361 introduced into the IP network for response time data collection. A 362 DYNAMIC definite response is one that the TN3270E server itself adds 363 to a reply, in a transaction for which the SNA application at the 364 target SNA host did not specify DR in its reply. When the +/-RSP 365 comes back from the client, the server uses this response to calculate 366 timestamp F, but then it does not forward it on to the SNA application 367 (since the application is not expecting a response to its reply). 369 This dynamic definite responses option is related to the option of 370 including or excluding the IP-network component of response times 371 (discussed above) as follows: 373 o If the IP-network component is excluded, then there is 374 no reason for enabling dynamic definite responses: the 375 server always sets timestamp F equal to timestamp E, so 376 the additional IP-network traffic elicited by a dynamic 377 definite response would serve no purpose. 378 o If the IP-network component is included, then enabling 379 dynamic definite responses causes MORE transactions to 380 be included in the aggregated response time values: 382 - For clients that do not support sending of responses, 383 timestamp F can never be calculated, and so their 384 transactions are never included in the aggregate. 385 - For clients that support sending of responses, 386 timestamp F will always be calculated for transactions 387 in which the host SNA application specifies DR in 388 its reply, and so these transactions will always be 389 included in the aggregate. 390 - For clients that support sending of responses, 391 having dynamic definite responses enabled for a 392 collection results in the inclusion of additional 393 transactions in the aggregate: specifically, those 394 for which the host SNA application did not specify 395 DR in its reply. 397 A TN3270E server also has the option of substituting TIMEMARK 398 processing for definite responses in calculating the IP-network 399 component of a transaction's response time. Once again, there is no 400 reason for the server to do this if the collection has been set up to 402 Expires May 1998 [Page 8]~ 404 White, Moore TN3270E Response Time Collection MIB 19 November 1997 406 exclude the IP-network component altogether in computing response 407 times. 409 The MIB is structured to keep for each response time the total time (F 410 - D) and the IP-network component (F - E). A management application 411 can obviously calculate from these two values a response time's SNA- 412 network component (E - D). The SNA-network component would also 413 contain the host processing time at both the TN3270E Server and at the 414 target application. As in the IP case, these response times are only 415 approximations, because the +/-RSP's crossing of the IP network is 416 substituted for that of the request that started the transaction. 418 When a TN3270E server is in the same SNA host as the target 419 application, then the SNA-network component of a transaction's 420 response time will approximately equal the host transit time (B - A) 421 described previously. A host (as opposed to a gateway) TN3270E server 422 implementation can typically support the establishment of sessions to 423 target applications in remote SNA hosts; in this case the SNA-network 424 component equals the actual SNA-network transit time plus two host 425 transit times. 427 3.3. Correlating TN3270E Server and Host Response Times 429 It is possible that response time data is collected from TN3270E 430 servers at the same time as a management application is monitoring the 431 SNA sessions at a host. For example, a management application can be 432 monitoring a secondary logical unit (SLU) while retrieving data from a 433 TN3270E server. Consider the following figure: 435 ------------------------------------------------ 436 | | 437 | Client TN3270E Target | 438 | Server SNA Host | 439 | Timestamps (PLU) | 440 | (SLU) Timestamps| 441 | <---IP Network-------><---SNA Network---> | 442 | | 443 | request D A | 444 | ------------------------------------------> | 445 | reply(DR) E B | | 446 | <----------------------------------------< | 447 | | +/-RSP F C | 448 | >--------------------------------------> | 449 | | 450 ------------------------------------------------ 452 The following response times are available: 454 Expires May 1998 [Page 9]~ 456 White, Moore TN3270E Response Time Collection MIB 19 November 1997 458 o Target SNA host transit time: B - A 459 o Target SNA host (total) network transit time: C - B 460 o TN3270E server total response time: F - D 461 o TN3270E server IP-network component: F - E 463 The value added by the TN3270E server in this situation is its 464 approximation of the IP-network component of the overall response 465 time. The IP-network component can be subtracted from the total 466 network transit time determined by monitoring the SLU to see the 467 actual SNA versus IP network transit times. 469 The MIB defined by this memo does not specifically address correlation 470 of the data it contains with response time data collected by direct 471 monitoring of SNA resources: its focus is exclusively response time 472 data collection from a TN3270E server perspective. It has, however, 473 in conjunction with the TN3270E-MIB [10], been structured to provide 474 the information necessary for correlation between TN3270E server- 475 provided response time information and that gathered from directly 476 monitoring SNA resources. 478 A management application attempting to correlate SNA resource usage to 479 IP clients can monitor either the tn3270eResMapTable or the 480 tn3270eTcpConnTable to determine resource-to-client address mappings. 481 Both of these tables are defined by the TN3270E-MIB [10]. Another 482 helpful table is the tn3270eSnaMapTable, which provides a mapping 483 between SLU names as they are known at the SSCP (VTAM) and their local 484 names at the TN3270E server. Neither the tn3270eClientGroupTable, the 485 tn3270eResPoolTable, nor the tn3270eClientResMapTable from the 486 TN3270E-MIB can be used for correlation, since the mappings defined by 487 these tables can overlap and may not provide one-to-one mappings. 489 3.4. Timestamp Calculation 491 This section goes into more detail concerning when the various 492 timestamps can be taken as the flows between a TN3270E client and its 493 target SNA host pass through a TN3270E server. In addition, 494 information is provided on how the TN3270 TIMEMARK request/response 495 flow can be used in place of DR for approximating IP network transit 496 times. 498 Expires May 1998 [Page 10]~ 500 White, Moore TN3270E Response Time Collection MIB 19 November 1997 502 3.4.1. DR Usage 504 Consider the following flow: 506 ---------------------------------------------------------- 507 | | 508 | Client TN3270E Target SNA | 509 | Server Host | 510 | Timestamps | 511 | | 512 | <---IP Network-------><---SNA Network---> | 513 | | 514 | request D (BB,CD,OIC,ER) | 515 | -------------------------------------------> | 516 | reply (FIC,ER,EB) | | 517 | <-----------------------------------------< | 518 | reply (MIC,ER) | 519 | <-----------------------------------------< | 520 | reply (MIC,ER) | 521 | <-----------------------------------------< | 522 | reply(DR) E (LIC,DR) | 523 | <-----------------------------------------< | 524 | | +/-RSP F | 525 | >----------------------------------------> | 526 | | 527 | BB : Begin Bracket ER : Response by exception | 528 | EB : End Bracket DR : Definite Response Requested | 529 | CD : Change Direction FIC : First in chain | 530 | OIC: Only in chain MIC: Middle in chain | 531 | LIC: Last in chain | 532 ---------------------------------------------------------- 534 Timestamp D is taken at the TN3270E server when a client sends data to 535 the server for forwarding to its target SNA host. This is most likely 536 when the server finds the end of record indicator in the TCP data 537 received from the client. The target SNA returns its reply in one or 538 more SNA Request Units (RUs); in this example there are four RUs in 539 the reply. The first RU is marked as first in chain (FIC), the next 540 two are marked as middle in chain (MIC), and the last is marked as 541 last in chain (LIC). Timestamp E should be taken prior to sending the 542 RESPONSES request to the client; normally this is done when the server 543 receives the LIC RU. Timestamp F is taken when the RESPONSES response 544 is received from the client. 546 A target SNA application doesn't necessarily return data to a client 547 in a transaction; it may, for example, require more data from the 548 client before it can formulate a reply. In this case the application 549 may simply return to the TN3270E server a change of direction 551 Expires May 1998 [Page 11]~ 553 White, Moore TN3270E Response Time Collection MIB 19 November 1997 555 indicator. A TCP connection is full duplex: data can be received and 556 sent on it at the same time. An SNA session, on the other hand, is 557 half duplex, with a change of direction indicator to alter the 558 direction of data flow. Timestamps E and F require a reply to flow to 559 the client. A best-effort approach should be followed by a TN3270E 560 server when it attempts to calculate timestamps. For cases where the 561 target SNA application sends a change of direction indicator rather 562 than a reply, it is suggested that the entire transaction be omitted 563 from any response time calculations. 565 Another consideration is a mismatch between DR requested on the SNA 566 side and DR requested by a TN3270E server. If the SNA host sends a 567 multiple-RU chain, the server does not know until the last RU is 568 received whether DR is being requested. Meanwhile, the server may 569 have forwarded the first RU in the chain to the client. In practice, 570 therefore, some servers convert ER flows to DR flows. Timestamp E can 571 be taken when the first RESPONSES request flows to the client, and 572 timestamp F when its response is received. In this instance an 573 additional timestamp G is needed when the LIC RU is received: 575 --------------------------------------------------- 576 | | 577 | Client TN3270E Target | 578 | Server SNA Host | 579 | Timestamps | 580 | | 581 | <---IP Network-------><---SNA Network---> | 582 | | 583 | request D (BB,CD,OIC,ER) | 584 | ------------------------------------------> | 585 | reply(DR) E (FIC,ER,EB) | | 586 | <----------------------------------------< | 587 | | +/-RSP F | 588 | >-------------------> | 589 | reply (MIC,ER) | 590 | <----------------------------------------< | 591 | reply (MIC,ER) | 592 | <----------------------------------------< | 593 | reply(DR) (LIC,DR) | 594 | <----------------------------------------< | 595 | | +/-RSP G | 596 | >-------------------> | 597 | | 598 --------------------------------------------------- 600 The response times can then be calculated as follows: 602 o Total response time: G - D 604 Expires May 1998 [Page 12]~ 606 White, Moore TN3270E Response Time Collection MIB 19 November 1997 608 o IP network transit time: F - E 610 If DR is requested by the LIC RU, then the TN3270E server can use 611 either its response or the earlier one for approximating IP network 612 transit time. 614 3.4.2. TIMEMARK Usage 616 It is possible for a TN3270E server to use the TIMEMARK flow for 617 approximating IP network transit times. Using TIMEMARKs would make it 618 possible for a server to collect performance data for TN3270 clients, 619 as well as for TN3270E clients that do not support the RESPONSES 620 function. In order for TIMEMARKs to be used in this way, a client 621 can't have the NOP option enabled, since responses are needed to the 622 server's TIMEMARK requests. An IP network transit time approximation 623 using a TIMEMARK is basically the amount of time it takes for a TN3270 624 server to receive a response from a client to a TIMEMARK request. 626 If a TN3270 server is performing the TIMEMARK function (independent of 627 the response time monitoring use of the function discussed here), then 628 it most likely has a TIMEMARK interval for determining when to examine 629 client sessions for sending the TIMEMARK request. (This interval, 630 which is ordinarily a global value for an entire TN3270E server, is 631 represented in the TN3270E-MIB by the tn3270eSrvrConfActivityInterval 632 object.) A TIMEMARK request is sent only if, when it is examined, a 633 client session is found to have had no activity for a different length 634 of time, represented in the TN3270E-MIB by the 635 tn3270eSrvrConfActivityTimeout object. 637 If a TN3270E server sends a TIMEMARK request to every client with no 638 session activity, based solely on the server's TIMEMARK interval, then 639 network flooding may result, since a server may be supporting 640 thousands of client sessions. The use of TIMEMARKs for response time 641 monitoring could help to reduce this network flooding. Suppose a 642 server sends a TIMEMARK request to a client after a LIC RU has been 643 received, as a means of approximating IP network transit time: 645 Expires May 1998 [Page 13]~ 647 White, Moore TN3270E Response Time Collection MIB 19 November 1997 649 --------------------------------------------------- 650 | | 651 | Client TN3270E Target | 652 | Server Host | 653 | Timestamps | 654 | | 655 | <---IP Network-------><---SNA Network---> | 656 | | 657 | request D (BB,CD,OIC,ER) | 658 | -------------------------------------------> | 659 | reply (FIC,ER,EB) | | 660 | <-----------------------------------------< | 661 | reply (MIC,ER) | 662 | <-----------------------------------------< | 663 | reply (MIC,ER) | 664 | <-----------------------------------------< | 665 | reply(DR) (LIC,ER) | 666 | <-----------------------------------------< | 667 | TIMEMARK Rqst E | 668 | <--------------------- | 669 | | TIMEMARK Rsp F | 670 | >-------------------> | 671 | | 672 --------------------------------------------------- 674 The response times can then be calculated as follows: 676 o TN3270E server total response time: F - D 677 o TN3270E server IP network time: F - E 679 A TN3270E server would need to consider its normal TIMEMARK processing 680 when using TIMEMARKs for this purpose. For example, it must not send a 681 second TIMEMARK request to a client while waiting for the first to 682 return. Also, if a TIMEMARK flow has just been performed for a client 683 shortly before the LIC RU arrives, the server might use the interval 684 from this flow as its approximation for IP network transit time; in 685 this case the server would have to remember to add the interval from 686 this TIMEMARK flow (F' - E') to the interval from the transaction (E - 687 D) to get its approximation for the transaction's total response time. 689 The most accurate approach would be to send the TIMEMARK request after 690 the last RU was sent to the client since the resulting total response 691 time should include any transaction processing time at the client. 692 The actually accuracy of the total response time depends on when the 693 client responds to the TIMEMARK request. 695 Expires May 1998 [Page 14]~ 697 White, Moore TN3270E Response Time Collection MIB 19 November 1997 699 3.5. Performance Data Modelling 701 The following two subsections detail how the TN3270E-RT-MIB models and 702 controls capture of two types of response time data: average response 703 times and response time buckets. 705 3.5.1. Averaging Response Times 707 Average response times play two different roles in the MIB: 709 o They are made available for management applications to retrieve. 710 o They serve as triggers for emitting notifications. 712 Sliding-window averages are used rather than straight interval-based 713 averages, because they are often more meaningful, and because they 714 cause less notification thrashing. Sliding-window average calculation 715 can, if necessary, be disabled, by setting the sample period 716 multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample 717 period, tn3270eRtCollCtlSPeriod, to the required collection interval. 719 In order to calculate sliding-window averages, a TN3270E server must: 721 o Select a fixed, relative short, sample period SPeriod; the 722 default value for SPeriod in the MIB is 20 seconds. 724 o Select an averaging period multiplier SPMult. The actual 725 collection interval will then be SPMult times SPeriod. The 726 default value for SPMult in the MIB is 30, yielding a default 727 collection interval of 10 minutes. Note that the collection 728 interval (SPMult*SPeriod) is always a multiple of the sample 729 period. 731 o Maintain the following counters to keep track of activity within 732 the current sample period; these are internal counters, not 733 made visible to a management application via the MIB. 735 - T (number of transactions in the period) 736 - TotalRt (sum of the total response times for all 737 transactions in the period) 738 - TotalIpRt (sum of the IP network transit times for 739 all transactions in the period; note that if IP 740 network transit times are being excluded from the 741 response time collection, this value will always be 0). 743 o Also maintain sliding counters, initialized to zero, for each 744 of the quantities being counted: 746 Expires May 1998 [Page 15]~ 748 White, Moore TN3270E Response Time Collection MIB 19 November 1997 750 - AvgTransCount (sliding count of transactions) 751 - TotalRtSliding (sliding count of total response times) 752 - TotalIpRtSliding (sliding count of IP network transit times) 754 o At the end of each sample period, update the sliding counters: 756 AvgTransCount = AvgTransCount + T 757 - (AvgTransCount / SPMult) 759 TotalRtSliding = TotalRtSliding + TotalRt 760 - (TotalRtSliding / SPMult) 762 TotalIpRtSliding = TotalIpRtSliding + TotalIpRt 763 - (TotalIpRtSliding / SPMult) 765 Then reset T, TotalRt, and TotalIpRt to zero for use during the 766 next sample period. 768 o At the end of a collection interval, update the following MIB 769 objects as indicated: 771 tn3270eRtDataAvgTransCount = AvgTransCount 772 tn3270eRtDataAvgRt = TotalRtSliding / AvgTransCount 773 tn3270eRtDataAvgIpRt = TotalIpRtSliding / AvgTransCount 775 As expected, if IP network transit times are being excluded 776 from response time collection, then tn3270eRtDataAvgIpRt 777 will always return 0. 779 The sliding transaction counter AvgTransCount is not used for updating 780 the MIB object tn3270eRtDataTransCount: this object is an ordinary 781 SMI Counter32, which maintains a total count of transactions since its 782 last discontinuity event. The sliding counters are used only for 783 calculating averages. 785 Two mechanisms are present in the MIB to inhibit the generation of an 786 excessive number of notifications related to average response times. 787 First, there are high and low thresholds for average response times. A 788 tn3270eRtExceeded notification is generated the first time a 789 statistically significant average response time is found to have 790 exceeded the high threshold. After this, no other tn3270eRtExceeded 791 notifications are generated until an average response time is found to 792 have fallen below the low threshold. 794 The other mechanism to limit notifications is the significance test 795 for a high average response time. Intuitively, the significance of an 796 average is directly related to the number of samples that go into it; 797 so we might be inclined to use a rule such as "for the purpose of 799 Expires May 1998 [Page 16]~ 801 White, Moore TN3270E Response Time Collection MIB 19 November 1997 803 generating tn32709eRtExceeded notifications, ignore average response 804 times based on fewer than 20 transactions in the sample period." 806 In the case of response times, however, the number of transactions 807 sampled in a fixed sampling period is tied to these transactions' 808 response times. A few transactions with long response times can 809 guarantee that there will not be many transactions in a sample, 810 because these transactions "use up" the sampling time. Yet this case 811 of a few transactions with very poor response times should obviously 812 be classified as a problem, not as a statistical anomaly based on too 813 small a sample. 815 The solution is to make the significance level for a sample a function 816 of the average response time. In order to determine at a collection 817 interval whether to generate a tn3270eRtExceeded notification, a 818 TN3270E server uses the following algorithm: 820 if AvgTransCount * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 821 then generate the notification 823 Two examples illustrate how this algorithm works. Suppose that 824 IdleRate has been set to 20 transactions, and the high threshold to 825 200 msecs per transaction. If the average observed response time is 826 300 msecs, then a notification will be generated only if AvgTransCount 827 >= 80. If, however, the observed response time is 500 msecs, then a 828 notification is generated if AvgTransCount >= 9. 830 There is no corresponding significance test for the tn3270eRtOkay 831 notification: this notification is generated based on an average 832 response time that falls below the low threshold, regardless of the 833 sample size behind that average. 835 3.5.2. Response Time Buckets 837 The MIB also supports collection of response time data into a set of 838 five buckets. This data is suitable either for verification of service 839 level agreements, or for monitoring by a management application to 840 identify performance problems. The buckets provide counts of 841 transactions whose total response times fall into a set of specified 842 ranges. 844 Like everything for a collection, the "total" response times collected 845 in the buckets are governed by the specification of whether IP network 846 transit times are to be included in the totals. Depending on how this 847 option is specified, the response times being counted in the buckets 848 will either be total response times (F - D), or only SNA network 849 transit times (effectively E - D, because when it is excluding the 851 Expires May 1998 [Page 17]~ 853 White, Moore TN3270E Response Time Collection MIB 19 November 1997 855 IP-network component of transactions, a server makes timestamp F 856 identical to timestamp E). 857 Four bucket boundaries are specified for a response time collection, 858 resulting in five buckets. The first response time bucket counts those 859 transactions whose total response times were less than or equal to 860 Boundary 1, the second bucket counts those whose response times were 861 greater than Boundary 1 but less than or equal to Boundary 2, and so 862 on. The fifth bucket is unbounded on the top, counting all 863 transactions whose response times were greater than Boundary 4. 865 The four bucket boundaries have default values of: 1 second, 2 866 seconds, 5 seconds, and 10 seconds, respectively. These values are 867 the defaults in the 3174 controller's implementation of the SNA/MS RTM 868 function, and were thought to be appropriate for this MIB as well. 870 In SNA/MS the counter buckets were (by today's standards) relatively 871 small, with a maximum value of 65,535. The bucket objects in the MIB 872 are all Counter32's. 874 The following figure represents the buckets pictorially: 876 ---------------------------------------------- 877 | | 878 | Response Time Boundaries | 879 | | | | | | | | 880 | | | | | | | | 881 | | | | | | no | 882 | 0 B-1 B-2 B-3 B-4 bound| 883 | | | | | | | | 884 | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| | 885 | ----------------------------------------- | 886 | | 887 ---------------------------------------------- 889 4. Structure of the MIB 891 The TN3270E-RT-MIB has the following components: 893 o tn3270eRtCollCtlTable 894 o tn3270eRtDataTable 895 o Notifications 897 4.1. tn3270eRtCollCtlTable 899 The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex, imported 900 from the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. 902 Expires May 1998 [Page 18]~ 904 White, Moore TN3270E Response Time Collection MIB 19 November 1997 906 tn3270eSrvrConfIndex identifies within a host a particular TN3270E 907 server. tn3270eRtCollCtlClientGroupName identifies a collection of IP 908 clients for which response time data is to be collected. The 909 collection itself is defined using the tn3270eClientGroupTable from 910 the TN3270E-MIB. The index from the tn3270eClientGroupTable, 911 tn3270eClientGroupName, was not used directly, since doing so causes 912 an inconsistent indexing scheme error in some MIB compilers. To avoid 913 this error, tn3270eRtCollCtlClientGroupName was defined directly in 914 the tn3270eRtCollCtlEntry. 916 A tn3270eRtCollCtlEntry contains the following objects: 918 -------------------------------------------------- 919 1st Index | tn3270eSrvrConfIndex Unsigned32 | 920 2nd Index | tn3270eRtCollCtlClientGroupName Utf8String | 921 | tn3270eRtCollCtlType BITS | 922 | tn3270eRtCollCtlSPeriod Unsigned32 | 923 | tn3270eRtCollCtlSPMult Unsigned32 | 924 | tn3270eRtCollCtlThreshHigh Unsigned32 | 925 | tn3270eRtCollCtlThreshLow Unsigned32 | 926 | tn3270eRtCollCtlIdleRate Unsigned32 | 927 | tn3270eRtCollCtlBucketBndry1 Unsigned32 | 928 | tn3270eRtCollCtlBucketBndry2 Unsigned32 | 929 | tn3270eRtCollCtlBucketBndry3 Unsigned32 | 930 | tn3270eRtCollCtlBucketBndry4 Unsigned32 | 931 | tn3270eRtCollCtlRowStatus RowStatus | 932 -------------------------------------------------- 934 The tn3270eRtCollCtlType object controls the type(s) of response time 935 collection that occur, the granularity of the collection, whether 936 dynamic definite responses should be initiated, and whether 937 notifications should be generated. This object is of BITS SYNTAX, and 938 thus allows selection of multiple options. 940 The BITS in the tn3270eRtCollCtlType object have the following 941 meanings: 943 o aggregate(0) - If this bit is set to 1, then data should be 944 aggregated for the whole client group. In this case there will 945 be only one row created for the collection in the 946 tn3270eRtDataTable. The first two indexes for this row, 947 tn3270eSrvrConfIndex and tn3270eRtCollCtlClientGroupName, will 948 have the same values as the indexes for this row in the 949 tn3270eRtCollCtlTable. The third and fourth indexes for an 950 aggregated tn3270eRtDataEntry have the values 'unknown(0)' 951 (for tn3270eRtDataClientAddrType) and a null octet string 952 (for tn3270eRtDataClientAddress). 954 Expires May 1998 [Page 19]~ 956 White, Moore TN3270E Response Time Collection MIB 19 November 1997 958 If this bit is set to 0, then a separate entry is created in the 959 tn3270eRtDataTable for each member of the client group. In this 960 case the tn3270eRtDataClientAddress contains the client's actual 961 IP Address, and tn3270eRtDataClientAddrType indicates the type 962 of this address. 964 o excludeIpComponent(1) - If this bit is set to 1, then the 965 server should exclude the IP-network component from all the 966 response times for this collection. If the target SNA 967 application specifies DR in any of its replies, this DR will 968 still be passed down to the client, and the client's response 969 will still be forwarded to the application. But this response 970 will play no role in the server's response time calculations. 972 If this bit is set to 0, then the server includes in the 973 collection only those transactions for which it can include an 974 (approximate) IP-network component in the total response time 975 for the transaction. This component may be derived from a 976 "natural" DR (if the client supports the RESPONSES function), 977 from a dynamic DR introduced by the server (if the client 978 supports the RESPONSES function and the ddr(2) bit has been 979 set to 1), or from TIMEMARK processing (if the client supports 980 TIMEMARKs). 982 If this bit is set to 1, then the ddr(2) bit is ignored, since 983 there is no reason for the server to request additional 984 responses from the client(s) in the group. 986 o ddr(2) - If this bit is set to 1, then the server should, for 987 those clients in the group that support the RESPONSES function, 988 add a DR request to a reply in each transaction (usually, but 989 not necessarily the LIC reply), and use the client's subsequent 990 response for calculating an (approximate) IP-network component 991 to include in the transaction's total response times. 993 If this bit is set to 0, then the server does not add a DR 994 request to any replies from the target SNA application. 996 If the excludeIpComponent(1) bit is set to 1, then this bit is 997 ignored by the server. 999 o average(3) - If this bit is set to 1, then the server should 1000 calculate a sliding-window average for the collection, based 1001 on the parameters specfied for the group. 1003 If this bit is set to 0, then an average is not calculated. In 1004 this case the tn3270eRtExceeded and tn3270eRtOkay notifications 1005 are not generated, even if the traps(5) bit is set to 1. 1007 Expires May 1998 [Page 20]~ 1009 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1011 o buckets(4) - If this bit is set to 1, then the server should 1012 create and increment response time buckets for the collection, 1013 based on the parameters specified for the group. 1015 If this bit is set to 0, then response time buckets are not 1016 created. 1018 o traps(5) - If this bit is set to 1, then the server generates 1019 the notifications defined in this MIB. The tn3270CollStart and 1020 tn3270CollEnd notifications are always generated when this bit 1021 is set to 1; the tn3270eRtExceeded and tn3270eRtOkay 1022 notifications are generated only if the average(3) bit is also 1023 set to 1. 1025 If this bit is set to 0, then none of the notifications defined 1026 in this MIB are generated by the server. 1028 Either the average(3) or the buckets(4) bit must be set to 1 in order 1029 for response time data collection to occur. If the average(3) bit is 1030 set to 1, then the following objects have meaning, and are used to 1031 control the calculation of the averages, as well as the generation of 1032 the two notifications related to them: 1034 o tn3270eRtCollCtlSPeriod 1035 o tn3270eRtCollCtlSPMult 1036 o tn3270eRtCollCtlThreshHigh 1037 o tn3270eRtCollCtlThreshLow 1038 o tn3270eRtCollCtlIdleRate 1040 If the buckets(4) bit is set to 1, then the following objects have 1041 meaning, and specify the bucket boundaries: 1043 o tn3270eRtCollCtlBucketBndry1 1044 o tn3270eRtCollCtlBucketBndry2 1045 o tn3270eRtCollCtlBucketBndry3 1046 o tn3270eRtCollCtlBucketBndry4 1048 4.2. tn3270eRtDataTable 1050 Either a single entry or multiple entries are created in the 1051 tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on 1052 whether tn3270eRtCollCtlType in the control entry has aggregate(0) 1053 selected. The contents of an entry in the tn3270eRtDataTable depend 1054 on the contents of the corresponding entry in the 1055 tn3270eRtCollCtlTable: some objects in the data entry return 1056 meaningful values only when the average(3) option is selected in the 1058 Expires May 1998 [Page 21]~ 1060 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1062 control entry, while others return meaningful values only when the 1063 buckets(4) option is selected. If both options are selected, then all 1064 the objects return meaningful values. When an object is not specified 1065 to return a meaningful value, an implementation may return any value 1066 in response to a Get operation. 1068 The following objects return meaningful values if and only if the 1069 average(3) option was selected in the corresponding 1070 tn3270eRtCollCtlEntry: 1072 o tn3270eRtDataAvgRt 1073 o tn3270eRtDataAvgIpRt 1074 o tn3270eRtDataAvgTransCount 1075 o tn3270eRtDataIntTimeStamp 1076 o tn3270eRtDataTotalRt 1077 o tn3270eRtDataTotalIpRt 1078 o tn3270eRtDataTransCount 1079 o tn3270eRtDataDrCount 1080 o tn3270eRtDataElapsRndTrpSq 1081 o tn3270eRtDataElapsIpRtSq 1083 The first three objects in this list return values derived from the 1084 sliding-window average calculations described earlier. The time of 1085 the most recent sample for these calculations is returned in the 1086 tn3270eRtDaraIntTimeStamp object. The next four objects are normal 1087 Counter32 objects, maintaining counts of total response time and total 1088 transactions. The last two objects return sum of the squares values, 1089 to enable variance calculations by a management application. 1091 The following objects return meaningful values if and only if the 1092 buckets(4) option was selected in the corresponding 1093 tn3270eRtCollCtlEntry: 1095 o tn3270eRtDataBucket1 1096 o tn3270eRtDataBucket2 1097 o tn3270eRtDataBucket3 1098 o tn3270eRtDataBucket4 1099 o tn3270eRtDataBucket5 1101 A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used by 1102 a management application to detect when the values of the counter 1103 objects in this table may have been reset, or otherwise experienced a 1104 discontinuity. A possible cause for such a discontinuity is the 1105 TN3270E server's being stopped or restarted. This object returns a 1106 meaningful value regardless of which collection control options were 1107 selected. 1109 An object, tn3270eRtDataRtMethod, identifies whether the IP Network 1111 Expires May 1998 [Page 22]~ 1113 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1115 Time was calculated using either the definite response or TIMEMARK 1116 approach. 1118 When an entry is created in the tn3270eRtCollCtlTable with its 1119 tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is 1120 automatically created in the tn3270eRtDataTable; this entry's 1121 tn3270eRtDataClientAddress has the value of a null octet string, and 1122 its tn3270eRtDataClientAddrType has the value of unknown(0). 1124 When an entry is created in the tn3270eRtCollCtlTable with its 1125 tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is 1126 created in the tn3270eRtDataTable for each member of the client group 1127 that currently has a session with the TN3270E server. Entries are 1128 subsequently created for clients that the TN3270E server determines to 1129 be members of the client group when these clients establish sessions 1130 with the server. 1132 All entries associated with a tn3270eRtCollCtlEntry are deleted from 1133 the tn3270eRtDataTable when that entry is deleted from the 1134 tn3270eRtCollCtlTable. An entry for an individual client in a client 1135 group is deleted when its TCP connection terminates. 1137 4.3. Notifications 1139 This MIB defines four notifications related to a tn3270eRtDataEntry. 1140 If the associated tn3270eRtCollCtlType object's traps(5) bit is set to 1141 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications are 1142 generated when, respsectively, the tn3270eRtDataEntry is created and 1143 deleted. If, in addition, this tn3270eRtCollCtlType object's 1144 average(3) bit is set to 1, then the the tn3270eRtExceeded and 1145 tn3270eRtOkay notifications are generated when the conditions they 1146 report occur. 1148 The following notifications are defined by this MIB: 1150 o tn3270eRtExceeded - The purpose of this notification is to 1151 signal that a performance problem has been detected. If 1152 average(3) response time data is being collected, then this 1153 notification is generated whenever (1) an average response 1154 time is first found, on a collection interval boundary, to 1155 have exceeded the high threshold tn3270eRtCollCtlThreshHigh 1156 specified for the client group, AND (2) the sample on which the 1157 average is based is determined to have been a significant one, 1158 via the significance algorithm described earlier. This 1159 notification is not generated again for a tn3270eRtDataEntry 1160 until an average response time falling below the low 1161 threshold tn3270eRtCollCtlThreshLow specified for the client 1163 Expires May 1998 [Page 23]~ 1165 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1167 group has occured for the entry. 1169 o tn3270eRtOkay - The purpose of this notification is to signal 1170 that a previously reported performance problem has been 1171 resolved. If average(3) response time data is being collected, 1172 then this notification is generated whenever (1) a 1173 tn3270eRtExceeded notification has already been generated, AND 1174 (2) an average response time is first found, on a collection 1175 interval boundary, to have fallen below the low threshold 1176 tn3270eRtCollCtlThreshLow specified for the client group. 1177 This notification is not generated again for a 1178 tn3270eRtDataEntry until an average response time 1179 exceeding the high threshold tn3270eRtCollCtlThreshHigh 1180 specified for the client group has occurred for the entry. 1182 Taken together, the two preceding notifications serve to minimize the 1183 generation of an excessive number of traps in the case of an average 1184 response time that oscillates about its high threshold. 1186 o tn3270eRtCollStart - This notification is generated whenever 1187 data collection begins for a client group, or when a new 1188 tn3270eRtDataEntry becomes active. The primary purpose of 1189 this notification is signal to a management application that 1190 a new client TCP session has been established, and to provide 1191 the IP-to-resource mapping for the session. This notification 1192 is not critical when average(3) data collection is not being 1193 performed for the client group. 1195 o tn3270eRtCollEnd - This notification is generated whenever 1196 a data collection ends. For an aggregate collection, this 1197 occurs when the corresponding tn3270eRtCollCtlEntry is 1198 deleted. For an individual collection, this occurs either 1199 when the tn3270eRtCollCtlEntry is deleted, or when the 1200 client's TCP connection terminates. The purpose of this 1201 notification is to enable a management application to 1202 complete a monitoring function that it was performing, by 1203 returning final values for the collection's data objects. 1205 5. Definitions 1207 TN3270E-RT-MIB DEFINITIONS ::= BEGIN 1209 IMPORTS 1210 -- Some MIB Compilers require BITS to be imported from 1211 -- the SNMPv2-SMI 1212 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 1213 Counter32, Unsigned32, Gauge32 1215 Expires May 1998 [Page 24]~ 1217 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1219 FROM SNMPv2-SMI 1220 RowStatus, DateAndTime, TimeStamp 1221 FROM SNMPv2-TC 1222 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1223 FROM SNMPv2-CONF 1224 Tn3270eAddrType, Tn3270eTAddress, tn3270eSrvrConfIndex, 1225 tn3270eResMapElementName, tn3270eResMapElementType 1226 FROM TN3270E-MIB 1227 snanauMIB 1228 FROM SNA-NAU-MIB 1229 Utf8String 1230 FROM SYSAPPL-MIB; 1232 tn3270eRtMIB MODULE-IDENTITY 1233 LAST-UPDATED "9711200000Z" -- November 20, 1997 1234 ORGANIZATION "TN3270E Working Group" 1235 CONTACT-INFO 1236 "Kenneth White (kennethw@vnet.ibm.com) 1237 IBM Corp. - Dept. BRQA/Bldg. 501/G114 1238 P.O. Box 12195 1239 3039 Cornwallis 1240 RTP, NC 27709-2195 1241 (919) 254-0102 1243 Robert Moore (remoore@us.ibm.com) 1244 IBM Corp. - Dept. BRQA/Bldg. 501/G114 1245 P.O. Box 12195 1246 3039 Cornwallis 1247 RTP, NC 27709-2195 1248 (919) 254-4436" 1249 DESCRIPTION 1250 "This module defines a portion of the management information 1251 base (MIB) that enables monitoring of TN3270 and TN3270E 1252 clients' response times by a TN3270E server." 1253 ::= { snanauMIB 9 } 1255 -- Top level structure of the MIB 1257 tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 } 1258 tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 } 1259 tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 } 1261 -- MIB Objects 1263 -- Response Time Control Table 1265 tn3270eRtCollCtlTable OBJECT-TYPE 1266 SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry 1268 Expires May 1998 [Page 25]~ 1270 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "The response time monitoring collection control table, which 1276 allows a management application to control the types of 1277 response time data being collected, and the clients for which 1278 it is being collected. 1280 This table is indexed by tn3270eSrvrConfIndex, imported from 1281 the TN3270E-MIB, and by tn3270eRtCollCtlClientGroupName. 1282 tn3270eSrvrConfIndex indicates within a host which TN3270E 1283 server an entry applied to. 1285 tn3270eRtCollCtlClientGroupName is equivalent to the 1286 tn3270eClientGroupName index in the TN3270E-MIB; it identifies 1287 the collection of IP clients for which response time data 1288 is being collectedr. The particular IP clients making up the 1289 collection are identified in the tn3270eClientGroupTable in 1290 the TN3270E-MIB." 1291 ::= { tn3270eRtObjects 1} 1293 tn3270eRtCollCtlEntry OBJECT-TYPE 1294 SYNTAX Tn3270eRtCollCtlEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "Entry in the TN3270E response time monitoring collection 1299 control table. To handle the case of multiple TN3270E servers 1300 on the same host, the first index of this table is the 1301 tn3270eSrvrConfIndex from the TN3270E-MIB." 1302 INDEX { 1303 tn3270eSrvrConfIndex, -- Server's index 1304 tn3270eRtCollCtlClientGroupName } -- What to collect on 1305 ::= { tn3270eRtCollCtlTable 1 } 1307 Tn3270eRtCollCtlEntry ::= SEQUENCE { 1308 tn3270eRtCollCtlClientGroupName Utf8String, 1309 tn3270eRtCollCtlType BITS, 1310 tn3270eRtCollCtlSPeriod Unsigned32, 1311 tn3270eRtCollCtlSPMult Unsigned32, 1312 tn3270eRtCollCtlThreshHigh Unsigned32, 1313 tn3270eRtCollCtlThreshLow Unsigned32, 1314 tn3270eRtCollCtlIdleRate Unsigned32, 1315 tn3270eRtCollCtlBucketBndry1 Unsigned32, 1316 tn3270eRtCollCtlBucketBndry2 Unsigned32, 1317 tn3270eRtCollCtlBucketBndry3 Unsigned32, 1318 tn3270eRtCollCtlBucketBndry4 Unsigned32, 1319 tn3270eRtCollCtlRowStatus RowStatus } 1321 Expires May 1998 [Page 26]~ 1323 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1325 tn3270eRtCollCtlClientGroupName OBJECT-TYPE 1326 SYNTAX Utf8String (SIZE(1..24)) 1327 MAX-ACCESS not-accessible 1328 STATUS current 1329 DESCRIPTION 1330 "The name of a client group. Membership in a client group is 1331 specified via the TN3270E-MIB's tn3270eClientGroupTable. 1332 The index for that table, tn3270eClientGroupName, is 1333 equivalent to this object; it was not imported because 1334 doing so results in MIB compiler errors." 1336 ::= { tn3270eRtCollCtlEntry 1 } 1338 tn3270eRtCollCtlType OBJECT-TYPE 1339 SYNTAX BITS { 1340 aggregate(0), 1341 excludeIpComponent(1), 1342 ddr(2), 1343 average(3), 1344 buckets(4), 1345 traps(5) 1346 } 1347 MAX-ACCESS read-create 1348 STATUS current 1349 DESCRIPTION 1350 "This object controls what types of response time data to 1351 collect, whether to summarize the data across the members 1352 of a client group or keep it individually, whether to 1353 introduce dynamic definite responses, and whether to 1354 generate traps. 1356 aggregate(0) - Aggregate response time data for the 1357 client group as a whole. If this bit is 1358 set to 0, then maintain response time 1359 data separately for each member of the 1360 client group. 1361 excludeIpComponent(1) - Do not include the IP-network component 1362 in any response times. 1363 ddr(2) - Enable dynamic definite response. 1364 average(3) - Produce an average response time based 1365 on a specified collection interval. 1366 buckets(4) - Maintain tn3270eRtDataBucket values in 1367 a corresponding tn3270eRtDataEntry, 1368 based on the bucket boundaries 1369 specified in the 1370 tn3270eRtDataBucketBndry objects. 1371 traps(5) - generate the traps specified in this 1372 MIB module. The tn3270eRtExceeded and 1374 Expires May 1998 [Page 27]~ 1376 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1378 tn3270eRtOkay are generated only if 1379 average(3) is also specified." 1380 ::= { tn3270eRtCollCtlEntry 2 } 1382 tn3270eRtCollCtlSPeriod OBJECT-TYPE 1383 SYNTAX Unsigned32 -- 15 second minimum to 24 hour max 1384 UNITS "seconds" 1385 MAX-ACCESS read-create 1386 STATUS current 1387 DESCRIPTION 1388 "The number of seconds that defines the sample period. 1389 The actual interval is defined as tn3270eRtCollCtlSPeriod 1390 times tn3270eRtCollCtlSPMult. 1392 The value of this object is used only if the corresponding 1393 tn3270eRtCollCtlType has the average(3) setting." 1394 DEFVAL {20} -- 20 seconds 1395 ::= { tn3270eRtCollCtlEntry 3 } 1397 tn3270eRtCollCtlSPMult OBJECT-TYPE 1398 SYNTAX Unsigned32 -- should be > 1 1399 UNITS "count" 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "The sample period multiplier; this value is multiplied by the 1404 sample period, tn3270eRtCollCtlSPeriod, to determine the 1405 collection interval. 1407 The value of this object is used only if the corresponding 1408 tn3270eRtCollCtlType has the average(3) setting." 1409 DEFVAL { 30 } -- yields an interval of 10 minutes when 1410 -- used with the default SPeriod value 1411 ::= { tn3270eRtCollCtlEntry 4 } 1413 tn3270eRtCollCtlThreshHigh OBJECT-TYPE 1414 SYNTAX Unsigned32 1415 UNITS "seconds" 1416 MAX-ACCESS read-create 1417 STATUS current 1418 DESCRIPTION 1419 "The threshold for generating a tn3270eRtExceeded notification, 1420 signalling that a monitored total response time has exceeded the 1421 specified limit. A value of zero for this object suppresses 1422 generation of this notification. The value of this object is 1423 used only if the corresponding tn3270eRtCollCtlType has 1424 average(3) and traps(5) selected." 1425 ::= { tn3270eRtCollCtlEntry 5 } 1427 Expires May 1998 [Page 28]~ 1429 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1431 tn3270eRtCollCtlThreshLow OBJECT-TYPE 1432 SYNTAX Unsigned32 1433 UNITS "seconds" 1434 MAX-ACCESS read-create 1435 STATUS current 1436 DESCRIPTION 1437 "The threshold for generating a tn3270eRtOkay notification, 1438 signalling that a monitored total response time has fallen below 1439 the specified limit. A value of zero for this object suppresses 1440 generation of this notification. The value of this object is 1441 used only if the corresponding tn3270eRtCollCtlType has 1442 average(3) and traps(5) selected." 1443 ::= { tn3270eRtCollCtlEntry 6 } 1445 tn3270eRtCollCtlIdleRate OBJECT-TYPE 1446 SYNTAX Unsigned32 1447 UNITS "transaction count" 1448 MAX-ACCESS read-create 1449 STATUS current 1450 DESCRIPTION 1451 "The value of this object is used to determine whether a sample 1452 that yields an average response time exceeding the value of 1453 tn3270eRtCollCtlThreshHigh was a statistically valid one. If 1454 the following statement is true, then the sample was 1455 statistically valid, and so a tn3270eRtExceeded notification 1456 should be generated: 1458 AvgTransCount * ((AvgRt/ThreshHigh - 1) ** 2) < IdleRate 1460 This comparison is done only if the corresponding 1461 tn3270eRtCollCtlType has average(3) and traps(5) selected." 1462 DEFVAL { 1 } 1463 ::= { tn3270eRtCollCtlEntry 7 } 1465 tn3270eRtCollCtlBucketBndry1 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 defines the range of transaction 1472 response times counted in the Tn3270eRtDataBucket1 object: 1473 those less than or equal to this value." 1474 DEFVAL { 10 } 1475 ::= { tn3270eRtCollCtlEntry 8 } 1477 tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE 1478 SYNTAX Unsigned32 1480 Expires May 1998 [Page 29]~ 1482 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1484 UNITS "tenths of seconds" 1485 MAX-ACCESS read-create 1486 STATUS current 1487 DESCRIPTION 1488 "The value of this object, together with that of the 1489 tn3270eRtCollCtlBucketBndry1 object, defines the range of 1490 transaction response times counted in the Tn3270eRtDataBucket2 1491 object: those greater than the value of the 1492 tn3270eRtCollCtlBucketBndry1 object, and less than or equal to 1493 the value of this object." 1494 DEFVAL { 20 } 1495 ::= { tn3270eRtCollCtlEntry 9 } 1497 tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE 1498 SYNTAX Unsigned32 1499 UNITS "tenths of seconds" 1500 MAX-ACCESS read-create 1501 STATUS current 1502 DESCRIPTION 1503 "The value of this object, together with that of the 1504 tn3270eRtCollCtlBucketBndry2 object, defines the range of 1505 transaction response times counted in the Tn3270eRtDataBucket3 1506 object: those greater than the value of the 1507 tn3270eRtCollCtlBucketBndry2 object, and less than or equal to 1508 the value of this object." 1509 DEFVAL { 50 } 1510 ::= { tn3270eRtCollCtlEntry 10 } 1512 tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE 1513 SYNTAX Unsigned32 1514 UNITS "tenths of seconds" 1515 MAX-ACCESS read-create 1516 STATUS current 1517 DESCRIPTION 1518 "The value of this object, together with that of the 1519 tn3270eRtCollCtlBucketBndry3 object, defines the range of 1520 transaction response times counted in the Tn3270eRtDataBucket4 1521 object: those greater than the value of the 1522 tn3270eRtCollCtlBucketBndry3 object, and less than or equal to 1523 the value of this object. 1525 The value of this object also defines the range of transaction 1526 response times counted in the Tn3270eRtDataBucket5 object: 1527 those greater than the value of this object." 1528 DEFVAL { 100 } 1529 ::= { tn3270eRtCollCtlEntry 11 } 1531 tn3270eRtCollCtlRowStatus OBJECT-TYPE 1533 Expires May 1998 [Page 30]~ 1535 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1537 SYNTAX RowStatus 1538 MAX-ACCESS read-create 1539 STATUS current 1540 DESCRIPTION 1541 "This object allows entries to be created and deleted 1542 in the tn3270eRtCollCtlTable. An entry in this table 1543 is deleted by setting this object to destroy(6). 1544 Deleting an entry in this table has the side-effect 1545 of removing all entries from the tn3270eRtDataTable 1546 that are associated with the entry being deleted." 1547 ::= { tn3270eRtCollCtlEntry 12 } 1549 -- TN3270E Response Time Data Table 1551 tn3270eRtDataTable OBJECT-TYPE 1552 SYNTAX SEQUENCE OF Tn3270eRtDataEntry 1553 MAX-ACCESS not-accessible 1554 STATUS current 1555 DESCRIPTION 1556 "The response time data table. Entries in this table are 1557 created based on entries in the tn3270eRtCollCtlTable." 1558 ::= { tn3270eRtObjects 2 } 1560 tn3270eRtDataEntry OBJECT-TYPE 1561 SYNTAX Tn3270eRtDataEntry 1562 MAX-ACCESS not-accessible 1563 STATUS current 1564 DESCRIPTION 1565 "An entry in this table is created based upon the 1566 tn3270eRtCollCtlTable. A single entry is created with a 1567 tn3270eRtDataClientAddrType of 'unknown(0)' and a null octet 1568 string value for tn3270eRtDataClientAddress when the 1569 corresponding tn3270eRtCollCtlType has aggregate(0) specified. 1570 When aggregate(0) is not specified, then a separate entry is 1571 created for each client. 1573 Note that the following objects defined within an 1574 entry in this table can wrap: 1575 tn3270eRtDataTotalRt 1576 tn3270eRtDataTotalIpRt 1577 tn3270eRtDataTransCount 1578 tn3270eRtDataDrCount 1579 tn3270eRtDataElapsRnTrpSq 1580 tn3270eRtDataElapsIpRtSq 1581 tn3270eRtDataBucket1 1582 tn3270eRtDataBucket2 1583 tn3270eRtDataBucket3 1585 Expires May 1998 [Page 31]~ 1587 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1589 tn3270eRtDataBucket4 1590 tn3270eRtDataBucket5" 1591 INDEX { 1592 tn3270eSrvrConfIndex, -- Server's local index 1593 tn3270eRtCollCtlClientGroupName, -- Target of data collection 1594 tn3270eRtDataClientAddrType, 1595 tn3270eRtDataClientAddress } 1596 ::= { tn3270eRtDataTable 1 } 1598 Tn3270eRtDataEntry ::= SEQUENCE { 1599 tn3270eRtDataClientAddrType Tn3270eAddrType, 1600 tn3270eRtDataClientAddress Tn3270eTAddress, 1601 tn3270eRtDataDiscontinuityTime TimeStamp, 1602 tn3270eRtDataAvgRt Gauge32, 1603 tn3270eRtDataAvgIpRt Gauge32, 1604 tn3270eRtDataAvgTransCount Counter32, 1605 tn3270eRtDataIntTimeStamp DateAndTime, 1606 tn3270eRtDataTotalRt Counter32, 1607 tn3270eRtDataTotalIpRt Counter32, 1608 tn3270eRtDataTransCount Counter32, 1609 tn3270eRtDataDrCount Counter32, 1610 tn3270eRtDataElapsRndTrpSq Unsigned32, 1611 tn3270eRtDataElapsIpRtSq Unsigned32, 1612 tn3270eRtDataBucket1 Counter32, 1613 tn3270eRtDataBucket2 Counter32, 1614 tn3270eRtDataBucket3 Counter32, 1615 tn3270eRtDataBucket4 Counter32, 1616 tn3270eRtDataBucket5 Counter32, 1617 tn3270eRtDataRtMethod INTEGER 1618 } 1620 tn3270eRtDataClientAddrType OBJECT-TYPE 1621 SYNTAX Tn3270eAddrType 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "Indicates the type of address that following in the 1626 instance OID represented by tn3270eRtDataClientAddress." 1627 ::= { tn3270eRtDataEntry 1 } 1629 tn3270eRtDataClientAddress OBJECT-TYPE 1630 SYNTAX Tn3270eTAddress 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 "Contains the IP address of the TN3270 client being 1635 monitored. A null octet string is used if the aggregate 1636 of the Client Group is being collected " 1638 Expires May 1998 [Page 32]~ 1640 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1642 ::= { tn3270eRtDataEntry 2 } 1644 tn3270eRtDataDiscontinuityTime OBJECT-TYPE 1645 SYNTAX TimeStamp 1646 MAX-ACCESS read-only 1647 STATUS current 1648 DESCRIPTION 1649 "The value of sysUpTime on the most recent occasion at 1650 which any one or more of this entry's objects 1651 suffered a discontinuity. One possibility of this is 1652 when a TN3270E Server is stopped and then restarted 1653 where local methods are used to setup collection 1654 policy (tn3270eRtCollCtlTable entries). 1656 In order to prevent a TN3270E Server from caching this 1657 object it is recommended that the TN3270E Server's 1658 startup time be used as the objects initial value." 1659 ::= { tn3270eRtDataEntry 3 } 1661 tn3270eRtDataAvgRt OBJECT-TYPE 1662 SYNTAX Gauge32 1663 UNITS "tenths of seconds" 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "The average total response time measured over the last 1668 collection interval." 1669 DEFVAL { 0 } 1670 ::= { tn3270eRtDataEntry 4 } 1672 tn3270eRtDataAvgIpRt OBJECT-TYPE 1673 SYNTAX Gauge32 1674 UNITS "tenths of seconds" 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "The average IP response time measured over the last 1679 collection interval." 1680 DEFVAL { 0 } 1681 ::= { tn3270eRtDataEntry 5 } 1683 tn3270eRtDataAvgTransCount OBJECT-TYPE 1684 SYNTAX Counter32 1685 UNITS "transactions" 1686 MAX-ACCESS read-only 1687 STATUS current 1688 DESCRIPTION 1689 "The sliding transaction count used for calculating the values 1691 Expires May 1998 [Page 33]~ 1693 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1695 of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects. 1696 The actual transaction count is available in the 1697 tn3270eRtDataTransCount object." 1698 ::= { tn3270eRtDataEntry 6 } 1700 tn3270eRtDataIntTimeStamp OBJECT-TYPE 1701 SYNTAX DateAndTime 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "The date and time of the last interval that tn3270eRtDataAvgRt, 1706 tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgTransCount were 1707 calculated." 1708 ::= { tn3270eRtDataEntry 7 } 1710 tn3270eRtDataTotalRt OBJECT-TYPE 1711 SYNTAX Counter32 1712 UNITS "tenths of seconds" 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "A count of the total response time collected." 1717 ::= { tn3270eRtDataEntry 8 } 1719 tn3270eRtDataTotalIpRt OBJECT-TYPE 1720 SYNTAX Counter32 1721 UNITS "tenths of seconds" 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "A count of the total IP-network response time collected." 1726 ::= { tn3270eRtDataEntry 9 } 1728 tn3270eRtDataTransCount OBJECT-TYPE 1729 SYNTAX Counter32 1730 UNITS "transactions" 1731 MAX-ACCESS read-only 1732 STATUS current 1733 DESCRIPTION 1734 "A count of the total number of transactions detected." 1735 ::= { tn3270eRtDataEntry 10 } 1737 tn3270eRtDataDrCount OBJECT-TYPE 1738 SYNTAX Counter32 1739 UNITS "transactions" 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1744 Expires May 1998 [Page 34]~ 1746 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1748 "A count of the total number of definite responses detected." 1749 ::= { tn3270eRtDataEntry 11 } 1751 tn3270eRtDataElapsRndTrpSq OBJECT-TYPE 1752 SYNTAX Unsigned32 1753 UNITS "tenths of seconds squared" 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "The sum of the elapsed round trip time squared. A sum of the 1758 squares is keep in order to calculate a variance." 1759 DEFVAL { 0 } 1760 ::= { tn3270eRtDataEntry 12 } 1762 tn3270eRtDataElapsIpRtSq OBJECT-TYPE 1763 SYNTAX Unsigned32 1764 UNITS "tenths of seconds squared" 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "The sum of the elapsed IP round trip time squared. A sum of 1769 the squares is keep in order to calculate a variance." 1770 DEFVAL { 0 } 1771 ::= { tn3270eRtDataEntry 13 } 1773 tn3270eRtDataBucket1 OBJECT-TYPE 1774 SYNTAX Counter32 1775 MAX-ACCESS read-only 1776 STATUS current 1777 DESCRIPTION 1778 "A count of the response times falling into bucket 1." 1779 ::= { tn3270eRtDataEntry 14 } 1781 tn3270eRtDataBucket2 OBJECT-TYPE 1782 SYNTAX Counter32 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "A count of the response times falling into bucket 2." 1787 ::= { tn3270eRtDataEntry 15 } 1789 tn3270eRtDataBucket3 OBJECT-TYPE 1790 SYNTAX Counter32 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "A count of the response times falling into bucket 3." 1795 ::= { tn3270eRtDataEntry 16 } 1797 Expires May 1998 [Page 35]~ 1799 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1801 tn3270eRtDataBucket4 OBJECT-TYPE 1802 SYNTAX Counter32 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "A count of the response times falling into bucket 4." 1807 ::= { tn3270eRtDataEntry 17 } 1809 tn3270eRtDataBucket5 OBJECT-TYPE 1810 SYNTAX Counter32 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "A count of the response times falling into bucket 5." 1815 ::= { tn3270eRtDataEntry 18 } 1817 tn3270eRtDataRtMethod OBJECT-TYPE 1818 SYNTAX INTEGER { 1819 none(0), 1820 responses(1), 1821 timemark(2) 1822 } 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "The value of this object indicates the method that was used 1827 in calculate the IP Network Time." 1828 ::= { tn3270eRtDataEntry 19 } 1830 -- Notifications 1832 tn3270eRtExceeded NOTIFICATION-TYPE 1833 OBJECTS { 1834 tn3270eSrvrConfIndex, -- server's local index 1835 tn3270eRtCollCtlClientGroupName, -- target of data collection 1836 tn3270eRtDataClientAddrType, 1837 tn3270eRtDataClientAddress, 1838 tn3270eRtDataIntTimeStamp, 1839 tn3270eRtDataAvgRt, 1840 tn3270eRtDataAvgIpRt, 1841 tn3270eRtDataAvgTransCount, 1842 tn3270eRtDataRtMethod 1843 } 1844 STATUS current 1845 DESCRIPTION 1846 "This notification is generated when the average response time, 1847 tn3270eRtDataAvgRt, exceeds tn3270eRtCollCtlThresholdHigh at 1848 the end of a collection interval specified by 1850 Expires May 1998 [Page 36]~ 1852 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1854 tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult. Note that 1855 the corresponding tn3270eCollCtlType must have traps(5) and 1856 average(3) set for this notification to be generated. In 1857 addition, tn3270eRtDataAvgTransCount, 1858 tn3270eRtCollCtlThreshHigh and tn3270eRtDataAvgRt are 1859 algorithmically compared to tn3270eRtCollCtlIdleRate for 1860 determination if this will be suppressed." 1861 ::= { tn3270eRtNotifications 1 } 1863 tn3270eRtOkay NOTIFICATION-TYPE 1864 OBJECTS { 1865 tn3270eSrvrConfIndex, -- server's local index 1866 tn3270eRtCollCtlClientGroupName, -- target of data collection 1867 tn3270eRtDataClientAddrType, 1868 tn3270eRtDataClientAddress,-- IP Address or null octet string 1869 tn3270eRtDataIntTimeStamp, 1870 tn3270eRtDataAvgRt, 1871 tn3270eRtDataAvgIpRt, 1872 tn3270eRtDataAvgTransCount, 1873 tn3270eRtDataRtMethod 1874 } 1875 STATUS current 1876 DESCRIPTION 1877 "This notification is generated when the average response time, 1878 tn3270eRtDataAvgRt, falls below tn3270eRtCollCtlThresholdLow at 1879 the end of a collection interval specified by 1880 tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult, after a 1881 tn3270eRtExceeded notification was generated. Note that the 1882 corresponding tn3270eCollCtlType must have traps(5) and 1883 average(3) set for this notification to be generated." 1884 ::= { tn3270eRtNotifications 2 } 1886 tn3270eRtCollStart NOTIFICATION-TYPE 1887 OBJECTS { 1888 tn3270eSrvrConfIndex, -- server's local index 1889 tn3270eRtCollCtlClientGroupName, -- Data collection target 1890 tn3270eRtDataClientAddrType, 1891 tn3270eRtDataClientAddress, -- IP Address or null octet string 1892 tn3270eResMapElementName, -- IDs LU or printer association 1893 tn3270eResMapElementType -- type of resource 1894 } 1895 STATUS current 1896 DESCRIPTION 1897 "This notification is generated when response time data 1898 collection is enabled for a member of a client group. In order 1899 for this notification to occur the corresponding 1900 tn3270eRtCollCtlType must have traps(5) selected. The objects 1901 tn3270eResMapElementName and tn3270eResMapElementType contains 1903 Expires May 1998 [Page 37]~ 1905 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1907 valid values only if tn3270eRtDataClientAddress contains a 1908 valid IP address (rather than the null octet string)." 1909 ::= { tn3270eRtNotifications 3 } 1911 tn3270eRtCollEnd NOTIFICATION-TYPE 1912 OBJECTS { 1913 tn3270eSrvrConfIndex, -- server's local index 1914 tn3270eRtCollCtlClientGroupName, -- data collection target 1915 tn3270eRtDataClientAddrType, 1916 tn3270eRtDataClientAddress, 1917 tn3270eRtDataDiscontinuityTime, 1918 tn3270eRtDataAvgRt, 1919 tn3270eRtDataAvgIpRt, 1920 tn3270eRtDataAvgTransCount, 1921 tn3270eRtDataIntTimeStamp, 1922 tn3270eRtDataTotalRt, 1923 tn3270eRtDataTotalIpRt, 1924 tn3270eRtDataTransCount, 1925 tn3270eRtDataDrCount, 1926 tn3270eRtDataElapsRndTrpSq, 1927 tn3270eRtDataElapsIpRtSq, 1928 tn3270eRtDataBucket1, 1929 tn3270eRtDataBucket2, 1930 tn3270eRtDataBucket3, 1931 tn3270eRtDataBucket4, 1932 tn3270eRtDataBucket5, 1933 tn3270eRtDataRtMethod 1934 } 1935 STATUS current 1936 DESCRIPTION 1937 "This notification is generated when a tn3270eRtDataEntry is 1938 deleted after being active (actual data collected), in order to 1939 enable a management application monitoring a tn3270eRtDataTable 1940 entry to end get the entry's final values. Note that the 1941 corresponding tn3270eCollCtlType must have traps(5) set for this 1942 notification to be generated." 1943 ::= { tn3270eRtNotifications 4 } 1945 -- Conformance Statement 1947 tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 } 1948 tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 } 1950 -- Compliance statements 1952 tn3270eRtCompliance MODULE-COMPLIANCE 1953 STATUS current 1954 DESCRIPTION 1956 Expires May 1998 [Page 38]~ 1958 White, Moore TN3270E Response Time Collection MIB 19 November 1997 1960 "The compliance statement for agents that support the 1961 TN327E-RT-MIB " 1962 MODULE -- this module 1963 MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup } 1964 OBJECT tn3270eRtCollCtlSPeriod 1965 MIN-ACCESS read-only 1966 DESCRIPTION 1967 "The agent is not required to allow the user to change 1968 the default value of this object and is allowed 1969 to use a different default." 1970 ::= {tn3270eRtCompliances 1 } 1972 -- Group definitions 1974 tn3270eRtGroup OBJECT-GROUP 1975 OBJECTS { 1976 tn3270eRtCollCtlType, 1977 tn3270eRtCollCtlSPeriod, 1978 tn3270eRtCollCtlSPMult, 1979 tn3270eRtCollCtlThreshHigh, 1980 tn3270eRtCollCtlThreshLow, 1981 tn3270eRtCollCtlIdleRate, 1982 tn3270eRtCollCtlBucketBndry1, 1983 tn3270eRtCollCtlBucketBndry2, 1984 tn3270eRtCollCtlBucketBndry3, 1985 tn3270eRtCollCtlBucketBndry4, 1986 tn3270eRtCollCtlRowStatus, 1987 tn3270eRtDataDiscontinuityTime, 1988 tn3270eRtDataAvgRt, 1989 tn3270eRtDataAvgIpRt, 1990 tn3270eRtDataAvgTransCount, 1991 tn3270eRtDataIntTimeStamp, 1992 tn3270eRtDataTotalRt, 1993 tn3270eRtDataTotalIpRt, 1994 tn3270eRtDataTransCount, 1995 tn3270eRtDataDrCount, 1996 tn3270eRtDataElapsRndTrpSq, 1997 tn3270eRtDataElapsIpRtSq, 1998 tn3270eRtDataBucket1, 1999 tn3270eRtDataBucket2, 2000 tn3270eRtDataBucket3, 2001 tn3270eRtDataBucket4, 2002 tn3270eRtDataBucket5, 2003 tn3270eRtDataRtMethod } 2004 STATUS current 2005 DESCRIPTION 2006 "This group is mandatory for all host supporting the 2007 TN3270E-RT-MIB. " 2009 Expires May 1998 [Page 39]~ 2011 White, Moore TN3270E Response Time Collection MIB 19 November 1997 2013 ::= { tn3270eRtGroups 1 } 2015 tn3270eRtNotGroup NOTIFICATION-GROUP 2016 NOTIFICATIONS { 2017 tn3270eRtExceeded, 2018 tn3270eRtOkay, 2019 tn3270eRtCollStart, 2020 tn3270eRtCollEnd 2021 } 2022 STATUS current 2023 DESCRIPTION 2024 "The notifications which must be supported when the 2025 TN3270E-RT-MIB is implemented. " 2026 ::= { tn3270eRtGroups 2 } 2028 END 2030 6. Security Considerations 2032 Certain management information defined in this MIB may be considered 2033 sensitive in some network environments. Therefore, authentication of 2034 received SNMP requests and controlled access to management information 2035 should be employed in such environments. The method for this 2036 authentication is a function of the SNMP Administrative Framework, and 2037 has not been expanded by this MIB. 2039 Several objects in this MIB allow write access or provide for remote 2040 creation. Allowing this support in a non-secure environment can have a 2041 negative effect on network operations. It is recommended that 2042 implementers seriously consider whether set operations should be 2043 allowed without providing, at a minimum, authentication of request 2044 origin. It it recommended that without such support that the following 2045 objects be implemented as read-only: 2047 o tn3270eRtCollCtlType 2048 o tn3270eRtCollSPeriod 2049 o tn3270eRtCollSPMult 2050 o tn3270eRtCollCtlThreshHigh 2051 o tn3270eRtCollCtlThreshLow 2052 o tn3270eRtCollCtlIdleRate 2053 o tn3270eRtCollCtlBucketBndry1 2054 o tn3270eRtCollCtlBucketBndry2 2055 o tn3270eRtCollCtlBucketBndry3 2056 o tn3270eRtCollCtlBucketBndry4 2058 The following object should either be implemented as read-only or not 2059 implemented when security is an issue as previously discussed: 2061 Expires May 1998 [Page 40]~ 2063 White, Moore TN3270E Response Time Collection MIB 19 November 1997 2065 o tn3270eRtCollCtlRowStatus 2067 The administrative method to use to create and manage the 2068 tn3270eRtCollCtlTable when SET support is not allowed is outside of 2069 the scope of this memo. 2071 7. Acknowledgments 2073 This document is a product of the TN3270E Working Group. Special 2074 thanks is due to Derek Bolton and Michael Boe of Cisco Systems for 2075 their numerous comments and suggestions for improving the structure of 2076 this MIB. 2078 8. References 2080 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2081 Waldbusser S., "Structure of Management Information for version 2 2082 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2083 January 1996. 2085 [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet 2086 Protocol Specification", RFC 854, May 1983. 2088 [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing 2089 Mark Option", RFC 860, May 1983. 2091 [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", 2092 RFC 1041, January 1988. 2094 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2095 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2096 RFC 1213, Hughes LAN Systems, Performance Systems International, 2097 March 1991. 2099 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2100 Waldbusser, "Textual Conventions for version 2 of the Simple 2101 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 2103 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2105 Expires May 1998 [Page 41]~ 2107 White, Moore TN3270E Response Time Collection MIB 19 November 1997 2109 Waldbusser, "Protocol Operations for version 2 of the Simple 2110 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2112 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2113 Waldbusser, "Conformance Statements for version 2 of the Simple 2114 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 2116 [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2117 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2118 International, MIT Laboratory for Computer Science, May 1990. 2120 [10] IETF TN3270E Working Group and White, K., "Base Definitions of 2121 Managed Objects for TN3270E Using SMIv2", Internet-Draft Work in 2122 progress, June 1997. 2124 [11] Network Working Group, and Kelly, B., "TN3270 Enhancements", RFC 2125 1647, July 1994. 2127 [12] IBM, International Technical Support Centers, "Response Time Data 2128 Gathering", GG24-3212-01, November 1990. 2130 [13] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 2131 Managed Objects for Applications", April 15, 1997. 2133 9. Authors' Addresses 2135 Kenneth D. White 2136 Dept. BRQA/Bldg. 501/G114 2137 IBM Corporation 2138 P.O.Box 12195 2139 3039 Cornwallis 2140 Research Triangle Park, NC 27709, USA 2141 Phone: +1-919-254-0102 2142 E-mail: kennethw@vnet.ibm.com 2144 Robert Moore 2145 Dept. BRQA/Bldg. 501/G114 2146 IBM Corporation 2147 P.O.Box 12195 2148 3039 Cornwallis 2149 Research Triangle Park, NC 27709, USA 2151 Expires May 1998 [Page 42]~ 2153 White, Moore TN3270E Response Time Collection MIB 19 November 1997 2155 Phone: +1-919-254-7507 2156 E-mail: remoore@us.ibm.com 2158 Expires May 1998 [Page 43]~