¬†¬†¬† If a TN3270E server is performing the TIMING-MARK function
¬†¬†¬† (independent of the response time monitoring use of the function
¬†¬†¬† discussed here), then it most likely has a TIMING-MARK interval for
¬†¬†¬† determining when to examine client sessions for sending the TIMING-
¬†¬†¬† MARK request. This interval, which is ordinarily a global value for
¬†¬†¬† an entire TN3270E server, is represented in the TN3270E-MIB by the
¬†¬†¬† tn3270eSrvrConfTmNopInterval object. A TIMING-MARK request is sent
¬†¬†¬† only if, when it is examined, a client session is found to have had
¬†¬†¬† no activity for a different fixed length of time, represented in the
¬†¬†¬† TN3270E-MIB by the tn3270eSrvrConfTmNopInactTime object.

¬†¬†¬† Servers that support a large number of client sessions should spread
¬†¬†¬† out the TIMING-MARK requests they send to these clients over the
¬†¬†¬† activity interval, rather than sending them all in a single burst,
¬†¬†¬† since otherwise the network may be flooded with TIMING-MARK requests.
¬†¬†¬† When a server uses TIMING-MARKs for approximating response times,

White & Moore Standards Track [Page 14]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† this tends to introduce a natural spreading into its TIMING-MARK
¬†¬†¬† requests, since the requests are triggered by the arrival of traffic
¬†¬†¬† from an SNA host.

¬†¬†¬† A TN3270E server MUST integrate its normal TIMING-MARK processing
¬†¬†¬† with its use of TIMING-MARKs for computing response times. In
¬†¬†¬† particular, it MUST NOT send a second TIMING-MARK request to a client
¬†¬†¬† while waiting for the first to return, since this is ruled out by the
¬†¬†¬† TIMING-MARK protocol itself. If a TIMING-MARK flow has just been
¬†¬†¬† performed for a client shortly before the LIC RU arrives, the server
¬†¬†¬† MAY use the interval from this flow as its approximation for IP
¬†¬†¬† network transit time, (in other words, as its (F' - E') value) when
¬†¬†¬† calculating its approximation for the transaction's total response
¬†¬†¬† time, rather than sending a second TIMING-MARK request so soon after
¬†¬†¬† the preceding one.

¬†¬†¬† Regardless of when the server sends its TIMING-MARK request, the
¬†¬†¬† accuracy of its total response time calculation depends on exactly
¬†¬†¬† when the client responds to the TIMING-MARK request.

3.5 Performance Data Modelling

¬†¬†¬† The following two subsections detail how the TN3270E-RT-MIB models
¬†¬†¬† and controls capture of two types of response time data: average
¬†¬†¬† response times and response time buckets.

3.5.1 Averaging Response Times

¬†¬†¬† Average response times play two different roles in the MIB:

¬†¬†¬† o They are made available for management applications to retrieve.
¬†¬†¬† o They serve as triggers for emitting notifications.

¬†¬†¬† Sliding-window averages are used rather than straight interval-based
¬†¬†¬† averages, because they are often more meaningful, and because they
¬†¬†¬† cause less notification thrashing. Sliding-window average
¬†¬†¬† calculation can, if necessary, be disabled, by setting the sample
¬†¬†¬† period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the
¬†¬†¬† sample period, tn3270eRtCollCtlSPeriod, to the required collection
¬†¬†¬† interval.

¬†¬†¬† In order to calculate sliding-window averages, a TN3270E server MUST:

¬†¬†¬† o Select a fixed, relatively short, sample period SPeriod; the
¬†¬†¬†¬†¬†¬†¬† default value for SPeriod in the MIB is 20 seconds.
White & Moore Standards Track [Page 15]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† o Select an averaging period multiplier SPMult. The actual
¬†¬†¬†¬†¬†¬†¬† collection interval will then be SPMult times SPeriod. The
¬†¬†¬†¬†¬†¬†¬† default value for SPMult in the MIB is 30, yielding a default
¬†¬†¬†¬†¬†¬†¬† collection interval of 10 minutes. Note that the collection
¬†¬†¬†¬†¬†¬†¬† interval (SPMult*SPeriod) is always a multiple of the sample
¬†¬†¬†¬†¬†¬†¬† period.

¬†¬†¬†¬†¬†¬†¬† Clearlly, SPMult*SPeriod should not be thought of as literally
¬†¬†¬†¬†¬†¬†¬† the averaging period. The average calculated will include
¬†¬†¬†¬†¬†¬†¬† contributions older than that time, and does not weight equally
¬†¬†¬†¬†¬†¬†¬† all contributions since that time. In fact, it gives a smoother
¬†¬†¬†¬†¬†¬†¬† result than a traditional sliding average, as used in finance.
¬†¬†¬†¬†¬†¬†¬† More subtly, it is best to think of the effective averaging
¬†¬†¬†¬†¬†¬†¬† period as being 2*SPMult*SPeriod. To see this, consider how long
¬†¬†¬†¬†¬†¬†¬† the contribution to the result made by a particular transaction
¬†¬†¬†¬†¬†¬†¬† lasts. With a traditional sliding average, it lasts exactly the
¬†¬†¬†¬†¬†¬†¬† averaging period. With the aging mechanism described here, it
¬†¬†¬†¬†¬†¬†¬† has a half-life of SPMult*SPeriod.

¬†¬†¬† o Maintain the following counters to keep track of activity within
¬†¬†¬†¬†¬†¬†¬† the current sample period; these are internal counters, not made
¬†¬†¬†¬†¬†¬†¬† visible to a management application via the MIB.

¬†¬†¬†¬†¬†¬†¬† - T (number of transactions in the period)

¬†¬†¬†¬†¬†¬†¬† - TotalRts (sum of the total response times for all
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† transactions in the period)

