idnits 2.17.1 draft-ietf-frnetmib-frmrelay-service-04.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. ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** 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 142: '... The keywords MUST, MUST NOT, REQUIR...' RFC 2119 keyword, line 143: '... SHOULD NOT, RECOMMENDED, NOT RECOMM...' RFC 2119 keyword, line 257: '...etary reference points which MAY exist...' RFC 2119 keyword, line 425: '...monitoring point MAY be implemented in...' RFC 2119 keyword, line 434: '...monitoring point MAY be restricted to ...' (35 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 984 has weird spacing: '...(1) and frCir...' == Line 2860 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 (May 1, 2001) is 8389 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 112, but not defined == Missing Reference: '11' is mentioned on line 112, but not defined == Missing Reference: '12' is mentioned on line 2819, but not defined == Missing Reference: '13' is mentioned on line 117, but not defined == Missing Reference: '14' is mentioned on line 119, but not defined == Missing Reference: '15' is mentioned on line 2820, but not defined == Missing Reference: '16' is mentioned on line 124, but not defined == Missing Reference: '23' is mentioned on line 146, but not defined == Missing Reference: '17' is mentioned on line 2699, but not defined == Missing Reference: '18' is mentioned on line 994, but not defined == Missing Reference: '19' is mentioned on line 769, but not defined == Missing Reference: '21' is mentioned on line 971, but not defined == Missing Reference: '20' is mentioned on line 973, 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: 11 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 May 1, 2001 6 draft-ietf-frnetmib-frmrelay-service-04.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. Object Definitions .......................................... 24 86 7. Acknowledgments ............................................. 58 87 8. References .................................................. 59 88 9. Security Considerations ..................................... 62 89 10. Authors' Addresses ......................................... 62 90 11. Copyright Section .......................................... 63 92 1. The SNMP Management Framework 94 The SNMP Management Framework presently consists of five major 95 components: 97 o An overall architecture, described in RFC 2571 [1]. 99 o Mechanisms for describing and naming objects and events for the 100 purpose of management. The first version of this Structure of 101 Management Information (SMI) is called SMIv1 and described in RFC 102 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 103 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 104 2580 [7]. 106 o Message protocols for transferring management information. The 107 first version of the SNMP message protocol is called SNMPv1 and 108 described in RFC 1157 [8]. A second version of the SNMP message 109 protocol, which is not an Internet standards track protocol, is 110 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 111 The third version of the message protocol is called SNMPv3 and 112 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 114 o Protocol operations for accessing management information. The 115 first set of protocol operations and associated PDU formats is 116 described in RFC 1157 [8]. A second set of protocol operations and 117 associated PDU formats is described in RFC 1905 [13]. 119 o A set of fundamental applications described in RFC 2573 [14] and 120 the view-based access control mechanism described in RFC 2575 121 [15]. 123 A more detailed introduction to the current SNMP Management Framework 124 can be found in RFC 2570 [16]. 126 Managed objects are accessed via a virtual information store, termed 127 the Management Information Base or MIB. Objects in the MIB are 128 defined using the mechanisms defined in the SMI. 130 This memo specifies a MIB module that is compliant to the SMIv2. A 131 MIB conforming to the SMIv1 can be produced through the appropriate 132 translations. The resulting translated MIB must be semantically 133 equivalent, except where objects or events are omitted because no 134 translation is possible (use of Counter64). Some machine readable 135 information in SMIv2 will be converted into textual descriptions in 136 SMIv1 during the translation process. However, this loss of machine 137 readable information is not considered to change the semantics of the 138 MIB. 140 2. Conventions 142 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 143 SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when 144 they appear in this document, are to be interpreted as described in 145 RFC 2119 [23]. 147 3. Overview 149 This MIB module addresses the items required to manage the Frame 150 Relay Forum's Implementation Agreement for Service Level Definitions 151 (FRF.13 [17]). At present, this applies to these values of the 152 ifType variable in the Internet-standard MIB: 154 o frameRelay (32) 156 o frameRelayService (44) 158 This section provides an overview and background of how to use this 159 MIB module. 161 3.1. Frame Relay Service Level Definitions 163 The frame relay service level definitions address specific 164 characteristics of a frame relay service that can be used to 165 facilitate the following tasks: 167 o Evaluation of frame relay service providers, offerings or 168 products. 170 o Measurement of Quality of Service. 172 o Enforcement of Service Level Agreements. 174 o Planning or describing a frame relay network. 176 The following parameters are defined in FRF.13 [17] as a sufficient 177 set of values to accomplish the tasks previously stated. 179 o Delay - The amount of time elapsed, in microseconds, from the time 180 a frame exits the source to the time it reaches the destination. 181 NOTE: FRF.13 [17] defines this value in terms of milliseconds. 183 o Frame Delivery Ratio - The ratio of the number of frames delivered 184 to the destination versus the number of frames sent by the source. 185 This ratio can be further divided by inspecting either only the 186 frames within the CIR or only the frames in excess of the CIR. 188 o Data Delivery Ratio - The ratio of the amount of data delivered to 189 the destination versus the amount of data sent by the source. This 190 ratio can be further divided by inspecting either only the data 191 within the CIR or only the data in excess of the CIR. 193 o Service Availability - The amount of time the frame relay service 194 was not available. There are three types of availability 195 statistics defined in FRF.13 [17]: Mean Time to Repair, Virtual 196 Connection Availability, and Mean Time Between Service Outages. 197 The later two require information about the scheduled outage time. 198 It is assumed that scheduled outage time information will be 199 maintained by the network management software, so it is not 200 included in the MIB module. 202 Consult FRF.13 [17] for more details. 204 3.2. Terminology 206 o CIR - The Committed Information Rate (CIR) is the subscriber data 207 rate (expressed in bits/second) that the network commits to 208 deliver under normal network conditions. [18] 210 o DLCI - Data Link Connection Identifier. [18] 212 o Logical Port - This term is used to model the Frame Relay 213 "interface" on a device. [18] 215 o NNI - Network to Network Interface. [18] 217 o Permanent Virtual Connection (PVC) - A virtual connection that has 218 its end-points and bearer capabilities defined at subscription 219 time. [18] 221 o Reference Point (RP) - The point of reference within the network 222 model at which the calculations or data collection takes place. 224 o UNI - User to Network Interface. [18] 226 3.3. Network Model 228 The basic model, as illustrated in figure 1 below, contains two frame 229 relay DTE endpoints connected to a network cloud via a frame relay 230 UNI interface. The network cloud can contain zero or more internal 231 frame relay NNI connections that interconnect multiple networks. The 232 calculations and data collection can be performed at any reference 233 point within the network. 235 +-------------+ +-------------+ 236 | Frame Relay | | Frame Relay | 237 | DTE Device | | DTE Device | 238 +------+------+ +------+------+ 239 | | 240 UNI UNI 241 Connection Connection 242 | | 243 +------+------+ NNI +-------------+ NNI +------+------+ 244 | Network A +------------+ Network B +------------+ Network C | 245 +-------------+ Connection +-------------+ Connection +-------------+ 247 Figure 1 248 Frame Relay Network Reference Model 250 3.4. Reference Points 252 The collection and calculations of the service level definitions 253 apply to two reference points within the network. These two points 254 are the locations where the frames are referenced in the collection 255 of the service level specific information. The reference points used 256 in the MIB module are shown in figure 2 below. For completeness, the 257 module also allows for proprietary reference points which MAY exist 258 anywhere in the network that is not a previously defined reference 259 point. The meaning of the proprietary reference points is 260 insignificant unless defined by the device manufacturer. 262 +---------------------------+ 263 |+-----------+ +-----------+| 264 || | |Measurement|| 265 ||Frame Relay---Engine --(Source RP)----+ 266 ||DTE | |(If Exists)|| | 267 |+-----------+ +-----------+| | 268 +---------------------------+ | 269 Frame Relay Source | 270 +------------------------------------------+ 271 | Frame Relay Network 272 | +----------------------------------+ 273 | | +------------------------------+ | 274 | | | +---------+ +---------+ | | 275 | | | | | | Traffic | | | 276 +--(Ingress RP)--- L1 / L2 --- Policing| | | 277 | | | Control | | Engine | | | 278 | | +---------+ +----|----+ | | 279 | | | | | 280 | | (Traffic Policing RP)| | 281 | +------------------|-----------+ | 282 | Ingress Node | | 283 | | | 284 | +-----------|-----------+ | 285 | | Intermediate Nodes | | 286 | +-----------|-----------+ | 287 | | | 288 | Egress Node | | 289 | +--------------|-----------+ | 290 | | (Egress Queue Input RP) | | 291 | | | | | 292 | | +-------+------+ | | 293 | | | Egress Queue | | | 294 | | +-------+------+ | | 295 | | | | | 296 | | (Egress Queue Output RP) | | 297 | +--------------|-----------+ | 298 +--------------------|-------------+ 299 Frame Relay Destination | 300 +---------------------------+ +-----------+ 301 |+-----------+ +-----------+| | 302 || | |Measurement|| | 303 ||Frame Relay---Engine --(Destination RP)--+ 304 ||DTE | |(If Exists)|| 305 |+-----------+ +-----------+| 306 +---------------------------+ 308 Figure 2 309 Reference Points (FRF.13 [17]) 311 The MIB variables frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP 312 allow the user to view and configure the reference points at which 313 the calculations occur. These variables are specific to the device 314 on which they are located. Frame relay devices act as both frame 315 sources and frame destinations. The definitions in this MIB module 316 apply to the interaction of a pair of devices on the network path. 317 The same device can potentially use different reference points for 318 calculation and collection of the statistics based on whether the 319 referenced frame is sent or received by the device. When the device 320 is acting as a frame source, the value of frsldPvcCtrlTransmitRP 321 reflects the reference point used for all source calculations 322 pertaining to the specified PVC. When the device is acting as a frame 323 destination, the value of frsldPvcCtrlReceiveRP reflects the 324 reference point used for all destination calculations pertaining to 325 the specified PVC. 327 For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue 328 measurement domain as a domain in which measurement is performed 329 between an Ingress Reference Point and an Egress Queue Input 330 Reference Point. For this domain between a source device and a 331 destination device, the value of frsldPvcCtrlTransmitRP for the 332 source device would be set to ingTxLocalRP(2) and the value of 333 frsldPvcCtrlReceiveRP for the destination device would be set to 334 eqiRxLocalRP(4). While it is usually the case that the reference 335 points would be equivalent on the remote device when monitoring 336 frames going in the opposite direction, there is no requirement for 337 them to be so. 339 It can be seen from the above example that a total of four reference 340 points are required in order to collect information for both 341 directions of traffic flow. The reference points represent the 342 transmit and receive directions at both ends of a PVC. If a device 343 has knowledge of the information from the remote device, it is 344 possible to collect the statistics from a single device. This is not 345 always the case. In most instances, two devices will need to be 346 monitored to capture a complete description of the service level on a 347 PVC. The reference points a single device is capable of monitoring 348 are contained in the frsldRPCaps object. 350 3.5. Measurement Methodology 352 This document neither recommends nor suggests a method of 353 implementation. This is left to the device manufacturer and should be 354 independent of the data that is actually collected. 356 Periodic collection of this data can be performed through either 357 polling of the data table, use of the sample tables or use of the 358 user history group of RFC 2021 [19]. 360 3.6. Theory of Operation 362 The following sections describe how to use this MIB module. They 363 include row handling, data collection and data calculation. The 364 recommendations here in are suggestions as to implementation and do 365 not infer that they are the only method that can be used to perform 366 such operations. 368 3.6.1. Capabilities Discovery 370 Three objects are provided specifically to aid the network manager in 371 discovering the capabilities of the device with respect to this MIB 372 module. 374 o frsldPvcCtrlWriteCaps This object reports the write capabilities 375 of the PVC Control Table. Use this object 376 to determine which objects can be modified. 377 This need only be referenced if row 378 creation or modification is to be 379 performed. 381 o frsldSmplCtrlWriteCaps This object reports the write capabilities 382 of the Sample Control Table. Use this 383 object to determine which objects can be 384 modified. The group need only be 385 referenced if the sample tables will be 386 used to collect historical information. 388 o frsldRPCaps This object reports the reference points at 389 which the device is capable of collecting 390 information. This object needs to be 391 referenced if row creation is to be 392 performed in the PVC Control Table. 393 Devices can only create rows containing 394 supported reference points. 396 These objects do not imply that there is no need for an Agent 397 Capabilities macro for devices that do not fully support every object 398 in this MIB module. They are provided specifically to aid in the 399 ensured network management operations of this MIB module with respect 400 to row creation and modification. 402 An additional four objects are provided to report and control memory 403 the utilization of this MIB module. These objects are 404 frsldMaxPvcCtrls, frsldNumPvcCtrls, frsldMaxSmplCtrls are 405 frsldNumSmplCtrls. Together, they allow a manager to control the 406 amount of memory allocated for specific utilization by this MIB 407 module. This is done by setting the maximum allowed allocation of 408 controls. 410 3.6.2. Determining Reference Points for Row Creation 412 The performance of a PVC is monitored by evaluating the uni- 413 directional flow of frames from an ingress point to an egress point. 414 Reference points describe where each of the two measurements are 415 made. Monitoring both of the uni-directional flows that make-up the 416 PVC frame traffic requires a total of four reference points as shown 417 in Figures 3 through 5. A monitoring point that evaluates traffic is 418 restricted to counting frames that pass the reference points hosted 419 locally on the monitoring point. Thus, if the monitoring point is 420 near the ingress point of the flow, it will count the frames entering 421 into the frame relay network. The complete picture of frame loss for 422 the uni-directional flow requires information from the downstream 423 reference point located at another (remote) monitoring point. 425 The local monitoring point MAY be implemented in such way that the 426 information from the downstream monitoring point is moved to the 427 local monitoring point using implementation-specific mechanisms. In 428 this case all information required to calculate frame loss becomes 429 available from the local measurement point. The local measurement 430 point agent is capable of reporting all the objects in the 431 FrsldPvcDataEntry row - the counts for offered frames entering the 432 network and delivered frames exiting the network. 434 Alternatively, the local monitoring point MAY be restricted to counts 435 of frames observed on the local device only. In this case, the 436 objects of the FrsldPvcDataEntry row reporting what happened on the 437 remote device are not available. 439 The following list shows the possible valid reference points for an 440 FRF.13 SLA from the source reference point to the destination 441 reference point in both directions. 443 o Local Information Only 445 Local Device: srcLocalRP, desLocalRP 446 Remote Device: srcLocalRP, desLocalRP 448 o Remote Information Only 450 Local Device: srcRemoteRP, desRemoteRP 451 Remote Device: srcRemoteRP, desRemoteRP 453 o Mixed Two Device Model 1 (Local Device Always Transmitter) 455 Local Device: srcLocalRP, desRemoteRP 456 Remote Device: srcLocalRP, desRemoteRP 458 o Mixed Two Device Model 2 (Local Device Always Receiver) 460 Local Device: srcRemoteRP, desLocalRP 461 Remote Device: srcRemoteRP, desLocalRP 463 o Mixed One Device Model 1 (Directional Rows) 465 First Row: srcRemoteRP, desLocalRP (Receiver Row) 466 Second Row: srcLocalRP, desRemoteRP (Sender Row) 468 o Mixed One Device Model 2 (Device Based Rows) 470 First Row: srcLocalRP, desLocalRP (Local Row) 471 Second Row: srcRemoteRP, desRemoteRP (Remote Row) 473 Each of the above combinations is valid and provides the same 474 information. 476 The following steps are recommended to find which reference points 477 need to be configured: 479 1) Locate both of the devices at either end of the PVC to be 480 monitored. 482 2) Determine the capabilities by referencing the frsldRPCaps object 483 of each device. 485 3) Locate the best combination of the two devices such that the 486 necessary reference points are all represented. 488 4) If any one of the necessary reference points does not exist in 489 the combination of the two devices, it is not possible to 490 monitor the FRF.13 defined SLA between the two reference point 491 on the PVC. 493 3.6.2.1. Graphical Examples of Reference Points 495 FRF.13 [17] defines three specific combinations of reference points: 496 Edge-to-Edge Interface, Edge-to-Edge Egress Queue and End-to-End. 498 Examples of valid reference points that may be used for each of these 499 are discussed in the sections below. 501 It is often the case that a device knows as a minimum either only 502 local information or both local and remote information. Because 503 these are two common examples, each will be illustrated below. 505 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example 507 Device 1 Device 2 508 +-------------+ +-------------+ 509 | Ingress | | Egress | 510 | +-----+ | | +-----+ | 511 |(A)| | | Traffic Flow | | |(B)| 512 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 513 | | | | From Device 1 to 2 | | | | 514 | +-----+ | | +-----+ | 515 | | | | 516 | Egress | | Ingress | 517 | +-----+ | | +-----+ | 518 |(D)| | | Traffic Flow | | |(C)| 519 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 520 | | | | From Device 2 to 1 | | | | 521 | +-----+ | | +-----+ | 522 +-------------+ +-------------+ 524 where (A), (B), (C) and (D) are reference points 526 Figure 3 528 For devices with only local knowledge, one row is required on each 529 device as follows: 531 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 533 (B) frsldPvcCtlrReceiveRP for Device 2 = eqoRxLocalRP(5) 535 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 537 (D) frsldPvcCtlrReceiveRP for Device 1 = eqoRxLocalRP(5) 539 In which a single row is created on Device 1 containing reference 540 points (A) and (D), and a single row is created on Device 2 541 containing reference points (C) and (B). 543 For devices with both local and remote knowledge, the two rows can 544 exist in any combination on either device. For this example, the 545 transmitting devices will be responsible for information regarding 546 the flow for which they are the origin. Only one row is required per 547 device for this example. 549 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 551 (B) frsldPvcCtlrReceiveRP for Device 1 = eqoRxRemoteRP(11) 553 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 555 (D) frsldPvcCtlrReceiveRP for Device 2 = eqoRxRemoteRP(11) 557 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example 559 Device 1 Device 2 560 +-------------+ +-------------+ 561 | Ingress | | Egress | 562 | +-----+ | | +-----+ | 563 |(A)| | | Traffic Flow |(B)| | | 564 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 565 | | | | From Device 1 to 2 | | | | 566 | +-----+ | | +-----+ | 567 | | | | 568 | Egress | | Ingress | 569 | +-----+ | | +-----+ | 570 | | |(D)| Traffic Flow | | |(C)| 571 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 572 | | | | From Device 2 to 1 | | | | 573 | +-----+ | | +-----+ | 574 +-------------+ +-------------+ 576 where (A), (B), (C) and (D) are reference points 578 Figure 4 580 For devices with only local knowledge, one row is required on each 581 device as follows: 583 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 585 (B) frsldPvcCtlrReceiveRP for Device 2 = eqiRxLocalRP(4) 587 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 589 (D) frsldPvcCtlrReceiveRP for Device 1 = eqiRxLocalRP(4) 591 In which a single row is created on Device 1 containing reference 592 points (A) and (D), and a single row is created on Device 2 593 containing reference points (C) and (B). 595 For devices with both local and remote knowledge, the two rows can 596 exist in any combination on either device. For this example, the 597 transmitting devices will be responsible for information regarding 598 the flow for which they are the origin. Only one row is required per 599 device for this example. 601 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 603 (B) frsldPvcCtlrReceiveRP for Device 1 = eqiRxRemoteRP(10) 605 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 607 (D) frsldPvcCtlrReceiveRP for Device 2 = eqiRxRemoteRP(10) 609 3.6.2.1.3. End-to-End Using Reference Point Example 611 Device 1 Device 2 612 +-------------+ +-------------+ 613 | Source | | Destination | 614 | +-----+ | | +-----+ | 615 |(A)| | | Traffic Flow | | |(B)| 616 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 617 | | | | From Device 1 to 2 | | | | 618 | +-----+ | | +-----+ | 619 | | | | 620 | Destination | | Source | 621 | +-----+ | | +-----+ | 622 |(D)| | | Traffic Flow | | |(C)| 623 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 624 | | | | From Device 2 to 1 | | | | 625 | +-----+ | | +-----+ | 626 +-------------+ +-------------+ 628 where (A), (B), (C) and (D) are reference points 630 Figure 5 632 For devices with only local knowledge, one row is required on each 633 device as follows: 635 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 637 (B) frsldPvcCtlrReceiveRP for Device 2 = desLocalRP(1) 638 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 640 (D) frsldPvcCtlrReceiveRP for Device 1 = desLocalRP(1) 642 In which a single row is created on Device 1 containing reference 643 points (A) and (D), and a single row is created on Device 2 644 containing reference points (C) and (B). 646 For devices with both local and remote knowledge, the two rows can 647 exist in any combination on either device. For this example, the 648 transmitting devices will be responsible for information regarding 649 the flow for which they are the origin. Only one row is required per 650 device for this example. 652 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 654 (B) frsldPvcCtlrReceiveRP for Device 1 = desRemoteRP(7) 656 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 658 (D) frsldPvcCtlrReceiveRP for Device 2 = desRemoteRP(7) 660 3.6.3. Creation Process 662 In some cases, devices will automatically populate the rows of PVC 663 Control Table and potentially the Sample Control Table. However, in 664 many cases, it may be necessary for a network manager to manually 665 create rows. 667 Manual creation of rows requires the following steps: 669 1) Ensure the PVC exists between the two devices. 671 2) Determine the necessary reference points for row creation. 673 3) Create the row(s) in each device as needed. 675 4) Create the row(s) in the sample control tables if desired. 677 3.6.4. Destruction Process 678 3.6.4.1. Manual Row Destruction 680 Manual row destruction is straight forward. Any row can be destroyed 681 and the resources allocated to it are freed by setting the value of 682 its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus) 683 to destroy(6). It should be noted that when frsldPvcCtrlStatus is 684 set to destroy(6) all associated sample control, sample and data 685 table rows will also be destroyed. Similarly, when 686 frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be 687 destroyed. The frsldPvcCtrlPurge objects do not apply to manual row 688 destruction. If the row is set to destroy(6) manually, the rows are 689 destroyed as part of the set. 691 3.6.4.2. Automatic Row Destruction 693 Rows is the tables may be destroyed automatically based on the 694 existence of the DLCI on which they rely. This behavior is 695 controlled by the frsldPvcCtrlPurge and frsldPvcCtrlDeleteOnPurge 696 objects. When a DLCI no longer exists in the device, the data in the 697 tables has no relation to anything known on the network. However, 698 there may be some need to keep the historic information active for a 699 short period after the destruction or removal of a DLCI. If the 700 basis for the row no longer exists, the row will be destroyed at the 701 end of the purge interval that is controlled by frsldPvcCtrlPurge. 703 The effects of automatic row destruction are the same as manual row 704 destruction. 706 3.6.5. Modification Process 708 All read-create items in this MIB module can be modified at any time 709 if they are fully supported. Write access is not required. To 710 simplify the use of the MIB frsldPvcCtrlWriteCaps and 711 frsldSmplCtrlWriteCaps state which of the read-create variables can 712 actually be written on a particular device. 714 3.6.6. Collection Process 716 3.6.6.1. Remote Polling 718 This MIB module supports data collection through remote polling of 719 the free running counters in the PVC Data Table. Remote polling is a 720 common method used to capture real-time statistics. A remote 721 management station polls the device to collect the desired 722 information. It is recommended all statistics for a single PVC be 723 collected in a single PDU. 725 The following objects are designed around the concept of real-time 726 polling: 728 o frsldPvcDataMissedPolls 729 o frsldPvcDataFrDeliveredC 730 o frsldPvcDataFrDeliveredE 731 o frsldPvcDataFrOfferedC 732 o frsldPvcDataFrOfferedE 733 o frsldPvcDataDataDeliveredC 734 o frsldPvcDataDataDeliveredE 735 o frsldPvcDataDataOfferedC 736 o frsldPvcDataDataOfferedE 737 o frsldPvcDataHCFrDeliveredC 738 o frsldPvcDataHCFrDeliveredE 739 o frsldPvcDataHCFrOfferedC 740 o frsldPvcDataHCFrOfferedE 741 o frsldPvcDataHCDataDeliveredC 742 o frsldPvcDataHCDataDeliveredE 743 o frsldPvcDataHCDataOfferedC 744 o frsldPvcDataHCDataOfferedE 745 o frsldPvcDataUnavailableTime 746 o frsldPvcDataUnavailables 748 3.6.6.2. Sampling 750 The sample tables provide the ability to historically sample data 751 without requiring the additional overhead of polling. At key 752 periods, a network management station can collect the samples needed. 753 This method allows the manager to perform the collection of data at 754 times that will least affect the active network traffic. 756 The sample data can be collected using a series of SNMP getNext or 757 getBulk operations. The value of frsldPvcSmplIdx increments with 758 each new collection bucket. This allows the managers to skip 759 information that has already been collected. However, care should be 760 taken in that the value can roll over after a long period of time. 762 The start and end times of a collection period allow the manager to 763 know what the actual period of collection was. It is possible for 764 there to be discontinuities in the sample table, so both start and 765 end should be referenced. 767 3.6.6.3. User History 769 User history, as defined in RFC 2021 [19], is an alternative 770 mechanism that can be used to get the same benefits as the sample 771 table by using the objects provided for real-time polling. Some 772 devices MAY have the ability to use user history and opt not to 773 support the sample tables. If this is the case, the information from 774 the data table can be used to define a group of user history objects. 776 3.6.7. Use of MIB Module in Calculation of Service Level Definitions 778 The objects in this MIB module can be used to calculate the 779 statistics defined in FRF.13 [17]. The description below describes 780 the calculations for one direction of the data flow, i.e. data sent 781 from local transmitter to a remote receiver. A complete set of 782 bidirectional information would require calculations based on both 783 directions. For the purposes of this description, the reference 784 points used SHOULD consistently represent data that is sent by one 785 device and received by the other. 787 A complete evaluation requires the combination of two uni-directional 788 flows. It is possible for a management station to combine all of the 789 calculated information into one conceptual row. Doing this requires 790 that each of the metrics are collected for both flow directions and 791 grouped by direction If the information is split between two 792 devices, the management station must know which two devices to 793 communicate with for the collection of all information. The grouping 794 of information SHOULD be from ingress to egress in each flow 795 direction. 797 The calculations below use the following terminology: 799 o DelayAvg 801 The average delay on the PVC. This is represented within the 802 MIB module by frsldPvcSmplDelayAvg. 804 o FrDeliveredC 806 The number of frames received by the receiving device through 807 the receive reference point that were delivered within CIR. 808 This is represented within the MIB module by one of 809 frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC, 810 frsldPvcSmplFrDeliveredC, or frsldPvcSmplHCFrDeliveredC. 812 o FrDeliveredE 813 The number of frames received by the receiving device through 814 the receive reference point that were delivered in excess of 815 CIR. This is represented within the MIB module by one of 816 frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE, 817 frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE. 819 o FrOfferedC 821 The number of frames offered by the transmitting device through 822 the transmit reference point that were sent within CIR. This is 823 represented within the MIB module by one of 824 frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC, 825 frsldPvcSmplFrOfferedC, or frsldPvcSmplHCFrOfferedC. 827 o FrOfferedE 829 The number of frames offered by the transmitting device through 830 the transmit reference point that were sent in excess of CIR. 831 This is represented within the MIB module by one of 832 frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE, 833 frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE. 835 o DataDeliveredC 837 The number of octets received by the receiving device through 838 the receive reference point that were delivered within CIR. 839 This is represented within the MIB module by one of 840 frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC, 841 frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC. 843 o DataDeliveredE 845 The number of octets received by the receiving device through 846 the receive reference point that were delivered in excess of 847 CIR. This is represented within the MIB module by one of 848 frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE, 849 frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE. 851 o DataOfferedC 853 The number of octets offered by the transmitting device through 854 the transmit reference point that were sent within CIR. This is 855 represented within the MIB module by one of 856 frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC, 857 frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC. 859 o DataOfferedE 860 The number of octets offered by the transmitting device through 861 the transmit reference point that were sent in excess of CIR. 862 This is represented within the MIB module by one of 863 frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE, 864 frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE. 866 o UnavailableTime 868 The amount of time the PVC was not available during the interval 869 of interest. This is represented within the MIB module by 870 either frsldPvcDataUnavailableTime or 871 frsldPvcSmplUnavailableTime. 873 o Unavailables 875 The number of times the PVC was declared to be unavailable 876 during the interval of interest. This is represented within the 877 MIB module by either frsldPvcDataUnavailables or 878 frsldPvcSmplUnavailables. 880 3.6.8. Delay 882 The frame transfer delay is defined as the amount of time elapsed, in 883 microseconds, from the time a frame exits the source to the time it 884 reaches the destination. The average delay can be found using the MIB 885 variable described in DelayAvg above. The delay may be calculated as 886 either round trip or one way, and this information is held in the 887 frsldPvcCtrlDelayType MIB variable. If the delay be calculated as 888 round trip, the value of DelayAvg represents the average of the total 889 delays of the round trips. In this case, the manager SHOULD divide 890 the value returned by the agent by two to obtain the frame transfer 891 delay. In the case that frsldPvcCtrlDelayType is oneWay, the value 892 of DelayAvg represents the average of the frame transfer delays and 893 SHOULD be used as is. 895 3.6.9. Frame Delivery Ratio 897 The frame delivery ratio is defined as the total number of frames 898 delivered to the destination divided by the frames offered by the 899 source. The destination values can be obtained using FrDeliveredC 900 and FrDeliveredE. The source values can be obtained using FrOfferedC 901 and FrOfferedE. 903 FrDeliveredC + FrDeliveredE 904 Frame Delivery Ratio = --------------------------- 905 FrOfferedC + FrOfferedE 907 FrDeliveredC 908 Committed Frame Delivery Ratio = ------------ 909 FrOfferedC 911 FrDeliveredE 912 Excess Frame Delivery Ratio = ------------ 913 FrOfferedE 915 3.6.10. Data Delivery Ratio 917 The data delivery ratio is defined as the total amount of data 918 delivered to the destination divided by the data offered by the 919 source. The destination values can be obtained using DataDeliveredC 920 and DataDeliveredE. The source values can be obtained using 921 DataOfferedC and DataOfferedE. 923 DataDeliveredC + DataDeliveredE 924 Data Delivery Ratio = ------------------------------- 925 DataOfferedC + DataOfferedE 927 DataDeliveredC 928 Committed Data Delivery Ratio = -------------- 929 DataOfferedC 931 DataDeliveredE 932 Excess Data Delivery Ratio = -------------- 933 DataOfferedE 935 3.6.11. Service Availability 937 Some forms of service availability measurement defined in FRF.13 [17] 938 require knowledge of the amount of time the network is allowed to be 939 unavailable during the period of measurement. This is called the 940 excluded outage time and will be represented in the measurements 941 below as ExcludedTime. It is assumed that the management software 942 will maintain this information in that it often relates to specific 943 times and dates that many devices are not capable of maintaining. 944 Further, it may change based on a moving maintenance window that the 945 device cannot track well. 947 Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0. 949 UnavailableTime 950 Otherwise, FRMTTR = --------------- 951 Unavailables 953 Virtual Connection Availability (FRVCA) = 0 if IntervalTime equals 954 ExcludedTime. 956 IntervalTime - ExcludedTime - UnavailableTime 957 Otherwise, FRVCA = --------------------------------------------- *100 958 IntervalTime - ExcludedTime 960 Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0. 962 Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime 963 --------------------------------------------- 964 Unavailables 966 4. Relation to Other MIB Modules 968 There is no explicit relation to any other frame relay MIB module nor 969 are any required to implement this MIB module. However, there is a 970 need for knowledge of ifIndexes and some understanding of DLCIs. The 971 ifIndex information can be found in the IF-MIB [21] which is 972 required. The DLCI information can be found in either the Frame Relay 973 DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB (RFC 974 1604) [18]; however, neither is required. 976 Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to 977 active(1) the system can be in one of the following three states: 979 (1) The respective DLCI is known and is active. This corresponds to a 980 state in which frPVCEndptRowStatus is active(1) and 981 frPVCEndptRcvdSigStatus is either active(2) or none(4) for the 982 Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame 983 Relay DTE MIB, the same state is shown by frCircuitRowStatus of 984 active(1) and frCircuitState of active(2). 986 (2) The respective DLCI has not been created. This corresponds to a 987 state in which the row with either frPVCEndptDLCIIndex or 988 frCircuitDlci equal to the respective DLCI does not exist in 989 either the frPVCEndptTable or the frCircuitTable respectively. 991 (3) The respective DLCI has just been removed. This corresponds to a 992 state in which either frPVCEndptRowStatus is no longer active(1) 993 or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for 994 the Frame Relay Network Services MIB (RFC 1604) [18]. For the 995 Frame Relay DTE MIB, the same state is shown when either 996 frCircuitRowStatus is no longer active(1) or frCircuitState is no 997 longer active(2). 999 For the first case, the row in the frsldPvcDataTable will be filled. 1000 If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective 1001 DLCI is also `active' the frsldPvcSampleTable will be filled as well. 1003 For the second case, the respective rows will not be added to any of 1004 the data or sample tables and frsldPvcCtrlStatus SHOULD report 1005 notReady(3). 1007 For the third case, frsldPvcCtrlDeleteOnPurge should direct the 1008 behavior of the system. If all tables are purged, this case will be 1009 equivalent to the second case above. Otherwise, frsldPvcCtrlStatus 1010 SHOULD remain active(1). 1012 5. Structure of the MIB Module 1014 The FRSLD-MIB consists of the following components: 1016 o frsldPvcCtrlTable 1018 o frsldSmplCtrlTable 1020 o frsldPvcDataTable 1022 o frsldPvcSampleTable 1024 o frsldCapabilities 1026 Refer to the compliance statement defined within for a definition of 1027 what objects MUST be implemented. 1029 5.1. frsldPvcCtrlTable 1031 The frsldPvcCtrlTable is the central control table for operations of 1032 the Frame Relay Service Level Definitions MIB. It provides variables 1033 to control the parameters required to calculate the objects in the 1034 other tables. 1036 A row in this table MUST exist in order for a row to exist in any 1037 other table in this MIB module. 1039 5.2. frsldSmplCtrlTable 1041 This is an optional table to allow control of sampling of the data in 1042 the data table. 1044 5.3. frsldPvcDataTable 1046 This table contains the calculated data. It relies on configuration 1047 from the control table. 1049 5.4. frsldPvcSampleTable 1051 This table contains samples of the delivery and availability 1052 information from the data table as well as delay information 1053 calculated over the sample period. It relies on configuration from 1054 both the control table and the sample control table. 1056 5.5. frsldCapabilities 1058 This is a group of objects that define write capabilities of the 1059 read-create objects in the tables above. 1061 6. Object Definitions 1063 FRSLD-MIB DEFINITIONS ::= BEGIN 1065 IMPORTS 1066 MODULE-IDENTITY, OBJECT-TYPE, 1067 Counter32, Gauge32, Integer32, 1068 Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI 1069 CounterBasedGauge64 FROM HCNUM-TC 1070 TEXTUAL-CONVENTION, RowStatus, 1071 TimeStamp FROM SNMPv2-TC 1072 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1073 ifIndex FROM IF-MIB; 1075 frsldMIB MODULE-IDENTITY 1076 LAST-UPDATED "200105011500Z" -- May 1, 2001 1077 ORGANIZATION "IETF Frame Relay Service MIB Working Group" 1078 CONTACT-INFO 1079 "IETF Frame Relay Service MIB (frnetmib) Working Group 1081 WG Charter: http://www.ietf.org/html.charters/ 1082 frnetmib-charter.html 1083 WG-email: frnetmib@sunroof.eng.sun.com 1084 Subscribe: frnetmib-request@sunroof.eng.sun.com 1085 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 1086 Chair: Andy Malis 1087 Lucent Technologies 1088 Email: amalis@lucent.com 1090 WG editor: Robert Steinberger 1091 Paradyne Networks and 1092 Fujitsu Network Communications 1093 Email: robert.steinberger@fnc.fujitsu.com 1095 Co-author: Orly Nicklass 1096 RAD Data Communications Ltd. 1097 EMail: Orly_n@rad.co.il" 1098 DESCRIPTION 1099 "The MIB module to describe generic objects for 1100 FRF.13 Frame Relay Service Level Definitions." 1101 REVISION "200105011500Z" 1102 DESCRIPTION 1103 "o Added FrsldTxRP and FrsldRxRP TCs for reference 1104 points and changed frsldPvcCtrlTransmitRP and 1105 frsldPvcCtrlReceiveRP to use new TCs. 1106 o Added REFERENCE clauses. 1107 o Added frsldMaxPvcCtrls, frsldNumPvcCtrls, 1108 frsldMaxSmplCtrls and frsldNumSmplCtrls 1109 for memory control. 1110 o Made HC Data groups conditionally mandatory 1111 based on the speed of the network interface. 1112 o Updated description of the compliance objects. 1113 o Updated the description of the groups to show 1114 relationship." 1115 REVISION "200009191500Z" 1116 DESCRIPTION 1117 "o Removed frsldPvcCtrlDelayCnt. 1118 o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl- 1119 AvailBuckets, and frsldSmplCtrlAvailBucketsGranted. 1120 o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*. 1121 o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1122 and frsldPvcDataDelayAvg. 1123 o Changed frsldPvcDataSample* to frsldPvcSample*. 1124 o Changed frsldPvcDataSmpl* to frsldPvcSmpl*. 1125 o Added frsldPvcSmplUnavailableTime and frsldPvcSmpl- 1126 Unavailables. 1127 o Removed frsldPvcAvailSampleTable and all objects. 1128 o Removed frsldPvcCtrlDelayCnt from frsldPvcCtrlWrite- 1129 Caps. 1130 o Adjusted group definitions for frsldPvcDelayCtrlGroup, 1131 frsldPvc[Data]SampleCtrlGroup, frsldPvcReqDataGroup, 1132 frsldPvcDelayDataGroup, and frsldPvc[Avail]SampleAvail- 1133 Group to reflect above changes." 1135 REVISION "200006141500Z" 1136 DESCRIPTION 1137 "o Removed all uses of FrsldLocation by removing objects 1138 frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc 1139 o Removed FrsldRP TC and distributed source and destina- 1140 tion specific information into index for control table 1141 as frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP. 1142 o Added frsldPvcCtrlDelayCnt to control table. 1143 o Changed frsldPvcDataUnavailableTime from TimeStamp to 1144 TimeTicks. 1145 o Updated text of RowStatus objects 1146 o Added frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP 1147 as indices to ALL tables. 1148 o Added HC counters for all data delivery stats and 1149 samples. 1150 o Adjusted description of sample information for clarity. 1151 o Adjusted names of sample objects for consistency. 1152 o Added frsldRPCaps. 1153 o Changed location to mib-2 1154 o Reworked Group Definitions." 1156 REVISION "200002061500Z" 1157 DESCRIPTION 1158 "o Published as draft-ietf-frnetmib-frmrelay-service-00.txt 1159 o Added frsldCapabilities group to define the 1160 read/write capabilities 1161 o Changed location to experimental 104 1162 o Changed name of frsldTables to frsldObjects 1163 o Changed MAX-ACCESS of frsldPvcCtrlDelayType to 1164 read-create 1165 o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1166 and frsldPvcDataDelayAvg from the sample period" 1168 REVISION "199909031500Z" 1169 DESCRIPTION 1170 "o Added range to frsldPvcCtrlPacketFreq 1171 o Changed range of frsldPvcCtrlDelayTimeOut to match 1172 that of frsldPvcCtrlPacketFreq 1173 o Clarified what happens when frsldPvcCtrlPacketFreq 1174 is set to zero 1175 o Changed delay to count in microseconds instead of 1176 milliseconds 1177 o Created a new sample control table and moved sample 1178 specific information into it. 1179 o Changed the prefix of `frsldPvcCtrl' object name to 1180 `frsldSmplCtrl' 1181 o Added the sample control index to the indices of the 1182 sample tables 1184 o Changed all occasions of TimeTicks to TimeStamp 1185 o Added frsldPvcCtrlPurge to aid in control validity 1186 of information due to PVC status changes 1187 o Added frsldPvcCtrlDeleteOnPurge object 1188 o Added frsldPvcCtrlLastPurgeTime object 1189 o Added units clauses to all time related fields. 1190 o Reworded the `change in' syntax to be more explicit" 1191 ::= { mib-2 xxx } -- RFC editor - IANA assigns xxx 1193 -- 1194 -- Textual Conventions 1195 -- 1196 FrsldTxRP ::= TEXTUAL-CONVENTION 1197 STATUS current 1198 DESCRIPTION 1199 "The reference point a PVC uses for calculation 1200 of transmitter related statistics. 1202 The valid values for this type of object are as follows: 1203 - srcLocalRP(1) for the local source 1204 - ingTxLocalRP(2) for the local ingress queue input 1205 - tpTxLocalRP(3) for the local traffic policing 1206 - eqiTxLocalRP(4) for the local egress queue input 1207 - eqoTxLocalRP(5) for the local egress queue output 1208 - otherTxLocalRP(6) for any other local transmit point 1209 - srcRemoteRP(7) for the remote source 1210 - ingTxLocalRP(8) for the remote ingress queue input 1211 - tpTxLocalRP(9) for the remote traffic policing 1212 - eqiTxRemoteRP(10) for the remote egress queue input 1213 - eqoTxRemoteRP(11) for the remote egress queue output 1214 - otherTxRemoteRP(12) for any other remote xmit point" 1215 REFERENCE 1216 "FRF.13: Section 2.3" 1217 SYNTAX INTEGER { 1218 srcLocalRP(1), 1219 ingTxLocalRP(2), 1220 tpTxLocalRP(3), 1221 eqiTxLocalRP(4), 1222 eqoTxLocalRP(5), 1223 otherTxLocalRP(6), 1224 srcRemoteRP(7), 1225 ingTxRemoteRP(8), 1226 tpTxRemoteRP(9), 1227 eqiTxRemoteRP(10), 1228 eqoTxRemoteRP(11), 1229 otherTxRemoteRP(12) 1230 } 1232 FrsldRxRP ::= TEXTUAL-CONVENTION 1233 STATUS current 1234 DESCRIPTION 1235 "The reference point a PVC uses for calculation 1236 of receiver related statistics. 1238 The valid values for this object are as follows: 1239 - desLocalRP(1) for the local destination 1240 - ingRxLocalRP(2) for the local ingress queue input 1241 - tpRxLocalRP(3) for the local traffic policing 1242 - eqiRxLocalRP(4) for the local egress queue input 1243 - eqoRxLocalRP(5) for the local egress queue output 1244 - otherRxLocalRP(6) for any other local receive point 1245 - desRemoteRP(7) for the remote destination 1246 - ingRxRemoteRP(8) for the remote ingress input 1247 - tpRxRemoteRP(9) for the remote traffic policing 1248 - eqiRxRemoteRP(10) for the remote egress queue input 1249 - eqoRxRemoteRP(11) for the remote egress queue output 1250 - otherRxRemoteRP(12) for any other remote receive point" 1251 REFERENCE 1252 "FRF.13: Section 2.3" 1253 SYNTAX INTEGER { 1254 desLocalRP(1), 1255 ingRxLocalRP(2), 1256 tpRxLocalRP(3), 1257 eqiRxLocalRP(4), 1258 eqoRxLocalRP(5), 1259 otherRxLocalRP(6), 1260 desRemoteRP(7), 1261 ingRxRemoteRP(8), 1262 tpRxRemoteRP(9), 1263 eqiRxRemoteRP(10), 1264 eqoRxRemoteRP(11), 1265 otherRxRemoteRP(12) 1266 } 1268 -- 1269 -- Base Objects 1270 --- 1272 frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 } 1273 frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 } 1274 frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 } 1276 -- The Frame Relay Service Level Definitions PVC Control Table 1277 -- 1278 -- This table is used to define and display the parameters of 1279 -- service level definitions on individual PVCs. 1281 frsldPvcCtrlTable OBJECT-TYPE 1282 SYNTAX SEQUENCE OF FrsldPvcCtrlEntry 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The Frame Relay Service Level Definitions 1287 PVC control table." 1288 ::= { frsldObjects 1 } 1290 frsldPvcCtrlEntry OBJECT-TYPE 1291 SYNTAX FrsldPvcCtrlEntry 1292 MAX-ACCESS not-accessible 1293 STATUS current 1294 DESCRIPTION 1295 "An entry in the Frame Relay Service Level 1296 Definitions PVC control table." 1297 INDEX { ifIndex, frsldPvcCtrlDlci, 1298 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1299 ::= { frsldPvcCtrlTable 1 } 1301 FrsldPvcCtrlEntry ::= 1302 SEQUENCE { 1303 -- 1304 -- Index Control Variables 1305 -- 1306 frsldPvcCtrlDlci Integer32, 1307 frsldPvcCtrlTransmitRP FrsldTxRP, 1308 frsldPvcCtrlReceiveRP FrsldRxRP, 1309 frsldPvcCtrlStatus RowStatus, 1310 -- 1311 -- Service Level Definitions Setup Variables 1312 -- 1313 frsldPvcCtrlPacketFreq Integer32, 1314 -- 1315 -- Delay Specific Setup Variables 1316 -- 1317 frsldPvcCtrlDelayFrSize Integer32, 1318 frsldPvcCtrlDelayType INTEGER, 1319 frsldPvcCtrlDelayTimeOut Integer32, 1320 -- 1321 -- Data Persistence Control Variables 1322 -- 1323 frsldPvcCtrlPurge Integer32, 1324 frsldPvcCtrlDeleteOnPurge INTEGER, 1325 frsldPvcCtrlLastPurgeTime TimeStamp 1326 } 1328 frsldPvcCtrlDlci OBJECT-TYPE 1329 SYNTAX Integer32 (16..4194303) 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "The value of this object is equal to the DLCI 1334 value for this PVC." 1335 ::= { frsldPvcCtrlEntry 1 } 1337 frsldPvcCtrlTransmitRP OBJECT-TYPE 1338 SYNTAX FrsldTxRP 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "The reference point this PVC uses for calculation 1343 of transmitter related statistics. This object 1344 together with frsldPvcCtrlReceiveRP define the 1345 measurement domain." 1346 REFERENCE 1347 "FRF.13: Section 2.3" 1348 ::= { frsldPvcCtrlEntry 2 } 1350 frsldPvcCtrlReceiveRP OBJECT-TYPE 1351 SYNTAX FrsldRxRP 1352 MAX-ACCESS not-accessible 1353 STATUS current 1354 DESCRIPTION 1355 "The reference point this PVC uses for calculation 1356 of receiver related statistics. This object 1357 together with frsldPvcCtrlTransmitRP define the 1358 measurement domain." 1359 ::= { frsldPvcCtrlEntry 3 } 1361 frsldPvcCtrlStatus OBJECT-TYPE 1362 SYNTAX RowStatus 1363 MAX-ACCESS read-create 1364 STATUS current 1365 DESCRIPTION 1366 "The status of the current row. This object is 1367 used to add, delete, and disable rows in this 1368 table. When the status changes to active(1) for the 1369 first time, a row will also be added to the data 1370 table below. This row SHOULD not be removed until 1371 the status is changed to deleted. 1373 When this object is set to destroy(6), all associated 1374 sample and data table rows will also be deleted. 1375 When this object is changed from active(1) to any 1376 other valid value, the defined purge behavior will 1377 affect the data and sample tables. 1379 The rows added to this table MUST have a valid 1380 ifIndex and an ifType related to frame relay. Further, 1381 the reference points referred to by frsldPvcCtrlTransmitRP 1382 and frsldPvcCtrlReceiveRP MUST be supported (see the 1383 frsldRPCaps object). 1385 If at any point the row is not in the active(1) state 1386 and the DLCI no longer exists, the state SHOULD 1387 report notReady(3)." 1388 ::= { frsldPvcCtrlEntry 4 } 1390 frsldPvcCtrlPacketFreq OBJECT-TYPE 1391 SYNTAX Integer32 (0..3600) 1392 UNITS "seconds" 1393 MAX-ACCESS read-create 1394 STATUS current 1395 DESCRIPTION 1396 "The frequency in seconds between initiation of 1397 specialized packets used to collect delay and / or 1398 delivery information as supported by the device. 1399 A value of zero indicates that no packets will 1400 be sent." 1401 DEFVAL { 60 } 1402 ::= { frsldPvcCtrlEntry 5 } 1404 frsldPvcCtrlDelayFrSize OBJECT-TYPE 1405 SYNTAX Integer32 (1..8188) 1406 UNITS "octets" 1407 MAX-ACCESS read-create 1408 STATUS current 1409 DESCRIPTION 1410 "The size of the payload in the frame used for 1411 calculation of network delay." 1412 DEFVAL { 128 } 1413 ::= { frsldPvcCtrlEntry 6 } 1415 frsldPvcCtrlDelayType OBJECT-TYPE 1416 SYNTAX INTEGER { 1417 oneWay(1), 1418 roundTrip(2) 1419 } 1420 MAX-ACCESS read-create 1421 STATUS current 1422 DESCRIPTION 1423 "The type of delay measurement performed." 1424 REFERENCE 1425 "FRF.13: Section 3" 1426 ::= { frsldPvcCtrlEntry 7 } 1428 frsldPvcCtrlDelayTimeOut OBJECT-TYPE 1429 SYNTAX Integer32 (1..3600) 1430 UNITS "seconds" 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "A delay frame will count as a missed poll if 1435 it is not updated in the time specified by 1436 frsldPvcCtrlDelayTimeOut." 1437 DEFVAL { 60 } 1438 ::= { frsldPvcCtrlEntry 8 } 1440 frsldPvcCtrlPurge OBJECT-TYPE 1441 SYNTAX Integer32 (0..172800) -- up to 48 hours 1442 UNITS "seconds" 1443 MAX-ACCESS read-create 1444 STATUS current 1445 DESCRIPTION 1446 "This object defines the amount of time the device 1447 will wait, after discovering that a DLCI does not exist, 1448 the DLCI was deleted or the value of frsldPvcCtrlStatus 1449 changes from active(1) to either notInService(2) or 1450 notReady(3), prior to automatically purging the history 1451 in the sample tables and resetting the data in the data 1452 tables to all zeroes. If frsldPvcCtrlStatus is manually 1453 set to destroy(6), this object does not apply." 1454 DEFVAL { 0 } 1455 ::= { frsldPvcCtrlEntry 9 } 1457 frsldPvcCtrlDeleteOnPurge OBJECT-TYPE 1458 SYNTAX INTEGER { 1459 none(1), 1460 sampleContols(2), 1461 all(3) 1462 } 1463 MAX-ACCESS read-create 1464 STATUS current 1465 DESCRIPTION 1466 "This object defines whether rows will 1467 automatically be deleted from the tables 1468 when the information is purged. 1470 - A value of none(1) indicates that no rows 1471 will deleted. The last known values will 1472 be preserved. 1474 - A value of sampleControls(2) indicates 1475 that all associated sample control rows 1476 will be deleted. 1477 - A value of all(3) indicates that all 1478 associated rows SHOULD be deleted." 1479 DEFVAL { all } 1480 ::= { frsldPvcCtrlEntry 10 } 1482 frsldPvcCtrlLastPurgeTime OBJECT-TYPE 1483 SYNTAX TimeStamp 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "This object returns the value of sysUpTime 1488 at the time the information was last purged. 1489 This value SHOULD be set to the sysUpTime 1490 upon setting frsldPvcCtrlStatus to active(1) 1491 for the first time. If frsldPvcCtrlStatus has 1492 never been active(1), this object SHOULD return 0." 1493 ::= { frsldPvcCtrlEntry 11 } 1495 -- The Frame Relay Service Level Definitions Sampling Control 1496 -- Table 1497 -- 1498 -- This table is used to define the sample control parameters 1499 -- of service level definitions on individual PVCs. 1501 frsldSmplCtrlTable OBJECT-TYPE 1502 SYNTAX SEQUENCE OF FrsldSmplCtrlEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "The Frame Relay Service Level Definitions 1507 sampling control table." 1508 ::= { frsldObjects 2 } 1510 frsldSmplCtrlEntry OBJECT-TYPE 1511 SYNTAX FrsldSmplCtrlEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "An entry in the Frame Relay Service Level 1516 Definitions sample control table." 1517 INDEX { ifIndex, frsldPvcCtrlDlci, 1518 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1519 frsldSmplCtrlIdx } 1520 ::= { frsldSmplCtrlTable 1 } 1522 FrsldSmplCtrlEntry ::= 1523 SEQUENCE { 1524 -- 1525 -- Index Control Variables 1526 -- 1527 frsldSmplCtrlIdx Integer32, 1528 frsldSmplCtrlStatus RowStatus, 1529 -- 1530 -- Collection Control Variables 1531 -- 1532 frsldSmplCtrlColPeriod Integer32, 1533 frsldSmplCtrlBuckets Integer32, 1534 frsldSmplCtrlBucketsGranted Integer32 1535 } 1537 frsldSmplCtrlIdx OBJECT-TYPE 1538 SYNTAX Integer32 (1..256) 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "The unique index for this row in the 1543 sample control table." 1544 ::= { frsldSmplCtrlEntry 1 } 1546 frsldSmplCtrlStatus OBJECT-TYPE 1547 SYNTAX RowStatus 1548 MAX-ACCESS read-create 1549 STATUS current 1550 DESCRIPTION 1551 "The status of the current row. This object is 1552 used to add, delete, and disable rows in this 1553 table. This row SHOULD NOT be removed until the 1554 status is changed to destroy(6). When the status 1555 changes to active(1), the collection in the sample 1556 tables below will be activated. 1558 The rows added to this table MUST have a valid 1559 ifIndex, an ifType related to frame relay, 1560 frsldPvcCtrlDlci MUST exist for the specified 1561 ifIndex and frsldPvcCtrlStatus MUST have a 1562 value of active(1). 1564 The value of frsldPvcCtrlStatus MUST be active(1) 1565 to transition this object to active(1). If 1566 the value of frsldPvcCtrlStatus becomes anything 1567 other than active(1) when the state of this object 1568 is not active(1), this object SHOULD be set to 1569 notReady(3)." 1571 ::= { frsldSmplCtrlEntry 2 } 1573 frsldSmplCtrlColPeriod OBJECT-TYPE 1574 SYNTAX Integer32 (1..2147483647) 1575 UNITS "seconds" 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 "The amount of time in seconds that defines a 1580 period of collection for the statistics. 1581 At the end of each period, the statistics will be 1582 sampled and a row is added to the sample table." 1583 ::= { frsldSmplCtrlEntry 3 } 1585 frsldSmplCtrlBuckets OBJECT-TYPE 1586 SYNTAX Integer32 (1..65535) 1587 MAX-ACCESS read-create 1588 STATUS current 1589 DESCRIPTION 1590 "The number of discrete buckets over which the 1591 data statistics are sampled. 1593 When this object is created or modified, the device 1594 SHOULD attempt to set the frsldSmplCtrlBuckets- 1595 Granted to a value as close as is possible 1596 depending upon the implementation and the available 1597 resources." 1598 DEFVAL { 60 } 1599 ::= { frsldSmplCtrlEntry 4 } 1601 frsldSmplCtrlBucketsGranted OBJECT-TYPE 1602 SYNTAX Integer32 (0..65535) 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The number of discrete buckets granted. This 1607 object will return 0 until frsldSmplCtrlStatus is 1608 set to active(1). At that time the buckets will be 1609 allocated depending upon implementation and 1610 available resources." 1611 ::= { frsldSmplCtrlEntry 5 } 1613 -- The Frame Relay Service Level Definitions PVC Data Table 1614 -- 1615 -- This table contains the accumulated values of 1616 -- the collected data. This table is the table that should 1617 -- be referenced by external polling mechanisms if time 1618 -- based polling be desired. 1620 frsldPvcDataTable OBJECT-TYPE 1621 SYNTAX SEQUENCE OF FrsldPvcDataEntry 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "The Frame Relay Service Level Definitions 1626 data table. 1628 This table contains accumulated values of the 1629 collected data. It is the table that should be 1630 referenced by external polling mechanisms if 1631 time based polling be desired." 1632 ::= { frsldObjects 3 } 1634 frsldPvcDataEntry OBJECT-TYPE 1635 SYNTAX FrsldPvcDataEntry 1636 MAX-ACCESS not-accessible 1637 STATUS current 1638 DESCRIPTION 1639 "An entry in the Frame Relay Service Level 1640 Definitions data table." 1641 INDEX { ifIndex, frsldPvcCtrlDlci, 1642 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1643 ::= { frsldPvcDataTable 1 } 1645 FrsldPvcDataEntry ::= 1646 SEQUENCE { 1647 frsldPvcDataMissedPolls Counter32, 1648 frsldPvcDataFrDeliveredC Counter32, 1649 frsldPvcDataFrDeliveredE Counter32, 1650 frsldPvcDataFrOfferedC Counter32, 1651 frsldPvcDataFrOfferedE Counter32, 1652 frsldPvcDataDataDeliveredC Counter32, 1653 frsldPvcDataDataDeliveredE Counter32, 1654 frsldPvcDataDataOfferedC Counter32, 1655 frsldPvcDataDataOfferedE Counter32, 1656 frsldPvcDataHCFrDeliveredC Counter64, 1657 frsldPvcDataHCFrDeliveredE Counter64, 1658 frsldPvcDataHCFrOfferedC Counter64, 1659 frsldPvcDataHCFrOfferedE Counter64, 1660 frsldPvcDataHCDataDeliveredC Counter64, 1661 frsldPvcDataHCDataDeliveredE Counter64, 1662 frsldPvcDataHCDataOfferedC Counter64, 1663 frsldPvcDataHCDataOfferedE Counter64, 1664 frsldPvcDataUnavailableTime TimeTicks, 1665 frsldPvcDataUnavailables Counter32 1666 } 1668 frsldPvcDataMissedPolls OBJECT-TYPE 1669 SYNTAX Counter32 1670 MAX-ACCESS read-only 1671 STATUS current 1672 DESCRIPTION 1673 "The total number of polls that have been determined 1674 to be missed." 1675 ::= { frsldPvcDataEntry 1 } 1677 frsldPvcDataFrDeliveredC OBJECT-TYPE 1678 SYNTAX Counter32 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "The number of frames that were received at 1683 frsldPvcCtrlReceiveRP and determined to have been 1684 sent within CIR." 1685 REFERENCE 1686 "FRF.13: Section 4.1 (FramesDeliveredc)" 1687 ::= { frsldPvcDataEntry 2 } 1689 frsldPvcDataFrDeliveredE OBJECT-TYPE 1690 SYNTAX Counter32 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "The number of frames that were received at 1695 frsldPvcCtrlReceiveRP and determined to have been 1696 sent in excess of the CIR." 1697 REFERENCE 1698 "FRF.13: Section 4.1 (FramesDeliverede)" 1699 ::= { frsldPvcDataEntry 3 } 1701 frsldPvcDataFrOfferedC OBJECT-TYPE 1702 SYNTAX Counter32 1703 MAX-ACCESS read-only 1704 STATUS current 1705 DESCRIPTION 1706 "The number of frames that were offered through 1707 frsldPvcCtrlTransmitRP within CIR." 1708 REFERENCE 1709 "FRF.13: Section 4.1 (FramesOfferedc)" 1710 ::= { frsldPvcDataEntry 4 } 1712 frsldPvcDataFrOfferedE OBJECT-TYPE 1713 SYNTAX Counter32 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "The number of frames that were offered through 1718 frsldPvcCtrlTransmitRP in excess of the CIR." 1719 REFERENCE 1720 "FRF.13: Section 4.1 (FramesOfferede)" 1721 ::= { frsldPvcDataEntry 5 } 1723 frsldPvcDataDataDeliveredC OBJECT-TYPE 1724 SYNTAX Counter32 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "The number of octets that were received at 1729 frsldPvcCtrlReceiveRP and determined to have been 1730 sent within CIR." 1731 REFERENCE 1732 "FRF.13: Section 5.1 (DataDeliveredc)" 1733 ::= { frsldPvcDataEntry 6 } 1735 frsldPvcDataDataDeliveredE OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The number of octets that were received at 1741 frsldPvcCtrlReceiveRP and determined to have been 1742 sent in excess of the CIR." 1743 REFERENCE 1744 "FRF.13: Section 5.1 (DataDeliverede)" 1745 ::= { frsldPvcDataEntry 7 } 1747 frsldPvcDataDataOfferedC OBJECT-TYPE 1748 SYNTAX Counter32 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "The number of octets that were offered through 1753 frsldPvcCtrlTransmitRP within CIR." 1754 REFERENCE 1755 "FRF.13: Section 5.1 (DataOfferedc)" 1756 ::= { frsldPvcDataEntry 8 } 1758 frsldPvcDataDataOfferedE OBJECT-TYPE 1759 SYNTAX Counter32 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "The number of octets that were offered through 1764 frsldPvcCtrlTransmitRP in excess of the CIR." 1765 REFERENCE 1766 "FRF.13: Section 5.1 (DataOfferede)" 1767 ::= { frsldPvcDataEntry 9 } 1769 frsldPvcDataHCFrDeliveredC OBJECT-TYPE 1770 SYNTAX Counter64 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "The number of frames that were received at 1775 frsldPvcCtrlReceiveRP and determined to have been 1776 sent within CIR. This object is a 64-bit version 1777 of frsldPvcDataFrDeliveredC." 1778 REFERENCE 1779 "FRF.13: Section 4.1 (FramesDeliveredc)" 1780 ::= { frsldPvcDataEntry 10 } 1782 frsldPvcDataHCFrDeliveredE OBJECT-TYPE 1783 SYNTAX Counter64 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "The number of frames that were received at 1788 frsldPvcCtrlReceiveRP and determined to have been 1789 sent in excess of the CIR. This object is a 64-bit 1790 version of frsldPvcDataFrDeliveredE." 1791 REFERENCE 1792 "FRF.13: Section 4.1 (FramesDeliverede)" 1793 ::= { frsldPvcDataEntry 11 } 1795 frsldPvcDataHCFrOfferedC OBJECT-TYPE 1796 SYNTAX Counter64 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The number of frames that were offered through 1801 frsldPvcCtrlTransmitRP within CIR. This object is 1802 a 64-bit version of frsldPvcDataFrOfferedC." 1803 REFERENCE 1804 "FRF.13: Section 4.1 (FramesOfferedc)" 1805 ::= { frsldPvcDataEntry 12 } 1807 frsldPvcDataHCFrOfferedE OBJECT-TYPE 1808 SYNTAX Counter64 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "The number of frames that were offered through 1813 frsldPvcCtrlTransmitRP in excess of the CIR. This 1814 object is a 64-bit version of frsldPvcDataFrOfferedE." 1815 REFERENCE 1816 "FRF.13: Section 4.1 (FramesOfferede)" 1817 ::= { frsldPvcDataEntry 13 } 1819 frsldPvcDataHCDataDeliveredC OBJECT-TYPE 1820 SYNTAX Counter64 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "The number of octets that were received at 1825 frsldPvcCtrlReceiveRP and determined to have been 1826 sent within CIR. This object is a 64-bit version of 1827 frsldPvcDataDataDeliveredC." 1828 REFERENCE 1829 "FRF.13: Section 5.1 (DataDeliveredc)" 1830 ::= { frsldPvcDataEntry 14 } 1832 frsldPvcDataHCDataDeliveredE OBJECT-TYPE 1833 SYNTAX Counter64 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "The number of octets that were received at 1838 frsldPvcCtrlReceiveRP and determined to have been 1839 sent in excess of the CIR. This object is a 64-bit 1840 version of frsldPvcDataDataDeliveredE." 1841 REFERENCE 1842 "FRF.13: Section 5.1 (DataDeliverede)" 1843 ::= { frsldPvcDataEntry 15 } 1845 frsldPvcDataHCDataOfferedC OBJECT-TYPE 1846 SYNTAX Counter64 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "The number of octets that were offered through 1851 frsldPvcCtrlTransmitRP within CIR. This object is 1852 a 64-bit version of frsldPvcDataDataOfferedC." 1853 REFERENCE 1854 "FRF.13: Section 5.1 (DataOfferedc)" 1855 ::= { frsldPvcDataEntry 16 } 1857 frsldPvcDataHCDataOfferedE OBJECT-TYPE 1858 SYNTAX Counter64 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "The number of octets that were offered through 1863 frsldPvcCtrlTransmitRP in excess of the CIR. 1864 This object is a 64-bit version of 1865 frsldPvcDataDataOfferedE." 1866 REFERENCE 1867 "FRF.13: Section 5.1 (DataOfferede)" 1868 ::= { frsldPvcDataEntry 17 } 1870 frsldPvcDataUnavailableTime OBJECT-TYPE 1871 SYNTAX TimeTicks 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "The amount of time this PVC was declared unavailable 1876 for any reason since this row was created." 1877 REFERENCE 1878 "FRF.13: Section 6.1 (OutageTime)" 1879 ::= { frsldPvcDataEntry 18 } 1881 frsldPvcDataUnavailables OBJECT-TYPE 1882 SYNTAX Counter32 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "The number of times this PVC was declared unavailable 1887 for any reason since this row was created." 1888 REFERENCE 1889 "FRF.13: Section 6.1 (OutageCount)" 1890 ::= { frsldPvcDataEntry 19 } 1892 -- The Frame Relay Service Level Definitions PVC Sample Table 1893 -- 1894 -- This table contains the sampled delay, delivery and 1895 -- availability information. 1897 frsldPvcSampleTable OBJECT-TYPE 1898 SYNTAX SEQUENCE OF FrsldPvcSampleEntry 1899 MAX-ACCESS not-accessible 1900 STATUS current 1901 DESCRIPTION 1902 "The Frame Relay Service Level Definitions 1903 sample table." 1904 ::= { frsldObjects 4 } 1906 frsldPvcSampleEntry OBJECT-TYPE 1907 SYNTAX FrsldPvcSampleEntry 1908 MAX-ACCESS not-accessible 1909 STATUS current 1910 DESCRIPTION 1911 "An entry in the Frame Relay Service Level 1912 Definitions data sample table." 1913 INDEX { ifIndex, frsldPvcCtrlDlci, 1914 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1915 frsldSmplCtrlIdx, frsldPvcSmplIdx } 1916 ::= { frsldPvcSampleTable 1 } 1918 FrsldPvcSampleEntry ::= 1919 SEQUENCE { 1920 frsldPvcSmplIdx Integer32, 1921 frsldPvcSmplDelayMin Gauge32, 1922 frsldPvcSmplDelayMax Gauge32, 1923 frsldPvcSmplDelayAvg Gauge32, 1924 frsldPvcSmplMissedPolls Gauge32, 1925 frsldPvcSmplFrDeliveredC Gauge32, 1926 frsldPvcSmplFrDeliveredE Gauge32, 1927 frsldPvcSmplFrOfferedC Gauge32, 1928 frsldPvcSmplFrOfferedE Gauge32, 1929 frsldPvcSmplDataDeliveredC Gauge32, 1930 frsldPvcSmplDataDeliveredE Gauge32, 1931 frsldPvcSmplDataOfferedC Gauge32, 1932 frsldPvcSmplDataOfferedE Gauge32, 1933 frsldPvcSmplHCFrDeliveredC CounterBasedGauge64, 1934 frsldPvcSmplHCFrDeliveredE CounterBasedGauge64, 1935 frsldPvcSmplHCFrOfferedC CounterBasedGauge64, 1936 frsldPvcSmplHCFrOfferedE CounterBasedGauge64, 1937 frsldPvcSmplHCDataDeliveredC CounterBasedGauge64, 1938 frsldPvcSmplHCDataDeliveredE CounterBasedGauge64, 1939 frsldPvcSmplHCDataOfferedC CounterBasedGauge64, 1940 frsldPvcSmplHCDataOfferedE CounterBasedGauge64, 1941 frsldPvcSmplUnavailableTime TimeTicks, 1942 frsldPvcSmplUnavailables Gauge32, 1943 frsldPvcSmplStartTime TimeStamp, 1944 frsldPvcSmplEndTime TimeStamp 1945 } 1947 frsldPvcSmplIdx OBJECT-TYPE 1948 SYNTAX Integer32 (1..2147483647) 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "The bucket index of the current sample. This 1953 increments once for each new bucket in the 1954 table." 1955 ::= { frsldPvcSampleEntry 1 } 1957 frsldPvcSmplDelayMin OBJECT-TYPE 1958 SYNTAX Gauge32 1959 UNITS "microseconds" 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "The minimum delay reported in microseconds measured 1964 for any information packet that arrived during this 1965 interval. 1967 A value of zero means that no data is available." 1968 REFERENCE 1969 "FRF.13: Section 3.1 (FTD)" 1970 ::= { frsldPvcSampleEntry 2 } 1972 frsldPvcSmplDelayMax OBJECT-TYPE 1973 SYNTAX Gauge32 1974 UNITS "microseconds" 1975 MAX-ACCESS read-only 1976 STATUS current 1977 DESCRIPTION 1978 "The largest delay reported in microseconds measured 1979 for any information packet that arrived during this 1980 interval. 1982 A value of zero means that no data is available." 1983 REFERENCE 1984 "FRF.13: Section 3.1 (FTD)" 1985 ::= { frsldPvcSampleEntry 3 } 1987 frsldPvcSmplDelayAvg OBJECT-TYPE 1988 SYNTAX Gauge32 1989 UNITS "microseconds" 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "The average delay reported in microseconds measured 1994 for all delay packets that arrived during this 1995 interval. 1997 A value of zero means that no data is available." 1998 REFERENCE 1999 "FRF.13: Section 3.1 (FTD)" 2000 ::= { frsldPvcSampleEntry 4 } 2002 frsldPvcSmplMissedPolls OBJECT-TYPE 2003 SYNTAX Gauge32 2004 MAX-ACCESS read-only 2005 STATUS current 2006 DESCRIPTION 2007 "The total number of polls that were missed during 2008 this interval." 2009 ::= { frsldPvcSampleEntry 5 } 2011 frsldPvcSmplFrDeliveredC OBJECT-TYPE 2012 SYNTAX Gauge32 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "The number of frames that were received at 2017 frsldPvcCtrlReceiveRP and determined to have been 2018 sent within CIR during this interval." 2019 REFERENCE 2020 "FRF.13: Section 4.1 (FramesDeliveredc)" 2021 ::= { frsldPvcSampleEntry 6 } 2023 frsldPvcSmplFrDeliveredE OBJECT-TYPE 2024 SYNTAX Gauge32 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "The number of frames that were received at 2029 frsldPvcCtrlReceiveRP and determined to have been 2030 sent in excess of the CIR during this interval." 2031 REFERENCE 2032 "FRF.13: Section 4.1 (FramesDeliverede))" 2033 ::= { frsldPvcSampleEntry 7 } 2035 frsldPvcSmplFrOfferedC OBJECT-TYPE 2036 SYNTAX Gauge32 2037 MAX-ACCESS read-only 2038 STATUS current 2039 DESCRIPTION 2040 "The number of frames that were offered through 2041 frsldPvcCtrlTransmitRP within CIR during this 2042 interval." 2043 REFERENCE 2044 "FRF.13: Section 4.1 (FramesOfferedc)" 2045 ::= { frsldPvcSampleEntry 8 } 2047 frsldPvcSmplFrOfferedE OBJECT-TYPE 2048 SYNTAX Gauge32 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "The number of frames that were offered through 2053 frsldPvcCtrlTransmitRP in excess of the CIR 2054 during this interval." 2055 REFERENCE 2056 "FRF.13: Section 4.1 (FramesOfferede)" 2057 ::= { frsldPvcSampleEntry 9 } 2059 frsldPvcSmplDataDeliveredC OBJECT-TYPE 2060 SYNTAX Gauge32 2061 MAX-ACCESS read-only 2062 STATUS current 2063 DESCRIPTION 2064 "The number of octets that were received at 2065 frsldPvcCtrlReceiveRP and determined to have been 2066 sent within CIR during this interval." 2067 REFERENCE 2068 "FRF.13: Section 5.1 (DataDeliveredc)" 2069 ::= { frsldPvcSampleEntry 10 } 2071 frsldPvcSmplDataDeliveredE OBJECT-TYPE 2072 SYNTAX Gauge32 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "The number of octets that were received at 2077 frsldPvcCtrlDeliveredRP and determined to have been 2078 sent in excess of the CIR during this interval." 2079 REFERENCE 2080 "FRF.13: Section 5.1 (DataDeliverede)" 2081 ::= { frsldPvcSampleEntry 11 } 2083 frsldPvcSmplDataOfferedC OBJECT-TYPE 2084 SYNTAX Gauge32 2085 MAX-ACCESS read-only 2086 STATUS current 2087 DESCRIPTION 2088 "The number of octets that were offered through 2089 frsldPvcCtrlTransmitRP within CIR during this 2090 interval." 2091 REFERENCE 2092 "FRF.13: Section 5.1 (DataOfferedc)" 2093 ::= { frsldPvcSampleEntry 12 } 2095 frsldPvcSmplDataOfferedE OBJECT-TYPE 2096 SYNTAX Gauge32 2097 MAX-ACCESS read-only 2098 STATUS current 2099 DESCRIPTION 2100 "The number of octets that were offered through 2101 frsldPvcCtrlTransmitRP in excess of the CIR 2102 during this interval." 2103 REFERENCE 2104 "FRF.13: Section 5.1 (DataOfferede)" 2105 ::= { frsldPvcSampleEntry 13 } 2107 frsldPvcSmplHCFrDeliveredC OBJECT-TYPE 2108 SYNTAX CounterBasedGauge64 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "The number of frames that were received at 2113 frsldPvcCtrlReceiveRP and determined to have been 2114 sent within CIR during this interval. This object 2115 is a 64-bit version of frsldPvcSmplFrDeliveredC." 2116 REFERENCE 2117 "FRF.13: Section 4.1 (FramesDeliveredc)" 2118 ::= { frsldPvcSampleEntry 14 } 2120 frsldPvcSmplHCFrDeliveredE OBJECT-TYPE 2121 SYNTAX CounterBasedGauge64 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "The number of frames that were received at 2126 frsldPvcCtrlReceiveRP and determined to have been 2127 sent in excess of the CIR during this interval. 2128 This object is a 64-bit version of frsldPvcSmpl- 2129 FrDeliveredE." 2130 REFERENCE 2131 "FRF.13: Section 4.1 (FramesDeliverede)" 2132 ::= { frsldPvcSampleEntry 15 } 2134 frsldPvcSmplHCFrOfferedC OBJECT-TYPE 2135 SYNTAX CounterBasedGauge64 2136 MAX-ACCESS read-only 2137 STATUS current 2138 DESCRIPTION 2139 "The number of frames that were offered through 2140 frsldPvcCtrlTransmitRP within CIR during this 2141 interval. This object is a 64-bit version of 2142 frsldPvcSmplFrOfferedC." 2143 REFERENCE 2144 "FRF.13: Section 4.1 (FramesOfferedc)" 2145 ::= { frsldPvcSampleEntry 16 } 2147 frsldPvcSmplHCFrOfferedE OBJECT-TYPE 2148 SYNTAX CounterBasedGauge64 2149 MAX-ACCESS read-only 2150 STATUS current 2151 DESCRIPTION 2152 "The number of frames that were offered through 2153 frsldPvcCtrlTransmitRP in excess of the CIR 2154 during this interval. This object is a 64-bit 2155 version of frsldPvcSmplFrOfferedE." 2156 REFERENCE 2157 "FRF.13: Section 4.1 (FramesOfferede)" 2158 ::= { frsldPvcSampleEntry 17 } 2160 frsldPvcSmplHCDataDeliveredC OBJECT-TYPE 2161 SYNTAX CounterBasedGauge64 2162 MAX-ACCESS read-only 2163 STATUS current 2164 DESCRIPTION 2165 "The number of octets that were received at 2166 frsldPvcCtrlReceiveRP and determined to have been 2167 sent within CIR during this interval. This value 2168 is a 64-bit version of frsldPvcSmplDataDeliveredC." 2169 REFERENCE 2170 "FRF.13: Section 5.1 (DataDeliveredc)" 2171 ::= { frsldPvcSampleEntry 18 } 2173 frsldPvcSmplHCDataDeliveredE OBJECT-TYPE 2174 SYNTAX CounterBasedGauge64 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "The number of octets that were received at 2179 frsldPvcCtrlReceiveRP and determined to have been 2180 sent in excess of the CIR during this interval. This 2181 value is a 64-bit version of frsldPvcSmplData- 2182 DeliveredE." 2183 REFERENCE 2184 "FRF.13: Section 5.1 (DataDeliverede)" 2185 ::= { frsldPvcSampleEntry 19 } 2187 frsldPvcSmplHCDataOfferedC OBJECT-TYPE 2188 SYNTAX CounterBasedGauge64 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "The number of octets that were offered through 2193 frsldPvcCtrlTransmitRP within CIR during this 2194 interval. This value is a 64-bit version of 2195 frsldPvcSmplDataOfferedC." 2196 REFERENCE 2197 "FRF.13: Section 5.1 (DataOfferedc)" 2198 ::= { frsldPvcSampleEntry 20 } 2200 frsldPvcSmplHCDataOfferedE OBJECT-TYPE 2201 SYNTAX CounterBasedGauge64 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "The number of octets that were offered through 2206 frsldPvcCtrlTransmitRP in excess of the CIR 2207 during this interval. This object is a 64-bit 2208 version of frsldPvcSmplDataOfferedE." 2209 REFERENCE 2210 "FRF.13: Section 5.1 (DataOfferede)" 2211 ::= { frsldPvcSampleEntry 21 } 2213 frsldPvcSmplUnavailableTime OBJECT-TYPE 2214 SYNTAX TimeTicks 2215 MAX-ACCESS read-only 2216 STATUS current 2217 DESCRIPTION 2218 "The amount of time this PVC was declared 2219 unavailable for any reason during this interval." 2220 REFERENCE 2221 "FRF.13: Section 6.1 (OutageTime)" 2222 ::= { frsldPvcSampleEntry 22 } 2224 frsldPvcSmplUnavailables OBJECT-TYPE 2225 SYNTAX Gauge32 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "The number of times this PVC was declared 2230 unavailable for any reason during this interval." 2231 REFERENCE 2232 "FRF.13: Section 6.1 (OutageCount)" 2233 ::= { frsldPvcSampleEntry 23 } 2235 frsldPvcSmplStartTime OBJECT-TYPE 2236 SYNTAX TimeStamp 2237 MAX-ACCESS read-only 2238 STATUS current 2239 DESCRIPTION 2240 "The value of sysUpTime when this sample interval 2241 started." 2242 ::= { frsldPvcSampleEntry 24 } 2244 frsldPvcSmplEndTime OBJECT-TYPE 2245 SYNTAX TimeStamp 2246 MAX-ACCESS read-only 2247 STATUS current 2248 DESCRIPTION 2249 "The value of sysUpTime when this sample interval 2250 ended. No data will be reported and the row will 2251 not appear in the table until the sample has 2252 been collected." 2253 ::= { frsldPvcSampleEntry 25 } 2255 -- Capabilities Group 2257 -- This group provides capabilities objects for the tables 2258 -- that control configuration. 2260 frsldPvcCtrlWriteCaps OBJECT-TYPE 2261 SYNTAX BITS { 2262 frsldPvcCtrlStatus(0), 2263 frsldPvcCtrlPacketFreq(1), 2264 frsldPvcCtrlDelayFrSize(2), 2265 frsldPvcCtrlDelayType(3), 2266 frsldPvcCtrlDelayTimeOut(4), 2267 frsldPvcCtrlPurge(5), 2268 frsldPvcCtrlDeleteOnPurge(6) 2269 } 2270 MAX-ACCESS read-only 2271 STATUS current 2272 DESCRIPTION 2273 "This object specifies the write capabilities 2274 for the read-create objects of the PVC Control 2275 table. If the corresponding bit is enabled (1), 2276 the agent supports writes to that object." 2277 ::= { frsldCapabilities 1 } 2279 frsldSmplCtrlWriteCaps OBJECT-TYPE 2280 SYNTAX BITS { 2281 frsldSmplCtrlStatus(0), 2282 frsldSmplCtrlBuckets(1) 2283 } 2284 MAX-ACCESS read-only 2285 STATUS current 2286 DESCRIPTION 2287 "This object specifies the write capabilities 2288 for the read-create objects of the Sample Control 2289 table. If the corresponding bit is enabled (1), 2290 the agent supports writes to that object." 2291 ::= { frsldCapabilities 2 } 2293 frsldRPCaps OBJECT-TYPE 2294 SYNTAX BITS { 2295 srcLocalRP(0), 2296 ingTxLocalRP(1), 2297 tpTxLocalRP(2), 2298 eqiTxLocalRP(3), 2299 eqoTxLocalRP(4), 2300 otherTxLocalRP(5), 2301 srcRemoteRP(6), 2302 ingTxRemoteRP(7), 2303 tpTxRemoteRP(8), 2304 eqiTxRemoteRP(9), 2305 eqoTxRemoteRP(10), 2306 otherTxRemoteRP(11), 2307 desLocalRP(12), 2308 ingRxLocalRP(13), 2309 tpRxLocalRP(14), 2310 eqiRxLocalRP(15), 2311 eqoRxLocalRP(16), 2312 otherRxLocalRP(17), 2313 desRemoteRP(18), 2314 ingRxRemoteRP(19), 2315 tpRxRemoteRP(20), 2316 eqiRxRemoteRP(21), 2317 eqoRxRemoteRP(22), 2318 otherRxRemoteRP(23) 2319 } 2320 MAX-ACCESS read-only 2321 STATUS current 2322 DESCRIPTION 2323 "This object specifies the reference points that 2324 the agent supports. This object allows the management 2325 application to discover which rows can be created on 2326 a specific device." 2327 ::= { frsldCapabilities 3 } 2329 frsldMaxPvcCtrls OBJECT-TYPE 2330 SYNTAX Integer32 (0..2147483647) 2331 MAX-ACCESS read-write 2332 STATUS current 2333 DESCRIPTION 2334 "The maximum number of control rows that can be created 2335 in frsldPvcCtrlTable. Sets to this object lower than 2336 the current value of frsldNumPvcCtrls should result in 2337 badValue." 2338 ::= { frsldCapabilities 4 } 2340 frsldNumPvcCtrls OBJECT-TYPE 2341 SYNTAX Gauge32 2342 MAX-ACCESS read-only 2343 STATUS current 2344 DESCRIPTION 2345 "The current number of rows in frsldPvcCtrlTable." 2346 ::= { frsldCapabilities 5 } 2348 frsldMaxSmplCtrls OBJECT-TYPE 2349 SYNTAX Integer32 (0..2147483647) 2350 MAX-ACCESS read-write 2351 STATUS current 2352 DESCRIPTION 2353 "The maximum number of control rows that can be created 2354 in frsldSmplCtrlTable. Sets to this object lower than 2355 the current value of frsldNumSmplCtrls should result in 2356 badValue." 2357 ::= { frsldCapabilities 6 } 2359 frsldNumSmplCtrls OBJECT-TYPE 2360 SYNTAX Gauge32 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 "The current number of rows in frsldSmplCtrlTable." 2365 ::= { frsldCapabilities 7 } 2367 -- Conformance Information 2369 frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } 2370 frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } 2372 -- 2373 -- Compliance Statements 2374 -- 2376 frsldCompliance MODULE-COMPLIANCE 2377 STATUS current 2378 DESCRIPTION 2379 "The compliance statement for SNMPv2 entities 2380 which support with Frame Relay Service Level 2381 Definitions. This group defines the minimum 2382 level of support required for compliance." 2383 MODULE -- this module 2384 MANDATORY-GROUPS { frsldPvcReqCtrlGroup, 2385 frsldPvcReqDataGroup, 2386 frsldCapabilitiesGroup} 2388 GROUP frsldPvcHCFrameDataGroup 2389 DESCRIPTION 2390 "This group is mandatory only for those network interfaces 2391 with corresponding instance of ifSpeed greater than 2392 650,000,000 bits/second." 2394 GROUP frsldPvcHCOctetDataGroup 2395 DESCRIPTION 2396 "This group is mandatory only for those network interfaces 2397 with corresponding instance of ifSpeed greater than 2398 650,000,000 bits/second." 2400 OBJECT frsldPvcCtrlStatus 2401 SYNTAX INTEGER { active(1) } -- subset of RowStatus 2402 MIN-ACCESS read-only 2403 DESCRIPTION 2404 "Row creation can be done outside of the scope of 2405 the SNMP protocol. If this object is implemented 2406 with max-access of read-only, then the only value 2407 that MUST be returned is active(1) and 2408 frsldPvcCtrlWriteCaps MUST return 0 for the 2409 frsldPvcCtrlStatus(0) bit." 2411 OBJECT frsldPvcCtrlPurge 2412 MIN-ACCESS read-only 2413 DESCRIPTION 2414 "Write access is not required. If this object is 2415 implemented with a max-access of read-only, then 2416 the frsldPvcCtrlPurge(5) bit must return 0." 2418 OBJECT frsldPvcCtrlDeleteOnPurge 2419 MIN-ACCESS read-only 2420 DESCRIPTION 2421 "Write access is not required. If this object is 2422 implemented with a max-access of read-only, then 2423 the frsldPvcCtrlDeleteOnPurge(6) bit must return 2424 0." 2426 OBJECT frsldMaxPvcCtrls 2427 MIN-ACCESS read-only 2428 DESCRIPTION 2429 "Write access is not required if the device either 2430 dynamically allocates memory or statically allocates 2431 a fixed number of entries. In the case of static 2432 allocation, the device should always report the 2433 correct maximum number of controls. In the case 2434 of dynamic allocation, the device SHOULD always 2435 report a number greater than frsldNumPvcCtrls 2436 when allocation is possible and a number equal to 2437 frsldNumPvcCtrls when allocation is not possible." 2439 OBJECT frsldMaxSmplCtrls 2440 MIN-ACCESS read-only 2441 DESCRIPTION 2442 "Write access is not required if the device either 2443 dynamically allocates memory or statically allocates 2444 a fixed number of entries. In the case of static 2445 allocation, the device should always report the 2446 correct maximum number of controls. In the case 2447 of dynamic allocation, the device SHOULD always 2448 report a number greater than frsldNumSmplCtrls 2449 when allocation is possible and a number equal to 2450 frsldNumSmplCtrls when allocation is not possible." 2452 ::= { frsldMIBCompliances 1 } 2454 -- 2455 -- Units of Conformance 2456 -- 2457 frsldPvcReqCtrlGroup OBJECT-GROUP 2458 OBJECTS { 2459 frsldPvcCtrlStatus, 2460 frsldPvcCtrlPurge, 2461 frsldPvcCtrlDeleteOnPurge, 2462 frsldPvcCtrlLastPurgeTime 2463 } 2464 STATUS current 2465 DESCRIPTION 2466 "A collection of required objects providing 2467 control information applicable to a PVC which 2468 implements Service Level Definitions." 2469 ::= { frsldMIBGroups 1 } 2471 frsldPvcPacketGroup OBJECT-GROUP 2472 OBJECTS { 2473 frsldPvcCtrlPacketFreq 2474 } 2475 STATUS current 2476 DESCRIPTION 2477 "A collection of optional objects providing packet 2478 level control information applicable to a PVC which 2479 implements Service Level Definitions." 2480 ::= { frsldMIBGroups 2 } 2482 frsldPvcDelayCtrlGroup OBJECT-GROUP 2483 OBJECTS { 2484 frsldPvcCtrlDelayFrSize, 2485 frsldPvcCtrlDelayType, 2486 frsldPvcCtrlDelayTimeOut 2487 } 2488 STATUS current 2489 DESCRIPTION 2490 "A collection of optional objects providing delay 2491 control information applicable to a PVC which 2492 implements Service Level Definitions. 2494 If this group is implemented, frsldPvcPacketGroup 2495 and frsldPvcDelayDataGroup MUST also be implemented." 2496 ::= { frsldMIBGroups 3 } 2498 frsldPvcSampleCtrlGroup OBJECT-GROUP 2499 OBJECTS { 2500 frsldSmplCtrlStatus, 2501 frsldSmplCtrlColPeriod, 2502 frsldSmplCtrlBuckets, 2503 frsldSmplCtrlBucketsGranted 2504 } 2505 STATUS current 2506 DESCRIPTION 2507 "A collection of optional objects providing sample 2508 control information applicable to a PVC which 2509 implements Service Level Definitions. 2511 If this group is implemented, frsldPvcReqDataGroup 2512 and frsldPvcSampleGeneralGroup MUST also be 2513 implemented." 2514 ::= { frsldMIBGroups 4 } 2516 frsldPvcReqDataGroup OBJECT-GROUP 2517 OBJECTS { 2518 frsldPvcDataFrDeliveredC, 2519 frsldPvcDataFrDeliveredE, 2520 frsldPvcDataFrOfferedC, 2521 frsldPvcDataFrOfferedE, 2522 frsldPvcDataDataDeliveredC, 2523 frsldPvcDataDataDeliveredE, 2524 frsldPvcDataDataOfferedC, 2525 frsldPvcDataDataOfferedE, 2526 frsldPvcDataUnavailableTime, 2527 frsldPvcDataUnavailables 2528 } 2529 STATUS current 2530 DESCRIPTION 2531 "A collection of required objects providing data 2532 collected on a PVC which implements Service 2533 Level Definitions." 2534 ::= { frsldMIBGroups 5 } 2536 frsldPvcDelayDataGroup OBJECT-GROUP 2537 OBJECTS { 2538 frsldPvcDataMissedPolls 2539 } 2540 STATUS current 2541 DESCRIPTION 2542 "A collection of optional objects providing delay 2543 data collected on a PVC which implements Service 2544 Level Definitions. 2546 If this group is implemented, frsldPvcDelayCtrlGroup 2547 MUST also be implemented." 2548 ::= { frsldMIBGroups 6 } 2550 frsldPvcHCFrameDataGroup OBJECT-GROUP 2551 OBJECTS { 2552 frsldPvcDataHCFrDeliveredC, 2553 frsldPvcDataHCFrDeliveredE, 2554 frsldPvcDataHCFrOfferedC, 2555 frsldPvcDataHCFrOfferedE 2556 } 2557 STATUS current 2558 DESCRIPTION 2559 "A collection of optional objects providing high 2560 capacity frame data collected on a PVC which 2561 implements Service Level Definitions." 2562 ::= { frsldMIBGroups 7 } 2564 frsldPvcHCOctetDataGroup OBJECT-GROUP 2565 OBJECTS { 2566 frsldPvcDataHCDataDeliveredC, 2567 frsldPvcDataHCDataDeliveredE, 2568 frsldPvcDataHCDataOfferedC, 2569 frsldPvcDataHCDataOfferedE 2570 } 2571 STATUS current 2572 DESCRIPTION 2573 "A collection of optional objects providing high 2574 capacity octet data collected on a PVC which 2575 implements Service Level Definitions." 2576 ::= { frsldMIBGroups 8 } 2578 frsldPvcSampleDelayGroup OBJECT-GROUP 2579 OBJECTS { 2580 frsldPvcSmplDelayMin, 2581 frsldPvcSmplDelayMax, 2582 frsldPvcSmplDelayAvg, 2583 frsldPvcSmplMissedPolls 2584 } 2585 STATUS current 2586 DESCRIPTION 2587 "A collection of optional objects providing delay 2588 sample data collected on a PVC which implements 2589 Service Level Definitions. 2591 If this group is implemented, frsldPvcDelayCtrlGroup 2592 MUST also be implemented." 2593 ::= { frsldMIBGroups 9 } 2595 frsldPvcSampleDataGroup OBJECT-GROUP 2596 OBJECTS { 2597 frsldPvcSmplFrDeliveredC, 2598 frsldPvcSmplFrDeliveredE, 2599 frsldPvcSmplFrOfferedC, 2600 frsldPvcSmplFrOfferedE, 2601 frsldPvcSmplDataDeliveredC, 2602 frsldPvcSmplDataDeliveredE, 2603 frsldPvcSmplDataOfferedC, 2604 frsldPvcSmplDataOfferedE 2605 } 2606 STATUS current 2607 DESCRIPTION 2608 "A collection of optional objects providing data 2609 and frame delivery sample data collected on a PVC 2610 which implements Service Level Definitions. 2612 If this group is implemented, frsldPvcReqDataGroup 2613 MUST also be implemented." 2614 ::= { frsldMIBGroups 10 } 2616 frsldPvcSampleHCFrameGroup OBJECT-GROUP 2617 OBJECTS { 2618 frsldPvcSmplHCFrDeliveredC, 2619 frsldPvcSmplHCFrDeliveredE, 2620 frsldPvcSmplHCFrOfferedC, 2621 frsldPvcSmplHCFrOfferedE 2622 } 2623 STATUS current 2624 DESCRIPTION 2625 "A collection of optional objects providing high 2626 capacity frame delivery sample data collected on a PVC 2627 which implements Service Level Definitions. 2629 If this group is implemented, frsldPvcHCFrameDataGroup 2630 MUST also be implemented." 2631 ::= { frsldMIBGroups 11 } 2633 frsldPvcSampleHCDataGroup OBJECT-GROUP 2634 OBJECTS { 2635 frsldPvcSmplHCDataDeliveredC, 2636 frsldPvcSmplHCDataDeliveredE, 2637 frsldPvcSmplHCDataOfferedC, 2638 frsldPvcSmplHCDataOfferedE 2639 } 2640 STATUS current 2641 DESCRIPTION 2642 "A collection of optional objects providing high 2643 capacity data delivery sample data collected on a PVC 2644 which implements Service Level Definitions. 2646 If this group is implemented, frsldPvcHCOctetDataGroup 2647 MUST also be implemented." 2648 ::= { frsldMIBGroups 12 } 2650 frsldPvcSampleAvailGroup OBJECT-GROUP 2651 OBJECTS { 2652 frsldPvcSmplUnavailableTime, 2653 frsldPvcSmplUnavailables 2654 } 2655 STATUS current 2656 DESCRIPTION 2657 "A collection of optional objects providing 2658 availability sample data collected on a PVC which 2659 implements Service Level Definitions. 2661 If this group is implemented, frsldPvcReqDataGroup 2662 MUST also be implemented." 2663 ::= { frsldMIBGroups 13 } 2665 frsldPvcSampleGeneralGroup OBJECT-GROUP 2666 OBJECTS { 2667 frsldPvcSmplStartTime, 2668 frsldPvcSmplEndTime 2669 } 2670 STATUS current 2671 DESCRIPTION 2672 "A collection of optional objects providing 2673 general sample data collected on a PVC which 2674 implements Service Level Definitions." 2675 ::= { frsldMIBGroups 14 } 2677 frsldCapabilitiesGroup OBJECT-GROUP 2678 OBJECTS { 2679 frsldPvcCtrlWriteCaps, 2680 frsldSmplCtrlWriteCaps, 2681 frsldRPCaps, 2682 frsldMaxPvcCtrls, 2683 frsldNumPvcCtrls, 2684 frsldMaxSmplCtrls, 2685 frsldNumSmplCtrls 2686 } 2687 STATUS current 2688 DESCRIPTION 2689 "A collection of required objects providing 2690 capability information and control for this 2691 MIB module." 2692 ::= { frsldMIBGroups 15 } 2693 END 2695 7. Acknowledgments 2697 This document was produced by the Frame Relay Service MIB Working 2698 Group. It is based on the Frame Relay Forum's implementation 2699 agreement on service level definitions, FRF.13 [17]. 2701 The editors would like to thank the following people for their 2702 helpful comments: 2704 o Ken Rehbehn, Visual Networks 2706 o Santa Dasu, Quick Eagle Networks 2708 8. References 2710 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2711 Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, 2712 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2714 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2715 Management Information for TCP/IP-based Internets", RFC 1155, STD 2716 16, Performance Systems International, Hughes LAN Systems, May 1990 2718 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2719 STD 16, Performance Systems International, Hughes LAN Systems, March 2720 1991 2722 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2723 RFC 1215, Performance Systems International, March 1991 2725 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2726 and S. Waldbusser, "Structure of Management Information Version 2 2727 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 2728 Braunschweig, SNMP Research, First Virtual Holdings, International 2729 Network Services, April 1999 2731 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2732 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 2733 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2734 Virtual Holdings, International Network Services, April 1999 2736 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2737 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 2738 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2739 Virtual Holdings, International Network Services, April 1999 2741 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2742 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 2743 Systems International, Performance Systems International, MIT 2744 Laboratory for Computer Science, May 1990. 2746 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction 2747 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 2748 Systems, Inc., Dover Beach Consulting, Inc., International Network 2749 Services, January 1996. 2751 [10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2752 Mappings for Version 2 of the Simple Network Management Protocol 2753 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 2754 Beach Consulting, Inc., International Network Services, January 2755 1996. 2757 [11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2758 Processing and Dispatching for the Simple Network Management 2759 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 2760 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2762 [12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2763 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2764 2574, IBM T. J. Watson Research, April 1999 2766 [13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2767 Operations for Version 2 of the Simple Network Management Protocol 2768 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 2769 Beach Consulting, Inc., International Network Services, January 2770 1996. 2772 [14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2773 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2774 Systems, April 1999 2776 [15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2777 Control Model (VACM) for the Simple Network Management Protocol 2778 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 2779 Cisco Systems, Inc., April 1999 2781 [16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2782 Version 3 of the Internet-standard Network Management Framework", 2783 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 2784 Ericsson, Cisco Systems, April 1999 2786 [17]Frame Relay Forum Technical Committee, "Service Level Definitions 2787 Implementations Agreement", FRF.13, August 1998. 2789 [18]Brown, T., "Definitions of Managed Objects for Frame Relay Service", 2790 RFC 1604, Bell Communications Research, March 1994. 2792 [19]Waldbusser, S., "Remote Network Monitoring Management Information 2793 Base Version 2 using SMIv2", RFC 2021, International Network 2794 Service, January 1997. 2796 [20]Brown, C., Baker, F., "Management Information Base for Frame Relay 2797 DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, 2798 September 1997. 2800 [21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC 2801 2863, Cisco Systems, Argon Networks, June 2000. 2803 9. Security Considerations 2805 There are a number of management objects defined in this MIB that 2806 have a MAX-ACCESS clause of read-write and/or read-create. Such 2807 objects may be considered sensitive or vulnerable in some network 2808 environments. The support for SET operations in a non-secure 2809 environment without proper protection can have a negative effect on 2810 network operations. 2812 SNMPv1 by itself is not a secure environment. Even if the network 2813 itself is secure (for example by using IPSec), even then, there is no 2814 control as to who on the secure network is allowed to access and 2815 GET/SET (read/change/create/delete) the objects in this MIB. 2817 It is recommended that the implementers consider the security 2818 features as provided by the SNMPv3 framework. Specifically, the use 2819 of the User-based Security Model RFC 2274 [12] and the View-based 2820 Access Control Model RFC 2275 [15] is recommended. 2822 It is then a customer/user responsibility to ensure that the SNMP 2823 entity giving access to an instance of this MIB, is properly 2824 configured to give access to the objects only to those principals 2825 (users) that have legitimate rights to indeed GET or SET 2826 (change/create/delete) them. 2828 10. Authors' Addresses 2830 Robert Steinberger 2831 Fujitsu Network Communications 2832 2801 Telecom Parkway 2833 Richardson, TX 75082 2835 Phone: 1-972-479-4739 2837 Email: robert.steinberger@fnc.fujitsu.com 2839 Orly Nicklass, Ph.D 2840 RAD Data Communications Ltd. 2841 12 Hanechoshet Street 2842 Tel Aviv, Israel 69710 2844 Phone: 972 3 7659969 2846 Email: Orly_n@rrad.co.il 2848 11. Copyright Section 2850 Copyright (C) The Internet Society (2000). All Rights Reserved. 2852 This document and translations of it may be copied and furnished to 2853 others, and derivative works that comment on or otherwise explain it 2854 or assist in its implementation may be prepared, copied, published 2855 and distributed, in whole or in part, without restriction of any 2856 kind, provided that the above copyright notice and this paragraph are 2857 included on all such copies and derivative works. However, this 2858 document itself may not be modified in any way, such as by removing 2859 the copyright notice or references to the Internet Society or other 2860 Internet organizations, except as needed for the purpose of 2861 developing Internet standards in which case the procedures for 2862 copyrights defined in the Internet Standards process must be 2863 followed, or as required to translate it into languages other than 2864 English. 2866 The limited permissions granted above are perpetual and will not be 2867 revoked by the Internet Society or its successors or assigns. 2869 This document and the information contained herein is provided on an 2870 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2871 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2872 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2873 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2874 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.