Internet Draft
INTERNET-DRAFT
<draft-ietf-atommib-perfhistTC-01.txt>
Textual Conventions for MIB Modules Using Performance History
Based on 15 Minute Intervals
October 24, 1996
Kaj Tesink (editor)
Bell Communications Research
kaj@cc.bellcore.com
1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as a
"work in progress".
To learn the current status of any Internet-Draft, please
check the "1id-abstracts.txt" listing contained in the
Internet-Drafts Shadow Directories on ds.internic.net (US East
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast),
or munnari.oz.au (Pacific Rim).
draft 15 Minute Based Performance History TCs 10/24/96
2. Introduction
When designing a MIB module, it is often useful to define new
types similar to those defined in the SMI. 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].
This memo does not specify a standard for the Internet
community.
Expires 4/24/97 [Page 2]
draft 15 Minute Based Performance History TCs 10/24/96
3. Definitions
PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Gauge32, experimental
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
mib-2
FROM RFC1213-MIB;
perfHistTCMIB MODULE-IDENTITY
LAST-UPDATED "9610241100Z"
ORGANIZATION "IETF AToMMIB and TrunkMIB WGs"
CONTACT-INFO
"Kaj Tesink
Postal: Bell Communications Research
331 Newman Springs Road
Red Bank, NJ 07701
USA
Tel: +1 908 758 5254
Fax: +1 908 758 4177
E-mail: kaj@cc.bellcore.com"
DESCRIPTION
"This MIB Module provides Textual Conventions
to be used by systems supporting 15 minute
based performance history counts."
::= { mib-2 xxx }
-- ****************************************
-- * Note to RFC editor *
-- * Assign a number for xxx *
-- * from IANA when publishing this *
-- * MIB as RFC *
-- ****************************************
-- The Textual Conventions defined below are organized
-- alphabetically
-- Use of these TCs assumes the following:
Expires 4/24/97 [Page 3]
draft 15 Minute Based Performance History TCs 10/24/96
-- 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 media-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 per
-- interface:
--
-- 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 error-measurement
-- period."
-- ::= { xxx }
-- xyzValidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..)
-- -- 1 =< n =< 96
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of previous near end intervals
-- for which valid data was collected. The value
-- will be unless the interface was brought
-- online within the last 24 hours, in which case
-- the value will be the number of complete 15
-- minute near end intervals since the interface
-- has been online. 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 valid data is available."
-- ::= { xxx }
-- xyzInvalidIntervals OBJECT-TYPE
-- SYNTAX INTEGER (0..)
Expires 4/24/97 [Page 4]
draft 15 Minute Based Performance History TCs 10/24/96
-- MAX-ACCESS read-only
-- STATUS current
-- DESCRIPTION
-- "The number of intervals for which no valid
-- data is available."
-- ::= { xxx }
PerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with interface
performance measurements in a current 15
minute measurement interval. The value
of this counter start 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."
SYNTAX Gauge32
PerfIntervalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with interface
performance measurements 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 (noSuch*)
shall be returned. 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."
Expires 4/24/97 [Page 5]
draft 15 Minute Based Performance History TCs 10/24/96
SYNTAX Gauge32
PerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with interface
performance measurements agggregating the
previous valid 15 minute measurement
intervals. Intervals for which no valid
data was available are counted as 0."
SYNTAX Gauge32
END
Expires 4/24/97 [Page 6]
draft 15 Minute Based Performance History TCs 10/24/96
4. Acknowledgments
This document is a product of the AToMMIB and TrunkMIB Working
Groups.
Expires 4/24/97 [Page 7]
draft 15 Minute Based Performance History TCs 10/24/96
5. References
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC1903, SNMP
Research,Inc., Cisco Systems, Inc., Dover Beach
Consulting, Inc., International Network Services, January
1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Structure of Management Information for Version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC1902,
SNMP Research,Inc., Cisco Systems, Inc., Dover Beach
Consulting, Inc., International Network Services, January
1996.
[3] Fowler, D., "Definitions of Managed Objects for the DS1,
E1, DS2 and E2 Interface Types", RFCxxxx, Newbridge
Networks, ????? 1996.
[4] Fowler, D., "Definitions of Managed Objects for the
DS3/E3 Interface Type", RFCxxxx, Newbridge Networks, ????
1996.
[5] Tesink, K., "Definitions of Managed Objects for the
SONET/SDH Interface Type", RFCxxxx, Newbridge Networks,
???? 1996.
Expires 4/24/97 [Page 8]
draft 15 Minute Based Performance History TCs 10/24/96
6. Security Considerations
Security issues are not discussed in this memo.
7. Authors' Addresses
Kaj Tesink
Bell Communications Research
Room 1A-427
331 Newman Springs Road
P.O. Box 7020
Red Bank, NJ 07701-7020
Phone: (908) 758-5254
EMail: kaj@cc.bellcore.com
Expires 4/24/97 [Page 9]
draft 15 Minute Based Performance History TCs 10/24/96
Table of Contents
1 Status of this Memo ................................... 1
2 Introduction .......................................... 2
3 Definitions ........................................... 3
4 Acknowledgments ....................................... 7
5 References ............................................ 8
6 Security Considerations ............................... 9
7 Authors' Addresses .................................... 9
Expires 4/24/97 [Page 10]