¬†¬†¬†¬†¬†¬†¬† - TotalIpRts (sum of the IP network transit times for all
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† transactions in the period; note that if IP network transit
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† times are being excluded from the response time collection,
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† this value will always be 0).

¬†¬†¬† o Also maintain sliding counters, initialized to zero, for each of
¬†¬†¬†¬†¬†¬†¬† the quantities being counted:

¬†¬†¬†¬†¬†¬†¬† As expected, if IP network transit times are being excluded from
¬†¬†¬†¬†¬†¬†¬† response time collection, then tn3270eRtDataAvgIpRt will always
¬†¬†¬†¬†¬†¬†¬† return 0.

¬†¬†¬† The sliding transaction counter AvgCountTrans is not used for
¬†¬†¬† updating the MIB object tn3270eRtDataCountTrans: this object is an
¬†¬†¬† ordinary SMI Counter32, which maintains a total count of transactions
¬†¬†¬† since its last discontinuity event. The sliding counters are used
¬†¬†¬† only for calculating averages.

¬†¬†¬† Two mechanisms are present in the MIB to inhibit the generation of an
¬†¬†¬† excessive number of notifications related to average response times.
¬†¬†¬† First, there are high and low thresholds for average response times.
¬†¬†¬† A tn3270eRtExceeded notification is generated the first time a
¬†¬†¬† statistically significant average response time is found to have
¬†¬†¬† exceeded the high threshold. (The test for statistical significance
¬†¬†¬† is described below.) After this, no other tn3270eRtExceeded
¬†¬†¬† notifications are generated until an average response time is found
¬†¬†¬† to have fallen below the low threshold.

¬†¬†¬† The other mechanism to limit notifications is the significance test
¬†¬†¬† for a high average response time. Intuitively, the significance of
¬†¬†¬† an average is directly related to the number of samples that go into
¬†¬†¬† it; so we might be inclined to use a rule such as "for the purpose of
¬†¬†¬† generating tn3270eRtExceeded notifications, ignore average response
¬†¬†¬† times based on fewer than 20 transactions in the sample period."

¬†¬†¬† In the case of response times, however, the number of transactions
¬†¬†¬† sampled in a fixed sampling period is tied to these transactions'
¬†¬†¬† response times. A few transactions with long response times can
¬†¬†¬† guarantee that there will not be many transactions in a sample,
¬†¬†¬† because these transactions "use up" the sampling time. Yet this case

White & Moore Standards Track [Page 17]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† of a few transactions with very poor response times should obviously
¬†¬†¬† be classified as a problem, not as a statistical anomaly based on too
¬†¬†¬† small a sample.

¬†¬†¬† The solution is to make the significance level for a sample a
¬†¬†¬† function of the average response time. A value IdleCount is
¬†¬†¬† specified, which is used to qualify an sample as statistically
¬†¬†¬† significant. In order to determine at a collection interval whether
¬†¬†¬† to generate a tn3270eRtExceeded notification, a TN3270E server uses
¬†¬†¬† the following algorithm:

¬†¬†¬† where AvgRt is the value that would be returned by the object
¬†¬†¬† tn3270eRtDataAvgRt at the end of the interval, and the "**" notation
¬†¬†¬† indicates exponientiation.

¬†¬†¬† Two examples illustrate how this algorithm works. Suppose that
¬†¬†¬† IdleCount has been set to 20 transactions, and the high threshold to
¬†¬†¬† 200 msecs per transaction. If the average observed response time is
¬†¬†¬† 300 msecs, then a notification will be generated only if
¬†¬†¬† AvgCountTrans >= 80. If, however, the observed response time is 500
¬†¬†¬† msecs, then a notification is generated if AvgCountTrans >= 9.

¬†¬†¬† There is no corresponding significance test for the tn3270eRtOkay
¬†¬†¬† notification: this notification is generated based on an average
¬†¬†¬† response time that falls below the low threshold, regardless of the
¬†¬†¬† sample size behind that average.

3.5.2 Response Time Buckets

¬†¬†¬† The MIB also supports collection of response time data into a set of
¬†¬†¬† five buckets. This data is suitable either for verification of
¬†¬†¬† service level agreements, or for monitoring by a management
¬†¬†¬† application to identify performance problems. The buckets provide
¬†¬†¬† counts of transactions whose total response times fall into a set of
¬†¬†¬† specified ranges.

¬†¬†¬† Like everything for a collection, the "total" response times
¬†¬†¬† collected in the buckets are governed by the specification of whether
¬†¬†¬† IP network transit times are to be included in the totals. Depending
¬†¬†¬† on how this option is specified, the response times being counted in
¬†¬†¬† the buckets will either be total response times (F - D), or only SNA
¬†¬†¬† network transit times (effectively E - D, because when it is
¬†¬†¬† excluding the IP-network component of transactions, a server makes
¬†¬†¬† timestamp F identical to timestamp E).
White & Moore Standards Track [Page 18]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† Four bucket boundaries are specified for a response time collection,
¬†¬†¬† resulting in five buckets. The first response time bucket counts
¬†¬†¬† those transactions whose total response times were less than or equal
¬†¬†¬† to Boundary 1, the second bucket counts those whose response times
¬†¬†¬† were greater than Boundary 1 but less than or equal to Boundary 2,
¬†¬†¬† and so on. The fifth bucket is unbounded on the top, counting all
¬†¬†¬† transactions whose response times were greater than Boundary 4.

¬†¬†¬† The four bucket boundaries have default values of: 1 second, 2
¬†¬†¬† seconds, 5 seconds, and 10 seconds, respectively. These values are
¬†¬†¬† the defaults in the 3174 controller's implementation of the SNA/MS
¬†¬†¬† RTM function, and are thought to be appropriate for this MIB as well.

