Network Working Group K. Tesink, Editor
Request for Comments: 2493 Bellcore
Category: Standards Track January 1999
Network Working Group K. Tesink, Editor
Request for Comments: 2493 Bellcore
Category: Standards Track January 1999
Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
使用基于15分钟间隔的性能历史记录的MIB模块的文本约定
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This document defines a set of Textual Conventions for MIB modules which make use of performance history data based on 15 minute intervals.
本文档为MIB模块定义了一组文本约定，这些MIB模块使用基于15分钟间隔的性能历史数据。
1 Table of Contents ..................................... 1
2 Introduction .......................................... 1
3 Note on Invalid Data and Proxy ........................ 2
4 Note on xyzTimeElapsed ................................ 3
5 Note on xyzValidIntervals ............................. 3
6 Definitions ........................................... 3
7 Acknowledgments ....................................... 7
8 References ............................................ 7
9 Security Considerations ............................... 8
10 IANA Considerations .................................. 8
11 Author's Address ..................................... 8
12 Intellectual Property ................................ 8
13 Full Copyright Statement ............................. 9
1 Table of Contents ..................................... 1
2 Introduction .......................................... 1
3 Note on Invalid Data and Proxy ........................ 2
4 Note on xyzTimeElapsed ................................ 3
5 Note on xyzValidIntervals ............................. 3
6 Definitions ........................................... 3
7 Acknowledgments ....................................... 7
8 References ............................................ 7
9 Security Considerations ............................... 8
10 IANA Considerations .................................. 8
11 Author's Address ..................................... 8
12 Intellectual Property ................................ 8
13 Full Copyright Statement ............................. 9
In cases where a manager must obtain performance history data about the behavior of equipment it manages several strategies can be followed in the design of a MIB that represents the managed equipment, including:
如果管理者必须获得有关其所管理设备行为的性能历史数据，则在设计代表所管理设备的MIB时，可以遵循几种策略，包括：
0 The agent counts events on a continuous basis and, whenever desired, the manager obtains the value of the event counter and adjusts its understanding of the history of events at the agent.
0代理连续统计事件，并且，只要需要，管理器就会获得事件计数器的值，并调整其对代理上事件历史的理解。
0 The agent allocates events to 'buckets' where each bucket represents an interval of time.
0代理将事件分配给“bucket”，其中每个bucket表示一个时间间隔。
Telecommunications equipment often makes use of the latter strategy. See [3][4][5] for examples. In particular, for this equipment it is common that history data is maintained by the agent in terms of fifteen minute intervals.
电信设备通常采用后一种策略。示例见[3][4][5]。特别是，对于该设备，历史数据通常由代理按15分钟的间隔进行维护。
This memo does not attempt to compare the relative merits of different strategies to obtain history data. Differences may include polling policy, the amount of management traffic between manager and agent, agent simplicity, and 'data currentness' of the data obtained by the manager. MIB designers should consider these aspects when choosing a particular strategy in a MIB design. Instead, this memo provides definitions that can be used in MIB modules that require history data based on fifteen minute intervals.
本备忘录并不试图比较不同策略的相对优点以获取历史数据。差异可能包括轮询策略、管理器和代理之间的管理通信量、代理的简单性以及管理器获得的数据的“数据当前性”。MIB设计者在选择MIB设计中的特定策略时应该考虑这些方面。相反，本备忘录提供的定义可用于MIB模块中，这些模块需要基于15分钟间隔的历史数据。
When designing a MIB module, it is often useful to define new types similar to those defined in the SMI [2]. In comparison to a type defined in the SMI, each of these new types has a different name, a similar syntax, but a more precise semantics. These newly defined types are termed textual conventions, and are used for the convenience of humans reading the MIB module. This is done through Textual Conventions as defined in RFC1903[1]. It is the purpose of this document to define the set of textual conventions to be used when performance history based on 15 minute intervals is kept. See for example the Trunk MIB modules [3][4][5].
在设计MIB模块时，定义与SMI[2]中定义的类型类似的新类型通常很有用。与SMI中定义的类型相比，每个新类型都有不同的名称、相似的语法，但语义更精确。这些新定义的类型称为文本约定，用于方便人们阅读MIB模块。这是通过RFC1903[1]中定义的文本约定完成的。本文件的目的是定义在保留基于15分钟间隔的性能历史记录时要使用的一组文本约定。例如，请参见中继MIB模块[3][4][5]。
In this document, the word proxy is meant to indicate an application which receives SNMP messages and replies to them on behalf of the devices where the actual implementation resides, e.g., DS3/E3 interfaces. The proxy will have already collected the information about the DS3/E3 interfaces into its local database and may not necessarily forward requests to the actual DS3/E3 interface. It is expected in such an application that there are periods of time where the proxy is not communicating with the DS3/E3 interfaces. In these instances the proxy will not necessarily have up-to-date configuration information and will most likely have missed the collection of some data. Missed data collection may result in some intervals in the interval table being unavailable.
在本文档中，“代理”一词是指代表实际实现所在的设备（如DS3/E3接口）接收SNMP消息并回复这些消息的应用程序。代理已经将有关DS3/E3接口的信息收集到其本地数据库中，并且可能不一定将请求转发到实际的DS3/E3接口。在这种应用程序中，预计有一段时间代理不与DS3/E3接口通信。在这些情况下，代理不一定具有最新的配置信息，并且很可能错过了一些数据的收集。未收集数据可能会导致间隔表中的某些间隔不可用。
While xyzTimeElapsed is defined as having a maximum there may be cases (e.g., an adjustment in the system's time-of-day clock) where the actual value of the current interval would exceed this maximum value.
虽然XYZTimeAppeased被定义为具有最大值，但在某些情况下（例如，系统的时间时钟调整），当前间隔的实际值可能会超过该最大值。
Suppose that an agent which aligns its 15-minute measurement intervals to 15-minute time-of-day ("wall clock") boundaries has a time-of-day clock that systematically gains time, and that a manager periodically corrects the clock by setting it back.
假设一个代理将其15分钟的测量间隔与15分钟的时间（“挂钟”）边界对齐，该代理有一个系统地获取时间的时间时钟，并且管理者通过将时钟设置回原位来定期校正时钟。
It is assumed that the agent's time-of-day clock is reasonably accurate, say within a few seconds per day. Thus, the manager's periodic clock adjustments will normally be small, and if done frequently enough, need not ever exceed 10 seconds. In this case all interval durations will be within the allowed tolerance and none need be marked invalid, _if_ the ANSI procedure of ending measurement intervals at 15-minute time-of-day boundaries is followed [6].
假设代理的时间时钟相当准确，例如每天几秒钟之内。因此，管理器的周期性时钟调整通常很小，如果足够频繁，不需要超过10秒。在这种情况下，所有间隔时间都将在允许的公差范围内，并且如果遵循ANSI在一天中的15分钟结束测量间隔的程序，则无需将任何间隔时间标记为无效[6]。
If the time-of-day clock is systematically adjusted in small increments, then always ending measurement intervals at 15-minute time-of-day boundaries will result in the long term in the correct number of intervals with the correct average duration, irrespective of whether the clock is moved ahead or moved back. Thus, if, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, it is considered acceptable that the agent will return the maximum value.
如果系统地以小增量调整一天中的时间时钟，则始终以15分钟的时间边界结束测量间隔，将导致在正确的时间间隔数和正确的平均持续时间内进行长期调整，无论时钟是向前移动还是向后移动。因此，如果出于某种原因，例如系统的时间时钟调整，当前间隔超过最大值，则认为代理返回最大值是可以接受的。
The overall constraint on <n> is 1 =< n =< 96. Any additional constraints on n must be defined in the DESCRIPTION clause (e.g., see [5]).
<n>的总体约束是1=<n=<96。n上的任何附加约束必须在描述条款中定义（例如，见[5]）。
PerfHist-TC-MIB DEFINITIONS ::= BEGIN
PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, Gauge32, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
从SNMPv2 TC从SNMPv2 SMI文本约定导入模块标识、量规32、mib-2；
perfHistTCMIB MODULE-IDENTITY
perfHistTCMIB模块标识
LAST-UPDATED "9811071100Z"
ORGANIZATION "IETF AToMMIB and TrunkMIB WGs"
CONTACT-INFO
"Kaj Tesink
Postal: Bellcore
331 Newman Springs Road
Red Bank, NJ 07701
USA
Tel: +1 732 758 5254
Fax: +1 732 758 2269
E-mail: kaj@bellcore.com"
DESCRIPTION
"This MIB Module provides Textual Conventions
to be used by systems supporting 15 minute
based performance history counts."
::= { mib-2 58 }
LAST-UPDATED "9811071100Z"
ORGANIZATION "IETF AToMMIB and TrunkMIB WGs"
CONTACT-INFO
"Kaj Tesink
Postal: Bellcore
331 Newman Springs Road
Red Bank, NJ 07701
USA
Tel: +1 732 758 5254
Fax: +1 732 758 2269
E-mail: kaj@bellcore.com"
DESCRIPTION
"This MIB Module provides Textual Conventions
to be used by systems supporting 15 minute
based performance history counts."
::= { mib-2 58 }
-- The Textual Conventions defined below are organized
-- alphabetically
-- The Textual Conventions defined below are organized
-- alphabetically
-- Use of these TCs assumes the following:
-- 0 The agent supports 15 minute based history
-- counters.
-- 0 The agent is capable of keeping a history of n
-- intervals of 15 minute performance data. The
-- value of n is defined by the specific MIB
-- module but shall be 0 < n =< 96.
-- 0 The agent may optionally support performance
-- data aggregating the history intervals.
-- 0 The agent will keep separate tables for the
-- current interval, the history intervals, and
-- the total aggregates.
-- 0 The agent will keep the following objects.
-- If performance data is kept for multiple instances
-- of a measured entity, then
-- these objects are applied to each instance of
-- the measured entity (e.g., interfaces).
--
-- Use of these TCs assumes the following:
-- 0 The agent supports 15 minute based history
-- counters.
-- 0 The agent is capable of keeping a history of n
-- intervals of 15 minute performance data. The
-- value of n is defined by the specific MIB
-- module but shall be 0 < n =< 96.
-- 0 The agent may optionally support performance
-- data aggregating the history intervals.
-- 0 The agent will keep separate tables for the
-- current interval, the history intervals, and
-- the total aggregates.
-- 0 The agent will keep the following objects.
-- If performance data is kept for multiple instances
-- of a measured entity, then
-- these objects are applied to each instance of
-- the measured entity (e.g., interfaces).
--
-- xyzTimeElapsed OBJECT-TYPE
-- SYNTAX INTEGER (0..899)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- xyzTimeElapsed OBJECT-TYPE
-- SYNTAX INTEGER (0..899)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of seconds that have elapsed since
-- the beginning of the current measurement period.
-- If, for some reason, such as an adjustment in the
-- system's time-of-day clock, the current interval
-- exceeds the maximum value, the agent will return
-- the maximum value."
-- ::= { xxx }
-- "The number of seconds that have elapsed since
-- the beginning of the current measurement period.
-- If, for some reason, such as an adjustment in the
-- system's time-of-day clock, the current interval
-- exceeds the maximum value, the agent will return
-- the maximum value."
-- ::= { xxx }
-- xyzValidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..<n>)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of previous near end intervals
-- for which data was collected.
-- [ The overall constraint on <n> is 1 =< n =< 96; ]
-- [ Define any additional constraints on <n> here. ]
-- The value will be <n> unless the measurement was
-- (re-)started within the last (<n>*15) minutes, in which
-- case the value will be the number of complete 15
-- minute intervals for which the agent has at least
-- some data. In certain cases (e.g., in the case
-- where the agent is a proxy) it is possible that some
-- intervals are unavailable. In this case, this
-- interval is the maximum interval number for
-- which data is available."
-- ::= { xxx }
-- xyzValidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..<n>)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of previous near end intervals
-- for which data was collected.
-- [ The overall constraint on <n> is 1 =< n =< 96; ]
-- [ Define any additional constraints on <n> here. ]
-- The value will be <n> unless the measurement was
-- (re-)started within the last (<n>*15) minutes, in which
-- case the value will be the number of complete 15
-- minute intervals for which the agent has at least
-- some data. In certain cases (e.g., in the case
-- where the agent is a proxy) it is possible that some
-- intervals are unavailable. In this case, this
-- interval is the maximum interval number for
-- which data is available."
-- ::= { xxx }
-- xyzInvalidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..<n>)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of intervals in the range from
-- 0 to xyzValidIntervals for which no
-- data is available. This object will typically
-- be zero except in cases where the data for some
-- intervals are not available (e.g., in proxy
-- situations)."
-- ::= { xxx }
-- xyzInvalidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..<n>)
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of intervals in the range from
-- 0 to xyzValidIntervals for which no
-- data is available. This object will typically
-- be zero except in cases where the data for some
-- intervals are not available (e.g., in proxy
-- situations)."
-- ::= { xxx }
PerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with a
performance measurement in a current 15
minute measurement interval. The value
of this counter starts from zero and is
PerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with a
performance measurement in a current 15
minute measurement interval. The value
of this counter starts from zero and is
increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation)." SYNTAX Gauge32
发生相关事件时增加，直到15分钟间隔结束。此时，计数器的值存储在前15分钟的历史间隔中，CurrentCount在零处重新启动。如果代理在当前间隔内没有可用的有效数据，则相应的对象实例不可用，并且在检索请求时，应返回相应的错误消息以指示该实例不存在（例如，SNMPv1的noSuchName错误和SNMPv2 GET操作的noSuchInstance）。“语法规范32
PerfIntervalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with a
performance measurement in a previous
15 minute measurement interval. In the
case where the agent has no valid data
available for a particular interval the
corresponding object instance is not
available and upon a retrieval request
a corresponding error message shall be
returned to indicate that this instance
does not exist (for example, a noSuchName
error for SNMPv1 and a noSuchInstance for
SNMPv2 GET operation).
In a system supporting
a history of n intervals with
IntervalCount(1) and IntervalCount(n) the
most and least recent intervals
respectively, the following applies at
the end of a 15 minute interval:
- discard the value of IntervalCount(n)
- the value of IntervalCount(i) becomes that
of IntervalCount(i-1) for n >= i > 1
- the value of IntervalCount(1) becomes that
of CurrentCount
- the TotalCount, if supported, is adjusted."
SYNTAX Gauge32
PerfIntervalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with a
performance measurement in a previous
15 minute measurement interval. In the
case where the agent has no valid data
available for a particular interval the
corresponding object instance is not
available and upon a retrieval request
a corresponding error message shall be
returned to indicate that this instance
does not exist (for example, a noSuchName
error for SNMPv1 and a noSuchInstance for
SNMPv2 GET operation).
In a system supporting
a history of n intervals with
IntervalCount(1) and IntervalCount(n) the
most and least recent intervals
respectively, the following applies at
the end of a 15 minute interval:
- discard the value of IntervalCount(n)
- the value of IntervalCount(i) becomes that
of IntervalCount(i-1) for n >= i > 1
- the value of IntervalCount(1) becomes that
of CurrentCount
- the TotalCount, if supported, is adjusted."
SYNTAX Gauge32
PerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current
PerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A counter associated with a performance measurements aggregating the previous valid 15 minute measurement intervals. (Intervals for which no valid data was available are not counted)" SYNTAX Gauge32
描述“与性能测量相关联的计数器，该计数器汇总了以前有效的15分钟测量间隔。（没有有效数据的间隔不计算在内）”语法量表32
END
终止
This document is a product of the AToMMIB and TrunkMIB Working Groups.
本文件是AToMMIB和TrunkMIB工作组的产品。
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[1] Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[3] Fowler, D., "Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types", RFC 2495, January 1999.
[3] Fowler，D.，“DS1、E1、DS2和E2接口类型的托管对象定义”，RFC 2495，1999年1月。
[4] Fowler, D., "Definitions of Managed Objects for the DS3/E3 Interface Type", RFC 2496, January 1999.
[4] Fowler，D.，“DS3/E3接口类型的托管对象定义”，RFC2496，1999年1月。
[5] Tesink, K., "Definitions of Managed Objects for the SONET/SDH Interface Type", Work in Progress.
[5] Tesink，K.“SONET/SDH接口类型的受管对象定义”，正在进行中。
[6] American National Standard for Telecommunications - Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring, ANSI T1.231-1997, September 1997.
[6] 美国国家电信标准-数字体系-第1层在用数字传输性能监测，ANSI T1.231-1997，1997年9月。
This memo defines textual conventions for use in other MIB modules. Security issues for these MIB modules are addressed in the memos defining those modules.
此备忘录定义了在其他MIB模块中使用的文本约定。这些MIB模块的安全问题在定义这些模块的备忘录中进行了说明。
Prior to publication of this memo as an RFC, IANA is requested to make a suitable OBJECT IDENTIFIER assignment.
在将本备忘录作为RFC发布之前，IANA需要进行适当的对象标识符分配。
Kaj Tesink Bellcore 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020
新泽西州纽曼斯普林斯路331号Kaj Tesink Bellcore邮政信箱7020 Red Bank，邮编：07701-7020
Phone: (732) 758-5254 EMail: kaj@bellcore.com
电话：（732）758-5254电子邮件：kaj@bellcore.com
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 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 implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
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.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。