Browse Prior Art Database

Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals (RFC3593)

IP.com Disclosure Number: IPCOM000019168D
Original Publication Date: 2003-Sep-01
Included in the Prior Art Database: 2003-Sep-03
Document File: 11 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Tesink: AUTHOR [+2]

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 17% of the total text.

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

as...