idnits 2.17.1 draft-ietf-frnetmib-frmrelay-service-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 142: '... The keywords MUST, MUST NOT, REQUIR...' RFC 2119 keyword, line 143: '... SHOULD NOT, RECOMMENDED, NOT RECOMM...' RFC 2119 keyword, line 257: '...erence points which MAY exist anywhere...' RFC 2119 keyword, line 415: '...monitoring point MAY be implemented in...' RFC 2119 keyword, line 424: '...monitoring point MAY be restricted to ...' (23 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 972 has weird spacing: '...(1) and frCir...' == Line 2610 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 (December 19, 2000) is 8528 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 2568, 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 2569, 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 2451, but not defined == Missing Reference: '18' is mentioned on line 982, but not defined == Missing Reference: '19' is mentioned on line 758, but not defined == Missing Reference: '20' is mentioned on line 961, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') Summary: 10 errors (**), 0 flaws (~~), 17 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 December 19, 2000 6 draft-ietf-frnetmib-frmrelay-service-03.txt 8 Robert A. Steinberger 9 Paradyne Networks 10 rsteinberger@paradyne.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. This memo does not specify a 41 standard for the Internet community. 43 Copyright Notice 45 Copyright (C) The Internet Society (2001). All Rights Reserved. 47 Table of Contents 49 1. The SNMP Management Framework ............................... 3 50 2. Conventions ................................................. 4 51 3. Overview .................................................... 4 52 3.1. Frame Relay Service Level Definitions ..................... 4 53 3.2. Terminology ............................................... 5 54 3.3. Network Model ............................................. 5 55 3.4. Reference Points .......................................... 6 56 3.5. Measurement Methodology ................................... 8 57 3.6. Theory of Operation ....................................... 9 58 3.6.1. Capabilities Discovery .................................. 9 59 3.6.2. Determining Reference Points for Row Creation ........... 9 60 3.6.2.1. Graphical Examples of Reference Points ................ 11 61 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example ...... 12 62 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example ... 13 63 3.6.2.1.3. End-to-End Using Reference Point Example ............ 14 64 3.6.3. Creation Process ........................................ 15 65 3.6.4. Destruction Process ..................................... 15 66 3.6.4.1. Manual Row Destruction ................................ 15 67 3.6.4.2. Automatic Row Destruction ............................. 16 68 3.6.5. Modification Process .................................... 16 69 3.6.6. Collection Process ...................................... 16 70 3.6.6.1. Remote Polling ........................................ 16 71 3.6.6.2. Sampling .............................................. 17 72 3.6.6.3. User History .......................................... 17 73 3.6.7. Use of MIB in Calculation of Service Level 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 MIBs ...................................... 22 79 5. Structure of the MIB ........................................ 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 ............................................. 53 87 8. References .................................................. 54 88 9. Security Considerations ..................................... 56 89 10. Authors' Addresses ......................................... 56 90 11. Copyright Section .......................................... 57 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 addresses the items required to manage the Frame Relay 150 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. 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. 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 are shown in figure 2 below. For completeness, the MIB 257 also allows for proprietary reference points which MAY exist anywhere 258 in the network that is not a previously defined reference point. The 259 meaning of the proprietary reference points is insignificant unless 260 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 apply to 316 the interaction of a pair of devices on the network path. The same 317 device can potentially use different reference points for calculation 318 and collection of the statistics based on whether the referenced 319 frame is sent or received by the device. When the device is acting as 320 a frame source, the value of frsldPvcCtrlTransmitRP reflects the 321 reference point used for all source calculations pertaining to the 322 specified PVC. When the device is acting as a frame destination, the 323 value of frsldPvcCtrlReceiveRP reflects the reference point used for 324 all destination calculations pertaining to the specified PVC. 326 For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue 327 measurement domain as a domain in which measurement is performed 328 between an Ingress Reference Point and an Egress Queue Input 329 Reference Point. For this domain between a source device and a 330 destination device, the value of frsldPvcCtrlTransmitRP for the 331 source device would be set to ingTxLocalRP(2) and the value of 332 frsldPvcCtrlReceiveRP for the destination device would be set to 333 eqiRxLocalRP(4). While it is usually the case that the reference 334 points would be equivalent on the remote device when monitoring 335 frames going in the opposite direction, there is no requirement for 336 them to be so. 338 It can be seen from the above example that a total of four reference 339 points are required in order to collect information for both 340 directions of traffic flow. The reference points represent the 341 transmit and receive directions at both ends of a PVC. If a device 342 has knowledge of the information from the remote device, it is 343 possible to collect the statistics from a single device. This is not 344 always the case. In most instances, two devices will need to be 345 monitored to capture a complete description of the service level on a 346 PVC. The reference points a single device is capable of monitoring 347 are contained in the frsldRPCaps object. 349 3.5. Measurement Methodology 351 This document neither recommends nor suggests a method of 352 implementation. This is left to the device manufacturer and should be 353 independent of the data that is actually collected. 355 Periodic collection of this data can be performed through either 356 polling of the data table, use of the sample tables or use of the 357 user history group of RFC 2021 [19]. 359 3.6. Theory of Operation 361 The following sections describe how to use this MIB. They include 362 row handling, data collection and data calculation. The 363 recommendations here in are suggestions as to implementation and do 364 not infer that they are the only method that can be used to perform 365 such operations. 367 3.6.1. Capabilities Discovery 369 Three objects are provided to aid the network manager in discovering 370 the capabilities of the device with respect to this MIB. 372 o frsldPvcCtrlWriteCaps This object reports the write capabilities 373 of the PVC Control Table. Use this object 374 to determine which objects can be modified. 375 This need only be referenced if row 376 creation or modification is to be 377 performed. 379 o frsldSmplCtrlWriteCaps This object reports the write capabilities 380 of the Sample Control Table. Use this 381 object to determine which objects can be 382 modified. The group need only be 383 referenced if the sample tables will be 384 used to collect historical information. 386 o frsldRPCaps This object reports the reference points at 387 which the device is capable of collecting 388 information. This object needs to be 389 referenced if row creation is to be 390 performed in the PVC Control Table. 391 Devices can only create rows containing 392 supported reference points. 394 These objects do not imply that there is no need for an Agent 395 Capabilities macro for devices that do not fully support every object 396 in this MIB. They are provided specifically to aid in the ensured 397 network management operations of this MIB with respect to row 398 creation and modification. 400 3.6.2. Determining Reference Points for Row Creation 402 The performance of a PVC is monitored by evaluating the uni- 403 directional flow of frames from an ingress point to an egress point. 404 Reference points describe where each of the two measurements are 405 made. Monitoring both of the uni-directional flows that make-up the 406 PVC frame traffic requires a total of four reference points as shown 407 in Figures 3 through 5. A monitoring point that evaluates traffic is 408 restricted to counting frames that pass the reference points hosted 409 locally on the monitoring point. Thus, if the monitoring point is 410 near the ingress point of the flow, it will count the frames entering 411 into the frame relay network. The complete picture of frame loss for 412 the uni-directional flow requires information from the downstream 413 reference point located at another (remote) monitoring point. 415 The local monitoring point MAY be implemented in such way that the 416 information from the downstream monitoring point is moved to the 417 local monitoring point using implementation-specific mechanisms. In 418 this case all information required to calculate frame loss becomes 419 available from the local measurement point. The local measurement 420 point agent is capable of reporting all the objects in the 421 FrsldPvcDataEntry row - the counts for offered frames entering the 422 network and delivered frames exiting the network. 424 Alternatively, the local monitoring point MAY be restricted to counts 425 of frames observed on the local device only. In this case, the 426 objects of the FrsldPvcDataEntry row reporting what happened on the 427 remote device are not available. 429 The following list shows the possible valid reference points for an 430 FRF.13 SLA from the source reference point to the destination 431 reference point in both directions. 433 o Local Information Only 435 Local Device: srcLocalRP, desLocalRP 436 Remote Device: srcLocalRP, desLocalRP 438 o Remote Information Only 440 Local Device: srcRemoteRP, desRemoteRP 441 Remote Device: srcRemoteRP, desRemoteRP 443 o Mixed Two Device Model 1 (Local Device Always Transmitter) 445 Local Device: srcLocalRP, desRemoteRP 446 Remote Device: srcLocalRP, desRemoteRP 448 o Mixed Two Device Model 2 (Local Device Always Receiver) 450 Local Device: srcRemoteRP, desLocalRP 451 Remote Device: srcRemoteRP, desLocalRP 453 o Mixed One Device Model 1 (Directional Rows) 455 First Row: srcRemoteRP, desLocalRP (Receiver Row) 456 Second Row: srcLocalRP, desRemoteRP (Sender Row) 458 o Mixed One Device Model 2 (Device Based Rows) 460 First Row: srcLocalRP, desLocalRP (Local Row) 461 Second Row: srcRemoteRP, desRemoteRP (Remote Row) 463 Each of the above combinations is valid and provides the same 464 information. 466 The following steps are recommended to find which reference points 467 need to be configured: 469 1) Locate both of the devices at either end of the PVC to be 470 monitored. 472 2) Determine the capabilities by referencing the frsldRPCaps object 473 of each device. 475 3) Locate the best combination of the two devices such that the 476 necessary reference points are all represented. 478 4) If any one of the necessary reference points does not exist in 479 the combination of the two devices, it is not possible to 480 monitor the FRF.13 defined SLA between the two reference point 481 on the PVC. 483 3.6.2.1. Graphical Examples of Reference Points 485 FRF.13 [17] defines three specific combinations of reference points: 486 Edge-to-Edge Interface, Edge-to-Edge Egress Queue and End-to-End. 487 Examples of valid reference points that may be used for each of these 488 are discussed in the sections below. 490 It is often the case that a device knows as a minimum either only 491 local information or both local and remote information. Because 492 these are two common examples, each will be illustrated below. 494 3.6.2.1.1. Edge-to-Edge Interface Reference Point Example 496 Device 1 Device 2 497 +-------------+ +-------------+ 498 | Ingress | | Egress | 499 | +-----+ | | +-----+ | 500 |(A)| | | Traffic Flow | | |(B)| 501 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 502 | | | | From Device 1 to 2 | | | | 503 | +-----+ | | +-----+ | 504 | | | | 505 | Egress | | Ingress | 506 | +-----+ | | +-----+ | 507 |(D)| | | Traffic Flow | | |(C)| 508 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 509 | | | | From Device 2 to 1 | | | | 510 | +-----+ | | +-----+ | 511 +-------------+ +-------------+ 513 where (A), (B), (C) and (D) are reference points 515 Figure 3 517 For devices with only local knowledge, one row is required on each 518 device as follows: 520 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 522 (B) frsldPvcCtlrReceiveRP for Device 2 = eqoRxLocalRP(5) 524 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 526 (D) frsldPvcCtlrReceiveRP for Device 1 = eqoRxLocalRP(5) 528 In which a single row is created on Device 1 containing reference 529 points (A) and (D), and a single row is created on Device 2 530 containing reference points (C) and (B). 532 For devices with both local and remote knowledge, the two rows can 533 exist in any combination on either device. For this example, the 534 transmitting devices will be responsible for information regarding 535 the flow for which they are the origin. Only one row is required per 536 device for this example. 538 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 539 (B) frsldPvcCtlrReceiveRP for Device 1 = eqoRxRemoteRP(11) 541 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 543 (D) frsldPvcCtlrReceiveRP for Device 2 = eqoRxRemoteRP(11) 545 3.6.2.1.2. Edge-to-Edge Egress Queue Reference Point Example 547 Device 1 Device 2 548 +-------------+ +-------------+ 549 | Ingress | | Egress | 550 | +-----+ | | +-----+ | 551 |(A)| | | Traffic Flow |(B)| | | 552 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 553 | | | | From Device 1 to 2 | | | | 554 | +-----+ | | +-----+ | 555 | | | | 556 | Egress | | Ingress | 557 | +-----+ | | +-----+ | 558 | | |(D)| Traffic Flow | | |(C)| 559 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 560 | | | | From Device 2 to 1 | | | | 561 | +-----+ | | +-----+ | 562 +-------------+ +-------------+ 564 where (A), (B), (C) and (D) are reference points 566 Figure 4 568 For devices with only local knowledge, one row is required on each 569 device as follows: 571 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 573 (B) frsldPvcCtlrReceiveRP for Device 2 = eqiRxLocalRP(4) 575 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 577 (D) frsldPvcCtlrReceiveRP for Device 1 = eqiRxLocalRP(4) 579 In which a single row is created on Device 1 containing reference 580 points (A) and (D), and a single row is created on Device 2 581 containing reference points (C) and (B). 583 For devices with both local and remote knowledge, the two rows can 584 exist in any combination on either device. For this example, the 585 transmitting devices will be responsible for information regarding 586 the flow for which they are the origin. Only one row is required per 587 device for this example. 589 (A) frsldPvcCtrlTransmitRP for Device 1 = ingTxLocalRP(2) 591 (B) frsldPvcCtlrReceiveRP for Device 1 = eqiRxRemoteRP(10) 593 (C) frsldPvcCtrlTransmitRP for Device 2 = ingTxLocalRP(2) 595 (D) frsldPvcCtlrReceiveRP for Device 2 = eqiRxRemoteRP(10) 597 3.6.2.1.3. End-to-End Using Reference Point Example 599 Device 1 Device 2 600 +-------------+ +-------------+ 601 | Source | | Destination | 602 | +-----+ | | +-----+ | 603 |(A)| | | Traffic Flow | | |(B)| 604 -->-->-- -->-->-->-->-->-->-->-->-->-->-->- -->-->--> 605 | | | | From Device 1 to 2 | | | | 606 | +-----+ | | +-----+ | 607 | | | | 608 | Destination | | Source | 609 | +-----+ | | +-----+ | 610 |(D)| | | Traffic Flow | | |(C)| 611 <--<--<- -<--<--<--<--<--<--<--<--<--<--<-- --<--<-- 612 | | | | From Device 2 to 1 | | | | 613 | +-----+ | | +-----+ | 614 +-------------+ +-------------+ 616 where (A), (B), (C) and (D) are reference points 618 Figure 5 620 For devices with only local knowledge, one row is required on each 621 device as follows: 623 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 625 (B) frsldPvcCtlrReceiveRP for Device 2 = desLocalRP(1) 627 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 629 (D) frsldPvcCtlrReceiveRP for Device 1 = desLocalRP(1) 630 In which a single row is created on Device 1 containing reference 631 points (A) and (D), and a single row is created on Device 2 632 containing reference points (C) and (B). 634 For devices with both local and remote knowledge, the two rows can 635 exist in any combination on either device. For this example, the 636 transmitting devices will be responsible for information regarding 637 the flow for which they are the origin. Only one row is required per 638 device for this example. 640 (A) frsldPvcCtrlTransmitRP for Device 1 = srcLocalRP(1) 642 (B) frsldPvcCtlrReceiveRP for Device 1 = desRemoteRP(7) 644 (C) frsldPvcCtrlTransmitRP for Device 2 = srcLocalRP(1) 646 (D) frsldPvcCtlrReceiveRP for Device 2 = desRemoteRP(7) 648 3.6.3. Creation Process 650 In some cases, devices will automatically populate the rows of PVC 651 Control Table and potentially the Sample Control Table. However, in 652 many cases, it may be necessary for a network manager to manually 653 create rows. 655 Manual creation of rows requires the following steps: 657 1) Ensure the PVC exists between the two devices. 659 2) Determine the necessary reference points for row creation. 661 3) Create the row(s) in each device as needed. 663 4) Create the row(s) in the sample control tables if desired. 665 3.6.4. Destruction Process 667 3.6.4.1. Manual Row Destruction 669 Manual row destruction is straight forward. Any row can be destroyed 670 and the resources allocated to it are freed by setting the value of 671 its status object (either frsldPvcCtrlStatus or frsldSmplCtrlStatus) 672 to destroy(6). It should be noted that when frsldPvcCtrlStatus is 673 set to destroy(6) all associated sample control, sample and data 674 table rows will also be destroyed. Similarly, when 675 frsldSmplCtrlStatus is set to destroy(6) all sample rows will also be 676 destroyed. The frsldPvcCtrlPurge objects do not apply to manual row 677 destruction. If the row is set to destroy(6) manually, the rows are 678 destroyed as part of the set. 680 3.6.4.2. Automatic Row Destruction 682 Rows is the tables may be destroyed automatically based on the 683 existence of the DLCI on which they rely. This behavior is 684 controlled by the frsldPvcCtrlPurge and frsldPvcCtrlDeleteOnPurge 685 objects. When a DLCI no longer exists in the device, the data in the 686 tables has no relation to anything known on the network. However, 687 there may be some need to keep the historic information active for a 688 short period after the destruction or removal of a DLCI. If the 689 basis for the row no longer exists, the row will be destroyed at the 690 end of the purge interval that is controlled by frsldPvcCtrlPurge. 692 The effects of automatic row destruction are the same as manual row 693 destruction. 695 3.6.5. Modification Process 697 All read-create items in this MIB can be modified at any time if they 698 are fully supported. Write access is not required. To simplify the 699 use of the MIB frsldPvcCtrlWriteCaps and frsldSmplCtrlWriteCaps state 700 which of the read-create variables can actually be written on a 701 particular device. 703 3.6.6. Collection Process 705 3.6.6.1. Remote Polling 707 This MIB supports data collection through remote polling of the free 708 running counters in the PVC Data Table. Remote polling is a common 709 method used to capture real-time statistics. A remote management 710 station polls the device to collect the desired information. It is 711 recommended all statistics for a single PVC be collected in a single 712 PDU. 714 The following objects are designed around the concept of real-time 715 polling: 717 o frsldPvcDataMissedPolls 718 o frsldPvcDataFrDeliveredC 719 o frsldPvcDataFrDeliveredE 720 o frsldPvcDataFrOfferedC 721 o frsldPvcDataFrOfferedE 722 o frsldPvcDataDataDeliveredC 723 o frsldPvcDataDataDeliveredE 724 o frsldPvcDataDataOfferedC 725 o frsldPvcDataDataOfferedE 726 o frsldPvcDataHCFrDeliveredC 727 o frsldPvcDataHCFrDeliveredE 728 o frsldPvcDataHCFrOfferedC 729 o frsldPvcDataHCFrOfferedE 730 o frsldPvcDataHCDataDeliveredC 731 o frsldPvcDataHCDataDeliveredE 732 o frsldPvcDataHCDataOfferedC 733 o frsldPvcDataHCDataOfferedE 734 o frsldPvcDataUnavailableTime 735 o frsldPvcDataUnavailables 737 3.6.6.2. Sampling 739 The sample tables provide the ability to historically sample data 740 without requiring the additional overhead of polling. At key 741 periods, a network management station can collect the samples needed. 742 This method allows the manager to perform the collection of data at 743 times that will least affect the active network traffic. 745 The sample data can be collected using a series of SNMP getNext or 746 getBulk operations. The value of frsldPvcSmplIdx increments with 747 each new collection bucket. This allows the managers to skip 748 information that has already been collected. However, care should be 749 taken in that the value can roll over after a long period of time. 751 The start and end times of a collection period allow the manager to 752 know what the actual period of collection was. It is possible for 753 there to be discontinuities in the sample table, so both start and 754 end should be referenced. 756 3.6.6.3. User History 758 User history, as defined in RFC 2021 [19], is an alternative 759 mechanism that can be used to get the same benefits as the sample 760 table by using the objects provided for real-time polling. Some 761 devices MAY have the ability to use user history and opt not to 762 support the sample tables. If this is the case, the information from 763 the data table can be used to define a group of user history objects. 765 3.6.7. Use of MIB in Calculation of Service Level Definitions 767 The objects in this MIB can be used to calculate the statistics 768 defined in FRF.13 [17]. The description below describes the 769 calculations for one direction of the data flow, i.e. data sent from 770 local transmitter to a remote receiver. A complete set of 771 bidirectional information would require calculations based on both 772 directions. For the purposes of this description, the reference 773 points used SHOULD consistently represent data that is sent by one 774 device and received by the other. 776 A complete evaluation requires the combination of two uni-directional 777 flows. It is possible for a management station to combine all of the 778 calculated information into one conceptual row. Doing this requires 779 that each of the metrics are collected for both flow directions and 780 grouped by direction If the information is split between two 781 devices, the management station must know which two devices to 782 communicate with for the collection of all information. The grouping 783 of information SHOULD be from ingress to egress in each flow 784 direction. 786 The calculations below use the following terminology: 788 o DelayAvg 790 The average delay on the PVC. This is represented within the 791 MIB by frsldPvcSmplDelayAvg. 793 o FrDeliveredC 795 The number of frames received by the receiving device through 796 the receive reference point that were delivered within CIR. 797 This is represented within the MIB by one of 798 frsldPvcDataFrDeliveredC, frsldPvcDataHCFrDeliveredC, 799 frsldPvcSmplFrDeliveredC, or frsldPvcSmplHCFrDeliveredC. 801 o FrDeliveredE 803 The number of frames received by the receiving device through 804 the receive reference point that were delivered in excess of 805 CIR. This is represented within the MIB by one of 806 frsldPvcDataFrDeliveredE, frsldPvcDataHCFrDeliveredE, 807 frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE. 809 o FrOfferedC 810 The number of frames offered by the transmitting device through 811 the transmit reference point that were sent within CIR. This is 812 represented within the MIB by one of frsldPvcDataFrOfferedC, 813 frsldPvcDataHCFrOfferedC, frsldPvcSmplFrOfferedC, or 814 frsldPvcSmplHCFrOfferedC. 816 o FrOfferedE 818 The number of frames offered by the transmitting device through 819 the transmit reference point that were sent in excess of CIR. 820 This is represented within the MIB by one of 821 frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE, 822 frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE. 824 o DataDeliveredC 826 The number of octets received by the receiving device through 827 the receive reference point that were delivered within CIR. 828 This is represented within the MIB by one of 829 frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC, 830 frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC. 832 o DataDeliveredE 834 The number of octets received by the receiving device through 835 the receive reference point that were delivered in excess of 836 CIR. This is represented within the MIB by one of 837 frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE, 838 frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE. 840 o DataOfferedC 842 The number of octets offered by the transmitting device through 843 the transmit reference point that were sent within CIR. This is 844 represented within the MIB by one of frsldPvcDataDataOfferedC, 845 frsldPvcDataHCDataOfferedC, frsldPvcSmplDataOfferedC, or 846 frsldPvcSmplHCDataOfferedC. 848 o DataOfferedE 850 The number of octets offered by the transmitting device through 851 the transmit reference point that were sent in excess of CIR. 852 This is represented within the MIB by one of 853 frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE, 854 frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE. 856 o UnavailableTime 857 The amount of time the PVC was not available during the interval 858 of interest. This is represented within the MIB by either 859 frsldPvcDataUnavailableTime or frsldPvcSmplUnavailableTime. 861 o Unavailables 863 The number of times the PVC was declared to be unavailable 864 during the interval of interest. This is represented within the 865 MIB by either frsldPvcDataUnavailables or 866 frsldPvcSmplUnavailables. 868 3.6.8. Delay 870 The frame transfer delay is defined as the amount of time elapsed, in 871 microseconds, from the time a frame exits the source to the time it 872 reaches the destination. The average delay can be found using the MIB 873 variable described in DelayAvg above. The delay may be calculated as 874 either round trip or one way, and this information is held in the 875 frsldPvcCtrlDelayType MIB variable. If the delay be calculated as 876 round trip, the value of DelayAvg represents the average of the total 877 delays of the round trips. In this case, the manager SHOULD divide 878 the value returned by the agent by two to obtain the frame transfer 879 delay. In the case that frsldPvcCtrlDelayType is oneWay, the value 880 of DelayAvg represents the average of the frame transfer delays and 881 SHOULD be used as is. 883 3.6.9. Frame Delivery Ratio 885 The frame delivery ratio is defined as the total number of frames 886 delivered to the destination divided by the frames offered by the 887 source. The destination values can be obtained using FrDeliveredC 888 and FrDeliveredE. The source values can be obtained using FrOfferedC 889 and FrOfferedE. 891 FrDeliveredC + FrDeliveredE 892 Frame Delivery Ratio = --------------------------- 893 FrOfferedC + FrOfferedE 895 FrDeliveredC 896 Committed Frame Delivery Ratio = ------------ 897 FrOfferedC 899 FrDeliveredE 900 Excess Frame Delivery Ratio = ------------ 901 FrOfferedE 903 3.6.10. Data Delivery Ratio 905 The data delivery ratio is defined as the total amount of data 906 delivered to the destination divided by the data offered by the 907 source. The destination values can be obtained using DataDeliveredC 908 and DataDeliveredE. The source values can be obtained using 909 DataOfferedC and DataOfferedE. 911 DataDeliveredC + DataDeliveredE 912 Data Delivery Ratio = ------------------------------- 913 DataOfferedC + DataOfferedE 915 DataDeliveredC 916 Committed Data Delivery Ratio = -------------- 917 DataOfferedC 919 DataDeliveredE 920 Excess Data Delivery Ratio = -------------- 921 DataOfferedE 923 3.6.11. Service Availability 925 Some forms of service availability measurement defined in FRF.13 [17] 926 require knowledge of the amount of time the network is allowed to be 927 unavailable during the period of measurement. This is called the 928 excluded outage time and will be represented in the measurements 929 below as ExcludedTime. It is assumed that the management software 930 will maintain this information in that it often relates to specific 931 times and dates that many devices are not capable of maintaining. 932 Further, it may change based on a moving maintenance window that the 933 device cannot track well. 935 Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0. 937 UnavailableTime 938 Otherwise, FRMTTR = --------------- 939 Unavailables 941 Virtual Connection Availability (FRVCA) = 0 if IntervalTime equals 942 ExcludedTime. 944 IntervalTime - ExcludedTime - UnavailableTime 945 Otherwise, FRVCA = --------------------------------------------- *100 946 IntervalTime - ExcludedTime 948 Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0. 950 Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime 951 --------------------------------------------- 952 Unavailables 954 4. Relation to Other MIBs 956 There is no explicit relation to any other frame relay MIB nor are 957 any required to implement this MIB. However, there is a need for 958 knowledge of ifIndexes and some understanding of DLCIs. The ifIndex 959 information can be found in the IF-MIB which is required. The DLCI 960 information can be found in either the Frame Relay DTE MIB (RFC 2115) 961 [20] or the Frame Relay Network Services MIB (RFC 1604) [18]; 962 however, neither is required. 964 Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to 965 active(1) the system can be in one of the following three states: 967 (1) The respective DLCI is known and is active. This corresponds to a 968 state in which frPVCEndptRowStatus is active(1) and 969 frPVCEndptRcvdSigStatus is either active(2) or none(4) for the 970 Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame 971 Relay DTE MIB, the same state is shown by frCircuitRowStatus of 972 active(1) and frCircuitState of active(2). 974 (2) The respective DLCI has not been created. This corresponds to a 975 state in which the row with either frPVCEndptDLCIIndex or 976 frCircuitDlci equal to the respective DLCI does not exist in 977 either the frPVCEndptTable or the frCircuitTable respectively. 979 (3) The respective DLCI has just been removed. This corresponds to a 980 state in which either frPVCEndptRowStatus is no longer active(1) 981 or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for 982 the Frame Relay Network Services MIB (RFC 1604) [18]. For the 983 Frame Relay DTE MIB, the same state is shown when either 984 frCircuitRowStatus is no longer active(1) or frCircuitState is no 985 longer active(2). 987 For the first case, the row in the frsldPvcDataTable will be filled. 988 If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective 989 DLCI is also `active' the frsldPvcSampleTable will be filled as well. 991 For the second case, the respective rows will not be added to any of 992 the data or sample tables and frsldPvcCtrlStatus SHOULD be set to 993 notReady(3). 995 For the third case, frsldPvcCtrlDeleteOnPurge should direct the 996 behavior of the system. If all tables are purged, this case will be 997 equivalent to the second case above. Otherwise, frsldPvcCtrlStatus 998 SHOULD remain active(1). 1000 5. Structure of the MIB 1002 The FRSLD-MIB consists of the following components: 1004 o frsldPvcCtrlTable 1006 o frsldSmplCtrlTable 1008 o frsldPvcDataTable 1010 o frsldPvcSampleTable 1012 o frsldCapabilities 1014 Refer to the compliance statement defined within for a definition of 1015 what objects MUST be implemented. 1017 5.1. frsldPvcCtrlTable 1019 The frsldPvcCtrlTable is the central control table for operations of 1020 the Frame Relay Service Level Definitions MIB. It provides variables 1021 to control the parameters required to calculate the objects in the 1022 other tables. 1024 A row in this table MUST exist in order for a row to exist in any 1025 other table in this MIB. 1027 5.2. frsldSmplCtrlTable 1029 This is an optional table to allow control of sampling of the data in 1030 the data table. 1032 5.3. frsldPvcDataTable 1034 This table contains the calculated data. It relies on configuration 1035 from the control table. 1037 5.4. frsldPvcSampleTable 1039 This table contains samples of the delivery and availability 1040 information from the data table as well as delay information 1041 calculated over the sample period. It relies on configuration from 1042 both the control table and the sample control table. 1044 5.5. frsldCapabilities 1046 This is a group of objects that define write capabilities of the 1047 read-create objects in the tables above. 1049 6. Object Definitions 1051 FRSLD-MIB DEFINITIONS ::= BEGIN 1053 IMPORTS 1054 MODULE-IDENTITY, OBJECT-TYPE, 1055 Counter32, Gauge32, Integer32, 1056 Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI 1057 CounterBasedGauge64 FROM HCNUM-TC 1058 RowStatus, TimeStamp FROM SNMPv2-TC 1059 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1060 ifIndex FROM IF-MIB; 1062 frsldMIB MODULE-IDENTITY 1063 LAST-UPDATED "200009191500Z" -- September 19, 2000 1064 ORGANIZATION "IETF Frame Relay Service MIB Working Group" 1065 CONTACT-INFO 1066 "IETF Frame Relay Service MIB (frnetmib) Working Group 1068 WG Charter: http://www.ietf.org/html.charters/ 1069 frnetmib-charter.html 1070 WG-email: frnetmib@sunroof.eng.sun.com 1071 Subscribe: frnetmib-request@sunroof.eng.sun.com 1072 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 1074 Chair: Andy Malis 1075 Lucent Technologies 1076 Email: amalis@lucent.com 1078 WG editor: Robert Steinberger 1079 Paradyne Networks 1080 Email: rsteinberger@paradyne.com 1082 Co-author: Orly Nicklass 1083 RAD Data Communications Ltd. 1084 EMail: Orly_n@rad.co.il" 1085 DESCRIPTION 1086 "The MIB module to describe generic objects for 1087 FRF.13 Frame Relay Service Level Definitions." 1088 REVISION "200009191500Z" 1089 DESCRIPTION 1090 "o Removed frsldPvcCtrlDelayCnt. 1091 o Removed frsldSmplCtrlAvailColPeriod, frsdlSmplCtrl- 1092 AvailBuckets, and frsldSmplCtrlAvailBucketsGranted. 1093 o Changed name of frsldSmplCtrlData* to frsldSmplCtrl*. 1094 o Removed frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1095 and frsldPvcDataDelayAvg. 1096 o Changed frsldPvcDataSample* to frsldPvcSample*. 1097 o Changed frsldPvcDataSmpl* to frsldPvcSmpl*. 1098 o Added frsldPvcSmplUnavailableTime and frsldPvcSmpl- 1099 Unavailables. 1100 o Removed frsldPvcAvailSampleTable and all objects. 1101 o Removed frsldPvcCtrlDelayCnt from frsldPvcCtrlWrite- 1102 Caps. 1103 o Adjusted group definitions for frsldPvcDelayCtrlGroup, 1104 frsldPvc[Data]SampleCtrlGroup, frsldPvcReqDataGroup, 1105 frsldPvcDelayDataGroup, and frsldPvc[Avail]SampleAvail- 1106 Group to reflect above changes." 1107 REVISION "200006141500Z" 1108 DESCRIPTION 1109 "o Removed all uses of FrsldLocation by removing objects 1110 frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc 1111 o Removed FrsldRP TC and distributed source and destina- 1112 tion specific information into index for control table 1113 as frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP. 1114 o Added frsldPvcCtrlDelayCnt to control table. 1115 o Changed frsldPvcDataUnavailableTime from TimeStamp to 1116 TimeTicks. 1117 o Updated text of RowStatus objects 1118 o Added frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP 1119 as indices to ALL tables. 1120 o Added HC counters for all data delivery stats and 1121 samples. 1122 o Adjusted description of sample information for clarity. 1124 o Adjusted names of sample objects for consistency. 1125 o Added frsldRPCaps. 1126 o Changed location to mib-2 1127 o Reworked Group Definitions." 1129 REVISION "200002061500Z" 1130 DESCRIPTION 1131 "o Published as draft-ietf-frnetmib-frmrelay-service-00.txt 1132 o Added frsldCapabilities group to define the 1133 read/write capabilities 1134 o Changed location to experimental 104 1135 o Changed name of frsldTables to frsldObjects 1136 o Changed MAX-ACCESS of frsldPvcCtrlDelayType to 1137 read-create 1138 o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax, 1139 and frsldPvcDataDelayAvg from the sample period" 1141 REVISION "199909031500Z" 1142 DESCRIPTION 1143 "o Added range to frsldPvcCtrlPacketFreq 1144 o Changed range of frsldPvcCtrlDelayTimeOut to match 1145 that of frsldPvcCtrlPacketFreq 1146 o Clarified what happens when frsldPvcCtrlPacketFreq 1147 is set to zero 1148 o Changed delay to count in microseconds instead of 1149 milliseconds 1150 o Created a new sample control table and moved sample 1151 specific information into it. 1152 o Changed the prefix of `frsldPvcCtrl' object name to 1153 `frsldSmplCtrl' 1154 o Added the sample control index to the indices of the 1155 sample tables 1156 o Changed all occasions of TimeTicks to TimeStamp 1157 o Added frsldPvcCtrlPurge to aid in control validity 1158 of information due to PVC status changes 1159 o Added frsldPvcCtrlDeleteOnPurge object 1160 o Added frsldPvcCtrlLastPurgeTime object 1161 o Added units clauses to all time related fields. 1162 o Reworded the `change in' syntax to be more explicit" 1163 ::= { mib-2 xxx } -- RFC editor - IANA assigns xxx 1165 frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 } 1166 frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 } 1167 frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 } 1169 -- The Frame Relay Service Level Definitions PVC Control Table 1170 -- 1171 -- This table is used to define and display the parameters of 1172 -- service level definitions on individual PVCs. 1174 frsldPvcCtrlTable OBJECT-TYPE 1175 SYNTAX SEQUENCE OF FrsldPvcCtrlEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "The Frame Relay Service Level Definitions 1180 PVC control table." 1181 ::= { frsldObjects 1 } 1183 frsldPvcCtrlEntry OBJECT-TYPE 1184 SYNTAX FrsldPvcCtrlEntry 1185 MAX-ACCESS not-accessible 1186 STATUS current 1187 DESCRIPTION 1188 "An entry in the Frame Relay Service Level 1189 Definitions PVC control table." 1190 INDEX { ifIndex, frsldPvcCtrlDlci, 1191 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1192 ::= { frsldPvcCtrlTable 1 } 1194 FrsldPvcCtrlEntry ::= 1195 SEQUENCE { 1196 -- 1197 -- Index Control Variables 1198 -- 1199 frsldPvcCtrlDlci Integer32, 1200 frsldPvcCtrlTransmitRP INTEGER, 1201 frsldPvcCtrlReceiveRP INTEGER, 1202 frsldPvcCtrlStatus RowStatus, 1203 -- 1204 -- Service Level Definitions Setup Variables 1205 -- 1206 frsldPvcCtrlPacketFreq Integer32, 1207 -- 1208 -- Delay Specific Setup Variables 1209 -- 1210 frsldPvcCtrlDelayFrSize Integer32, 1211 frsldPvcCtrlDelayType INTEGER, 1212 frsldPvcCtrlDelayTimeOut Integer32, 1213 -- 1214 -- Data Persistence Control Variables 1215 -- 1216 frsldPvcCtrlPurge Integer32, 1217 frsldPvcCtrlDeleteOnPurge INTEGER, 1218 frsldPvcCtrlLastPurgeTime TimeStamp 1219 } 1221 frsldPvcCtrlDlci OBJECT-TYPE 1222 SYNTAX Integer32 (16..4194303) 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "The value of this object is equal to the DLCI 1227 value for this PVC." 1228 ::= { frsldPvcCtrlEntry 1 } 1230 frsldPvcCtrlTransmitRP OBJECT-TYPE 1231 SYNTAX INTEGER { 1232 srcLocalRP(1), 1233 ingTxLocalRP(2), 1234 tpTxLocalRP(3), 1235 eqiTxLocalRP(4), 1236 eqoTxLocalRP(5), 1237 otherTxLocalRP(6), 1238 srcRemoteRP(7), 1239 ingTxRemoteRP(8), 1240 tpTxRemoteRP(9), 1241 eqiTxRemoteRP(10), 1242 eqoTxRemoteRP(11), 1243 otherTxRemoteRP(12) 1244 } 1245 MAX-ACCESS not-accessible 1246 STATUS current 1247 DESCRIPTION 1248 "The reference point this PVC used for calculation 1249 of transmitter related statistics. This object 1250 together with frsldPvcCtrlReceiveRP define the 1251 measurement domain. 1253 The valid values for this object are as follows: 1254 - srcLocalRP(1) for the local source 1255 - ingTxLocalRP(2) for the local ingress queue input 1256 - tpTxLocalRP(3) for the local traffic policing 1257 - eqiTxLocalRP(4) for the local egress queue input 1258 - eqoTxLocalRP(5) for the local egress queue output 1259 - otherTxLocalRP(6) for any other local transmit point 1260 - srcRemoteRP(7) for the remote source 1261 - ingTxLocalRP(8) for the remote ingress queue input 1262 - tpTxLocalRP(9) for the remote traffic policing 1263 - eqiTxRemoteRP(10) for the remote egress queue input 1264 - eqoTxRemoteRP(11) for the remote egress queue output 1265 - otherTxRemoteRP(12) for any other remote xmit point" 1266 ::= { frsldPvcCtrlEntry 2 } 1268 frsldPvcCtrlReceiveRP OBJECT-TYPE 1269 SYNTAX INTEGER { 1270 desLocalRP(1), 1271 ingRxLocalRP(2), 1272 tpRxLocalRP(3), 1273 eqiRxLocalRP(4), 1274 eqoRxLocalRP(5), 1275 otherRxLocalRP(6), 1276 desRemoteRP(7), 1277 ingRxRemoteRP(8), 1278 tpRxRemoteRP(9), 1279 eqiRxRemoteRP(10), 1280 eqoRxRemoteRP(11), 1281 otherRxRemoteRP(12) 1282 } 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The reference point this PVC used for calculation 1287 of receiver related statistics. This object 1288 together with frsldPvcCtrlTransmitRP define the 1289 measurement domain. 1291 The valid values for this object are as follows: 1292 - desLocalRP(1) for the local destination 1293 - ingRxLocalRP(2) for the local ingress queue input 1294 - tpRxLocalRP(3) for the local traffic policing 1295 - eqiRxLocalRP(4) for the local egress queue input 1296 - eqoRxLocalRP(5) for the local egress queue output 1297 - otherRxLocalRP(6) for any other local receive point 1298 - desRemoteRP(7) for the remote destination 1299 - ingRxRemoteRP(8) for the remote ingress input 1300 - tpRxRemoteRP(9) for the remote traffic policing 1301 - eqiRxRemoteRP(10) for the remote egress queue input 1302 - eqoRxRemoteRP(11) for the remote egress queue output 1303 - otherRxRemoteRP(12) for any other remote receive point" 1304 ::= { frsldPvcCtrlEntry 3 } 1306 frsldPvcCtrlStatus OBJECT-TYPE 1307 SYNTAX RowStatus 1308 MAX-ACCESS read-create 1309 STATUS current 1310 DESCRIPTION 1311 "The status of the current row. This object is 1312 used to add, delete, and disable rows in this 1313 table. When the status changes to active(1) for the 1314 first time, a row will also be added to the data 1315 table below. This row SHOULD not be removed until 1316 the status is changed to deleted. 1318 When this object is set to destroy(6), all associated 1319 sample and data table rows will also be deleted. 1320 When this object is changed from active(1) to any 1321 other valid value, the defined purge behavior will 1322 affect the data and sample tables. 1324 The rows added to this table MUST have a valid 1325 ifIndex and an ifType related to frame relay. Further, 1326 the reference points referred to by frsldPvcCtrlTransmitRP 1327 and frsldPvcCtrlReceiveRP MUST be supported (see the 1328 frsldRPCaps object). 1330 If at any point the row is not in the active(1) state 1331 and the DLCI no longer exists, the state SHOULD 1332 report notReady(3)." 1333 ::= { frsldPvcCtrlEntry 4 } 1335 frsldPvcCtrlPacketFreq OBJECT-TYPE 1336 SYNTAX Integer32 (0..3600) 1337 UNITS "seconds" 1338 MAX-ACCESS read-create 1339 STATUS current 1340 DESCRIPTION 1341 "The frequency in seconds between initiation of 1342 specialized packets used to collect delay and / or 1343 delivery information as supported by the device. 1344 A value of zero indicates that no packets will 1345 be sent." 1346 DEFVAL { 60 } 1347 ::= { frsldPvcCtrlEntry 5 } 1349 frsldPvcCtrlDelayFrSize OBJECT-TYPE 1350 SYNTAX Integer32 (1..8188) 1351 UNITS "octets" 1352 MAX-ACCESS read-create 1353 STATUS current 1354 DESCRIPTION 1355 "The size of the payload in the frame used for 1356 calculation of network delay." 1357 DEFVAL { 128 } 1358 ::= { frsldPvcCtrlEntry 6 } 1360 frsldPvcCtrlDelayType OBJECT-TYPE 1361 SYNTAX INTEGER { 1362 oneWay(1), 1363 roundTrip(2) 1364 } 1365 MAX-ACCESS read-create 1366 STATUS current 1367 DESCRIPTION 1368 "The type of delay measurement performed." 1369 ::= { frsldPvcCtrlEntry 7 } 1371 frsldPvcCtrlDelayTimeOut OBJECT-TYPE 1372 SYNTAX Integer32 (1..3600) 1373 UNITS "seconds" 1374 MAX-ACCESS read-create 1375 STATUS current 1376 DESCRIPTION 1377 "A delay frame will count as a missed poll if 1378 it is not updated in the time specified by 1379 frsldPvcCtrlDelayTimeOut." 1380 DEFVAL { 60 } 1381 ::= { frsldPvcCtrlEntry 8 } 1383 frsldPvcCtrlPurge OBJECT-TYPE 1384 SYNTAX Integer32 (0..172800) -- up to 48 hours 1385 UNITS "seconds" 1386 MAX-ACCESS read-create 1387 STATUS current 1388 DESCRIPTION 1389 "This object defines the amount of time the device 1390 will wait, after discovering that a DLCI does not exist, 1391 the DLCI was deleted or the value of frsldPvcCtrlStatus 1392 changes from active(1) to either notInService(2) or 1393 notReady(3), prior to automatically purging the history 1394 in the sample tables and resetting the data in the data 1395 tables to all zeroes. If frsldPvcCtrlStatus is manually 1396 set to destroy(6), this object does not apply." 1397 DEFVAL { 0 } 1398 ::= { frsldPvcCtrlEntry 9 } 1400 frsldPvcCtrlDeleteOnPurge OBJECT-TYPE 1401 SYNTAX INTEGER { 1402 none(1), 1403 sampleContols(2), 1404 all(3) 1405 } 1406 MAX-ACCESS read-create 1407 STATUS current 1408 DESCRIPTION 1409 "This object defines whether rows will 1410 automatically be deleted from the tables 1411 when the information is purged. 1413 - A value of none(1) indicates that no rows 1414 will deleted. The last known values will 1415 be preserved. 1416 - A value of sampleControls(2) indicates 1417 that all associated sample control rows 1418 will be deleted. 1419 - A value of all(3) indicates that all 1420 associated rows SHOULD be deleted." 1421 DEFVAL { all } 1422 ::= { frsldPvcCtrlEntry 10 } 1424 frsldPvcCtrlLastPurgeTime OBJECT-TYPE 1425 SYNTAX TimeStamp 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "This object returns the value of sysUpTime 1430 at the time the information was last purged. 1431 This value SHOULD be set to the sysUpTime 1432 upon setting frsldPvcCtrlStatus to active(1) 1433 for the first time. If frsldPvcCtrlStatus has 1434 never been active(1), this object SHOULD return 0." 1435 DEFVAL { 0 } 1436 ::= { frsldPvcCtrlEntry 11 } 1438 -- The Frame Relay Service Level Definitions Sampling Control 1439 -- Table 1440 -- 1441 -- This table is used to define the sample control parameters 1442 -- of service level definitions on individual PVCs. 1444 frsldSmplCtrlTable OBJECT-TYPE 1445 SYNTAX SEQUENCE OF FrsldSmplCtrlEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "The Frame Relay Service Level Definitions 1450 sampling control table." 1451 ::= { frsldObjects 2 } 1453 frsldSmplCtrlEntry OBJECT-TYPE 1454 SYNTAX FrsldSmplCtrlEntry 1455 MAX-ACCESS not-accessible 1456 STATUS current 1457 DESCRIPTION 1458 "An entry in the Frame Relay Service Level 1459 Definitions sample control table." 1460 INDEX { ifIndex, frsldPvcCtrlDlci, 1461 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1462 frsldSmplCtrlIdx } 1463 ::= { frsldSmplCtrlTable 1 } 1465 FrsldSmplCtrlEntry ::= 1466 SEQUENCE { 1467 -- 1468 -- Index Control Variables 1469 -- 1470 frsldSmplCtrlIdx Integer32, 1471 frsldSmplCtrlStatus RowStatus, 1472 -- 1473 -- Collection Control Variables 1474 -- 1475 frsldSmplCtrlColPeriod Integer32, 1476 frsldSmplCtrlBuckets Integer32, 1477 frsldSmplCtrlBucketsGranted Integer32 1478 } 1480 frsldSmplCtrlIdx OBJECT-TYPE 1481 SYNTAX Integer32 (1..256) 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "The unique index for this row in the 1486 sample control table." 1487 ::= { frsldSmplCtrlEntry 1 } 1489 frsldSmplCtrlStatus OBJECT-TYPE 1490 SYNTAX RowStatus 1491 MAX-ACCESS read-create 1492 STATUS current 1493 DESCRIPTION 1494 "The status of the current row. This object is 1495 used to add, delete, and disable rows in this 1496 table. This row SHOULD NOT be removed until the 1497 status is changed to destroy(6). When the status 1498 changes to active(1), the collection in the sample 1499 tables below will be activated. 1501 The rows added to this table MUST have a valid 1502 ifIndex, an ifType related to frame relay, 1503 frsldPvcCtrlDlci MUST exist for the specified 1504 ifIndex and frsldPvcCtrlStatus MUST have a 1505 value of active(1). 1507 The value of frsldPvcCtrlStatus MUST be active(1) 1508 to transition this object to active(1). If 1509 the value of frsldPvcCtrlStatus becomes anything 1510 other than active(1) when the state of this object 1511 is not active(1), this object SHOULD be set to 1512 notReady(3)." 1513 ::= { frsldSmplCtrlEntry 2 } 1515 frsldSmplCtrlColPeriod OBJECT-TYPE 1516 SYNTAX Integer32 (1..2147483647) 1517 UNITS "seconds" 1518 MAX-ACCESS read-create 1519 STATUS current 1520 DESCRIPTION 1521 "The amount of time in seconds that defines a 1522 period of collection for the statistics. 1523 At the end of each period, the statistics will be 1524 sampled and a row is added to the sample table." 1525 ::= { frsldSmplCtrlEntry 3 } 1527 frsldSmplCtrlBuckets OBJECT-TYPE 1528 SYNTAX Integer32 (1..65535) 1529 MAX-ACCESS read-create 1530 STATUS current 1531 DESCRIPTION 1532 "The number of discrete buckets over which the 1533 data statistics are sampled. 1535 When this object is created or modified, the device 1536 SHOULD attempt to set the frsldSmplCtrlBuckets- 1537 Granted to a value as close as is possible 1538 depending upon the implementation and the available 1539 resources." 1540 DEFVAL { 60 } 1541 ::= { frsldSmplCtrlEntry 4 } 1543 frsldSmplCtrlBucketsGranted OBJECT-TYPE 1544 SYNTAX Integer32 (0..65535) 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The number of discrete buckets granted. This 1549 object will return 0 until frsldSmplCtrlStatus is 1550 set to active(1). At that time the buckets will be 1551 allocated depending upon implementation and 1552 available resources." 1553 ::= { frsldSmplCtrlEntry 5 } 1555 -- The Frame Relay Service Level Definitions PVC Data Table 1556 -- 1557 -- This table contains the accumulated values of 1558 -- the collected data. This table is the table that should 1559 -- be referenced by external polling mechanisms if time 1560 -- based polling be desired. 1562 frsldPvcDataTable OBJECT-TYPE 1563 SYNTAX SEQUENCE OF FrsldPvcDataEntry 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "The Frame Relay Service Level Definitions 1568 data table. 1570 This table contains accumulated values of the 1571 collected data. It is the table that should be 1572 referenced by external polling mechanisms if 1573 time based polling be desired." 1574 ::= { frsldObjects 3 } 1576 frsldPvcDataEntry OBJECT-TYPE 1577 SYNTAX FrsldPvcDataEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "An entry in the Frame Relay Service Level 1582 Definitions data table." 1583 INDEX { ifIndex, frsldPvcCtrlDlci, 1584 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP} 1585 ::= { frsldPvcDataTable 1 } 1587 FrsldPvcDataEntry ::= 1588 SEQUENCE { 1589 frsldPvcDataMissedPolls Counter32, 1590 frsldPvcDataFrDeliveredC Counter32, 1591 frsldPvcDataFrDeliveredE Counter32, 1592 frsldPvcDataFrOfferedC Counter32, 1593 frsldPvcDataFrOfferedE Counter32, 1594 frsldPvcDataDataDeliveredC Counter32, 1595 frsldPvcDataDataDeliveredE Counter32, 1596 frsldPvcDataDataOfferedC Counter32, 1597 frsldPvcDataDataOfferedE Counter32, 1598 frsldPvcDataHCFrDeliveredC Counter64, 1599 frsldPvcDataHCFrDeliveredE Counter64, 1600 frsldPvcDataHCFrOfferedC Counter64, 1601 frsldPvcDataHCFrOfferedE Counter64, 1602 frsldPvcDataHCDataDeliveredC Counter64, 1603 frsldPvcDataHCDataDeliveredE Counter64, 1604 frsldPvcDataHCDataOfferedC Counter64, 1605 frsldPvcDataHCDataOfferedE Counter64, 1606 frsldPvcDataUnavailableTime TimeTicks, 1607 frsldPvcDataUnavailables Counter32 1608 } 1610 frsldPvcDataMissedPolls OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "The total number of polls that have been determined 1616 to be missed." 1617 ::= { frsldPvcDataEntry 1 } 1619 frsldPvcDataFrDeliveredC OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "The number of frames that were received at 1625 frsldPvcCtrlReceiveRP and determined to have been 1626 sent within CIR." 1627 ::= { frsldPvcDataEntry 2 } 1629 frsldPvcDataFrDeliveredE OBJECT-TYPE 1630 SYNTAX Counter32 1631 MAX-ACCESS read-only 1632 STATUS current 1633 DESCRIPTION 1634 "The number of frames that were received at 1635 frsldPvcCtrlReceiveRP and determined to have been 1636 sent in excess of the CIR." 1637 ::= { frsldPvcDataEntry 3 } 1639 frsldPvcDataFrOfferedC OBJECT-TYPE 1640 SYNTAX Counter32 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "The number of frames that were offered through 1645 frsldPvcCtrlTransmitRP within CIR." 1646 ::= { frsldPvcDataEntry 4 } 1648 frsldPvcDataFrOfferedE OBJECT-TYPE 1649 SYNTAX Counter32 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The number of frames that were offered through 1654 frsldPvcCtrlTransmitRP in excess of the CIR." 1655 ::= { frsldPvcDataEntry 5 } 1657 frsldPvcDataDataDeliveredC OBJECT-TYPE 1658 SYNTAX Counter32 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 "The number of octets that were received at 1663 frsldPvcCtrlReceiveRP and determined to have been 1664 sent within CIR." 1665 ::= { frsldPvcDataEntry 6 } 1667 frsldPvcDataDataDeliveredE OBJECT-TYPE 1668 SYNTAX Counter32 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The number of octets that were received at 1673 frsldPvcCtrlReceiveRP and determined to have been 1674 sent in excess of the CIR." 1675 ::= { frsldPvcDataEntry 7 } 1677 frsldPvcDataDataOfferedC OBJECT-TYPE 1678 SYNTAX Counter32 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "The number of octets that were offered through 1683 frsldPvcCtrlTransmitRP within CIR." 1684 ::= { frsldPvcDataEntry 8 } 1686 frsldPvcDataDataOfferedE OBJECT-TYPE 1687 SYNTAX Counter32 1688 MAX-ACCESS read-only 1689 STATUS current 1690 DESCRIPTION 1691 "The number of octets that were offered through 1692 frsldPvcCtrlTransmitRP in excess of the CIR." 1693 ::= { frsldPvcDataEntry 9 } 1695 frsldPvcDataHCFrDeliveredC OBJECT-TYPE 1696 SYNTAX Counter64 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "The number of frames that were received at 1701 frsldPvcCtrlReceiveRP and determined to have been 1702 sent within CIR. This object is a 64-bit version 1703 of frsldPvcDataFrDeliveredC." 1704 ::= { frsldPvcDataEntry 10 } 1706 frsldPvcDataHCFrDeliveredE OBJECT-TYPE 1707 SYNTAX Counter64 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "The number of frames that were received at 1712 frsldPvcCtrlReceiveRP and determined to have been 1713 sent in excess of the CIR. This object is a 64-bit 1714 version of frsldPvcDataFrDeliveredE." 1715 ::= { frsldPvcDataEntry 11 } 1717 frsldPvcDataHCFrOfferedC OBJECT-TYPE 1718 SYNTAX Counter64 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "The number of frames that were offered through 1723 frsldPvcCtrlTransmitRP within CIR. This object is 1724 a 64-bit version of frsldPvcDataFrOfferedC." 1725 ::= { frsldPvcDataEntry 12 } 1727 frsldPvcDataHCFrOfferedE OBJECT-TYPE 1728 SYNTAX Counter64 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "The number of frames that were offered through 1733 frsldPvcCtrlTransmitRP in excess of the CIR. This 1734 object is a 64-bit version of frsldPvcDataFrOfferedE." 1735 ::= { frsldPvcDataEntry 13 } 1737 frsldPvcDataHCDataDeliveredC OBJECT-TYPE 1738 SYNTAX Counter64 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "The number of octets that were received at 1743 frsldPvcCtrlReceiveRP and determined to have been 1744 sent within CIR. This object is a 64-bit version of 1745 frsldPvcDataDataDeliveredC." 1746 ::= { frsldPvcDataEntry 14 } 1748 frsldPvcDataHCDataDeliveredE OBJECT-TYPE 1749 SYNTAX Counter64 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "The number of octets that were received at 1754 frsldPvcCtrlReceiveRP and determined to have been 1755 sent in excess of the CIR. This object is a 64-bit 1756 version of frsldPvcDataDataDeliveredE." 1757 ::= { frsldPvcDataEntry 15 } 1759 frsldPvcDataHCDataOfferedC OBJECT-TYPE 1760 SYNTAX Counter64 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "The number of octets that were offered through 1765 frsldPvcCtrlTransmitRP within CIR. This object is 1766 a 64-bit version of frsldPvcDataDataOfferedC." 1767 ::= { frsldPvcDataEntry 16 } 1769 frsldPvcDataHCDataOfferedE OBJECT-TYPE 1770 SYNTAX Counter64 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "The number of octets that were offered through 1775 frsldPvcCtrlTransmitRP in excess of the CIR. 1776 This object is a 64-bit version of 1777 frsldPvcDataDataOfferedE." 1778 ::= { frsldPvcDataEntry 17 } 1780 frsldPvcDataUnavailableTime OBJECT-TYPE 1781 SYNTAX TimeTicks 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "The amount of time this PVC was declared unavailable 1786 for any reason since this row was created." 1787 ::= { frsldPvcDataEntry 18 } 1789 frsldPvcDataUnavailables OBJECT-TYPE 1790 SYNTAX Counter32 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "The number of times this PVC was declared unavailable 1795 for any reason since this row was created." 1796 ::= { frsldPvcDataEntry 19 } 1798 -- The Frame Relay Service Level Definitions PVC Sample Table 1799 -- 1800 -- This table contains the sampled delay, delivery and 1801 -- availability information. 1803 frsldPvcSampleTable OBJECT-TYPE 1804 SYNTAX SEQUENCE OF FrsldPvcSampleEntry 1805 MAX-ACCESS not-accessible 1806 STATUS current 1807 DESCRIPTION 1808 "The Frame Relay Service Level Definitions 1809 sample table." 1810 ::= { frsldObjects 4 } 1812 frsldPvcSampleEntry OBJECT-TYPE 1813 SYNTAX FrsldPvcSampleEntry 1814 MAX-ACCESS not-accessible 1815 STATUS current 1816 DESCRIPTION 1817 "An entry in the Frame Relay Service Level 1818 Definitions data sample table." 1819 INDEX { ifIndex, frsldPvcCtrlDlci, 1820 frsldPvcCtrlTransmitRP, frsldPvcCtrlReceiveRP, 1821 frsldSmplCtrlIdx, frsldPvcSmplIdx } 1822 ::= { frsldPvcSampleTable 1 } 1824 FrsldPvcSampleEntry ::= 1825 SEQUENCE { 1826 frsldPvcSmplIdx Integer32, 1827 frsldPvcSmplDelayMin Gauge32, 1828 frsldPvcSmplDelayMax Gauge32, 1829 frsldPvcSmplDelayAvg Gauge32, 1830 frsldPvcSmplMissedPolls Gauge32, 1831 frsldPvcSmplFrDeliveredC Gauge32, 1832 frsldPvcSmplFrDeliveredE Gauge32, 1833 frsldPvcSmplFrOfferedC Gauge32, 1834 frsldPvcSmplFrOfferedE Gauge32, 1835 frsldPvcSmplDataDeliveredC Gauge32, 1836 frsldPvcSmplDataDeliveredE Gauge32, 1837 frsldPvcSmplDataOfferedC Gauge32, 1838 frsldPvcSmplDataOfferedE Gauge32, 1839 frsldPvcSmplHCFrDeliveredC CounterBasedGauge64, 1840 frsldPvcSmplHCFrDeliveredE CounterBasedGauge64, 1841 frsldPvcSmplHCFrOfferedC CounterBasedGauge64, 1842 frsldPvcSmplHCFrOfferedE CounterBasedGauge64, 1843 frsldPvcSmplHCDataDeliveredC CounterBasedGauge64, 1844 frsldPvcSmplHCDataDeliveredE CounterBasedGauge64, 1845 frsldPvcSmplHCDataOfferedC CounterBasedGauge64, 1846 frsldPvcSmplHCDataOfferedE CounterBasedGauge64, 1847 frsldPvcSmplUnavailableTime TimeTicks, 1848 frsldPvcSmplUnavailables Gauge32, 1849 frsldPvcSmplStartTime TimeStamp, 1850 frsldPvcSmplEndTime TimeStamp 1851 } 1853 frsldPvcSmplIdx OBJECT-TYPE 1854 SYNTAX Integer32 (1..2147483647) 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "The bucket index of the current sample. This 1859 increments once for each new bucket in the 1860 table." 1861 ::= { frsldPvcSampleEntry 1 } 1863 frsldPvcSmplDelayMin OBJECT-TYPE 1864 SYNTAX Gauge32 1865 UNITS "microseconds" 1866 MAX-ACCESS read-only 1867 STATUS current 1868 DESCRIPTION 1869 "The minimum delay reported in microseconds measured 1870 for any information packet that arrived during this 1871 interval. 1873 A value of zero means that no data is available." 1874 ::= { frsldPvcSampleEntry 2 } 1876 frsldPvcSmplDelayMax OBJECT-TYPE 1877 SYNTAX Gauge32 1878 UNITS "microseconds" 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "The largest delay reported in microseconds measured 1883 for any information packet that arrived during this 1884 interval. 1886 A value of zero means that no data is available." 1887 ::= { frsldPvcSampleEntry 3 } 1889 frsldPvcSmplDelayAvg OBJECT-TYPE 1890 SYNTAX Gauge32 1891 UNITS "microseconds" 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "The average delay reported in microseconds measured 1896 for all delay packets that arrived during this 1897 interval. 1899 A value of zero means that no data is available." 1900 ::= { frsldPvcSampleEntry 4 } 1902 frsldPvcSmplMissedPolls OBJECT-TYPE 1903 SYNTAX Gauge32 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The total number of polls that were missed during 1908 this interval." 1909 ::= { frsldPvcSampleEntry 5 } 1911 frsldPvcSmplFrDeliveredC OBJECT-TYPE 1912 SYNTAX Gauge32 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "The number of frames that were received at 1917 frsldPvcCtrlReceiveRP and determined to have been 1918 sent within CIR during this interval." 1919 ::= { frsldPvcSampleEntry 6 } 1921 frsldPvcSmplFrDeliveredE OBJECT-TYPE 1922 SYNTAX Gauge32 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "The number of frames that were received at 1927 frsldPvcCtrlReceiveRP and determined to have been 1928 sent in excess of the CIR during this interval." 1929 ::= { frsldPvcSampleEntry 7 } 1931 frsldPvcSmplFrOfferedC OBJECT-TYPE 1932 SYNTAX Gauge32 1933 MAX-ACCESS read-only 1934 STATUS current 1935 DESCRIPTION 1936 "The number of frames that were offered through 1937 frsldPvcCtrlTransmitRP within CIR during this 1938 interval." 1939 ::= { frsldPvcSampleEntry 8 } 1941 frsldPvcSmplFrOfferedE OBJECT-TYPE 1942 SYNTAX Gauge32 1943 MAX-ACCESS read-only 1944 STATUS current 1945 DESCRIPTION 1946 "The number of frames that were offered through 1947 frsldPvcCtrlTransmitRP in excess of the CIR 1948 during this interval." 1949 ::= { frsldPvcSampleEntry 9 } 1951 frsldPvcSmplDataDeliveredC OBJECT-TYPE 1952 SYNTAX Gauge32 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The number of octets that were received at 1957 frsldPvcCtrlReceiveRP and determined to have been 1958 sent within CIR during this interval." 1959 ::= { frsldPvcSampleEntry 10 } 1961 frsldPvcSmplDataDeliveredE OBJECT-TYPE 1962 SYNTAX Gauge32 1963 MAX-ACCESS read-only 1964 STATUS current 1965 DESCRIPTION 1966 "The number of octets that were received at 1967 frsldPvcCtrlDeliveredRP and determined to have been 1968 sent in excess of the CIR during this interval." 1969 ::= { frsldPvcSampleEntry 11 } 1971 frsldPvcSmplDataOfferedC OBJECT-TYPE 1972 SYNTAX Gauge32 1973 MAX-ACCESS read-only 1974 STATUS current 1975 DESCRIPTION 1976 "The number of octets that were offered through 1977 frsldPvcCtrlTransmitRP within CIR during this 1978 interval." 1979 ::= { frsldPvcSampleEntry 12 } 1981 frsldPvcSmplDataOfferedE OBJECT-TYPE 1982 SYNTAX Gauge32 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "The number of octets that were offered through 1987 frsldPvcCtrlTransmitRP in excess of the CIR 1988 during this interval." 1989 ::= { frsldPvcSampleEntry 13 } 1991 frsldPvcSmplHCFrDeliveredC OBJECT-TYPE 1992 SYNTAX CounterBasedGauge64 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "The number of frames that were received at 1997 frsldPvcCtrlReceiveRP and determined to have been 1998 sent within CIR during this interval. This object 1999 is a 64-bit version of frsldPvcSmplFrDeliveredC." 2000 ::= { frsldPvcSampleEntry 14 } 2002 frsldPvcSmplHCFrDeliveredE OBJECT-TYPE 2003 SYNTAX CounterBasedGauge64 2004 MAX-ACCESS read-only 2005 STATUS current 2006 DESCRIPTION 2007 "The number of frames that were received at 2008 frsldPvcCtrlReceiveRP and determined to have been 2009 sent in excess of the CIR during this interval. 2010 This object is a 64-bit version of frsldPvcSmpl- 2011 FrDeliveredE." 2012 ::= { frsldPvcSampleEntry 15 } 2014 frsldPvcSmplHCFrOfferedC OBJECT-TYPE 2015 SYNTAX CounterBasedGauge64 2016 MAX-ACCESS read-only 2017 STATUS current 2018 DESCRIPTION 2019 "The number of frames that were offered through 2020 frsldPvcCtrlTransmitRP within CIR during this 2021 interval. This object is a 64-bit version of 2022 frsldPvcSmplFrOfferedC." 2023 ::= { frsldPvcSampleEntry 16 } 2025 frsldPvcSmplHCFrOfferedE OBJECT-TYPE 2026 SYNTAX CounterBasedGauge64 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The number of frames that were offered through 2031 frsldPvcCtrlTransmitRP in excess of the CIR 2032 during this interval. This object is a 64-bit 2033 version of frsldPvcSmplFrOfferedE." 2034 ::= { frsldPvcSampleEntry 17 } 2036 frsldPvcSmplHCDataDeliveredC OBJECT-TYPE 2037 SYNTAX CounterBasedGauge64 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "The number of octets that were received at 2042 frsldPvcCtrlReceiveRP and determined to have been 2043 sent within CIR during this interval. This value 2044 is a 64-bit version of frsldPvcSmplDataDeliveredC." 2045 ::= { frsldPvcSampleEntry 18 } 2047 frsldPvcSmplHCDataDeliveredE OBJECT-TYPE 2048 SYNTAX CounterBasedGauge64 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "The number of octets that were received at 2053 frsldPvcCtrlReceiveRP and determined to have been 2054 sent in excess of the CIR during this interval. This 2055 value is a 64-bit version of frsldPvcSmplData- 2056 DeliveredE." 2057 ::= { frsldPvcSampleEntry 19 } 2059 frsldPvcSmplHCDataOfferedC OBJECT-TYPE 2060 SYNTAX CounterBasedGauge64 2061 MAX-ACCESS read-only 2062 STATUS current 2063 DESCRIPTION 2064 "The number of octets that were offered through 2065 frsldPvcCtrlTransmitRP within CIR during this 2066 interval. This value is a 64-bit version of 2067 frsldPvcSmplDataOfferedC." 2068 ::= { frsldPvcSampleEntry 20 } 2070 frsldPvcSmplHCDataOfferedE OBJECT-TYPE 2071 SYNTAX CounterBasedGauge64 2072 MAX-ACCESS read-only 2073 STATUS current 2074 DESCRIPTION 2075 "The number of octets that were offered through 2076 frsldPvcCtrlTransmitRP in excess of the CIR 2077 during this interval. This object is a 64-bit 2078 version of frsldPvcSmplDataOfferedE." 2079 ::= { frsldPvcSampleEntry 21 } 2081 frsldPvcSmplUnavailableTime OBJECT-TYPE 2082 SYNTAX TimeTicks 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "The amount of time this PVC was declared 2087 unavailable for any reason during this interval." 2088 ::= { frsldPvcSampleEntry 22 } 2090 frsldPvcSmplUnavailables OBJECT-TYPE 2091 SYNTAX Gauge32 2092 MAX-ACCESS read-only 2093 STATUS current 2094 DESCRIPTION 2095 "The number of times this PVC was declared 2096 unavailable for any reason during this interval." 2097 ::= { frsldPvcSampleEntry 23 } 2099 frsldPvcSmplStartTime OBJECT-TYPE 2100 SYNTAX TimeStamp 2101 MAX-ACCESS read-only 2102 STATUS current 2103 DESCRIPTION 2104 "The value of sysUpTime when this sample interval 2105 started." 2106 ::= { frsldPvcSampleEntry 24 } 2108 frsldPvcSmplEndTime OBJECT-TYPE 2109 SYNTAX TimeStamp 2110 MAX-ACCESS read-only 2111 STATUS current 2112 DESCRIPTION 2113 "The value of sysUpTime when this sample interval 2114 ended. No data will be reported and the row will 2115 not appear in the table until the sample has 2116 been collected." 2117 ::= { frsldPvcSampleEntry 25 } 2119 -- Capabilities Group 2121 -- This group provides capabilities objects for the tables 2122 -- that control configuration. 2124 frsldPvcCtrlWriteCaps OBJECT-TYPE 2125 SYNTAX BITS { 2126 frsldPvcCtrlStatus(0), 2127 frsldPvcCtrlPacketFreq(1), 2128 frsldPvcCtrlDelayFrSize(2), 2129 frsldPvcCtrlDelayType(3), 2130 frsldPvcCtrlDelayTimeOut(4), 2131 frsldPvcCtrlPurge(5), 2132 frsldPvcCtrlDeleteOnPurge(6) 2133 } 2134 MAX-ACCESS read-only 2135 STATUS current 2136 DESCRIPTION 2137 "This object specifies the write capabilities 2138 for the read-create objects of the PVC Control 2139 table. If the corresponding bit is enabled (1), 2140 the agent supports writes to that object." 2141 ::= { frsldCapabilities 1 } 2143 frsldSmplCtrlWriteCaps OBJECT-TYPE 2144 SYNTAX BITS { 2145 frsldSmplCtrlStatus(0), 2146 frsldSmplCtrlBuckets(1) 2147 } 2148 MAX-ACCESS read-only 2149 STATUS current 2150 DESCRIPTION 2151 "This object specifies the write capabilities 2152 for the read-create objects of the Sample Control 2153 table. If the corresponding bit is enabled (1), 2154 the agent supports writes to that object." 2155 ::= { frsldCapabilities 2 } 2157 frsldRPCaps OBJECT-TYPE 2158 SYNTAX BITS { 2159 srcLocalRP(0), 2160 ingTxLocalRP(1), 2161 tpTxLocalRP(2), 2162 eqiTxLocalRP(3), 2163 eqoTxLocalRP(4), 2164 otherTxLocalRP(5), 2165 srcRemoteRP(6), 2166 ingTxRemoteRP(7), 2167 tpTxRemoteRP(8), 2168 eqiTxRemoteRP(9), 2169 eqoTxRemoteRP(10), 2170 otherTxRemoteRP(11), 2171 desLocalRP(12), 2172 ingRxLocalRP(13), 2173 tpRxLocalRP(14), 2174 eqiRxLocalRP(15), 2175 eqoRxLocalRP(16), 2176 otherRxLocalRP(17), 2177 desRemoteRP(18), 2178 ingRxRemoteRP(19), 2179 tpRxRemoteRP(20), 2180 eqiRxRemoteRP(21), 2181 eqoRxRemoteRP(22), 2182 otherRxRemoteRP(23) 2184 } 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "This object specifies the reference points that 2189 the agent supports. This object allows the management 2190 application to discover which rows can be created on 2191 a specific device." 2192 ::= { frsldCapabilities 3 } 2194 -- Conformance Information 2196 frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } 2197 frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } 2199 -- 2200 -- Compliance Statements 2201 -- 2203 frsldCompliance MODULE-COMPLIANCE 2204 STATUS current 2205 DESCRIPTION 2206 "The compliance statement for SNMPv2 entities 2207 which support with Frame Relay Service Level 2208 Definitions. This group defines the minimum 2209 level of support required for compliance." 2210 MODULE -- this module 2211 MANDATORY-GROUPS { frsldPvcReqCtrlGroup, 2212 frsldPvcReqDataGroup, 2213 frsldCapabilitiesGroup} 2215 OBJECT frsldPvcCtrlStatus 2216 SYNTAX INTEGER { active(1) } -- subset of RowStatus 2217 MIN-ACCESS read-only 2218 DESCRIPTION 2219 "Write access is not required, and only one of the six 2220 enumerated values for the RowStatus textual convention 2221 need be supported, specifically: active(1)." 2223 OBJECT frsldPvcCtrlPurge 2224 MIN-ACCESS read-only 2225 DESCRIPTION 2226 "Write access is not required." 2228 OBJECT frsldPvcCtrlDeleteOnPurge 2229 MIN-ACCESS read-only 2230 DESCRIPTION 2231 "Write access is not required." 2233 ::= { frsldMIBCompliances 1 } 2235 -- 2236 -- Units of Conformance 2237 -- 2238 frsldPvcReqCtrlGroup OBJECT-GROUP 2239 OBJECTS { 2240 frsldPvcCtrlStatus, 2241 frsldPvcCtrlPurge, 2242 frsldPvcCtrlDeleteOnPurge, 2243 frsldPvcCtrlLastPurgeTime 2244 } 2245 STATUS current 2246 DESCRIPTION 2247 "A collection of required objects providing 2248 control information applicable to a PVC which 2249 implements Service Level Definitions." 2250 ::= { frsldMIBGroups 1 } 2252 frsldPvcPacketGroup OBJECT-GROUP 2253 OBJECTS { 2254 frsldPvcCtrlPacketFreq 2255 } 2256 STATUS current 2257 DESCRIPTION 2258 "A collection of optional objects providing packet 2259 level control information applicable to a PVC which 2260 implements Service Level Definitions." 2261 ::= { frsldMIBGroups 2 } 2263 frsldPvcDelayCtrlGroup OBJECT-GROUP 2264 OBJECTS { 2265 frsldPvcCtrlDelayFrSize, 2266 frsldPvcCtrlDelayType, 2267 frsldPvcCtrlDelayTimeOut 2268 } 2269 STATUS current 2270 DESCRIPTION 2271 "A collection of optional objects providing delay 2272 control information applicable to a PVC which 2273 implements Service Level Definitions." 2274 ::= { frsldMIBGroups 3 } 2276 frsldPvcSampleCtrlGroup OBJECT-GROUP 2277 OBJECTS { 2278 frsldSmplCtrlStatus, 2279 frsldSmplCtrlColPeriod, 2280 frsldSmplCtrlBuckets, 2281 frsldSmplCtrlBucketsGranted 2282 } 2283 STATUS current 2284 DESCRIPTION 2285 "A collection of optional objects providing sample 2286 control information applicable to a PVC which 2287 implements Service Level Definitions." 2288 ::= { frsldMIBGroups 4 } 2290 frsldPvcReqDataGroup OBJECT-GROUP 2291 OBJECTS { 2292 frsldPvcDataFrDeliveredC, 2293 frsldPvcDataFrDeliveredE, 2294 frsldPvcDataFrOfferedC, 2295 frsldPvcDataFrOfferedE, 2296 frsldPvcDataDataDeliveredC, 2297 frsldPvcDataDataDeliveredE, 2298 frsldPvcDataDataOfferedC, 2299 frsldPvcDataDataOfferedE, 2300 frsldPvcDataUnavailableTime, 2301 frsldPvcDataUnavailables 2302 } 2303 STATUS current 2304 DESCRIPTION 2305 "A collection of required objects providing data 2306 collected on a PVC which implements Service 2307 Level Definitions." 2308 ::= { frsldMIBGroups 5 } 2310 frsldPvcDelayDataGroup OBJECT-GROUP 2311 OBJECTS { 2312 frsldPvcDataMissedPolls 2313 } 2314 STATUS current 2315 DESCRIPTION 2316 "A collection of optional objects providing delay 2317 data collected on a PVC which implements Service 2318 Level Definitions." 2319 ::= { frsldMIBGroups 6 } 2321 frsldPvcHCFrameDataGroup OBJECT-GROUP 2322 OBJECTS { 2323 frsldPvcDataHCFrDeliveredC, 2324 frsldPvcDataHCFrDeliveredE, 2325 frsldPvcDataHCFrOfferedC, 2326 frsldPvcDataHCFrOfferedE 2327 } 2328 STATUS current 2329 DESCRIPTION 2330 "A collection of optional objects providing high 2331 capacity frame data collected on a PVC which 2332 implements Service Level Definitions." 2333 ::= { frsldMIBGroups 7 } 2335 frsldPvcHCOctetDataGroup OBJECT-GROUP 2336 OBJECTS { 2337 frsldPvcDataHCDataDeliveredC, 2338 frsldPvcDataHCDataDeliveredE, 2339 frsldPvcDataHCDataOfferedC, 2340 frsldPvcDataHCDataOfferedE 2341 } 2342 STATUS current 2343 DESCRIPTION 2344 "A collection of optional objects providing high 2345 capacity octet data collected on a PVC which 2346 implements Service Level Definitions." 2347 ::= { frsldMIBGroups 8 } 2349 frsldPvcSampleDelayGroup OBJECT-GROUP 2350 OBJECTS { 2351 frsldPvcSmplDelayMin, 2352 frsldPvcSmplDelayMax, 2353 frsldPvcSmplDelayAvg, 2354 frsldPvcSmplMissedPolls 2355 } 2356 STATUS current 2357 DESCRIPTION 2358 "A collection of optional objects providing delay 2359 sample data collected on a PVC which implements 2360 Service Level Definitions." 2361 ::= { frsldMIBGroups 9 } 2363 frsldPvcSampleDataGroup OBJECT-GROUP 2364 OBJECTS { 2365 frsldPvcSmplFrDeliveredC, 2366 frsldPvcSmplFrDeliveredE, 2367 frsldPvcSmplFrOfferedC, 2368 frsldPvcSmplFrOfferedE, 2369 frsldPvcSmplDataDeliveredC, 2370 frsldPvcSmplDataDeliveredE, 2371 frsldPvcSmplDataOfferedC, 2372 frsldPvcSmplDataOfferedE 2373 } 2374 STATUS current 2375 DESCRIPTION 2376 "A collection of optional objects providing data 2377 and frame delivery sample data collected on a PVC 2378 which implements Service Level Definitions." 2379 ::= { frsldMIBGroups 10 } 2381 frsldPvcSampleHCFrameGroup OBJECT-GROUP 2382 OBJECTS { 2383 frsldPvcSmplHCFrDeliveredC, 2384 frsldPvcSmplHCFrDeliveredE, 2385 frsldPvcSmplHCFrOfferedC, 2386 frsldPvcSmplHCFrOfferedE 2387 } 2388 STATUS current 2389 DESCRIPTION 2390 "A collection of optional objects providing high 2391 capacity frame delivery sample data collected on a PVC 2392 which implements Service Level Definitions." 2393 ::= { frsldMIBGroups 11 } 2395 frsldPvcSampleHCDataGroup OBJECT-GROUP 2396 OBJECTS { 2397 frsldPvcSmplHCDataDeliveredC, 2398 frsldPvcSmplHCDataDeliveredE, 2399 frsldPvcSmplHCDataOfferedC, 2400 frsldPvcSmplHCDataOfferedE 2401 } 2402 STATUS current 2403 DESCRIPTION 2404 "A collection of optional objects providing high 2405 capacity data delivery sample data collected on a PVC 2406 which implements Service Level Definitions." 2407 ::= { frsldMIBGroups 12 } 2409 frsldPvcSampleAvailGroup OBJECT-GROUP 2410 OBJECTS { 2411 frsldPvcSmplUnavailableTime, 2412 frsldPvcSmplUnavailables 2413 } 2414 STATUS current 2415 DESCRIPTION 2416 "A collection of optional objects providing 2417 availability sample data collected on a PVC which 2418 implements Service Level Definitions." 2419 ::= { frsldMIBGroups 13 } 2421 frsldPvcSampleGeneralGroup OBJECT-GROUP 2422 OBJECTS { 2423 frsldPvcSmplStartTime, 2424 frsldPvcSmplEndTime 2426 } 2427 STATUS current 2428 DESCRIPTION 2429 "A collection of optional objects providing 2430 general sample data collected on a PVC which 2431 implements Service Level Definitions." 2432 ::= { frsldMIBGroups 14 } 2434 frsldCapabilitiesGroup OBJECT-GROUP 2435 OBJECTS { 2436 frsldPvcCtrlWriteCaps, 2437 frsldSmplCtrlWriteCaps, 2438 frsldRPCaps 2439 } 2440 STATUS current 2441 DESCRIPTION 2442 "A collection of required objects providing 2443 capability information for this MIB." 2444 ::= { frsldMIBGroups 15 } 2445 END 2447 7. Acknowledgments 2449 This document was produced by the Frame Relay Service MIB Working 2450 Group. It is based on the Frame Relay Forum's implementation 2451 agreement on service level definitions, FRF.13 [17]. 2453 The editors would like to thank the following people for their 2454 helpful comments: 2456 o Ken Rehbehn, Visual Networks 2458 o Santa Dasu, Quick Eagle Networks 2460 8. References 2462 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2463 Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, 2464 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2466 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2467 Management Information for TCP/IP-based Internets", RFC 1155, STD 2468 16, Performance Systems International, Hughes LAN Systems, May 1990 2470 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2471 STD 16, Performance Systems International, Hughes LAN Systems, March 2472 1991 2474 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2475 RFC 1215, Performance Systems International, March 1991 2477 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2478 and S. Waldbusser, "Structure of Management Information Version 2 2479 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 2480 Braunschweig, SNMP Research, First Virtual Holdings, International 2481 Network Services, April 1999 2483 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2484 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 2485 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2486 Virtual Holdings, International Network Services, April 1999 2488 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2489 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 2490 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2491 Virtual Holdings, International Network Services, April 1999 2493 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2494 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 2495 Systems International, Performance Systems International, MIT 2496 Laboratory for Computer Science, May 1990. 2498 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction 2499 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 2500 Systems, Inc., Dover Beach Consulting, Inc., International Network 2501 Services, January 1996. 2503 [10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2504 Mappings for Version 2 of the Simple Network Management Protocol 2505 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 2506 Beach Consulting, Inc., International Network Services, January 2507 1996. 2509 [11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2510 Processing and Dispatching for the Simple Network Management 2511 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 2512 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 2514 [12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2515 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2516 2574, IBM T. J. Watson Research, April 1999 2518 [13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2519 Operations for Version 2 of the Simple Network Management Protocol 2520 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 2521 Beach Consulting, Inc., International Network Services, January 2522 1996. 2524 [14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2525 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2526 Systems, April 1999 2528 [15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2529 Control Model (VACM) for the Simple Network Management Protocol 2530 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 2531 Cisco Systems, Inc., April 1999 2533 [16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2534 Version 3 of the Internet-standard Network Management Framework", 2535 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 2536 Ericsson, Cisco Systems, April 1999 2538 [17]Frame Relay Forum Technical Committee, "Service Level Definitions 2539 Implementations Agreement", FRF.13, August 1998. 2541 [18]Brown, T., "Definitions of Managed Objects for Frame Relay Service", 2542 RFC 1604, Bell Communications Research, March 1994. 2544 [19]Waldbusser, S., "Remote Network Monitoring Management Information 2545 Base Version 2 using SMIv2", RFC 2021, International Network 2546 Service, January 1997. 2548 [20]Brown, C., Baker, F., "Management Information Base for Frame Relay 2549 DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, 2550 September 1997. 2552 9. Security Considerations 2554 There are a number of management objects defined in this MIB that 2555 have a MAX-ACCESS clause of read-write and/or read-create. Such 2556 objects may be considered sensitive or vulnerable in some network 2557 environments. The support for SET operations in a non-secure 2558 environment without proper protection can have a negative effect on 2559 network operations. 2561 SNMPv1 by itself is not a secure environment. Even if the network 2562 itself is secure (for example by using IPSec), even then, there is no 2563 control as to who on the secure network is allowed to access and 2564 GET/SET (read/change/create/delete) the objects in this MIB. 2566 It is recommended that the implementers consider the security 2567 features as provided by the SNMPv3 framework. Specifically, the use 2568 of the User-based Security Model RFC 2274 [12] and the View-based 2569 Access Control Model RFC 2275 [15] is recommended. 2571 It is then a customer/user responsibility to ensure that the SNMP 2572 entity giving access to an instance of this MIB, is properly 2573 configured to give access to the objects only to those principals 2574 (users) that have legitimate rights to indeed GET or SET 2575 (change/create/delete) them. 2577 10. Authors' Addresses 2579 Robert Steinberger 2580 Paradyne Networks 2581 Mailstop: LG-132 2582 8545 126th Avenue North 2583 Largo, FL USA 33773 2585 Phone: 1(727)530-2395 2587 Email: rsteinberger@paradyne.com 2589 Orly Nicklass, Ph.D 2590 RAD Data Communications Ltd. 2591 12 Hanechoshet Street 2592 Tel Aviv, Israel 69710 2594 Phone: 972 3 7659969 2596 Email: Orly_n@rrad.co.il 2598 11. Copyright Section 2600 Copyright (C) The Internet Society (2000). All Rights Reserved. 2602 This document and translations of it may be copied and furnished to 2603 others, and derivative works that comment on or otherwise explain it 2604 or assist in its implementation may be prepared, copied, published 2605 and distributed, in whole or in part, without restriction of any 2606 kind, provided that the above copyright notice and this paragraph are 2607 included on all such copies and derivative works. However, this 2608 document itself may not be modified in any way, such as by removing 2609 the copyright notice or references to the Internet Society or other 2610 Internet organizations, except as needed for the purpose of 2611 developing Internet standards in which case the procedures for 2612 copyrights defined in the Internet Standards process must be 2613 followed, or as required to translate it into languages other than 2614 English. 2616 The limited permissions granted above are perpetual and will not be 2617 revoked by the Internet Society or its successors or assigns. 2619 This document and the information contained herein is provided on an 2620 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2621 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2622 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2623 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2624 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.