draft-ietf-frnetmib-frmrelay-service-03.txt   draft-ietf-frnetmib-frmrelay-service-04.txt 
Definitions of Managed Objects Definitions of Managed Objects
for Frame Relay Service Level Definitions for Frame Relay Service Level Definitions
December 19, 2000 May 1, 2001
draft-ietf-frnetmib-frmrelay-service-03.txt draft-ietf-frnetmib-frmrelay-service-04.txt
Robert A. Steinberger Robert A. Steinberger
Paradyne Networks Paradyne Networks
rsteinberger@paradyne.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
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 working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
skipping to change at page 1, line 42 skipping to change at page 1, line 42
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
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. This memo does not specify a Relay Service Level Definitions.
standard for the Internet community.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
3.5. Measurement Methodology ................................... 8 3.5. Measurement Methodology ................................... 8
3.6. Theory of Operation ....................................... 9 3.6. Theory of Operation ....................................... 9
3.6.1. Capabilities Discovery .................................. 9 3.6.1. Capabilities Discovery .................................. 9
3.6.2. Determining Reference Points for Row Creation ........... 9 3.6.2. Determining Reference Points for Row Creation ........... 10
3.6.2.1. Graphical Examples of Reference Points ................ 11 3.6.2.1. Graphical Examples of Reference Points ................ 11
3.6.2.1.1. Edge-to-Edge Interface Reference Point Example ...... 12 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example ...... 12
3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example ... 13 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example ... 13
3.6.2.1.3. End-to-End Using Reference Point Example ............ 14 3.6.2.1.3. End-to-End Using Reference Point Example ............ 14
3.6.3. Creation Process ........................................ 15 3.6.3. Creation Process ........................................ 15
3.6.4. Destruction Process ..................................... 15 3.6.4. Destruction Process ..................................... 15
3.6.4.1. Manual Row Destruction ................................ 15 3.6.4.1. Manual Row Destruction ................................ 16
3.6.4.2. Automatic Row Destruction ............................. 16 3.6.4.2. Automatic Row Destruction ............................. 16
3.6.5. Modification Process .................................... 16 3.6.5. Modification Process .................................... 16
3.6.6. Collection Process ...................................... 16 3.6.6. Collection Process ...................................... 16
3.6.6.1. Remote Polling ........................................ 16 3.6.6.1. Remote Polling ........................................ 16
3.6.6.2. Sampling .............................................. 17 3.6.6.2. Sampling .............................................. 17
3.6.6.3. User History .......................................... 17 3.6.6.3. User History .......................................... 18
3.6.7. Use of MIB in Calculation of Service Level Definitions .. 18 3.6.7. Use of MIB Module in Calculation of Service Level
Definitions .................................................... 18
3.6.8. Delay ................................................... 20 3.6.8. Delay ................................................... 20
3.6.9. Frame Delivery Ratio .................................... 20 3.6.9. Frame Delivery Ratio .................................... 20
3.6.10. Data Delivery Ratio .................................... 21 3.6.10. Data Delivery Ratio .................................... 21
3.6.11. Service Availability ................................... 21 3.6.11. Service Availability ................................... 21
4. Relation to Other MIBs ...................................... 22 4. Relation to Other MIB Modules ............................... 22
5. Structure of the MIB ........................................ 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. Object Definitions .......................................... 24 6. Object Definitions .......................................... 24
7. Acknowledgments ............................................. 53 7. Acknowledgments ............................................. 58
8. References .................................................. 54 8. References .................................................. 59
9. Security Considerations ..................................... 56 9. Security Considerations ..................................... 62
10. Authors' Addresses ......................................... 56 10. Authors' Addresses ......................................... 62
11. Copyright Section .......................................... 57 11. Copyright Section .......................................... 63
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 14 skipping to change at page 4, line 14
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 [23].
3. Overview 3. Overview
This MIB addresses the items required to manage the Frame Relay This MIB module addresses the items required to manage the Frame
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)
o frameRelayService (44) o frameRelayService (44)
This section provides an overview and background of how to use this This section provides an overview and background of how to use this
MIB. MIB module.
3.1. Frame Relay Service Level Definitions 3.1. Frame Relay Service Level Definitions
The frame relay service level definitions address specific The frame relay service level definitions address specific
characteristics of a frame relay service that can be used to characteristics of a frame relay service that can be used to
facilitate the following tasks: facilitate the following tasks:
o Evaluation of frame relay service providers, offerings or o Evaluation of frame relay service providers, offerings or
products. products.
skipping to change at page 5, line 18 skipping to change at page 5, line 18
ratio can be further divided by inspecting either only the data ratio can be further divided by inspecting either only the data
within the CIR or only the data in excess of the CIR. within the CIR or only the data in excess of the CIR.
o Service Availability - The amount of time the frame relay service o Service Availability - The amount of time the frame relay service
was not available. There are three types of availability was not available. There are three types of availability
statistics defined in FRF.13 [17]: Mean Time to Repair, Virtual statistics defined in FRF.13 [17]: Mean Time to Repair, Virtual
Connection Availability, and Mean Time Between Service Outages. Connection Availability, and Mean Time Between Service Outages.
The later two require information about the scheduled outage time. The later two require information about the scheduled outage time.
It is assumed that scheduled outage time information will be It is assumed that scheduled outage time information will be
maintained by the network management software, so it is not maintained by the network management software, so it is not
included in the MIB. included in the MIB module.
Consult FRF.13 [17] for more details. Consult FRF.13 [17] for more details.
3.2. Terminology 3.2. Terminology
o CIR - The Committed Information Rate (CIR) is the subscriber data o CIR - The Committed Information Rate (CIR) is the subscriber data
rate (expressed in bits/second) that the network commits to rate (expressed in bits/second) that the network commits to
deliver under normal network conditions. [18] deliver under normal network conditions. [18]
o DLCI - Data Link Connection Identifier. [18] o DLCI - Data Link Connection Identifier. [18]
skipping to change at page 6, line 30 skipping to change at page 6, line 30
Figure 1 Figure 1
Frame Relay Network Reference Model Frame Relay Network Reference Model
3.4. Reference Points 3.4. Reference Points
The collection and calculations of the service level definitions The collection and calculations of the service level definitions
apply to two reference points within the network. These two points apply to two reference points within the network. These two points
are the locations where the frames are referenced in the collection are the locations where the frames are referenced in the collection
of the service level specific information. The reference points used of the service level specific information. The reference points used
in the MIB are shown in figure 2 below. For completeness, the MIB in the MIB module are shown in figure 2 below. For completeness, the
also allows for proprietary reference points which MAY exist anywhere module also allows for proprietary reference points which MAY exist
in the network that is not a previously defined reference point. The anywhere in the network that is not a previously defined reference
meaning of the proprietary reference points is insignificant unless point. The meaning of the proprietary reference points is
defined by the device manufacturer. insignificant unless defined by the device manufacturer.
+---------------------------+ +---------------------------+
|+-----------+ +-----------+| |+-----------+ +-----------+|
|| | |Measurement|| || | |Measurement||
||Frame Relay---Engine --(Source RP)----+ ||Frame Relay---Engine --(Source RP)----+
||DTE | |(If Exists)|| | ||DTE | |(If Exists)|| |
|+-----------+ +-----------+| | |+-----------+ +-----------+| |
+---------------------------+ | +---------------------------+ |
Frame Relay Source | Frame Relay Source |
+------------------------------------------+ +------------------------------------------+
skipping to change at page 8, line 8 skipping to change at page 8, line 8
||DTE | |(If Exists)|| ||DTE | |(If Exists)||
|+-----------+ +-----------+| |+-----------+ +-----------+|
+---------------------------+ +---------------------------+
Figure 2 Figure 2
Reference Points (FRF.13 [17]) Reference Points (FRF.13 [17])
The MIB variables frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP The MIB variables frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP
allow the user to view and configure the reference points at which allow the user to view and configure the reference points at which
the calculations occur. These variables are specific to the device the calculations occur. These variables are specific to the device
on which they are located. Frame relay devices act as both frame on which they are located. Frame relay devices act as both frame
sources and frame destinations. The definitions in this MIB apply to sources and frame destinations. The definitions in this MIB module
the interaction of a pair of devices on the network path. The same apply to the interaction of a pair of devices on the network path.
device can potentially use different reference points for calculation The same device can potentially use different reference points for
and collection of the statistics based on whether the referenced calculation and collection of the statistics based on whether the
frame is sent or received by the device. When the device is acting as referenced frame is sent or received by the device. When the device
a frame source, the value of frsldPvcCtrlTransmitRP reflects the is acting as a frame source, the value of frsldPvcCtrlTransmitRP
reference point used for all source calculations pertaining to the reflects the reference point used for all source calculations
specified PVC. When the device is acting as a frame destination, the pertaining to the specified PVC. When the device is acting as a frame
value of frsldPvcCtrlReceiveRP reflects the reference point used for destination, the value of frsldPvcCtrlReceiveRP reflects the
all destination calculations pertaining to the specified PVC. reference point used for all destination calculations pertaining to
the specified PVC.
For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue
measurement domain as a domain in which measurement is performed measurement domain as a domain in which measurement is performed
between an Ingress Reference Point and an Egress Queue Input between an Ingress Reference Point and an Egress Queue Input
Reference Point. For this domain between a source device and a Reference Point. For this domain between a source device and a
destination device, the value of frsldPvcCtrlTransmitRP for the destination device, the value of frsldPvcCtrlTransmitRP for the
source device would be set to ingTxLocalRP(2) and the value of source device would be set to ingTxLocalRP(2) and the value of
frsldPvcCtrlReceiveRP for the destination device would be set to frsldPvcCtrlReceiveRP for the destination device would be set to
eqiRxLocalRP(4). While it is usually the case that the reference eqiRxLocalRP(4). While it is usually the case that the reference
points would be equivalent on the remote device when monitoring points would be equivalent on the remote device when monitoring
skipping to change at page 9, line 7 skipping to change at page 9, line 8
This document neither recommends nor suggests a method of This document neither recommends nor suggests a method of
implementation. This is left to the device manufacturer and should be implementation. This is left to the device manufacturer and should be
independent of the data that is actually collected. independent of the data that is actually collected.
Periodic collection of this data can be performed through either Periodic collection of this data can be performed through either
polling of the data table, use of the sample tables or use of the polling of the data table, use of the sample tables or use of the
user history group of RFC 2021 [19]. user history group of RFC 2021 [19].
3.6. Theory of Operation 3.6. Theory of Operation
The following sections describe how to use this MIB. They include The following sections describe how to use this MIB module. They
row handling, data collection and data calculation. The include row handling, data collection and data calculation. The
recommendations here in are suggestions as to implementation and do recommendations here in are suggestions as to implementation and do
not infer that they are the only method that can be used to perform not infer that they are the only method that can be used to perform
such operations. such operations.
3.6.1. Capabilities Discovery 3.6.1. Capabilities Discovery
Three objects are provided to aid the network manager in discovering Three objects are provided specifically to aid the network manager in
the capabilities of the device with respect to this MIB. discovering the capabilities of the device with respect to this MIB
module.
o frsldPvcCtrlWriteCaps This object reports the write capabilities o frsldPvcCtrlWriteCaps This object reports the write capabilities
of the PVC Control Table. Use this object of the PVC Control Table. Use this object
to determine which objects can be modified. to determine which objects can be modified.
This need only be referenced if row This need only be referenced if row
creation or modification is to be creation or modification is to be
performed. performed.
o frsldSmplCtrlWriteCaps This object reports the write capabilities o frsldSmplCtrlWriteCaps This object reports the write capabilities
of the Sample Control Table. Use this of the Sample Control Table. Use this
skipping to change at page 9, line 42 skipping to change at page 9, line 44
o frsldRPCaps This object reports the reference points at o frsldRPCaps This object reports the reference points at
which the device is capable of collecting which the device is capable of collecting
information. This object needs to be information. This object needs to be
referenced if row creation is to be referenced if row creation is to be
performed in the PVC Control Table. performed in the PVC Control Table.
Devices can only create rows containing Devices can only create rows containing
supported reference points. supported reference points.
These objects do not imply that there is no need for an Agent These objects do not imply that there is no need for an Agent
Capabilities macro for devices that do not fully support every object Capabilities macro for devices that do not fully support every object
in this MIB. They are provided specifically to aid in the ensured in this MIB module. They are provided specifically to aid in the
network management operations of this MIB with respect to row ensured network management operations of this MIB module with respect
creation and modification. to row creation and modification.
An additional four objects are provided to report and control memory
the utilization of this MIB module. These objects are
frsldMaxPvcCtrls, frsldNumPvcCtrls, frsldMaxSmplCtrls are
frsldNumSmplCtrls. Together, they allow a manager to control the
amount of memory allocated for specific utilization by this MIB
module. This is done by setting the maximum allowed allocation of
controls.
3.6.2. Determining Reference Points for Row Creation 3.6.2. Determining Reference Points for Row Creation
The performance of a PVC is monitored by evaluating the uni- The performance of a PVC is monitored by evaluating the uni-
directional flow of frames from an ingress point to an egress point. directional flow of frames from an ingress point to an egress point.
Reference points describe where each of the two measurements are Reference points describe where each of the two measurements are
made. Monitoring both of the uni-directional flows that make-up the made. Monitoring both of the uni-directional flows that make-up the
PVC frame traffic requires a total of four reference points as shown PVC frame traffic requires a total of four reference points as shown
in Figures 3 through 5. A monitoring point that evaluates traffic is in Figures 3 through 5. A monitoring point that evaluates traffic is
restricted to counting frames that pass the reference points hosted restricted to counting frames that pass the reference points hosted
skipping to change at page 16, line 28 skipping to change at page 16, line 35
there may be some need to keep the historic information active for a there may be some need to keep the historic information active for a
short period after the destruction or removal of a DLCI. If the short period after the destruction or removal of a DLCI. If the
basis for the row no longer exists, the row will be destroyed at the basis for the row no longer exists, the row will be destroyed at the
end of the purge interval that is controlled by frsldPvcCtrlPurge. end of the purge interval that is controlled by frsldPvcCtrlPurge.
The effects of automatic row destruction are the same as manual row The effects of automatic row destruction are the same as manual row
destruction. destruction.
3.6.5. Modification Process 3.6.5. Modification Process
All read-create items in this MIB can be modified at any time if they All read-create items in this MIB module can be modified at any time
are fully supported. Write access is not required. To simplify the if they are fully supported. Write access is not required. To
use of the MIB frsldPvcCtrlWriteCaps and frsldSmplCtrlWriteCaps state simplify the use of the MIB frsldPvcCtrlWriteCaps and
which of the read-create variables can actually be written on a frsldSmplCtrlWriteCaps state which of the read-create variables can
particular device. actually be written on a particular device.
3.6.6. Collection Process 3.6.6. Collection Process
3.6.6.1. Remote Polling 3.6.6.1. Remote Polling
This MIB supports data collection through remote polling of the free This MIB module supports data collection through remote polling of
running counters in the PVC Data Table. Remote polling is a common the free running counters in the PVC Data Table. Remote polling is a
method used to capture real-time statistics. A remote management common method used to capture real-time statistics. A remote
station polls the device to collect the desired information. It is management station polls the device to collect the desired
recommended all statistics for a single PVC be collected in a single information. It is recommended all statistics for a single PVC be
PDU. collected in a single PDU.
The following objects are designed around the concept of real-time The following objects are designed around the concept of real-time
polling: polling:
o frsldPvcDataMissedPolls o frsldPvcDataMissedPolls
o frsldPvcDataFrDeliveredC o frsldPvcDataFrDeliveredC
o frsldPvcDataFrDeliveredE o frsldPvcDataFrDeliveredE
o frsldPvcDataFrOfferedC o frsldPvcDataFrOfferedC
o frsldPvcDataFrOfferedE o frsldPvcDataFrOfferedE
o frsldPvcDataDataDeliveredC o frsldPvcDataDataDeliveredC
skipping to change at page 18, line 6 skipping to change at page 18, line 14
3.6.6.3. User History 3.6.6.3. User History
User history, as defined in RFC 2021 [19], is an alternative User history, as defined in RFC 2021 [19], is an alternative
mechanism that can be used to get the same benefits as the sample mechanism that can be used to get the same benefits as the sample
table by using the objects provided for real-time polling. Some table by using the objects provided for real-time polling. Some
devices MAY have the ability to use user history and opt not to devices MAY have the ability to use user history and opt not to
support the sample tables. If this is the case, the information from support the sample tables. If this is the case, the information from
the data table can be used to define a group of user history objects. the data table can be used to define a group of user history objects.
3.6.7. Use of MIB in Calculation of Service Level Definitions 3.6.7. Use of MIB Module in Calculation of Service Level Definitions
The objects in this MIB can be used to calculate the statistics The objects in this MIB module can be used to calculate the
defined in FRF.13 [17]. The description below describes the statistics defined in FRF.13 [17]. The description below describes
calculations for one direction of the data flow, i.e. data sent from the calculations for one direction of the data flow, i.e. data sent
local transmitter to a remote receiver. A complete set of from local transmitter to a remote receiver. A complete set of
bidirectional information would require calculations based on both bidirectional information would require calculations based on both
directions. For the purposes of this description, the reference directions. For the purposes of this description, the reference
points used SHOULD consistently represent data that is sent by one points used SHOULD consistently represent data that is sent by one
device and received by the other. device and received by the other.
A complete evaluation requires the combination of two uni-directional A complete evaluation requires the combination of two uni-directional
flows. It is possible for a management station to combine all of the flows. It is possible for a management station to combine all of the
calculated information into one conceptual row. Doing this requires calculated information into one conceptual row. Doing this requires
that each of the metrics are collected for both flow directions and that each of the metrics are collected for both flow directions and
grouped by direction If the information is split between two grouped by direction If the information is split between two
devices, the management station must know which two devices to devices, the management station must know which two devices to
communicate with for the collection of all information. The grouping communicate with for the collection of all information. The grouping
of information SHOULD be from ingress to egress in each flow of information SHOULD be from ingress to egress in each flow
direction. direction.
The calculations below use the following terminology: The calculations below use the following terminology:
o DelayAvg o DelayAvg
The average delay on the PVC. This is represented within the The average delay on the PVC. This is represented within the
MIB by frsldPvcSmplDelayAvg. MIB module by frsldPvcSmplDelayAvg.
o FrDeliveredC o FrDeliveredC
The number of frames received by the receiving device through The number of frames received by the receiving device through
the receive reference point that were delivered within CIR. the receive reference point that were delivered within CIR.
This is represented within the MIB by one of This is represented within the MIB module by one of
frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC, frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC,
frsldPvcSmplFrDeliveredC, or frsldPvcSmplHCFrDeliveredC. frsldPvcSmplFrDeliveredC, or frsldPvcSmplHCFrDeliveredC.
o FrDeliveredE o FrDeliveredE
The number of frames received by the receiving device through The number of frames received by the receiving device through
the receive reference point that were delivered in excess of the receive reference point that were delivered in excess of
CIR. This is represented within the MIB by one of CIR. This is represented within the MIB module by one of
frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE, frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE,
frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE. frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE.
o FrOfferedC o FrOfferedC
The number of frames offered by the transmitting device through The number of frames offered by the transmitting device through
the transmit reference point that were sent within CIR. This is the transmit reference point that were sent within CIR. This is
represented within the MIB by one of frsldPvcDataFrOfferedC, represented within the MIB module by one of
frsldPvcDataHCFrOfferedC, frsldPvcSmplFrOfferedC, or frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC,
frsldPvcSmplHCFrOfferedC. frsldPvcSmplFrOfferedC, or frsldPvcSmplHCFrOfferedC.
o FrOfferedE o FrOfferedE
The number of frames offered by the transmitting device through The number of frames offered by the transmitting device through
the transmit reference point that were sent in excess of CIR. the transmit reference point that were sent in excess of CIR.
This is represented within the MIB by one of This is represented within the MIB module by one of
frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE, frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE,
frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE. frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE.
o DataDeliveredC o DataDeliveredC
The number of octets received by the receiving device through The number of octets received by the receiving device through
the receive reference point that were delivered within CIR. the receive reference point that were delivered within CIR.
This is represented within the MIB by one of This is represented within the MIB module by one of
frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC, frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC,
frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC. frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC.
o DataDeliveredE o DataDeliveredE
The number of octets received by the receiving device through The number of octets received by the receiving device through
the receive reference point that were delivered in excess of the receive reference point that were delivered in excess of
CIR. This is represented within the MIB by one of CIR. This is represented within the MIB module by one of
frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE, frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE,
frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE. frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE.
o DataOfferedC o DataOfferedC
The number of octets offered by the transmitting device through The number of octets offered by the transmitting device through
the transmit reference point that were sent within CIR. This is the transmit reference point that were sent within CIR. This is
represented within the MIB by one of frsldPvcDataDataOfferedC, represented within the MIB module by one of
frsldPvcDataHCDataOfferedC, frsldPvcSmplDataOfferedC, or frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC,
frsldPvcSmplHCDataOfferedC. frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC.
o DataOfferedE o DataOfferedE
The number of octets offered by the transmitting device through The number of octets offered by the transmitting device through
the transmit reference point that were sent in excess of CIR. the transmit reference point that were sent in excess of CIR.
This is represented within the MIB by one of This is represented within the MIB module by one of
frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE, frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE,
frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE. frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE.
o UnavailableTime o UnavailableTime
The amount of time the PVC was not available during the interval The amount of time the PVC was not available during the interval
of interest. This is represented within the MIB by either of interest. This is represented within the MIB module by
frsldPvcDataUnavailableTime or frsldPvcSmplUnavailableTime. either frsldPvcDataUnavailableTime or
frsldPvcSmplUnavailableTime.
o Unavailables o Unavailables
The number of times the PVC was declared to be unavailable The number of times the PVC was declared to be unavailable
during the interval of interest. This is represented within the during the interval of interest. This is represented within the
MIB by either frsldPvcDataUnavailables or MIB module by either frsldPvcDataUnavailables or
frsldPvcSmplUnavailables. frsldPvcSmplUnavailables.
3.6.8. Delay 3.6.8. Delay
The frame transfer delay is defined as the amount of time elapsed, in The frame transfer delay is defined as the amount of time elapsed, in
microseconds, from the time a frame exits the source to the time it microseconds, from the time a frame exits the source to the time it
reaches the destination. The average delay can be found using the MIB reaches the destination. The average delay can be found using the MIB
variable described in DelayAvg above. The delay may be calculated as variable described in DelayAvg above. The delay may be calculated as
either round trip or one way, and this information is held in the either round trip or one way, and this information is held in the
frsldPvcCtrlDelayType MIB variable. If the delay be calculated as frsldPvcCtrlDelayType MIB variable. If the delay be calculated as
skipping to change at page 22, line 24 skipping to change at page 22, line 24
IntervalTime - ExcludedTime - UnavailableTime IntervalTime - ExcludedTime - UnavailableTime
Otherwise, FRVCA = --------------------------------------------- *100 Otherwise, FRVCA = --------------------------------------------- *100
IntervalTime - ExcludedTime IntervalTime - ExcludedTime
Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0. Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0.
Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime
--------------------------------------------- ---------------------------------------------
Unavailables Unavailables
4. Relation to Other MIBs 4. Relation to Other MIB Modules
There is no explicit relation to any other frame relay MIB nor are There is no explicit relation to any other frame relay MIB module nor
any required to implement this MIB. However, there is a need for are any required to implement this MIB module. However, there is a
knowledge of ifIndexes and some understanding of DLCIs. The ifIndex need for knowledge of ifIndexes and some understanding of DLCIs. The
information can be found in the IF-MIB which is required. The DLCI ifIndex information can be found in the IF-MIB [21] which is
information can be found in either the Frame Relay DTE MIB (RFC 2115) required. The DLCI information can be found in either the Frame Relay
[20] or the Frame Relay Network Services MIB (RFC 1604) [18]; DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC
however, neither is required. 1604) [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 1604) [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).
skipping to change at page 23, line 16 skipping to change at page 23, line 16
the Frame Relay Network Services MIB (RFC 1604) [18]. For the the Frame Relay Network Services MIB (RFC 1604) [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 be set to the data or sample tables and frsldPvcCtrlStatus SHOULD report
notReady(3). notReady(3).
For the third case, frsldPvcCtrlDeleteOnPurge should direct the For the third case, frsldPvcCtrlDeleteOnPurge should direct the
behavior of the system. If all tables are purged, this case will be behavior of the system. If all tables are purged, this case will be
equivalent to the second case above. Otherwise, frsldPvcCtrlStatus equivalent to the second case above. Otherwise, frsldPvcCtrlStatus
SHOULD remain active(1). SHOULD remain active(1).
5. Structure of the MIB 5. Structure of the MIB Module
The FRSLD-MIB consists of the following components: The FRSLD-MIB consists of the following components:
o frsldPvcCtrlTable o frsldPvcCtrlTable
o frsldSmplCtrlTable o frsldSmplCtrlTable
o frsldPvcDataTable o frsldPvcDataTable
o frsldPvcSampleTable o frsldPvcSampleTable
skipping to change at page 23, line 49 skipping to change at page 23, line 49
what objects MUST be implemented. what objects MUST be implemented.
5.1. frsldPvcCtrlTable 5.1. frsldPvcCtrlTable
The frsldPvcCtrlTable is the central control table for operations of The frsldPvcCtrlTable is the central control table for operations of
the Frame Relay Service Level Definitions MIB. It provides variables the Frame Relay Service Level Definitions MIB. It provides variables
to control the parameters required to calculate the objects in the to control the parameters required to calculate the objects in the
other tables. other tables.
A row in this table MUST exist in order for a row to exist in any A row in this table MUST exist in order for a row to exist in any
other table in this MIB. other table in this MIB module.
5.2. frsldSmplCtrlTable 5.2. frsldSmplCtrlTable
This is an optional table to allow control of sampling of the data in This is an optional table to allow control of sampling of the data in
the data table. the data table.
5.3. frsldPvcDataTable 5.3. frsldPvcDataTable
This table contains the calculated data. It relies on configuration This table contains the calculated data. It relies on configuration
from the control table. from the control table.
skipping to change at page 24, line 36 skipping to change at page 24, line 36
6. Object Definitions 6. Object Definitions
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
RowStatus, TimeStamp FROM SNMPv2-TC TEXTUAL-CONVENTION, RowStatus,
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;
frsldMIB MODULE-IDENTITY frsldMIB MODULE-IDENTITY
LAST-UPDATED "200009191500Z" -- September 19, 2000 LAST-UPDATED "200105011500Z" -- May 1, 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
Chair: Andy Malis Chair: Andy Malis
Lucent Technologies Lucent Technologies
Email: amalis@lucent.com Email: amalis@lucent.com
WG editor: Robert Steinberger WG editor: Robert Steinberger
Paradyne Networks Paradyne Networks and
Email: rsteinberger@paradyne.com Fujitsu Network Communications
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 "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" REVISION "200009191500Z"
DESCRIPTION DESCRIPTION
"o Removed frsldPvcCtrlDelayCnt. "o Removed frsldPvcCtrlDelayCnt.
o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl- o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl-
AvailBuckets, and frsldSmplCtrlAvailBucketsGranted. AvailBuckets, and frsldSmplCtrlAvailBucketsGranted.
o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*. o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*.
o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax, o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax,
and frsldPvcDataDelayAvg. and frsldPvcDataDelayAvg.
o Changed frsldPvcDataSample* to frsldPvcSample*. o Changed frsldPvcDataSample* to frsldPvcSample*.
o Changed frsldPvcDataSmpl* to frsldPvcSmpl*. o Changed frsldPvcDataSmpl* to frsldPvcSmpl*.
skipping to change at page 26, line 46 skipping to change at page 27, line 13
sample tables sample tables
o Changed all occasions of TimeTicks to TimeStamp o Changed all occasions of TimeTicks to TimeStamp
o Added frsldPvcCtrlPurge to aid in control validity o Added frsldPvcCtrlPurge to aid in control validity
of information due to PVC status changes of information due to PVC status changes
o Added frsldPvcCtrlDeleteOnPurge object o Added frsldPvcCtrlDeleteOnPurge object
o Added frsldPvcCtrlLastPurgeTime object o Added frsldPvcCtrlLastPurgeTime object
o Added units clauses to all time related fields. o Added units clauses to all time related fields.
o Reworded the `change in' syntax to be more explicit" 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
--
FrsldTxRP ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The reference point a PVC uses for calculation
of transmitter related statistics.
The valid values for this type of object are as follows:
- srcLocalRP(1) for the local source
- ingTxLocalRP(2) for the local ingress queue input
- tpTxLocalRP(3) for the local traffic policing
- eqiTxLocalRP(4) for the local egress queue input
- eqoTxLocalRP(5) for the local egress queue output
- otherTxLocalRP(6) for any other local transmit point
- srcRemoteRP(7) for the remote source
- ingTxLocalRP(8) for the remote ingress queue input
- tpTxLocalRP(9) for the remote traffic policing
- eqiTxRemoteRP(10) for the remote egress queue input
- eqoTxRemoteRP(11) for the remote egress queue output
- otherTxRemoteRP(12) for any other remote xmit point"
REFERENCE
"FRF.13: Section 2.3"
SYNTAX INTEGER {
srcLocalRP(1),
ingTxLocalRP(2),
tpTxLocalRP(3),
eqiTxLocalRP(4),
eqoTxLocalRP(5),
otherTxLocalRP(6),
srcRemoteRP(7),
ingTxRemoteRP(8),
tpTxRemoteRP(9),
eqiTxRemoteRP(10),
eqoTxRemoteRP(11),
otherTxRemoteRP(12)
}
FrsldRxRP ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The reference point a PVC uses for calculation
of receiver related statistics.
The valid values for this object are as follows:
- desLocalRP(1) for the local destination
- ingRxLocalRP(2) for the local ingress queue input
- tpRxLocalRP(3) for the local traffic policing
- eqiRxLocalRP(4) for the local egress queue input
- eqoRxLocalRP(5) for the local egress queue output
- otherRxLocalRP(6) for any other local receive point
- desRemoteRP(7) for the remote destination
- ingRxRemoteRP(8) for the remote ingress input
- tpRxRemoteRP(9) for the remote traffic policing
- eqiRxRemoteRP(10) for the remote egress queue input
- eqoRxRemoteRP(11) for the remote egress queue output
- otherRxRemoteRP(12) for any other remote receive point"
REFERENCE
"FRF.13: Section 2.3"
SYNTAX INTEGER {
desLocalRP(1),
ingRxLocalRP(2),
tpRxLocalRP(3),
eqiRxLocalRP(4),
eqoRxLocalRP(5),
otherRxLocalRP(6),
desRemoteRP(7),
ingRxRemoteRP(8),
tpRxRemoteRP(9),
eqiRxRemoteRP(10),
eqoRxRemoteRP(11),
otherRxRemoteRP(12)
}
--
-- Base Objects
---
frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 } frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 }
frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 } frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 }
frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 } frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 }
-- The Frame Relay Service Level Definitions PVC Control Table -- The Frame Relay Service Level Definitions PVC Control Table
-- --
-- This table is used to define and display the parameters of -- This table is used to define and display the parameters of
-- service level definitions on individual PVCs. -- service level definitions on individual PVCs.
frsldPvcCtrlTable OBJECT-TYPE frsldPvcCtrlTable OBJECT-TYPE
skipping to change at page 27, line 32 skipping to change at page 29, line 31
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 Integer32,
frsldPvcCtrlTransmitRP INTEGER, frsldPvcCtrlTransmitRP FrsldTxRP,
frsldPvcCtrlReceiveRP INTEGER, 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
-- --
frsldPvcCtrlDelayFrSize Integer32, frsldPvcCtrlDelayFrSize Integer32,
frsldPvcCtrlDelayType INTEGER, frsldPvcCtrlDelayType INTEGER,
skipping to change at page 28, line 14 skipping to change at page 30, line 13
frsldPvcCtrlDlci OBJECT-TYPE frsldPvcCtrlDlci OBJECT-TYPE
SYNTAX Integer32 (16..4194303) SYNTAX Integer32 (16..4194303)
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 INTEGER { SYNTAX FrsldTxRP
srcLocalRP(1),
ingTxLocalRP(2),
tpTxLocalRP(3),
eqiTxLocalRP(4),
eqoTxLocalRP(5),
otherTxLocalRP(6),
srcRemoteRP(7),
ingTxRemoteRP(8),
tpTxRemoteRP(9),
eqiTxRemoteRP(10),
eqoTxRemoteRP(11),
otherTxRemoteRP(12)
}
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reference point this PVC used for calculation "The reference point this PVC uses for calculation
of transmitter related statistics. This object of transmitter related statistics. This object
together with frsldPvcCtrlReceiveRP define the together with frsldPvcCtrlReceiveRP define the
measurement domain. measurement domain."
REFERENCE
The valid values for this object are as follows: "FRF.13: Section 2.3"
- srcLocalRP(1) for the local source
- ingTxLocalRP(2) for the local ingress queue input
- tpTxLocalRP(3) for the local traffic policing
- eqiTxLocalRP(4) for the local egress queue input
- eqoTxLocalRP(5) for the local egress queue output
- otherTxLocalRP(6) for any other local transmit point
- srcRemoteRP(7) for the remote source
- ingTxLocalRP(8) for the remote ingress queue input
- tpTxLocalRP(9) for the remote traffic policing
- eqiTxRemoteRP(10) for the remote egress queue input
- eqoTxRemoteRP(11) for the remote egress queue output
- otherTxRemoteRP(12) for any other remote xmit point"
::= { frsldPvcCtrlEntry 2 } ::= { frsldPvcCtrlEntry 2 }
frsldPvcCtrlReceiveRP OBJECT-TYPE frsldPvcCtrlReceiveRP OBJECT-TYPE
SYNTAX INTEGER { SYNTAX FrsldRxRP
desLocalRP(1),
ingRxLocalRP(2),
tpRxLocalRP(3),
eqiRxLocalRP(4),
eqoRxLocalRP(5),
otherRxLocalRP(6),
desRemoteRP(7),
ingRxRemoteRP(8),
tpRxRemoteRP(9),
eqiRxRemoteRP(10),
eqoRxRemoteRP(11),
otherRxRemoteRP(12)
}
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reference point this PVC used for calculation "The reference point this PVC uses for calculation
of receiver related statistics. This object of receiver related statistics. This object
together with frsldPvcCtrlTransmitRP define the together with frsldPvcCtrlTransmitRP define the
measurement domain. measurement domain."
The valid values for this object are as follows:
- desLocalRP(1) for the local destination
- ingRxLocalRP(2) for the local ingress queue input
- tpRxLocalRP(3) for the local traffic policing
- eqiRxLocalRP(4) for the local egress queue input
- eqoRxLocalRP(5) for the local egress queue output
- otherRxLocalRP(6) for any other local receive point
- desRemoteRP(7) for the remote destination
- ingRxRemoteRP(8) for the remote ingress input
- tpRxRemoteRP(9) for the remote traffic policing
- eqiRxRemoteRP(10) for the remote egress queue input
- eqoRxRemoteRP(11) for the remote egress queue output
- otherRxRemoteRP(12) for any other remote receive point"
::= { frsldPvcCtrlEntry 3 } ::= { frsldPvcCtrlEntry 3 }
frsldPvcCtrlStatus OBJECT-TYPE frsldPvcCtrlStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the current row. This object is "The status of the current row. This object is
used to add, delete, and disable rows in this used to add, delete, and disable rows in this
table. When the status changes to active(1) for the table. When the status changes to active(1) for the
skipping to change at page 31, line 7 skipping to change at page 31, line 51
frsldPvcCtrlDelayType OBJECT-TYPE frsldPvcCtrlDelayType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
oneWay(1), oneWay(1),
roundTrip(2) roundTrip(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of delay measurement performed." "The type of delay measurement performed."
REFERENCE
"FRF.13: Section 3"
::= { frsldPvcCtrlEntry 7 } ::= { frsldPvcCtrlEntry 7 }
frsldPvcCtrlDelayTimeOut OBJECT-TYPE frsldPvcCtrlDelayTimeOut OBJECT-TYPE
SYNTAX Integer32 (1..3600) SYNTAX Integer32 (1..3600)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A delay frame will count as a missed poll if "A delay frame will count as a missed poll if
it is not updated in the time specified by it is not updated in the time specified by
skipping to change at page 32, line 25 skipping to change at page 33, line 24
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. If frsldPvcCtrlStatus has
never been active(1), this object SHOULD return 0." never been active(1), this object SHOULD return 0."
DEFVAL { 0 }
::= { 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 36, line 25 skipping to change at page 37, line 21
::= { 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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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
for any reason since this row was created." for any reason since this row was created."
REFERENCE
"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."
REFERENCE
"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
SYNTAX SEQUENCE OF FrsldPvcSampleEntry SYNTAX SEQUENCE OF FrsldPvcSampleEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 41, line 32 skipping to change at page 43, line 15
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum delay reported in microseconds measured "The minimum delay reported in microseconds measured
for any information packet that arrived during this for any information packet that arrived during this
interval. interval.
A value of zero means that no data is available." A value of zero means that no data is available."
REFERENCE
"FRF.13: Section 3.1 (FTD)"
::= { frsldPvcSampleEntry 2 } ::= { frsldPvcSampleEntry 2 }
frsldPvcSmplDelayMax OBJECT-TYPE frsldPvcSmplDelayMax OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The largest delay reported in microseconds measured "The largest delay reported in microseconds measured
for any information packet that arrived during this for any information packet that arrived during this
interval. interval.
A value of zero means that no data is available." A value of zero means that no data is available."
REFERENCE
"FRF.13: Section 3.1 (FTD)"
::= { frsldPvcSampleEntry 3 } ::= { frsldPvcSampleEntry 3 }
frsldPvcSmplDelayAvg OBJECT-TYPE frsldPvcSmplDelayAvg OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average delay reported in microseconds measured "The average delay reported in microseconds measured
for all delay packets that arrived during this for all delay packets that arrived during this
interval. interval.
A value of zero means that no data is available." A value of zero means that no data is available."
REFERENCE
"FRF.13: Section 3.1 (FTD)"
::= { frsldPvcSampleEntry 4 } ::= { frsldPvcSampleEntry 4 }
frsldPvcSmplMissedPolls OBJECT-TYPE frsldPvcSmplMissedPolls OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of polls that were missed during "The total number of polls that were missed during
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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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."
REFERENCE
"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
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval. This object sent within CIR during this interval. This object
is a 64-bit version of frsldPvcSmplFrDeliveredC." is a 64-bit version of frsldPvcSmplFrDeliveredC."
REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)"
::= { frsldPvcSampleEntry 14 } ::= { frsldPvcSampleEntry 14 }
frsldPvcSmplHCFrDeliveredE OBJECT-TYPE frsldPvcSmplHCFrDeliveredE 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
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.
This object is a 64-bit version of frsldPvcSmpl- This object is a 64-bit version of frsldPvcSmpl-
FrDeliveredE." FrDeliveredE."
REFERENCE
"FRF.13: Section 4.1 (FramesDeliverede)"
::= { frsldPvcSampleEntry 15 } ::= { frsldPvcSampleEntry 15 }
frsldPvcSmplHCFrOfferedC OBJECT-TYPE frsldPvcSmplHCFrOfferedC 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 offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR during this frsldPvcCtrlTransmitRP within CIR during this
interval. This object is a 64-bit version of interval. This object is a 64-bit version of
frsldPvcSmplFrOfferedC." frsldPvcSmplFrOfferedC."
REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)"
::= { frsldPvcSampleEntry 16 } ::= { frsldPvcSampleEntry 16 }
frsldPvcSmplHCFrOfferedE OBJECT-TYPE frsldPvcSmplHCFrOfferedE 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 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. This object is a 64-bit during this interval. This object is a 64-bit
version of frsldPvcSmplFrOfferedE." version of frsldPvcSmplFrOfferedE."
REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)"
::= { frsldPvcSampleEntry 17 } ::= { frsldPvcSampleEntry 17 }
frsldPvcSmplHCDataDeliveredC OBJECT-TYPE frsldPvcSmplHCDataDeliveredC OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
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. This value sent within CIR during this interval. This value
is a 64-bit version of frsldPvcSmplDataDeliveredC." is a 64-bit version of frsldPvcSmplDataDeliveredC."
REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)"
::= { frsldPvcSampleEntry 18 } ::= { frsldPvcSampleEntry 18 }
frsldPvcSmplHCDataDeliveredE OBJECT-TYPE frsldPvcSmplHCDataDeliveredE OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
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 during this interval. This sent in excess of the CIR during this interval. This
value is a 64-bit version of frsldPvcSmplData- value is a 64-bit version of frsldPvcSmplData-
DeliveredE." DeliveredE."
REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)"
::= { frsldPvcSampleEntry 19 } ::= { frsldPvcSampleEntry 19 }
frsldPvcSmplHCDataOfferedC OBJECT-TYPE frsldPvcSmplHCDataOfferedC OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
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. This value is a 64-bit version of interval. This value is a 64-bit version of
frsldPvcSmplDataOfferedC." frsldPvcSmplDataOfferedC."
REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)"
::= { frsldPvcSampleEntry 20 } ::= { frsldPvcSampleEntry 20 }
frsldPvcSmplHCDataOfferedE OBJECT-TYPE frsldPvcSmplHCDataOfferedE OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
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. This object is a 64-bit during this interval. This object is a 64-bit
version of frsldPvcSmplDataOfferedE." version of frsldPvcSmplDataOfferedE."
REFERENCE
"FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcSampleEntry 21 } ::= { frsldPvcSampleEntry 21 }
frsldPvcSmplUnavailableTime OBJECT-TYPE frsldPvcSmplUnavailableTime 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 "The amount of time this PVC was declared
unavailable for any reason during this interval." unavailable for any reason during this interval."
REFERENCE
"FRF.13: Section 6.1 (OutageTime)"
::= { frsldPvcSampleEntry 22 } ::= { frsldPvcSampleEntry 22 }
frsldPvcSmplUnavailables OBJECT-TYPE frsldPvcSmplUnavailables OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times this PVC was declared "The number of times this PVC was declared
unavailable for any reason during this interval." unavailable for any reason during this interval."
REFERENCE
"FRF.13: Section 6.1 (OutageCount)"
::= { frsldPvcSampleEntry 23 } ::= { frsldPvcSampleEntry 23 }
frsldPvcSmplStartTime OBJECT-TYPE frsldPvcSmplStartTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this sample interval "The value of sysUpTime when this sample interval
started." started."
::= { frsldPvcSampleEntry 24 } ::= { frsldPvcSampleEntry 24 }
skipping to change at page 48, line 14 skipping to change at page 50, line 40
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the reference points that "This object specifies the reference points that
the agent supports. This object allows the management the agent supports. This object allows the management
application to discover which rows can be created on application to discover which rows can be created on
a specific device." a specific device."
::= { frsldCapabilities 3 } ::= { frsldCapabilities 3 }
frsldMaxPvcCtrls OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of control rows that can be created
in frsldPvcCtrlTable. Sets to this object lower than
the current value of frsldNumPvcCtrls should result in
badValue."
::= { frsldCapabilities 4 }
frsldNumPvcCtrls OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of rows in frsldPvcCtrlTable."
::= { frsldCapabilities 5 }
frsldMaxSmplCtrls OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of control rows that can be created
in frsldSmplCtrlTable. Sets to this object lower than
the current value of frsldNumSmplCtrls should result in
badValue."
::= { frsldCapabilities 6 }
frsldNumSmplCtrls OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of rows in frsldSmplCtrlTable."
::= { frsldCapabilities 7 }
-- Conformance Information -- Conformance Information
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 SNMPv2 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
DESCRIPTION
"This group is mandatory only for those network interfaces
with corresponding instance of ifSpeed greater than
650,000,000 bits/second."
GROUP frsldPvcHCOctetDataGroup
DESCRIPTION
"This group is mandatory only for those network interfaces
with corresponding instance of ifSpeed greater than
650,000,000 bits/second."
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
"Write access is not required, and only one of the six "Row creation can be done outside of the scope of
enumerated values for the RowStatus textual convention the SNMP protocol. If this object is implemented
need be supported, specifically: active(1)." with max-access of read-only, then the only value
that MUST be returned is active(1) and
frsldPvcCtrlWriteCaps MUST return 0 for the
frsldPvcCtrlStatus(0) bit."
OBJECT frsldPvcCtrlPurge OBJECT frsldPvcCtrlPurge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required. If this object is
implemented with a max-access of read-only, then
the frsldPvcCtrlPurge(5) bit must return 0."
OBJECT frsldPvcCtrlDeleteOnPurge OBJECT frsldPvcCtrlDeleteOnPurge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required. If this object is
implemented with a max-access of read-only, then
the frsldPvcCtrlDeleteOnPurge(6) bit must return
0."
OBJECT frsldMaxPvcCtrls
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the device either
dynamically allocates memory or statically allocates
a fixed number of entries. In the case of static
allocation, the device should always report the
correct maximum number of controls. In the case
of dynamic allocation, the device SHOULD always
report a number greater than frsldNumPvcCtrls
when allocation is possible and a number equal to
frsldNumPvcCtrls when allocation is not possible."
OBJECT frsldMaxSmplCtrls
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the device either
dynamically allocates memory or statically allocates
a fixed number of entries. In the case of static
allocation, the device should always report the
correct maximum number of controls. In the case
of dynamic allocation, the device SHOULD always
report a number greater than frsldNumSmplCtrls
when allocation is possible and a number equal to
frsldNumSmplCtrls when allocation is not possible."
::= { frsldMIBCompliances 1 } ::= { frsldMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
frsldPvcReqCtrlGroup OBJECT-GROUP frsldPvcReqCtrlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcCtrlStatus, frsldPvcCtrlStatus,
frsldPvcCtrlPurge, frsldPvcCtrlPurge,
frsldPvcCtrlDeleteOnPurge, frsldPvcCtrlDeleteOnPurge,
skipping to change at page 49, line 44 skipping to change at page 54, line 12
frsldPvcDelayCtrlGroup OBJECT-GROUP frsldPvcDelayCtrlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcCtrlDelayFrSize, frsldPvcCtrlDelayFrSize,
frsldPvcCtrlDelayType, frsldPvcCtrlDelayType,
frsldPvcCtrlDelayTimeOut frsldPvcCtrlDelayTimeOut
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing delay "A collection of optional objects providing delay
control information applicable to a PVC which control information applicable to a PVC which
implements Service Level Definitions." implements Service Level Definitions.
If this group is implemented, frsldPvcPacketGroup
and frsldPvcDelayDataGroup MUST also be implemented."
::= { frsldMIBGroups 3 } ::= { frsldMIBGroups 3 }
frsldPvcSampleCtrlGroup OBJECT-GROUP frsldPvcSampleCtrlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldSmplCtrlStatus, frsldSmplCtrlStatus,
frsldSmplCtrlColPeriod, frsldSmplCtrlColPeriod,
frsldSmplCtrlBuckets, frsldSmplCtrlBuckets,
frsldSmplCtrlBucketsGranted frsldSmplCtrlBucketsGranted
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing sample "A collection of optional objects providing sample
control information applicable to a PVC which control information applicable to a PVC which
implements Service Level Definitions." implements Service Level Definitions.
If this group is implemented, frsldPvcReqDataGroup
and frsldPvcSampleGeneralGroup MUST also be
implemented."
::= { frsldMIBGroups 4 } ::= { frsldMIBGroups 4 }
frsldPvcReqDataGroup OBJECT-GROUP frsldPvcReqDataGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcDataFrDeliveredC, frsldPvcDataFrDeliveredC,
frsldPvcDataFrDeliveredE, frsldPvcDataFrDeliveredE,
frsldPvcDataFrOfferedC, frsldPvcDataFrOfferedC,
frsldPvcDataFrOfferedE, frsldPvcDataFrOfferedE,
frsldPvcDataDataDeliveredC, frsldPvcDataDataDeliveredC,
frsldPvcDataDataDeliveredE, frsldPvcDataDataDeliveredE,
skipping to change at page 50, line 41 skipping to change at page 55, line 16
::= { frsldMIBGroups 5 } ::= { frsldMIBGroups 5 }
frsldPvcDelayDataGroup OBJECT-GROUP frsldPvcDelayDataGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcDataMissedPolls frsldPvcDataMissedPolls
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing delay "A collection of optional objects providing delay
data collected on a PVC which implements Service data collected on a PVC which implements Service
Level Definitions." Level Definitions.
If this group is implemented, frsldPvcDelayCtrlGroup
MUST also be implemented."
::= { frsldMIBGroups 6 } ::= { frsldMIBGroups 6 }
frsldPvcHCFrameDataGroup OBJECT-GROUP frsldPvcHCFrameDataGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcDataHCFrDeliveredC, frsldPvcDataHCFrDeliveredC,
frsldPvcDataHCFrDeliveredE, frsldPvcDataHCFrDeliveredE,
frsldPvcDataHCFrOfferedC, frsldPvcDataHCFrOfferedC,
frsldPvcDataHCFrOfferedE frsldPvcDataHCFrOfferedE
} }
STATUS current STATUS current
skipping to change at page 51, line 35 skipping to change at page 56, line 13
OBJECTS { OBJECTS {
frsldPvcSmplDelayMin, frsldPvcSmplDelayMin,
frsldPvcSmplDelayMax, frsldPvcSmplDelayMax,
frsldPvcSmplDelayAvg, frsldPvcSmplDelayAvg,
frsldPvcSmplMissedPolls frsldPvcSmplMissedPolls
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing delay "A collection of optional objects providing delay
sample data collected on a PVC which implements sample data collected on a PVC which implements
Service Level Definitions." Service Level Definitions.
If this group is implemented, frsldPvcDelayCtrlGroup
MUST also be implemented."
::= { frsldMIBGroups 9 } ::= { frsldMIBGroups 9 }
frsldPvcSampleDataGroup OBJECT-GROUP frsldPvcSampleDataGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcSmplFrDeliveredC, frsldPvcSmplFrDeliveredC,
frsldPvcSmplFrDeliveredE, frsldPvcSmplFrDeliveredE,
frsldPvcSmplFrOfferedC, frsldPvcSmplFrOfferedC,
frsldPvcSmplFrOfferedE, frsldPvcSmplFrOfferedE,
frsldPvcSmplDataDeliveredC, frsldPvcSmplDataDeliveredC,
frsldPvcSmplDataDeliveredE, frsldPvcSmplDataDeliveredE,
frsldPvcSmplDataOfferedC, frsldPvcSmplDataOfferedC,
frsldPvcSmplDataOfferedE frsldPvcSmplDataOfferedE
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing data "A collection of optional objects providing data
and frame delivery sample data collected on a PVC and frame delivery sample data collected on a PVC
which implements Service Level Definitions." which implements Service Level Definitions.
If this group is implemented, frsldPvcReqDataGroup
MUST also be implemented."
::= { frsldMIBGroups 10 } ::= { frsldMIBGroups 10 }
frsldPvcSampleHCFrameGroup OBJECT-GROUP frsldPvcSampleHCFrameGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcSmplHCFrDeliveredC, frsldPvcSmplHCFrDeliveredC,
frsldPvcSmplHCFrDeliveredE, frsldPvcSmplHCFrDeliveredE,
frsldPvcSmplHCFrOfferedC, frsldPvcSmplHCFrOfferedC,
frsldPvcSmplHCFrOfferedE frsldPvcSmplHCFrOfferedE
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing high "A collection of optional objects providing high
capacity frame delivery sample data collected on a PVC capacity frame delivery sample data collected on a PVC
which implements Service Level Definitions." which implements Service Level Definitions.
If this group is implemented, frsldPvcHCFrameDataGroup
MUST also be implemented."
::= { frsldMIBGroups 11 } ::= { frsldMIBGroups 11 }
frsldPvcSampleHCDataGroup OBJECT-GROUP frsldPvcSampleHCDataGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcSmplHCDataDeliveredC, frsldPvcSmplHCDataDeliveredC,
frsldPvcSmplHCDataDeliveredE, frsldPvcSmplHCDataDeliveredE,
frsldPvcSmplHCDataOfferedC, frsldPvcSmplHCDataOfferedC,
frsldPvcSmplHCDataOfferedE frsldPvcSmplHCDataOfferedE
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing high "A collection of optional objects providing high
capacity data delivery sample data collected on a PVC capacity data delivery sample data collected on a PVC
which implements Service Level Definitions." which implements Service Level Definitions.
If this group is implemented, frsldPvcHCOctetDataGroup
MUST also be implemented."
::= { frsldMIBGroups 12 } ::= { frsldMIBGroups 12 }
frsldPvcSampleAvailGroup OBJECT-GROUP frsldPvcSampleAvailGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcSmplUnavailableTime, frsldPvcSmplUnavailableTime,
frsldPvcSmplUnavailables frsldPvcSmplUnavailables
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing "A collection of optional objects providing
availability sample data collected on a PVC which availability sample data collected on a PVC which
implements Service Level Definitions." implements Service Level Definitions.
If this group is implemented, frsldPvcReqDataGroup
MUST also be implemented."
::= { frsldMIBGroups 13 } ::= { frsldMIBGroups 13 }
frsldPvcSampleGeneralGroup OBJECT-GROUP frsldPvcSampleGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcSmplStartTime, frsldPvcSmplStartTime,
frsldPvcSmplEndTime frsldPvcSmplEndTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing "A collection of optional objects providing
skipping to change at page 53, line 11 skipping to change at page 58, line 4
OBJECTS { OBJECTS {
frsldPvcSmplStartTime, frsldPvcSmplStartTime,
frsldPvcSmplEndTime frsldPvcSmplEndTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of optional objects providing "A collection of optional objects providing
general sample data collected on a PVC which general sample data collected on a PVC which
implements Service Level Definitions." implements Service Level Definitions."
::= { frsldMIBGroups 14 } ::= { frsldMIBGroups 14 }
frsldCapabilitiesGroup OBJECT-GROUP frsldCapabilitiesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frsldPvcCtrlWriteCaps, frsldPvcCtrlWriteCaps,
frsldSmplCtrlWriteCaps, frsldSmplCtrlWriteCaps,
frsldRPCaps frsldRPCaps,
frsldMaxPvcCtrls,
frsldNumPvcCtrls,
frsldMaxSmplCtrls,
frsldNumSmplCtrls
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of required objects providing "A collection of required objects providing
capability information for this MIB." capability information and control for this
MIB module."
::= { frsldMIBGroups 15 } ::= { frsldMIBGroups 15 }
END END
7. Acknowledgments 7. Acknowledgments
This document was produced by the Frame Relay Service MIB Working This document was produced by the Frame Relay Service MIB Working
Group. It is based on the Frame Relay Forum's implementation Group. It is based on the Frame Relay Forum's implementation
agreement on service level definitions, FRF.13 [17]. agreement on service level definitions, FRF.13 [17].
The editors would like to thank the following people for their The editors would like to thank the following people for their
skipping to change at page 56, line 5 skipping to change at page 60, line 44
RFC 1604, Bell Communications Research, March 1994. RFC 1604, Bell Communications Research, March 1994.
[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
2863, Cisco Systems, Argon Networks, June 2000.
9. Security Considerations 9. 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
skipping to change at page 56, line 33 skipping to change at page 62, line 33
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
10. Authors' Addresses 10. Authors' Addresses
Robert Steinberger Robert Steinberger
Paradyne Networks Fujitsu Network Communications
Mailstop: LG-132 2801 Telecom Parkway
8545 126th Avenue North Richardson, TX 75082
Largo, FL USA 33773
Phone: 1(727)530-2395 Phone: 1-972-479-4739
Email: rsteinberger@paradyne.com Email: robert.steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D Orly Nicklass, Ph.D
RAD Data Communications Ltd. RAD Data Communications Ltd.
12 Hanechoshet Street 12 Hanechoshet Street
Tel Aviv, Israel 69710 Tel Aviv, Israel 69710
Phone: 972 3 7659969 Phone: 972 3 7659969
Email: Orly_n@rrad.co.il Email: Orly_n@rrad.co.il
 End of changes. 117 change blocks. 
177 lines changed or deleted 425 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/