Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
RFC 3593
Document | Type |
RFC - Draft Standard
(September 2003; No errata)
Obsoletes RFC 2493
|
|
---|---|---|---|
Author | Kaj Tesink | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3593 (Draft Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Erik Nordmark | ||
IESG note | The implementation report can be viewed at http://www.ietf.org/IESG/Implementations/RFC2493-Implementation.txt | ||
Send notices to | <fayely98@hotmail.com> |
Network Working Group K. Tesink, Ed. Request for Comments: 3593 Telcordia Technologies Obsoletes: 2493 September 2003 Category: Standards Track Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 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. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract This document defines a set of Textual Conventions for MIB modules that make use of performance history data based on 15 minute intervals. This memo replaces RFC 2493. Changes relative to RFC 2493 are summarized in the MIB module's REVISION clause. Table of Contents 1. Introduction ................................................. 2 2. Note on Invalid Data and Proxies ............................. 2 3. Note on xyzTimeElapsed ....................................... 3 4. Note on xyzValidIntervals .................................... 3 5. Definitions .................................................. 4 6. Acknowledgments .............................................. 8 7. References ................................................... 8 7.1. Normative References ................................... 8 7.2. Informative References ................................. 8 8. Security Considerations ...................................... 9 9. Intellectual Property Statement .............................. 9 10. Editor's Address ............................................. 9 11. Full Copyright Statement ..................................... 10 Tesink Standards Track [Page 1] RFC 3593 15 Minute Based Performance History TCs September 2003 1. Introduction 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: 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 The agent allocates events to 'buckets' where each bucket represents an interval of time. Telecommunications equipment often makes use of the latter strategy. See [3][4][5][7][8] for examples. In particular, for this equipment it is common that history data is maintained by the agent in terms of fifteen minute intervals. This memo does not attempt to compare the relative merits of different strategies used 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. 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 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 RFC 2579 [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. The performance history textual conventions defined in this memo are based on 32 bit counts. For high capacity performance history counts see [9]. 2. Note on Invalid Data and Proxies In this document, the word proxy indicates 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 Tesink Standards Track [Page 2] RFC 3593 15 Minute Based Performance History TCs September 2003 forward requests to the actual DS3/E3 interface. It is expected in such an application that there are periods of time where the proxy isShow full document text