rfc2562.txt

来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 1,449 行 · 第 1/5 页

TXT
1,449
字号
       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:   o   tn3270eRtCollCtlSPeriod   o   tn3270eRtCollCtlSPMult   o   tn3270eRtCollCtlThreshHigh   o   tn3270eRtCollCtlThreshLow   o   tn3270eRtCollCtlIdleCount   The previous objects' values are meaningless if the associated   average(3) bit is not set to 1.   If the buckets(4) bit is set to 1, then the following objects have   meaning, and specify the bucket boundaries:   o   tn3270eRtCollCtlBucketBndry1   o   tn3270eRtCollCtlBucketBndry2   o   tn3270eRtCollCtlBucketBndry3   o   tn3270eRtCollCtlBucketBndry4   The previous objects' values are meaningless if the associated   buckets(4) bit is not set to 1.   If an entry in the tn3270RtCollCtlTable has the value active(1) for   its RowStatus, then an implementation SHALL NOT allow Set operations   for any objects in the entry except:White & Moore               Standards Track                    [Page 22]RFC 2562                     TN3270E-RT-MIB                   April 1999   o   tn3270eRtCollCtlThreshHigh   o   tn3270eRtCollCtlThreshLow   o   tn3270eRtCollCtlRowStatus4.2  tn3270eRtDataTable   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:   o   tn3270eRtDataAvgRt   o   tn3270eRtDataAvgIpRt   o   tn3270eRtDataAvgCountTrans   o   tn3270eRtDataIntTimeStamp   o   tn3270eRtDataTotalRts   o   tn3270eRtDataTotalIpRts   o   tn3270eRtDataCountTrans   o   tn3270eRtDataCountDrs   o   tn3270eRtDataElapsRndTrpSq   o   tn3270eRtDataElapsIpRtSq   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:White & Moore               Standards Track                    [Page 23]RFC 2562                     TN3270E-RT-MIB                   April 1999   o   tn3270eRtDataBucket1Rts   o   tn3270eRtDataBucket2Rts   o   tn3270eRtDataBucket3Rts   o   tn3270eRtDataBucket4Rts   o   tn3270eRtDataBucket5Rts   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 notificationsWhite & 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.5.0  Definitions  TN3270E-RT-MIB DEFINITIONS ::= BEGIN  IMPORTS      MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,      Counter32, Unsigned32, Gauge32                  FROM SNMPv2-SMI      RowStatus, DateAndTime, TimeStamp, TestAndIncr                  FROM SNMPv2-TC      MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP                  FROM SNMPv2-CONF      tn3270eSrvrConfIndex, tn3270eClientGroupName,      tn3270eResMapElementType                  FROM TN3270E-MIB      IANATn3270eAddrType, IANATn3270eAddress                  FROM IANATn3270eTC-MIB      snanauMIB                  FROM SNA-NAU-MIB;    tn3270eRtMIB   MODULE-IDENTITY        LAST-UPDATED "9807270000Z" -- July 27, 

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?