draft-ietf-frnetmib-frmrelay-service-05.txt   draft-ietf-frnetmib-frmrelay-service-06.txt 
Definitions of Managed Objects Definitions of Managed Objects
for Frame Relay Service Level Definitions for Frame Relay Service Level Definitions
June 18, 2001 September 25, 2001
draft-ietf-frnetmib-frmrelay-service-05.txt draft-ietf-frnetmib-frmrelay-service-06.txt
Robert A. Steinberger Robert A. Steinberger
Paradyne Networks Paradyne Networks
robert.steinberger@fnc.fujitsu.com robert.steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D Orly Nicklass, Ph.D
RAD Data Communications Ltd. RAD Data Communications Ltd.
Orly_n@rad.co.il Orly_n@rad.co.il
Status of this Memo Status of this Memo
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Abstract Abstract
This memo defines an extension of the Management Information Base This memo defines an extension of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based (MIB) for use with network management protocols in TCP/IP-based
internets. In particular, it defines objects for managing the Frame internets. In particular, it defines objects for managing the Frame
Relay Service Level Definitions. Relay Service Level Definitions.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Table of Contents Table of Contents
1. The SNMP Management Framework ............................... 3 1. The SNMP Management Framework ............................... 3
2. Conventions ................................................. 4 2. Conventions ................................................. 4
3. Overview .................................................... 4 3. Overview .................................................... 4
3.1. Frame Relay Service Level Definitions ..................... 4 3.1. Frame Relay Service Level Definitions ..................... 4
3.2. Terminology ............................................... 5 3.2. Terminology ............................................... 5
3.3. Network Model ............................................. 5 3.3. Network Model ............................................. 5
3.4. Reference Points .......................................... 6 3.4. Reference Points .......................................... 6
skipping to change at page 2, line 46 skipping to change at page 2, line 46
3.6.11. Service Availability ................................... 21 3.6.11. Service Availability ................................... 21
4. Relation to Other MIB Modules ............................... 22 4. Relation to Other MIB Modules ............................... 22
5. Structure of the MIB Module ................................. 23 5. Structure of the MIB Module ................................. 23
5.1. frsldPvcCtrlTable ......................................... 23 5.1. frsldPvcCtrlTable ......................................... 23
5.2. frsldSmplCtrlTable ........................................ 24 5.2. frsldSmplCtrlTable ........................................ 24
5.3. frsldPvcDataTable ......................................... 24 5.3. frsldPvcDataTable ......................................... 24
5.4. frsldPvcSampleTable ....................................... 24 5.4. frsldPvcSampleTable ....................................... 24
5.5. frsldCapabilities ......................................... 24 5.5. frsldCapabilities ......................................... 24
6. Persistence of Data ......................................... 24 6. Persistence of Data ......................................... 24
7. Object Definitions .......................................... 24 7. Object Definitions .......................................... 24
8. Acknowledgments ............................................. 59 8. Acknowledgments ............................................. 61
9. References .................................................. 60 9. References .................................................. 62
10. Security Considerations .................................... 63 10. Security Considerations .................................... 65
11. Authors' Addresses ......................................... 63 11. Authors' Addresses ......................................... 65
12. Copyright Section .......................................... 64 12. Copyright Section .......................................... 66
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 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 4, line 10 skipping to change at page 4, line 10
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Conventions 2. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in they appear in this document, are to be interpreted as described in
RFC 2119 [23]. RFC 2119 [22].
3. Overview 3. Overview
This MIB module addresses the items required to manage the Frame This MIB module addresses the items required to manage the Frame
Relay Forum's Implementation Agreement for Service Level Definitions Relay Forum's Implementation Agreement for Service Level Definitions
(FRF.13 [17]). At present, this applies to these values of the (FRF.13 [17]). At present, this applies to these values of the
ifType variable in the Internet-standard MIB: ifType variable in the Internet-standard MIB:
o frameRelay (32) o frameRelay (32)
skipping to change at page 22, line 32 skipping to change at page 22, line 32
Unavailables Unavailables
4. Relation to Other MIB Modules 4. Relation to Other MIB Modules
There is no explicit relation to any other frame relay MIB module nor There is no explicit relation to any other frame relay MIB module nor
are any required to implement this MIB module. However, there is a are any required to implement this MIB module. However, there is a
need for knowledge of ifIndexes and some understanding of DLCIs. The need for knowledge of ifIndexes and some understanding of DLCIs. The
ifIndex information can be found in the IF-MIB [21] which is ifIndex information can be found in the IF-MIB [21] which is
required. The DLCI information can be found in either the Frame Relay required. The DLCI information can be found in either the Frame Relay
DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC
1604) [18]; however, neither is required. 2954) [18]; however, neither is required.
Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to
active(1) the system can be in one of the following three states: active(1) the system can be in one of the following three states:
(1) The respective DLCI is known and is active. This corresponds to a (1) The respective DLCI is known and is active. This corresponds to a
state in which frPVCEndptRowStatus is active(1) and state in which frPVCEndptRowStatus is active(1) and
frPVCEndptRcvdSigStatus is either active(2) or none(4) for the frPVCEndptRcvdSigStatus is either active(2) or none(4) for the
Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame Frame Relay Network Services MIB (RFC 2954) [18]. For the Frame
Relay DTE MIB, the same state is shown by frCircuitRowStatus of Relay DTE MIB, the same state is shown by frCircuitRowStatus of
active(1) and frCircuitState of active(2). active(1) and frCircuitState of active(2).
(2) The respective DLCI has not been created. This corresponds to a (2) The respective DLCI has not been created. This corresponds to a
state in which the row with either frPVCEndptDLCIIndex or state in which the row with either frPVCEndptDLCIIndex or
frCircuitDlci equal to the respective DLCI does not exist in frCircuitDlci equal to the respective DLCI does not exist in
either the frPVCEndptTable or the frCircuitTable respectively. either the frPVCEndptTable or the frCircuitTable respectively.
(3) The respective DLCI has just been removed. This corresponds to a (3) The respective DLCI has just been removed. This corresponds to a
state in which either frPVCEndptRowStatus is no longer active(1) state in which either frPVCEndptRowStatus is no longer active(1)
or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for
the Frame Relay Network Services MIB (RFC 1604) [18]. For the the Frame Relay Network Services MIB (RFC 2954) [18]. For the
Frame Relay DTE MIB, the same state is shown when either Frame Relay DTE MIB, the same state is shown when either
frCircuitRowStatus is no longer active(1) or frCircuitState is no frCircuitRowStatus is no longer active(1) or frCircuitState is no
longer active(2). longer active(2).
For the first case, the row in the frsldPvcDataTable will be filled. For the first case, the row in the frsldPvcDataTable will be filled.
If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective
DLCI is also `active' the frsldPvcSampleTable will be filled as well. DLCI is also `active' the frsldPvcSampleTable will be filled as well.
For the second case, the respective rows will not be added to any of For the second case, the respective rows will not be added to any of
the data or sample tables and frsldPvcCtrlStatus SHOULD report the data or sample tables and frsldPvcCtrlStatus SHOULD report
skipping to change at page 24, line 49 skipping to change at page 24, line 49
FRSLD-MIB DEFINITIONS ::= BEGIN FRSLD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Gauge32, Integer32, Counter32, Gauge32, Integer32,
Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI
CounterBasedGauge64 FROM HCNUM-TC CounterBasedGauge64 FROM HCNUM-TC
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TimeStamp FROM SNMPv2-TC TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB; ifIndex FROM IF-MIB
DLCI FROM FRAME-RELAY-DTE-MIB;
frsldMIB MODULE-IDENTITY frsldMIB MODULE-IDENTITY
LAST-UPDATED "200106181500Z" -- June 18, 2001 LAST-UPDATED "200109251500Z" -- September 25, 2001
ORGANIZATION "IETF Frame Relay Service MIB Working Group" ORGANIZATION "IETF Frame Relay Service MIB Working Group"
CONTACT-INFO CONTACT-INFO
"IETF Frame Relay Service MIB (frnetmib) Working Group "IETF Frame Relay Service MIB (frnetmib) Working Group
WG Charter: http://www.ietf.org/html.charters/ WG Charter: http://www.ietf.org/html.charters/
frnetmib-charter.html frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
skipping to change at page 25, line 30 skipping to change at page 25, line 31
Paradyne Networks and Paradyne Networks and
Fujitsu Network Communications Fujitsu Network Communications
Email: robert.steinberger@fnc.fujitsu.com Email: robert.steinberger@fnc.fujitsu.com
Co-author: Orly Nicklass Co-author: Orly Nicklass
RAD Data Communications Ltd. RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il" EMail: Orly_n@rad.co.il"
DESCRIPTION DESCRIPTION
"The MIB module to describe generic objects for "The MIB module to describe generic objects for
FRF.13 Frame Relay Service Level Definitions." FRF.13 Frame Relay Service Level Definitions."
REVISION "200106181500Z" REVISION "200109251500Z" -- September 25, 2001
DESCRIPTION
"o Added text about persistence to RowStatus objects.
o Added text to description of frsldPvcDataMissed-
Polls.
o Changed badValue to inconsistentValue in
frsldMaxPvcCtrls and frsldMaxSmplCtrls."
REVISION "200105011500Z"
DESCRIPTION
"o Added FrsldTxRP and FrsldRxRP TCs for reference
points and changed frsldPvcCtrlTransmitRP and
frsldPvcCtrlReceiveRP to use new TCs.
o Added REFERENCE clauses.
o Added frsldMaxPvcCtrls, frsldNumPvcCtrls,
frsldMaxSmplCtrls and frsldNumSmplCtrls
for memory control.
o Made HC Data groups conditionally mandatory
based on the speed of the network interface.
o Updated description of the compliance objects.
o Updated the description of the groups to show
relationship."
REVISION "200009191500Z"
DESCRIPTION
"o Removed frsldPvcCtrlDelayCnt.
o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl-
AvailBuckets, and frsldSmplCtrlAvailBucketsGranted.
o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*.
o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax,
and frsldPvcDataDelayAvg.
o Changed frsldPvcDataSample* to frsldPvcSample*.
o Changed frsldPvcDataSmpl* to frsldPvcSmpl*.
o Added frsldPvcSmplUnavailableTime and frsldPvcSmpl-
Unavailables.
o Removed frsldPvcAvailSampleTable and all objects.
o Removed frsldPvcCtrlDelayCnt from frsldPvcCtrlWrite-
Caps.
o Adjusted group definitions for frsldPvcDelayCtrlGroup,
frsldPvc[Data]SampleCtrlGroup, frsldPvcReqDataGroup,
frsldPvcDelayDataGroup, and frsldPvc[Avail]SampleAvail-
Group to reflect above changes."
REVISION "200006141500Z"
DESCRIPTION
"o Removed all uses of FrsldLocation by removing objects
frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc
o Removed FrsldRP TC and distributed source and destina-
tion specific information into index for control table
as frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP.
o Added frsldPvcCtrlDelayCnt to control table.
o Changed frsldPvcDataUnavailableTime from TimeStamp to
TimeTicks.
o Updated text of RowStatus objects
o Added frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP
as indices to ALL tables.
o Added HC counters for all data delivery stats and
samples.
o Adjusted description of sample information for clarity.
o Adjusted names of sample objects for consistency.
o Added frsldRPCaps.
o Changed location to mib-2
o Reworked Group Definitions."
REVISION "200002061500Z"
DESCRIPTION
"o Published as draft-ietf-frnetmib-frmrelay-service-00.txt
o Added frsldCapabilities group to define the
read/write capabilities
o Changed location to experimental 104
o Changed name of frsldTables to frsldObjects
o Changed MAX-ACCESS of frsldPvcCtrlDelayType to
read-create
o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax,
and frsldPvcDataDelayAvg from the sample period"
REVISION "199909031500Z"
DESCRIPTION DESCRIPTION
"o Added range to frsldPvcCtrlPacketFreq "Initial version, published as RFC xxxx"
o Changed range of frsldPvcCtrlDelayTimeOut to match -- xxxx to be assigned by RFC Editor
that of frsldPvcCtrlPacketFreq
o Clarified what happens when frsldPvcCtrlPacketFreq
is set to zero
o Changed delay to count in microseconds instead of
milliseconds
o Created a new sample control table and moved sample
specific information into it.
o Changed the prefix of `frsldPvcCtrl' object name to
`frsldSmplCtrl'
o Added the sample control index to the indices of the
sample tables
o Changed all occasions of TimeTicks to TimeStamp
o Added frsldPvcCtrlPurge to aid in control validity
of information due to PVC status changes
o Added frsldPvcCtrlDeleteOnPurge object
o Added frsldPvcCtrlLastPurgeTime object
o Added units clauses to all time related fields.
o Reworded the `change in' syntax to be more explicit"
::= { mib-2 xxx } -- RFC editor - IANA assigns xxx ::= { mib-2 xxx } -- RFC editor - IANA assigns xxx
-- --
-- Textual Conventions -- Textual Conventions
-- --
FrsldTxRP ::= TEXTUAL-CONVENTION FrsldTxRP ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reference point a PVC uses for calculation "The reference point a PVC uses for calculation
of transmitter related statistics. of transmitter related statistics.
skipping to change at page 29, line 48 skipping to change at page 28, line 6
Definitions PVC control table." Definitions PVC control table."
INDEX { ifIndex, frsldPvcCtrlDlci, INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP}
::= { frsldPvcCtrlTable 1 } ::= { frsldPvcCtrlTable 1 }
FrsldPvcCtrlEntry ::= FrsldPvcCtrlEntry ::=
SEQUENCE { SEQUENCE {
-- --
-- Index Control Variables -- Index Control Variables
-- --
frsldPvcCtrlDlci Integer32, frsldPvcCtrlDlci DLCI,
frsldPvcCtrlTransmitRP FrsldTxRP, frsldPvcCtrlTransmitRP FrsldTxRP,
frsldPvcCtrlReceiveRP FrsldRxRP, frsldPvcCtrlReceiveRP FrsldRxRP,
frsldPvcCtrlStatus RowStatus, frsldPvcCtrlStatus RowStatus,
-- --
-- Service Level Definitions Setup Variables -- Service Level Definitions Setup Variables
-- --
frsldPvcCtrlPacketFreq Integer32, frsldPvcCtrlPacketFreq Integer32,
-- --
-- Delay Specific Setup Variables -- Delay Specific Setup Variables
-- --
skipping to change at page 30, line 23 skipping to change at page 28, line 29
frsldPvcCtrlDelayTimeOut Integer32, frsldPvcCtrlDelayTimeOut Integer32,
-- --
-- Data Persistence Control Variables -- Data Persistence Control Variables
-- --
frsldPvcCtrlPurge Integer32, frsldPvcCtrlPurge Integer32,
frsldPvcCtrlDeleteOnPurge INTEGER, frsldPvcCtrlDeleteOnPurge INTEGER,
frsldPvcCtrlLastPurgeTime TimeStamp frsldPvcCtrlLastPurgeTime TimeStamp
} }
frsldPvcCtrlDlci OBJECT-TYPE frsldPvcCtrlDlci OBJECT-TYPE
SYNTAX Integer32 (16..4194303) SYNTAX DLCI
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is equal to the DLCI "The value of this object is equal to the DLCI
value for this PVC." value for this PVC."
::= { frsldPvcCtrlEntry 1 } ::= { frsldPvcCtrlEntry 1 }
frsldPvcCtrlTransmitRP OBJECT-TYPE frsldPvcCtrlTransmitRP OBJECT-TYPE
SYNTAX FrsldTxRP SYNTAX FrsldTxRP
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 33, line 46 skipping to change at page 32, line 4
frsldPvcCtrlLastPurgeTime OBJECT-TYPE frsldPvcCtrlLastPurgeTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object returns the value of sysUpTime "This object returns the value of sysUpTime
at the time the information was last purged. at the time the information was last purged.
This value SHOULD be set to the sysUpTime This value SHOULD be set to the sysUpTime
upon setting frsldPvcCtrlStatus to active(1) upon setting frsldPvcCtrlStatus to active(1)
for the first time. If frsldPvcCtrlStatus has for the first time. Each time a
never been active(1), this object SHOULD return 0." discontinuity in the counters occurs, this
value MUST be set to the sysUpTime.
If frsldPvcCtrlStatus has never been active(1),
this object SHOULD return 0.
This object SHOULD be used as the discontinuity
timer for the counters in frsldPvcDataTable."
::= { frsldPvcCtrlEntry 11 } ::= { frsldPvcCtrlEntry 11 }
-- The Frame Relay Service Level Definitions Sampling Control -- The Frame Relay Service Level Definitions Sampling Control
-- Table -- Table
-- --
-- This table is used to define the sample control parameters -- This table is used to define the sample control parameters
-- of service level definitions on individual PVCs. -- of service level definitions on individual PVCs.
frsldSmplCtrlTable OBJECT-TYPE frsldSmplCtrlTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldSmplCtrlEntry SYNTAX SEQUENCE OF FrsldSmplCtrlEntry
skipping to change at page 37, line 47 skipping to change at page 36, line 13
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of polls that have been determined "The total number of polls that have been determined
to be missed. These polls are typically associated to be missed. These polls are typically associated
with the calculation of delay but may also be with the calculation of delay but may also be
used for the calculation of other statistics. If an used for the calculation of other statistics. If an
anticipated poll is not received in a reasonable anticipated poll is not received in a reasonable
amount of time, it should be counted as missed. amount of time, it should be counted as missed.
The value used to determine the reasonable amount The value used to determine the reasonable amount
of time is contained in frsldPvcCtrlDelayTimeOut." of time is contained in frsldPvcCtrlDelayTimeOut.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
::= { frsldPvcDataEntry 1 } ::= { frsldPvcDataEntry 1 }
frsldPvcDataFrDeliveredC OBJECT-TYPE frsldPvcDataFrDeliveredC OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR." sent within CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)" "FRF.13: Section 4.1 (FramesDeliveredc)"
::= { frsldPvcDataEntry 2 } ::= { frsldPvcDataEntry 2 }
frsldPvcDataFrDeliveredE OBJECT-TYPE frsldPvcDataFrDeliveredE OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR." sent in excess of the CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliverede)" "FRF.13: Section 4.1 (FramesDeliverede)"
::= { frsldPvcDataEntry 3 } ::= { frsldPvcDataEntry 3 }
frsldPvcDataFrOfferedC OBJECT-TYPE frsldPvcDataFrOfferedC OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR." frsldPvcCtrlTransmitRP within CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)" "FRF.13: Section 4.1 (FramesOfferedc)"
::= { frsldPvcDataEntry 4 } ::= { frsldPvcDataEntry 4 }
frsldPvcDataFrOfferedE OBJECT-TYPE frsldPvcDataFrOfferedE OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR." frsldPvcCtrlTransmitRP in excess of the CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)" "FRF.13: Section 4.1 (FramesOfferede)"
::= { frsldPvcDataEntry 5 } ::= { frsldPvcDataEntry 5 }
frsldPvcDataDataDeliveredC OBJECT-TYPE frsldPvcDataDataDeliveredC OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR." sent within CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)" "FRF.13: Section 5.1 (DataDeliveredc)"
::= { frsldPvcDataEntry 6 } ::= { frsldPvcDataEntry 6 }
frsldPvcDataDataDeliveredE OBJECT-TYPE frsldPvcDataDataDeliveredE OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR." sent in excess of the CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)" "FRF.13: Section 5.1 (DataDeliverede)"
::= { frsldPvcDataEntry 7 } ::= { frsldPvcDataEntry 7 }
frsldPvcDataDataOfferedC OBJECT-TYPE frsldPvcDataDataOfferedC OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR." frsldPvcCtrlTransmitRP within CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)" "FRF.13: Section 5.1 (DataOfferedc)"
::= { frsldPvcDataEntry 8 } ::= { frsldPvcDataEntry 8 }
frsldPvcDataDataOfferedE OBJECT-TYPE frsldPvcDataDataOfferedE OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR." frsldPvcCtrlTransmitRP in excess of the CIR.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferede)" "FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcDataEntry 9 } ::= { frsldPvcDataEntry 9 }
frsldPvcDataHCFrDeliveredC OBJECT-TYPE frsldPvcDataHCFrDeliveredC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version sent within CIR. This object is a 64-bit version
of frsldPvcDataFrDeliveredC." of frsldPvcDataFrDeliveredC.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)" "FRF.13: Section 4.1 (FramesDeliveredc)"
::= { frsldPvcDataEntry 10 } ::= { frsldPvcDataEntry 10 }
frsldPvcDataHCFrDeliveredE OBJECT-TYPE frsldPvcDataHCFrDeliveredE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR. This object is a 64-bit sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataFrDeliveredE." version of frsldPvcDataFrDeliveredE.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliverede)" "FRF.13: Section 4.1 (FramesDeliverede)"
::= { frsldPvcDataEntry 11 } ::= { frsldPvcDataEntry 11 }
frsldPvcDataHCFrOfferedC OBJECT-TYPE frsldPvcDataHCFrOfferedC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataFrOfferedC." a 64-bit version of frsldPvcDataFrOfferedC.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)" "FRF.13: Section 4.1 (FramesOfferedc)"
::= { frsldPvcDataEntry 12 } ::= { frsldPvcDataEntry 12 }
frsldPvcDataHCFrOfferedE OBJECT-TYPE frsldPvcDataHCFrOfferedE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR. This frsldPvcCtrlTransmitRP in excess of the CIR. This
object is a 64-bit version of frsldPvcDataFrOfferedE." object is a 64-bit version of frsldPvcDataFrOfferedE.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)" "FRF.13: Section 4.1 (FramesOfferede)"
::= { frsldPvcDataEntry 13 } ::= { frsldPvcDataEntry 13 }
frsldPvcDataHCDataDeliveredC OBJECT-TYPE frsldPvcDataHCDataDeliveredC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version of sent within CIR. This object is a 64-bit version of
frsldPvcDataDataDeliveredC." frsldPvcDataDataDeliveredC.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)" "FRF.13: Section 5.1 (DataDeliveredc)"
::= { frsldPvcDataEntry 14 } ::= { frsldPvcDataEntry 14 }
frsldPvcDataHCDataDeliveredE OBJECT-TYPE frsldPvcDataHCDataDeliveredE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR. This object is a 64-bit sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataDataDeliveredE." version of frsldPvcDataDataDeliveredE.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)" "FRF.13: Section 5.1 (DataDeliverede)"
::= { frsldPvcDataEntry 15 } ::= { frsldPvcDataEntry 15 }
frsldPvcDataHCDataOfferedC OBJECT-TYPE frsldPvcDataHCDataOfferedC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataDataOfferedC." a 64-bit version of frsldPvcDataDataOfferedC.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)" "FRF.13: Section 5.1 (DataOfferedc)"
::= { frsldPvcDataEntry 16 } ::= { frsldPvcDataEntry 16 }
frsldPvcDataHCDataOfferedE OBJECT-TYPE frsldPvcDataHCDataOfferedE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR. frsldPvcCtrlTransmitRP in excess of the CIR.
This object is a 64-bit version of This object is a 64-bit version of
frsldPvcDataDataOfferedE." frsldPvcDataDataOfferedE.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferede)" "FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcDataEntry 17 } ::= { frsldPvcDataEntry 17 }
frsldPvcDataUnavailableTime OBJECT-TYPE frsldPvcDataUnavailableTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time this PVC was declared unavailable "The amount of time this PVC was declared unavailable
skipping to change at page 42, line 20 skipping to change at page 42, line 23
REFERENCE REFERENCE
"FRF.13: Section 6.1 (OutageTime)" "FRF.13: Section 6.1 (OutageTime)"
::= { frsldPvcDataEntry 18 } ::= { frsldPvcDataEntry 18 }
frsldPvcDataUnavailables OBJECT-TYPE frsldPvcDataUnavailables OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times this PVC was declared unavailable "The number of times this PVC was declared unavailable
for any reason since this row was created." for any reason since this row was created.
Discontinuities in the value of this counter can
occur at re-initialization of the management system
and at other times as indicated by
frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 6.1 (OutageCount)" "FRF.13: Section 6.1 (OutageCount)"
::= { frsldPvcDataEntry 19 } ::= { frsldPvcDataEntry 19 }
-- The Frame Relay Service Level Definitions PVC Sample Table -- The Frame Relay Service Level Definitions PVC Sample Table
-- --
-- This table contains the sampled delay, delivery and -- This table contains the sampled delay, delivery and
-- availability information. -- availability information.
frsldPvcSampleTable OBJECT-TYPE frsldPvcSampleTable OBJECT-TYPE
skipping to change at page 45, line 7 skipping to change at page 45, line 15
this interval." this interval."
::= { frsldPvcSampleEntry 5 } ::= { frsldPvcSampleEntry 5 }
frsldPvcSmplFrDeliveredC OBJECT-TYPE frsldPvcSmplFrDeliveredC OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval." sent within CIR during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCFrDeliveredC."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)" "FRF.13: Section 4.1 (FramesDeliveredc)"
::= { frsldPvcSampleEntry 6 } ::= { frsldPvcSampleEntry 6 }
frsldPvcSmplFrDeliveredE OBJECT-TYPE frsldPvcSmplFrDeliveredE OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR during this interval." sent in excess of the CIR during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCFrDeliveredE."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliverede))" "FRF.13: Section 4.1 (FramesDeliverede))"
::= { frsldPvcSampleEntry 7 } ::= { frsldPvcSampleEntry 7 }
frsldPvcSmplFrOfferedC OBJECT-TYPE frsldPvcSmplFrOfferedC OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR during this frsldPvcCtrlTransmitRP within CIR during this
interval." interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCFrOfferedC."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)" "FRF.13: Section 4.1 (FramesOfferedc)"
::= { frsldPvcSampleEntry 8 } ::= { frsldPvcSampleEntry 8 }
frsldPvcSmplFrOfferedE OBJECT-TYPE frsldPvcSmplFrOfferedE OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR frsldPvcCtrlTransmitRP in excess of the CIR
during this interval." during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCFrOfferedE."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)" "FRF.13: Section 4.1 (FramesOfferede)"
::= { frsldPvcSampleEntry 9 } ::= { frsldPvcSampleEntry 9 }
frsldPvcSmplDataDeliveredC OBJECT-TYPE frsldPvcSmplDataDeliveredC OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval." sent within CIR during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCDataDeliveredC."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)" "FRF.13: Section 5.1 (DataDeliveredc)"
::= { frsldPvcSampleEntry 10 } ::= { frsldPvcSampleEntry 10 }
frsldPvcSmplDataDeliveredE OBJECT-TYPE frsldPvcSmplDataDeliveredE OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlDeliveredRP and determined to have been frsldPvcCtrlDeliveredRP and determined to have been
sent in excess of the CIR during this interval." sent in excess of the CIR during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCDataDeliveredE."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)" "FRF.13: Section 5.1 (DataDeliverede)"
::= { frsldPvcSampleEntry 11 } ::= { frsldPvcSampleEntry 11 }
frsldPvcSmplDataOfferedC OBJECT-TYPE frsldPvcSmplDataOfferedC OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR during this frsldPvcCtrlTransmitRP within CIR during this
interval." interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCDataOfferredC."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)" "FRF.13: Section 5.1 (DataOfferedc)"
::= { frsldPvcSampleEntry 12 } ::= { frsldPvcSampleEntry 12 }
frsldPvcSmplDataOfferedE OBJECT-TYPE frsldPvcSmplDataOfferedE OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR frsldPvcCtrlTransmitRP in excess of the CIR
during this interval." during this interval.
If it is the case that the high capacity counters
are also used, this MUST report the value of the
lower 32 bits of the CounterBasedGauge64 value of
frsldPvcSmplHCDataOfferedE."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferede)" "FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcSampleEntry 13 } ::= { frsldPvcSampleEntry 13 }
frsldPvcSmplHCFrDeliveredC OBJECT-TYPE frsldPvcSmplHCFrDeliveredC OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
skipping to change at page 52, line 32 skipping to change at page 53, line 32
frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 }
frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
frsldCompliance MODULE-COMPLIANCE frsldCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv2 entities "The compliance statement for SNMP entities
which support with Frame Relay Service Level which support with Frame Relay Service Level
Definitions. This group defines the minimum Definitions. This group defines the minimum
level of support required for compliance." level of support required for compliance."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { frsldPvcReqCtrlGroup, MANDATORY-GROUPS { frsldPvcReqCtrlGroup,
frsldPvcReqDataGroup, frsldPvcReqDataGroup,
frsldCapabilitiesGroup} frsldCapabilitiesGroup}
GROUP frsldPvcHCFrameDataGroup GROUP frsldPvcHCFrameDataGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network "This group is mandatory only for those network
interfaces with corresponding instance of ifSpeed interfaces with corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP frsldPvcHCOctetDataGroup GROUP frsldPvcHCOctetDataGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network "This group is mandatory only for those network
interfaces with corresponding instance of ifSpeed interfaces with corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP frsldPvcPacketGroup
DESCRIPTION
"This group is optional. Network interfaces that
allow control of the packets used to collect
information are encouraged to implement this
group."
GROUP frsldPvcDelayCtrlGroup
DESCRIPTION
"This group is optional. Network interfaces that
offer control of the delay measurement are
strongly encouraged to implement this group."
GROUP frsldPvcSampleCtrlGroup
DESCRIPTION
"This group is mandatory only for those network
interfaces that allow data sampling."
GROUP frsldPvcDelayDataGroup
DESCRIPTION
"This group is only mandatory when
frsldPvcDelayCtrlGroup is implemented. It is
strongly encouraged that any device capable
of measuring delay implement this group."
GROUP frsldPvcSampleDelayGroup
DESCRIPTION
"This group is only mandatory when both
frsldPvcSampleCtrlGroup and frsldPvcDelayDataGroup
are supported."
GROUP frsldPvcSampleDataGroup
DESCRIPTION
"This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported."
GROUP frsldPvcSampleHCFrameGroup
DESCRIPTION
"This group is mandatory whenever both
frsldPvcSampleCtrlGroup and frsldPvcHCFrameDataGroup
are supported."
GROUP frsldPvcSampleHCDataGroup
DESCRIPTION
"This group is mandatory whenever both
frsldPvcSampleCtrlGroup and frsldPvcHCOctetDataGroup
are supported."
GROUP frsldPvcSampleAvailGroup
DESCRIPTION
"This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported."
GROUP frsldPvcSampleGeneralGroup
DESCRIPTION
"This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported."
OBJECT frsldPvcCtrlStatus OBJECT frsldPvcCtrlStatus
SYNTAX INTEGER { active(1) } -- subset of RowStatus SYNTAX INTEGER { active(1) } -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Row creation can be done outside of the scope of "Row creation can be done outside of the scope of
the SNMP protocol. If this object is implemented the SNMP protocol. If this object is implemented
with max-access of read-only, then the only value with max-access of read-only, then the only value
that MUST be returned is active(1) and that MUST be returned is active(1) and
frsldPvcCtrlWriteCaps MUST return 0 for the frsldPvcCtrlWriteCaps MUST return 0 for the
frsldPvcCtrlStatus(0) bit." frsldPvcCtrlStatus(0) bit."
skipping to change at page 61, line 33 skipping to change at page 63, line 33
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc.,
[16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to [16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to
Version 3 of the Internet-standard Network Management Framework", Version 3 of the Internet-standard Network Management Framework",
RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc.,
[17]Frame Relay Forum Technical Committee, "Service Level Definitions [17]Frame Relay Forum Technical Committee, "Service Level Definitions
Implementations Agreement", FRF.13, August 1998. Implementations Agreement", FRF.13, August 1998.
[18]Brown, T., "Definitions of Managed Objects for Frame Relay Service", [18]Rehbehn, K., Fowler, D., "Definitions of Managed Objects for Frame
RFC 1604, Bell Communications Research, March 1994. Relay Service", RFC 2954, Megisto Systems, Syndesis Limited, October
2000.
[19]Waldbusser, S., "Remote Network Monitoring Management Information [19]Waldbusser, S., "Remote Network Monitoring Management Information
Base Version 2 using SMIv2", RFC 2021, International Network Base Version 2 using SMIv2", RFC 2021, International Network
Service, January 1997. Service, January 1997.
[20]Brown, C., Baker, F., "Management Information Base for Frame Relay [20]Brown, C., Baker, F., "Management Information Base for Frame Relay
DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems,
September 1997. September 1997.
[21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC [21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC
2863, Cisco Systems, Argon Networks, June 2000. 2863, Cisco Systems, Argon Networks, June 2000.
[22]Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, Harvard University, March 1997.
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
 End of changes. 45 change blocks. 
142 lines changed or deleted 249 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/