Definitions of Managed Objects
for Frame Relay Service Level Definitions
June 14, 2000
draft-ietf-frnetmib-frmrelay-service-01.txt
Robert A. Steinberger
Paradyne Networks
rsteinberger@paradyne.com
Orly Nicklass, Ph.D
RAD Data Communications Ltd.
Orly_n@rad.co.il
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This memo defines an extension of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets. In particular, it defines objects for managing the Frame
Relay Service Level Definitions. This memo does not specify a
standard for the Internet community.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Expires December 2000 Steinberger & Nicklass [Page 1]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
Table of Contents
1. The SNMP Management Framework ............................... 3
2. Conventions ................................................. 4
3. Overview .................................................... 4
3.1. Frame Relay Service Level Definitions ..................... 4
3.2. Terminology ............................................... 5
3.3. Network Model ............................................. 5
3.4. Reference Points .......................................... 6
3.5. Measurement Methodology ................................... 8
3.6. Theory of Operation ....................................... 9
3.6.1. Capabilities Discovery .................................. 9
3.6.2. Determining Reference Points for Row Creation ........... 9
3.6.3. Creation Process ........................................ 11
3.6.4. Destruction Process ..................................... 11
3.6.4.1. Manual Row Destruction ................................ 11
3.6.4.2. Automatic Row Destruction ............................. 12
3.6.5. Modification Process .................................... 12
3.6.6. Collection Process ...................................... 12
3.6.6.1. Remote Polling ........................................ 12
3.6.6.2. Sampling .............................................. 13
3.6.6.3. User History .......................................... 14
3.6.7. Use of MIB in Calculation of Service Level Definitions .. 14
3.6.8. Delay ................................................... 16
3.6.9. Frame Delivery Ratio .................................... 16
3.6.10. Data Delivery Ratio .................................... 17
3.6.11. Service Availability ................................... 17
4. Relation to Other MIBs ...................................... 18
5. Structure of the MIB ........................................ 19
5.1. frsldPvcCtrlTable ......................................... 19
5.2. frsldSmplCtrlTable ........................................ 20
5.3. frsldPvcDataTable ......................................... 20
5.4. frsldPvcDataSampleTable ................................... 20
5.5. frsldPvcAvailSampleTable .................................. 20
5.6. frsldCapabilities ......................................... 20
6. Object Definitions .......................................... 20
7. Acknowledgments ............................................. 52
8. References .................................................. 54
9. Security Considerations ..................................... 56
10. Authors' Addresses ......................................... 56
11. Copyright Section .......................................... 57
Expires December 2000 Steinberger & Nicklass [Page 2]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC
2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations and
associated PDU formats is described in RFC 1905 [13].
o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
Expires December 2000 Steinberger & Nicklass [Page 3]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
2. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in
RFC 2119 [23].
3. Overview
This MIB addresses the items required to manage the Frame Relay
Forum's Implementation Agreement for Service Level Definitions
(FRF.13 [17]). At present, this applies to these values of the
ifType variable in the Internet-standard MIB:
o frameRelay (32)
o frameRelayService (44)
This section provides an overview and background of how to use this
MIB.
3.1. Frame Relay Service Level Definitions
The frame relay service level definitions address specific
characteristics of a frame relay service that can be used to
facilitate the following tasks:
o Evaluation of frame relay service providers, offerings or
products.
o Measurement of Quality of Service.
o Enforcement of Service Level Agreements.
o Planning or describing a frame relay network.
The following parameters are defined in FRF.13 [17] as a sufficient
set of values to accomplish the tasks previously stated.
o Delay - The amount of time elapsed, in microseconds, from the time
a frame exits the source to the time it reaches the destination.
NOTE: FRF.13 [17] defines this value in terms of milliseconds.
o Frame Delivery Ratio - The ratio of the number of frames delivered
to the destination versus the number of frames sent by the source.
This ratio can be further divided by inspecting either only the
Expires December 2000 Steinberger & Nicklass [Page 4]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
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
the destination versus the amount of data sent by the source. This
ratio can be further divided by inspecting either only the data
within the CIR or only the data in excess of the CIR.
o Service Availability - The amount of time the frame relay service
was not available. There are three types of availability
statistics defined in FRF.13 [17]: Mean Time to Repair, Virtual
Connection Availability, and Mean Time Between Service Outages.
The later two require information about the scheduled outage time.
It is assumed that scheduled outage time information will be
maintained by the network management software, so it is not
included in the MIB.
Consult FRF.13 [17] for more details.
3.2. Terminology
o CIR - The Committed Information Rate (CIR) is the subscriber data
rate (expressed in bits/second) that the network commits to
deliver under normal network conditions. [18]
o DLCI - Data Link Connection Identifier. [18]
o Logical Port - This term is used to model the Frame Relay
"interface" on a device. [18]
o NNI - Network to Network Interface. [18]
o Permanent Virtual Connection (PVC) - A virtual connection that has
its end-points and bearer capabilities defined at subscription
time. [18]
o Reference Point (RP) - The point of reference within the network
model at which the calculations or data collection takes place.
o UNI - User to Network Interface. [18]
3.3. Network Model
The basic model, as illustrated in figure 1 below, contains two frame
relay DTE endpoints connected to a network cloud via a frame relay
Expires December 2000 Steinberger & Nicklass [Page 5]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
UNI interface. The network cloud can contain zero or more internal
frame relay NNI connections that interconnect multiple networks. The
calculations and data collection can be performed at any reference
point within the network.
+-------------+ +-------------+
| Frame Relay | | Frame Relay |
| DTE Device | | DTE Device |
+------+------+ +------+------+
| |
UNI UNI
Connection Connection
| |
+------+------+ NNI +-------------+ NNI +------+------+
| Network A +------------+ Network B +------------+ Network C |
+-------------+ Connection +-------------+ Connection +-------------+
Figure 1
Frame Relay Network Reference Model
3.4. Reference Points
The collection and calculations of the service level definitions
apply to two reference points within the network. These two points
are the locations where the frames are referenced in the collection
of the service level specific information. The reference points used
in the MIB are shown in figure 2 below. For completeness, the MIB
also allows for proprietary reference points which MAY exist anywhere
in the network that is not a previously defined reference point. The
meaning of the proprietary reference points is insignificant unless
defined by the device manufacturer.
Expires December 2000 Steinberger & Nicklass [Page 6]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
+---------------------------+
|+-----------+ +-----------+|
|| | |Measurement||
||Frame Relay---Engine --(Source RP)----+
||DTE | |(If Exists)|| |
|+-----------+ +-----------+| |
+---------------------------+ |
Frame Relay Source |
+------------------------------------------+
| Frame Relay Network
| +----------------------------------+
| | +------------------------------+ |
| | | +---------+ +---------+ | |
| | | | | | Traffic | | |
+--(Ingress RP)--- L1 / L2 --- Policing| | |
| | | Control | | Engine | | |
| | +---------+ +----|----+ | |
| | | | |
| | (Traffic Policing RP)| |
| +------------------|-----------+ |
| Ingress Node | |
| | |
| +-----------|-----------+ |
| | Intermediate Nodes | |
| +-----------|-----------+ |
| | |
| Egress Node | |
| +--------------|-----------+ |
| | (Egress Queue Input RP) | |
| | | | |
| | +-------+------+ | |
| | | Egress Queue | | |
| | +-------+------+ | |
| | | | |
| | (Egress Queue Output RP) | |
| +--------------|-----------+ |
+--------------------|-------------+
Frame Relay Destination |
+---------------------------+ +-----------+
|+-----------+ +-----------+| |
|| | |Measurement|| |
||Frame Relay---Engine --(Destination RP)--+
||DTE | |(If Exists)||
|+-----------+ +-----------+|
+---------------------------+
Figure 2
Reference Points (FRF.13 [17])
Expires December 2000 Steinberger & Nicklass [Page 7]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
The MIB variables frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP
allow the user to view and configure the reference points at which
the calculations occur. These variables are specific to the device
on which they are located. Frame relay devices act as both frame
sources and frame destinations. The definitions in this MIB apply to
the interaction of a pair of devices on the network path. The same
device can potentially use different reference points for calculation
and collection of the statistics based on whether the referenced
frame is sent or received by the device. When the device is acting as
a frame source, the value of frsldPvcCtrlTransmitRP reflects the
reference point used for all source calculations pertaining to the
specified PVC. When the device is acting as a frame destination, the
value of frsldPvcCtrlReceiveRP reflects the reference point used for
all destination calculations pertaining to the specified PVC.
For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue
measurement domain as a domain in which measurement is performed
between an Ingress Reference Point and an Egress Queue Input
Reference Point. For this domain between a source device and a
destination device, the value of frsldPvcCtrlTransmitRP for the
source device would be set to ingTxLocalRP(2) and the value of
frsldPvcCtrlReceiveRP for the destination device would be set to
eqiRxLocalRP(4). While it is usually the case that the reference
points would be equivalent on the remote device when monitoring
frames going in the opposite direction, there is no requirement for
them to be so.
It can be seen from the above example that a total of four reference
points are required in order to collect information for both
directions of traffic flow. The reference points represent the
transmit and receive directions at both ends of a PVC. If a device
has knowledge of the information from the remote device, it is
possible to collect the statistics from a single device. This is not
always the case. In most instances, two devices will need to be
monitored to capture a complete description of the service level on a
PVC. The reference points a single device is capable of monitoring
are contained in the frsldRPCaps object.
3.5. Measurement Methodology
This document neither recommends nor suggests a method of
implementation. This is left to the device manufacturer and should be
independent of the data that is actually collected.
Periodic collection of this data can be performed through either
polling of the data table, use of the sample tables or use of the
user history group of RFC 2021 [19].
Expires December 2000 Steinberger & Nicklass [Page 8]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
3.6. Theory of Operation
The following sections describe how to use this MIB. They include
row handling, data collection and data calculation. The
recommendations here in are suggestions as to implementation and do
not infer that they are the only method that can be used to perform
such operations.
3.6.1. Capabilities Discovery
Three objects are provided to aid the network manager in discovering
the capabilities of the device with respect to this MIB.
o frsldPvcCtrlWriteCaps This object reports the write capabilities
of the PVC Control Table. Use this object
to determine which objects can be modified.
This need only be referenced if row
creation or modification is to be
performed.
o frsldSmplCtrlWriteCaps This object reports the write capabilities
of the Sample Control Table. Use this
object to determine which objects can be
modified. The group need only be
referenced if the sample tables will be
used to collect historical information.
o frsldRPCaps This object reports the reference points at
which the device is capable of collecting
information. This object needs to be
referenced if row creation is to be
performed in the PVC Control Table.
Devices can only create rows containing
supported reference points.
These objects do not imply that there is no need for an Agent
Capabilities macro for devices that do not fully support every object
in this MIB. They are provided specifically to aid in the ensured
network management operations of this MIB with respect to row
creation and modification.
3.6.2. Determining Reference Points for Row Creation
The ability to monitor specific reference points varies between
devices. This variance is based on the capabilities of device in
regards to communication with the remote devices along the PVC as
Expires December 2000 Steinberger & Nicklass [Page 9]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
well as where the device exists in the network. Most endpoint devices
are capable of monitoring the local source and destination reference
points but may not have the capability to monitor any other reference
points. Some devices are able to communicate with remote devices in
such a way that information concerning the remote reference points is
known locally.
To monitor bidirectional information on a PVC a total of four
reference points is required. Two relate to the local device and two
relate to the remote device. It does not matter on which device the
reference points exist as long as the transmit and receive reference
points for each device are captured.
The following list shows the possible valid reference points for an
FRF.13 SLA from the source reference point to the destination
reference point in both directions.
o Local Information Only
Local Device: srcLocalRP, desLocalRP
Remote Device: srcLocalRP, desLocalRP
o Remote Information Only
Local Device: srcRemoteRP, desRemoteRP
Remote Device: srcRemoteRP, desRemoteRP
o Mixed Two Device Model 1 (Local Device Always Transmitter)
Local Device: srcLocalRP, desRemoteRP
Remote Device: srcLocalRP, desRemoteRP
o Mixed Two Device Model 2 (Local Device Always Receiver)
Local Device: srcRemoteRP, desLocalRP
Remote Device: srcRemoteRP, desLocalRP
o Mixed One Device Model 1 (Directional Rows)
First Row: srcRemoteRP, desLocalRP (Receiver Row)
Second Row: srcLocalRP, desRemoteRP (Sender Row)
o Mixed One Device Model 2 (Device Based Rows)
First Row: srcLocalRP, desLocalRP (Local Row)
Second Row: srcRemoteRP, desRemoteRP (Remote Row)
Each of the above combinations is valid and provides the same
Expires December 2000 Steinberger & Nicklass [Page 10]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
information.
The following steps are recommended to find which reference points
need to be configured:
1) Locate both of the devices at either end of the PVC to be
monitored.
2) Determine the capabilities by referencing the frsldRPCaps object
of each device.
3) Locate the best combination of the two devices such that the
necessary reference points are all represented.
4) If any one of the necessary reference points does not exist in
the combination of the two devices, it is not possible to
monitor the FRF.13 defined SLA between the two reference point
on the PVC.
3.6.3. Creation Process
In some cases, devices will automatically populate the rows of PVC
Control Table and potentially the Sample Control Table. However, in
many cases, it may be necessary for a network manager to manually
create rows.
Manual creation of rows requires the following steps:
1) Ensure the PVC exists between the two devices.
2) Determine the necessary reference points for row creation.
3) Create the row(s) in each device as needed.
4) Create the row(s) in the sample control tables if desired.
3.6.4. Destruction Process
3.6.4.1. Manual Row Destruction
Manual row destruction is straight forward. Any row can be destroyed
and the resources allocated to it are freed by setting the value of
its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus)
Expires December 2000 Steinberger & Nicklass [Page 11]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
to destroy(6). It should be noted that when frsldPvcCtrlStatus is
set to destroy(6) all associated sample control, sample and data
table rows will also be destroyed. Similarly, when
frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be
destroyed. The frsldPvcCtrlPurge objects do not apply to manual row
destruction. If the row is set to destroy(6) manually, the rows are
destroyed as part of the set.
3.6.4.2. Automatic Row Destruction
Rows is the tables may be destroyed automatically based on the
existence of the DLCI on which they rely. This behavior is
controlled by the frsldPvcCtrlPurge and frsldPvcCtrlDeleteOnPurge
objects. When a DLCI no longer exists in the device, the data in the
tables has no relation to anything known on the network. However,
there may be some need to keep the historic information active for a
short period after the destruction or removal of a DLCI. If the
basis for the row no longer exists, the row will be destroyed at the
end of the purge interval that is controlled by frsldPvcCtrlPurge.
The effects of automatic row destruction are the same as manual row
destruction.
3.6.5. Modification Process
All read-create items in this MIB can be modified at any time if they
are fully supported. Write access is not required. To simplify the
use of the MIB frsldPvcCtrlWriteCaps and frsldSmplCtrlWriteCaps state
which of the read-create variables can actually be written on a
particular device.
3.6.6. Collection Process
3.6.6.1. Remote Polling
This MIB supports data collection through remote polling of the free
running counters in the PVC Data Table. Remote polling is a common
method used to capture real-time statistics. A remote management
station polls the device to collect the desired information. It is
recommended all statistics for a single PVC be collected in a single
PDU.
The following objects are designed around the concept of real-time
polling:
Expires December 2000 Steinberger & Nicklass [Page 12]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
o frsldPvcDataDelayMin
o frsldPvcDataDelayMax
o frsldPvcDataDelayAvg
o frsldPvcDataMissedPolls
o frsldPvcDataFrDeliveredC
o frsldPvcDataFrDeliveredE
o frsldPvcDataFrOfferedC
o frsldPvcDataFrOfferedE
o frsldPvcDataDataDeliveredC
o frsldPvcDataDataDeliveredE
o frsldPvcDataDataOfferedC
o frsldPvcDataDataOfferedE
o frsldPvcDataHCFrDeliveredC
o frsldPvcDataHCFrDeliveredE
o frsldPvcDataHCFrOfferedC
o frsldPvcDataHCFrOfferedE
o frsldPvcDataHCDataDeliveredC
o frsldPvcDataHCDataDeliveredE
o frsldPvcDataHCDataOfferedC
o frsldPvcDataHCDataOfferedE
o frsldPvcDataUnavailableTime
o frsldPvcDataUnavailables
3.6.6.2. Sampling
The sample tables provide the ability to historically sample data
without requiring the additional overhead of polling. At key
periods, a network management station can collect the samples needed.
This method allows the manager to perform the collection of data at
times that will least affect the active network traffic.
The sample data can be collected using a series of SNMP getNext or
getBulk operations. The values of frsldPvcDataSmplIdx and
frsldPvcAvailSmplIdx increment with each new collection bucket. This
allows the managers to skip information that has already been
collected. However, care should be taken in that the value can roll
over after a long period of time.
The start and end times of a collection period allow the manager to
know what the actual period of collection was. It is possible for
there to be discontinuities in the sample table, so both start and
end should be referenced.
Expires December 2000 Steinberger & Nicklass [Page 13]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
3.6.6.3. User History
User history, as defined in RFC 2021 [19], is an alternative
mechanism that can be used to get the same benefits as the sample
table by using the objects provided for real-time polling. Some
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
the data table can be used to define a group of user history objects.
3.6.7. Use of MIB in Calculation of Service Level Definitions
The objects in this MIB can be used to calculate the statistics
defined in FRF.13 [17]. The description below describes the
calculations for one direction of the data flow, i.e. data sent from
local transmitter to a remote receiver. A complete set of
bidirectional information would require calculations based on both
directions. For the purposes of this description, the reference
points used SHOULD consistently represent data that is sent by one
device and received by the other.
The calculations below use the following terminology:
o DelayAvg
The average delay on the PVC. This is represented within the
MIB by either frsldPvcDataDelayAvg or frsldPvcDataSmplDelayAvg.
o FrDeliveredC
The number of frames received by the receiving device through
the receive reference point that were delivered within CIR.
This is represented within the MIB by one of
frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC,
frsldPvcDataSmplFrDeliveredC, or frsldPvcDataSmplHCFrDeliveredC.
o FrDeliveredE
The number of frames received by the receiving device through
the receive reference point that were delivered in excess of
CIR. This is represented within the MIB by one of
frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE,
frsldPvcDataSmplFrDeliveredE, or frsldPvcDataSmplHCFrDeliveredE.
o FrOfferedC
The number of frames offered by the transmitting device through
the transmit reference point that were sent within CIR. This is
Expires December 2000 Steinberger & Nicklass [Page 14]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
represented within the MIB by one of frsldPvcDataFrOfferedC,
frsldPvcDataHCFrOfferedC, frsldPvcDataSmplFrOfferedC, or
frsldPvcDataSmplHCFrOfferedC.
o FrOfferedE
The number of frames offered by the transmitting device through
the transmit reference point that were sent in excess of CIR.
This is represented within the MIB by one of
frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE,
frsldPvcDataSmplFrOfferedE, or frsldPvcDataSmplHCFrOfferedE.
o DataDeliveredC
The number of octets received by the receiving device through
the receive reference point that were delivered within CIR.
This is represented within the MIB by one of
frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC,
frsldPvcDataSmplDataDeliveredC, or
frsldPvcDataSmplHCDataDeliveredC.
o DataDeliveredE
The number of octets received by the receiving device through
the receive reference point that were delivered in excess of
CIR. This is represented within the MIB by one of
frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE,
frsldPvcDataSmplDataDeliveredE, or
frsldPvcDataSmplHCDataDeliveredE.
o DataOfferedC
The number of octets offered by the transmitting device through
the transmit reference point that were sent within CIR. This is
represented within the MIB by one of frsldPvcDataDataOfferedC,
frsldPvcDataHCDataOfferedC, frsldPvcDataSmplDataOfferedC, or
frsldPvcDataSmplHCDataOfferedC.
o DataOfferedE
The number of octets offered by the transmitting device through
the transmit reference point that were sent in excess of CIR.
This is represented within the MIB by one of
frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE,
frsldPvcDataSmplDataOfferedE, or frsldPvcDataSmplHCDataOfferedE.
o UnavailableTime
Expires December 2000 Steinberger & Nicklass [Page 15]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
The amount of time the PVC was not available during the interval
of interest. This is represented within the MIB by either
frsldPvcDataUnavailableTime or frsldPvcAvailSmplUnavailableTime.
o Unavailables
The number of times the PVC was declared to be unavailable
during the interval of interest. This is represented within the
MIB by either frsldPvcDataUnavailables or
frsldPvcAvailSmplUnavailables.
3.6.8. Delay
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
reaches the destination. The average delay can be found using the MIB
variable described in DelayAvg above. The delay may be calculated as
either round trip or one way, and this information is held in the
frsldPvcCtrlDelayType MIB variable. If the delay be calculated as
round trip, the value of DelayAvg represents the average of the total
delays of the round trips. In this case, the manager SHOULD divide
the value returned by the agent by two to obtain the frame transfer
delay. In the case that frsldPvcCtrlDelayType is oneWay, the value
of DelayAvg represents the average of the frame transfer delays and
SHOULD be used as is.
3.6.9. Frame Delivery Ratio
The frame delivery ratio is defined as the total number of frames
delivered to the destination divided by the frames offered by the
source. The destination values can be obtained using FrDeliveredC
and FrDeliveredE. The source values can be obtained using FrOfferedC
and FrOfferedE.
FrDeliveredC + FrDeliveredE
Frame Delivery Ratio = ---------------------------
FrOfferedC + FrOfferedE
FrDeliveredC
Committed Frame Delivery Ratio = ------------
FrOfferedC
FrDeliveredE
Excess Frame Delivery Ratio = ------------
FrOfferedE
Expires December 2000 Steinberger & Nicklass [Page 16]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
3.6.10. Data Delivery Ratio
The data delivery ratio is defined as the total amount of data
delivered to the destination divided by the data offered by the
source. The destination values can be obtained using DataDeliveredC
and DataDeliveredE. The source values can be obtained using
DataOfferedC and DataOfferedE.
DataDeliveredC + DataDeliveredE
Data Delivery Ratio = -------------------------------
DataOfferedC + DataOfferedE
DataDeliveredC
Committed Data Delivery Ratio = --------------
DataOfferedC
DataDeliveredE
Excess Data Delivery Ratio = --------------
DataOfferedE
3.6.11. Service Availability
Some forms of service availability measurement defined in FRF.13 [17]
require knowledge of the amount of time the network is allowed to be
unavailable during the period of measurement. This is called the
excluded outage time and will be represented in the measurements
below as ExcludedTime. It is assumed that the management software
will maintain this information in that it often relates to specific
times and dates that many devices are not capable of maintaining.
Further, it may change based on a moving maintenance window that the
device cannot track well.
Expires December 2000 Steinberger & Nicklass [Page 17]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0.
UnavailableTime
Otherwise, FRMTTR = ---------------
Unavailables
Virtual Connection Availability (FRVCA) = 0 if IntervalTime equals
ExcludedTime.
IntervalTime - ExcludedTime - UnavailableTime
Otherwise, FRVCA = --------------------------------------------- * 100
IntervalTime - ExcludedTime
Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0.
Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime
---------------------------------------------
Unavailables
4. Relation to Other MIBs
There is no explicit relation to any other frame relay MIB nor are
any required to implement this MIB. However, there is a need for
knowledge of ifIndexes and some understanding of DLCIs. The ifIndex
information can be found in the IF-MIB which is required. The DLCI
information can be found in either the Frame Relay DTE MIB (RFC 2115)
[20] or the Frame Relay Network Services MIB (RFC 1604) [18];
however, neither is required.
Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to
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
state in which frPVCEndptRowStatus is active(1) and
frPVCEndptRcvdSigStatus is either active(2) or none(4) for the
Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame
Relay DTE MIB, the same state is shown by frCircuitRowStatus of
active(1) and frCircuitState of active(2).
(2) The respective DLCI has not been created. This corresponds to a
state in which the row with either frPVCEndptDLCIIndex or
frCircuitDlci equal to the respective DLCI does not exist in
either the frPVCEndptTable or the frCircuitTable respectively.
(3) The respective DLCI has just been removed. This corresponds to a
Expires December 2000 Steinberger & Nicklass [Page 18]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
state in which either frPVCEndptRowStatus is no longer active(1)
or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for
the Frame Relay Network Services MIB (RFC 1604) [18]. For the
Frame Relay DTE MIB, the same state is shown when either
frCircuitRowStatus is no longer active(1) or frCircuitState is no
longer active(2).
For the first case, the row in the frsldPvcDataTable will be filled.
If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective
DLCI is also `active' the frsldPvcDataSampleTable and
frsldPvcAvailSampleTable will be filled as well.
For the second case, the respective rows will not be added to any of
the data or sample tables and frsldPvcCtrlStatus SHOULD be set to
notReady(3).
For the third case, frsldPvcCtrlDeleteOnPurge should direct the
behavior of the system. If all tables are purged, this case will be
equivalent to the second case above. Otherwise, frsldPvcCtrlStatus
SHOULD remain active(1).
5. Structure of the MIB
The FRSLD-MIB consists of the following components:
o frsldPvcCtrlTable
o frsldSmplCtrlTable
o frsldPvcDataTable
o frsldPvcDataSampleTable
o frsldPvcAvailSampleTable
o frsldCapabilities
Refer to the compliance statement defined within for a definition of
what objects MUST be implemented.
5.1. frsldPvcCtrlTable
The frsldPvcCtrlTable is the central control table for operations of
the Frame Relay Service Level Definitions MIB. It provides variables
to control the parameters required to calculate the objects in the
other tables.
Expires December 2000 Steinberger & Nicklass [Page 19]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
A row in this table MUST exist in order for a row to exist in any
other table in this MIB.
5.2. frsldSmplCtrlTable
This is an optional table to allow control of sampling of the data in
the data table.
5.3. frsldPvcDataTable
This table contains the calculated data. It relies on configuration
from the control table.
5.4. frsldPvcDataSampleTable
This table contains samples of the delay and delivery information
from the data table. It relies on configuration from both the
control table and the sample control table.
5.5. frsldPvcAvailSampleTable
This table contains samples of the availability information from the
data table. It relies on configuration from both the control table
and the sample control table.
5.6. frsldCapabilities
This is a group of objects that define write capabilities of the
read-create objects in the tables above.
6. Object Definitions
FRSLD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Gauge32, Integer32,
Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI
CounterBasedGauge64 FROM HCNUM-TC
RowStatus, TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB;
frsldMIB MODULE-IDENTITY
LAST-UPDATED "200006141500Z" -- June 14, 2000
ORGANIZATION "IETF Frame Relay Service MIB Working Group"
CONTACT-INFO
"IETF Frame Relay Service MIB (frnetmib) Working Group
Expires December 2000 Steinberger & Nicklass [Page 20]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
WG Charter: http://www.ietf.org/html.charters/
frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
Chair: Andy Malis
Lucent Technologies
Email: amalis@lucent.com
WG editor: Robert Steinberger
Paradyne Networks
Email: rsteinberger@paradyne.com
Co-author: Orly Nicklass
RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il"
DESCRIPTION
"The MIB module to describe generic objects for
FRF.13 Frame Relay Service Level Definitions."
REVISION "200006141500Z"
DESCRIPTION
"o Removed all uses of FrsldLocation by removing objects
frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc
o Removed FrsldRP TC and distributed source and destination
specific information into index for control table as
frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP.
o Added frsldPvcCtrlDelayCnt to control table.
o Changed frsldPvcDataUnavailableTime from TimeStamp to
TimeTicks.
o Updated text of RowStatus objects
o Added frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP as
indices to ALL tables.
o Added HC counters for all data delivery stats and
samples.
o Adjusted description of sample information for clarity.
o Adjusted names of sample objects for consistency.
o Added frsldRPCaps.
o Changed location to mib-2
o Reworked Group Definitions."
REVISION "200002061500Z"
DESCRIPTION
"o Published as draft-ietf-frnetmib-frmrelay-service-00.txt
o Added frsldCapabilities group to define the
read/write capabilities
o Changed location to experimental 104
o Changed name of frsldTables to frsldObjects
Expires December 2000 Steinberger & Nicklass [Page 21]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
o Changed MAX-ACCESS of frsldPvcCtrlDelayType to
read-create
o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax,
and frsldPvcDataDelayAvg from the sample period"
REVISION "199909031500Z"
DESCRIPTION
"o Added range to frsldPvcCtrlPacketFreq
o Changed range of frsldPvcCtrlDelayTimeOut to match
that of frsldPvcCtrlPacketFreq
o Clarified what happens when frsldPvcCtrlPacketFreq
is set to zero
o Changed delay to count in microseconds instead of
milliseconds
o Created a new sample control table and moved sample
specific information into it.
o Changed the prefix of `frsldPvcCtrl' object name to
`frsldSmplCtrl'
o Added the sample control index to the indices of the
sample tables
o Changed all occasions of TimeTicks to TimeStamp
o Added frsldPvcCtrlPurge to aid in control validity
of information due to PVC status changes
o Added frsldPvcCtrlDeleteOnPurge object
o Added frsldPvcCtrlLastPurgeTime object
o Added units clauses to all time related fields.
o Reworded the `change in' syntax to be more explicit"
-- ::= { experimental 104 } OLD Value
::= { mib-2 xxx } -- RFC editor - IANA assigns xxx
frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 }
frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 }
frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 }
-- The Frame Relay Service Level Definitions PVC Control Table
--
-- This table is used to define and display the parameters of
-- service level definitions on individual PVCs.
frsldPvcCtrlTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldPvcCtrlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Service Level Definitions
PVC control table."
::= { frsldObjects 1 }
Expires December 2000 Steinberger & Nicklass [Page 22]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcCtrlEntry OBJECT-TYPE
SYNTAX FrsldPvcCtrlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Service Level
Definitions PVC control table."
INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP}
::= { frsldPvcCtrlTable 1 }
FrsldPvcCtrlEntry ::=
SEQUENCE {
--
-- Index Control Variables
--
frsldPvcCtrlDlci Integer32,
frsldPvcCtrlTransmitRP INTEGER,
frsldPvcCtrlReceiveRP INTEGER,
frsldPvcCtrlStatus RowStatus,
--
-- Service Level Definitions Setup Variables
--
frsldPvcCtrlPacketFreq Integer32,
--
-- Delay Specific Setup Variables
--
frsldPvcCtrlDelayFrSize Integer32,
frsldPvcCtrlDelayType INTEGER,
frsldPvcCtrlDelayTimeOut Integer32,
frsldPvcCtrlDelayCnt Integer32,
--
-- Data Persistence Control Variables
--
frsldPvcCtrlPurge Integer32,
frsldPvcCtrlDeleteOnPurge INTEGER,
frsldPvcCtrlLastPurgeTime TimeStamp
}
frsldPvcCtrlDlci OBJECT-TYPE
SYNTAX Integer32 (16..4194303)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this object is equal to the DLCI
value for this PVC."
::= { frsldPvcCtrlEntry 1 }
Expires December 2000 Steinberger & Nicklass [Page 23]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcCtrlTransmitRP OBJECT-TYPE
SYNTAX INTEGER {
srcLocalRP(1),
ingTxLocalRP(2),
tpTxLocalRP(3),
eqiTxLocalRP(4),
eqoTxLocalRP(5),
otherTxLocalRP(6),
srcRemoteRP(7),
ingTxRemoteRP(8),
tpTxRemoteRP(9),
eqiTxRemoteRP(10),
eqoTxRemoteRP(11),
otherTxRemoteRP(12)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reference point this PVC used for calculation
of transmitter related statistics. This object
together with frsldPvcCtrlReceiveRP define the
measurement domain.
The valid values for this object are as follows:
- srcLocalRP(1) for the local source
- ingTxLocalRP(2) for the local ingress queue input
- tpTxLocalRP(3) for the local traffic policing
- eqiTxLocalRP(4) for the local egress queue input
- eqoTxLocalRP(5) for the local egress queue output
- otherTxLocalRP(6) for any other local transmit point
- srcRemoteRP(7) for the remote source
- ingTxLocalRP(8) for the remote ingress queue input
- tpTxLocalRP(9) for the remote traffic policing
- eqiTxRemoteRP(10) for the remote egress queue input
- eqoTxRemoteRP(11) for the remote egress queue output
- otherTxRemoteRP(12) for any other remote transmit point"
::= { frsldPvcCtrlEntry 2 }
frsldPvcCtrlReceiveRP OBJECT-TYPE
SYNTAX INTEGER {
desLocalRP(1),
ingRxLocalRP(2),
tpRxLocalRP(3),
eqiRxLocalRP(4),
eqoRxLocalRP(5),
otherRxLocalRP(6),
desRemoteRP(7),
ingRxRemoteRP(8),
Expires December 2000 Steinberger & Nicklass [Page 24]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
tpRxRemoteRP(9),
eqiRxRemoteRP(10),
eqoRxRemoteRP(11),
otherRxRemoteRP(12)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reference point this PVC used for calculation
of receiver related statistics. This object
together with frsldPvcCtrlTransmitRP define the
measurement domain.
The valid values for this object are as follows:
- desLocalRP(1) for the local destination
- ingRxLocalRP(2) for the local ingress queue input
- tpRxLocalRP(3) for the local traffic policing
- eqiRxLocalRP(4) for the local egress queue input
- eqoRxLocalRP(5) for the local egress queue output
- otherRxLocalRP(6) for any other local receive point
- desRemoteRP(7) for the remote destination
- ingRxRemoteRP(8) for the remote ingress input
- tpRxRemoteRP(9) for the remote traffic policing
- eqiRxRemoteRP(10) for the remote egress queue input
- eqoRxRemoteRP(11) for the remote egress queue output
- otherRxRemoteRP(12) for any other remote receive point"
::= { frsldPvcCtrlEntry 3 }
frsldPvcCtrlStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of the current row. This object is
used to add, delete, and disable rows in this
table. When the status changes to active(1) for the
first time, a row will also be added to the data
table below. This row SHOULD not be removed until
the status is changed to deleted.
When this object is set to destroy(6), all associated
sample and data table rows will also be deleted.
When this object is changed from active(1) to any
other valid value, the defined purge behavior will
affect the data and sample tables.
The rows added to this table MUST have a valid
ifIndex and an ifType related to frame relay. Further,
Expires December 2000 Steinberger & Nicklass [Page 25]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
the reference points referred to by frsldPvcCtrlTransmitRP
and frsldPvcCtrlReceiveRP MUST be supported (see the
frsldRPCaps object).
If at any point the row is not in the active(1) state
and the DLCI no longer exists, the state SHOULD
report notReady(3)."
::= { frsldPvcCtrlEntry 4 }
frsldPvcCtrlPacketFreq OBJECT-TYPE
SYNTAX Integer32 (0..3600)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The frequency in seconds between initiation of
specialized packets used to collect delay and / or
delivery information as supported by the device.
A value of zero indicates that no packets will
be sent."
DEFVAL { 60 }
::= { frsldPvcCtrlEntry 5 }
frsldPvcCtrlDelayFrSize OBJECT-TYPE
SYNTAX Integer32 (1..8188)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The size of the payload in the frame used for
calculation of network delay."
DEFVAL { 128 }
::= { frsldPvcCtrlEntry 6 }
frsldPvcCtrlDelayType OBJECT-TYPE
SYNTAX INTEGER {
oneWay(1),
roundTrip(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of delay measurement performed."
::= { frsldPvcCtrlEntry 7 }
frsldPvcCtrlDelayTimeOut OBJECT-TYPE
SYNTAX Integer32 (1..3600)
UNITS "seconds"
Expires December 2000 Steinberger & Nicklass [Page 26]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A delay frame will count as a missed poll if
it is not updated in the time specified by
frsldPvcCtrlDelayTimeOut."
DEFVAL { 60 }
::= { frsldPvcCtrlEntry 8 }
frsldPvcCtrlDelayCnt OBJECT-TYPE
SYNTAX Integer32 (0..32767)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of discrete delay measurements that are
used to calculate the free running minimum, maximum
and average. A value of zero indicates that the values
are unbounded."
DEFVAL { 1000 }
::= { frsldPvcCtrlEntry 9 }
frsldPvcCtrlPurge OBJECT-TYPE
SYNTAX Integer32 (0..172800) -- up to 48 hours
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines the amount of time the device
will wait, after discovering that a DLCI does not exist,
the DLCI was deleted or the value of frsldPvcCtrlStatus
changes from active(1) to either notInService(2) or
notReady(3), prior to automatically purging the history
in the sample tables and resetting the data in the data
tables to all zeroes. If frsldPvcCtrlStatus is manually
set to destroy(6), this object does not apply."
DEFVAL { 0 }
::= { frsldPvcCtrlEntry 10 }
frsldPvcCtrlDeleteOnPurge OBJECT-TYPE
SYNTAX INTEGER {
none(1),
sampleContols(2),
all(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines whether rows will
Expires December 2000 Steinberger & Nicklass [Page 27]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
automatically be deleted from the tables
when the information is purged.
- A value of none(1) indicates that no rows
will deleted. The last known values will
be preserved.
- A value of sampleControls(2) indicates
that all associated sample control rows
will be deleted.
- A value of all(3) indicates that all
associated rows SHOULD be deleted."
DEFVAL { all }
::= { frsldPvcCtrlEntry 11 }
frsldPvcCtrlLastPurgeTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object returns the value of sysUpTime
at the time the information was last purged.
This value SHOULD be set to the sysUpTime
upon setting frsldPvcCtrlStatus to active(1)
for the first time. If frsldPvcCtrlStatus has
never been active(1), this object SHOULD return 0."
DEFVAL { 0 }
::= { frsldPvcCtrlEntry 12 }
-- The Frame Relay Service Level Definitions Sampling Control
-- Table
--
-- This table is used to define the sample control parameters
-- of service level definitions on individual PVCs.
frsldSmplCtrlTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldSmplCtrlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Service Level Definitions
sampling control table."
::= { frsldObjects 2 }
frsldSmplCtrlEntry OBJECT-TYPE
SYNTAX FrsldSmplCtrlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Expires December 2000 Steinberger & Nicklass [Page 28]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
"An entry in the Frame Relay Service Level
Definitions sample control table."
INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP,
frsldSmplCtrlIdx }
::= { frsldSmplCtrlTable 1 }
FrsldSmplCtrlEntry ::=
SEQUENCE {
--
-- Index Control Variables
--
frsldSmplCtrlIdx Integer32,
frsldSmplCtrlStatus RowStatus,
--
-- Data Collection Control Variables
--
frsldSmplCtrlDataColPeriod Integer32,
frsldSmplCtrlDataBuckets Integer32,
frsldSmplCtrlDataBucketsGranted Integer32,
--
-- Availability Collection Control Variables
--
frsldSmplCtrlAvailColPeriod Integer32,
frsldSmplCtrlAvailBuckets Integer32,
frsldSmplCtrlAvailBucketsGranted Integer32
}
frsldSmplCtrlIdx OBJECT-TYPE
SYNTAX Integer32 (1..256)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique index for this row in the
sample control table."
::= { frsldSmplCtrlEntry 1 }
frsldSmplCtrlStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of the current row. This object is
used to add, delete, and disable rows in this
table. This row SHOULD NOT be removed until the
status is changed to destroy(6). When the status
changes to active(1), the collection in the sample
tables below will be activated.
Expires December 2000 Steinberger & Nicklass [Page 29]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
The rows added to this table MUST have a valid
ifIndex, an ifType related to frame relay,
frsldPvcCtrlDlci MUST exist for the specified
ifIndex and frsldPvcCtrlStatus MUST have a
value of active(1).
The value of frsldPvcCtrlStatus MUST be active(1)
to transition this object to active(1). If
the value of frsldPvcCtrlStatus becomes anything
other than active(1) when the state of this object
is not active(1), this object SHOULD be set to
notReady(3)."
::= { frsldSmplCtrlEntry 2 }
frsldSmplCtrlDataColPeriod OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The amount of time in seconds that defines a
period of collection for data delivery statistics.
At the end of each period, the statistics will be
sampled and a row is added to the sample table."
::= { frsldSmplCtrlEntry 3 }
frsldSmplCtrlDataBuckets OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of discrete buckets over which the
data statistics are sampled.
When this object is created or modified, the device
SHOULD attempt to set the frsldSmplCtrlDataBuckets-
Granted to a value as close as is possible
depending upon the implementation and the available
resources."
DEFVAL { 60 }
::= { frsldSmplCtrlEntry 4 }
frsldSmplCtrlDataBucketsGranted OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of discrete buckets granted. This
Expires December 2000 Steinberger & Nicklass [Page 30]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
object will return 0 until frsldSmplCtrlStatus is
set to active(1). At that time the buckets will be
allocated depending upon implementation and
available resources."
::= { frsldSmplCtrlEntry 5 }
frsldSmplCtrlAvailColPeriod OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The amount of time in seconds that defines a
period of collection for availability statistics.
At the end of each period, the statistics will be
sampled and a row is added to the sample table."
::= { frsldSmplCtrlEntry 6 }
frsldSmplCtrlAvailBuckets OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of discrete buckets over which the
availability statistics are sampled.
When this object is created or modified, the device
SHOULD attempt to set the frsldSmplCtrlDataBuckets-
Granted to a value as close as is possible
depending upon the implementation and the available
resources."
DEFVAL { 60 }
::= { frsldSmplCtrlEntry 7 }
frsldSmplCtrlAvailBucketsGranted OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of discrete buckets granted. This
object will return 0 until frsldSmplCtrlStatus is
set to active(1). At that time the buckets will be
allocated depending upon implementation and
available resources."
::= { frsldSmplCtrlEntry 8 }
-- The Frame Relay Service Level Definitions PVC Data Table
--
Expires December 2000 Steinberger & Nicklass [Page 31]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
-- This table contains the accumulated values of
-- the collected data. This table is the table that should
-- be referenced by external polling mechanisms if time
-- based polling be desired.
frsldPvcDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldPvcDataEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Service Level Definitions
data table.
This table contains accumulated values of the
collected data. It is the table that should be
referenced by external polling mechanisms if
time based polling be desired."
::= { frsldObjects 3 }
frsldPvcDataEntry OBJECT-TYPE
SYNTAX FrsldPvcDataEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Service Level
Definitions data table."
INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP}
::= { frsldPvcDataTable 1 }
FrsldPvcDataEntry ::=
SEQUENCE {
frsldPvcDataDelayMin Gauge32,
frsldPvcDataDelayMax Gauge32,
frsldPvcDataDelayAvg Gauge32,
frsldPvcDataMissedPolls Counter32,
frsldPvcDataFrDeliveredC Counter32,
frsldPvcDataFrDeliveredE Counter32,
frsldPvcDataFrOfferedC Counter32,
frsldPvcDataFrOfferedE Counter32,
frsldPvcDataDataDeliveredC Counter32,
frsldPvcDataDataDeliveredE Counter32,
frsldPvcDataDataOfferedC Counter32,
frsldPvcDataDataOfferedE Counter32,
frsldPvcDataHCFrDeliveredC Counter64,
frsldPvcDataHCFrDeliveredE Counter64,
frsldPvcDataHCFrOfferedC Counter64,
frsldPvcDataHCFrOfferedE Counter64,
Expires December 2000 Steinberger & Nicklass [Page 32]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataHCDataDeliveredC Counter64,
frsldPvcDataHCDataDeliveredE Counter64,
frsldPvcDataHCDataOfferedC Counter64,
frsldPvcDataHCDataOfferedE Counter64,
frsldPvcDataUnavailableTime TimeTicks,
frsldPvcDataUnavailables Counter32
}
frsldPvcDataDelayMin OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum delay, reported in microseconds, that
has been detected within the frsldPvcCtrlDelayCnt
most recent delay queries.
A value of zero means that no data is available."
::= { frsldPvcDataEntry 1 }
frsldPvcDataDelayMax OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest delay, reported in microseconds, that
has been detected within the frsldPvcCtrlDelayCnt
most recent delay queries.
A value of zero means that no data is available."
::= { frsldPvcDataEntry 2 }
frsldPvcDataDelayAvg OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average delay, reported in microseconds,
calculated over the frsldPvcCtrlDelayCnt most
recent delay queries.
A value of zero means that no data is available."
::= { frsldPvcDataEntry 3 }
frsldPvcDataMissedPolls OBJECT-TYPE
Expires December 2000 Steinberger & Nicklass [Page 33]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of polls that have been determined
to be missed."
::= { frsldPvcDataEntry 4 }
frsldPvcDataFrDeliveredC OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR."
::= { frsldPvcDataEntry 5 }
frsldPvcDataFrDeliveredE OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR."
::= { frsldPvcDataEntry 6 }
frsldPvcDataFrOfferedC OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR."
::= { frsldPvcDataEntry 7 }
frsldPvcDataFrOfferedE OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR."
::= { frsldPvcDataEntry 8 }
frsldPvcDataDataDeliveredC OBJECT-TYPE
SYNTAX Counter32
Expires December 2000 Steinberger & Nicklass [Page 34]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR."
::= { frsldPvcDataEntry 9 }
frsldPvcDataDataDeliveredE OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR."
::= { frsldPvcDataEntry 10 }
frsldPvcDataDataOfferedC OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR."
::= { frsldPvcDataEntry 11 }
frsldPvcDataDataOfferedE OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR."
::= { frsldPvcDataEntry 12 }
frsldPvcDataHCFrDeliveredC OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version
of frsldPvcDataFrDeliveredC."
::= { frsldPvcDataEntry 13 }
frsldPvcDataHCFrDeliveredE OBJECT-TYPE
Expires December 2000 Steinberger & Nicklass [Page 35]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataFrDeliveredE."
::= { frsldPvcDataEntry 14 }
frsldPvcDataHCFrOfferedC OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataFrOfferedC."
::= { frsldPvcDataEntry 15 }
frsldPvcDataHCFrOfferedE OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR. This
object is a 64-bit version of frsldPvcDataFrOfferedE."
::= { frsldPvcDataEntry 16 }
frsldPvcDataHCDataDeliveredC OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR. This object is a 64-bit version of
frsldPvcDataDataDeliveredC."
::= { frsldPvcDataEntry 17 }
frsldPvcDataHCDataDeliveredE OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
Expires December 2000 Steinberger & Nicklass [Page 36]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
sent in excess of the CIR. This object is a 64-bit
version of frsldPvcDataDataDeliveredE."
::= { frsldPvcDataEntry 18 }
frsldPvcDataHCDataOfferedC OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR. This object is
a 64-bit version of frsldPvcDataDataOfferedC."
::= { frsldPvcDataEntry 19 }
frsldPvcDataHCDataOfferedE OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR.
This object is a 64-bit version of
frsldPvcDataDataOfferedE."
::= { frsldPvcDataEntry 20 }
frsldPvcDataUnavailableTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time this PVC was declared unavailable
for any reason since this row was created."
::= { frsldPvcDataEntry 21 }
frsldPvcDataUnavailables OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this PVC was declared unavailable
for any reason since this row was created."
::= { frsldPvcDataEntry 22 }
-- The Frame Relay Service Level Definitions PVC
-- Data Sample Table
--
-- This table contains the sampled delay and delivery
-- information.
Expires December 2000 Steinberger & Nicklass [Page 37]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataSampleTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldPvcDataSampleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Service Level Definitions
data sample table."
::= { frsldObjects 4 }
frsldPvcDataSampleEntry OBJECT-TYPE
SYNTAX FrsldPvcDataSampleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Service Level
Definitions data sample table."
INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP,
frsldSmplCtrlIdx, frsldPvcDataSmplIdx }
::= { frsldPvcDataSampleTable 1 }
FrsldPvcDataSampleEntry ::=
SEQUENCE {
frsldPvcDataSmplIdx Integer32,
frsldPvcDataSmplDelayMin Gauge32,
frsldPvcDataSmplDelayMax Gauge32,
frsldPvcDataSmplDelayAvg Gauge32,
frsldPvcDataSmplMissedPolls Gauge32,
frsldPvcDataSmplFrDeliveredC Gauge32,
frsldPvcDataSmplFrDeliveredE Gauge32,
frsldPvcDataSmplFrOfferedC Gauge32,
frsldPvcDataSmplFrOfferedE Gauge32,
frsldPvcDataSmplDataDeliveredC Gauge32,
frsldPvcDataSmplDataDeliveredE Gauge32,
frsldPvcDataSmplDataOfferedC Gauge32,
frsldPvcDataSmplDataOfferedE Gauge32,
frsldPvcDataSmplHCFrDeliveredC CounterBasedGauge64,
frsldPvcDataSmplHCFrDeliveredE CounterBasedGauge64,
frsldPvcDataSmplHCFrOfferedC CounterBasedGauge64,
frsldPvcDataSmplHCFrOfferedE CounterBasedGauge64,
frsldPvcDataSmplHCDataDeliveredC CounterBasedGauge64,
frsldPvcDataSmplHCDataDeliveredE CounterBasedGauge64,
frsldPvcDataSmplHCDataOfferedC CounterBasedGauge64,
frsldPvcDataSmplHCDataOfferedE CounterBasedGauge64,
frsldPvcDataSmplStartTime TimeStamp,
frsldPvcDataSmplEndTime TimeStamp
}
Expires December 2000 Steinberger & Nicklass [Page 38]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataSmplIdx OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The bucket index of the current sample. This
increments once for each new bucket in the
table."
::= { frsldPvcDataSampleEntry 1 }
frsldPvcDataSmplDelayMin OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum delay reported in microseconds measured
for any information packet that arrived during this
interval.
A value of zero means that no data is available."
::= { frsldPvcDataSampleEntry 2 }
frsldPvcDataSmplDelayMax OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest delay reported in microseconds measured
for any information packet that arrived during this
interval.
A value of zero means that no data is available."
::= { frsldPvcDataSampleEntry 3 }
frsldPvcDataSmplDelayAvg OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average delay reported in microseconds measured
for all delay packets that arrived during this
interval.
A value of zero means that no data is available."
::= { frsldPvcDataSampleEntry 4 }
Expires December 2000 Steinberger & Nicklass [Page 39]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataSmplMissedPolls OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of polls that were missed during
this interval."
::= { frsldPvcDataSampleEntry 5 }
frsldPvcDataSmplFrDeliveredC OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval."
::= { frsldPvcDataSampleEntry 6 }
frsldPvcDataSmplFrDeliveredE OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR during this interval."
::= { frsldPvcDataSampleEntry 7 }
frsldPvcDataSmplFrOfferedC OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR during this
interval."
::= { frsldPvcDataSampleEntry 8 }
frsldPvcDataSmplFrOfferedE OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR
during this interval."
::= { frsldPvcDataSampleEntry 9 }
Expires December 2000 Steinberger & Nicklass [Page 40]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataSmplDataDeliveredC OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval."
::= { frsldPvcDataSampleEntry 10 }
frsldPvcDataSmplDataDeliveredE OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlDeliveredRP and determined to have been
sent in excess of the CIR during this interval."
::= { frsldPvcDataSampleEntry 11 }
frsldPvcDataSmplDataOfferedC OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR during this
interval."
::= { frsldPvcDataSampleEntry 12 }
frsldPvcDataSmplDataOfferedE OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR
during this interval."
::= { frsldPvcDataSampleEntry 13 }
frsldPvcDataSmplHCFrDeliveredC OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval. This object
Expires December 2000 Steinberger & Nicklass [Page 41]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
is a 64-bit version of frsldPvcDataSmplFrDeliveredC."
::= { frsldPvcDataSampleEntry 14 }
frsldPvcDataSmplHCFrDeliveredE OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR during this interval.
This object is a 64-bit version of frsldPvcDataSmpl-
FrDeliveredE."
::= { frsldPvcDataSampleEntry 15 }
frsldPvcDataSmplHCFrOfferedC OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP within CIR during this
interval. This object is a 64-bit version of
frsldPvcDataSmplFrOfferedC."
::= { frsldPvcDataSampleEntry 16 }
frsldPvcDataSmplHCFrOfferedE OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR
during this interval. This object is a 64-bit
version of frsldPvcDataSmplFrOfferedE."
::= { frsldPvcDataSampleEntry 17 }
frsldPvcDataSmplHCDataDeliveredC OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent within CIR during this interval. This value
is a 64-bit version of frsldPvcDataSmplDataDeliveredC."
::= { frsldPvcDataSampleEntry 18 }
Expires December 2000 Steinberger & Nicklass [Page 42]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataSmplHCDataDeliveredE OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were received at
frsldPvcCtrlReceiveRP and determined to have been
sent in excess of the CIR during this interval. This
value is a 64-bit version of frsldPvcDataSmplData-
DeliveredE."
::= { frsldPvcDataSampleEntry 19 }
frsldPvcDataSmplHCDataOfferedC OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP within CIR during this
interval. This value is a 64-bit version of
frsldPvcDataSmplDataOfferedC."
::= { frsldPvcDataSampleEntry 20 }
frsldPvcDataSmplHCDataOfferedE OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets that were offered through
frsldPvcCtrlTransmitRP in excess of the CIR
during this interval. This object is a 64-bit
version of frsldPvcDataSmplDataOfferedE."
::= { frsldPvcDataSampleEntry 21 }
frsldPvcDataSmplStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this sample interval
started."
::= { frsldPvcDataSampleEntry 22 }
frsldPvcDataSmplEndTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Expires December 2000 Steinberger & Nicklass [Page 43]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
"The value of sysUpTime when this sample interval
ended. No data will be reported and the row will
not appear in the table until the sample has
been collected."
::= { frsldPvcDataSampleEntry 23 }
-- The Frame Relay Service Level Definitions PVC
-- Availability Sample Table
--
-- This table contains the sampled availability information.
frsldPvcAvailSampleTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrsldPvcAvailSampleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Service Level Definitions
availability sample table."
::= { frsldObjects 5 }
frsldPvcAvailSampleEntry OBJECT-TYPE
SYNTAX FrsldPvcAvailSampleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Service Level
Definitions availability sample table."
INDEX { ifIndex, frsldPvcCtrlDlci,
frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP,
frsldSmplCtrlIdx, frsldPvcAvailSmplIdx }
::= { frsldPvcAvailSampleTable 1 }
FrsldPvcAvailSampleEntry ::=
SEQUENCE {
frsldPvcAvailSmplIdx Integer32,
frsldPvcAvailSmplUnavailableTime TimeTicks,
frsldPvcAvailSmplUnavailables Gauge32,
frsldPvcAvailSmplStartTime TimeStamp,
frsldPvcAvailSmplEndTime TimeStamp
}
frsldPvcAvailSmplIdx OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The bucket index of the current sample. This
increments once for each new bucket in the
Expires December 2000 Steinberger & Nicklass [Page 44]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
table."
::= { frsldPvcAvailSampleEntry 1 }
frsldPvcAvailSmplUnavailableTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time this PVC was declared
unavailable for any reason during this interval."
::= { frsldPvcAvailSampleEntry 2 }
frsldPvcAvailSmplUnavailables OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this PVC was declared
unavailable for any reason during this interval."
::= { frsldPvcAvailSampleEntry 3 }
frsldPvcAvailSmplStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this sample interval
started."
::= { frsldPvcAvailSampleEntry 4 }
frsldPvcAvailSmplEndTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this sample interval
ended. No data will be reported and the row will
not appear in the table until the sample has
been collected."
::= { frsldPvcAvailSampleEntry 5 }
-- Capabilities Group
-- This group provides capabilities objects for the tables
-- that control configuration.
frsldPvcCtrlWriteCaps OBJECT-TYPE
SYNTAX BITS {
Expires December 2000 Steinberger & Nicklass [Page 45]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcCtrlStatus(0),
frsldPvcCtrlPacketFreq(1),
frsldPvcCtrlDelayFrSize(2),
frsldPvcCtrlDelayType(3),
frsldPvcCtrlDelayTimeOut(4),
frsldPvcCtrlDelayCnt(5),
frsldPvcCtrlPurge(6),
frsldPvcCtrlDeleteOnPurge(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the write capabilities
for the read-create objects of the PVC Control
table. If the corresponding bit is enabled (1),
the agent supports writes to that object."
::= { frsldCapabilities 1 }
frsldSmplCtrlWriteCaps OBJECT-TYPE
SYNTAX BITS {
frsldSmplCtrlStatus(0),
frsldSmplCtrlBuckets(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the write capabilities
for the read-create objects of the Sample Control
table. If the corresponding bit is enabled (1),
the agent supports writes to that object."
::= { frsldCapabilities 2 }
frsldRPCaps OBJECT-TYPE
SYNTAX BITS {
srcLocalRP(0),
ingTxLocalRP(1),
tpTxLocalRP(2),
eqiTxLocalRP(3),
eqoTxLocalRP(4),
otherTxLocalRP(5),
srcRemoteRP(6),
ingTxRemoteRP(7),
tpTxRemoteRP(8),
eqiTxRemoteRP(9),
eqoTxRemoteRP(10),
otherTxRemoteRP(11),
desLocalRP(12),
ingRxLocalRP(13),
Expires December 2000 Steinberger & Nicklass [Page 46]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
tpRxLocalRP(14),
eqiRxLocalRP(15),
eqoRxLocalRP(16),
otherRxLocalRP(17),
desRemoteRP(18),
ingRxRemoteRP(19),
tpRxRemoteRP(20),
eqiRxLocalRP(21),
eqoRxLocalRP(22),
otherRxRemoteRP(23)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the reference points that
the agent supports. This object allows the management
application to discover which rows can be created on
a specific device."
::= { frsldCapabilities 3 }
-- Conformance Information
frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 }
frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 }
--
-- Compliance Statements
--
frsldCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities
which support with Frame Relay Service Level
Definitions. This group defines the minimum
level of support required for compliance."
MODULE -- this module
MANDATORY-GROUPS { frsldPvcReqCtrlGroup,
frsldPvcReqDataGroup,
frsldCapabilitiesGroup}
OBJECT frsldPvcCtrlStatus
SYNTAX INTEGER { active(1) } -- subset of RowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and only one of the six
enumerated values for the RowStatus textual convention
need be supported, specifically: active(1)."
Expires December 2000 Steinberger & Nicklass [Page 47]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
OBJECT frsldPvcCtrlPurge
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT frsldPvcCtrlDeleteOnPurge
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { frsldMIBCompliances 1 }
--
-- Units of Conformance
--
frsldPvcReqCtrlGroup OBJECT-GROUP
OBJECTS {
frsldPvcCtrlStatus,
frsldPvcCtrlPurge,
frsldPvcCtrlDeleteOnPurge,
frsldPvcCtrlLastPurgeTime
}
STATUS current
DESCRIPTION
"A collection of required objects providing
control information applicable to a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 1 }
frsldPvcPacketGroup OBJECT-GROUP
OBJECTS {
frsldPvcCtrlPacketFreq
}
STATUS current
DESCRIPTION
"A collection of optional objects providing packet
level control information applicable to a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 2 }
frsldPvcDelayCtrlGroup OBJECT-GROUP
OBJECTS {
frsldPvcCtrlDelayFrSize,
frsldPvcCtrlDelayType,
frsldPvcCtrlDelayTimeOut,
frsldPvcCtrlDelayCnt
}
STATUS current
Expires December 2000 Steinberger & Nicklass [Page 48]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
DESCRIPTION
"A collection of optional objects providing delay
control information applicable to a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 3 }
frsldPvcDataSampleCtrlGroup OBJECT-GROUP
OBJECTS {
frsldSmplCtrlStatus,
frsldSmplCtrlDataColPeriod,
frsldSmplCtrlDataBuckets,
frsldSmplCtrlDataBucketsGranted,
frsldSmplCtrlAvailColPeriod,
frsldSmplCtrlAvailBuckets,
frsldSmplCtrlAvailBucketsGranted
}
STATUS current
DESCRIPTION
"A collection of optional objects providing sample
control information applicable to a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 4 }
frsldPvcReqDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataDelayAvg,
frsldPvcDataFrDeliveredC,
frsldPvcDataFrDeliveredE,
frsldPvcDataFrOfferedC,
frsldPvcDataFrOfferedE,
frsldPvcDataDataDeliveredC,
frsldPvcDataDataDeliveredE,
frsldPvcDataDataOfferedC,
frsldPvcDataDataOfferedE,
frsldPvcDataUnavailableTime,
frsldPvcDataUnavailables
}
STATUS current
DESCRIPTION
"A collection of required objects providing data
collected on a PVC which implements Service
Level Definitions."
::= { frsldMIBGroups 5 }
frsldPvcDelayDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataDelayMin,
frsldPvcDataDelayMax,
Expires December 2000 Steinberger & Nicklass [Page 49]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcDataMissedPolls
}
STATUS current
DESCRIPTION
"A collection of optional objects providing delay
data collected on a PVC which implements Service
Level Definitions."
::= { frsldMIBGroups 6 }
frsldPvcHCFrameDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataHCFrDeliveredC,
frsldPvcDataHCFrDeliveredE,
frsldPvcDataHCFrOfferedC,
frsldPvcDataHCFrOfferedE
}
STATUS current
DESCRIPTION
"A collection of optional objects providing high
capacity frame data collected on a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 7 }
frsldPvcHCOctetDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataHCDataDeliveredC,
frsldPvcDataHCDataDeliveredE,
frsldPvcDataHCDataOfferedC,
frsldPvcDataHCDataOfferedE
}
STATUS current
DESCRIPTION
"A collection of optional objects providing high
capacity octet data collected on a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 8 }
frsldPvcDataSampleDelayGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataSmplDelayMin,
frsldPvcDataSmplDelayMax,
frsldPvcDataSmplDelayAvg,
frsldPvcDataSmplMissedPolls
}
STATUS current
DESCRIPTION
"A collection of optional objects providing delay
sample data collected on a PVC which implements
Expires December 2000 Steinberger & Nicklass [Page 50]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
Service Level Definitions."
::= { frsldMIBGroups 9 }
frsldPvcDataSampleDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataSmplFrDeliveredC,
frsldPvcDataSmplFrDeliveredE,
frsldPvcDataSmplFrOfferedC,
frsldPvcDataSmplFrOfferedE,
frsldPvcDataSmplDataDeliveredC,
frsldPvcDataSmplDataDeliveredE,
frsldPvcDataSmplDataOfferedC,
frsldPvcDataSmplDataOfferedE
}
STATUS current
DESCRIPTION
"A collection of optional objects providing data
and frame delivery sample data collected on a PVC
which implements Service Level Definitions."
::= { frsldMIBGroups 10 }
frsldPvcDataSampleHCFrameGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataSmplHCFrDeliveredC,
frsldPvcDataSmplHCFrDeliveredE,
frsldPvcDataSmplHCFrOfferedC,
frsldPvcDataSmplHCFrOfferedE
}
STATUS current
DESCRIPTION
"A collection of optional objects providing high
capacity frame delivery sample data collected on a PVC
which implements Service Level Definitions."
::= { frsldMIBGroups 11 }
frsldPvcDataSampleHCDataGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataSmplHCDataDeliveredC,
frsldPvcDataSmplHCDataDeliveredE,
frsldPvcDataSmplHCDataOfferedC,
frsldPvcDataSmplHCDataOfferedE
}
STATUS current
DESCRIPTION
"A collection of optional objects providing high
capacity data delivery sample data collected on a PVC
which implements Service Level Definitions."
::= { frsldMIBGroups 12 }
Expires December 2000 Steinberger & Nicklass [Page 51]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
frsldPvcAvailSampleAvailGroup OBJECT-GROUP
OBJECTS {
frsldPvcAvailSmplUnavailableTime,
frsldPvcAvailSmplUnavailables,
frsldPvcAvailSmplStartTime,
frsldPvcAvailSmplEndTime
}
STATUS current
DESCRIPTION
"A collection of optional objects providing
availability sample data collected on a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 13 }
frsldPvcDataSampleGeneralGroup OBJECT-GROUP
OBJECTS {
frsldPvcDataSmplStartTime,
frsldPvcDataSmplEndTime
}
STATUS current
DESCRIPTION
"A collection of optional objects providing
general sample data collected on a PVC which
implements Service Level Definitions."
::= { frsldMIBGroups 14 }
frsldCapabilitiesGroup OBJECT-GROUP
OBJECTS {
frsldPvcCtrlWriteCaps,
frsldSmplCtrlWriteCaps,
frsldRPCaps
}
STATUS current
DESCRIPTION
"A collection of required objects providing
capability information for this MIB."
::= { frsldMIBGroups 15 }
END
7. Acknowledgments
This document was produced by the Frame Relay Service MIB Working
Group. It is based on the Frame Relay Forum's implementation
agreement on service level definitions, FRF.13 [17].
The editors would like to thank the following people for their
helpful comments:
Expires December 2000 Steinberger & Nicklass [Page 52]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
o Ken Rehbehn, Visual Networks
o Santa Dasu, Quick Eagle Networks
Expires December 2000 Steinberger & Nicklass [Page 53]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
8. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999
[2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, STD
16, Performance Systems International, Hughes LAN Systems, May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
STD 16, Performance Systems International, Hughes LAN Systems, March
1991
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU
Braunschweig, SNMP Research, First Virtual Holdings, International
Network Services, April 1999
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First
Virtual Holdings, International Network Services, April 1999
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First
Virtual Holdings, International Network Services, April 1999
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, STD 15, SNMP Research, Performance
Systems International, Performance Systems International, MIT
Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction
to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover
Beach Consulting, Inc., International Network Services, January
Expires December 2000 Steinberger & Nicklass [Page 54]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
1996.
[11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999
[12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2574, IBM T. J. Watson Research, April 1999
[13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover
Beach Consulting, Inc., International Network Services, January
1996.
[14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, April 1999
[15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., April 1999
[16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to
Version 3 of the Internet-standard Network Management Framework",
RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc.,
Ericsson, Cisco Systems, April 1999
[17]Frame Relay Forum Technical Committee, "Service Level Definitions
Implementations Agreement", FRF.13, August 1998.
[18]Brown, T., "Definitions of Managed Objects for Frame Relay Service",
RFC 1604, Bell Communications Research, March 1994.
[19]Waldbusser, S., "Remote Network Monitoring Management Information
Base Version 2 using SMIv2", RFC 2021, International Network
Service, January 1997.
[20]Brown, C., Baker, F., "Management Information Base for Frame Relay
DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems,
September 1997.
Expires December 2000 Steinberger & Nicklass [Page 55]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
9. Security Considerations
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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
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
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
10. Authors' Addresses
Robert Steinberger
Paradyne Networks
Mailstop: LG-132
8545 126th Avenue North
Largo, FL USA 33773
Phone: 1(727)530-2395
Email: rsteinberger@paradyne.com
Orly Nicklass, Ph.D
RAD Data Communications Ltd.
12 Hanechoshet Street
Tel Aviv, Israel 69710
Phone: 972 3 7659969
Email: Orly_n@rrad.co.il
Expires December 2000 Steinberger & Nicklass [Page 56]
Internet Draft Frame Relay Service Level Defs MIB June 14, 2000
11. Copyright Section
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Expires December 2000 Steinberger & Nicklass [Page 57]