¬†¬†¬† In SNA/MS the counter buckets were (by today's standards) relatively
¬†¬†¬† small, with a maximum value of 65,535. The bucket objects in the MIB
¬†¬†¬† are all Counter32's.

¬†¬†¬† The tn3270eRtCollCtlTable is indexed by tn3270eSrvrConfIndex and
¬†¬†¬† tn3270eClientGroupName imported from the TN3270E-MIB.
¬†¬†¬† tn3270eSrvrConfIndex identifies within a host a particular TN3270E

White & Moore Standards Track [Page 19]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† server. tn3270eClientGroupName identifies a collection of IP clients
¬†¬†¬† for which response time data is to be collected. The set of clients
¬†¬†¬† is defined using the tn3270eClientGroupTable from the TN3270E-MIB.

¬†¬†¬† The tn3270eRtCollCtlType object controls the type(s) of response time
¬†¬†¬† collection that occur, the granularity of the collection, whether
¬†¬†¬† dynamic definite responses SHOULD be initiated, and whether
¬†¬†¬† notifications SHOULD be generated. This object is of BITS SYNTAX,
¬†¬†¬† and thus allows selection of multiple options.

¬†¬†¬† The BITS in the tn3270eRtCollCtlType object have the following
¬†¬†¬† meanings:

¬†¬†¬† o aggregate(0) - If this bit is set to 1, then data SHOULD be
¬†¬†¬†¬†¬†¬†¬† aggregated for the whole client group. In this case there will
¬†¬†¬†¬†¬†¬†¬† be only one row created for the collection in the
¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataTable. The first two indexes for this row,
¬†¬†¬†¬†¬†¬†¬† tn3270eSrvrConfIndex and tn3270eClientGroupName, will have the
¬†¬†¬†¬†¬†¬†¬† same values as the indexes for the corresponding
¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlEntry. The third and fourth indexes of an
¬†¬†¬†¬†¬†¬†¬† aggregated tn3270eRtDataEntry have the values unknown(0)
¬†¬†¬†¬†¬†¬†¬† (tn3270eRtDataClientAddrType) and a zero-length octet string
¬†¬†¬†¬†¬†¬†¬† (tn3270eRtDataClientAddress). The fifth index,
¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataClientPort, has the value 0.

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 0, then a separate entry is created in the
¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataTable from each member of the client group. In this
¬†¬†¬†¬†¬†¬†¬† case tn3270eRtDataClientAddress contains the client's actual IP

White & Moore Standards Track [Page 20]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬†¬†¬†¬†¬† Address, tn3270eRtDataClientAddrType indicates the address type,
¬†¬†¬†¬†¬†¬†¬† and tn3270eRtDataClientPort contains the number of the port the
¬†¬†¬†¬†¬†¬†¬† client is using for its TN3270/TN3270E session.

¬†¬†¬† o excludeIpComponent(1) - If this bit is set to 1, then the server
¬†¬†¬†¬†¬†¬†¬† SHOULD exclude the IP-network component from all the response
¬†¬†¬†¬†¬†¬†¬† times for this collection. If the target SNA application
¬†¬†¬†¬†¬†¬†¬† specifies DR in any of its replies, this DR will still be passed
¬†¬†¬†¬†¬†¬†¬† down to the client, and the client's response will still be
¬†¬†¬†¬†¬†¬†¬† forwarded to the application. But this response will play no
¬†¬†¬†¬†¬†¬†¬† role in the server's response time calculations.

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 0, then the server includes in the
¬†¬†¬†¬†¬†¬†¬† collection only those transactions for which it can include an
¬†¬†¬†¬†¬†¬†¬† (approximate) IP-network component in the total response time for
¬†¬†¬†¬†¬†¬†¬† the transaction. This component MAY be derived from a "natural"
¬†¬†¬†¬†¬†¬†¬† DR (if the client supports the RESPONSES function), from a
¬†¬†¬†¬†¬†¬†¬† dynamic DR introduced by the server (if the client supports the
¬†¬†¬†¬†¬†¬†¬† RESPONSES function and the ddr(2) bit has been set to 1), or from
¬†¬†¬†¬†¬†¬†¬† TIMING-MARK processing (if the client supports TIMING-MARKs).

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 1, then the ddr(2) bit is ignored, since
¬†¬†¬†¬†¬†¬†¬† there is no reason for the server to request additional responses
¬†¬†¬†¬†¬†¬†¬† from the client(s) in the group.

¬†¬†¬† o ddr(2) - If this bit is set to 1, then the server SHOULD, for
¬†¬†¬†¬†¬†¬†¬† those clients in the group that support the RESPONSES function,
¬†¬†¬†¬†¬†¬†¬† add a DR request to the FIC reply in each transaction, and use
¬†¬†¬†¬†¬†¬†¬† the client's subsequent response for calculating an (approximate)
¬†¬†¬†¬†¬†¬†¬† IP-network component to include in the transaction's total
¬†¬†¬†¬†¬†¬†¬† response times.

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 0, then the server does not add a DR
¬†¬†¬†¬†¬†¬†¬† request that it was not otherwise going to add to any replies
¬†¬†¬†¬†¬†¬†¬† from the target SNA application.

¬†¬†¬†¬†¬†¬†¬† If the excludeIpComponent(1) bit is set to 1, then this bit is
¬†¬†¬†¬†¬†¬†¬† ignored by the server.

¬†¬†¬† o average(3) - If this bit is set to 1, then the server SHOULD
¬†¬†¬†¬†¬†¬†¬† calculate a sliding-window average for the collection, based on
¬†¬†¬†¬†¬†¬†¬† the parameters specified for the group.

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 0, then an average is not calculated. In
¬†¬†¬†¬†¬†¬†¬† this case the tn3270eRtExceeded and tn3270eRtOkay notifications
¬†¬†¬†¬†¬†¬†¬† are not generated, even if the traps(5) bit is set to 1.

White & Moore Standards Track [Page 21]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† o buckets(4) - If this bit is set to 1, then the server SHOULD
¬†¬†¬†¬†¬†¬†¬† create and increment response time buckets for the collection,
¬†¬†¬†¬†¬†¬†¬† based on the parameters specified for the group.

¬†¬†¬†¬†¬†¬†¬† If this bit is set to 0, then response time buckets are not
¬†¬†¬†¬†¬†¬†¬† created.

¬†¬†¬† o traps(5) - If this bit is set to 1, then a TN3270E Server is
¬†¬†¬†¬†¬†¬†¬† enabled to generate notifications pertaining to an
¬†¬†¬†¬†¬†¬†¬† tn3270eCollCtlEntry. tn3270CollStart and tn3270CollEnd
¬†¬†¬†¬†¬†¬†¬† generation is enabled simply by traps(5) being set to 1.
¬†¬†¬†¬†¬†¬†¬† tn3270eRtExceeded and tn3270eRtOkay generation enablement
¬†¬†¬†¬†¬†¬†¬† requires that average(3) be set to 1 in addition to the traps(5)
¬†¬†¬†¬†¬†¬†¬† requirement.

¬†¬†¬†¬†¬†¬†¬† If traps(5) is set to 0, then none of the notifications defined
¬†¬†¬†¬†¬†¬†¬† in this MIB are generated for a particular tn3270eRtCollCtlEntry.

¬†¬†¬† Either the average(3) or the buckets(4) bit MUST be set to 1 in order
¬†¬†¬† for response time data collection to occur; both bits MAY be set to
¬†¬†¬† 1. If the average(3) bit is set to 1, then the following objects
¬†¬†¬† have meaning, and are used to control the calculation of the
¬†¬†¬† averages, as well as the generation of the two notifications related
¬†¬†¬† to them:

¬†¬†¬† Either a single entry or multiple entries are created in the
¬†¬†¬† tn3270eRtDataTable for each tn3270eRtCollCtlEntry, depending on
¬†¬†¬† whether tn3270eRtCollCtlType in the control entry has aggregate(0)
¬†¬†¬† selected. The contents of an entry in the tn3270eRtDataTable depend
¬†¬†¬† on the contents of the corresponding entry in the
¬†¬†¬† tn3270eRtCollCtlTable: as described above, some objects in the data
¬†¬†¬† entry return meaningful values only when the average(3) option is
¬†¬†¬† selected in the control entry, while others return meaningful values
¬†¬†¬† only when the buckets(4) option is selected. If both options are
¬†¬†¬† selected, then all the objects return meaningful values. When an
¬†¬†¬† object is not specified to return a meaningful value, an
¬†¬†¬† implementation may return any syntactically valid value in response
¬†¬†¬† to a Get operation.

¬†¬†¬† The following objects return meaningful values if and only if the
¬†¬†¬† average(3) option was selected in the corresponding
¬†¬†¬† tn3270eRtCollCtlEntry:

¬†¬†¬† The first three objects in this list return values derived from the
¬†¬†¬† sliding-window average calculations described earlier. The time of
¬†¬†¬† the most recent sample for these calculations is returned in the
¬†¬†¬† tn3270eRtDataIntTimeStamp object. The next four objects are normal
¬†¬†¬† Counter32 objects, maintaining counts of total response time and
¬†¬†¬† total transactions. The last two objects return sum of the squares
¬†¬†¬† values, to enable variance calculations by a management application.

¬†¬†¬† The following objects return meaningful values if and only if the
¬†¬†¬† buckets(4) option was selected in the corresponding
¬†¬†¬† tn3270eRtCollCtlEntry:

¬†¬†¬† A discontinuity object, tn3270eRtDataDiscontinuityTime, can be used
¬†¬†¬† by a management application to detect when the values of the counter
¬†¬†¬† objects in this table may have been reset, or otherwise experienced a
¬†¬†¬† discontinuity. A possible cause for such a discontinuity is the
¬†¬†¬† TN3270E server's being stopped or restarted. This object returns a
¬†¬†¬† meaningful value regardless of which collection control options were
¬†¬†¬† selected.

¬†¬†¬† An object, tn3270eRtDataRtMethod, identifies whether the IP Network
¬†¬†¬† Time was calculated using either the definite response or TIMING-MARK
¬†¬†¬† approach.

¬†¬†¬† When an entry is created in the tn3270eRtCollCtlTable with its
¬†¬†¬† tn3270eRtCollCtlType aggregate(0) bit set to 1, an entry is
¬†¬†¬† automatically created in the tn3270eRtDataTable; this entry's
¬†¬†¬† tn3270eRtDataClientAddress has the value of a zero-length octet
¬†¬†¬† string, its tn3270eRtDataClientAddrType has the value of unknown(0),
¬†¬†¬† and its tn3270eRtDataClientPort has the value 0.

¬†¬†¬† When an entry is created in the tn3270eRtCollCtlTable with its
¬†¬†¬† tn3270eRtCollCtlType aggregate(0) bit set to 0, a separate entry is
¬†¬†¬† created in the tn3270eRtDataTable for each member of the client group
¬†¬†¬† that currently has a session with the TN3270E server. Entries are
¬†¬†¬† subsequently created for clients that the TN3270E server determines
¬†¬†¬† to be members of the client group when these clients establish
¬†¬†¬† sessions with the server. Entries are also created when clients with
¬†¬†¬† existing sessions are added to the group.

¬†¬†¬† All entries associated with a tn3270eRtCollCtlEntry are deleted from
¬†¬†¬† the tn3270eRtDataTable when that entry is deleted from the
¬†¬†¬† tn3270eRtCollCtlTable. An entry for an individual client in a client
¬†¬†¬† group is deleted when its TCP connection terminates. Once it has
¬†¬†¬† been created, a client's entry in the tn3270eRtDataTable remains
¬†¬†¬† active as long as the collection's tn3270eRtCollCtlEntry exists, even
¬†¬†¬† if the client is removed from the client group for the
¬†¬†¬† tn3270eRtCollCtlEntry.

4.3 Notifications

¬†¬†¬† This MIB defines four notifications related to a tn3270eRtDataEntry.
¬†¬†¬† If the associated tn3270eRtCollCtlType object's traps(5) bit is set
¬†¬†¬† to 1, then the tn3270RtCollStart and tn3270RtCollEnd notifications

White & Moore Standards Track [Page 24]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† are generated when, respsectively, the tn3270eRtDataEntry is created
¬†¬†¬† and deleted. If, in addition, this tn3270eRtCollCtlType object's
¬†¬†¬† average(3) bit is set to 1, then the the tn3270eRtExceeded and
¬†¬†¬† tn3270eRtOkay notifications are generated when the conditions they
¬†¬†¬† report occur.

¬†¬†¬† The following notifications are defined by this MIB:

¬†¬†¬† o tn3270eRtExceeded - The purpose of this notification is to signal
¬†¬†¬†¬†¬†¬†¬† that a performance problem has been detected. If average(3)
¬†¬†¬†¬†¬†¬†¬† response time data is being collected, then this notification is
¬†¬†¬†¬†¬†¬†¬† generated whenever (1) an average response time is first found,
¬†¬†¬†¬†¬†¬†¬† on a collection interval boundary, to have exceeded the high
¬†¬†¬†¬†¬†¬†¬† threshold tn3270eRtCollCtlThreshHigh specified for the client
¬†¬†¬†¬†¬†¬†¬† group, AND (2) the sample on which the average is based is
¬†¬†¬†¬†¬†¬†¬† determined to have been a significant one, via the significance
¬†¬†¬†¬†¬†¬†¬† algorithm described earlier. This notification is not generated
¬†¬†¬†¬†¬†¬†¬† again for a tn3270eRtDataEntry until an average response time
¬†¬†¬†¬†¬†¬†¬† falling below the low threshold tn3270eRtCollCtlThreshLow
¬†¬†¬†¬†¬†¬†¬† specified for the client group has occurred for the entry.

¬†¬†¬† o tn3270eRtOkay - The purpose of this notification is to signal
¬†¬†¬†¬†¬†¬†¬† that a previously reported performance problem has been resolved.
¬†¬†¬†¬†¬†¬†¬† If average(3) response time data is being collected, then this
¬†¬†¬†¬†¬†¬†¬† notification is generated whenever (1) a tn3270eRtExceeded
¬†¬†¬†¬†¬†¬†¬† notification has already been generated, AND (2) an average
¬†¬†¬†¬†¬†¬†¬† response time is first found, on a collection interval boundary,
¬†¬†¬†¬†¬†¬†¬† to have fallen below the low threshold tn3270eRtCollCtlThreshLow
¬†¬†¬†¬†¬†¬†¬† specified for the client group. This notification is not
¬†¬†¬†¬†¬†¬†¬† generated again for a tn3270eRtDataEntry until an average
¬†¬†¬†¬†¬†¬†¬† response time exceeding the high threshold
¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlThreshHigh specified for the client group has
¬†¬†¬†¬†¬†¬†¬† occurred for the entry.

¬†¬†¬† Taken together, the two preceding notifications serve to minimize the
¬†¬†¬† generation of an excessive number of traps in the case of an average
¬†¬†¬† response time that oscillates about its high threshold.

¬†¬†¬† o tn3270eRtCollStart - This notification is generated whenever data
¬†¬†¬†¬†¬†¬†¬† collection begins for a client group, or when a new
¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataEntry becomes active. The primary purpose of this
¬†¬†¬†¬†¬†¬†¬† notification is signal to a management application that a new
¬†¬†¬†¬†¬†¬†¬† client TCP session has been established, and to provide the IP-
¬†¬†¬†¬†¬†¬†¬† to-resource mapping for the session. This notification is not
¬†¬†¬†¬†¬†¬†¬† critical when average(3) data collection is not being performed
¬†¬†¬†¬†¬†¬†¬† for the client group.

White & Moore Standards Track [Page 25]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† o tn3270eRtCollEnd - This notification is generated whenever a data
¬†¬†¬†¬†¬†¬†¬† collection ends. For an aggregate collection, this occurs when
¬†¬†¬†¬†¬†¬†¬† the corresponding tn3270eRtCollCtlEntry is deleted. For an
¬†¬†¬†¬†¬†¬†¬† individual collection, this occurs either when the
¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlEntry is deleted, or when the client's TCP
¬†¬†¬†¬†¬†¬†¬† connection terminates. The purpose of this notification is to
¬†¬†¬†¬†¬†¬†¬† enable a management application to complete a monitoring function
¬†¬†¬†¬†¬†¬†¬† that it was performing, by returning final values for the
¬†¬†¬†¬†¬†¬†¬† collection's data objects.

4.4 Advisory Spin Lock Usage

¬†¬†¬† Within the TN3270E-RT-MIB, tn3270eRtSpinLock is defined as an
¬†¬†¬† advisory lock that allows cooperating TN3270E-RT-MIB applications to
¬†¬†¬† coordinate their use of the tn3270eRtCollCtlTable. When creating a
¬†¬†¬† new entry or altering an existing entry in the tn3270eRtCollCtlTable,
¬†¬†¬† an application SHOULD make use of tn3270eRtSpinLock to serialize
¬†¬†¬† application changes or additions. Since this is an advisory lock,
¬†¬†¬† its use by management applications SHALL NOT be enforced by agents.
¬†¬†¬† Agents MUST, however, implement the tn3270eRtSpinLock object.

¬†¬† tn3270eRtCollCtlTable OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX SEQUENCE OF Tn3270eRtCollCtlEntry
¬†¬†¬†¬†¬†¬† MAX-ACCESS not-accessible
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The response time monitoring collection control table,
¬†¬†¬†¬†¬†¬†¬†¬† which allows a management application to control the
¬†¬†¬†¬†¬†¬†¬†¬† types of response time data being collected, and the
¬†¬†¬†¬†¬†¬†¬†¬† clients for which it is being collected.

¬†¬†¬†¬†¬†¬†¬†¬† This table is indexed by tn3270eSrvrConfIndex and
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eClientGroupName imported from the
¬†¬†¬†¬†¬†¬†¬†¬† TN3270E-MIB. tn3270eSrvrConfIndex indicates within
¬†¬†¬†¬†¬†¬†¬†¬† a host which TN3270E server an entry applies to.
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eClientGroupName it identifies the set of IP
¬†¬†¬†¬†¬†¬†¬†¬† clients for which response time data is being collected.
¬†¬†¬†¬†¬†¬†¬†¬† The particular IP clients making up the set are identified
¬†¬†¬†¬†¬†¬†¬†¬† in the tn3270eClientGroupTable in the TN3270E-MIB."

White & Moore Standards Track [Page 28]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬†¬†¬†¬†¬†¬†¬† aggregate(0) - Aggregate response time data for the
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† client group as a whole. If this bit
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† is set to 0, then maintain response
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† time data separately for each member
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† of the client group.
¬†¬†¬†¬†¬†¬†¬†¬†¬† excludeIpComponent(1) - Do not include the IP-network
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† component in any response times.
¬†¬†¬†¬†¬†¬†¬†¬†¬† ddr(2) - Enable dynamic definite response.
¬†¬†¬†¬†¬†¬†¬†¬†¬† average(3) - Produce an average response time
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† based on a specified collection
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† interval.
¬†¬†¬†¬†¬†¬†¬†¬†¬† buckets(4) - Maintain tn3270eRtDataBucket values in
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† a corresponding tn3270eRtDataEntry,
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† based on the bucket boundaries specified
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† in the tn3270eRtCollCtlBucketBndry
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† objects .
¬†¬†¬†¬†¬†¬†¬†¬†¬† traps(5) - generate the notifications specified
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† in this MIB module. The
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtExceeded and tn3270eRtOkay
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† notifications are generated only if
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† average(3) is also specified."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtCollCtlEntry 2 }

¬†¬†¬†¬†¬†¬†¬†¬†¬† The value of this object is used only if the corresponding
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType has the average(3) setting."
¬†¬†¬†¬†¬†¬† DEFVAL {20} -- 20 seconds
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtCollCtlEntry 3 }

