📄 rfc3202.txt
字号:
Network Working Group R. Steinberger
Request for Comments: 3202 Paradyne Networks
Category: Standards Track O. Nicklass
RAD Data Communications Ltd.
January 2002
Definitions of Managed Objects
for Frame Relay Service Level Definitions
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
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.
Table of Contents
1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 3
3. Overview .................................................... 3
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 ........... 10
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.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.3. Creation Process ........................................ 15
3.6.4. Destruction Process ..................................... 15
Steinberger & Nicklass Standards Track [Page 1]
RFC 3202 Frame Relay Service Level Defs MIB January 2002
3.6.4.1. Manual Row Destruction ................................ 15
3.6.4.2. Automatic Row Destruction ............................. 16
3.6.5. Modification Process .................................... 16
3.6.6. Collection Process ...................................... 16
3.6.6.1. Remote Polling ........................................ 16
3.6.6.2. Sampling .............................................. 17
3.6.6.3. User History .......................................... 17
3.6.7. Use of MIB Module in Calculation of Service Level
Definitions .................................................... 17
3.6.8. Delay ................................................... 20
3.6.9. Frame Delivery Ratio .................................... 20
3.6.10. Data Delivery Ratio .................................... 21
3.6.11. Service Availability ................................... 21
4. Relation to Other MIB Modules ............................... 22
5. Structure of the MIB Module ................................. 23
5.1. frsldPvcCtrlTable ......................................... 23
5.2. frsldSmplCtrlTable ........................................ 23
5.3. frsldPvcDataTable ......................................... 23
5.4. frsldPvcSampleTable ....................................... 24
5.5. frsldCapabilities ......................................... 24
6. Persistence of Data ......................................... 24
7. Object Definitions .......................................... 24
8. Acknowledgments ............................................. 61
9. References .................................................. 61
10. Security Considerations .................................... 63
11. Authors' Addresses ......................................... 63
12. Full Copyright Statement ................................... 64
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 STD
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, 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 STD 15, 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
Steinberger & Nicklass Standards Track [Page 2]
RFC 3202 Frame Relay Service Level Defs MIB January 2002
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 STD 15, 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.
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 [22].
3. Overview
This MIB module 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)
Steinberger & Nicklass Standards Track [Page 3]
RFC 3202 Frame Relay Service Level Defs MIB January 2002
This section provides an overview and background of how to use this
MIB module.
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
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 module.
Consult FRF.13 [17] for more details.
Steinberger & Nicklass Standards Track [Page 4]
RFC 3202 Frame Relay Service Level Defs MIB January 2002
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
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
Steinberger & Nicklass Standards Track [Page 5]
RFC 3202 Frame Relay Service Level Defs MIB January 2002
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 module are shown in figure 2 below. For completeness, the
module 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.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -