draft-ietf-frnetmib-frmrelay-service-06.txt   rfc3202.txt 
Definitions of Managed Objects Network Working Group R. Steinberger
for Frame Relay Service Level Definitions Request for Comments: 3202 Paradyne Networks
Category: Standards Track O. Nicklass
September 25, 2001 RAD Data Communications Ltd.
January 2002
draft-ietf-frnetmib-frmrelay-service-06.txt
Robert A. Steinberger
Paradyne Networks
robert.steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D Definitions of Managed Objects
RAD Data Communications Ltd. for Frame Relay Service Level Definitions
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 specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet-Drafts are working Internet community, and requests discussion and suggestions for
documents of the Internet Engineering Task Force (IETF), its areas, improvements. Please refer to the current edition of the "Internet
and its working groups. Note that other groups may also distribute Official Protocol Standards" (STD 1) for the standardization state
working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2002). All Rights Reserved.
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. Relay Service Level Definitions.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Table of Contents Table of Contents
1. The SNMP Management Framework ............................... 3 1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 4 2. Conventions ................................................. 3
3. Overview .................................................... 4 3. Overview .................................................... 3
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 ........... 10 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 ................................ 16 3.6.4.1. Manual Row Destruction ................................ 15
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 .......................................... 18 3.6.6.3. User History .......................................... 17
3.6.7. Use of MIB Module in Calculation of Service Level 3.6.7. Use of MIB Module in Calculation of Service Level
Definitions .................................................... 18 Definitions .................................................... 17
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 MIB Modules ............................... 22 4. Relation to Other MIB Modules ............................... 22
5. Structure of the MIB Module ................................. 23 5. Structure of the MIB Module ................................. 23
5.1. frsldPvcCtrlTable ......................................... 23 5.1. frsldPvcCtrlTable ......................................... 23
5.2. frsldSmplCtrlTable ........................................ 24 5.2. frsldSmplCtrlTable ........................................ 23
5.3. frsldPvcDataTable ......................................... 24 5.3. frsldPvcDataTable ......................................... 23
5.4. frsldPvcSampleTable ....................................... 24 5.4. frsldPvcSampleTable ....................................... 24
5.5. frsldCapabilities ......................................... 24 5.5. frsldCapabilities ......................................... 24
6. Persistence of Data ......................................... 24 6. Persistence of Data ......................................... 24
7. Object Definitions .......................................... 24 7. Object Definitions .......................................... 24
8. Acknowledgments ............................................. 61 8. Acknowledgments ............................................. 61
9. References .................................................. 62 9. References .................................................. 61
10. Security Considerations .................................... 65 10. Security Considerations .................................... 63
11. Authors' Addresses ......................................... 65 11. Authors' Addresses ......................................... 63
12. Copyright Section .......................................... 66 12. Full Copyright Statement ................................... 64
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
Management Information (SMI) is called SMIv1 and described in RFC Management Information (SMI) is called SMIv1 and described in STD
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC second version, called SMIv2, is described in STD 58, RFC 2578
2580 [7]. [5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
The third version of the message protocol is called SNMPv3 and 1906 [10]. The third version of the message protocol is called
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations and described in STD 15, RFC 1157 [8]. A second set of protocol
associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2575 the view-based access control mechanism described in RFC 2575
[15]. [15].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16]. can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Conventions 2. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in they appear in this document, are to be interpreted as described in
RFC 2119 [22]. RFC 2119 [22].
skipping to change at page 5, line 7 skipping to change at page 4, line 35
o Delay - The amount of time elapsed, in microseconds, from the time o Delay - The amount of time elapsed, in microseconds, from the time
a frame exits the source to the time it reaches the destination. a frame exits the source to the time it reaches the destination.
NOTE: FRF.13 [17] defines this value in terms of milliseconds. NOTE: FRF.13 [17] defines this value in terms of milliseconds.
o Frame Delivery Ratio - The ratio of the number of frames delivered o Frame Delivery Ratio - The ratio of the number of frames delivered
to the destination versus the number of frames sent by the source. to the destination versus the number of frames sent by the source.
This ratio can be further divided by inspecting either only the This ratio can be further divided by inspecting either only the
frames within the CIR or only the frames in excess of the CIR. frames within the CIR or only the frames in excess of the CIR.
o Data Delivery Ratio - The ratio of the amount of data delivered to o Data Delivery Ratio - The ratio of the amount of data delivered to
the destination versus the amount of data sent by the source. This the destination versus the amount of data sent by the source.
ratio can be further divided by inspecting either only the data This ratio can be further divided by inspecting either only the
within the CIR or only the data in excess of the CIR. data 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 module. 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].
o Logical Port - This term is used to model the Frame Relay o Logical Port - This term is used to model the Frame Relay
"interface" on a device. [18] "interface" on a device [18].
o NNI - Network to Network Interface. [18] o NNI - Network to Network Interface [18].
o Permanent Virtual Connection (PVC) - A virtual connection that has o Permanent Virtual Connection (PVC) - A virtual connection that has
its end-points and bearer capabilities defined at subscription its end-points and bearer capabilities defined at subscription
time. [18] time [18].
o Reference Point (RP) - The point of reference within the network o Reference Point (RP) - The point of reference within the network
model at which the calculations or data collection takes place. model at which the calculations or data collection takes place.
o UNI - User to Network Interface. [18] o UNI - User to Network Interface [18].
3.3. Network Model 3.3. Network Model
The basic model, as illustrated in figure 1 below, contains two frame The basic model, as illustrated in figure 1 below, contains two frame
relay DTE endpoints connected to a network cloud via a frame relay relay DTE endpoints connected to a network cloud via a frame relay
UNI interface. The network cloud can contain zero or more internal UNI interface. The network cloud can contain zero or more internal
frame relay NNI connections that interconnect multiple networks. The frame relay NNI connections that interconnect multiple networks. The
calculations and data collection can be performed at any reference calculations and data collection can be performed at any reference
point within the network. point within the network.
+-------------+ +-------------+ +-------------+ +-------------+
| Frame Relay | | Frame Relay | | Frame Relay | | Frame Relay |
| DTE Device | | DTE Device | | DTE Device | | DTE Device |
+------+------+ +------+------+ +------+------+ +------+------+
| | | |
UNI UNI UNI UNI
skipping to change at page 6, line 27 skipping to change at page 6, line 8
+------+------+ NNI +-------------+ NNI +------+------+ +------+------+ NNI +-------------+ NNI +------+------+
| Network A +------------+ Network B +------------+ Network C | | Network A +------------+ Network B +------------+ Network C |
+-------------+ Connection +-------------+ Connection +-------------+ +-------------+ Connection +-------------+ Connection +-------------+
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 module are shown in figure 2 below. For completeness, the in the MIB module are shown in figure 2 below. For completeness, the
module also allows for proprietary reference points which MAY exist module also allows for proprietary reference points which MAY exist
anywhere in the network that is not a previously defined reference anywhere in the network that is not a previously defined reference
point. The meaning of the proprietary reference points is point. The meaning of the proprietary reference points is
insignificant unless 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 |
+------------------------------------------+ +------------------------------------------+
| Frame Relay Network | Frame Relay Network
| +----------------------------------+ | +----------------------------------+
| | +------------------------------+ | | | +------------------------------+ |
| | | +---------+ +---------+ | | | | | +---------+ +---------+ | |
| | | | | | Traffic | | | | | | | | | Traffic | | |
+--(Ingress RP)--- L1 / L2 --- Policing| | | +--(Ingress RP)--- L1 / L2 --- Policing| | |
| | | Control | | Engine | | | | | | Control | | Engine | | |
| | +---------+ +----|----+ | | | | +---------+ +----|----+ | |
| | | | | | | | | |
| | (Traffic Policing RP)| | | | (Traffic Policing RP)| |
| +------------------|-----------+ | | +------------------|-----------+ |
| Ingress Node | | | Ingress Node | |
| | | | | |
| +-----------|-----------+ | | +-----------|-----------+ |
| | Intermediate Nodes | | | | Intermediate Nodes | |
| +-----------|-----------+ | | +-----------|-----------+ |
| | | | | |
| Egress Node | | | Egress Node | |
| +--------------|-----------+ | | +--------------|-----------+ |
| | (Egress Queue Input RP) | | | | (Egress Queue Input RP) | |
| | | | | | | | | |
| | +-------+------+ | | | | +-------+------+ | |
| | | Egress Queue | | | | | | Egress Queue | | |
| | +-------+------+ | | | | +-------+------+ | |
| | | | | | | | | |
| | (Egress Queue Output RP) | | | | (Egress Queue Output RP) | |
| +--------------|-----------+ | | +--------------|-----------+ |
+--------------------|-------------+ +--------------------|-------------+
Frame Relay Destination | Frame Relay Destination |
+---------------------------+ +-----------+ +---------------------------+ +-----------+
|+-----------+ +-----------+| | |+-----------+ +-----------+| |
|| | |Measurement|| | || | |Measurement|| |
||Frame Relay---Engine --(Destination RP)--+ ||Frame Relay---Engine --(Destination RP)--+
||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 module sources and frame destinations. The definitions in this MIB module
apply to the interaction of a pair of devices on the network path. apply to the interaction of a pair of devices on the network path.
The same device can potentially use different reference points for The same device can potentially use different reference points for
calculation and collection of the statistics based on whether the calculation and collection of the statistics based on whether the
referenced frame is sent or received by the device. When the device referenced frame is sent or received by the device. When the device
is acting as a frame source, the value of frsldPvcCtrlTransmitRP is acting as a frame source, the value of frsldPvcCtrlTransmitRP
reflects the reference point used for all source calculations reflects the reference point used for all source calculations
pertaining to the specified PVC. When the device is acting as a frame pertaining to the specified PVC. When the device is acting as a
destination, the value of frsldPvcCtrlReceiveRP reflects the frame destination, the value of frsldPvcCtrlReceiveRP reflects the
reference point used for all destination calculations pertaining to reference point used for all destination calculations pertaining to
the specified PVC. 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
frames going in the opposite direction, there is no requirement for frames going in the opposite direction, there is no requirement for
them to be so. them to be so.
It can be seen from the above example that a total of four reference It can be seen from the above example that a total of four reference
points are required in order to collect information for both points are required in order to collect information for both
directions of traffic flow. The reference points represent the directions of traffic flow. The reference points represent the
transmit and receive directions at both ends of a PVC. If a device transmit and receive directions at both ends of a PVC. If a device
has knowledge of the information from the remote device, it is has knowledge of the information from the remote device, it is
possible to collect the statistics from a single device. This is not possible to collect the statistics from a single device. This is not
always the case. In most instances, two devices will need to be always the case. In most instances, two devices will need to be
monitored to capture a complete description of the service level on a monitored to capture a complete description of the service level on a
PVC. The reference points a single device is capable of monitoring PVC. The reference points a single device is capable of monitoring
are contained in the frsldRPCaps object. are contained in the frsldRPCaps object.
3.5. Measurement Methodology 3.5. Measurement Methodology
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
independent of the data that is actually collected. be 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 module. They The following sections describe how to use this MIB module. They
include 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
skipping to change at page 9, line 44 skipping to change at page 9, line 43
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 module. They are provided specifically to aid in the in this MIB module. They are provided specifically to aid in the
ensured network management operations of this MIB module with respect ensured network management operations of this MIB module with respect
to row creation and modification. to row creation and modification.
An additional four objects are provided to report and control memory An additional four objects are provided to report and control memory
the utilization of this MIB module. These objects are the utilization of this MIB module. These objects are
frsldMaxPvcCtrls, frsldNumPvcCtrls, frsldMaxSmplCtrls are frsldMaxPvcCtrls, frsldNumPvcCtrls, frsldMaxSmplCtrls are
frsldNumSmplCtrls. Together, they allow a manager to control the frsldNumSmplCtrls. Together, they allow a manager to control the
amount of memory allocated for specific utilization by this MIB amount of memory allocated for specific utilization by this MIB
module. This is done by setting the maximum allowed allocation of module. This is done by setting the maximum allowed allocation of
controls. controls.
skipping to change at page 10, line 45 skipping to change at page 10, line 43
of frames observed on the local device only. In this case, the of frames observed on the local device only. In this case, the
objects of the FrsldPvcDataEntry row reporting what happened on the objects of the FrsldPvcDataEntry row reporting what happened on the
remote device are not available. remote device are not available.
The following list shows the possible valid reference points for an The following list shows the possible valid reference points for an
FRF.13 SLA from the source reference point to the destination FRF.13 SLA from the source reference point to the destination
reference point in both directions. reference point in both directions.
o Local Information Only o Local Information Only
Local Device: srcLocalRP, desLocalRP Local Device: srcLocalRP, desLocalRP
Remote Device: srcLocalRP, desLocalRP Remote Device: srcLocalRP, desLocalRP
o Remote Information Only o Remote Information Only
Local Device: srcRemoteRP, desRemoteRP Local Device: srcRemoteRP, desRemoteRP
Remote Device: srcRemoteRP, desRemoteRP Remote Device: srcRemoteRP, desRemoteRP
o Mixed Two Device Model 1 (Local Device Always Transmitter) o Mixed Two Device Model 1 (Local Device Always Transmitter)
Local Device: srcLocalRP, desRemoteRP Local Device: srcLocalRP, desRemoteRP
Remote Device: srcLocalRP, desRemoteRP Remote Device: srcLocalRP, desRemoteRP
o Mixed Two Device Model 2 (Local Device Always Receiver) o Mixed Two Device Model 2 (Local Device Always Receiver)
Local Device: srcRemoteRP, desLocalRP Local Device: srcRemoteRP, desLocalRP
Remote Device: srcRemoteRP, desLocalRP Remote Device: srcRemoteRP, desLocalRP
o Mixed One Device Model 1 (Directional Rows) o Mixed One Device Model 1 (Directional Rows)
First Row: srcRemoteRP, desLocalRP (Receiver Row) First Row: srcRemoteRP, desLocalRP (Receiver Row)
Second Row: srcLocalRP, desRemoteRP (Sender Row) Second Row: srcLocalRP, desRemoteRP (Sender Row)
o Mixed One Device Model 2 (Device Based Rows) o Mixed One Device Model 2 (Device Based Rows)
First Row: srcLocalRP, desLocalRP (Local Row) First Row: srcLocalRP, desLocalRP (Local Row)
Second Row: srcRemoteRP, desRemoteRP (Remote Row) Second Row: srcRemoteRP, desRemoteRP (Remote Row)
Each of the above combinations is valid and provides the same Each of the above combinations is valid and provides the same
information. information.
The following steps are recommended to find which reference points The following steps are recommended to find which reference points
need to be configured: need to be configured:
1) Locate both of the devices at either end of the PVC to be 1) Locate both of the devices at either end of the PVC to be
monitored. monitored.
2) Determine the capabilities by referencing the frsldRPCaps object 2) Determine the capabilities by referencing the frsldRPCaps object
of each device. of each device.
3) Locate the best combination of the two devices such that the 3) Locate the best combination of the two devices such that the
necessary reference points are all represented. necessary reference points are all represented.
4) If any one of the necessary reference points does not exist in 4) If any one of the necessary reference points does not exist in the
the combination of the two devices, it is not possible to combination of the two devices, it is not possible to monitor the
monitor the FRF.13 defined SLA between the two reference point FRF.13 defined SLA between the two reference point on the PVC.
on the PVC.
3.6.2.1. Graphical Examples of Reference Points 3.6.2.1. Graphical Examples of Reference Points
FRF.13 [17] defines three specific combinations of reference points: FRF.13 [17] defines three specific combinations of reference points:
Edge-to-Edge Interface, Edge-to-Edge Egress Queue and End-to-End. Edge-to-Edge Interface, Edge-to-Edge Egress Queue and End-to-End.
Examples of valid reference points that may be used for each of these Examples of valid reference points that may be used for each of these
are discussed in the sections below. are discussed in the sections below.
It is often the case that a device knows as a minimum either only It is often the case that a device knows as a minimum either only
skipping to change at page 12, line 38 skipping to change at page 12, line 35
| +-----+ | | +-----+ | | +-----+ | | +-----+ |
+-------------+ +-------------+ +-------------+ +-------------+
where (A), (B), (C) and (D) are reference points where (A), (B), (C) and (D) are reference points
Figure 3 Figure 3
For devices with only local knowledge, one row is required on each For devices with only local knowledge, one row is required on each
device as follows: device as follows:
(A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2)
(B) frsldPvcCtlrReceiveRP for Device 2 = eqoRxLocalRP(5) (B) frsldPvcCtlrReceiveRP for Device 2 = eqoRxLocalRP(5)
(C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2)
(D) frsldPvcCtlrReceiveRP for Device 1 = eqoRxLocalRP(5) (D) frsldPvcCtlrReceiveRP for Device 1 = eqoRxLocalRP(5)
In which a single row is created on Device 1 containing reference In which a single row is created on Device 1 containing reference
points (A) and (D), and a single row is created on Device 2 points (A) and (D), and a single row is created on Device 2
containing reference points (C) and (B). containing reference points (C) and (B).
For devices with both local and remote knowledge, the two rows can For devices with both local and remote knowledge, the two rows can
exist in any combination on either device. For this example, the exist in any combination on either device. For this example, the
transmitting devices will be responsible for information regarding transmitting devices will be responsible for information regarding
the flow for which they are the origin. Only one row is required per the flow for which they are the origin. Only one row is required per
device for this example. device for this example.
(A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2)
(B) frsldPvcCtlrReceiveRP for Device 1 = eqoRxRemoteRP(11) (B) frsldPvcCtlrReceiveRP for Device 1 = eqoRxRemoteRP(11)
(C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2)
(D) frsldPvcCtlrReceiveRP for Device 2 = eqoRxRemoteRP(11) (D) frsldPvcCtlrReceiveRP for Device 2 = eqoRxRemoteRP(11)
3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example
Device 1 Device 2 Device 1 Device 2
+-------------+ +-------------+ +-------------+ +-------------+
| Ingress | | Egress | | Ingress | | Egress |
| +-----+ | | +-----+ | | +-----+ | | +-----+ |
|(A)| | | Traffic Flow |(B)| | | |(A)| | | Traffic Flow |(B)| | |
-->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->-->
| | | | From Device 1 to 2 | | | | | | | | From Device 1 to 2 | | | |
skipping to change at page 13, line 41 skipping to change at page 13, line 39
| +-----+ | | +-----+ | | +-----+ | | +-----+ |
+-------------+ +-------------+ +-------------+ +-------------+
where (A), (B), (C) and (D) are reference points where (A), (B), (C) and (D) are reference points
Figure 4 Figure 4
For devices with only local knowledge, one row is required on each For devices with only local knowledge, one row is required on each
device as follows: device as follows:
(A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2)
(B) frsldPvcCtlrReceiveRP for Device 2 = eqiRxLocalRP(4) (B) frsldPvcCtlrReceiveRP for Device 2 = eqiRxLocalRP(4)
(C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2)
(D) frsldPvcCtlrReceiveRP for Device 1 = eqiRxLocalRP(4) (D) frsldPvcCtlrReceiveRP for Device 1 = eqiRxLocalRP(4)
In which a single row is created on Device 1 containing reference In which a single row is created on Device 1 containing reference
points (A) and (D), and a single row is created on Device 2 points (A) and (D), and a single row is created on Device 2
containing reference points (C) and (B). containing reference points (C) and (B).
For devices with both local and remote knowledge, the two rows can For devices with both local and remote knowledge, the two rows can
exist in any combination on either device. For this example, the exist in any combination on either device. For this example, the
transmitting devices will be responsible for information regarding transmitting devices will be responsible for information regarding
the flow for which they are the origin. Only one row is required per the flow for which they are the origin. Only one row is required per
device for this example. device for this example.
(A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2)
(B) frsldPvcCtlrReceiveRP for Device 1 = eqiRxRemoteRP(10) (B) frsldPvcCtlrReceiveRP for Device 1 = eqiRxRemoteRP(10)
(C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2)
(D) frsldPvcCtlrReceiveRP for Device 2 = eqiRxRemoteRP(10) (D) frsldPvcCtlrReceiveRP for Device 2 = eqiRxRemoteRP(10)
3.6.2.1.3. End-to-End Using Reference Point Example 3.6.2.1.3. End-to-End Using Reference Point Example
Device 1 Device 2 Device 1 Device 2
+-------------+ +-------------+ +-------------+ +-------------+
| Source | | Destination | | Source | | Destination |
| +-----+ | | +-----+ | | +-----+ | | +-----+ |
|(A)| | | Traffic Flow | | |(B)| |(A)| | | Traffic Flow | | |(B)|
-->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->-->
| | | | From Device 1 to 2 | | | | | | | | From Device 1 to 2 | | | |
skipping to change at page 14, line 47 skipping to change at page 14, line 45
| +-----+ | | +-----+ | | +-----+ | | +-----+ |
+-------------+ +-------------+ +-------------+ +-------------+
where (A), (B), (C) and (D) are reference points where (A), (B), (C) and (D) are reference points
Figure 5 Figure 5
For devices with only local knowledge, one row is required on each For devices with only local knowledge, one row is required on each
device as follows: device as follows:
(A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1)
(B) frsldPvcCtlrReceiveRP for Device 2 = desLocalRP(1) (B) frsldPvcCtlrReceiveRP for Device 2 = desLocalRP(1)
(C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1)
(D) frsldPvcCtlrReceiveRP for Device 1 = desLocalRP(1) (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1)
(D) frsldPvcCtlrReceiveRP for Device 1 = desLocalRP(1)
In which a single row is created on Device 1 containing reference In which a single row is created on Device 1 containing reference
points (A) and (D), and a single row is created on Device 2 points (A) and (D), and a single row is created on Device 2
containing reference points (C) and (B). containing reference points (C) and (B).
For devices with both local and remote knowledge, the two rows can For devices with both local and remote knowledge, the two rows can
exist in any combination on either device. For this example, the exist in any combination on either device. For this example, the
transmitting devices will be responsible for information regarding transmitting devices will be responsible for information regarding
the flow for which they are the origin. Only one row is required per the flow for which they are the origin. Only one row is required per
device for this example. device for this example.
(A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1)
(B) frsldPvcCtlrReceiveRP for Device 1 = desRemoteRP(7) (B) frsldPvcCtlrReceiveRP for Device 1 = desRemoteRP(7)
(C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1)
(D) frsldPvcCtlrReceiveRP for Device 2 = desRemoteRP(7) (D) frsldPvcCtlrReceiveRP for Device 2 = desRemoteRP(7)
3.6.3. Creation Process 3.6.3. Creation Process
In some cases, devices will automatically populate the rows of PVC In some cases, devices will automatically populate the rows of PVC
Control Table and potentially the Sample Control Table. However, in Control Table and potentially the Sample Control Table. However, in
many cases, it may be necessary for a network manager to manually many cases, it may be necessary for a network manager to manually
create rows. create rows.
Manual creation of rows requires the following steps: Manual creation of rows requires the following steps:
1) Ensure the PVC exists between the two devices. 1) Ensure the PVC exists between the two devices.
2) Determine the necessary reference points for row creation. 2) Determine the necessary reference points for row creation.
3) Create the row(s) in each device as needed. 3) Create the row(s) in each device as needed.
4) Create the row(s) in the sample control tables if desired. 4) Create the row(s) in the sample control tables if desired.
3.6.4. Destruction Process 3.6.4. Destruction Process
3.6.4.1. Manual Row Destruction 3.6.4.1. Manual Row Destruction
Manual row destruction is straight forward. Any row can be destroyed Manual row destruction is straight forward. Any row can be destroyed
and the resources allocated to it are freed by setting the value of and the resources allocated to it are freed by setting the value of
its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus) its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus)
to destroy(6). It should be noted that when frsldPvcCtrlStatus is to destroy(6). It should be noted that when frsldPvcCtrlStatus is
set to destroy(6) all associated sample control, sample and data set to destroy(6) all associated sample control, sample and data
table rows will also be destroyed. Similarly, when table rows will also be destroyed. Similarly, when
frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be
destroyed. The frsldPvcCtrlPurge objects do not apply to manual row destroyed. The frsldPvcCtrlPurge objects do not apply to manual row
skipping to change at page 18, line 17 skipping to change at page 17, line 48
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 Module in Calculation of Service Level Definitions 3.6.7. Use of MIB Module in Calculation of Service Level Definitions
The objects in this MIB module can be used to calculate the The objects in this MIB module can be used to calculate the
statistics defined in FRF.13 [17]. The description below describes statistics defined in FRF.13 [17]. The description below describes
the calculations for one direction of the data flow, i.e. data sent the calculations for one direction of the data flow, i.e., data sent
from 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 module 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 module 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 receive reference point that were delivered in excess of The number of frames received by the receiving device through
CIR. This is represented within the MIB module by one of the receive reference point that were delivered in excess of
frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE, CIR. This is represented within the MIB module by one of
frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE. frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE,
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
represented within the MIB module by one of is represented within the MIB module by one of
frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC, frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC,
frsldPvcSmplFrOfferedC, or 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 module 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 module 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 module 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
represented within the MIB module by one of is represented within the MIB module by one of
frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC, frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC,
frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC. frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC.
o DataOfferedE o DataOfferedE
The number of octets offered by the transmitting device through
the transmit reference point that were sent in excess of CIR. The number of octets offered by the transmitting device through
This is represented within the MIB module by one of the transmit reference point that were sent in excess of CIR.
frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE, This is represented within the MIB module by one of
frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE. frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE,
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
of interest. This is represented within the MIB module by interval of interest. This is represented within the MIB
either frsldPvcDataUnavailableTime or module by either frsldPvcDataUnavailableTime or
frsldPvcSmplUnavailableTime. 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
MIB module by either frsldPvcDataUnavailables or the 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
variable described in DelayAvg above. The delay may be calculated as MIB variable described in DelayAvg above. The delay may be
either round trip or one way, and this information is held in the calculated as either round trip or one way, and this information is
frsldPvcCtrlDelayType MIB variable. If the delay be calculated as held in the frsldPvcCtrlDelayType MIB variable. If the delay be
round trip, the value of DelayAvg represents the average of the total calculated as round trip, the value of DelayAvg represents the
delays of the round trips. In this case, the manager SHOULD divide average of the total delays of the round trips. In this case, the
the value returned by the agent by two to obtain the frame transfer manager SHOULD divide the value returned by the agent by two to
delay. In the case that frsldPvcCtrlDelayType is oneWay, the value obtain the frame transfer delay. In the case that
of DelayAvg represents the average of the frame transfer delays and frsldPvcCtrlDelayType is oneWay, the value of DelayAvg represents the
SHOULD be used as is. average of the frame transfer delays and SHOULD be used as is.
3.6.9. Frame Delivery Ratio 3.6.9. Frame Delivery Ratio
The frame delivery ratio is defined as the total number of frames The frame delivery ratio is defined as the total number of frames
delivered to the destination divided by the frames offered by the delivered to the destination divided by the frames offered by the
source. The destination values can be obtained using FrDeliveredC source. The destination values can be obtained using FrDeliveredC
and FrDeliveredE. The source values can be obtained using FrOfferedC and FrDeliveredE. The source values can be obtained using FrOfferedC
and FrOfferedE. and FrOfferedE.
FrDeliveredC + FrDeliveredE FrDeliveredC + FrDeliveredE
skipping to change at page 21, line 22 skipping to change at page 21, line 10
FrDeliveredE FrDeliveredE
Excess Frame Delivery Ratio = ------------ Excess Frame Delivery Ratio = ------------
FrOfferedE FrOfferedE
3.6.10. Data Delivery Ratio 3.6.10. Data Delivery Ratio
The data delivery ratio is defined as the total amount of data The data delivery ratio is defined as the total amount of data
delivered to the destination divided by the data offered by the delivered to the destination divided by the data offered by the
source. The destination values can be obtained using DataDeliveredC source. The destination values can be obtained using DataDeliveredC
and DataDeliveredE. The source values can be obtained using and DataDeliveredE. The source values can be obtained using
DataOfferedC and DataOfferedE. DataOfferedC and DataOfferedE.
DataDeliveredC + DataDeliveredE DataDeliveredC + DataDeliveredE
Data Delivery Ratio = ------------------------------- Data Delivery Ratio = -------------------------------
DataOfferedC + DataOfferedE DataOfferedC + DataOfferedE
DataDeliveredC DataDeliveredC
Committed Data Delivery Ratio = -------------- Committed Data Delivery Ratio = --------------
DataOfferedC DataOfferedC
skipping to change at page 22, line 30 skipping to change at page 22, line 15
Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime
--------------------------------------------- ---------------------------------------------
Unavailables Unavailables
4. Relation to Other MIB Modules 4. Relation to Other MIB Modules
There is no explicit relation to any other frame relay MIB module nor There is no explicit relation to any other frame relay MIB module nor
are any required to implement this MIB module. However, there is a are any required to implement this MIB module. However, there is a
need for knowledge of ifIndexes and some understanding of DLCIs. The need for knowledge of ifIndexes and some understanding of DLCIs. The
ifIndex information can be found in the IF-MIB [21] which is ifIndex information can be found in the IF-MIB [21] which is
required. The DLCI information can be found in either the Frame Relay required. The DLCI information can be found in either the Frame
DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC Relay DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB
2954) [18]; however, neither is required. (RFC 2954) [18]; however, neither is required.
Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to
active(1) the system can be in one of the following three states: active(1) the system can be in one of the following three states:
(1) The respective DLCI is known and is active. This corresponds to a (1) The respective DLCI is known and is active. This corresponds to
state in which frPVCEndptRowStatus is active(1) and a 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 2954) [18]. For the Frame Frame Relay Network Services MIB (RFC 2954) [18]. For the Frame
Relay DTE MIB, the same state is shown by frCircuitRowStatus of Relay DTE MIB, the same state is shown by frCircuitRowStatus of
active(1) and frCircuitState of active(2). active(1) and frCircuitState of active(2).
(2) The respective DLCI has not been created. This corresponds to a (2) The respective DLCI has not been created. This corresponds to a
state in which the row with either frPVCEndptDLCIIndex or state in which the row with either frPVCEndptDLCIIndex or
frCircuitDlci equal to the respective DLCI does not exist in frCircuitDlci equal to the respective DLCI does not exist in
either the frPVCEndptTable or the frCircuitTable respectively. either the frPVCEndptTable or the frCircuitTable respectively.
(3) The respective DLCI has just been removed. This corresponds to a (3) The respective DLCI has just been removed. This corresponds to a
state in which either frPVCEndptRowStatus is no longer active(1) state in which either frPVCEndptRowStatus is no longer active(1)
or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for
the Frame Relay Network Services MIB (RFC 2954) [18]. For the the Frame Relay Network Services MIB (RFC 2954) [18]. For the
Frame Relay DTE MIB, the same state is shown when either Frame Relay DTE MIB, the same state is shown when either
frCircuitRowStatus is no longer active(1) or frCircuitState is no frCircuitRowStatus is no longer active(1) or frCircuitState is no
longer active(2). longer active(2).
For the first case, the row in the frsldPvcDataTable will be filled. For the first case, the row in the frsldPvcDataTable will be filled.
If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective
DLCI is also `active' the frsldPvcSampleTable will be filled as well. DLCI is also `active' the frsldPvcSampleTable will be filled as well.
For the second case, the respective rows will not be added to any of For the second case, the respective rows will not be added to any of
the data or sample tables and frsldPvcCtrlStatus SHOULD report the data or sample tables and frsldPvcCtrlStatus SHOULD report
skipping to change at page 25, line 4 skipping to change at page 24, line 41
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Gauge32, Integer32, Counter32, Gauge32, Integer32,
Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI
CounterBasedGauge64 FROM HCNUM-TC CounterBasedGauge64 FROM HCNUM-TC
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TimeStamp FROM SNMPv2-TC TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB ifIndex FROM IF-MIB
DLCI FROM FRAME-RELAY-DTE-MIB; DLCI FROM FRAME-RELAY-DTE-MIB;
frsldMIB MODULE-IDENTITY frsldMIB MODULE-IDENTITY
LAST-UPDATED "200109251500Z" -- September 25, 2001 LAST-UPDATED "200201030000Z" -- January 3, 2002
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 Vivace Networks
Email: amalis@lucent.com Email: Andy.Malis@vivacenetworks.com
WG editor: Robert Steinberger WG editor: Robert Steinberger
Paradyne Networks and Paradyne Networks and
Fujitsu Network Communications Fujitsu Network Communications
Email: robert.steinberger@fnc.fujitsu.com Email: robert.steinberger@fnc.fujitsu.com
Co-author: Orly Nicklass Co-author: Orly Nicklass
RAD Data Communications Ltd. RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il" EMail: Orly_n@rad.co.il"
DESCRIPTION DESCRIPTION
"The MIB module to describe generic objects for "The MIB module to describe generic objects for
FRF.13 Frame Relay Service Level Definitions." FRF.13 Frame Relay Service Level Definitions."
REVISION "200109251500Z" -- September 25, 2001 REVISION "200201030000Z" -- January 3, 2002
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx" "Initial version, published as RFC 3202"
-- xxxx to be assigned by RFC Editor ::= { mib-2 95 }
::= { mib-2 xxx } -- RFC editor - IANA assigns xxx
-- --
-- Textual Conventions -- Textual Conventions
-- --
FrsldTxRP ::= TEXTUAL-CONVENTION FrsldTxRP ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reference point a PVC uses for calculation "The reference point a PVC uses for calculation
of transmitter related statistics. of transmitter related statistics.
skipping to change at page 29, line 32 skipping to change at page 29, line 19
table below. This row SHOULD not be removed until table below. This row SHOULD not be removed until
the status is changed to deleted. the status is changed to deleted.
When this object is set to destroy(6), all associated When this object is set to destroy(6), all associated
sample and data table rows will also be deleted. sample and data table rows will also be deleted.
When this object is changed from active(1) to any When this object is changed from active(1) to any
other valid value, the defined purge behavior will other valid value, the defined purge behavior will
affect the data and sample tables. affect the data and sample tables.
The rows added to this table MUST have a valid The rows added to this table MUST have a valid
ifIndex and an ifType related to frame relay. Further, ifIndex and an ifType related to frame relay. Further,
the reference points referred to by frsldPvcCtrlTransmitRP the reference points referred to by frsldPvcCtrlTransmitRP
and frsldPvcCtrlReceiveRP MUST be supported (see the and frsldPvcCtrlReceiveRP MUST be supported (see the
frsldRPCaps object). frsldRPCaps object).
If at any point the row is not in the active(1) state If at any point the row is not in the active(1) state
and the DLCI no longer exists, the state SHOULD and the DLCI no longer exists, the state SHOULD
report notReady(3). report notReady(3).
The data in this table SHOULD persist through power The data in this table SHOULD persist through power
cycles. The symantics of readiness for the rows still cycles. The symantics of readiness for the rows still
skipping to change at page 35, line 10 skipping to change at page 34, line 44
frsldPvcDataTable OBJECT-TYPE frsldPvcDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldPvcDataEntry SYNTAX SEQUENCE OF FrsldPvcDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Frame Relay Service Level Definitions "The Frame Relay Service Level Definitions
data table. data table.
This table contains accumulated values of the This table contains accumulated values of the
collected data. It is the table that should be collected data. It is the table that should be
referenced by external polling mechanisms if referenced by external polling mechanisms if
time based polling be desired." time based polling be desired."
::= { frsldObjects 3 } ::= { frsldObjects 3 }
frsldPvcDataEntry OBJECT-TYPE frsldPvcDataEntry OBJECT-TYPE
SYNTAX FrsldPvcDataEntry SYNTAX FrsldPvcDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Frame Relay Service Level "An entry in the Frame Relay Service Level
skipping to change at page 36, line 9 skipping to change at page 35, line 43
} }
frsldPvcDataMissedPolls OBJECT-TYPE frsldPvcDataMissedPolls OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of polls that have been determined "The total number of polls that have been determined
to be missed. These polls are typically associated to be missed. These polls are typically associated
with the calculation of delay but may also be with the calculation of delay but may also be
used for the calculation of other statistics. If an used for the calculation of other statistics. If an
anticipated poll is not received in a reasonable anticipated poll is not received in a reasonable
amount of time, it should be counted as missed. amount of time, it should be counted as missed.
The value used to determine the reasonable amount The value used to determine the reasonable amount
of time is contained in frsldPvcCtrlDelayTimeOut. of time is contained in frsldPvcCtrlDelayTimeOut.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
::= { frsldPvcDataEntry 1 } ::= { frsldPvcDataEntry 1 }
skipping to change at page 39, line 16 skipping to change at page 38, line 50
"FRF.13: Section 5.1 (DataOfferede)" "FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcDataEntry 9 } ::= { frsldPvcDataEntry 9 }
frsldPvcDataHCFrDeliveredC OBJECT-TYPE frsldPvcDataHCFrDeliveredC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version sent within CIR. This object is a 64-bit version
of frsldPvcDataFrDeliveredC. of frsldPvcDataFrDeliveredC.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)" "FRF.13: Section 4.1 (FramesDeliveredc)"
::= { frsldPvcDataEntry 10 } ::= { frsldPvcDataEntry 10 }
frsldPvcDataHCFrDeliveredE OBJECT-TYPE frsldPvcDataHCFrDeliveredE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR. This object is a 64-bit sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataFrDeliveredE. version of frsldPvcDataFrDeliveredE.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesDeliverede)" "FRF.13: Section 4.1 (FramesDeliverede)"
::= { frsldPvcDataEntry 11 } ::= { frsldPvcDataEntry 11 }
frsldPvcDataHCFrOfferedC OBJECT-TYPE frsldPvcDataHCFrOfferedC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataFrOfferedC. a 64-bit version of frsldPvcDataFrOfferedC.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)" "FRF.13: Section 4.1 (FramesOfferedc)"
::= { frsldPvcDataEntry 12 } ::= { frsldPvcDataEntry 12 }
frsldPvcDataHCFrOfferedE OBJECT-TYPE frsldPvcDataHCFrOfferedE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were offered through "The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR. This frsldPvcCtrlTransmitRP in excess of the CIR. This
object is a 64-bit version of frsldPvcDataFrOfferedE. object is a 64-bit version of frsldPvcDataFrOfferedE.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)" "FRF.13: Section 4.1 (FramesOfferede)"
::= { frsldPvcDataEntry 13 } ::= { frsldPvcDataEntry 13 }
frsldPvcDataHCDataDeliveredC OBJECT-TYPE frsldPvcDataHCDataDeliveredC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version of sent within CIR. This object is a 64-bit version of
frsldPvcDataDataDeliveredC. frsldPvcDataDataDeliveredC.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)" "FRF.13: Section 5.1 (DataDeliveredc)"
::= { frsldPvcDataEntry 14 } ::= { frsldPvcDataEntry 14 }
frsldPvcDataHCDataDeliveredE OBJECT-TYPE frsldPvcDataHCDataDeliveredE OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were received at "The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR. This object is a 64-bit sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataDataDeliveredE. version of frsldPvcDataDataDeliveredE.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)" "FRF.13: Section 5.1 (DataDeliverede)"
::= { frsldPvcDataEntry 15 } ::= { frsldPvcDataEntry 15 }
frsldPvcDataHCDataOfferedC OBJECT-TYPE frsldPvcDataHCDataOfferedC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets that were offered through "The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataDataOfferedC. a 64-bit version of frsldPvcDataDataOfferedC.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system occur at re-initialization of the management system
and at other times as indicated by and at other times as indicated by
frsldPvcCtrlLastPurgeTime." frsldPvcCtrlLastPurgeTime."
REFERENCE REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)" "FRF.13: Section 5.1 (DataOfferedc)"
::= { frsldPvcDataEntry 16 } ::= { frsldPvcDataEntry 16 }
skipping to change at page 48, line 7 skipping to change at page 47, line 39
"FRF.13: Section 5.1 (DataOfferede)" "FRF.13: Section 5.1 (DataOfferede)"
::= { frsldPvcSampleEntry 13 } ::= { frsldPvcSampleEntry 13 }
frsldPvcSmplHCFrDeliveredC OBJECT-TYPE frsldPvcSmplHCFrDeliveredC OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
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 REFERENCE
"FRF.13: Section 4.1 (FramesDeliveredc)" "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
skipping to change at page 48, line 34 skipping to change at page 48, line 18
"FRF.13: Section 4.1 (FramesDeliverede)" "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 REFERENCE
"FRF.13: Section 4.1 (FramesOfferedc)" "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 REFERENCE
"FRF.13: Section 4.1 (FramesOfferede)" "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 REFERENCE
"FRF.13: Section 5.1 (DataDeliveredc)" "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 REFERENCE
"FRF.13: Section 5.1 (DataDeliverede)" "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 REFERENCE
"FRF.13: Section 5.1 (DataOfferedc)" "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 REFERENCE
"FRF.13: Section 5.1 (DataOfferede)" "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
skipping to change at page 51, line 22 skipping to change at page 51, line 6
frsldPvcCtrlDelayType(3), frsldPvcCtrlDelayType(3),
frsldPvcCtrlDelayTimeOut(4), frsldPvcCtrlDelayTimeOut(4),
frsldPvcCtrlPurge(5), frsldPvcCtrlPurge(5),
frsldPvcCtrlDeleteOnPurge(6) frsldPvcCtrlDeleteOnPurge(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the write capabilities "This object specifies the write capabilities
for the read-create objects of the PVC Control for the read-create objects of the PVC Control
table. If the corresponding bit is enabled (1), table. If the corresponding bit is enabled (1),
the agent supports writes to that object." the agent supports writes to that object."
::= { frsldCapabilities 1 } ::= { frsldCapabilities 1 }
frsldSmplCtrlWriteCaps OBJECT-TYPE frsldSmplCtrlWriteCaps OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
frsldSmplCtrlStatus(0), frsldSmplCtrlStatus(0),
frsldSmplCtrlBuckets(1) frsldSmplCtrlBuckets(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the write capabilities "This object specifies the write capabilities
for the read-create objects of the Sample Control for the read-create objects of the Sample Control
table. If the corresponding bit is enabled (1), table. If the corresponding bit is enabled (1),
the agent supports writes to that object." the agent supports writes to that object."
::= { frsldCapabilities 2 } ::= { frsldCapabilities 2 }
frsldRPCaps OBJECT-TYPE frsldRPCaps OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
srcLocalRP(0), srcLocalRP(0),
ingTxLocalRP(1), ingTxLocalRP(1),
tpTxLocalRP(2), tpTxLocalRP(2),
eqiTxLocalRP(3), eqiTxLocalRP(3),
eqoTxLocalRP(4), eqoTxLocalRP(4),
skipping to change at page 52, line 24 skipping to change at page 52, line 7
ingRxRemoteRP(19), ingRxRemoteRP(19),
tpRxRemoteRP(20), tpRxRemoteRP(20),
eqiRxRemoteRP(21), eqiRxRemoteRP(21),
eqoRxRemoteRP(22), eqoRxRemoteRP(22),
otherRxRemoteRP(23) otherRxRemoteRP(23)
} }
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 frsldMaxPvcCtrls OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of control rows that can be created "The maximum number of control rows that can be created
skipping to change at page 55, line 16 skipping to change at page 54, line 47
DESCRIPTION DESCRIPTION
"This group is mandatory whenever "This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported." frsldPvcSampleCtrlGroup is supported."
GROUP frsldPvcSampleGeneralGroup GROUP frsldPvcSampleGeneralGroup
DESCRIPTION DESCRIPTION
"This group is mandatory whenever "This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported." frsldPvcSampleCtrlGroup is supported."
OBJECT frsldPvcCtrlStatus OBJECT frsldPvcCtrlStatus
SYNTAX INTEGER { active(1) } -- subset of RowStatus SYNTAX RowStatus { active(1) } -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Row creation can be done outside of the scope of "Row creation can be done outside of the scope of
the SNMP protocol. If this object is implemented the SNMP protocol. If this object is implemented
with max-access of read-only, then the only value with max-access of read-only, then the only value
that MUST be returned is active(1) and that MUST be returned is active(1) and
frsldPvcCtrlWriteCaps MUST return 0 for the frsldPvcCtrlWriteCaps MUST return 0 for the
frsldPvcCtrlStatus(0) bit." frsldPvcCtrlStatus(0) bit."
OBJECT frsldPvcCtrlPurge OBJECT frsldPvcCtrlPurge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. If this object is "Write access is not required. If this object is
implemented with a max-access of read-only, then implemented with a max-access of read-only, then
the frsldPvcCtrlPurge(5) bit must return 0." 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. If this object is "Write access is not required. If this object is
implemented with a max-access of read-only, then implemented with a max-access of read-only, then
the frsldPvcCtrlDeleteOnPurge(6) bit must return the frsldPvcCtrlDeleteOnPurge(6) bit must return
0." 0."
OBJECT frsldMaxPvcCtrls OBJECT frsldMaxPvcCtrls
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the device either "Write access is not required if the device either
dynamically allocates memory or statically allocates dynamically allocates memory or statically allocates
a fixed number of entries. In the case of static a fixed number of entries. In the case of static
skipping to change at page 62, line 7 skipping to change at page 61, line 19
The editors would like to thank the following people for their The editors would like to thank the following people for their
helpful comments: helpful comments:
o Ken Rehbehn, Visual Networks o Ken Rehbehn, Visual Networks
o Santa Dasu, Quick Eagle Networks o Santa Dasu, Quick Eagle Networks
9. References 9. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, Describing SNMP Management Frameworks", RFC 2571, April 1999.
Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, STD Management Information for TCP/IP-based Internets", STD 16, RFC
16, Performance Systems International, Hughes LAN Systems, May 1990 1155, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
STD 16, Performance Systems International, Hughes LAN Systems, March RFC 1212, March 1991.
1991
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [4] Rose, M., "A Convention for Defining Traps for use with the
RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
and S. Waldbusser, "Structure of Management Information Version 2 M. and S. Waldbusser, "Structure of Management Information
(SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Braunschweig, SNMP Research, First Virtual Holdings, International
Network Services, April 1999
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First RFC 2579, April 1999.
Virtual Holdings, International Network Services, April 1999
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 58, RFC 2580, April 1999.
Virtual Holdings, International Network Services, April 1999
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Management Protocol", RFC 1157, STD 15, SNMP Research, Performance Network Management Protocol", STD 15, RFC 1157, May 1990.
Systems International, Performance Systems International, MIT
Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco "Introduction to Community-based SNMPv2", RFC 1901, January
Systems, Inc., Dover Beach Consulting, Inc., International Network 1996.
Services, January 1996.
[10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover (SNMPv2)", RFC 1906, January 1996.
Beach Consulting, Inc., International Network Services, January
1996.
[11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2572, April 1999.
Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999
[12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC for version 3 of the Simple Network Management Protocol
2574, IBM T. J. Watson Research, April 1999 (SNMPv3)", RFC 2574, April 1999.
[13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover Protocol (SNMPv2)", RFC 1905, January 1996.
Beach Consulting, Inc., International Network Services, January
1996.
[14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, April 1999.
Systems, April 1999
[15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2575, April 1999.
Cisco Systems, Inc., April 1999
[16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to [16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
Version 3 of the Internet-standard Network Management Framework", to Version 3 of the Internet-standard Network Management
RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., Framework", RFC 2570, April 1999.
Ericsson, Cisco Systems, April 1999
[17]Frame Relay Forum Technical Committee, "Service Level Definitions [17] Frame Relay Forum Technical Committee, "Service Level
Implementations Agreement", FRF.13, August 1998. Definitions Implementations Agreement", FRF.13, August 1998.
[18]Rehbehn, K., Fowler, D., "Definitions of Managed Objects for Frame [18] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects for
Relay Service", RFC 2954, Megisto Systems, Syndesis Limited, October Frame Relay Service", RFC 2954, October 2000.
2000.
[19]Waldbusser, S., "Remote Network Monitoring Management Information [19] Waldbusser, S., "Remote Network Monitoring Management
Base Version 2 using SMIv2", RFC 2021, International Network Information Base Version 2 using SMIv2", RFC 2021, January 1997.
Service, January 1997.
[20]Brown, C., Baker, F., "Management Information Base for Frame Relay [20] Brown, C. and F. Baker, "Management Information Base for Frame
DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, Relay DTEs Using SMIv2", RFC 2115, September 1997.
September 1997.
[21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC [21] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
2863, Cisco Systems, Argon Networks, June 2000. RFC 2863, June 2000.
[22]Bradner, S., "Key words for use in RFCs to Indicate Requirement [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, Harvard University, March 1997. Levels", BCP 14, RFC 2119, March 1997.
10. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
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.
11. Authors' Addresses 11. Authors' Addresses
Robert Steinberger Robert Steinberger
Fujitsu Network Communications Fujitsu Network Communications
2801 Telecom Parkway 2801 Telecom Parkway
Richardson, TX 75082 Richardson, TX 75082
Phone: 1-972-479-4739 Phone: 1-972-479-4739
EMail: robert.steinberger@fnc.fujitsu.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@rad.co.il
Email: Orly_n@rrad.co.il 12. Full Copyright Statement
12. Copyright Section
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 161 change blocks. 
373 lines changed or deleted 337 lines changed or added

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