¬†¬†¬†¬†¬†¬†¬†¬† The value of this object is used only if the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType has the average(3) setting."
¬†¬†¬†¬†¬†¬† DEFVAL { 30 } -- yields an interval of 10 minutes when
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† -- used with the default SPeriod value
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtCollCtlEntry 4 }

¬†¬† tn3270eRtCollCtlThreshHigh OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "seconds"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The threshold for generating a tn3270eRtExceeded
¬†¬†¬†¬†¬†¬†¬†¬† notification, signalling that a monitored total response
¬†¬†¬†¬†¬†¬†¬†¬† time has exceeded the specified limit. A value of zero
¬†¬†¬†¬†¬†¬†¬†¬† for this object suppresses generation of this notification.
¬†¬†¬†¬†¬†¬†¬†¬† The value of this object is used only if the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType has average(3) and traps(5) selected.

¬†¬†¬†¬†¬†¬†¬†¬† A tn3270eRtExceeded notification is not generated again for a
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataEntry until an average response time falling below
¬†¬†¬†¬†¬†¬†¬†¬† the low threshold tn3270eRtCollCtlThreshLow specified for the
¬†¬†¬†¬†¬†¬†¬†¬† client group has occurred for the entry."

¬†¬† tn3270eRtCollCtlThreshLow OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "seconds"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The threshold for generating a tn3270eRtOkay notification,
¬†¬†¬†¬†¬†¬†¬†¬† signalling that a monitored total response time has fallen
¬†¬†¬†¬†¬†¬†¬†¬† below the specified limit. A value of zero for this object
¬†¬†¬†¬†¬†¬†¬†¬† suppresses generation of this notification. The value of
¬†¬†¬†¬†¬†¬†¬†¬† this object is used only if the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType has average(3) and traps(5) selected.

