idnits 2.17.1 draft-ietf-frnetmib-frmrelay-service-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 143: '... The keywords MUST, MUST NOT, REQUIR...' RFC 2119 keyword, line 144: '... SHOULD NOT, RECOMMENDED, NOT RECOMM...' RFC 2119 keyword, line 258: '...etary reference points which MAY exist...' RFC 2119 keyword, line 426: '...monitoring point MAY be implemented in...' RFC 2119 keyword, line 435: '...monitoring point MAY be restricted to ...' (39 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 985 has weird spacing: '...(1) and frCir...' == Line 2894 has weird spacing: '...for the purpo...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: 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. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 18, 2001) is 8348 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '10' is mentioned on line 113, but not defined == Missing Reference: '11' is mentioned on line 113, but not defined == Missing Reference: '12' is mentioned on line 2853, but not defined == Missing Reference: '13' is mentioned on line 118, but not defined == Missing Reference: '14' is mentioned on line 120, but not defined == Missing Reference: '15' is mentioned on line 2854, but not defined == Missing Reference: '16' is mentioned on line 125, but not defined == Missing Reference: '23' is mentioned on line 147, but not defined == Missing Reference: '17' is mentioned on line 2733, but not defined == Missing Reference: '18' is mentioned on line 995, but not defined == Missing Reference: '19' is mentioned on line 770, but not defined == Missing Reference: '21' is mentioned on line 972, but not defined == Missing Reference: '20' is mentioned on line 974, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') Summary: 10 errors (**), 0 flaws (~~), 18 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Managed Objects 2 for Frame Relay Service Level Definitions 4 June 18, 2001 6 draft-ietf-frnetmib-frmrelay-service-05.txt 8 Robert A. Steinberger 9 Paradyne Networks 10 robert.steinberger@fnc.fujitsu.com 12 Orly Nicklass, Ph.D 13 RAD Data Communications Ltd. 14 Orly_n@rad.co.il 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, 21 and its working groups. Note that other groups may also distribute 22 working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This memo defines an extension of the Management Information Base 38 (MIB) for use with network management protocols in TCP/IP-based 39 internets. In particular, it defines objects for managing the Frame 40 Relay Service Level Definitions. 42 Copyright Notice 44 Copyright (C) The Internet Society (2001). All Rights Reserved. 46 Table of Contents 48 1. The SNMP Management Framework ............................... 3 49 2. Conventions ................................................. 4 50 3. Overview .................................................... 4 51 3.1. Frame Relay Service Level Definitions ..................... 4 52 3.2. Terminology ............................................... 5 53 3.3. Network Model ............................................. 5 54 3.4. Reference Points .......................................... 6 55 3.5. Measurement Methodology ................................... 8 56 3.6. Theory of Operation ....................................... 9 57 3.6.1. Capabilities Discovery .................................. 9 58 3.6.2. Determining Reference Points for Row Creation ........... 10 59 3.6.2.1. Graphical Examples of Reference Points ................ 11 60 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example ...... 12 61 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example ... 13 62 3.6.2.1.3. End-to-End Using Reference Point Example ............ 14 63 3.6.3. Creation Process ........................................ 15 64 3.6.4. Destruction Process ..................................... 15 65 3.6.4.1. Manual Row Destruction ................................ 16 66 3.6.4.2. Automatic Row Destruction ............................. 16 67 3.6.5. Modification Process .................................... 16 68 3.6.6. Collection Process ...................................... 16 69 3.6.6.1. Remote Polling ........................................ 16 70 3.6.6.2. Sampling .............................................. 17 71 3.6.6.3. User History .......................................... 18 72 3.6.7. Use of MIB Module in Calculation of Service Level 73 Definitions .................................................... 18 74 3.6.8. Delay ................................................... 20 75 3.6.9. Frame Delivery Ratio .................................... 20 76 3.6.10. Data Delivery Ratio .................................... 21 77 3.6.11. Service Availability ................................... 21 78 4. Relation to Other MIB Modules ............................... 22 79 5. Structure of the MIB Module ................................. 23 80 5.1. frsldPvcCtrlTable ......................................... 23 81 5.2. frsldSmplCtrlTable ........................................ 24 82 5.3. frsldPvcDataTable ......................................... 24 83 5.4. frsldPvcSampleTable ....................................... 24 84 5.5. frsldCapabilities ......................................... 24 85 6. Persistence of Data ......................................... 24 86 7. Object Definitions .......................................... 24 87 8. Acknowledgments ............................................. 59 88 9. References .................................................. 60 89 10. Security Considerations .................................... 63 90 11. Authors' Addresses ......................................... 63 91 12. Copyright Section .......................................... 64 93 1. The SNMP Management Framework 95 The SNMP Management Framework presently consists of five major 96 components: 98 o An overall architecture, described in RFC 2571 [1]. 100 o Mechanisms for describing and naming objects and events for the 101 purpose of management. The first version of this Structure of 102 Management Information (SMI) is called SMIv1 and described in RFC 103 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 104 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 105 2580 [7]. 107 o Message protocols for transferring management information. The 108 first version of the SNMP message protocol is called SNMPv1 and 109 described in RFC 1157 [8]. A second version of the SNMP message 110 protocol, which is not an Internet standards track protocol, is 111 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 112 The third version of the message protocol is called SNMPv3 and 113 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 115 o Protocol operations for accessing management information. The 116 first set of protocol operations and associated PDU formats is 117 described in RFC 1157 [8]. A second set of protocol operations and 118 associated PDU formats is described in RFC 1905 [13]. 120 o A set of fundamental applications described in RFC 2573 [14] and 121 the view-based access control mechanism described in RFC 2575 122 [15]. 124 A more detailed introduction to the current SNMP Management Framework 125 can be found in RFC 2570 [16]. 127 Managed objects are accessed via a virtual information store, termed 128 the Management Information Base or MIB. Objects in the MIB are 129 defined using the mechanisms defined in the SMI. 131 This memo specifies a MIB module that is compliant to the SMIv2. A 132 MIB conforming to the SMIv1 can be produced through the appropriate 133 translations. The resulting translated MIB must be semantically 134 equivalent, except where objects or events are omitted because no 135 translation is possible (use of Counter64). Some machine readable 136 information in SMIv2 will be converted into textual descriptions in 137 SMIv1 during the translation process. However, this loss of machine 138 readable information is not considered to change the semantics of the 139 MIB. 141 2. Conventions 143 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 144 SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when 145 they appear in this document, are to be interpreted as described in 146 RFC 2119 [23]. 148 3. Overview 150 This MIB module addresses the items required to manage the Frame 151 Relay Forum's Implementation Agreement for Service Level Definitions 152 (FRF.13 [17]). At present, this applies to these values of the 153 ifType variable in the Internet-standard MIB: 155 o frameRelay (32) 157 o frameRelayService (44) 159 This section provides an overview and background of how to use this 160 MIB module. 162 3.1. Frame Relay Service Level Definitions 164 The frame relay service level definitions address specific 165 characteristics of a frame relay service that can be used to 166 facilitate the following tasks: 168 o Evaluation of frame relay service providers, offerings or 169 products. 171 o Measurement of Quality of Service. 173 o Enforcement of Service Level Agreements. 175 o Planning or describing a frame relay network. 177 The following parameters are defined in FRF.13 [17] as a sufficient 178 set of values to accomplish the tasks previously stated. 180 o Delay - The amount of time elapsed, in microseconds, from the time 181 a frame exits the source to the time it reaches the destination. 182 NOTE: FRF.13 [17] defines this value in terms of milliseconds. 184 o Frame Delivery Ratio - The ratio of the number of frames delivered 185 to the destination versus the number of frames sent by the source. 186 This ratio can be further divided by inspecting either only the 187 frames within the CIR or only the frames in excess of the CIR. 189 o Data Delivery Ratio - The ratio of the amount of data delivered to 190 the destination versus the amount of data sent by the source. This 191 ratio can be further divided by inspecting either only the data 192 within the CIR or only the data in excess of the CIR. 194 o Service Availability - The amount of time the frame relay service 195 was not available. There are three types of availability 196 statistics defined in FRF.13 [17]: Mean Time to Repair, Virtual 197 Connection Availability, and Mean Time Between Service Outages. 198 The later two require information about the scheduled outage time. 199 It is assumed that scheduled outage time information will be 200 maintained by the network management software, so it is not 201 included in the MIB module. 203 Consult FRF.13 [17] for more details. 205 3.2. Terminology 207 o CIR - The Committed Information Rate (CIR) is the subscriber data 208 rate (expressed in bits/second) that the network commits to 209 deliver under normal network conditions. [18] 211 o DLCI - Data Link Connection Identifier. [18] 213 o Logical Port - This term is used to model the Frame Relay 214 "interface" on a device. [18] 216 o NNI - Network to Network Interface. [18] 218 o Permanent Virtual Connection (PVC) - A virtual connection that has 219 its end-points and bearer capabilities defined at subscription 220 time. [18] 222 o Reference Point (RP) - The point of reference within the network 223 model at which the calculations or data collection takes place. 225 o UNI - User to Network Interface. [18] 227 3.3. Network Model 229 The basic model, as illustrated in figure 1 below, contains two frame 230 relay DTE endpoints connected to a network cloud via a frame relay 231 UNI interface. The network cloud can contain zero or more internal 232 frame relay NNI connections that interconnect multiple networks. The 233 calculations and data collection can be performed at any reference 234 point within the network. 236 +-------------+ +-------------+ 237 | Frame Relay | | Frame Relay | 238 | DTE Device | | DTE Device | 239 +------+------+ +------+------+ 240 | | 241 UNI UNI 242 Connection Connection 243 | | 244 +------+------+ NNI +-------------+ NNI +------+------+ 245 | Network A +------------+ Network B +------------+ Network C | 246 +-------------+ Connection +-------------+ Connection +-------------+ 248 Figure 1 249 Frame Relay Network Reference Model 251 3.4. Reference Points 253 The collection and calculations of the service level definitions 254 apply to two reference points within the network. These two points 255 are the locations where the frames are referenced in the collection 256 of the service level specific information. The reference points used 257 in the MIB module are shown in figure 2 below. For completeness, the 258 module also allows for proprietary reference points which MAY exist 259 anywhere in the network that is not a previously defined reference 260 point. The meaning of the proprietary reference points is 261 insignificant unless defined by the device manufacturer. 263 +---------------------------+ 264 |+-----------+ +-----------+| 265 || | |Measurement|| 266 ||Frame Relay---Engine --(Source RP)----+ 267 ||DTE | |(If Exists)|| | 268 |+-----------+ +-----------+| | 269 +---------------------------+ | 270 Frame Relay Source | 271 +------------------------------------------+ 272 | Frame Relay Network 273 | +----------------------------------+ 274 | | +------------------------------+ | 275 | | | +---------+ +---------+ | | 276 | | | | | | Traffic | | | 277 +--(Ingress RP)--- L1 / L2 --- Policing| | | 278 | | | Control | | Engine | | | 279 | | +---------+ +----|----+ | | 280 | | | | | 281 | | (Traffic Policing RP)| | 282 | +------------------|-----------+ | 283 | Ingress Node | | 284 | | | 285 | +-----------|-----------+ | 286 | | Intermediate Nodes | | 287 | +-----------|-----------+ | 288 | | | 289 | Egress Node | | 290 | +--------------|-----------+ | 291 | | (Egress Queue Input RP) | | 292 | | | | | 293 | | +-------+------+ | | 294 | | | Egress Queue | | | 295 | | +-------+------+ | | 296 | | | | | 297 | | (Egress Queue Output RP) | | 298 | +--------------|-----------+ | 299 +--------------------|-------------+ 300 Frame Relay Destination | 301 +---------------------------+ +-----------+ 302 |+-----------+ +-----------+| | 303 || | |Measurement|| | 304 ||Frame Relay---Engine --(Destination RP)--+ 305 ||DTE | |(If Exists)|| 306 |+-----------+ +-----------+| 307 +---------------------------+ 309 Figure 2 310 Reference Points (FRF.13 [17]) 312 The MIB variables frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP 313 allow the user to view and configure the reference points at which 314 the calculations occur. These variables are specific to the device 315 on which they are located. Frame relay devices act as both frame 316 sources and frame destinations. The definitions in this MIB module 317 apply to the interaction of a pair of devices on the network path. 318 The same device can potentially use different reference points for 319 calculation and collection of the statistics based on whether the 320 referenced frame is sent or received by the device. When the device 321 is acting as a frame source, the value of frsldPvcCtrlTransmitRP 322 reflects the reference point used for all source calculations 323 pertaining to the specified PVC. When the device is acting as a frame 324 destination, the value of frsldPvcCtrlReceiveRP reflects the 325 reference point used for all destination calculations pertaining to 326 the specified PVC. 328 For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue 329 measurement domain as a domain in which measurement is performed 330 between an Ingress Reference Point and an Egress Queue Input 331 Reference Point. For this domain between a source device and a 332 destination device, the value of frsldPvcCtrlTransmitRP for the 333 source device would be set to ingTxLocalRP(2) and the value of 334 frsldPvcCtrlReceiveRP for the destination device would be set to 335 eqiRxLocalRP(4). While it is usually the case that the reference 336 points would be equivalent on the remote device when monitoring 337 frames going in the opposite direction, there is no requirement for 338 them to be so. 340 It can be seen from the above example that a total of four reference 341 points are required in order to collect information for both 342 directions of traffic flow. The reference points represent the 343 transmit and receive directions at both ends of a PVC. If a device 344 has knowledge of the information from the remote device, it is 345 possible to collect the statistics from a single device. This is not 346 always the case. In most instances, two devices will need to be 347 monitored to capture a complete description of the service level on a 348 PVC. The reference points a single device is capable of monitoring 349 are contained in the frsldRPCaps object. 351 3.5. Measurement Methodology 353 This document neither recommends nor suggests a method of 354 implementation. This is left to the device manufacturer and should be 355 independent of the data that is actually collected. 357 Periodic collection of this data can be performed through either 358 polling of the data table, use of the sample tables or use of the 359 user history group of RFC 2021 [19]. 361 3.6. Theory of Operation 363 The following sections describe how to use this MIB module. They 364 include row handling, data collection and data calculation. The 365 recommendations here in are suggestions as to implementation and do 366 not infer that they are the only method that can be used to perform 367 such operations. 369 3.6.1. Capabilities Discovery 371 Three objects are provided specifically to aid the network manager in 372 discovering the capabilities of the device with respect to this MIB 373 module. 375 o frsldPvcCtrlWriteCaps This object reports the write capabilities 376 of the PVC Control Table. Use this object 377 to determine which objects can be modified. 378 This need only be referenced if row 379 creation or modification is to be 380 performed. 382 o frsldSmplCtrlWriteCaps This object reports the write capabilities 383 of the Sample Control Table. Use this 384 object to determine which objects can be 385 modified. The group need only be 386 referenced if the sample tables will be 387 used to collect historical information. 389 o frsldRPCaps This object reports the reference points at 390 which the device is capable of collecting 391 information. This object needs to be 392 referenced if row creation is to be 393 performed in the PVC Control Table. 394 Devices can only create rows containing 395 supported reference points. 397 These objects do not imply that there is no need for an Agent 398 Capabilities macro for devices that do not fully support every object 399 in this MIB module. They are provided specifically to aid in the 400 ensured network management operations of this MIB module with respect 401 to row creation and modification. 403 An additional four objects are provided to report and control memory 404 the utilization of this MIB module. These objects are 405 frsldMaxPvcCtrls, frsldNumPvcCtrls, frsldMaxSmplCtrls are 406 frsldNumSmplCtrls. Together, they allow a manager to control the 407 amount of memory allocated for specific utilization by this MIB 408 module. This is done by setting the maximum allowed allocation of 409 controls. 411 3.6.2. Determining Reference Points for Row Creation 413 The performance of a PVC is monitored by evaluating the uni- 414 directional flow of frames from an ingress point to an egress point. 415 Reference points describe where each of the two measurements are 416 made. Monitoring both of the uni-directional flows that make-up the 417 PVC frame traffic requires a total of four reference points as shown 418 in Figures 3 through 5. A monitoring point that evaluates traffic is 419 restricted to counting frames that pass the reference points hosted 420 locally on the monitoring point. Thus, if the monitoring point is 421 near the ingress point of the flow, it will count the frames entering 422 into the frame relay network. The complete picture of frame loss for 423 the uni-directional flow requires information from the downstream 424 reference point located at another (remote) monitoring point. 426 The local monitoring point MAY be implemented in such way that the 427 information from the downstream monitoring point is moved to the 428 local monitoring point using implementation-specific mechanisms. In 429 this case all information required to calculate frame loss becomes 430 available from the local measurement point. The local measurement 431 point agent is capable of reporting all the objects in the 432 FrsldPvcDataEntry row - the counts for offered frames entering the 433 network and delivered frames exiting the network. 435 Alternatively, the local monitoring point MAY be restricted to counts 436 of frames observed on the local device only. In this case, the 437 objects of the FrsldPvcDataEntry row reporting what happened on the 438 remote device are not available. 440 The following list shows the possible valid reference points for an 441 FRF.13 SLA from the source reference point to the destination 442 reference point in both directions. 444 o Local Information Only 446 Local Device: srcLocalRP, desLocalRP 447 Remote Device: srcLocalRP, desLocalRP 449 o Remote Information Only 451 Local Device: srcRemoteRP, desRemoteRP 452 Remote Device: srcRemoteRP, desRemoteRP 454 o Mixed Two Device Model 1 (Local Device Always Transmitter) 456 Local Device: srcLocalRP, desRemoteRP 457 Remote Device: srcLocalRP, desRemoteRP 459 o Mixed Two Device Model 2 (Local Device Always Receiver) 461 Local Device: srcRemoteRP, desLocalRP 462 Remote Device: srcRemoteRP, desLocalRP 464 o Mixed One Device Model 1 (Directional Rows) 466 First Row: srcRemoteRP, desLocalRP (Receiver Row) 467 Second Row: srcLocalRP, desRemoteRP (Sender Row) 469 o Mixed One Device Model 2 (Device Based Rows) 471 First Row: srcLocalRP, desLocalRP (Local Row) 472 Second Row: srcRemoteRP, desRemoteRP (Remote Row) 474 Each of the above combinations is valid and provides the same 475 information. 477 The following steps are recommended to find which reference points 478 need to be configured: 480 1) Locate both of the devices at either end of the PVC to be 481 monitored. 483 2) Determine the capabilities by referencing the frsldRPCaps object 484 of each device. 486 3) Locate the best combination of the two devices such that the 487 necessary reference points are all represented. 489 4) If any one of the necessary reference points does not exist in 490 the combination of the two devices, it is not possible to 491 monitor the FRF.13 defined SLA between the two reference point 492 on the PVC. 494 3.6.2.1. Graphical Examples of Reference Points 496 FRF.13 [17] defines three specific combinations of reference points: 497 Edge-to-Edge Interface, Edge-to-Edge Egress Queue and End-to-End. 499 Examples of valid reference points that may be used for each of these 500 are discussed in the sections below. 502 It is often the case that a device knows as a minimum either only 503 local information or both local and remote information. Because 504 these are two common examples, each will be illustrated below. 506 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example 508 Device 1 Device 2 509 +-------------+ +-------------+ 510 | Ingress | | Egress | 511 | +-----+ | | +-----+ | 512 |(A)| | | Traffic Flow | | |(B)| 513 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 514 | | | | From Device 1 to 2 | | | | 515 | +-----+ | | +-----+ | 516 | | | | 517 | Egress | | Ingress | 518 | +-----+ | | +-----+ | 519 |(D)| | | Traffic Flow | | |(C)| 520 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 521 | | | | From Device 2 to 1 | | | | 522 | +-----+ | | +-----+ | 523 +-------------+ +-------------+ 525 where (A), (B), (C) and (D) are reference points 527 Figure 3 529 For devices with only local knowledge, one row is required on each 530 device as follows: 532 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 534 (B) frsldPvcCtlrReceiveRP for Device 2 = eqoRxLocalRP(5) 536 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 538 (D) frsldPvcCtlrReceiveRP for Device 1 = eqoRxLocalRP(5) 540 In which a single row is created on Device 1 containing reference 541 points (A) and (D), and a single row is created on Device 2 542 containing reference points (C) and (B). 544 For devices with both local and remote knowledge, the two rows can 545 exist in any combination on either device. For this example, the 546 transmitting devices will be responsible for information regarding 547 the flow for which they are the origin. Only one row is required per 548 device for this example. 550 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 552 (B) frsldPvcCtlrReceiveRP for Device 1 = eqoRxRemoteRP(11) 554 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 556 (D) frsldPvcCtlrReceiveRP for Device 2 = eqoRxRemoteRP(11) 558 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example 560 Device 1 Device 2 561 +-------------+ +-------------+ 562 | Ingress | | Egress | 563 | +-----+ | | +-----+ | 564 |(A)| | | Traffic Flow |(B)| | | 565 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 566 | | | | From Device 1 to 2 | | | | 567 | +-----+ | | +-----+ | 568 | | | | 569 | Egress | | Ingress | 570 | +-----+ | | +-----+ | 571 | | |(D)| Traffic Flow | | |(C)| 572 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 573 | | | | From Device 2 to 1 | | | | 574 | +-----+ | | +-----+ | 575 +-------------+ +-------------+ 577 where (A), (B), (C) and (D) are reference points 579 Figure 4 581 For devices with only local knowledge, one row is required on each 582 device as follows: 584 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 586 (B) frsldPvcCtlrReceiveRP for Device 2 = eqiRxLocalRP(4) 588 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 590 (D) frsldPvcCtlrReceiveRP for Device 1 = eqiRxLocalRP(4) 592 In which a single row is created on Device 1 containing reference 593 points (A) and (D), and a single row is created on Device 2 594 containing reference points (C) and (B). 596 For devices with both local and remote knowledge, the two rows can 597 exist in any combination on either device. For this example, the 598 transmitting devices will be responsible for information regarding 599 the flow for which they are the origin. Only one row is required per 600 device for this example. 602 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 604 (B) frsldPvcCtlrReceiveRP for Device 1 = eqiRxRemoteRP(10) 606 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 608 (D) frsldPvcCtlrReceiveRP for Device 2 = eqiRxRemoteRP(10) 610 3.6.2.1.3. End-to-End Using Reference Point Example 612 Device 1 Device 2 613 +-------------+ +-------------+ 614 | Source | | Destination | 615 | +-----+ | | +-----+ | 616 |(A)| | | Traffic Flow | | |(B)| 617 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 618 | | | | From Device 1 to 2 | | | | 619 | +-----+ | | +-----+ | 620 | | | | 621 | Destination | | Source | 622 | +-----+ | | +-----+ | 623 |(D)| | | Traffic Flow | | |(C)| 624 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 625 | | | | From Device 2 to 1 | | | | 626 | +-----+ | | +-----+ | 627 +-------------+ +-------------+ 629 where (A), (B), (C) and (D) are reference points 631 Figure 5 633 For devices with only local knowledge, one row is required on each 634 device as follows: 636 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 638 (B) frsldPvcCtlrReceiveRP for Device 2 = desLocalRP(1) 639 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 641 (D) frsldPvcCtlrReceiveRP for Device 1 = desLocalRP(1) 643 In which a single row is created on Device 1 containing reference 644 points (A) and (D), and a single row is created on Device 2 645 containing reference points (C) and (B). 647 For devices with both local and remote knowledge, the two rows can 648 exist in any combination on either device. For this example, the 649 transmitting devices will be responsible for information regarding 650 the flow for which they are the origin. Only one row is required per 651 device for this example. 653 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 655 (B) frsldPvcCtlrReceiveRP for Device 1 = desRemoteRP(7) 657 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 659 (D) frsldPvcCtlrReceiveRP for Device 2 = desRemoteRP(7) 661 3.6.3. Creation Process 663 In some cases, devices will automatically populate the rows of PVC 664 Control Table and potentially the Sample Control Table. However, in 665 many cases, it may be necessary for a network manager to manually 666 create rows. 668 Manual creation of rows requires the following steps: 670 1) Ensure the PVC exists between the two devices. 672 2) Determine the necessary reference points for row creation. 674 3) Create the row(s) in each device as needed. 676 4) Create the row(s) in the sample control tables if desired. 678 3.6.4. Destruction Process 679 3.6.4.1. Manual Row Destruction 681 Manual row destruction is straight forward. Any row can be destroyed 682 and the resources allocated to it are freed by setting the value of 683 its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus) 684 to destroy(6). It should be noted that when frsldPvcCtrlStatus is 685 set to destroy(6) all associated sample control, sample and data 686 table rows will also be destroyed. Similarly, when 687 frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be 688 destroyed. The frsldPvcCtrlPurge objects do not apply to manual row 689 destruction. If the row is set to destroy(6) manually, the rows are 690 destroyed as part of the set. 692 3.6.4.2. Automatic Row Destruction 694 Rows is the tables may be destroyed automatically based on the 695 existence of the DLCI on which they rely. This behavior is 696 controlled by the frsldPvcCtrlPurge and frsldPvcCtrlDeleteOnPurge 697 objects. When a DLCI no longer exists in the device, the data in the 698 tables has no relation to anything known on the network. However, 699 there may be some need to keep the historic information active for a 700 short period after the destruction or removal of a DLCI. If the 701 basis for the row no longer exists, the row will be destroyed at the 702 end of the purge interval that is controlled by frsldPvcCtrlPurge. 704 The effects of automatic row destruction are the same as manual row 705 destruction. 707 3.6.5. Modification Process 709 All read-create items in this MIB module can be modified at any time 710 if they are fully supported. Write access is not required. To 711 simplify the use of the MIB frsldPvcCtrlWriteCaps and 712 frsldSmplCtrlWriteCaps state which of the read-create variables can 713 actually be written on a particular device. 715 3.6.6. Collection Process 717 3.6.6.1. Remote Polling 719 This MIB module supports data collection through remote polling of 720 the free running counters in the PVC Data Table. Remote polling is a 721 common method used to capture real-time statistics. A remote 722 management station polls the device to collect the desired 723 information. It is recommended all statistics for a single PVC be 724 collected in a single PDU. 726 The following objects are designed around the concept of real-time 727 polling: 729 o frsldPvcDataMissedPolls 730 o frsldPvcDataFrDeliveredC 731 o frsldPvcDataFrDeliveredE 732 o frsldPvcDataFrOfferedC 733 o frsldPvcDataFrOfferedE 734 o frsldPvcDataDataDeliveredC 735 o frsldPvcDataDataDeliveredE 736 o frsldPvcDataDataOfferedC 737 o frsldPvcDataDataOfferedE 738 o frsldPvcDataHCFrDeliveredC 739 o frsldPvcDataHCFrDeliveredE 740 o frsldPvcDataHCFrOfferedC 741 o frsldPvcDataHCFrOfferedE 742 o frsldPvcDataHCDataDeliveredC 743 o frsldPvcDataHCDataDeliveredE 744 o frsldPvcDataHCDataOfferedC 745 o frsldPvcDataHCDataOfferedE 746 o frsldPvcDataUnavailableTime 747 o frsldPvcDataUnavailables 749 3.6.6.2. Sampling 751 The sample tables provide the ability to historically sample data 752 without requiring the additional overhead of polling. At key 753 periods, a network management station can collect the samples needed. 754 This method allows the manager to perform the collection of data at 755 times that will least affect the active network traffic. 757 The sample data can be collected using a series of SNMP getNext or 758 getBulk operations. The value of frsldPvcSmplIdx increments with 759 each new collection bucket. This allows the managers to skip 760 information that has already been collected. However, care should be 761 taken in that the value can roll over after a long period of time. 763 The start and end times of a collection period allow the manager to 764 know what the actual period of collection was. It is possible for 765 there to be discontinuities in the sample table, so both start and 766 end should be referenced. 768 3.6.6.3. User History 770 User history, as defined in RFC 2021 [19], is an alternative 771 mechanism that can be used to get the same benefits as the sample 772 table by using the objects provided for real-time polling. Some 773 devices MAY have the ability to use user history and opt not to 774 support the sample tables. If this is the case, the information from 775 the data table can be used to define a group of user history objects. 777 3.6.7. Use of MIB Module in Calculation of Service Level Definitions 779 The objects in this MIB module can be used to calculate the 780 statistics defined in FRF.13 [17]. The description below describes 781 the calculations for one direction of the data flow, i.e. data sent 782 from local transmitter to a remote receiver. A complete set of 783 bidirectional information would require calculations based on both 784 directions. For the purposes of this description, the reference 785 points used SHOULD consistently represent data that is sent by one 786 device and received by the other. 788 A complete evaluation requires the combination of two uni-directional 789 flows. It is possible for a management station to combine all of the 790 calculated information into one conceptual row. Doing this requires 791 that each of the metrics are collected for both flow directions and 792 grouped by direction If the information is split between two 793 devices, the management station must know which two devices to 794 communicate with for the collection of all information. The grouping 795 of information SHOULD be from ingress to egress in each flow 796 direction. 798 The calculations below use the following terminology: 800 o DelayAvg 802 The average delay on the PVC. This is represented within the 803 MIB module by frsldPvcSmplDelayAvg. 805 o FrDeliveredC 807 The number of frames received by the receiving device through 808 the receive reference point that were delivered within CIR. 809 This is represented within the MIB module by one of 810 frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC, 811 frsldPvcSmplFrDeliveredC, or frsldPvcSmplHCFrDeliveredC. 813 o FrDeliveredE 814 The number of frames received by the receiving device through 815 the receive reference point that were delivered in excess of 816 CIR. This is represented within the MIB module by one of 817 frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE, 818 frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE. 820 o FrOfferedC 822 The number of frames offered by the transmitting device through 823 the transmit reference point that were sent within CIR. This is 824 represented within the MIB module by one of 825 frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC, 826 frsldPvcSmplFrOfferedC, or frsldPvcSmplHCFrOfferedC. 828 o FrOfferedE 830 The number of frames offered by the transmitting device through 831 the transmit reference point that were sent in excess of CIR. 832 This is represented within the MIB module by one of 833 frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE, 834 frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE. 836 o DataDeliveredC 838 The number of octets received by the receiving device through 839 the receive reference point that were delivered within CIR. 840 This is represented within the MIB module by one of 841 frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC, 842 frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC. 844 o DataDeliveredE 846 The number of octets received by the receiving device through 847 the receive reference point that were delivered in excess of 848 CIR. This is represented within the MIB module by one of 849 frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE, 850 frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE. 852 o DataOfferedC 854 The number of octets offered by the transmitting device through 855 the transmit reference point that were sent within CIR. This is 856 represented within the MIB module by one of 857 frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC, 858 frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC. 860 o DataOfferedE 861 The number of octets offered by the transmitting device through 862 the transmit reference point that were sent in excess of CIR. 863 This is represented within the MIB module by one of 864 frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE, 865 frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE. 867 o UnavailableTime 869 The amount of time the PVC was not available during the interval 870 of interest. This is represented within the MIB module by 871 either frsldPvcDataUnavailableTime or 872 frsldPvcSmplUnavailableTime. 874 o Unavailables 876 The number of times the PVC was declared to be unavailable 877 during the interval of interest. This is represented within the 878 MIB module by either frsldPvcDataUnavailables or 879 frsldPvcSmplUnavailables. 881 3.6.8. Delay 883 The frame transfer delay is defined as the amount of time elapsed, in 884 microseconds, from the time a frame exits the source to the time it 885 reaches the destination. The average delay can be found using the MIB 886 variable described in DelayAvg above. The delay may be calculated as 887 either round trip or one way, and this information is held in the 888 frsldPvcCtrlDelayType MIB variable. If the delay be calculated as 889 round trip, the value of DelayAvg represents the average of the total 890 delays of the round trips. In this case, the manager SHOULD divide 891 the value returned by the agent by two to obtain the frame transfer 892 delay. In the case that frsldPvcCtrlDelayType is oneWay, the value 893 of DelayAvg represents the average of the frame transfer delays and 894 SHOULD be used as is. 896 3.6.9. Frame Delivery Ratio 898 The frame delivery ratio is defined as the total number of frames 899 delivered to the destination divided by the frames offered by the 900 source. The destination values can be obtained using FrDeliveredC 901 and FrDeliveredE. The source values can be obtained using FrOfferedC 902 and FrOfferedE. 904 FrDeliveredC + FrDeliveredE 905 Frame Delivery Ratio = --------------------------- 906 FrOfferedC + FrOfferedE 908 FrDeliveredC 909 Committed Frame Delivery Ratio = ------------ 910 FrOfferedC 912 FrDeliveredE 913 Excess Frame Delivery Ratio = ------------ 914 FrOfferedE 916 3.6.10. Data Delivery Ratio 918 The data delivery ratio is defined as the total amount of data 919 delivered to the destination divided by the data offered by the 920 source. The destination values can be obtained using DataDeliveredC 921 and DataDeliveredE. The source values can be obtained using 922 DataOfferedC and DataOfferedE. 924 DataDeliveredC + DataDeliveredE 925 Data Delivery Ratio = ------------------------------- 926 DataOfferedC + DataOfferedE 928 DataDeliveredC 929 Committed Data Delivery Ratio = -------------- 930 DataOfferedC 932 DataDeliveredE 933 Excess Data Delivery Ratio = -------------- 934 DataOfferedE 936 3.6.11. Service Availability 938 Some forms of service availability measurement defined in FRF.13 [17] 939 require knowledge of the amount of time the network is allowed to be 940 unavailable during the period of measurement. This is called the 941 excluded outage time and will be represented in the measurements 942 below as ExcludedTime. It is assumed that the management software 943 will maintain this information in that it often relates to specific 944 times and dates that many devices are not capable of maintaining. 945 Further, it may change based on a moving maintenance window that the 946 device cannot track well. 948 Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0. 950 UnavailableTime 951 Otherwise, FRMTTR = --------------- 952 Unavailables 954 Virtual Connection Availability (FRVCA) = 0 if IntervalTime equals 955 ExcludedTime. 957 IntervalTime - ExcludedTime - UnavailableTime 958 Otherwise, FRVCA = --------------------------------------------- *100 959 IntervalTime - ExcludedTime 961 Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0. 963 Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime 964 --------------------------------------------- 965 Unavailables 967 4. Relation to Other MIB Modules 969 There is no explicit relation to any other frame relay MIB module nor 970 are any required to implement this MIB module. However, there is a 971 need for knowledge of ifIndexes and some understanding of DLCIs. The 972 ifIndex information can be found in the IF-MIB [21] which is 973 required. The DLCI information can be found in either the Frame Relay 974 DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC 975 1604) [18]; however, neither is required. 977 Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to 978 active(1) the system can be in one of the following three states: 980 (1) The respective DLCI is known and is active. This corresponds to a 981 state in which frPVCEndptRowStatus is active(1) and 982 frPVCEndptRcvdSigStatus is either active(2) or none(4) for the 983 Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame 984 Relay DTE MIB, the same state is shown by frCircuitRowStatus of 985 active(1) and frCircuitState of active(2). 987 (2) The respective DLCI has not been created. This corresponds to a 988 state in which the row with either frPVCEndptDLCIIndex or 989 frCircuitDlci equal to the respective DLCI does not exist in 990 either the frPVCEndptTable or the frCircuitTable respectively. 992 (3) The respective DLCI has just been removed. This corresponds to a 993 state in which either frPVCEndptRowStatus is no longer active(1) 994 or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for 995 the Frame Relay Network Services MIB (RFC 1604) [18]. For the 996 Frame Relay DTE MIB, the same state is shown when either 997 frCircuitRowStatus is no longer active(1) or frCircuitState is no 998 longer active(2). 1000 For the first case, the row in the frsldPvcDataTable will be filled. 1001 If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective 1002 DLCI is also `active' the frsldPvcSampleTable will be filled as well. 1004 For the second case, the respective rows will not be added to any of 1005 the data or sample tables and frsldPvcCtrlStatus SHOULD report 1006 notReady(3). 1008 For the third case, frsldPvcCtrlDeleteOnPurge should direct the 1009 behavior of the system. If all tables are purged, this case will be 1010 equivalent to the second case above. Otherwise, frsldPvcCtrlStatus 1011 SHOULD remain active(1). 1013 5. Structure of the MIB Module 1015 The FRSLD-MIB consists of the following components: 1017 o frsldPvcCtrlTable 1019 o frsldSmplCtrlTable 1021 o frsldPvcDataTable 1023 o frsldPvcSampleTable 1025 o frsldCapabilities 1027 Refer to the compliance statement defined within for a definition of 1028 what objects MUST be implemented. 1030 5.1. frsldPvcCtrlTable 1032 The frsldPvcCtrlTable is the central control table for operations of 1033 the Frame Relay Service Level Definitions MIB. It provides variables 1034 to control the parameters required to calculate the objects in the 1035 other tables. 1037 A row in this table MUST exist in order for a row to exist in any 1038 other table in this MIB module. 1040 5.2. frsldSmplCtrlTable 1042 This is an optional table to allow control of sampling of the data in 1043 the data table. 1045 5.3. frsldPvcDataTable 1047 This table contains the calculated data. It relies on configuration 1048 from the control table. 1050 5.4. frsldPvcSampleTable 1052 This table contains samples of the delivery and availability 1053 information from the data table as well as delay information 1054 calculated over the sample period. It relies on configuration from 1055 both the control table and the sample control table. 1057 5.5. frsldCapabilities 1059 This is a group of objects that define write capabilities of the 1060 read-create objects in the tables above. 1062 6. Persistence of Data 1064 The data in frsldPvcCtrlTable and frsldSmplCtrlTable SHOULD persist 1065 through power cycles. Note, however, that the symantics of readiness 1066 for the rows still applies. This means that it is possible for a row 1067 to be reprovisioned as notReady(3) if the underlying DLCI does not 1068 persist. The data collected in the other tables SHOULD NOT persist 1069 through power cycles in that the reference TimeStamp is no longer 1070 valid. 1072 7. Object Definitions 1074 FRSLD-MIB DEFINITIONS ::= BEGIN 1076 IMPORTS 1077 MODULE-IDENTITY, OBJECT-TYPE, 1078 Counter32, Gauge32, Integer32, 1079 Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI 1080 CounterBasedGauge64 FROM HCNUM-TC 1081 TEXTUAL-CONVENTION, RowStatus, 1082 TimeStamp FROM SNMPv2-TC 1083 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1084 ifIndex FROM IF-MIB; 1086 frsldMIB MODULE-IDENTITY 1087 LAST-UPDATED "200106181500Z" -- June 18, 2001 1088 ORGANIZATION "IETF Frame Relay Service MIB Working Group" 1089 CONTACT-INFO 1090 "IETF Frame Relay Service MIB (frnetmib) Working Group 1092 WG Charter: http://www.ietf.org/html.charters/ 1093 frnetmib-charter.html 1094 WG-email: frnetmib@sunroof.eng.sun.com 1095 Subscribe: frnetmib-request@sunroof.eng.sun.com 1096 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 1098 Chair: Andy Malis 1099 Lucent Technologies 1100 Email: amalis@lucent.com 1102 WG editor: Robert Steinberger 1103 Paradyne Networks and 1104 Fujitsu Network Communications 1105 Email: robert.steinberger@fnc.fujitsu.com 1107 Co-author: Orly Nicklass 1108 RAD Data Communications Ltd. 1109 EMail: Orly_n@rad.co.il" 1110 DESCRIPTION 1111 "The MIB module to describe generic objects for 1112 FRF.13 Frame Relay Service Level Definitions." 1113 REVISION "200106181500Z" 1114 DESCRIPTION 1115 "o Added text about persistence to RowStatus objects. 1116 o Added text to description of frsldPvcDataMissed- 1117 Polls. 1118 o Changed badValue to inconsistentValue in 1119 frsldMaxPvcCtrls and frsldMaxSmplCtrls." 1120 REVISION "200105011500Z" 1121 DESCRIPTION 1122 "o Added FrsldTxRP and FrsldRxRP TCs for reference 1123 points and changed frsldPvcCtrlTransmitRP and 1124 frsldPvcCtrlReceiveRP to use new TCs. 1125 o Added REFERENCE clauses. 1126 o Added frsldMaxPvcCtrls, frsldNumPvcCtrls, 1127 frsldMaxSmplCtrls and frsldNumSmplCtrls 1128 for memory control. 1129 o Made HC Data groups conditionally mandatory 1130 based on the speed of the network interface. 1131 o Updated description of the compliance objects. 1132 o Updated the description of the groups to show 1133 relationship." 1134 REVISION "200009191500Z" 1135 DESCRIPTION 1136 "o Removed frsldPvcCtrlDelayCnt. 1137 o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl- 1138 AvailBuckets, and frsldSmplCtrlAvailBucketsGranted. 1139 o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*. 1140 o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1141 and frsldPvcDataDelayAvg. 1142 o Changed frsldPvcDataSample* to frsldPvcSample*. 1143 o Changed frsldPvcDataSmpl* to frsldPvcSmpl*. 1144 o Added frsldPvcSmplUnavailableTime and frsldPvcSmpl- 1145 Unavailables. 1146 o Removed frsldPvcAvailSampleTable and all objects. 1147 o Removed frsldPvcCtrlDelayCnt from frsldPvcCtrlWrite- 1148 Caps. 1149 o Adjusted group definitions for frsldPvcDelayCtrlGroup, 1150 frsldPvc[Data]SampleCtrlGroup, frsldPvcReqDataGroup, 1151 frsldPvcDelayDataGroup, and frsldPvc[Avail]SampleAvail- 1152 Group to reflect above changes." 1153 REVISION "200006141500Z" 1154 DESCRIPTION 1155 "o Removed all uses of FrsldLocation by removing objects 1156 frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc 1157 o Removed FrsldRP TC and distributed source and destina- 1158 tion specific information into index for control table 1159 as frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP. 1160 o Added frsldPvcCtrlDelayCnt to control table. 1161 o Changed frsldPvcDataUnavailableTime from TimeStamp to 1162 TimeTicks. 1163 o Updated text of RowStatus objects 1164 o Added frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP 1165 as indices to ALL tables. 1166 o Added HC counters for all data delivery stats and 1167 samples. 1168 o Adjusted description of sample information for clarity. 1169 o Adjusted names of sample objects for consistency. 1170 o Added frsldRPCaps. 1171 o Changed location to mib-2 1172 o Reworked Group Definitions." 1174 REVISION "200002061500Z" 1175 DESCRIPTION 1176 "o Published as draft-ietf-frnetmib-frmrelay-service-00.txt 1177 o Added frsldCapabilities group to define the 1178 read/write capabilities 1179 o Changed location to experimental 104 1180 o Changed name of frsldTables to frsldObjects 1181 o Changed MAX-ACCESS of frsldPvcCtrlDelayType to 1182 read-create 1184 o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1185 and frsldPvcDataDelayAvg from the sample period" 1187 REVISION "199909031500Z" 1188 DESCRIPTION 1189 "o Added range to frsldPvcCtrlPacketFreq 1190 o Changed range of frsldPvcCtrlDelayTimeOut to match 1191 that of frsldPvcCtrlPacketFreq 1192 o Clarified what happens when frsldPvcCtrlPacketFreq 1193 is set to zero 1194 o Changed delay to count in microseconds instead of 1195 milliseconds 1196 o Created a new sample control table and moved sample 1197 specific information into it. 1198 o Changed the prefix of `frsldPvcCtrl' object name to 1199 `frsldSmplCtrl' 1200 o Added the sample control index to the indices of the 1201 sample tables 1202 o Changed all occasions of TimeTicks to TimeStamp 1203 o Added frsldPvcCtrlPurge to aid in control validity 1204 of information due to PVC status changes 1205 o Added frsldPvcCtrlDeleteOnPurge object 1206 o Added frsldPvcCtrlLastPurgeTime object 1207 o Added units clauses to all time related fields. 1208 o Reworded the `change in' syntax to be more explicit" 1209 ::= { mib-2 xxx } -- RFC editor - IANA assigns xxx 1211 -- 1212 -- Textual Conventions 1213 -- 1214 FrsldTxRP ::= TEXTUAL-CONVENTION 1215 STATUS current 1216 DESCRIPTION 1217 "The reference point a PVC uses for calculation 1218 of transmitter related statistics. 1220 The valid values for this type of object are as follows: 1221 - srcLocalRP(1) for the local source 1222 - ingTxLocalRP(2) for the local ingress queue input 1223 - tpTxLocalRP(3) for the local traffic policing 1224 - eqiTxLocalRP(4) for the local egress queue input 1225 - eqoTxLocalRP(5) for the local egress queue output 1226 - otherTxLocalRP(6) for any other local transmit point 1227 - srcRemoteRP(7) for the remote source 1228 - ingTxLocalRP(8) for the remote ingress queue input 1229 - tpTxLocalRP(9) for the remote traffic policing 1230 - eqiTxRemoteRP(10) for the remote egress queue input 1231 - eqoTxRemoteRP(11) for the remote egress queue output 1232 - otherTxRemoteRP(12) for any other remote xmit point" 1233 REFERENCE 1234 "FRF.13: Section 2.3" 1235 SYNTAX INTEGER { 1236 srcLocalRP(1), 1237 ingTxLocalRP(2), 1238 tpTxLocalRP(3), 1239 eqiTxLocalRP(4), 1240 eqoTxLocalRP(5), 1241 otherTxLocalRP(6), 1242 srcRemoteRP(7), 1243 ingTxRemoteRP(8), 1244 tpTxRemoteRP(9), 1245 eqiTxRemoteRP(10), 1246 eqoTxRemoteRP(11), 1247 otherTxRemoteRP(12) 1248 } 1250 FrsldRxRP ::= TEXTUAL-CONVENTION 1251 STATUS current 1252 DESCRIPTION 1253 "The reference point a PVC uses for calculation 1254 of receiver related statistics. 1256 The valid values for this object are as follows: 1257 - desLocalRP(1) for the local destination 1258 - ingRxLocalRP(2) for the local ingress queue input 1259 - tpRxLocalRP(3) for the local traffic policing 1260 - eqiRxLocalRP(4) for the local egress queue input 1261 - eqoRxLocalRP(5) for the local egress queue output 1262 - otherRxLocalRP(6) for any other local receive point 1263 - desRemoteRP(7) for the remote destination 1264 - ingRxRemoteRP(8) for the remote ingress input 1265 - tpRxRemoteRP(9) for the remote traffic policing 1266 - eqiRxRemoteRP(10) for the remote egress queue input 1267 - eqoRxRemoteRP(11) for the remote egress queue output 1268 - otherRxRemoteRP(12) for any other remote receive point" 1269 REFERENCE 1270 "FRF.13: Section 2.3" 1271 SYNTAX INTEGER { 1272 desLocalRP(1), 1273 ingRxLocalRP(2), 1274 tpRxLocalRP(3), 1275 eqiRxLocalRP(4), 1276 eqoRxLocalRP(5), 1277 otherRxLocalRP(6), 1278 desRemoteRP(7), 1279 ingRxRemoteRP(8), 1280 tpRxRemoteRP(9), 1281 eqiRxRemoteRP(10), 1282 eqoRxRemoteRP(11), 1283 otherRxRemoteRP(12) 1284 } 1286 -- 1287 -- Base Objects 1288 --- 1290 frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 } 1291 frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 } 1292 frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 } 1294 -- The Frame Relay Service Level Definitions PVC Control Table 1295 -- 1296 -- This table is used to define and display the parameters of 1297 -- service level definitions on individual PVCs. 1299 frsldPvcCtrlTable OBJECT-TYPE 1300 SYNTAX SEQUENCE OF FrsldPvcCtrlEntry 1301 MAX-ACCESS not-accessible 1302 STATUS current 1303 DESCRIPTION 1304 "The Frame Relay Service Level Definitions 1305 PVC control table." 1306 ::= { frsldObjects 1 } 1308 frsldPvcCtrlEntry OBJECT-TYPE 1309 SYNTAX FrsldPvcCtrlEntry 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "An entry in the Frame Relay Service Level 1314 Definitions PVC control table." 1315 INDEX { ifIndex, frsldPvcCtrlDlci, 1316 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1317 ::= { frsldPvcCtrlTable 1 } 1319 FrsldPvcCtrlEntry ::= 1320 SEQUENCE { 1321 -- 1322 -- Index Control Variables 1323 -- 1324 frsldPvcCtrlDlci Integer32, 1325 frsldPvcCtrlTransmitRP FrsldTxRP, 1326 frsldPvcCtrlReceiveRP FrsldRxRP, 1327 frsldPvcCtrlStatus RowStatus, 1328 -- 1329 -- Service Level Definitions Setup Variables 1330 -- 1331 frsldPvcCtrlPacketFreq Integer32, 1332 -- 1333 -- Delay Specific Setup Variables 1334 -- 1335 frsldPvcCtrlDelayFrSize Integer32, 1336 frsldPvcCtrlDelayType INTEGER, 1337 frsldPvcCtrlDelayTimeOut Integer32, 1338 -- 1339 -- Data Persistence Control Variables 1340 -- 1341 frsldPvcCtrlPurge Integer32, 1342 frsldPvcCtrlDeleteOnPurge INTEGER, 1343 frsldPvcCtrlLastPurgeTime TimeStamp 1344 } 1346 frsldPvcCtrlDlci OBJECT-TYPE 1347 SYNTAX Integer32 (16..4194303) 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "The value of this object is equal to the DLCI 1352 value for this PVC." 1353 ::= { frsldPvcCtrlEntry 1 } 1355 frsldPvcCtrlTransmitRP OBJECT-TYPE 1356 SYNTAX FrsldTxRP 1357 MAX-ACCESS not-accessible 1358 STATUS current 1359 DESCRIPTION 1360 "The reference point this PVC uses for calculation 1361 of transmitter related statistics. This object 1362 together with frsldPvcCtrlReceiveRP define the 1363 measurement domain." 1364 REFERENCE 1365 "FRF.13: Section 2.3" 1366 ::= { frsldPvcCtrlEntry 2 } 1368 frsldPvcCtrlReceiveRP OBJECT-TYPE 1369 SYNTAX FrsldRxRP 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "The reference point this PVC uses for calculation 1374 of receiver related statistics. This object 1375 together with frsldPvcCtrlTransmitRP define the 1376 measurement domain." 1377 ::= { frsldPvcCtrlEntry 3 } 1379 frsldPvcCtrlStatus OBJECT-TYPE 1380 SYNTAX RowStatus 1381 MAX-ACCESS read-create 1382 STATUS current 1383 DESCRIPTION 1384 "The status of the current row. This object is 1385 used to add, delete, and disable rows in this 1386 table. When the status changes to active(1) for the 1387 first time, a row will also be added to the data 1388 table below. This row SHOULD not be removed until 1389 the status is changed to deleted. 1391 When this object is set to destroy(6), all associated 1392 sample and data table rows will also be deleted. 1393 When this object is changed from active(1) to any 1394 other valid value, the defined purge behavior will 1395 affect the data and sample tables. 1397 The rows added to this table MUST have a valid 1398 ifIndex and an ifType related to frame relay. Further, 1399 the reference points referred to by frsldPvcCtrlTransmitRP 1400 and frsldPvcCtrlReceiveRP MUST be supported (see the 1401 frsldRPCaps object). 1403 If at any point the row is not in the active(1) state 1404 and the DLCI no longer exists, the state SHOULD 1405 report notReady(3). 1407 The data in this table SHOULD persist through power 1408 cycles. The symantics of readiness for the rows still 1409 applies. This means that it is possible for a row to be 1410 reprovisioned as notReady(3) if the underlying DLCI does 1411 not persist." 1412 ::= { frsldPvcCtrlEntry 4 } 1414 frsldPvcCtrlPacketFreq OBJECT-TYPE 1415 SYNTAX Integer32 (0..3600) 1416 UNITS "seconds" 1417 MAX-ACCESS read-create 1418 STATUS current 1419 DESCRIPTION 1420 "The frequency in seconds between initiation of 1421 specialized packets used to collect delay and / or 1422 delivery information as supported by the device. 1423 A value of zero indicates that no packets will 1424 be sent." 1425 DEFVAL { 60 } 1426 ::= { frsldPvcCtrlEntry 5 } 1428 frsldPvcCtrlDelayFrSize OBJECT-TYPE 1429 SYNTAX Integer32 (1..8188) 1430 UNITS "octets" 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "The size of the payload in the frame used for 1435 calculation of network delay." 1436 DEFVAL { 128 } 1437 ::= { frsldPvcCtrlEntry 6 } 1439 frsldPvcCtrlDelayType OBJECT-TYPE 1440 SYNTAX INTEGER { 1441 oneWay(1), 1442 roundTrip(2) 1443 } 1444 MAX-ACCESS read-create 1445 STATUS current 1446 DESCRIPTION 1447 "The type of delay measurement performed." 1448 REFERENCE 1449 "FRF.13: Section 3" 1450 ::= { frsldPvcCtrlEntry 7 } 1452 frsldPvcCtrlDelayTimeOut OBJECT-TYPE 1453 SYNTAX Integer32 (1..3600) 1454 UNITS "seconds" 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1458 "A delay frame will count as a missed poll if 1459 it is not updated in the time specified by 1460 frsldPvcCtrlDelayTimeOut." 1461 DEFVAL { 60 } 1462 ::= { frsldPvcCtrlEntry 8 } 1464 frsldPvcCtrlPurge OBJECT-TYPE 1465 SYNTAX Integer32 (0..172800) -- up to 48 hours 1466 UNITS "seconds" 1467 MAX-ACCESS read-create 1468 STATUS current 1469 DESCRIPTION 1470 "This object defines the amount of time the device 1471 will wait, after discovering that a DLCI does not exist, 1472 the DLCI was deleted or the value of frsldPvcCtrlStatus 1473 changes from active(1) to either notInService(2) or 1474 notReady(3), prior to automatically purging the history 1475 in the sample tables and resetting the data in the data 1476 tables to all zeroes. If frsldPvcCtrlStatus is manually 1477 set to destroy(6), this object does not apply." 1478 DEFVAL { 0 } 1479 ::= { frsldPvcCtrlEntry 9 } 1481 frsldPvcCtrlDeleteOnPurge OBJECT-TYPE 1482 SYNTAX INTEGER { 1483 none(1), 1484 sampleContols(2), 1485 all(3) 1486 } 1487 MAX-ACCESS read-create 1488 STATUS current 1489 DESCRIPTION 1490 "This object defines whether rows will 1491 automatically be deleted from the tables 1492 when the information is purged. 1494 - A value of none(1) indicates that no rows 1495 will deleted. The last known values will 1496 be preserved. 1497 - A value of sampleControls(2) indicates 1498 that all associated sample control rows 1499 will be deleted. 1500 - A value of all(3) indicates that all 1501 associated rows SHOULD be deleted." 1502 DEFVAL { all } 1503 ::= { frsldPvcCtrlEntry 10 } 1505 frsldPvcCtrlLastPurgeTime OBJECT-TYPE 1506 SYNTAX TimeStamp 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "This object returns the value of sysUpTime 1511 at the time the information was last purged. 1512 This value SHOULD be set to the sysUpTime 1513 upon setting frsldPvcCtrlStatus to active(1) 1514 for the first time. If frsldPvcCtrlStatus has 1515 never been active(1), this object SHOULD return 0." 1516 ::= { frsldPvcCtrlEntry 11 } 1518 -- The Frame Relay Service Level Definitions Sampling Control 1519 -- Table 1520 -- 1521 -- This table is used to define the sample control parameters 1522 -- of service level definitions on individual PVCs. 1524 frsldSmplCtrlTable OBJECT-TYPE 1525 SYNTAX SEQUENCE OF FrsldSmplCtrlEntry 1526 MAX-ACCESS not-accessible 1527 STATUS current 1528 DESCRIPTION 1529 "The Frame Relay Service Level Definitions 1530 sampling control table." 1531 ::= { frsldObjects 2 } 1533 frsldSmplCtrlEntry OBJECT-TYPE 1534 SYNTAX FrsldSmplCtrlEntry 1535 MAX-ACCESS not-accessible 1536 STATUS current 1537 DESCRIPTION 1538 "An entry in the Frame Relay Service Level 1539 Definitions sample control table." 1540 INDEX { ifIndex, frsldPvcCtrlDlci, 1541 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1542 frsldSmplCtrlIdx } 1543 ::= { frsldSmplCtrlTable 1 } 1545 FrsldSmplCtrlEntry ::= 1546 SEQUENCE { 1547 -- 1548 -- Index Control Variables 1549 -- 1550 frsldSmplCtrlIdx Integer32, 1551 frsldSmplCtrlStatus RowStatus, 1552 -- 1553 -- Collection Control Variables 1554 -- 1555 frsldSmplCtrlColPeriod Integer32, 1556 frsldSmplCtrlBuckets Integer32, 1557 frsldSmplCtrlBucketsGranted Integer32 1558 } 1560 frsldSmplCtrlIdx OBJECT-TYPE 1561 SYNTAX Integer32 (1..256) 1562 MAX-ACCESS not-accessible 1563 STATUS current 1564 DESCRIPTION 1565 "The unique index for this row in the 1566 sample control table." 1567 ::= { frsldSmplCtrlEntry 1 } 1569 frsldSmplCtrlStatus OBJECT-TYPE 1570 SYNTAX RowStatus 1571 MAX-ACCESS read-create 1572 STATUS current 1573 DESCRIPTION 1574 "The status of the current row. This object is 1575 used to add, delete, and disable rows in this 1576 table. This row SHOULD NOT be removed until the 1577 status is changed to destroy(6). When the status 1578 changes to active(1), the collection in the sample 1579 tables below will be activated. 1581 The rows added to this table MUST have a valid 1582 ifIndex, an ifType related to frame relay, 1583 frsldPvcCtrlDlci MUST exist for the specified 1584 ifIndex and frsldPvcCtrlStatus MUST have a 1585 value of active(1). 1587 The value of frsldPvcCtrlStatus MUST be active(1) 1588 to transition this object to active(1). If 1589 the value of frsldPvcCtrlStatus becomes anything 1590 other than active(1) when the state of this object 1591 is not active(1), this object SHOULD be set to 1592 notReady(3). 1594 The data in this table SHOULD persist through power 1595 cycles. The symantics of readiness for the rows still 1596 applies. This means that it is possible for a row to be 1597 reprovisioned as notReady(3) if the underlying DLCI does 1598 not persist." 1599 ::= { frsldSmplCtrlEntry 2 } 1601 frsldSmplCtrlColPeriod OBJECT-TYPE 1602 SYNTAX Integer32 (1..2147483647) 1603 UNITS "seconds" 1604 MAX-ACCESS read-create 1605 STATUS current 1606 DESCRIPTION 1607 "The amount of time in seconds that defines a 1608 period of collection for the statistics. 1609 At the end of each period, the statistics will be 1610 sampled and a row is added to the sample table." 1611 ::= { frsldSmplCtrlEntry 3 } 1613 frsldSmplCtrlBuckets OBJECT-TYPE 1614 SYNTAX Integer32 (1..65535) 1615 MAX-ACCESS read-create 1616 STATUS current 1617 DESCRIPTION 1618 "The number of discrete buckets over which the 1619 data statistics are sampled. 1621 When this object is created or modified, the device 1622 SHOULD attempt to set the frsldSmplCtrlBuckets- 1623 Granted to a value as close as is possible 1624 depending upon the implementation and the available 1625 resources." 1626 DEFVAL { 60 } 1627 ::= { frsldSmplCtrlEntry 4 } 1629 frsldSmplCtrlBucketsGranted OBJECT-TYPE 1630 SYNTAX Integer32 (0..65535) 1631 MAX-ACCESS read-only 1632 STATUS current 1633 DESCRIPTION 1634 "The number of discrete buckets granted. This 1635 object will return 0 until frsldSmplCtrlStatus is 1636 set to active(1). At that time the buckets will be 1637 allocated depending upon implementation and 1638 available resources." 1639 ::= { frsldSmplCtrlEntry 5 } 1641 -- The Frame Relay Service Level Definitions PVC Data Table 1642 -- 1643 -- This table contains the accumulated values of 1644 -- the collected data. This table is the table that should 1645 -- be referenced by external polling mechanisms if time 1646 -- based polling be desired. 1648 frsldPvcDataTable OBJECT-TYPE 1649 SYNTAX SEQUENCE OF FrsldPvcDataEntry 1650 MAX-ACCESS not-accessible 1651 STATUS current 1652 DESCRIPTION 1653 "The Frame Relay Service Level Definitions 1654 data table. 1656 This table contains accumulated values of the 1657 collected data. It is the table that should be 1658 referenced by external polling mechanisms if 1659 time based polling be desired." 1660 ::= { frsldObjects 3 } 1662 frsldPvcDataEntry OBJECT-TYPE 1663 SYNTAX FrsldPvcDataEntry 1664 MAX-ACCESS not-accessible 1665 STATUS current 1666 DESCRIPTION 1667 "An entry in the Frame Relay Service Level 1668 Definitions data table." 1669 INDEX { ifIndex, frsldPvcCtrlDlci, 1670 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1671 ::= { frsldPvcDataTable 1 } 1673 FrsldPvcDataEntry ::= 1674 SEQUENCE { 1675 frsldPvcDataMissedPolls Counter32, 1676 frsldPvcDataFrDeliveredC Counter32, 1677 frsldPvcDataFrDeliveredE Counter32, 1678 frsldPvcDataFrOfferedC Counter32, 1679 frsldPvcDataFrOfferedE Counter32, 1680 frsldPvcDataDataDeliveredC Counter32, 1681 frsldPvcDataDataDeliveredE Counter32, 1682 frsldPvcDataDataOfferedC Counter32, 1683 frsldPvcDataDataOfferedE Counter32, 1684 frsldPvcDataHCFrDeliveredC Counter64, 1685 frsldPvcDataHCFrDeliveredE Counter64, 1686 frsldPvcDataHCFrOfferedC Counter64, 1687 frsldPvcDataHCFrOfferedE Counter64, 1688 frsldPvcDataHCDataDeliveredC Counter64, 1689 frsldPvcDataHCDataDeliveredE Counter64, 1690 frsldPvcDataHCDataOfferedC Counter64, 1691 frsldPvcDataHCDataOfferedE Counter64, 1692 frsldPvcDataUnavailableTime TimeTicks, 1693 frsldPvcDataUnavailables Counter32 1694 } 1696 frsldPvcDataMissedPolls OBJECT-TYPE 1697 SYNTAX Counter32 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "The total number of polls that have been determined 1702 to be missed. These polls are typically associated 1703 with the calculation of delay but may also be 1704 used for the calculation of other statistics. If an 1705 anticipated poll is not received in a reasonable 1706 amount of time, it should be counted as missed. 1707 The value used to determine the reasonable amount 1708 of time is contained in frsldPvcCtrlDelayTimeOut." 1709 ::= { frsldPvcDataEntry 1 } 1711 frsldPvcDataFrDeliveredC OBJECT-TYPE 1712 SYNTAX Counter32 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "The number of frames that were received at 1717 frsldPvcCtrlReceiveRP and determined to have been 1718 sent within CIR." 1719 REFERENCE 1720 "FRF.13: Section 4.1 (FramesDeliveredc)" 1721 ::= { frsldPvcDataEntry 2 } 1723 frsldPvcDataFrDeliveredE OBJECT-TYPE 1724 SYNTAX Counter32 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "The number of frames that were received at 1729 frsldPvcCtrlReceiveRP and determined to have been 1730 sent in excess of the CIR." 1731 REFERENCE 1732 "FRF.13: Section 4.1 (FramesDeliverede)" 1733 ::= { frsldPvcDataEntry 3 } 1735 frsldPvcDataFrOfferedC OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The number of frames that were offered through 1741 frsldPvcCtrlTransmitRP within CIR." 1742 REFERENCE 1743 "FRF.13: Section 4.1 (FramesOfferedc)" 1744 ::= { frsldPvcDataEntry 4 } 1746 frsldPvcDataFrOfferedE OBJECT-TYPE 1747 SYNTAX Counter32 1748 MAX-ACCESS read-only 1749 STATUS current 1750 DESCRIPTION 1751 "The number of frames that were offered through 1752 frsldPvcCtrlTransmitRP in excess of the CIR." 1753 REFERENCE 1754 "FRF.13: Section 4.1 (FramesOfferede)" 1755 ::= { frsldPvcDataEntry 5 } 1757 frsldPvcDataDataDeliveredC OBJECT-TYPE 1758 SYNTAX Counter32 1759 MAX-ACCESS read-only 1760 STATUS current 1761 DESCRIPTION 1762 "The number of octets that were received at 1763 frsldPvcCtrlReceiveRP and determined to have been 1764 sent within CIR." 1765 REFERENCE 1766 "FRF.13: Section 5.1 (DataDeliveredc)" 1767 ::= { frsldPvcDataEntry 6 } 1769 frsldPvcDataDataDeliveredE OBJECT-TYPE 1770 SYNTAX Counter32 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "The number of octets that were received at 1775 frsldPvcCtrlReceiveRP and determined to have been 1776 sent in excess of the CIR." 1777 REFERENCE 1778 "FRF.13: Section 5.1 (DataDeliverede)" 1779 ::= { frsldPvcDataEntry 7 } 1781 frsldPvcDataDataOfferedC OBJECT-TYPE 1782 SYNTAX Counter32 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "The number of octets that were offered through 1787 frsldPvcCtrlTransmitRP within CIR." 1788 REFERENCE 1789 "FRF.13: Section 5.1 (DataOfferedc)" 1790 ::= { frsldPvcDataEntry 8 } 1792 frsldPvcDataDataOfferedE OBJECT-TYPE 1793 SYNTAX Counter32 1794 MAX-ACCESS read-only 1795 STATUS current 1796 DESCRIPTION 1797 "The number of octets that were offered through 1798 frsldPvcCtrlTransmitRP in excess of the CIR." 1799 REFERENCE 1800 "FRF.13: Section 5.1 (DataOfferede)" 1801 ::= { frsldPvcDataEntry 9 } 1803 frsldPvcDataHCFrDeliveredC OBJECT-TYPE 1804 SYNTAX Counter64 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "The number of frames that were received at 1809 frsldPvcCtrlReceiveRP and determined to have been 1810 sent within CIR. This object is a 64-bit version 1811 of frsldPvcDataFrDeliveredC." 1812 REFERENCE 1813 "FRF.13: Section 4.1 (FramesDeliveredc)" 1814 ::= { frsldPvcDataEntry 10 } 1816 frsldPvcDataHCFrDeliveredE OBJECT-TYPE 1817 SYNTAX Counter64 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "The number of frames that were received at 1822 frsldPvcCtrlReceiveRP and determined to have been 1823 sent in excess of the CIR. This object is a 64-bit 1824 version of frsldPvcDataFrDeliveredE." 1825 REFERENCE 1826 "FRF.13: Section 4.1 (FramesDeliverede)" 1827 ::= { frsldPvcDataEntry 11 } 1829 frsldPvcDataHCFrOfferedC OBJECT-TYPE 1830 SYNTAX Counter64 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "The number of frames that were offered through 1835 frsldPvcCtrlTransmitRP within CIR. This object is 1836 a 64-bit version of frsldPvcDataFrOfferedC." 1837 REFERENCE 1838 "FRF.13: Section 4.1 (FramesOfferedc)" 1839 ::= { frsldPvcDataEntry 12 } 1841 frsldPvcDataHCFrOfferedE OBJECT-TYPE 1842 SYNTAX Counter64 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The number of frames that were offered through 1847 frsldPvcCtrlTransmitRP in excess of the CIR. This 1848 object is a 64-bit version of frsldPvcDataFrOfferedE." 1849 REFERENCE 1850 "FRF.13: Section 4.1 (FramesOfferede)" 1851 ::= { frsldPvcDataEntry 13 } 1853 frsldPvcDataHCDataDeliveredC OBJECT-TYPE 1854 SYNTAX Counter64 1855 MAX-ACCESS read-only 1856 STATUS current 1857 DESCRIPTION 1858 "The number of octets that were received at 1859 frsldPvcCtrlReceiveRP and determined to have been 1860 sent within CIR. This object is a 64-bit version of 1861 frsldPvcDataDataDeliveredC." 1862 REFERENCE 1863 "FRF.13: Section 5.1 (DataDeliveredc)" 1864 ::= { frsldPvcDataEntry 14 } 1866 frsldPvcDataHCDataDeliveredE OBJECT-TYPE 1867 SYNTAX Counter64 1868 MAX-ACCESS read-only 1869 STATUS current 1870 DESCRIPTION 1871 "The number of octets that were received at 1872 frsldPvcCtrlReceiveRP and determined to have been 1873 sent in excess of the CIR. This object is a 64-bit 1874 version of frsldPvcDataDataDeliveredE." 1875 REFERENCE 1876 "FRF.13: Section 5.1 (DataDeliverede)" 1877 ::= { frsldPvcDataEntry 15 } 1879 frsldPvcDataHCDataOfferedC OBJECT-TYPE 1880 SYNTAX Counter64 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "The number of octets that were offered through 1885 frsldPvcCtrlTransmitRP within CIR. This object is 1886 a 64-bit version of frsldPvcDataDataOfferedC." 1887 REFERENCE 1888 "FRF.13: Section 5.1 (DataOfferedc)" 1889 ::= { frsldPvcDataEntry 16 } 1891 frsldPvcDataHCDataOfferedE OBJECT-TYPE 1892 SYNTAX Counter64 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "The number of octets that were offered through 1897 frsldPvcCtrlTransmitRP in excess of the CIR. 1898 This object is a 64-bit version of 1899 frsldPvcDataDataOfferedE." 1900 REFERENCE 1901 "FRF.13: Section 5.1 (DataOfferede)" 1902 ::= { frsldPvcDataEntry 17 } 1904 frsldPvcDataUnavailableTime OBJECT-TYPE 1905 SYNTAX TimeTicks 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The amount of time this PVC was declared unavailable 1910 for any reason since this row was created." 1911 REFERENCE 1912 "FRF.13: Section 6.1 (OutageTime)" 1913 ::= { frsldPvcDataEntry 18 } 1915 frsldPvcDataUnavailables OBJECT-TYPE 1916 SYNTAX Counter32 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The number of times this PVC was declared unavailable 1921 for any reason since this row was created." 1922 REFERENCE 1923 "FRF.13: Section 6.1 (OutageCount)" 1924 ::= { frsldPvcDataEntry 19 } 1926 -- The Frame Relay Service Level Definitions PVC Sample Table 1927 -- 1928 -- This table contains the sampled delay, delivery and 1929 -- availability information. 1931 frsldPvcSampleTable OBJECT-TYPE 1932 SYNTAX SEQUENCE OF FrsldPvcSampleEntry 1933 MAX-ACCESS not-accessible 1934 STATUS current 1935 DESCRIPTION 1936 "The Frame Relay Service Level Definitions 1937 sample table." 1938 ::= { frsldObjects 4 } 1940 frsldPvcSampleEntry OBJECT-TYPE 1941 SYNTAX FrsldPvcSampleEntry 1942 MAX-ACCESS not-accessible 1943 STATUS current 1944 DESCRIPTION 1945 "An entry in the Frame Relay Service Level 1946 Definitions data sample table." 1947 INDEX { ifIndex, frsldPvcCtrlDlci, 1948 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1949 frsldSmplCtrlIdx, frsldPvcSmplIdx } 1950 ::= { frsldPvcSampleTable 1 } 1952 FrsldPvcSampleEntry ::= 1953 SEQUENCE { 1954 frsldPvcSmplIdx Integer32, 1955 frsldPvcSmplDelayMin Gauge32, 1956 frsldPvcSmplDelayMax Gauge32, 1957 frsldPvcSmplDelayAvg Gauge32, 1958 frsldPvcSmplMissedPolls Gauge32, 1959 frsldPvcSmplFrDeliveredC Gauge32, 1960 frsldPvcSmplFrDeliveredE Gauge32, 1961 frsldPvcSmplFrOfferedC Gauge32, 1962 frsldPvcSmplFrOfferedE Gauge32, 1963 frsldPvcSmplDataDeliveredC Gauge32, 1964 frsldPvcSmplDataDeliveredE Gauge32, 1965 frsldPvcSmplDataOfferedC Gauge32, 1966 frsldPvcSmplDataOfferedE Gauge32, 1967 frsldPvcSmplHCFrDeliveredC CounterBasedGauge64, 1968 frsldPvcSmplHCFrDeliveredE CounterBasedGauge64, 1969 frsldPvcSmplHCFrOfferedC CounterBasedGauge64, 1970 frsldPvcSmplHCFrOfferedE CounterBasedGauge64, 1971 frsldPvcSmplHCDataDeliveredC CounterBasedGauge64, 1972 frsldPvcSmplHCDataDeliveredE CounterBasedGauge64, 1973 frsldPvcSmplHCDataOfferedC CounterBasedGauge64, 1974 frsldPvcSmplHCDataOfferedE CounterBasedGauge64, 1975 frsldPvcSmplUnavailableTime TimeTicks, 1976 frsldPvcSmplUnavailables Gauge32, 1977 frsldPvcSmplStartTime TimeStamp, 1978 frsldPvcSmplEndTime TimeStamp 1979 } 1981 frsldPvcSmplIdx OBJECT-TYPE 1982 SYNTAX Integer32 (1..2147483647) 1983 MAX-ACCESS not-accessible 1984 STATUS current 1985 DESCRIPTION 1986 "The bucket index of the current sample. This 1987 increments once for each new bucket in the 1988 table." 1989 ::= { frsldPvcSampleEntry 1 } 1991 frsldPvcSmplDelayMin OBJECT-TYPE 1992 SYNTAX Gauge32 1993 UNITS "microseconds" 1994 MAX-ACCESS read-only 1995 STATUS current 1996 DESCRIPTION 1997 "The minimum delay reported in microseconds measured 1998 for any information packet that arrived during this 1999 interval. 2001 A value of zero means that no data is available." 2002 REFERENCE 2003 "FRF.13: Section 3.1 (FTD)" 2004 ::= { frsldPvcSampleEntry 2 } 2006 frsldPvcSmplDelayMax OBJECT-TYPE 2007 SYNTAX Gauge32 2008 UNITS "microseconds" 2009 MAX-ACCESS read-only 2010 STATUS current 2011 DESCRIPTION 2012 "The largest delay reported in microseconds measured 2013 for any information packet that arrived during this 2014 interval. 2016 A value of zero means that no data is available." 2017 REFERENCE 2018 "FRF.13: Section 3.1 (FTD)" 2019 ::= { frsldPvcSampleEntry 3 } 2021 frsldPvcSmplDelayAvg OBJECT-TYPE 2022 SYNTAX Gauge32 2023 UNITS "microseconds" 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "The average delay reported in microseconds measured 2028 for all delay packets that arrived during this 2029 interval. 2031 A value of zero means that no data is available." 2032 REFERENCE 2033 "FRF.13: Section 3.1 (FTD)" 2034 ::= { frsldPvcSampleEntry 4 } 2036 frsldPvcSmplMissedPolls OBJECT-TYPE 2037 SYNTAX Gauge32 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "The total number of polls that were missed during 2042 this interval." 2043 ::= { frsldPvcSampleEntry 5 } 2045 frsldPvcSmplFrDeliveredC OBJECT-TYPE 2046 SYNTAX Gauge32 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "The number of frames that were received at 2051 frsldPvcCtrlReceiveRP and determined to have been 2052 sent within CIR during this interval." 2053 REFERENCE 2054 "FRF.13: Section 4.1 (FramesDeliveredc)" 2055 ::= { frsldPvcSampleEntry 6 } 2057 frsldPvcSmplFrDeliveredE OBJECT-TYPE 2058 SYNTAX Gauge32 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "The number of frames that were received at 2063 frsldPvcCtrlReceiveRP and determined to have been 2064 sent in excess of the CIR during this interval." 2065 REFERENCE 2066 "FRF.13: Section 4.1 (FramesDeliverede))" 2067 ::= { frsldPvcSampleEntry 7 } 2069 frsldPvcSmplFrOfferedC OBJECT-TYPE 2070 SYNTAX Gauge32 2071 MAX-ACCESS read-only 2072 STATUS current 2073 DESCRIPTION 2074 "The number of frames that were offered through 2075 frsldPvcCtrlTransmitRP within CIR during this 2076 interval." 2077 REFERENCE 2078 "FRF.13: Section 4.1 (FramesOfferedc)" 2079 ::= { frsldPvcSampleEntry 8 } 2081 frsldPvcSmplFrOfferedE OBJECT-TYPE 2082 SYNTAX Gauge32 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "The number of frames that were offered through 2087 frsldPvcCtrlTransmitRP in excess of the CIR 2088 during this interval." 2089 REFERENCE 2090 "FRF.13: Section 4.1 (FramesOfferede)" 2091 ::= { frsldPvcSampleEntry 9 } 2093 frsldPvcSmplDataDeliveredC OBJECT-TYPE 2094 SYNTAX Gauge32 2095 MAX-ACCESS read-only 2096 STATUS current 2097 DESCRIPTION 2098 "The number of octets that were received at 2099 frsldPvcCtrlReceiveRP and determined to have been 2100 sent within CIR during this interval." 2101 REFERENCE 2102 "FRF.13: Section 5.1 (DataDeliveredc)" 2103 ::= { frsldPvcSampleEntry 10 } 2105 frsldPvcSmplDataDeliveredE OBJECT-TYPE 2106 SYNTAX Gauge32 2107 MAX-ACCESS read-only 2108 STATUS current 2109 DESCRIPTION 2110 "The number of octets that were received at 2111 frsldPvcCtrlDeliveredRP and determined to have been 2112 sent in excess of the CIR during this interval." 2113 REFERENCE 2114 "FRF.13: Section 5.1 (DataDeliverede)" 2115 ::= { frsldPvcSampleEntry 11 } 2117 frsldPvcSmplDataOfferedC OBJECT-TYPE 2118 SYNTAX Gauge32 2119 MAX-ACCESS read-only 2120 STATUS current 2121 DESCRIPTION 2122 "The number of octets that were offered through 2123 frsldPvcCtrlTransmitRP within CIR during this 2124 interval." 2125 REFERENCE 2126 "FRF.13: Section 5.1 (DataOfferedc)" 2127 ::= { frsldPvcSampleEntry 12 } 2129 frsldPvcSmplDataOfferedE OBJECT-TYPE 2130 SYNTAX Gauge32 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "The number of octets that were offered through 2135 frsldPvcCtrlTransmitRP in excess of the CIR 2136 during this interval." 2137 REFERENCE 2138 "FRF.13: Section 5.1 (DataOfferede)" 2139 ::= { frsldPvcSampleEntry 13 } 2141 frsldPvcSmplHCFrDeliveredC OBJECT-TYPE 2142 SYNTAX CounterBasedGauge64 2143 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "The number of frames that were received at 2147 frsldPvcCtrlReceiveRP and determined to have been 2148 sent within CIR during this interval. This object 2149 is a 64-bit version of frsldPvcSmplFrDeliveredC." 2150 REFERENCE 2151 "FRF.13: Section 4.1 (FramesDeliveredc)" 2152 ::= { frsldPvcSampleEntry 14 } 2154 frsldPvcSmplHCFrDeliveredE OBJECT-TYPE 2155 SYNTAX CounterBasedGauge64 2156 MAX-ACCESS read-only 2157 STATUS current 2158 DESCRIPTION 2159 "The number of frames that were received at 2160 frsldPvcCtrlReceiveRP and determined to have been 2161 sent in excess of the CIR during this interval. 2162 This object is a 64-bit version of frsldPvcSmpl- 2163 FrDeliveredE." 2164 REFERENCE 2165 "FRF.13: Section 4.1 (FramesDeliverede)" 2166 ::= { frsldPvcSampleEntry 15 } 2168 frsldPvcSmplHCFrOfferedC OBJECT-TYPE 2169 SYNTAX CounterBasedGauge64 2170 MAX-ACCESS read-only 2171 STATUS current 2172 DESCRIPTION 2173 "The number of frames that were offered through 2174 frsldPvcCtrlTransmitRP within CIR during this 2175 interval. This object is a 64-bit version of 2176 frsldPvcSmplFrOfferedC." 2177 REFERENCE 2178 "FRF.13: Section 4.1 (FramesOfferedc)" 2179 ::= { frsldPvcSampleEntry 16 } 2181 frsldPvcSmplHCFrOfferedE OBJECT-TYPE 2182 SYNTAX CounterBasedGauge64 2183 MAX-ACCESS read-only 2184 STATUS current 2185 DESCRIPTION 2186 "The number of frames that were offered through 2187 frsldPvcCtrlTransmitRP in excess of the CIR 2188 during this interval. This object is a 64-bit 2189 version of frsldPvcSmplFrOfferedE." 2190 REFERENCE 2191 "FRF.13: Section 4.1 (FramesOfferede)" 2192 ::= { frsldPvcSampleEntry 17 } 2194 frsldPvcSmplHCDataDeliveredC OBJECT-TYPE 2195 SYNTAX CounterBasedGauge64 2196 MAX-ACCESS read-only 2197 STATUS current 2198 DESCRIPTION 2199 "The number of octets that were received at 2200 frsldPvcCtrlReceiveRP and determined to have been 2201 sent within CIR during this interval. This value 2202 is a 64-bit version of frsldPvcSmplDataDeliveredC." 2203 REFERENCE 2204 "FRF.13: Section 5.1 (DataDeliveredc)" 2205 ::= { frsldPvcSampleEntry 18 } 2207 frsldPvcSmplHCDataDeliveredE OBJECT-TYPE 2208 SYNTAX CounterBasedGauge64 2209 MAX-ACCESS read-only 2210 STATUS current 2211 DESCRIPTION 2212 "The number of octets that were received at 2213 frsldPvcCtrlReceiveRP and determined to have been 2214 sent in excess of the CIR during this interval. This 2215 value is a 64-bit version of frsldPvcSmplData- 2216 DeliveredE." 2217 REFERENCE 2218 "FRF.13: Section 5.1 (DataDeliverede)" 2219 ::= { frsldPvcSampleEntry 19 } 2221 frsldPvcSmplHCDataOfferedC OBJECT-TYPE 2222 SYNTAX CounterBasedGauge64 2223 MAX-ACCESS read-only 2224 STATUS current 2225 DESCRIPTION 2226 "The number of octets that were offered through 2227 frsldPvcCtrlTransmitRP within CIR during this 2228 interval. This value is a 64-bit version of 2229 frsldPvcSmplDataOfferedC." 2230 REFERENCE 2231 "FRF.13: Section 5.1 (DataOfferedc)" 2232 ::= { frsldPvcSampleEntry 20 } 2234 frsldPvcSmplHCDataOfferedE OBJECT-TYPE 2235 SYNTAX CounterBasedGauge64 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "The number of octets that were offered through 2240 frsldPvcCtrlTransmitRP in excess of the CIR 2241 during this interval. This object is a 64-bit 2242 version of frsldPvcSmplDataOfferedE." 2243 REFERENCE 2244 "FRF.13: Section 5.1 (DataOfferede)" 2245 ::= { frsldPvcSampleEntry 21 } 2247 frsldPvcSmplUnavailableTime OBJECT-TYPE 2248 SYNTAX TimeTicks 2249 MAX-ACCESS read-only 2250 STATUS current 2251 DESCRIPTION 2252 "The amount of time this PVC was declared 2253 unavailable for any reason during this interval." 2254 REFERENCE 2255 "FRF.13: Section 6.1 (OutageTime)" 2256 ::= { frsldPvcSampleEntry 22 } 2258 frsldPvcSmplUnavailables OBJECT-TYPE 2259 SYNTAX Gauge32 2260 MAX-ACCESS read-only 2261 STATUS current 2262 DESCRIPTION 2263 "The number of times this PVC was declared 2264 unavailable for any reason during this interval." 2265 REFERENCE 2266 "FRF.13: Section 6.1 (OutageCount)" 2267 ::= { frsldPvcSampleEntry 23 } 2269 frsldPvcSmplStartTime OBJECT-TYPE 2270 SYNTAX TimeStamp 2271 MAX-ACCESS read-only 2272 STATUS current 2273 DESCRIPTION 2274 "The value of sysUpTime when this sample interval 2275 started." 2276 ::= { frsldPvcSampleEntry 24 } 2278 frsldPvcSmplEndTime OBJECT-TYPE 2279 SYNTAX TimeStamp 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "The value of sysUpTime when this sample interval 2284 ended. No data will be reported and the row will 2285 not appear in the table until the sample has 2286 been collected." 2287 ::= { frsldPvcSampleEntry 25 } 2289 -- Capabilities Group 2290 -- This group provides capabilities objects for the tables 2291 -- that control configuration. 2293 frsldPvcCtrlWriteCaps OBJECT-TYPE 2294 SYNTAX BITS { 2295 frsldPvcCtrlStatus(0), 2296 frsldPvcCtrlPacketFreq(1), 2297 frsldPvcCtrlDelayFrSize(2), 2298 frsldPvcCtrlDelayType(3), 2299 frsldPvcCtrlDelayTimeOut(4), 2300 frsldPvcCtrlPurge(5), 2301 frsldPvcCtrlDeleteOnPurge(6) 2302 } 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "This object specifies the write capabilities 2307 for the read-create objects of the PVC Control 2308 table. If the corresponding bit is enabled (1), 2309 the agent supports writes to that object." 2310 ::= { frsldCapabilities 1 } 2312 frsldSmplCtrlWriteCaps OBJECT-TYPE 2313 SYNTAX BITS { 2314 frsldSmplCtrlStatus(0), 2315 frsldSmplCtrlBuckets(1) 2316 } 2317 MAX-ACCESS read-only 2318 STATUS current 2319 DESCRIPTION 2320 "This object specifies the write capabilities 2321 for the read-create objects of the Sample Control 2322 table. If the corresponding bit is enabled (1), 2323 the agent supports writes to that object." 2324 ::= { frsldCapabilities 2 } 2326 frsldRPCaps OBJECT-TYPE 2327 SYNTAX BITS { 2328 srcLocalRP(0), 2329 ingTxLocalRP(1), 2330 tpTxLocalRP(2), 2331 eqiTxLocalRP(3), 2332 eqoTxLocalRP(4), 2333 otherTxLocalRP(5), 2334 srcRemoteRP(6), 2335 ingTxRemoteRP(7), 2336 tpTxRemoteRP(8), 2337 eqiTxRemoteRP(9), 2338 eqoTxRemoteRP(10), 2339 otherTxRemoteRP(11), 2340 desLocalRP(12), 2341 ingRxLocalRP(13), 2342 tpRxLocalRP(14), 2343 eqiRxLocalRP(15), 2344 eqoRxLocalRP(16), 2345 otherRxLocalRP(17), 2346 desRemoteRP(18), 2347 ingRxRemoteRP(19), 2348 tpRxRemoteRP(20), 2349 eqiRxRemoteRP(21), 2350 eqoRxRemoteRP(22), 2351 otherRxRemoteRP(23) 2352 } 2353 MAX-ACCESS read-only 2354 STATUS current 2355 DESCRIPTION 2356 "This object specifies the reference points that 2357 the agent supports. This object allows the management 2358 application to discover which rows can be created on 2359 a specific device." 2360 ::= { frsldCapabilities 3 } 2362 frsldMaxPvcCtrls OBJECT-TYPE 2363 SYNTAX Integer32 (0..2147483647) 2364 MAX-ACCESS read-write 2365 STATUS current 2366 DESCRIPTION 2367 "The maximum number of control rows that can be created 2368 in frsldPvcCtrlTable. Sets to this object lower than 2369 the current value of frsldNumPvcCtrls should result in 2370 inconsistentValue." 2371 ::= { frsldCapabilities 4 } 2373 frsldNumPvcCtrls OBJECT-TYPE 2374 SYNTAX Gauge32 2375 MAX-ACCESS read-only 2376 STATUS current 2377 DESCRIPTION 2378 "The current number of rows in frsldPvcCtrlTable." 2379 ::= { frsldCapabilities 5 } 2381 frsldMaxSmplCtrls OBJECT-TYPE 2382 SYNTAX Integer32 (0..2147483647) 2383 MAX-ACCESS read-write 2384 STATUS current 2385 DESCRIPTION 2386 "The maximum number of control rows that can be created 2387 in frsldSmplCtrlTable. Sets to this object lower than 2388 the current value of frsldNumSmplCtrls should result in 2389 inconsistentValue." 2390 ::= { frsldCapabilities 6 } 2392 frsldNumSmplCtrls OBJECT-TYPE 2393 SYNTAX Gauge32 2394 MAX-ACCESS read-only 2395 STATUS current 2396 DESCRIPTION 2397 "The current number of rows in frsldSmplCtrlTable." 2398 ::= { frsldCapabilities 7 } 2400 -- Conformance Information 2402 frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } 2403 frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } 2405 -- 2406 -- Compliance Statements 2407 -- 2409 frsldCompliance MODULE-COMPLIANCE 2410 STATUS current 2411 DESCRIPTION 2412 "The compliance statement for SNMPv2 entities 2413 which support with Frame Relay Service Level 2414 Definitions. This group defines the minimum 2415 level of support required for compliance." 2416 MODULE -- this module 2417 MANDATORY-GROUPS { frsldPvcReqCtrlGroup, 2418 frsldPvcReqDataGroup, 2419 frsldCapabilitiesGroup} 2421 GROUP frsldPvcHCFrameDataGroup 2422 DESCRIPTION 2423 "This group is mandatory only for those network 2424 interfaces with corresponding instance of ifSpeed 2425 greater than 650,000,000 bits/second." 2427 GROUP frsldPvcHCOctetDataGroup 2428 DESCRIPTION 2429 "This group is mandatory only for those network 2430 interfaces with corresponding instance of ifSpeed 2431 greater than 650,000,000 bits/second." 2433 OBJECT frsldPvcCtrlStatus 2434 SYNTAX INTEGER { active(1) } -- subset of RowStatus 2435 MIN-ACCESS read-only 2436 DESCRIPTION 2437 "Row creation can be done outside of the scope of 2438 the SNMP protocol. If this object is implemented 2439 with max-access of read-only, then the only value 2440 that MUST be returned is active(1) and 2441 frsldPvcCtrlWriteCaps MUST return 0 for the 2442 frsldPvcCtrlStatus(0) bit." 2444 OBJECT frsldPvcCtrlPurge 2445 MIN-ACCESS read-only 2446 DESCRIPTION 2447 "Write access is not required. If this object is 2448 implemented with a max-access of read-only, then 2449 the frsldPvcCtrlPurge(5) bit must return 0." 2451 OBJECT frsldPvcCtrlDeleteOnPurge 2452 MIN-ACCESS read-only 2453 DESCRIPTION 2454 "Write access is not required. If this object is 2455 implemented with a max-access of read-only, then 2456 the frsldPvcCtrlDeleteOnPurge(6) bit must return 2457 0." 2459 OBJECT frsldMaxPvcCtrls 2460 MIN-ACCESS read-only 2461 DESCRIPTION 2462 "Write access is not required if the device either 2463 dynamically allocates memory or statically allocates 2464 a fixed number of entries. In the case of static 2465 allocation, the device should always report the 2466 correct maximum number of controls. In the case 2467 of dynamic allocation, the device SHOULD always 2468 report a number greater than frsldNumPvcCtrls 2469 when allocation is possible and a number equal to 2470 frsldNumPvcCtrls when allocation is not possible." 2472 OBJECT frsldMaxSmplCtrls 2473 MIN-ACCESS read-only 2474 DESCRIPTION 2475 "Write access is not required if the device either 2476 dynamically allocates memory or statically allocates 2477 a fixed number of entries. In the case of static 2478 allocation, the device should always report the 2479 correct maximum number of controls. In the case 2480 of dynamic allocation, the device SHOULD always 2481 report a number greater than frsldNumSmplCtrls 2482 when allocation is possible and a number equal to 2483 frsldNumSmplCtrls when allocation is not possible." 2485 ::= { frsldMIBCompliances 1 } 2487 -- 2488 -- Units of Conformance 2489 -- 2490 frsldPvcReqCtrlGroup OBJECT-GROUP 2491 OBJECTS { 2492 frsldPvcCtrlStatus, 2493 frsldPvcCtrlPurge, 2494 frsldPvcCtrlDeleteOnPurge, 2495 frsldPvcCtrlLastPurgeTime 2496 } 2497 STATUS current 2498 DESCRIPTION 2499 "A collection of required objects providing 2500 control information applicable to a PVC which 2501 implements Service Level Definitions." 2502 ::= { frsldMIBGroups 1 } 2504 frsldPvcPacketGroup OBJECT-GROUP 2505 OBJECTS { 2506 frsldPvcCtrlPacketFreq 2507 } 2508 STATUS current 2509 DESCRIPTION 2510 "A collection of optional objects providing packet 2511 level control information applicable to a PVC which 2512 implements Service Level Definitions." 2513 ::= { frsldMIBGroups 2 } 2515 frsldPvcDelayCtrlGroup OBJECT-GROUP 2516 OBJECTS { 2517 frsldPvcCtrlDelayFrSize, 2518 frsldPvcCtrlDelayType, 2519 frsldPvcCtrlDelayTimeOut 2520 } 2521 STATUS current 2522 DESCRIPTION 2523 "A collection of optional objects providing delay 2524 control information applicable to a PVC which 2525 implements Service Level Definitions. 2527 If this group is implemented, frsldPvcPacketGroup 2528 and frsldPvcDelayDataGroup MUST also be implemented." 2530 ::= { frsldMIBGroups 3 } 2532 frsldPvcSampleCtrlGroup OBJECT-GROUP 2533 OBJECTS { 2534 frsldSmplCtrlStatus, 2535 frsldSmplCtrlColPeriod, 2536 frsldSmplCtrlBuckets, 2537 frsldSmplCtrlBucketsGranted 2538 } 2539 STATUS current 2540 DESCRIPTION 2541 "A collection of optional objects providing sample 2542 control information applicable to a PVC which 2543 implements Service Level Definitions. 2545 If this group is implemented, frsldPvcReqDataGroup 2546 and frsldPvcSampleGeneralGroup MUST also be 2547 implemented." 2548 ::= { frsldMIBGroups 4 } 2550 frsldPvcReqDataGroup OBJECT-GROUP 2551 OBJECTS { 2552 frsldPvcDataFrDeliveredC, 2553 frsldPvcDataFrDeliveredE, 2554 frsldPvcDataFrOfferedC, 2555 frsldPvcDataFrOfferedE, 2556 frsldPvcDataDataDeliveredC, 2557 frsldPvcDataDataDeliveredE, 2558 frsldPvcDataDataOfferedC, 2559 frsldPvcDataDataOfferedE, 2560 frsldPvcDataUnavailableTime, 2561 frsldPvcDataUnavailables 2562 } 2563 STATUS current 2564 DESCRIPTION 2565 "A collection of required objects providing data 2566 collected on a PVC which implements Service 2567 Level Definitions." 2568 ::= { frsldMIBGroups 5 } 2570 frsldPvcDelayDataGroup OBJECT-GROUP 2571 OBJECTS { 2572 frsldPvcDataMissedPolls 2573 } 2574 STATUS current 2575 DESCRIPTION 2576 "A collection of optional objects providing delay 2577 data collected on a PVC which implements Service 2578 Level Definitions. 2580 If this group is implemented, frsldPvcDelayCtrlGroup 2581 MUST also be implemented." 2582 ::= { frsldMIBGroups 6 } 2584 frsldPvcHCFrameDataGroup OBJECT-GROUP 2585 OBJECTS { 2586 frsldPvcDataHCFrDeliveredC, 2587 frsldPvcDataHCFrDeliveredE, 2588 frsldPvcDataHCFrOfferedC, 2589 frsldPvcDataHCFrOfferedE 2590 } 2591 STATUS current 2592 DESCRIPTION 2593 "A collection of optional objects providing high 2594 capacity frame data collected on a PVC which 2595 implements Service Level Definitions." 2596 ::= { frsldMIBGroups 7 } 2598 frsldPvcHCOctetDataGroup OBJECT-GROUP 2599 OBJECTS { 2600 frsldPvcDataHCDataDeliveredC, 2601 frsldPvcDataHCDataDeliveredE, 2602 frsldPvcDataHCDataOfferedC, 2603 frsldPvcDataHCDataOfferedE 2604 } 2605 STATUS current 2606 DESCRIPTION 2607 "A collection of optional objects providing high 2608 capacity octet data collected on a PVC which 2609 implements Service Level Definitions." 2610 ::= { frsldMIBGroups 8 } 2612 frsldPvcSampleDelayGroup OBJECT-GROUP 2613 OBJECTS { 2614 frsldPvcSmplDelayMin, 2615 frsldPvcSmplDelayMax, 2616 frsldPvcSmplDelayAvg, 2617 frsldPvcSmplMissedPolls 2618 } 2619 STATUS current 2620 DESCRIPTION 2621 "A collection of optional objects providing delay 2622 sample data collected on a PVC which implements 2623 Service Level Definitions. 2625 If this group is implemented, frsldPvcDelayCtrlGroup 2626 MUST also be implemented." 2627 ::= { frsldMIBGroups 9 } 2629 frsldPvcSampleDataGroup OBJECT-GROUP 2630 OBJECTS { 2631 frsldPvcSmplFrDeliveredC, 2632 frsldPvcSmplFrDeliveredE, 2633 frsldPvcSmplFrOfferedC, 2634 frsldPvcSmplFrOfferedE, 2635 frsldPvcSmplDataDeliveredC, 2636 frsldPvcSmplDataDeliveredE, 2637 frsldPvcSmplDataOfferedC, 2638 frsldPvcSmplDataOfferedE 2639 } 2640 STATUS current 2641 DESCRIPTION 2642 "A collection of optional objects providing data 2643 and frame delivery sample data collected on a PVC 2644 which implements Service Level Definitions. 2646 If this group is implemented, frsldPvcReqDataGroup 2647 MUST also be implemented." 2648 ::= { frsldMIBGroups 10 } 2650 frsldPvcSampleHCFrameGroup OBJECT-GROUP 2651 OBJECTS { 2652 frsldPvcSmplHCFrDeliveredC, 2653 frsldPvcSmplHCFrDeliveredE, 2654 frsldPvcSmplHCFrOfferedC, 2655 frsldPvcSmplHCFrOfferedE 2656 } 2657 STATUS current 2658 DESCRIPTION 2659 "A collection of optional objects providing high 2660 capacity frame delivery sample data collected on a PVC 2661 which implements Service Level Definitions. 2663 If this group is implemented, frsldPvcHCFrameDataGroup 2664 MUST also be implemented." 2665 ::= { frsldMIBGroups 11 } 2667 frsldPvcSampleHCDataGroup OBJECT-GROUP 2668 OBJECTS { 2669 frsldPvcSmplHCDataDeliveredC, 2670 frsldPvcSmplHCDataDeliveredE, 2671 frsldPvcSmplHCDataOfferedC, 2672 frsldPvcSmplHCDataOfferedE 2673 } 2674 STATUS current 2675 DESCRIPTION 2676 "A collection of optional objects providing high 2677 capacity data delivery sample data collected on a PVC 2678 which implements Service Level Definitions. 2680 If this group is implemented, frsldPvcHCOctetDataGroup 2681 MUST also be implemented." 2682 ::= { frsldMIBGroups 12 } 2684 frsldPvcSampleAvailGroup OBJECT-GROUP 2685 OBJECTS { 2686 frsldPvcSmplUnavailableTime, 2687 frsldPvcSmplUnavailables 2688 } 2689 STATUS current 2690 DESCRIPTION 2691 "A collection of optional objects providing 2692 availability sample data collected on a PVC which 2693 implements Service Level Definitions. 2695 If this group is implemented, frsldPvcReqDataGroup 2696 MUST also be implemented." 2697 ::= { frsldMIBGroups 13 } 2699 frsldPvcSampleGeneralGroup OBJECT-GROUP 2700 OBJECTS { 2701 frsldPvcSmplStartTime, 2702 frsldPvcSmplEndTime 2703 } 2704 STATUS current 2705 DESCRIPTION 2706 "A collection of optional objects providing 2707 general sample data collected on a PVC which 2708 implements Service Level Definitions." 2709 ::= { frsldMIBGroups 14 } 2711 frsldCapabilitiesGroup OBJECT-GROUP 2712 OBJECTS { 2713 frsldPvcCtrlWriteCaps, 2714 frsldSmplCtrlWriteCaps, 2715 frsldRPCaps, 2716 frsldMaxPvcCtrls, 2717 frsldNumPvcCtrls, 2718 frsldMaxSmplCtrls, 2719 frsldNumSmplCtrls 2720 } 2721 STATUS current 2722 DESCRIPTION 2723 "A collection of required objects providing 2724 capability information and control for this 2725 MIB module." 2726 ::= { frsldMIBGroups 15 } 2727 END 2729 8. Acknowledgments 2731 This document was produced by the Frame Relay Service MIB Working 2732 Group. It is based on the Frame Relay Forum's implementation 2733 agreement on service level definitions, FRF.13 [17]. 2735 The editors would like to thank the following people for their 2736 helpful comments: 2738 o Ken Rehbehn, Visual Networks 2740 o Santa Dasu, Quick Eagle Networks 2742 9. References 2744 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2745 Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, 2746 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2748 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2749 Management Information for TCP/IP-based Internets", RFC 1155, STD 2750 16, Performance Systems International, Hughes LAN Systems, May 1990 2752 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2753 STD 16, Performance Systems International, Hughes LAN Systems, March 2754 1991 2756 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2757 RFC 1215, Performance Systems International, March 1991 2759 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2760 and S. Waldbusser, "Structure of Management Information Version 2 2761 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 2762 Braunschweig, SNMP Research, First Virtual Holdings, International 2763 Network Services, April 1999 2765 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2766 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 2767 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2768 Virtual Holdings, International Network Services, April 1999 2770 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2771 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 2772 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2773 Virtual Holdings, International Network Services, April 1999 2775 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2776 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 2777 Systems International, Performance Systems International, MIT 2778 Laboratory for Computer Science, May 1990. 2780 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction 2781 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 2782 Systems, Inc., Dover Beach Consulting, Inc., International Network 2783 Services, January 1996. 2785 [10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2786 Mappings for Version 2 of the Simple Network Management Protocol 2787 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 2788 Beach Consulting, Inc., International Network Services, January 2789 1996. 2791 [11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2792 Processing and Dispatching for the Simple Network Management 2793 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 2794 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2796 [12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2797 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2798 2574, IBM T. J. Watson Research, April 1999 2800 [13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2801 Operations for Version 2 of the Simple Network Management Protocol 2802 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 2803 Beach Consulting, Inc., International Network Services, January 2804 1996. 2806 [14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2807 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2808 Systems, April 1999 2810 [15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2811 Control Model (VACM) for the Simple Network Management Protocol 2812 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 2813 Cisco Systems, Inc., April 1999 2815 [16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2816 Version 3 of the Internet-standard Network Management Framework", 2817 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 2818 Ericsson, Cisco Systems, April 1999 2820 [17]Frame Relay Forum Technical Committee, "Service Level Definitions 2821 Implementations Agreement", FRF.13, August 1998. 2823 [18]Brown, T., "Definitions of Managed Objects for Frame Relay Service", 2824 RFC 1604, Bell Communications Research, March 1994. 2826 [19]Waldbusser, S., "Remote Network Monitoring Management Information 2827 Base Version 2 using SMIv2", RFC 2021, International Network 2828 Service, January 1997. 2830 [20]Brown, C., Baker, F., "Management Information Base for Frame Relay 2831 DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, 2832 September 1997. 2834 [21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC 2835 2863, Cisco Systems, Argon Networks, June 2000. 2837 10. Security Considerations 2839 There are a number of management objects defined in this MIB that 2840 have a MAX-ACCESS clause of read-write and/or read-create. Such 2841 objects may be considered sensitive or vulnerable in some network 2842 environments. The support for SET operations in a non-secure 2843 environment without proper protection can have a negative effect on 2844 network operations. 2846 SNMPv1 by itself is not a secure environment. Even if the network 2847 itself is secure (for example by using IPSec), even then, there is no 2848 control as to who on the secure network is allowed to access and 2849 GET/SET (read/change/create/delete) the objects in this MIB. 2851 It is recommended that the implementers consider the security 2852 features as provided by the SNMPv3 framework. Specifically, the use 2853 of the User-based Security Model RFC 2274 [12] and the View-based 2854 Access Control Model RFC 2275 [15] is recommended. 2856 It is then a customer/user responsibility to ensure that the SNMP 2857 entity giving access to an instance of this MIB, is properly 2858 configured to give access to the objects only to those principals 2859 (users) that have legitimate rights to indeed GET or SET 2860 (change/create/delete) them. 2862 11. Authors' Addresses 2864 Robert Steinberger 2865 Fujitsu Network Communications 2866 2801 Telecom Parkway 2867 Richardson, TX 75082 2869 Phone: 1-972-479-4739 2871 Email: robert.steinberger@fnc.fujitsu.com 2873 Orly Nicklass, Ph.D 2874 RAD Data Communications Ltd. 2875 12 Hanechoshet Street 2876 Tel Aviv, Israel 69710 2878 Phone: 972 3 7659969 2880 Email: Orly_n@rrad.co.il 2882 12. Copyright Section 2884 Copyright (C) The Internet Society (2000). All Rights Reserved. 2886 This document and translations of it may be copied and furnished to 2887 others, and derivative works that comment on or otherwise explain it 2888 or assist in its implementation may be prepared, copied, published 2889 and distributed, in whole or in part, without restriction of any 2890 kind, provided that the above copyright notice and this paragraph are 2891 included on all such copies and derivative works. However, this 2892 document itself may not be modified in any way, such as by removing 2893 the copyright notice or references to the Internet Society or other 2894 Internet organizations, except as needed for the purpose of 2895 developing Internet standards in which case the procedures for 2896 copyrights defined in the Internet Standards process must be 2897 followed, or as required to translate it into languages other than 2898 English. 2900 The limited permissions granted above are perpetual and will not be 2901 revoked by the Internet Society or its successors or assigns. 2903 This document and the information contained herein is provided on an 2904 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2905 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2906 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2907 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2908 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.