draft-ietf-adslmib-hc-tc-01.txt   draft-ietf-adslmib-hc-tc-02.txt 
Network Working Group B. Ray Network Working Group B. Ray
Category: Internet Draft PESA Switching Systems Category: Internet Draft PESA Switching Systems
R. Abbi R. Abbi
Alcatel Alcatel
June 2002 September 2002
High Capacity Textual Conventions for MIB Modules Using High Capacity Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals Performance History Based on 15 Minute Intervals
draft-ietf-adslmib-hc-tc-01.txt draft-ietf-adslmib-hc-tc-02.txt
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [RFC2026]. Internet-Drafts are all provisions of Section 10 of [RFC2026]. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. The SNMP Management Framework ................................... 2 1. The SNMP Management Framework ................................... 2
2. Overview ........................................................ 3 2. Overview ........................................................ 3
3. Definitions ..................................................... 4 3. Definitions ..................................................... 4
References ...................................................... 8 References ...................................................... 8
Security Considerations ......................................... 10 Security Considerations ......................................... 10
IANA Considerations ............................................. 10 IANA Considerations ............................................. 10
Acknowledgements ................................................ 10 Acknowledgements ................................................ 10
Intellectual Property Notice .................................... 10 Intellectual Property Notice .................................... 10
Authors' Addresses .............................................. 10 Authors' Addresses .............................................. 11
Full Copyright Statement ........................................ 11 Full Copyright Statement ........................................ 11
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
skipping to change at page 4, line 17 skipping to change at page 4, line 20
in an INDEX clause, because there is no INDEX clause mapping in an INDEX clause, because there is no INDEX clause mapping
defined for objects of type Counter64. defined for objects of type Counter64.
3. Definitions 3. Definitions
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Counter64, Counter64,
Unsigned32,
mib-2 FROM SNMPv2-SMI mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
hcPerfHistTCMIB MODULE-IDENTITY hcPerfHistTCMIB MODULE-IDENTITY
LAST-UPDATED "200206160000Z" -- June 16, 2002 LAST-UPDATED "200206160000Z" -- June 16, 2002
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
skipping to change at page 4, line 53 skipping to change at page 4, line 57
Phone: +1 919 850 6194 Phone: +1 919 850 6194
" "
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions to be "This MIB Module provides Textual Conventions to be
used by systems supporting 15 minute based performance used by systems supporting 15 minute based performance
history counts that require high-capacity counts." history counts that require high-capacity counts."
REVISION "200206160000Z" -- June 16, 2002 REVISION "200206160000Z" -- June 16, 2002
DESCRIPTION "Corrected addresses and references." DESCRIPTION "Corrected addresses and references."
REVISION "200209230000Z" -- September 23, 2002
DESCRIPTION "Added HCPerfValidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed, and HCPerfIntervalThreshold."
::= { mib-2 xxx } -- to be assigned by IANA ::= { mib-2 xxx } -- to be assigned by IANA
-- The Textual Conventions defined below are organized -- The Textual Conventions defined below are organized
-- alphabetically -- alphabetically
-- Use of these TCs assumes the following: -- Use of these TCs assumes the following:
-- 0 The agent supports 15 minute based history -- 0 The agent supports 15 minute based history
-- counters. -- counters.
-- 0 The agent is capable of keeping a history of n -- 0 The agent is capable of keeping a history of 96
-- intervals of 15 minute performance data. The -- intervals of 15 minute performance data.
-- value of n is defined by the specific MIB
-- module but shall be 0 < n =< 96.
-- 0 The agent may optionally support performance -- 0 The agent may optionally support performance
-- data aggregating the history intervals. -- data aggregating the history intervals.
-- 0 The agent will keep separate tables for the -- 0 The agent will keep separate tables for the
-- current interval, the history intervals, and -- current interval, the history intervals, and
-- the total aggregates. -- the total aggregates.
-- 0 The agent will keep the following objects. -- 0 The agent will keep the following objects.
-- If performance data is kept for multiple instances -- If performance data is kept for multiple instances
-- of a measured entity, then -- of a measured entity, then
-- these objects are applied to each instance of -- these objects are applied to each instance of
-- the measured entity (e.g., interfaces). -- the measured entity (e.g., interfaces).
-- xyzTimeElapsed OBJECT-TYPE HCPerfValidIntervals ::= TEXTUAL-CONVENTION
-- SYNTAX INTEGER (0..899) STATUS current
-- MAX-ACCESS read-only DESCRIPTION
-- STATUS current "The number of previous near end intervals for which
-- DESCRIPTION data was collected. The value will be 96 unless the
-- "The number of seconds that have elapsed since measurement was (re-)started within the last 900 minutes,
-- the beginning of the current measurement period. in which case the value will be the number of complete 15
-- If, for some reason, such as an adjustment in the minute intervals for which the agent has at least some
-- system's time-of-day clock, the current interval data. In certain cases (e.g., in the case where the agent
-- exceeds the maximum value, the agent will return is a proxy) it is possible that some intervals are
-- the maximum value." unavailable. In this case, this interval is the maximum
-- ::= { xxx } interval number for which data is available."
SYNTAX INTEGER (0..96)
-- xyzValidIntervals OBJECT-TYPE HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION
-- SYNTAX INTEGER (0..<n>) STATUS current
-- MAX-ACCESS read-only DESCRIPTION
-- STATUS current "The number of previous intervals for which no data is
-- DESCRIPTION available. This object will typically be zero except in
-- "The number of previous near end intervals cases where the data for some intervals are not available
-- for which data was collected. (e.g., in proxy situations)."
-- [ The overall constraint on <n> is 1 =< n =< 96; ] SYNTAX INTEGER (0..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 HCPerfTimeElapsed ::= TEXTUAL-CONVENTION
-- SYNTAX INTEGER (0..<n>) STATUS current
-- MAX-ACCESS read-only DESCRIPTION
-- STATUS current "The number of seconds that have elapsed since the beginning
-- DESCRIPTION of the current measurement period. If, for some reason, such
-- "The number of intervals in the range from as an adjustment in the system's time-of-day clock or the
-- 0 to xyzValidIntervals for which no addition of a leap second, the current interval exceeds the
-- data is available. This object will typically maximum value, the agent will return the maximum value.
-- be zero except in cases where the data for some
-- intervals are not available (e.g., in proxy
-- situations)."
-- ::= { xxx }
-- See the notes in [RFC2493] for additional information For 15 minute intervals, the range is limited to (0..899).
-- concerning the above objects. For 24 hour intervals, the range is limited to (0..86399)."
SYNTAX Unsigned32 (0..86399)
HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention defines a range of values that may be set
in a fault threshold alarm control. As the number of seconds
in a 15-minute interval numbers at most 900, objects of this
type may have a range of 0...900, where the value of 0 disables
the alarm."
SYNTAX Unsigned32 (0..900)
HCPerfCurrentCount ::= TEXTUAL-CONVENTION HCPerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with a performance measurement in a "A counter associated with a performance measurement in a
current 15 minute measurement interval. The value of this current 15 minute measurement interval. The value of this
counter starts from zero and is increased when associated counter starts from zero and is increased when associated
events occur, until the end of the 15 minute interval. events occur, until the end of the 15 minute interval.
At that time the value of the counter is stored in the At that time the value of the counter is stored in the
first 15 minute history interval, and the CurrentCount is first 15 minute history interval, and the CurrentCount is
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/