¬†¬†¬†¬†¬†¬†¬†¬† A tn3270eRtOkay notification is not generated again for a
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataEntry until an average response time

¬†¬† tn3270eRtCollCtlIdleCount OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "transactions"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The value of this object is used to determine whether a
¬†¬†¬†¬†¬†¬†¬†¬† sample that yields an average response time exceeding the
¬†¬†¬†¬†¬†¬†¬†¬† value of tn3270eRtCollCtlThreshHigh was a statistically
¬†¬†¬†¬†¬†¬†¬†¬† valid one. If the following statement is true, then the
¬†¬†¬†¬†¬†¬†¬†¬† sample was statistically valid, and so a tn3270eRtExceeded
¬†¬†¬†¬†¬†¬†¬†¬† notification should be generated:

¬†¬† tn3270eRtCollCtlBucketBndry2 OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "tenths of seconds"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The value of this object, together with that of the
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlBucketBndry1 object, defines the range
¬†¬†¬†¬†¬†¬†¬†¬† of transaction response times counted in the
¬†¬†¬†¬†¬†¬†¬†¬† Tn3270eRtDataBucket2Rts object: those greater than the
¬†¬†¬†¬†¬†¬†¬†¬† value of the tn3270eRtCollCtlBucketBndry1 object, and

