RFC 2562 (rfc2562) - Page 2 of 49

Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)

RFC 2562                     TN3270E-RT-MIB                   April 1999


     3.4.2  TIMING-MARK Usage   . . . . . . . . . . . . . . . . . . 13
   3.5  Performance Data Modelling  . . . . . . . . . . . . . . . . 15
     3.5.1  Averaging Response Times  . . . . . . . . . . . . . . . 15
     3.5.2  Response Time Buckets   . . . . . . . . . . . . . . . . 18
   4.0  Structure of the MIB  . . . . . . . . . . . . . . . . . . . 19
   4.1  tn3270eRtCollCtlTable   . . . . . . . . . . . . . . . . . . 19
   4.2  tn3270eRtDataTable  . . . . . . . . . . . . . . . . . . . . 23
   4.3  Notifications   . . . . . . . . . . . . . . . . . . . . . . 24
   4.4  Advisory Spin Lock Usage  . . . . . . . . . . . . . . . . . 26
   5.0  Definitions   . . . . . . . . . . . . . . . . . . . . . . . 26
   6.0  Security Considerations   . . . . . . . . . . . . . . . . . 45
   7.0  Intellectual Property   . . . . . . . . . . . . . . . . . . 45
   8.0  Acknowledgments   . . . . . . . . . . . . . . . . . . . . . 46
   9.0  References  . . . . . . . . . . . . . . . . . . . . . . . . 46
   10.0  Authors' Addresses   . . . . . . . . . . . . . . . . . . . 48
   11.0  Full Copyright Statement   . . . . . . . . . . . . . . . . 49

1.0  Introduction

   This document is a product of the TN3270E Working Group.  It defines
   a protocol and a MIB module to enable a TN3270E server to collect and
   keep track of response time data for both TN3270 and TN3270E clients.
   Basis for implementing this MIB:

   o   TN3270E-MIB, Base Definitions of Managed Objects for TN3270E
       Using SMIv2 [20]

   o   TN3270E RFCs

   o   Telnet Timing Mark Option RFC [17].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119, reference
   [23].

2.0  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o   An overall architecture, described in RFC 2271 [1].

   o   Mechanisms for describing and naming objects and events for the
       purpose of management.  The first version of this Structure of
       Management Information (SMI) is called SMIv1 and described in STD
       16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].  The
       second version, called SMIv2, is described in RFC 1902 [5], RFC



White & Moore               Standards Track