Debian Codegraph @

rfc2562.html

raw
1 <pre>Network Working Group K. White
2 Request for Comments: 2562 IBM Corp.
3 Category: Standards Track R. Moore
4 IBM Corp.
5 April 1999
6
7
8 <span class="h1">Definitions of Protocol and Managed Objects for</span>
9 <span class="h1">TN3270E Response Time Collection Using SMIv2</span>
10 <span class="h1">(TN3270E-RT-MIB)</span>
11
12 Status of this Memo
13
14 This document specifies an Internet standards track protocol for the
15 Internet community, and requests discussion and suggestions for
16 improvements. Please refer to the current edition of the "Internet
17 Official Protocol Standards" (STD 1) for the standardization state
18 and status of this protocol. Distribution of this memo is unlimited.
19
20 Copyright Notice
21
22 Copyright (C) The Internet Society (1999). All Rights Reserved.
23
24 Abstract
25
26 This memo defines the protocol and the Management Information Base
27 (MIB) for performing response time data collection on TN3270 and
28 TN3270E sessions by a TN3270E server. The response time data
29 collected by a TN3270E server is structured to support both
30 validation of service level agreements and performance monitoring of
31 TN3270 and TN3270E Sessions. This MIB has as a prerequisite the
32 TN3270E-MIB, reference [<a href="#ref-20" title="&quot;Base Definitions of Managed Objects for TN3270E Using SMIv2&quot;">20</a>].
33
34 TN3270E, defined by <a href="./rfc2355">RFC 2355</a> [<a href="#ref-19" title="&quot;TN3270 Enhancements&quot;">19</a>], refers to the enhancements made to
35 the Telnet 3270 (TN3270) terminal emulation practices. Refer to <a href="./rfc1041">RFC</a>
36 <a href="./rfc1041">1041</a> [<a href="#ref-18" title="&quot;Telnet 3270 Regime Option&quot;">18</a>], STD 8, <a href="./rfc854">RFC 854</a> [<a href="#ref-16" title="&quot;Telnet Protocol Specification&quot;">16</a>], and STD 31, <a href="./rfc860">RFC 860</a> [<a href="#ref-17" title="&quot;Telnet Timing Mark Option&quot;">17</a>] for a sample
37 of what is meant by TN3270 practices.
38
39 Table of Contents
40
41 <a href="#section-1.0">1.0</a> Introduction . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
42 <a href="#section-2.0">2.0</a> The SNMP Network Management Framework . . . . . . . . . . <a href="#page-2">2</a>
43 <a href="#section-3.0">3.0</a> Response Time Collection Methodology . . . . . . . . . . . <a href="#page-3">3</a>
44 <a href="#section-3.1">3.1</a> General Response Time Collection . . . . . . . . . . . . . <a href="#page-3">3</a>
45 <a href="#section-3.2">3.2</a> TN3270E Server Response Time Collection . . . . . . . . . <a href="#page-5">5</a>
46 <a href="#section-3.3">3.3</a> Correlating TN3270E Server and Host Response Times . . . . <a href="#page-10">10</a>
47 <a href="#section-3.4">3.4</a> Timestamp Calculation . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
48 <a href="#section-3.4.1">3.4.1</a> DR Usage . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
49
50
51
52 <span class="grey">White &amp; Moore Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
55
56
57 <a href="#section-3.4.2">3.4.2</a> TIMING-MARK Usage . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
58 <a href="#section-3.5">3.5</a> Performance Data Modelling . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
59 <a href="#section-3.5.1">3.5.1</a> Averaging Response Times . . . . . . . . . . . . . . . <a href="#page-15">15</a>
60 <a href="#section-3.5.2">3.5.2</a> Response Time Buckets . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
61 <a href="#section-4.0">4.0</a> Structure of the MIB . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
62 <a href="#section-4.1">4.1</a> tn3270eRtCollCtlTable . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
63 <a href="#section-4.2">4.2</a> tn3270eRtDataTable . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
64 <a href="#section-4.3">4.3</a> Notifications . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
65 <a href="#section-4.4">4.4</a> Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
66 <a href="#section-5.0">5.0</a> Definitions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
67 <a href="#section-6.0">6.0</a> Security Considerations . . . . . . . . . . . . . . . . . <a href="#page-45">45</a>
68 <a href="#section-7.0">7.0</a> Intellectual Property . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a>
69 <a href="#section-8.0">8.0</a> Acknowledgments . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
70 <a href="#section-9.0">9.0</a> References . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
71 <a href="#section-10.0">10.0</a> Authors' Addresses . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a>
72 <a href="#section-11.0">11.0</a> Full Copyright Statement . . . . . . . . . . . . . . . . <a href="#page-49">49</a>
73
74 <span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> Introduction</span>
75
76 This document is a product of the TN3270E Working Group. It defines
77 a protocol and a MIB module to enable a TN3270E server to collect and
78 keep track of response time data for both TN3270 and TN3270E clients.
79 Basis for implementing this MIB:
80
81 o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E
82 Using SMIv2 [<a href="#ref-20" title="&quot;Base Definitions of Managed Objects for TN3270E Using SMIv2&quot;">20</a>]
83
84 o TN3270E RFCs
85
86 o Telnet Timing Mark Option RFC [<a href="#ref-17" title="&quot;Telnet Timing Mark Option&quot;">17</a>].
87
88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
90 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a>, reference
91 [<a href="#ref-23" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">23</a>].
92
93 <span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> The SNMP Network Management Framework</span>
94
95 The SNMP Management Framework presently consists of five major
96 components:
97
98 o An overall architecture, described in <a href="./rfc2271">RFC 2271</a> [<a href="#ref-1" title="&quot;An Architecture for Describing SNMP Management Frameworks&quot;">1</a>].
99
100 o Mechanisms for describing and naming objects and events for the
101 purpose of management. The first version of this Structure of
102 Management Information (SMI) is called SMIv1 and described in STD
103 16, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-2" title="&quot;Structure and Identification of Management Information for TCP/IP-based Internets&quot;">2</a>], STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-3" title="&quot;Concise MIB Definitions&quot;">3</a>] and <a href="./rfc1215">RFC 1215</a> [<a href="#ref-4" title="&quot;A Convention for Defining Traps for use with the SNMP&quot;">4</a>]. The
104 second version, called SMIv2, is described in <a href="./rfc1902">RFC 1902</a> [<a href="#ref-5" title="&quot;Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>], RFC
105
106
107
108 <span class="grey">White &amp; Moore Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
111
112
113 1903 [<a href="#ref-6" title="&quot;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] and <a href="./rfc1904">RFC 1904</a> [<a href="#ref-7" title="&quot;Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>].
114
115 o Message protocols for transferring management information. The
116 first version of the SNMP message protocol is called SNMPv1 and
117 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second version of the SNMP
118 message protocol, which is not an Internet standards track
119 protocol, is called SNMPv2c and described in <a href="./rfc1901">RFC 1901</a> [<a href="#ref-9" title="&quot;Introduction to Community-based SNMPv2&quot;">9</a>] and <a href="./rfc1906">RFC</a>
120 <a href="./rfc1906">1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>]. The third version of the message protocol is called
121 SNMPv3 and described in <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>], <a href="./rfc2272">RFC 2272</a> [<a href="#ref-11" title="&quot;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)&quot;">11</a>] and <a href="./rfc2274">RFC 2274</a>
122 [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>].
123
124 o Protocol operations for accessing management information. The
125 first set of protocol operations and associated PDU formats is
126 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second set of protocol
127 operations and associated PDU formats is described in <a href="./rfc1905">RFC 1905</a>
128 [<a href="#ref-13" title="&quot;Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">13</a>].
129
130 o A set of fundamental applications described in <a href="./rfc2273">RFC 2273</a> [<a href="#ref-14" title="&quot;SNMPv3 Applications&quot;">14</a>] and
131 the view-based access control mechanism described in <a href="./rfc2275">RFC 2275</a>
132 [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>].
133
134 Managed objects are accessed via a virtual information store, termed
135 the Management Information Base or MIB. Objects in the MIB are
136 defined using the mechanisms defined in the SMI.
137
138 This memo specifies a MIB module that is compliant to the SMIv2. A
139 MIB conforming to the SMIv1 can be produced through the appropriate
140 translations. The resulting translated MIB must be semantically
141 equivalent, except where objects or events are omitted because no
142 translation is possible (use of Counter64). Some machine readable
143 information in SMIv2 will be converted into textual descriptions in
144 SMIv1 during the translation process. However, this loss of machine
145 readable information is not considered to change the semantics of the
146 MIB.
147
148 <span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> Response Time Collection Methodology</span>
149
150 This section explains the methodology and approach used by the MIB
151 defined by this memo for response time data collection by a TN3270E
152 server.
153
154 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> General Response Time Collection</span>
155
156 Two primary methods exist for measuring response times in SNA
157 networks:
158
159 o The Systems Network Architecture Management Services (SNA/MS)
160 Response Time Monitoring (RTM) function.
161
162
163
164 <span class="grey">White &amp; Moore Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
167
168
169 o Timestamping using definite response flows.
170
171 This memo defines an approach using definite responses to timestamp
172 the flows between a client and its TN3270E server, rather than by use
173 of the RTM method. Extensions to the SNA/MS RTM flow were considered,
174 but this approach was deemed unsuitable since not all TN3270E server
175 implementations have access to their underlying SNA stacks. The RTM
176 concepts of keeping response time buckets for service level
177 agreements and of interval-based response time collection for
178 performance monitoring are preserved in the MIB module defined in
179 this memo.
180
181 As mentioned, this memo focuses on using definite responses to
182 timestamp the flows between a client and its TN3270E server for
183 generating performance data. Use of a definite response flow
184 requires that the client supports TN3270E with the RESPONSES function
185 negotiated. The TN3270 TIMING-MARK option can be used instead of
186 definite response for supporting TN3270 clients or TN3270E clients
187 that don't support RESPONSES. This document focuses first on
188 defining the protocol and methods for generating performance data
189 using definite responses, and then describes how the TIMING-MARK
190 option can be used instead of definite response.
191
192 In an SNA network, a transaction between a client Logical Unit (LU)
193 and a target host in general looks as follows:
194
195 ------------------------------------------------
196 | |
197 | Client LU Target SNA Host |
198 | |
199 | Timestamps |
200 | request A |
201 | -----------------------------------------&gt; |
202 | reply(DR) B | |
203 | &lt;---------------------------------------&lt; |
204 | | +/-RSP C |
205 | &gt;---------------------------------------&gt; |
206 | |
207 | DR: Definite Response requested |
208 | +/-RSP: Definite Response |
209 | |
210 ------------------------------------------------
211
212 This transaction is a simple one, and is being used only to
213 illustrate how timestamping at a target SNA host can be used to
214 generate response times. An IBM redbook [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>] provides a more
215 detailed description of response time collection for a transaction of
216 this type. Note that for the purpose of calculating an approximation
217
218
219
220 <span class="grey">White &amp; Moore Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
223
224
225 for network transit time, it doesn't matter if the response is
226 positive or negative. Two response time values are typically
227 calculated:
228
229 o Host Transit Time: Timestamp B - Timestamp A
230 o Network Transit Time: Timestamp C - Timestamp B
231
232 Network transit time is an approximation for the amount of time that
233 a transaction requires to flow across a network, since the response
234 flow is being substituted for the request flow at the start of the
235 transaction. Network transit time, timestamp C - timestamp B, is the
236 amount of time that the definite response request and its response
237 required. Host time, timestamp B - timestamp A, is the actual time
238 that the host required to process the transaction. Experience has
239 shown that using the response flow to approximate network transit
240 times is useful, and does correlate well with actual network transit
241 times.
242
243 A client SHOULD respond to a definite response request when it
244 completes processing the transaction. This is important since it
245 increases the accuracy of a total response time. Clients that
246 immediately respond to a definite response request will be attributed
247 with lower total response times then those that actually occurred.
248
249 The TN3270E-RT-MIB describes a method of collecting performance data
250 that is not appropriate for printer (LU Type 1 or LU Type 3)
251 sessions; thus collection of performance data for printer sessions is
252 excluded from this MIB. This exclusion of printer sessions is not
253 considered a problem, since these sessions are not the most important
254 ones for response time monitoring, and since historically they were
255 excluded from SNA/MS RTM collection. The tn3270eTcpConnResourceType
256 object in a tn3270eTcpConnEntry (in the TN3270E-MIB) can be examined
257 to determine if a client session is ineligible for response time data
258 collection for this reason.
259
260 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> TN3270E Server Response Time Collection</span>
261
262 A TN3270E server connects a Telnet client performing 3270 emulation
263 to a target SNA host over both a client-side network (client to
264 TN3270E server) and an SNA Network (TN3270E server to target SNA
265 host). The client-side network is typically TCP/IP, but it need not
266 be. For ease of exposition this document uses the term "IP network"
267 to refer to the client-side network, since IP is by far the most
268 common protocol for these networks.
269
270 A TN3270E server can use SNA definite responses and the TN3270
271 Enhancement (<a href="./rfc2355">RFC 2355</a> [<a href="#ref-19" title="&quot;TN3270 Enhancements&quot;">19</a>]) RESPONSES function to calculate response
272 times for a transaction, by timestamping when a client request
273
274
275
276 <span class="grey">White &amp; Moore Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
279
280
281 arrives at the server, when the reply arrives from the target host,
282 and when the response acknowledging this reply arrives from the
283 client.
284
285 <a href="#section-3.4">Section 3.4</a>, Timestamp Calculation, provides specifics on when in the
286 sequence of flows between a TN3270E client and its target SNA host a
287 TN3270E server takes the required timestamps. In addition, it
288 provides information on how a TN3270 TIMING-MARK request/response
289 flow can be used instead of DR for approximating IP network transit
290 times.
291
292 The following figure adds a TN3270E server between the client, in
293 this case a TN3270E client and the target SNA host:
294
295 ------------------------------------------------
296 | |
297 | Client TN3270E Target |
298 | Server SNA Host |
299 | Timestamps |
300 | |
301 | &lt;---IP Network-------&gt;&lt;---SNA Network---&gt; |
302 | |
303 | request D |
304 | ------------------------------------------&gt; |
305 | reply(DR) E | |
306 | &lt;----------------------------------------&lt; |
307 | | +/-RSP F |
308 | &gt;-------------------- - - - - - - - - - &gt; |
309 | |
310 ------------------------------------------------
311
312 A TN3270E server can save timestamp D when it receives a client
313 request, save timestamp E when the target SNA host replies, and save
314 timestamp F when the client responds to the definite response request
315 that flowed with the reply. It doesn't matter whether the target SNA
316 host requested a definite response on its reply: if it didn't, the
317 TN3270E server makes the request on its own, to enable it to produce
318 timestamp F. In this case the TN3270E server does not forward the
319 response to the target SNA host, as the dotted line in the figure
320 indicates.
321
322 Because it is a special case, a transaction in which a target SNA
323 host returns an UNBIND in response to a client's request, and the
324 TN3270E server forwards the UNBIND to the client, is not included in
325 any response time calculations.
326
327
328
329
330
331
332 <span class="grey">White &amp; Moore Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
335
336
337 In order to generate timestamp F, a TN3270E server MUST insure that
338 the transaction specifies DR, and that the TN3270E RESPONSES function
339 has been negotiated between itself and the client. Negotiation of
340 the TN3270E RESPONSES function occurs during the client's TN3270E
341 session initialization. The TN3270E servers that the authors are
342 aware of do request the RESPONSES function during client session
343 initialization. TN3270E clients either automatically support the
344 RESPONSES function, or can be configured during startup to support
345 it.
346
347 Using timestamps D, E, and F the following response times can be
348 calculated by a TN3270E server:
349
350 o Total Response time: Timestamp F - Timestamp D
351 o IP Network Transit Time: Timestamp F - Timestamp E
352
353 Just as in the SNA case presented above, these response times are
354 also approximations, since the final +/- RSP from the client is being
355 substituted for the request from the client that began the
356 transaction.
357
358 The MIB provides an object, tn3270eRtCollCtlType, to control several
359 aspects of response time data collection. One of the available
360 options in setting up a response time collection policy is to
361 eliminate the IP-network component altogether. This might be done
362 because it is determined either that the additional IP network
363 traffic would not be desirable, or that the IP-network component of
364 the overall response times is not significant.
365
366 Excluding the IP-network component from response times also has an
367 implication for the way in which response time data is aggregated. A
368 TN3270E server may find that some of its clients simply don't support
369 any of the functions necessary for the server to calculate the IP-
370 network component of response times. For these clients, the most
371 that the server can calculate is the SNA-network component of their
372 overall response times; the server records this SNA-network component
373 as the TOTAL response time each of these clients' transactions. If a
374 response time collection is aggregating data from a number of
375 clients, some of which have the support necessary for including the
376 IP-network component in their total response time calculations, and
377 some of which do not, then the server aggregates the data differently
378 depending on whether the collection has been defined to include or
379 exclude the IP-network component:
380
381 o If the IP-network component is included, then transactions for the
382 clients that don't support calculation of the IP-network component
383 of their response times are excluded from the aggregation
384 altogether.
385
386
387
388 <span class="grey">White &amp; Moore Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
391
392
393 o If the IP-network component is excluded, then total response times
394 for ALL clients include only the SNA-network component, even
395 though the server could have included an IP-network component in
396 the overall response times for some of these clients. The server
397 does this by setting timestamp F, which marks the end of a
398 transaction's total response time, equal to timestamp E, the end
399 of the transaction's SNA-network component.
400
401 The principle here is that all the transactions contributing their
402 response times to an aggregated value MUST make the same
403 contribution. If the aggregation specifies that an IP-network
404 component MUST be included in the aggregation's response times, then
405 transactions for which an IP-network component cannot be calculated
406 aren't included at all. If the aggregation specifies that an IP-
407 network component is not to be included, then only the SNA-network
408 component is used, even for those transactions for which an IP-
409 network component could have been calculated.
410
411 There is one more complication here: the MIB allows a management
412 application to enable or disable dynamic definite responses for a
413 response time collection. Once again the purpose of this option is
414 to give the network operator control over the amount of traffic
415 introduced into the IP network for response time data collection. A
416 DYNAMIC definite response is one that the TN3270E server itself adds
417 to a reply, in a transaction for which the SNA application at the
418 target SNA host did not specify DR in its reply. When the +/-RSP
419 comes back from the client, the server uses this response to
420 calculate timestamp F, but then it does not forward the response on
421 to the SNA application (since the application is not expecting a
422 response to its reply).
423
424 The dynamic definite responses option is related to the option of
425 including or excluding the IP-network component of response times
426 (discussed above) as follows:
427
428 o If the IP-network component is excluded, then there is no reason
429 for enabling dynamic definite responses: the server always sets
430 timestamp F equal to timestamp E, so the additional IP-network
431 traffic elicited by a dynamic definite response would serve no
432 purpose.
433
434 o If the IP-network component is included, then enabling dynamic
435 definite responses causes MORE transactions to be included in the
436 aggregated response time values:
437
438 - For clients that do not support sending of responses, timestamp
439 F can never be calculated, and so their transactions are never
440 included in the aggregate.
441
442
443
444 <span class="grey">White &amp; Moore Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
447
448
449 - For clients that support sending of responses, timestamp F will
450 always be calculated for transactions in which the host SNA
451 application specifies DR in its reply, and so these
452 transactions will always be included in the aggregate.
453
454 - For clients that support sending of responses, having dynamic
455 definite responses enabled for a collection results in the
456 inclusion of additional transactions in the aggregate:
457 specifically, those for which the host SNA application did not
458 specify DR in its reply.
459
460 A TN3270E server also has the option of substituting TIMING-MARK
461 processing for definite responses in calculating the IP-network
462 component of a transaction's response time. Once again, there is no
463 reason for the server to do this if the collection has been set up to
464 exclude the IP-network component altogether in computing response
465 times.
466
467 The MIB is structured to keep counts and averages for total response
468 times (F - D) and their IP-network components (F - E). A management
469 application can obviously calculate from these two values an average
470 SNA-network component (E - D) for the response times. This SNA-
471 network component includes the SNA node processing time at both the
472 TN3270E server and at the target application.
473
474 A host TN3270E server refers to an implementation where the TN3270E
475 server is collocated with the Systems Network Architecture (SNA)
476 System Services Control Point (SSCP) for the dependent Secondary
477 Logical Units (SLUs) that the server makes available to its clients
478 for connecting into an SNA network. A gateway TN3270E server resides
479 on an SNA node other than an SSCP, either an SNA type 2.0 node, a
480 boundary-function-attached type 2.1 node, or an APPN node acting in
481 the role of a Dependent LU Requester (DLUR). Host and gateway
482 TN3270E server implementations typically differ greatly as to their
483 internal implementation and System Definition (SYSDEF) requirements.
484
485 If a host TN3270E server is in the same SNA host as the target
486 application, then the SNA-network component of a transaction's
487 response time will approximately equal the host transit time (B - A)
488 described previously. A host TN3270E server implementation can,
489 however, typically support the establishment of sessions to target
490 applications in SNA hosts remote from itself. In this case the SNA-
491 network component of the response time equals the actual SNA-network
492 transit time plus two host transit times.
493
494
495
496
497
498
499
500 <span class="grey">White &amp; Moore Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
503
504
505 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Correlating TN3270E Server and Host Response Times</span>
506
507 It is possible that response time data is collected from TN3270E
508 servers at the same time as a management application is monitoring
509 the SNA sessions at a host. For example, a management application
510 can be monitoring a secondary logical unit (SLU) while retrieving
511 data from a TN3270E server. Consider the following figure:
512
513 ------------------------------------------------
514 | |
515 | Client TN3270E Target |
516 | Server SNA Host |
517 | Timestamps (PLU) |
518 | (SLU) Timestamps|
519 | &lt;---IP Network-------&gt;&lt;---SNA Network---&gt; |
520 | |
521 | request D A |
522 | ------------------------------------------&gt; |
523 | reply(DR) E B | |
524 | &lt;----------------------------------------&lt; |
525 | | +/-RSP F C |
526 | &gt;--------------------------------------&gt; |
527 | |
528 ------------------------------------------------
529
530 The following response times are available:
531
532 o Target SNA host transit time: Timestamp B - Timestamp A
533 o Target SNA host network transit time: Timestamp C - Timestamp B
534 o TN3270E server total response time: Timestamp F - Timestamp D
535 o TN3270E server IP-network component: Timestamp F - Timestamp E
536
537 The value added by the TN3270E server in this situation is its
538 approximation of the IP-network component of the overall response
539 time. The IP-network component can be subtracted from the total
540 network transit time (which can be captured at an SSCP monitoring SNA
541 traffic from/to the SLU) to see the actual SNA versus IP network
542 transit times.
543
544 The MIB defined by this memo does not specifically address
545 correlation of the data it contains with response time data collected
546 by direct monitoring of SNA resources: its focus is exclusively
547 response time data collection from a TN3270E server perspective. It
548 has, however, in conjunction with the TN3270E-MIB [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>], been
549 structured to provide the information necessary for correlation
550 between TN3270E server-provided response time information and that
551 gathered from directly monitoring SNA resources.
552
553
554
555
556 <span class="grey">White &amp; Moore Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
559
560
561 A management application attempting to correlate SNA resource usage
562 to Telnet clients can monitor either the tn3270eResMapTable or the
563 tn3270eTcpConnTable to determine resource-to-client address mappings.
564 Both of these tables are defined by the TN3270E-MIB [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>]. Another
565 helpful table is the tn3270eSnaMapTable, which provides a mapping
566 between SLU names as they are known at the SSCP (VTAM) and their
567 local names at the TN3270E server. Neither the
568 tn3270eClientGroupTable, the tn3270eResPoolTable, nor the
569 tn3270eClientResMapTable from the TN3270E-MIB can be used for
570 correlation, since the mappings defined by these tables can overlap,
571 and may not provide one-to-one mappings.
572
573 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Timestamp Calculation</span>
574
575 This section goes into more detail concerning when the various
576 timestamps can be taken as the flows between a TN3270E client and its
577 target SNA host pass through a TN3270E server. In addition,
578 information is provided on how the TN3270 TIMING-MARK
579 request/response flow can be used in place of DR for approximating IP
580 network transit times.
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">White &amp; Moore Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
615
616
617 <span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a> DR Usage</span>
618
619 Consider the following flow:
620
621 ----------------------------------------------------------
622 | |
623 | Client TN3270E Target SNA |
624 | Server Host |
625 | Timestamps |
626 | |
627 | &lt;---IP Network-------&gt;&lt;---SNA Network---&gt; |
628 | |
629 | request D (BB,CD,OIC,ER) |
630 | -------------------------------------------&gt; |
631 | reply(DR) (FIC,ER,EB) | |
632 | &lt;-----------------------------------------&lt; |
633 | reply (MIC,ER) |
634 | &lt;-----------------------------------------&lt; |
635 | reply (MIC,ER) |
636 | &lt;-----------------------------------------&lt; |
637 | reply E (LIC,DR) |
638 | &lt;-----------------------------------------&lt; |
639 | | +/-RSP F |
640 | &gt;----------------------------------------&gt; |
641 | |
642 | BB : Begin Bracket ER : Response by exception |
643 | EB : End Bracket DR : Definite Response Requested |
644 | CD : Change Direction FIC : First in chain |
645 | OIC: Only in chain MIC: Middle in chain |
646 | LIC: Last in chain |
647 ----------------------------------------------------------
648
649 Timestamp D is taken at the TN3270E server when the server has
650 received data from a client for forwarding to its target SNA host,
651 and the direction of the SNA session allows the server to forward the
652 data immediately (either the direction is inbound towards the SNA
653 host, or the session is between brackets). This is most likely when
654 the server finds the end of record indicator in the TCP data received
655 from the client.
656
657 The target SNA application returns its reply in one or more SNA
658 Request Units (RUs); in this example there are four RUs in the reply.
659 The first RU is marked as first in chain (FIC), the next two are
660 marked as middle in chain (MIC), and the last is marked as last in
661 chain (LIC). If the SNA host sends a multiple-RU chain, the server
662 does not know until the last RU is received whether DR is being
663 requested. The server's only chance to request DR from the client,
664 however, comes when it forwards the FIC RU, since this is the only
665
666
667
668 <span class="grey">White &amp; Moore Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
671
672
673 time that the TN3270E header is included. Since a server may forward
674 the FIC RU to the client before it receives the LIC RU from the SNA
675 host, some servers routinely specify DR on all FIC RUs.
676
677 If the server has specified DR on the TN3270E request for the FIC RU
678 in a chain, it takes timestamp E when it forwards the LIC RU to the
679 client. Since timestamp E is used for calculating the IP-network
680 time for the transaction, the server SHOULD take timestamp E as close
681 as possible to its "Telnet edge". The server takes timestamp F when
682 it receives the RESPONSES response from the client.
683
684 A target SNA application doesn't necessarily return data to a client
685 in a transaction; it may, for example, require more data from the
686 client before it can formulate a reply. In this case the application
687 may simply return to the TN3270E server a change of direction
688 indicator. At this point the server must send something to the
689 client (typically a Write operation with a WCC) to unlock the
690 keyboard. If the server specifies DR on the request to the client
691 triggered by its receipt of the change of direction indicator from
692 the SNA application, then timestamps E and F can be taken, and the
693 usual response times can be calculated. When the client sends in the
694 additional data and gets a textual response from the SNA application,
695 the server treats this as a separate transaction from the one
696 involving the change of direction.
697
698 <span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a> TIMING-MARK Usage</span>
699
700 It is possible for a TN3270E server to use the TIMING-MARK flow for
701 approximating IP network transit times. Using TIMING-MARKs would
702 make it possible for a server to collect performance data for TN3270
703 clients, as well as for TN3270E clients that do not support the
704 RESPONSES function. In order for TIMING-MARKs to be used in this
705 way, a client can't have the NOP option enabled, since responses are
706 needed to the server's TIMING-MARK requests. An IP network transit
707 time approximation using a TIMING-MARK is basically the amount of
708 time it takes for a TN3270 server to receive from a client a response
709 to a TIMING-MARK request.
710
711 To get an estimate for IP network transit time, a TN3270E server
712 sends a TIMING-MARK request to a client after a LIC RU has been
713 received, as a means of approximating IP network transit time:
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">White &amp; Moore Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
727
728
729 ---------------------------------------------------
730 | |
731 | Client TN3270E Target |
732 | Server Host |
733 | Timestamps |
734 | |
735 | &lt;---IP Network-------&gt;&lt;---SNA Network---&gt; |
736 | |
737 | request D (BB,CD,OIC,ER) |
738 | -------------------------------------------&gt; |
739 | reply (FIC,ER,EB) | |
740 | &lt;-----------------------------------------&lt; |
741 | reply (MIC,ER) |
742 | &lt;-----------------------------------------&lt; |
743 | reply (MIC,ER) |
744 | &lt;-----------------------------------------&lt; |
745 | reply E (LIC,ER) |
746 | &lt;-----------------------------------------&lt; |
747 | TIMING-MARK Rqst E' |
748 | &lt;--------------------- |
749 | | TIMING-MARK Rsp F' |
750 | &gt;-------------------&gt; |
751 | |
752 ---------------------------------------------------
753
754 The response times can then be calculated as follows:
755
756 o TN3270E server total response time:
757 (Timestamp E - Timestamp D) + (Timestamp F' - Timestamp E')
758
759 o TN3270E server IP network time: Timestamp F' - Timestamp E'
760
761 If a TN3270E server is performing the TIMING-MARK function
762 (independent of the response time monitoring use of the function
763 discussed here), then it most likely has a TIMING-MARK interval for
764 determining when to examine client sessions for sending the TIMING-
765 MARK request. This interval, which is ordinarily a global value for
766 an entire TN3270E server, is represented in the TN3270E-MIB by the
767 tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent
768 only if, when it is examined, a client session is found to have had
769 no activity for a different fixed length of time, represented in the
770 TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object.
771
772 Servers that support a large number of client sessions should spread
773 out the TIMING-MARK requests they send to these clients over the
774 activity interval, rather than sending them all in a single burst,
775 since otherwise the network may be flooded with TIMING-MARK requests.
776 When a server uses TIMING-MARKs for approximating response times,
777
778
779
780 <span class="grey">White &amp; Moore Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
783
784
785 this tends to introduce a natural spreading into its TIMING-MARK
786 requests, since the requests are triggered by the arrival of traffic
787 from an SNA host.
788
789 A TN3270E server MUST integrate its normal TIMING-MARK processing
790 with its use of TIMING-MARKs for computing response times. In
791 particular, it MUST NOT send a second TIMING-MARK request to a client
792 while waiting for the first to return, since this is ruled out by the
793 TIMING-MARK protocol itself. If a TIMING-MARK flow has just been
794 performed for a client shortly before the LIC RU arrives, the server
795 MAY use the interval from this flow as its approximation for IP
796 network transit time, (in other words, as its (F' - E') value) when
797 calculating its approximation for the transaction's total response
798 time, rather than sending a second TIMING-MARK request so soon after
799 the preceding one.
800
801 Regardless of when the server sends its TIMING-MARK request, the
802 accuracy of its total response time calculation depends on exactly
803 when the client responds to the TIMING-MARK request.
804
805 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Performance Data Modelling</span>
806
807 The following two subsections detail how the TN3270E-RT-MIB models
808 and controls capture of two types of response time data: average
809 response times and response time buckets.
810
811 <span class="h4"><a class="selflink" id="section-3.5.1" href="#section-3.5.1">3.5.1</a> Averaging Response Times</span>
812
813 Average response times play two different roles in the MIB:
814
815 o They are made available for management applications to retrieve.
816 o They serve as triggers for emitting notifications.
817
818 Sliding-window averages are used rather than straight interval-based
819 averages, because they are often more meaningful, and because they
820 cause less notification thrashing. Sliding-window average
821 calculation can, if necessary, be disabled, by setting the sample
822 period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the
823 sample period, tn3270eRtCollCtlSPeriod, to the required collection
824 interval.
825
826 In order to calculate sliding-window averages, a TN3270E server MUST:
827
828 o Select a fixed, relatively short, sample period SPeriod; the
829 default value for SPeriod in the MIB is 20 seconds.
830
831
832
833
834
835
836 <span class="grey">White &amp; Moore Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
839
840
841 o Select an averaging period multiplier SPMult. The actual
842 collection interval will then be SPMult times SPeriod. The
843 default value for SPMult in the MIB is 30, yielding a default
844 collection interval of 10 minutes. Note that the collection
845 interval (SPMult*SPeriod) is always a multiple of the sample
846 period.
847
848 Clearlly, SPMult*SPeriod should not be thought of as literally
849 the averaging period. The average calculated will include
850 contributions older than that time, and does not weight equally
851 all contributions since that time. In fact, it gives a smoother
852 result than a traditional sliding average, as used in finance.
853 More subtly, it is best to think of the effective averaging
854 period as being 2*SPMult*SPeriod. To see this, consider how long
855 the contribution to the result made by a particular transaction
856 lasts. With a traditional sliding average, it lasts exactly the
857 averaging period. With the aging mechanism described here, it
858 has a half-life of SPMult*SPeriod.
859
860 o Maintain the following counters to keep track of activity within
861 the current sample period; these are internal counters, not made
862 visible to a management application via the MIB.
863
864 - T (number of transactions in the period)
865
866 - TotalRts (sum of the total response times for all
867 transactions in the period)
868
869 - TotalIpRts (sum of the IP network transit times for all
870 transactions in the period; note that if IP network transit
871 times are being excluded from the response time collection,
872 this value will always be 0).
873
874 o Also maintain sliding counters, initialized to zero, for each of
875 the quantities being counted:
876
877 - AvgCountTrans (sliding count of transactions)
878 - TotalRtsSliding (sliding count of total response times)
879 - TotalIpRtsSliding (sliding count of IP network transit times)
880
881 o At the end of each sample period, update the sliding interval
882 counters, using the following floating-point calculations:
883
884 AvgCountTrans = AvgCountTrans + T
885 - (AvgCountTrans / SPMult)
886
887 TotalRtsSliding = TotalRtsSliding + TotalRts
888 - (TotalRtsSliding / SPMult)
889
890
891
892 <span class="grey">White &amp; Moore Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
895
896
897 TotalIpRtsSliding = TotalIpRtsSliding + TotalIpRts
898 - (TotalIpRtsSliding / SPMult)
899
900 Then reset T, TotalRts, and TotalIpRts to zero for use during the
901 next sample period.
902
903 o At the end of a collection interval, update the following MIB
904 objects as indicated; the floating-point numbers are rounded
905 rather than truncated.
906
907 tn3270eRtDataAvgCountTrans = AvgCountTrans
908 tn3270eRtDataAvgRt = TotalRtsSliding / AvgCountTrans
909 tn3270eRtDataAvgIpRt = TotalIpRtsSliding / AvgCountTrans
910
911 As expected, if IP network transit times are being excluded from
912 response time collection, then tn3270eRtDataAvgIpRt will always
913 return 0.
914
915 The sliding transaction counter AvgCountTrans is not used for
916 updating the MIB object tn3270eRtDataCountTrans: this object is an
917 ordinary SMI Counter32, which maintains a total count of transactions
918 since its last discontinuity event. The sliding counters are used
919 only for calculating averages.
920
921 Two mechanisms are present in the MIB to inhibit the generation of an
922 excessive number of notifications related to average response times.
923 First, there are high and low thresholds for average response times.
924 A tn3270eRtExceeded notification is generated the first time a
925 statistically significant average response time is found to have
926 exceeded the high threshold. (The test for statistical significance
927 is described below.) After this, no other tn3270eRtExceeded
928 notifications are generated until an average response time is found
929 to have fallen below the low threshold.
930
931 The other mechanism to limit notifications is the significance test
932 for a high average response time. Intuitively, the significance of
933 an average is directly related to the number of samples that go into
934 it; so we might be inclined to use a rule such as "for the purpose of
935 generating tn3270eRtExceeded notifications, ignore average response
936 times based on fewer than 20 transactions in the sample period."
937
938 In the case of response times, however, the number of transactions
939 sampled in a fixed sampling period is tied to these transactions'
940 response times. A few transactions with long response times can
941 guarantee that there will not be many transactions in a sample,
942 because these transactions "use up" the sampling time. Yet this case
943
944
945
946
947
948 <span class="grey">White &amp; Moore Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
951
952
953 of a few transactions with very poor response times should obviously
954 be classified as a problem, not as a statistical anomaly based on too
955 small a sample.
956
957 The solution is to make the significance level for a sample a
958 function of the average response time. A value IdleCount is
959 specified, which is used to qualify an sample as statistically
960 significant. In order to determine at a collection interval whether
961 to generate a tn3270eRtExceeded notification, a TN3270E server uses
962 the following algorithm:
963
964 if AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &gt;= IdleCount
965 then generate the notification,
966
967 where AvgRt is the value that would be returned by the object
968 tn3270eRtDataAvgRt at the end of the interval, and the "**" notation
969 indicates exponientiation.
970
971 Two examples illustrate how this algorithm works. Suppose that
972 IdleCount has been set to 20 transactions, and the high threshold to
973 200 msecs per transaction. If the average observed response time is
974 300 msecs, then a notification will be generated only if
975 AvgCountTrans &gt;= 80. If, however, the observed response time is 500
976 msecs, then a notification is generated if AvgCountTrans &gt;= 9.
977
978 There is no corresponding significance test for the tn3270eRtOkay
979 notification: this notification is generated based on an average
980 response time that falls below the low threshold, regardless of the
981 sample size behind that average.
982
983 <span class="h4"><a class="selflink" id="section-3.5.2" href="#section-3.5.2">3.5.2</a> Response Time Buckets</span>
984
985 The MIB also supports collection of response time data into a set of
986 five buckets. This data is suitable either for verification of
987 service level agreements, or for monitoring by a management
988 application to identify performance problems. The buckets provide
989 counts of transactions whose total response times fall into a set of
990 specified ranges.
991
992 Like everything for a collection, the "total" response times
993 collected in the buckets are governed by the specification of whether
994 IP network transit times are to be included in the totals. Depending
995 on how this option is specified, the response times being counted in
996 the buckets will either be total response times (F - D), or only SNA
997 network transit times (effectively E - D, because when it is
998 excluding the IP-network component of transactions, a server makes
999 timestamp F identical to timestamp E).
1000
1001
1002
1003
1004 <span class="grey">White &amp; Moore Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1007
1008
1009 Four bucket boundaries are specified for a response time collection,
1010 resulting in five buckets. The first response time bucket counts
1011 those transactions whose total response times were less than or equal
1012 to Boundary 1, the second bucket counts those whose response times
1013 were greater than Boundary 1 but less than or equal to Boundary 2,
1014 and so on. The fifth bucket is unbounded on the top, counting all
1015 transactions whose response times were greater than Boundary 4.
1016
1017 The four bucket boundaries have default values of: 1 second, 2
1018 seconds, 5 seconds, and 10 seconds, respectively. These values are
1019 the defaults in the 3174 controller's implementation of the SNA/MS
1020 RTM function, and are thought to be appropriate for this MIB as well.
1021
1022 In SNA/MS the counter buckets were (by today's standards) relatively
1023 small, with a maximum value of 65,535. The bucket objects in the MIB
1024 are all Counter32's.
1025
1026 The following figure represents the buckets pictorially:
1027
1028 ----------------------------------------------
1029 | |
1030 | Response Time Boundaries |
1031 | | | | | | | |
1032 | | | | | | | |
1033 | | | | | | no |
1034 | 0 B-1 B-2 B-3 B-4 bound|
1035 | | | | | | | |
1036 | |Bucket1|Bucket2|Bucket3|Bucket4|Bucket5| |
1037 | ----------------------------------------- |
1038 | |
1039 ----------------------------------------------
1040
1041 <span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> Structure of the MIB</span>
1042
1043 The TN3270E-RT-MIB has the following components:
1044
1045 o tn3270eRtCollCtlTable
1046 o tn3270eRtDataTable
1047 o Notifications
1048 o Advisory Spin Lock Usage
1049
1050 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> tn3270eRtCollCtlTable</span>
1051
1052 The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and
1053 tn3270eClientGroupName imported from the TN3270E-MIB.
1054 tn3270eSrvrConfIndex identifies within a host a particular TN3270E
1055
1056
1057
1058
1059
1060 <span class="grey">White &amp; Moore Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1063
1064
1065 server. tn3270eClientGroupName identifies a collection of IP clients
1066 for which response time data is to be collected. The set of clients
1067 is defined using the tn3270eClientGroupTable from the TN3270E-MIB.
1068
1069 A tn3270eRtCollCtlEntry contains the following objects:
1070
1071 --------------------------------------------------
1072 1st Index | tn3270eSrvrConfIndex Unsigned32 |
1073 2nd Index | tn3270eClientGroupName Utf8String |
1074 | tn3270eRtCollCtlType BITS |
1075 | tn3270eRtCollCtlSPeriod Unsigned32 |
1076 | tn3270eRtCollCtlSPMult Unsigned32 |
1077 | tn3270eRtCollCtlThreshHigh Unsigned32 |
1078 | tn3270eRtCollCtlThreshLow Unsigned32 |
1079 | tn3270eRtCollCtlIdleCount Unsigned32 |
1080 | tn3270eRtCollCtlBucketBndry1 Unsigned32 |
1081 | tn3270eRtCollCtlBucketBndry2 Unsigned32 |
1082 | tn3270eRtCollCtlBucketBndry3 Unsigned32 |
1083 | tn3270eRtCollCtlBucketBndry4 Unsigned32 |
1084 | tn3270eRtCollCtlRowStatus RowStatus |
1085 --------------------------------------------------
1086
1087 The tn3270eRtCollCtlType object controls the type(s) of response time
1088 collection that occur, the granularity of the collection, whether
1089 dynamic definite responses SHOULD be initiated, and whether
1090 notifications SHOULD be generated. This object is of BITS SYNTAX,
1091 and thus allows selection of multiple options.
1092
1093 The BITS in the tn3270eRtCollCtlType object have the following
1094 meanings:
1095
1096 o aggregate(0) - If this bit is set to 1, then data SHOULD be
1097 aggregated for the whole client group. In this case there will
1098 be only one row created for the collection in the
1099 tn3270eRtDataTable. The first two indexes for this row,
1100 tn3270eSrvrConfIndex and tn3270eClientGroupName, will have the
1101 same values as the indexes for the corresponding
1102 tn3270eRtCollCtlEntry. The third and fourth indexes of an
1103 aggregated tn3270eRtDataEntry have the values unknown(0)
1104 (tn3270eRtDataClientAddrType) and a zero-length octet string
1105 (tn3270eRtDataClientAddress). The fifth index,
1106 tn3270eRtDataClientPort, has the value 0.
1107
1108 If this bit is set to 0, then a separate entry is created in the
1109 tn3270eRtDataTable from each member of the client group. In this
1110 case tn3270eRtDataClientAddress contains the client's actual IP
1111
1112
1113
1114
1115
1116 <span class="grey">White &amp; Moore Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1119
1120
1121 Address, tn3270eRtDataClientAddrType indicates the address type,
1122 and tn3270eRtDataClientPort contains the number of the port the
1123 client is using for its TN3270/TN3270E session.
1124
1125 o excludeIpComponent(1) - If this bit is set to 1, then the server
1126 SHOULD exclude the IP-network component from all the response
1127 times for this collection. If the target SNA application
1128 specifies DR in any of its replies, this DR will still be passed
1129 down to the client, and the client's response will still be
1130 forwarded to the application. But this response will play no
1131 role in the server's response time calculations.
1132
1133 If this bit is set to 0, then the server includes in the
1134 collection only those transactions for which it can include an
1135 (approximate) IP-network component in the total response time for
1136 the transaction. This component MAY be derived from a "natural"
1137 DR (if the client supports the RESPONSES function), from a
1138 dynamic DR introduced by the server (if the client supports the
1139 RESPONSES function and the ddr(2) bit has been set to 1), or from
1140 TIMING-MARK processing (if the client supports TIMING-MARKs).
1141
1142 If this bit is set to 1, then the ddr(2) bit is ignored, since
1143 there is no reason for the server to request additional responses
1144 from the client(s) in the group.
1145
1146 o ddr(2) - If this bit is set to 1, then the server SHOULD, for
1147 those clients in the group that support the RESPONSES function,
1148 add a DR request to the FIC reply in each transaction, and use
1149 the client's subsequent response for calculating an (approximate)
1150 IP-network component to include in the transaction's total
1151 response times.
1152
1153 If this bit is set to 0, then the server does not add a DR
1154 request that it was not otherwise going to add to any replies
1155 from the target SNA application.
1156
1157 If the excludeIpComponent(1) bit is set to 1, then this bit is
1158 ignored by the server.
1159
1160 o average(3) - If this bit is set to 1, then the server SHOULD
1161 calculate a sliding-window average for the collection, based on
1162 the parameters specified for the group.
1163
1164 If this bit is set to 0, then an average is not calculated. In
1165 this case the tn3270eRtExceeded and tn3270eRtOkay notifications
1166 are not generated, even if the traps(5) bit is set to 1.
1167
1168
1169
1170
1171
1172 <span class="grey">White &amp; Moore Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1175
1176
1177 o buckets(4) - If this bit is set to 1, then the server SHOULD
1178 create and increment response time buckets for the collection,
1179 based on the parameters specified for the group.
1180
1181 If this bit is set to 0, then response time buckets are not
1182 created.
1183
1184 o traps(5) - If this bit is set to 1, then a TN3270E Server is
1185 enabled to generate notifications pertaining to an
1186 tn3270eCollCtlEntry. tn3270CollStart and tn3270CollEnd
1187 generation is enabled simply by traps(5) being set to 1.
1188 tn3270eRtExceeded and tn3270eRtOkay generation enablement
1189 requires that average(3) be set to 1 in addition to the traps(5)
1190 requirement.
1191
1192 If traps(5) is set to 0, then none of the notifications defined
1193 in this MIB are generated for a particular tn3270eRtCollCtlEntry.
1194
1195 Either the average(3) or the buckets(4) bit MUST be set to 1 in order
1196 for response time data collection to occur; both bits MAY be set to
1197 1. If the average(3) bit is set to 1, then the following objects
1198 have meaning, and are used to control the calculation of the
1199 averages, as well as the generation of the two notifications related
1200 to them:
1201
1202 o tn3270eRtCollCtlSPeriod
1203 o tn3270eRtCollCtlSPMult
1204 o tn3270eRtCollCtlThreshHigh
1205 o tn3270eRtCollCtlThreshLow
1206 o tn3270eRtCollCtlIdleCount
1207
1208 The previous objects' values are meaningless if the associated
1209 average(3) bit is not set to 1.
1210
1211 If the buckets(4) bit is set to 1, then the following objects have
1212 meaning, and specify the bucket boundaries:
1213
1214 o tn3270eRtCollCtlBucketBndry1
1215 o tn3270eRtCollCtlBucketBndry2
1216 o tn3270eRtCollCtlBucketBndry3
1217 o tn3270eRtCollCtlBucketBndry4
1218
1219 The previous objects' values are meaningless if the associated
1220 buckets(4) bit is not set to 1.
1221
1222 If an entry in the tn3270RtCollCtlTable has the value active(1) for
1223 its RowStatus, then an implementation SHALL NOT allow Set operations
1224 for any objects in the entry except:
1225
1226
1227
1228 <span class="grey">White &amp; Moore Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1231
1232
1233 o tn3270eRtCollCtlThreshHigh
1234 o tn3270eRtCollCtlThreshLow
1235 o tn3270eRtCollCtlRowStatus
1236
1237 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> tn3270eRtDataTable</span>
1238
1239 Either a single entry or multiple entries are created in the
1240 tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on
1241 whether tn3270eRtCollCtlType in the control entry has aggregate(0)
1242 selected. The contents of an entry in the tn3270eRtDataTable depend
1243 on the contents of the corresponding entry in the
1244 tn3270eRtCollCtlTable: as described above, some objects in the data
1245 entry return meaningful values only when the average(3) option is
1246 selected in the control entry, while others return meaningful values
1247 only when the buckets(4) option is selected. If both options are
1248 selected, then all the objects return meaningful values. When an
1249 object is not specified to return a meaningful value, an
1250 implementation may return any syntactically valid value in response
1251 to a Get operation.
1252
1253 The following objects return meaningful values if and only if the
1254 average(3) option was selected in the corresponding
1255 tn3270eRtCollCtlEntry:
1256
1257 o tn3270eRtDataAvgRt
1258 o tn3270eRtDataAvgIpRt
1259 o tn3270eRtDataAvgCountTrans
1260 o tn3270eRtDataIntTimeStamp
1261 o tn3270eRtDataTotalRts
1262 o tn3270eRtDataTotalIpRts
1263 o tn3270eRtDataCountTrans
1264 o tn3270eRtDataCountDrs
1265 o tn3270eRtDataElapsRndTrpSq
1266 o tn3270eRtDataElapsIpRtSq
1267
1268 The first three objects in this list return values derived from the
1269 sliding-window average calculations described earlier. The time of
1270 the most recent sample for these calculations is returned in the
1271 tn3270eRtDataIntTimeStamp object. The next four objects are normal
1272 Counter32 objects, maintaining counts of total response time and
1273 total transactions. The last two objects return sum of the squares
1274 values, to enable variance calculations by a management application.
1275
1276 The following objects return meaningful values if and only if the
1277 buckets(4) option was selected in the corresponding
1278 tn3270eRtCollCtlEntry:
1279
1280
1281
1282
1283
1284 <span class="grey">White &amp; Moore Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1287
1288
1289 o tn3270eRtDataBucket1Rts
1290 o tn3270eRtDataBucket2Rts
1291 o tn3270eRtDataBucket3Rts
1292 o tn3270eRtDataBucket4Rts
1293 o tn3270eRtDataBucket5Rts
1294
1295 A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used
1296 by a management application to detect when the values of the counter
1297 objects in this table may have been reset, or otherwise experienced a
1298 discontinuity. A possible cause for such a discontinuity is the
1299 TN3270E server's being stopped or restarted. This object returns a
1300 meaningful value regardless of which collection control options were
1301 selected.
1302
1303 An object, tn3270eRtDataRtMethod, identifies whether the IP Network
1304 Time was calculated using either the definite response or TIMING-MARK
1305 approach.
1306
1307 When an entry is created in the tn3270eRtCollCtlTable with its
1308 tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is
1309 automatically created in the tn3270eRtDataTable; this entry's
1310 tn3270eRtDataClientAddress has the value of a zero-length octet
1311 string, its tn3270eRtDataClientAddrType has the value of unknown(0),
1312 and its tn3270eRtDataClientPort has the value 0.
1313
1314 When an entry is created in the tn3270eRtCollCtlTable with its
1315 tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is
1316 created in the tn3270eRtDataTable for each member of the client group
1317 that currently has a session with the TN3270E server. Entries are
1318 subsequently created for clients that the TN3270E server determines
1319 to be members of the client group when these clients establish
1320 sessions with the server. Entries are also created when clients with
1321 existing sessions are added to the group.
1322
1323 All entries associated with a tn3270eRtCollCtlEntry are deleted from
1324 the tn3270eRtDataTable when that entry is deleted from the
1325 tn3270eRtCollCtlTable. An entry for an individual client in a client
1326 group is deleted when its TCP connection terminates. Once it has
1327 been created, a client's entry in the tn3270eRtDataTable remains
1328 active as long as the collection's tn3270eRtCollCtlEntry exists, even
1329 if the client is removed from the client group for the
1330 tn3270eRtCollCtlEntry.
1331
1332 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Notifications</span>
1333
1334 This MIB defines four notifications related to a tn3270eRtDataEntry.
1335 If the associated tn3270eRtCollCtlType object's traps(5) bit is set
1336 to 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications
1337
1338
1339
1340 <span class="grey">White &amp; Moore Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1343
1344
1345 are generated when, respsectively, the tn3270eRtDataEntry is created
1346 and deleted. If, in addition, this tn3270eRtCollCtlType object's
1347 average(3) bit is set to 1, then the the tn3270eRtExceeded and
1348 tn3270eRtOkay notifications are generated when the conditions they
1349 report occur.
1350
1351 The following notifications are defined by this MIB:
1352
1353 o tn3270eRtExceeded - The purpose of this notification is to signal
1354 that a performance problem has been detected. If average(3)
1355 response time data is being collected, then this notification is
1356 generated whenever (1) an average response time is first found,
1357 on a collection interval boundary, to have exceeded the high
1358 threshold tn3270eRtCollCtlThreshHigh specified for the client
1359 group, AND (2) the sample on which the average is based is
1360 determined to have been a significant one, via the significance
1361 algorithm described earlier. This notification is not generated
1362 again for a tn3270eRtDataEntry until an average response time
1363 falling below the low threshold tn3270eRtCollCtlThreshLow
1364 specified for the client group has occurred for the entry.
1365
1366 o tn3270eRtOkay - The purpose of this notification is to signal
1367 that a previously reported performance problem has been resolved.
1368 If average(3) response time data is being collected, then this
1369 notification is generated whenever (1) a tn3270eRtExceeded
1370 notification has already been generated, AND (2) an average
1371 response time is first found, on a collection interval boundary,
1372 to have fallen below the low threshold tn3270eRtCollCtlThreshLow
1373 specified for the client group. This notification is not
1374 generated again for a tn3270eRtDataEntry until an average
1375 response time exceeding the high threshold
1376 tn3270eRtCollCtlThreshHigh specified for the client group has
1377 occurred for the entry.
1378
1379 Taken together, the two preceding notifications serve to minimize the
1380 generation of an excessive number of traps in the case of an average
1381 response time that oscillates about its high threshold.
1382
1383 o tn3270eRtCollStart - This notification is generated whenever data
1384 collection begins for a client group, or when a new
1385 tn3270eRtDataEntry becomes active. The primary purpose of this
1386 notification is signal to a management application that a new
1387 client TCP session has been established, and to provide the IP-
1388 to-resource mapping for the session. This notification is not
1389 critical when average(3) data collection is not being performed
1390 for the client group.
1391
1392
1393
1394
1395
1396 <span class="grey">White &amp; Moore Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1399
1400
1401 o tn3270eRtCollEnd - This notification is generated whenever a data
1402 collection ends. For an aggregate collection, this occurs when
1403 the corresponding tn3270eRtCollCtlEntry is deleted. For an
1404 individual collection, this occurs either when the
1405 tn3270eRtCollCtlEntry is deleted, or when the client's TCP
1406 connection terminates. The purpose of this notification is to
1407 enable a management application to complete a monitoring function
1408 that it was performing, by returning final values for the
1409 collection's data objects.
1410
1411 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Advisory Spin Lock Usage</span>
1412
1413 Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an
1414 advisory lock that allows cooperating TN3270E-RT-MIB applications to
1415 coordinate their use of the tn3270eRtCollCtlTable. When creating a
1416 new entry or altering an existing entry in the tn3270eRtCollCtlTable,
1417 an application SHOULD make use of tn3270eRtSpinLock to serialize
1418 application changes or additions. Since this is an advisory lock,
1419 its use by management applications SHALL NOT be enforced by agents.
1420 Agents MUST, however, implement the tn3270eRtSpinLock object.
1421
1422 <span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> Definitions</span>
1423
1424 TN3270E-RT-MIB DEFINITIONS ::= BEGIN
1425
1426 IMPORTS
1427 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
1428 Counter32, Unsigned32, Gauge32
1429 FROM SNMPv2-SMI
1430 RowStatus, DateAndTime, TimeStamp, TestAndIncr
1431 FROM SNMPv2-TC
1432 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
1433 FROM SNMPv2-CONF
1434 tn3270eSrvrConfIndex, tn3270eClientGroupName,
1435 tn3270eResMapElementType
1436 FROM TN3270E-MIB
1437 IANATn3270eAddrType, IANATn3270eAddress
1438 FROM IANATn3270eTC-MIB
1439 snanauMIB
1440 FROM SNA-NAU-MIB;
1441
1442 tn3270eRtMIB MODULE-IDENTITY
1443 LAST-UPDATED "9807270000Z" -- July 27, 1998
1444 ORGANIZATION "TN3270E Working Group"
1445 CONTACT-INFO
1446 "Kenneth White ([email protected])
1447 IBM Corp. - Dept. BRQA/Bldg. 501/G114
1448 P.O. Box 12195
1449
1450
1451
1452 <span class="grey">White &amp; Moore Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1455
1456
1457 3039 Cornwallis
1458 RTP, NC 27709-2195
1459
1460 Robert Moore ([email protected])
1461 IBM Corp. - Dept. BRQA/Bldg. 501/G114
1462 P.O. Box 12195
1463 3039 Cornwallis
1464 RTP, NC 27709-2195
1465 (919) 254-4436"
1466 DESCRIPTION
1467 "This module defines a portion of the management
1468 information base (MIB) that enables monitoring of
1469 TN3270 and TN3270E clients' response times by a
1470 TN3270E server."
1471 REVISION "9807270000Z" -- July 27, 1998
1472 DESCRIPTION
1473 "RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
1474 ::= { snanauMIB 9 }
1475 -- snanauMIB ::= { mib-2 34 }
1476
1477 -- Top level structure of the MIB
1478
1479 tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 }
1480 tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 }
1481 tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 }
1482
1483 -- MIB Objects
1484
1485 -- Response Time Control Table
1486
1487 tn3270eRtCollCtlTable OBJECT-TYPE
1488 SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry
1489 MAX-ACCESS not-accessible
1490 STATUS current
1491 DESCRIPTION
1492 "The response time monitoring collection control table,
1493 which allows a management application to control the
1494 types of response time data being collected, and the
1495 clients for which it is being collected.
1496
1497 This table is indexed by tn3270eSrvrConfIndex and
1498 tn3270eClientGroupName imported from the
1499 TN3270E-MIB. tn3270eSrvrConfIndex indicates within
1500 a host which TN3270E server an entry applies to.
1501 tn3270eClientGroupName it identifies the set of IP
1502 clients for which response time data is being collected.
1503 The particular IP clients making up the set are identified
1504 in the tn3270eClientGroupTable in the TN3270E-MIB."
1505
1506
1507
1508 <span class="grey">White &amp; Moore Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1511
1512
1513 ::= { tn3270eRtObjects 1}
1514
1515 tn3270eRtCollCtlEntry OBJECT-TYPE
1516 SYNTAX Tn3270eRtCollCtlEntry
1517 MAX-ACCESS not-accessible
1518 STATUS current
1519 DESCRIPTION
1520 "An entry in the TN3270E response time monitoring collection
1521 control table. To handle the case of multiple TN3270E
1522 servers on the same host, the first index of this table is
1523 the tn3270eSrvrConfIndex from the TN3270E-MIB."
1524 INDEX {
1525 tn3270eSrvrConfIndex, -- Server's index
1526 tn3270eClientGroupName } -- What to collect on
1527 ::= { tn3270eRtCollCtlTable 1 }
1528
1529 Tn3270eRtCollCtlEntry ::= SEQUENCE {
1530 tn3270eRtCollCtlType BITS,
1531 tn3270eRtCollCtlSPeriod Unsigned32,
1532 tn3270eRtCollCtlSPMult Unsigned32,
1533 tn3270eRtCollCtlThreshHigh Unsigned32,
1534 tn3270eRtCollCtlThreshLow Unsigned32,
1535 tn3270eRtCollCtlIdleCount Unsigned32,
1536 tn3270eRtCollCtlBucketBndry1 Unsigned32,
1537 tn3270eRtCollCtlBucketBndry2 Unsigned32,
1538 tn3270eRtCollCtlBucketBndry3 Unsigned32,
1539 tn3270eRtCollCtlBucketBndry4 Unsigned32,
1540 tn3270eRtCollCtlRowStatus RowStatus }
1541
1542 -- The OID { tn3270eRtCollCtlEntry 1 } is not used
1543
1544 tn3270eRtCollCtlType OBJECT-TYPE
1545 SYNTAX BITS {
1546 aggregate(0),
1547 excludeIpComponent(1),
1548 ddr(2),
1549 average(3),
1550 buckets(4),
1551 traps(5)
1552 }
1553 MAX-ACCESS read-create
1554 STATUS current
1555 DESCRIPTION
1556 "This object controls what types of response time data to
1557 collect, whether to summarize the data across the members
1558 of a client group or keep it individually, whether to
1559 introduce dynamic definite responses, and whether to
1560 generate traps.
1561
1562
1563
1564 <span class="grey">White &amp; Moore Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1567
1568
1569 aggregate(0) - Aggregate response time data for the
1570 client group as a whole. If this bit
1571 is set to 0, then maintain response
1572 time data separately for each member
1573 of the client group.
1574 excludeIpComponent(1) - Do not include the IP-network
1575 component in any response times.
1576 ddr(2) - Enable dynamic definite response.
1577 average(3) - Produce an average response time
1578 based on a specified collection
1579 interval.
1580 buckets(4) - Maintain tn3270eRtDataBucket values in
1581 a corresponding tn3270eRtDataEntry,
1582 based on the bucket boundaries specified
1583 in the tn3270eRtCollCtlBucketBndry
1584 objects .
1585 traps(5) - generate the notifications specified
1586 in this MIB module. The
1587 tn3270eRtExceeded and tn3270eRtOkay
1588 notifications are generated only if
1589 average(3) is also specified."
1590 ::= { tn3270eRtCollCtlEntry 2 }
1591
1592 tn3270eRtCollCtlSPeriod OBJECT-TYPE
1593 SYNTAX Unsigned32 (15..86400) -- 15 second min, 24 hour max
1594 UNITS "seconds"
1595 MAX-ACCESS read-create
1596 STATUS current
1597 DESCRIPTION
1598 "The number of seconds that defines the sample period.
1599 The actual interval is defined as tn3270eRtCollCtlSPeriod
1600 times tn3270eRtCollCtlSPMult.
1601
1602 The value of this object is used only if the corresponding
1603 tn3270eRtCollCtlType has the average(3) setting."
1604 DEFVAL {20} -- 20 seconds
1605 ::= { tn3270eRtCollCtlEntry 3 }
1606
1607 tn3270eRtCollCtlSPMult OBJECT-TYPE
1608 SYNTAX Unsigned32 (1..5760) -- 5760 x SPeriod of 15 is 24 hours
1609 UNITS "period"
1610 MAX-ACCESS read-create
1611 STATUS current
1612 DESCRIPTION
1613 "The sample period multiplier; this value is multiplied by
1614 the sample period, tn3270eRtCollCtlSPeriod, to determine
1615 the collection interval.
1616
1617
1618
1619
1620 <span class="grey">White &amp; Moore Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1623
1624
1625 Sliding-window average calculation can, if necessary, be
1626 disabled, by setting the sample period multiplier,
1627 tn3270eRtCollCtlSPMult, to 1, and setting the sample
1628 period, tn3270eRtCollCtlSPeriod, to the required
1629 collection interval.
1630
1631 The value of this object is used only if the corresponding
1632 tn3270eRtCollCtlType has the average(3) setting."
1633 DEFVAL { 30 } -- yields an interval of 10 minutes when
1634 -- used with the default SPeriod value
1635 ::= { tn3270eRtCollCtlEntry 4 }
1636
1637 tn3270eRtCollCtlThreshHigh OBJECT-TYPE
1638 SYNTAX Unsigned32
1639 UNITS "seconds"
1640 MAX-ACCESS read-create
1641 STATUS current
1642 DESCRIPTION
1643 "The threshold for generating a tn3270eRtExceeded
1644 notification, signalling that a monitored total response
1645 time has exceeded the specified limit. A value of zero
1646 for this object suppresses generation of this notification.
1647 The value of this object is used only if the corresponding
1648 tn3270eRtCollCtlType has average(3) and traps(5) selected.
1649
1650 A tn3270eRtExceeded notification is not generated again for a
1651 tn3270eRtDataEntry until an average response time falling below
1652 the low threshold tn3270eRtCollCtlThreshLow specified for the
1653 client group has occurred for the entry."
1654
1655 DEFVAL { 0 } -- suppress notifications
1656 ::= { tn3270eRtCollCtlEntry 5 }
1657
1658 tn3270eRtCollCtlThreshLow OBJECT-TYPE
1659 SYNTAX Unsigned32
1660 UNITS "seconds"
1661 MAX-ACCESS read-create
1662 STATUS current
1663 DESCRIPTION
1664 "The threshold for generating a tn3270eRtOkay notification,
1665 signalling that a monitored total response time has fallen
1666 below the specified limit. A value of zero for this object
1667 suppresses generation of this notification. The value of
1668 this object is used only if the corresponding
1669 tn3270eRtCollCtlType has average(3) and traps(5) selected.
1670
1671 A tn3270eRtOkay notification is not generated again for a
1672 tn3270eRtDataEntry until an average response time
1673
1674
1675
1676 <span class="grey">White &amp; Moore Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1679
1680
1681 exceeding the high threshold tn3270eRtCollCtlThreshHigh
1682 specified for the client group has occurred for the entry."
1683 DEFVAL { 0 } -- suppress notifications
1684 ::= { tn3270eRtCollCtlEntry 6 }
1685
1686 tn3270eRtCollCtlIdleCount OBJECT-TYPE
1687 SYNTAX Unsigned32
1688 UNITS "transactions"
1689 MAX-ACCESS read-create
1690 STATUS current
1691 DESCRIPTION
1692 "The value of this object is used to determine whether a
1693 sample that yields an average response time exceeding the
1694 value of tn3270eRtCollCtlThreshHigh was a statistically
1695 valid one. If the following statement is true, then the
1696 sample was statistically valid, and so a tn3270eRtExceeded
1697 notification should be generated:
1698
1699 AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) &gt;= IdleCount
1700
1701 This comparison is done only if the corresponding
1702 tn3270eRtCollCtlType has average(3) and traps(5) selected."
1703 DEFVAL { 1 }
1704 ::= { tn3270eRtCollCtlEntry 7 }
1705
1706 tn3270eRtCollCtlBucketBndry1 OBJECT-TYPE
1707 SYNTAX Unsigned32
1708 UNITS "tenths of seconds"
1709 MAX-ACCESS read-create
1710 STATUS current
1711 DESCRIPTION
1712 "The value of this object defines the range of transaction
1713 response times counted in the Tn3270eRtDataBucket1Rts
1714 object: those less than or equal to this value."
1715 DEFVAL { 10 }
1716 ::= { tn3270eRtCollCtlEntry 8 }
1717
1718 tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE
1719 SYNTAX Unsigned32
1720 UNITS "tenths of seconds"
1721 MAX-ACCESS read-create
1722 STATUS current
1723 DESCRIPTION
1724 "The value of this object, together with that of the
1725 tn3270eRtCollCtlBucketBndry1 object, defines the range
1726 of transaction response times counted in the
1727 Tn3270eRtDataBucket2Rts object: those greater than the
1728 value of the tn3270eRtCollCtlBucketBndry1 object, and
1729
1730
1731
1732 <span class="grey">White &amp; Moore Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1735
1736
1737 less than or equal to the value of this object."
1738 DEFVAL { 20 }
1739 ::= { tn3270eRtCollCtlEntry 9 }
1740
1741 tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE
1742 SYNTAX Unsigned32
1743 UNITS "tenths of seconds"
1744 MAX-ACCESS read-create
1745 STATUS current
1746 DESCRIPTION
1747 "The value of this object, together with that of the
1748 tn3270eRtCollCtlBucketBndry2 object, defines the range of
1749 transaction response times counted in the
1750 Tn3270eRtDataBucket3Rts object: those greater than the
1751 value of the tn3270eRtCollCtlBucketBndry2 object, and less
1752 than or equal to the value of this object."
1753 DEFVAL { 50 }
1754 ::= { tn3270eRtCollCtlEntry 10 }
1755
1756 tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE
1757 SYNTAX Unsigned32
1758 UNITS "tenths of seconds"
1759 MAX-ACCESS read-create
1760 STATUS current
1761 DESCRIPTION
1762 "The value of this object, together with that of the
1763 tn3270eRtCollCtlBucketBndry3 object, defines the range
1764 of transaction response times counted in the
1765 Tn3270eRtDataBucket4Rts object: those greater than the
1766 value of the tn3270eRtCollCtlBucketBndry3 object, and
1767 less than or equal to the value of this object.
1768
1769 The value of this object also defines the range of
1770 transaction response times counted in the
1771 Tn3270eRtDataBucket5Rts object: those greater than the
1772 value of this object."
1773 DEFVAL { 100 }
1774 ::= { tn3270eRtCollCtlEntry 11 }
1775
1776 tn3270eRtCollCtlRowStatus OBJECT-TYPE
1777 SYNTAX RowStatus
1778 MAX-ACCESS read-create
1779 STATUS current
1780 DESCRIPTION
1781 "This object allows entries to be created and deleted
1782 in the tn3270eRtCollCtlTable. An entry in this table
1783 is deleted by setting this object to destroy(6).
1784 Deleting an entry in this table has the side-effect
1785
1786
1787
1788 <span class="grey">White &amp; Moore Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1791
1792
1793 of removing all entries from the tn3270eRtDataTable
1794 that are associated with the entry being deleted."
1795 ::= { tn3270eRtCollCtlEntry 12 }
1796
1797
1798 -- TN3270E Response Time Data Table
1799
1800 tn3270eRtDataTable OBJECT-TYPE
1801 SYNTAX SEQUENCE OF Tn3270eRtDataEntry
1802 MAX-ACCESS not-accessible
1803 STATUS current
1804 DESCRIPTION
1805 "The response time data table. Entries in this table are
1806 created based on entries in the tn3270eRtCollCtlTable."
1807 ::= { tn3270eRtObjects 2 }
1808
1809 tn3270eRtDataEntry OBJECT-TYPE
1810 SYNTAX Tn3270eRtDataEntry
1811 MAX-ACCESS not-accessible
1812 STATUS current
1813 DESCRIPTION
1814 "Entries in this table are created based upon the
1815 tn3270eRtCollCtlTable. When the corresponding
1816 tn3270eRtCollCtlType has aggregate(0) specified, a single
1817 entry is created in this table, with a tn3270eRtDataClientAddrType
1818 of unknown(0), a zero-length octet string value for
1819 tn3270eRtDataClientAddress, and a tn3270eRtDataClientPort value of
1820 0. When aggregate(0) is not specified, a separate entry is
1821 created for each client in the group.
1822
1823 Note that the following objects defined within an entry in this
1824 table can wrap:
1825 tn3270eRtDataTotalRts
1826 tn3270eRtDataTotalIpRts
1827 tn3270eRtDataCountTrans
1828 tn3270eRtDataCountDrs
1829 tn3270eRtDataElapsRnTrpSq
1830 tn3270eRtDataElapsIpRtSq
1831 tn3270eRtDataBucket1Rts
1832 tn3270eRtDataBucket2Rts
1833 tn3270eRtDataBucket3Rts
1834 tn3270eRtDataBucket4Rts
1835 tn3270eRtDataBucket5Rts"
1836 INDEX {
1837 tn3270eSrvrConfIndex, -- Server's local index
1838 tn3270eClientGroupName, -- Collection target
1839 tn3270eRtDataClientAddrType,
1840 tn3270eRtDataClientAddress,
1841
1842
1843
1844 <span class="grey">White &amp; Moore Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1847
1848
1849 tn3270eRtDataClientPort }
1850 ::= { tn3270eRtDataTable 1 }
1851
1852 Tn3270eRtDataEntry ::= SEQUENCE {
1853 tn3270eRtDataClientAddrType IANATn3270eAddrType,
1854 tn3270eRtDataClientAddress IANATn3270eAddress,
1855 tn3270eRtDataClientPort Unsigned32,
1856 tn3270eRtDataAvgRt Gauge32,
1857 tn3270eRtDataAvgIpRt Gauge32,
1858 tn3270eRtDataAvgCountTrans Gauge32,
1859 tn3270eRtDataIntTimeStamp DateAndTime,
1860 tn3270eRtDataTotalRts Counter32,
1861 tn3270eRtDataTotalIpRts Counter32,
1862 tn3270eRtDataCountTrans Counter32,
1863 tn3270eRtDataCountDrs Counter32,
1864 tn3270eRtDataElapsRndTrpSq Unsigned32,
1865 tn3270eRtDataElapsIpRtSq Unsigned32,
1866 tn3270eRtDataBucket1Rts Counter32,
1867 tn3270eRtDataBucket2Rts Counter32,
1868 tn3270eRtDataBucket3Rts Counter32,
1869 tn3270eRtDataBucket4Rts Counter32,
1870 tn3270eRtDataBucket5Rts Counter32,
1871 tn3270eRtDataRtMethod INTEGER,
1872 tn3270eRtDataDiscontinuityTime TimeStamp
1873 }
1874
1875 tn3270eRtDataClientAddrType OBJECT-TYPE
1876 SYNTAX IANATn3270eAddrType
1877 MAX-ACCESS not-accessible
1878 STATUS current
1879 DESCRIPTION
1880 "Indicates the type of address represented by the value
1881 of tn3270eRtDataClientAddress. The value unknown(0) is
1882 used if aggregate data is being collected for the client
1883 group."
1884 ::= { tn3270eRtDataEntry 1 }
1885
1886 tn3270eRtDataClientAddress OBJECT-TYPE
1887 SYNTAX IANATn3270eAddress
1888 MAX-ACCESS not-accessible
1889 STATUS current
1890 DESCRIPTION
1891 "Contains the IP address of the TN3270 client being
1892 monitored. A zero-length octet string is used if
1893 aggregate data is being collected for the client group."
1894 ::= { tn3270eRtDataEntry 2 }
1895
1896 tn3270eRtDataClientPort OBJECT-TYPE
1897
1898
1899
1900 <span class="grey">White &amp; Moore Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1903
1904
1905 SYNTAX Unsigned32(0..65535)
1906 MAX-ACCESS not-accessible
1907 STATUS current
1908 DESCRIPTION
1909 "Contains the client port number of the TN3270 client being
1910 monitored. The value 0 is used if aggregate data is being
1911 collected for the client group, or if the
1912 tn3270eRtDataClientAddrType identifies an address type that
1913 does not support ports."
1914 ::= { tn3270eRtDataEntry 3 }
1915
1916 tn3270eRtDataAvgRt OBJECT-TYPE
1917 SYNTAX Gauge32
1918 UNITS "tenths of seconds"
1919 MAX-ACCESS read-only
1920 STATUS current
1921 DESCRIPTION
1922 "The average total response time measured over the last
1923 collection interval."
1924 DEFVAL { 0 }
1925 ::= { tn3270eRtDataEntry 4 }
1926
1927 tn3270eRtDataAvgIpRt OBJECT-TYPE
1928 SYNTAX Gauge32
1929 UNITS "tenths of seconds"
1930 MAX-ACCESS read-only
1931 STATUS current
1932 DESCRIPTION
1933 "The average IP response time measured over the last
1934 collection interval."
1935 DEFVAL { 0 }
1936 ::= { tn3270eRtDataEntry 5 }
1937
1938 tn3270eRtDataAvgCountTrans OBJECT-TYPE
1939 SYNTAX Gauge32
1940 UNITS "transactions"
1941 MAX-ACCESS read-only
1942 STATUS current
1943 DESCRIPTION
1944 "The sliding transaction count used for calculating the
1945 values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt
1946 objects. The actual transaction count is available in
1947 the tn3270eRtDataCountTrans object.
1948
1949 The initial value of this object, before any averages have
1950 been calculated, is 0."
1951 ::= { tn3270eRtDataEntry 6 }
1952
1953
1954
1955
1956 <span class="grey">White &amp; Moore Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
1959
1960
1961 tn3270eRtDataIntTimeStamp OBJECT-TYPE
1962 SYNTAX DateAndTime
1963 MAX-ACCESS read-only
1964 STATUS current
1965 DESCRIPTION
1966 "The date and time of the last interval that
1967 tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and
1968 tn3270eRtDataAvgCountTrans were calculated.
1969
1970 Prior to the calculation of the first interval
1971 averages, this object returns the value
1972 0x0000000000000000000000. When this value is
1973 returned, the remaining objects in the entry have
1974 no significance."
1975 ::= { tn3270eRtDataEntry 7 }
1976
1977 tn3270eRtDataTotalRts OBJECT-TYPE
1978 SYNTAX Counter32
1979 UNITS "tenths of seconds"
1980 MAX-ACCESS read-only
1981 STATUS current
1982 DESCRIPTION
1983 "The count of the total response times collected.
1984
1985 A management application can detect discontinuities in this
1986 counter by monitoring the tn3270eRtDataDiscontinuityTime
1987 object."
1988 ::= { tn3270eRtDataEntry 8 }
1989
1990 tn3270eRtDataTotalIpRts OBJECT-TYPE
1991 SYNTAX Counter32
1992 UNITS "tenths of seconds"
1993 MAX-ACCESS read-only
1994 STATUS current
1995 DESCRIPTION
1996 "The count of the total IP-network response times
1997 collected.
1998
1999 A management application can detect discontinuities in this
2000 counter by monitoring the tn3270eRtDataDiscontinuityTime
2001 object."
2002 ::= { tn3270eRtDataEntry 9 }
2003
2004 tn3270eRtDataCountTrans OBJECT-TYPE
2005 SYNTAX Counter32
2006 UNITS "transactions"
2007 MAX-ACCESS read-only
2008 STATUS current
2009
2010
2011
2012 <span class="grey">White &amp; Moore Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2015
2016
2017 DESCRIPTION
2018 "The count of the total number of transactions detected.
2019
2020 A management application can detect discontinuities in this
2021 counter by monitoring the tn3270eRtDataDiscontinuityTime
2022 object."
2023 ::= { tn3270eRtDataEntry 10 }
2024
2025 tn3270eRtDataCountDrs OBJECT-TYPE
2026 SYNTAX Counter32
2027 UNITS "definite responses"
2028 MAX-ACCESS read-only
2029 STATUS current
2030 DESCRIPTION
2031 "The count of the total number of definite responses
2032 detected.
2033
2034 A management application can detect discontinuities in this
2035 counter by monitoring the tn3270eRtDataDiscontinuityTime
2036 object."
2037 ::= { tn3270eRtDataEntry 11 }
2038
2039 tn3270eRtDataElapsRndTrpSq OBJECT-TYPE
2040 SYNTAX Unsigned32
2041 UNITS "tenths of seconds squared"
2042 MAX-ACCESS read-only
2043 STATUS current
2044 DESCRIPTION
2045 "The sum of the elapsed round trip time squared. The sum
2046 of the squares is kept in order to enable calculation of
2047 a variance."
2048 DEFVAL { 0 }
2049 ::= { tn3270eRtDataEntry 12 }
2050
2051 tn3270eRtDataElapsIpRtSq OBJECT-TYPE
2052 SYNTAX Unsigned32
2053 UNITS "tenths of seconds squared"
2054 MAX-ACCESS read-only
2055 STATUS current
2056 DESCRIPTION
2057 "The sum of the elapsed IP round trip time squared.
2058 The sum of the squares is kept in order to enable
2059 calculation of a variance."
2060 DEFVAL { 0 }
2061 ::= { tn3270eRtDataEntry 13 }
2062
2063 tn3270eRtDataBucket1Rts OBJECT-TYPE
2064 SYNTAX Counter32
2065
2066
2067
2068 <span class="grey">White &amp; Moore Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2071
2072
2073 MAX-ACCESS read-only
2074 STATUS current
2075 DESCRIPTION
2076 "The count of the response times falling into bucket 1.
2077
2078 A management application can detect discontinuities in this
2079 counter by monitoring the tn3270eRtDataDiscontinuityTime
2080 object."
2081 ::= { tn3270eRtDataEntry 14 }
2082
2083 tn3270eRtDataBucket2Rts OBJECT-TYPE
2084 SYNTAX Counter32
2085 MAX-ACCESS read-only
2086 STATUS current
2087 DESCRIPTION
2088 "The count of the response times falling into bucket 2.
2089
2090 A management application can detect discontinuities in this
2091 counter by monitoring the tn3270eRtDataDiscontinuityTime
2092 object."
2093 ::= { tn3270eRtDataEntry 15 }
2094
2095 tn3270eRtDataBucket3Rts OBJECT-TYPE
2096 SYNTAX Counter32
2097 MAX-ACCESS read-only
2098 STATUS current
2099 DESCRIPTION
2100 "The count of the response times falling into bucket 3.
2101
2102 A management application can detect discontinuities in this
2103 counter by monitoring the tn3270eRtDataDiscontinuityTime
2104 object."
2105 ::= { tn3270eRtDataEntry 16 }
2106
2107 tn3270eRtDataBucket4Rts OBJECT-TYPE
2108 SYNTAX Counter32
2109 MAX-ACCESS read-only
2110 STATUS current
2111 DESCRIPTION
2112 "The count of the response times falling into bucket 4.
2113
2114 A management application can detect discontinuities in this
2115 counter by monitoring the tn3270eRtDataDiscontinuityTime
2116 object."
2117 ::= { tn3270eRtDataEntry 17 }
2118
2119 tn3270eRtDataBucket5Rts OBJECT-TYPE
2120 SYNTAX Counter32
2121
2122
2123
2124 <span class="grey">White &amp; Moore Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2127
2128
2129 MAX-ACCESS read-only
2130 STATUS current
2131 DESCRIPTION
2132 "The count of the response times falling into bucket 5.
2133
2134 A management application can detect discontinuities in this
2135 counter by monitoring the tn3270eRtDataDiscontinuityTime
2136 object."
2137 ::= { tn3270eRtDataEntry 18 }
2138
2139 tn3270eRtDataRtMethod OBJECT-TYPE
2140 SYNTAX INTEGER {
2141 none(0),
2142 responses(1),
2143 timingMark(2)
2144 }
2145 MAX-ACCESS read-only
2146 STATUS current
2147 DESCRIPTION
2148 "The value of this object indicates the method that was
2149 used in calculating the IP network time.
2150
2151 The value 'none(0) indicates that response times were not
2152 calculated for the IP network."
2153 ::= { tn3270eRtDataEntry 19 }
2154
2155 tn3270eRtDataDiscontinuityTime OBJECT-TYPE
2156 SYNTAX TimeStamp
2157 MAX-ACCESS read-only
2158 STATUS current
2159 DESCRIPTION
2160 "The value of sysUpTime on the most recent occasion at
2161 which one or more of this entry's counter objects
2162 suffered a discontinuity. This may happen if a TN3270E
2163 server is stopped and then restarted, and local methods
2164 are used to set up collection policy
2165 (tn3270eRtCollCtlTable entries)."
2166 ::= { tn3270eRtDataEntry 20 }
2167
2168
2169 tn3270eRtSpinLock OBJECT-TYPE
2170 SYNTAX TestAndIncr
2171 MAX-ACCESS read-write
2172 STATUS current
2173 DESCRIPTION
2174 "An advisory lock used to allow cooperating TN3270E-RT-MIB
2175 applications to coordinate their use of the
2176 tn3270eRtCollCtlTable.
2177
2178
2179
2180 <span class="grey">White &amp; Moore Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2183
2184
2185 When creating a new entry or altering an existing entry
2186 in the tn3270eRtCollCtlTable, an application should make
2187 use of tn3270eRtSpinLock to serialize application changes
2188 or additions.
2189
2190 Since this is an advisory lock, the use of this lock is
2191 not enforced."
2192 ::= { tn3270eRtObjects 3 }
2193
2194 -- Notifications
2195
2196 tn3270eRtExceeded NOTIFICATION-TYPE
2197 OBJECTS {
2198 tn3270eRtDataIntTimeStamp,
2199 tn3270eRtDataAvgRt,
2200 tn3270eRtDataAvgIpRt,
2201 tn3270eRtDataAvgCountTrans,
2202 tn3270eRtDataRtMethod
2203 }
2204 STATUS current
2205 DESCRIPTION
2206 "This notification is generated when the average response
2207 time, tn3270eRtDataAvgRt, exceeds
2208 tn3270eRtCollCtlThresholdHigh at the end of a collection
2209 interval specified by tn3270eCollCtlSPeriod
2210 times tn3270eCollCtlSPMult. Note that the corresponding
2211 tn3270eCollCtlType must have traps(5) and average(3) set
2212 for this notification to be generated. In addition,
2213 tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and
2214 tn3270eRtDataAvgRt are algorithmically compared to
2215 tn3270eRtCollCtlIdleCount for determination if this
2216 notification will be suppressed."
2217 ::= { tn3270eRtNotifications 1 }
2218
2219 tn3270eRtOkay NOTIFICATION-TYPE
2220 OBJECTS {
2221 tn3270eRtDataIntTimeStamp,
2222 tn3270eRtDataAvgRt,
2223 tn3270eRtDataAvgIpRt,
2224 tn3270eRtDataAvgCountTrans,
2225 tn3270eRtDataRtMethod
2226 }
2227 STATUS current
2228 DESCRIPTION
2229 "This notification is generated when the average response
2230 time, tn3270eRtDataAvgRt, falls below
2231 tn3270eRtCollCtlThresholdLow at the end of a collection
2232 interval specified by tn3270eCollCtlSPeriod times
2233
2234
2235
2236 <span class="grey">White &amp; Moore Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2239
2240
2241 tn3270eCollCtlSPMult, after a tn3270eRtExceeded
2242 notification was generated. Note that the corresponding
2243 tn3270eCollCtlType must have traps(5) and average(3)
2244 set for this notification to be generated."
2245 ::= { tn3270eRtNotifications 2 }
2246
2247 tn3270eRtCollStart NOTIFICATION-TYPE
2248 OBJECTS {
2249 tn3270eRtDataRtMethod, -- type of collection
2250 tn3270eResMapElementType -- type of resource
2251 }
2252 STATUS current
2253 DESCRIPTION
2254 "This notification is generated when response time data
2255 collection is enabled for a member of a client group.
2256 In order for this notification to occur the corresponding
2257 tn3270eRtCollCtlType must have traps(5) selected.
2258
2259 tn3270eResMapElementType contains a valid value only if
2260 tn3270eRtDataClientAddress contains a valid address
2261 (rather than a zero-length octet string)."
2262 ::= { tn3270eRtNotifications 3 }
2263
2264 tn3270eRtCollEnd NOTIFICATION-TYPE
2265 OBJECTS {
2266 tn3270eRtDataDiscontinuityTime,
2267 tn3270eRtDataAvgRt,
2268 tn3270eRtDataAvgIpRt,
2269 tn3270eRtDataAvgCountTrans,
2270 tn3270eRtDataIntTimeStamp,
2271 tn3270eRtDataTotalRts,
2272 tn3270eRtDataTotalIpRts,
2273 tn3270eRtDataCountTrans,
2274 tn3270eRtDataCountDrs,
2275 tn3270eRtDataElapsRndTrpSq,
2276 tn3270eRtDataElapsIpRtSq,
2277 tn3270eRtDataBucket1Rts,
2278 tn3270eRtDataBucket2Rts,
2279 tn3270eRtDataBucket3Rts,
2280 tn3270eRtDataBucket4Rts,
2281 tn3270eRtDataBucket5Rts,
2282 tn3270eRtDataRtMethod
2283 }
2284 STATUS current
2285 DESCRIPTION
2286 "This notification is generated when an tn3270eRtDataEntry
2287 is deleted after being active (actual data collected), in
2288 order to enable a management application monitoring an
2289
2290
2291
2292 <span class="grey">White &amp; Moore Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2295
2296
2297 tn3270eRtDataEntry to get the entry's final values. Note
2298 that the corresponding tn3270eCollCtlType must have traps(5)
2299 set for this notification to be generated."
2300 ::= { tn3270eRtNotifications 4 }
2301
2302 -- Conformance Statement
2303
2304 tn3270eRtGroups OBJECT IDENTIFIER ::= { tn3270eRtConformance 1 }
2305 tn3270eRtCompliances OBJECT IDENTIFIER ::= { tn3270eRtConformance 2 }
2306
2307 -- Compliance statements
2308
2309 tn3270eRtCompliance MODULE-COMPLIANCE
2310 STATUS current
2311 DESCRIPTION
2312 "The compliance statement for agents that support the
2313 TN327E-RT-MIB."
2314 MODULE -- this module
2315 MANDATORY-GROUPS { tn3270eRtGroup, tn3270eRtNotGroup }
2316
2317 OBJECT tn3270eRtCollCtlType
2318 MIN-ACCESS read-only
2319 DESCRIPTION
2320 "The agent is not required to support a SET operation to
2321 this object in the absence of adequate security."
2322
2323 OBJECT tn3270eRtCollCtlSPeriod
2324 MIN-ACCESS read-only
2325 DESCRIPTION
2326 "The agent is not required to allow the user to change
2327 the default value of this object, and is allowed to
2328 use a different default."
2329
2330 OBJECT tn3270eRtCollCtlSPMult
2331 MIN-ACCESS read-only
2332 DESCRIPTION
2333 "The agent is not required to support a SET operation
2334 to this object in the absence of adequate security."
2335
2336 OBJECT tn3270eRtCollCtlThreshHigh
2337 MIN-ACCESS read-only
2338 DESCRIPTION
2339 "The agent is not required to support a SET operation
2340 to this object in the absence of adequate security."
2341
2342 OBJECT tn3270eRtCollCtlThreshLow
2343 MIN-ACCESS read-only
2344 DESCRIPTION
2345
2346
2347
2348 <span class="grey">White &amp; Moore Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2351
2352
2353 "The agent is not required to support a SET operation
2354 to this object in the absence of adequate security."
2355
2356 OBJECT tn3270eRtCollCtlIdleCount
2357 MIN-ACCESS read-only
2358 DESCRIPTION
2359 "The agent is not required to support a SET operation
2360 to this object in the absence of adequate security."
2361
2362 OBJECT tn3270eRtCollCtlBucketBndry1
2363 MIN-ACCESS read-only
2364 DESCRIPTION
2365 "The agent is not required to support a SET operation
2366 to this object in the absence of adequate security."
2367
2368 OBJECT tn3270eRtCollCtlBucketBndry2
2369 MIN-ACCESS read-only
2370 DESCRIPTION
2371 "The agent is not required to support a SET operation
2372 to this object in the absence of adequate security."
2373
2374 OBJECT tn3270eRtCollCtlBucketBndry3
2375 MIN-ACCESS read-only
2376 DESCRIPTION
2377 "The agent is not required to support a SET operation
2378 to this object in the absence of adequate security."
2379
2380 OBJECT tn3270eRtCollCtlBucketBndry4
2381 MIN-ACCESS read-only
2382 DESCRIPTION
2383 "The agent is not required to support a SET operation
2384 to this object in the absence of adequate security."
2385
2386 OBJECT tn3270eRtCollCtlRowStatus
2387 SYNTAX INTEGER {
2388 active(1) -- subset of RowStatus
2389 }
2390 MIN-ACCESS read-only
2391 DESCRIPTION
2392 "Write access is not required, and only one of the six
2393 enumerated values for the RowStatus textual convention
2394 need be supported, specifically: active(1)."
2395
2396 ::= {tn3270eRtCompliances 1 }
2397
2398 -- Group definitions
2399
2400 tn3270eRtGroup OBJECT-GROUP
2401
2402
2403
2404 <span class="grey">White &amp; Moore Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2407
2408
2409 OBJECTS {
2410 tn3270eRtCollCtlType,
2411 tn3270eRtCollCtlSPeriod,
2412 tn3270eRtCollCtlSPMult,
2413 tn3270eRtCollCtlThreshHigh,
2414 tn3270eRtCollCtlThreshLow,
2415 tn3270eRtCollCtlIdleCount,
2416 tn3270eRtCollCtlBucketBndry1,
2417 tn3270eRtCollCtlBucketBndry2,
2418 tn3270eRtCollCtlBucketBndry3,
2419 tn3270eRtCollCtlBucketBndry4,
2420 tn3270eRtCollCtlRowStatus,
2421 tn3270eRtDataDiscontinuityTime,
2422 tn3270eRtDataAvgRt,
2423 tn3270eRtDataAvgIpRt,
2424 tn3270eRtDataAvgCountTrans,
2425 tn3270eRtDataIntTimeStamp,
2426 tn3270eRtDataTotalRts,
2427 tn3270eRtDataTotalIpRts,
2428 tn3270eRtDataCountTrans,
2429 tn3270eRtDataCountDrs,
2430 tn3270eRtDataElapsRndTrpSq,
2431 tn3270eRtDataElapsIpRtSq,
2432 tn3270eRtDataBucket1Rts,
2433 tn3270eRtDataBucket2Rts,
2434 tn3270eRtDataBucket3Rts,
2435 tn3270eRtDataBucket4Rts,
2436 tn3270eRtDataBucket5Rts,
2437 tn3270eRtDataRtMethod,
2438 tn3270eRtSpinLock }
2439 STATUS current
2440 DESCRIPTION
2441 "This group is mandatory for all implementations that
2442 support the TN3270E-RT-MIB. "
2443 ::= { tn3270eRtGroups 1 }
2444
2445 tn3270eRtNotGroup NOTIFICATION-GROUP
2446 NOTIFICATIONS {
2447 tn3270eRtExceeded,
2448 tn3270eRtOkay,
2449 tn3270eRtCollStart,
2450 tn3270eRtCollEnd
2451 }
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">White &amp; Moore Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2463
2464
2465 STATUS current
2466 DESCRIPTION
2467 "The notifications that must be supported when the
2468 TN3270E-RT-MIB is implemented. "
2469 ::= { tn3270eRtGroups 2 }
2470
2471 END
2472
2473
2474 <span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> Security Considerations</span>
2475
2476 Certain management information defined in this MIB may be considered
2477 sensitive in some network environments. Therefore, authentication of
2478 received SNMP requests and controlled access to management
2479 information SHOULD be employed in such environments. An
2480 authentication protocol is defined in [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>]. A protocol for access
2481 control is defined in [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>].
2482
2483 Several objects in this MIB allow write access or provide for row
2484 creation. Allowing this support in a non-secure environment can have
2485 a negative effect on network operations. It is RECOMMENDED that
2486 implementers seriously consider whether set operations or row
2487 creation SHOULD be allowed without providing, at a minimum,
2488 authentication of request origin. It is RECOMMENDED that without
2489 such support that the following objects be implemented as read-only:
2490
2491 o tn3270eRtCollCtlType
2492 o tn3270eRtCollCtlSPeriod
2493 o tn3270eRtCollCtlSPMult
2494 o tn3270eRtCollCtlThreshHigh
2495 o tn3270eRtCollCtlThreshLow
2496 o tn3270eRtCollCtlIdleCount
2497 o tn3270eRtCollCtlBucketBndry1
2498 o tn3270eRtCollCtlBucketBndry2
2499 o tn3270eRtCollCtlBucketBndry3
2500 o tn3270eRtCollCtlBucketBndry4
2501 o tn3270eRtCollCtlRowStatus
2502
2503 The administrative method to use to create and manage the
2504 tn3270eRtCollCtlTable when SET support is not allowed is outside of
2505 the scope of this memo.
2506
2507 <span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> Intellectual Property</span>
2508
2509 The IETF takes no position regarding the validity or scope of any
2510 intellectual property or other rights that might be claimed to
2511 pertain to the implementation or use of the technology described in
2512 this document or the extent to which any license under such rights
2513
2514
2515
2516 <span class="grey">White &amp; Moore Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2519
2520
2521 might or might not be available; neither does it represent that it
2522 has made any effort to identify any such rights. Information on the
2523 IETF's procedures with respect to rights in standards-track and
2524 standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
2525 claims of rights made available for publication and any assurances of
2526 licenses to be made available, or the result of an attempt made to
2527 obtain a general license or permission for the use of such
2528 proprietary rights by implementers or users of this specification can
2529 be obtained from the IETF Secretariat.
2530
2531 The IETF invites any interested party to bring to its attention any
2532 copyrights, patents or patent applications, or other proprietary
2533 rights which may cover technology that may be required to practice
2534 this standard. Please address the information to the IETF Executive
2535 Director.
2536
2537 <span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> Acknowledgments</span>
2538
2539 This document is a product of the TN3270E Working Group. Special
2540 thanks are due to Derek Bolton and Michael Boe of Cisco Systems for
2541 their numerous comments and suggestions for improving the structure
2542 of this MIB. Thanks also to Randy Presuhn of BMC Software for his
2543 valuable review comments on several versions of the document.
2544
2545 <span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> References</span>
2546
2547 [<a id="ref-1">1</a>] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for
2548 Describing SNMP Management Frameworks", <a href="./rfc2271">RFC 2271</a>, January 1998.
2549
2550 [<a id="ref-2">2</a>] Rose, M. and K. McCloghrie, "Structure and Identification of
2551 Management Information for TCP/IP-based Internets", STD 16, <a href="./rfc1155">RFC</a>
2552 <a href="./rfc1155">1155</a>, May 1990.
2553
2554 [<a id="ref-3">3</a>] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
2555 <a href="./rfc1212">RFC 1212</a>, March 1991.
2556
2557 [<a id="ref-4">4</a>] Rose, M., "A Convention for Defining Traps for use with the
2558 SNMP", <a href="./rfc1215">RFC 1215</a>, March 1991.
2559
2560 [<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure
2561 of Management Information for Version 2 of the Simple Network
2562 Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>, January 1996.
2563
2564 [<a id="ref-6">6</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
2565 Conventions for Version 2 of the Simple Network Management
2566 Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
2567
2568
2569
2570
2571
2572 <span class="grey">White &amp; Moore Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2575
2576
2577 [<a id="ref-7">7</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2578 "Conformance Statements for Version 2 of the Simple Network
2579 Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January 1996.
2580
2581 [<a id="ref-8">8</a>] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
2582 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990.
2583
2584 [<a id="ref-9">9</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2585 "Introduction to Community-based SNMPv2", <a href="./rfc1901">RFC 1901</a>, January
2586 1996.
2587
2588 [<a id="ref-10">10</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
2589 Mappings for Version 2 of the Simple Network Management Protocol
2590 (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
2591
2592 [<a id="ref-11">11</a>] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
2593 Processing and Dispatching for the Simple Network Management
2594 Protocol (SNMP)", <a href="./rfc2272">RFC 2272</a>, January 1998.
2595
2596 [<a id="ref-12">12</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
2597 for version 3 of the Simple Network Management Protocol
2598 (SNMPv3)", <a href="./rfc2274">RFC 2274</a>, January 1998.
2599
2600 [<a id="ref-13">13</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
2601 Operations for Version 2 of the Simple Network Management
2602 Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
2603
2604 [<a id="ref-14">14</a>] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", <a href="./rfc2273">RFC</a>
2605 <a href="./rfc2273">2273</a>, January 1998.
2606
2607 [<a id="ref-15">15</a>] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
2608 Control Model (VACM) for the Simple Network Management Protocol
2609 (SNMP)", <a href="./rfc2275">RFC 2275</a>, January 1998.
2610
2611 [<a id="ref-16">16</a>] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
2612 8, <a href="./rfc854">RFC 854</a>, May 1983.
2613
2614 [<a id="ref-17">17</a>] Postel, J. and J. Reynolds, "Telnet Timing Mark Option", STD 31,
2615 <a href="./rfc860">RFC 860</a>, May 1983.
2616
2617 [<a id="ref-18">18</a>] Rekhter, J., "Telnet 3270 Regime Option", <a href="./rfc1041">RFC 1041</a>, January
2618 1988.
2619
2620 [<a id="ref-19">19</a>] Kelly, B., "TN3270 Enhancements", <a href="./rfc2355">RFC 2355</a>, June 1998.
2621
2622 [<a id="ref-20">20</a>] White, K. and R. Moore, "Base Definitions of Managed Objects for
2623 TN3270E Using SMIv2", <a href="./rfc2561">RFC 2561</a>, April 1999.
2624
2625
2626
2627
2628 <span class="grey">White &amp; Moore Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2631
2632
2633 [<a id="ref-21">21</a>] IBM, International Technical Support Centers, "Response Time
2634 Data Gathering", GG24-3212-01, November 1990.
2635
2636 [<a id="ref-22">22</a>] Hovey, R. and S. Bradner, "The Organizations Involved in the
2637 IETF Standards Process", <a href="https://www.rfc-editor.org/bcp/bcp11">BCP 11</a>, <a href="./rfc2028">RFC 2028</a>, October 1996.
2638
2639 [<a id="ref-23">23</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
2640 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
2641
2642 <span class="h3"><a class="selflink" id="section-10.0" href="#section-10.0">10.0</a> Authors' Addresses</span>
2643
2644 Kenneth D. White
2645 Dept. BRQA/Bldg. 501/G114
2646 IBM Corporation
2647 P.O.Box 12195
2648 3039 Cornwallis
2649 Research Triangle Park, NC 27709, USA
2650
2651 EMail: [email protected]
2652
2653
2654 Robert Moore
2655 Dept. BRQA/Bldg. 501/G114
2656 IBM Corporation
2657 P.O.Box 12195
2658 3039 Cornwallis
2659 Research Triangle Park, NC 27709, USA
2660
2661 Phone: +1-919-254-7507
2662 EMail: [email protected]
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684 <span class="grey">White &amp; Moore Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc2562">RFC 2562</a> TN3270E-RT-MIB April 1999</span>
2687
2688
2689 <span class="h3"><a class="selflink" id="section-11.0" href="#section-11.0">11.0</a> Full Copyright Statement</span>
2690
2691 Copyright (C) The Internet Society (1999). All Rights Reserved.
2692
2693 This document and translations of it may be copied and furnished to
2694 others, and derivative works that comment on or otherwise explain it
2695 or assist in its implementation may be prepared, copied, published
2696 and distributed, in whole or in part, without restriction of any
2697 kind, provided that the above copyright notice and this paragraph are
2698 included on all such copies and derivative works. However, this
2699 document itself may not be modified in any way, such as by removing
2700 the copyright notice or references to the Internet Society or other
2701 Internet organizations, except as needed for the purpose of
2702 developing Internet standards in which case the procedures for
2703 copyrights defined in the Internet Standards process must be
2704 followed, or as required to translate it into languages other than
2705 English.
2706
2707 The limited permissions granted above are perpetual and will not be
2708 revoked by the Internet Society or its successors or assigns.
2709
2710 This document and the information contained herein is provided on an
2711 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2712 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2713 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2714 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2715 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740 White &amp; Moore Standards Track [Page 49]
2741 </pre>