¬†¬† tn3270eRtCollCtlBucketBndry3 OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "tenths of seconds"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The value of this object, together with that of the
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlBucketBndry2 object, defines the range of
¬†¬†¬†¬†¬†¬†¬†¬† transaction response times counted in the
¬†¬†¬†¬†¬†¬†¬†¬† Tn3270eRtDataBucket3Rts object: those greater than the
¬†¬†¬†¬†¬†¬†¬†¬† value of the tn3270eRtCollCtlBucketBndry2 object, and less
¬†¬†¬†¬†¬†¬†¬†¬† than or equal to the value of this object."
¬†¬†¬†¬†¬†¬† DEFVAL { 50 }
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtCollCtlEntry 10 }

¬†¬† tn3270eRtCollCtlBucketBndry4 OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Unsigned32
¬†¬†¬†¬†¬†¬† UNITS "tenths of seconds"
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "The value of this object, together with that of the
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlBucketBndry3 object, defines the range
¬†¬†¬†¬†¬†¬†¬†¬† of transaction response times counted in the
¬†¬†¬†¬†¬†¬†¬†¬† Tn3270eRtDataBucket4Rts object: those greater than the
¬†¬†¬†¬†¬†¬†¬†¬† value of the tn3270eRtCollCtlBucketBndry3 object, and
¬†¬†¬†¬†¬†¬†¬†¬† less than or equal to the value of this object.

¬†¬†¬†¬†¬†¬†¬†¬† The value of this object also defines the range of
¬†¬†¬†¬†¬†¬†¬†¬† transaction response times counted in the
¬†¬†¬†¬†¬†¬†¬†¬† Tn3270eRtDataBucket5Rts object: those greater than the
¬†¬†¬†¬†¬†¬†¬†¬† value of this object."
¬†¬†¬†¬†¬†¬† DEFVAL { 100 }
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtCollCtlEntry 11 }

¬†¬† tn3270eRtCollCtlRowStatus OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX RowStatus
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-create
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "This object allows entries to be created and deleted
¬†¬†¬†¬†¬†¬†¬†¬†¬† in the tn3270eRtCollCtlTable. An entry in this table
¬†¬†¬†¬†¬†¬†¬†¬†¬† is deleted by setting this object to destroy(6).
¬†¬†¬†¬†¬†¬†¬†¬†¬† Deleting an entry in this table has the side-effect

¬†¬† tn3270eRtDataEntry OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX Tn3270eRtDataEntry
¬†¬†¬†¬†¬†¬† MAX-ACCESS not-accessible
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "Entries in this table are created based upon the
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlTable. When the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType has aggregate(0) specified, a single
¬†¬†¬†¬†¬†¬†¬†¬† entry is created in this table, with a tn3270eRtDataClientAddrType
¬†¬†¬†¬†¬†¬†¬†¬† of unknown(0), a zero-length octet string value for
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataClientAddress, and a tn3270eRtDataClientPort value of
¬†¬†¬†¬†¬†¬†¬†¬† 0. When aggregate(0) is not specified, a separate entry is
¬†¬†¬†¬†¬†¬†¬†¬† created for each client in the group.

¬†¬†¬†¬†¬†¬†¬†¬† Prior to the calculation of the first interval
¬†¬†¬†¬†¬†¬†¬†¬† averages, this object returns the value
¬†¬†¬†¬†¬†¬†¬†¬† 0x0000000000000000000000. When this value is
¬†¬†¬†¬†¬†¬†¬†¬† returned, the remaining objects in the entry have
¬†¬†¬†¬†¬†¬†¬†¬† no significance."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtDataEntry 7 }

¬†¬†¬†¬†¬†¬†¬†¬† The value 'none(0) indicates that response times were not
¬†¬†¬†¬†¬†¬†¬†¬† calculated for the IP network."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtDataEntry 19 }

¬†¬† tn3270eRtDataDiscontinuityTime OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX TimeStamp
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-only
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The value of sysUpTime on the most recent occasion at
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† which one or more of this entry's counter objects
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† suffered a discontinuity. This may happen if a TN3270E
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† server is stopped and then restarted, and local methods
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† are used to set up collection policy
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† (tn3270eRtCollCtlTable entries)."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtDataEntry 20 }
¬†¬† tn3270eRtSpinLock OBJECT-TYPE
¬†¬†¬†¬†¬†¬† SYNTAX TestAndIncr
¬†¬†¬†¬†¬†¬† MAX-ACCESS read-write
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "An advisory lock used to allow cooperating TN3270E-RT-MIB
¬†¬†¬†¬†¬†¬†¬†¬† applications to coordinate their use of the
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlTable.

White & Moore Standards Track [Page 39]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬†¬†¬†¬†¬†¬† When creating a new entry or altering an existing entry
¬†¬†¬†¬†¬†¬†¬†¬† in the tn3270eRtCollCtlTable, an application should make
¬†¬†¬†¬†¬†¬†¬†¬† use of tn3270eRtSpinLock to serialize application changes
¬†¬†¬†¬†¬†¬†¬†¬† or additions.

¬†¬†¬†¬†¬†¬†¬†¬† Since this is an advisory lock, the use of this lock is
¬†¬†¬†¬†¬†¬†¬†¬† not enforced."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtObjects 3 }

¬†¬† -- Notifications

¬†¬† tn3270eRtExceeded NOTIFICATION-TYPE
¬†¬†¬†¬†¬†¬† OBJECTS {
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataIntTimeStamp,
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataAvgRt,
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataAvgIpRt,
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataAvgCountTrans,
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataRtMethod
¬†¬†¬†¬†¬†¬† }
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "This notification is generated when the average response
¬†¬†¬†¬†¬†¬†¬†¬† time, tn3270eRtDataAvgRt, exceeds
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlThresholdHigh at the end of a collection
¬†¬†¬†¬†¬†¬†¬†¬† interval specified by tn3270eCollCtlSPeriod
¬†¬†¬†¬†¬†¬†¬†¬† times tn3270eCollCtlSPMult. Note that the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eCollCtlType must have traps(5) and average(3) set
¬†¬†¬†¬†¬†¬†¬†¬† for this notification to be generated. In addition,
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataAvgRt are algorithmically compared to
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlIdleCount for determination if this
¬†¬†¬†¬†¬†¬†¬†¬† notification will be suppressed."
¬†¬†¬†¬†¬†¬† ::= { tn3270eRtNotifications 1 }

¬†¬† tn3270eRtCollStart NOTIFICATION-TYPE
¬†¬†¬†¬†¬†¬† OBJECTS {
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtDataRtMethod, -- type of collection
¬†¬†¬†¬†¬†¬†¬†¬†¬† tn3270eResMapElementType -- type of resource
¬†¬†¬†¬†¬†¬† }
¬†¬†¬†¬†¬†¬† STATUS current
¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬† "This notification is generated when response time data
¬†¬†¬†¬†¬†¬†¬†¬† collection is enabled for a member of a client group.
¬†¬†¬†¬†¬†¬†¬†¬† In order for this notification to occur the corresponding
¬†¬†¬†¬†¬†¬†¬†¬† tn3270eRtCollCtlType must have traps(5) selected.

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlType
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation to
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlSPeriod
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to allow the user to change
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† the default value of this object, and is allowed to
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† use a different default."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlSPMult
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlThreshHigh
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

White & Moore Standards Track [Page 42]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlIdleCount
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlBucketBndry1
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlBucketBndry2
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlBucketBndry3
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬†¬†¬†¬† OBJECT tn3270eRtCollCtlBucketBndry4
¬†¬†¬†¬†¬†¬†¬†¬†¬† MIN-ACCESS read-only
¬†¬†¬†¬†¬†¬†¬†¬†¬† DESCRIPTION
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† "The agent is not required to support a SET operation
¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬†¬† to this object in the absence of adequate security."

¬†¬†¬† Certain management information defined in this MIB may be considered
¬†¬†¬† sensitive in some network environments. Therefore, authentication of
¬†¬†¬† received SNMP requests and controlled access to management
¬†¬†¬† information SHOULD be employed in such environments. An
¬†¬†¬† authentication protocol is defined in [12]. A protocol for access
¬†¬†¬† control is defined in [15].

¬†¬†¬† Several objects in this MIB allow write access or provide for row
¬†¬†¬† creation. Allowing this support in a non-secure environment can have
¬†¬†¬† a negative effect on network operations. It is RECOMMENDED that
¬†¬†¬† implementers seriously consider whether set operations or row
¬†¬†¬† creation SHOULD be allowed without providing, at a minimum,
¬†¬†¬† authentication of request origin. It is RECOMMENDED that without
¬†¬†¬† such support that the following objects be implemented as read-only:

¬†¬†¬† The administrative method to use to create and manage the
¬†¬†¬† tn3270eRtCollCtlTable when SET support is not allowed is outside of
¬†¬†¬† the scope of this memo.

7.0 Intellectual Property

¬†¬†¬† The IETF takes no position regarding the validity or scope of any
¬†¬†¬† intellectual property or other rights that might be claimed to
¬†¬†¬† pertain to the implementation or use of the technology described in
¬†¬†¬† this document or the extent to which any license under such rights

White & Moore Standards Track [Page 45]
¬†
RFC 2562 TN3270E-RT-MIB April 1999
¬†¬†¬† might or might not be available; neither does it represent that it
¬†¬†¬† has made any effort to identify any such rights. Information on the
¬†¬†¬† IETF's procedures with respect to rights in standards-track and
¬†¬†¬† standards-related documentation can be found in BCP-11. Copies of
¬†¬†¬† claims of rights made available for publication and any assurances of
¬†¬†¬† licenses to be made available, or the result of an attempt made to
¬†¬†¬† obtain a general license or permission for the use of such
¬†¬†¬† proprietary rights by implementers or users of this specification can
¬†¬†¬† be obtained from the IETF Secretariat.

¬†¬†¬† The IETF invites any interested party to bring to its attention any
¬†¬†¬† copyrights, patents or patent applications, or other proprietary
¬†¬†¬† rights which may cover technology that may be required to practice
¬†¬†¬† this standard. Please address the information to the IETF Executive
¬†¬†¬† Director.

8.0 Acknowledgments

¬†¬†¬† This document is a product of the TN3270E Working Group. Special
¬†¬†¬† thanks are due to Derek Bolton and Michael Boe of Cisco Systems for
¬†¬†¬† their numerous comments and suggestions for improving the structure
¬†¬†¬† of this MIB. Thanks also to Randy Presuhn of BMC Software for his
¬†¬†¬† valuable review comments on several versions of the document.

¬†¬†¬† This document and translations of it may be copied and furnished to
¬†¬†¬† others, and derivative works that comment on or otherwise explain it
¬†¬†¬† or assist in its implementation may be prepared, copied, published
¬†¬†¬† and distributed, in whole or in part, without restriction of any
¬†¬†¬† kind, provided that the above copyright notice and this paragraph are
¬†¬†¬† included on all such copies and derivative works. However, this
¬†¬†¬† document itself may not be modified in any way, such as by removing
¬†¬†¬† the copyright notice or references to the Internet Society or other
¬†¬†¬† Internet organizations, except as needed for the purpose of
¬†¬†¬† developing Internet standards in which case the procedures for
¬†¬†¬† copyrights defined in the Internet Standards process must be
¬†¬†¬† followed, or as required to translate it into languages other than
¬†¬†¬† English.

¬†¬†¬† The limited permissions granted above are perpetual and will not be
¬†¬†¬† revoked by the Internet Society or its successors or assigns.

¬†¬†¬† This document and the information contained herein is provided on an
¬†¬†¬† "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
¬†¬†¬† TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
¬†¬†¬† BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
¬†¬†¬† HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
¬†¬†¬† MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.