idnits 2.17.1 draft-ietf-frnetmib-frmrelay-service-00.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 44 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 8 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 567: '... what objects MUST be implemented....' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 304 has weird spacing: '...e point used ...' == Line 307 has weird spacing: '... to the speci...' == Line 521 has weird spacing: '...(1) and frCir...' == Line 1416 has weird spacing: '...alue of frsld...' == Line 2000 has weird spacing: '...for the purpo...' -- 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 (February 7, 2000) is 8843 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 97, but not defined == Missing Reference: '11' is mentioned on line 98, but not defined == Missing Reference: '12' is mentioned on line 1958, but not defined == Missing Reference: '13' is mentioned on line 104, but not defined == Missing Reference: '14' is mentioned on line 106, but not defined == Missing Reference: '15' is mentioned on line 1959, but not defined == Missing Reference: '16' is mentioned on line 111, but not defined == Missing Reference: '17' is mentioned on line 1848, but not defined == Missing Reference: '18' is mentioned on line 531, but not defined == Missing Reference: '19' is mentioned on line 328, but not defined == Missing Reference: '20' is mentioned on line 510, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') Summary: 11 errors (**), 0 flaws (~~), 19 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 February 7, 2000 6 draft-ietf-frnetmib-frmrelay-service-00.txt 8 Robert A. Steinberger 9 Paradyne Networks 10 rsteinberger@paradyne.com 12 Orly Nicklass, Ph.D 13 RAD Data Communications Ltd. 14 orly@radmail.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 (2000). All Rights Reserved. 47 Table of Contents 49 1. The SNMP Management Framework ............................... 3 50 2. Overview .................................................... 4 51 2.1. Frame Relay Service Level Definitions ..................... 4 52 2.2. Terminology ............................................... 5 53 2.3. Network Model ............................................. 6 54 2.4. Reference Points .......................................... 6 55 2.5. Measurement Methodology ................................... 8 56 2.6. Collection Location ....................................... 8 57 2.7. Use of MIB in Calculation of Service Level Definitions .... 10 58 2.7.1. Delay ................................................... 11 59 2.7.2. Frame Delivery Ratio .................................... 11 60 2.7.3. Data Delivery Ratio ..................................... 11 61 2.7.4. Service Availability .................................... 12 62 3. Relation to Other MIBs ...................................... 12 63 4. Structure of the MIB ........................................ 13 64 4.1. frsldPvcCtrlTable ......................................... 13 65 4.2. frsldSmplCtrlTable ........................................ 14 66 4.3. frsldPvcDataTable ......................................... 14 67 4.4. frsldPvcDataSampleTable ................................... 14 68 4.5. frsldPvcAvailSampleTable .................................. 14 69 4.6. frsldCapabilities ......................................... 14 70 5. Object Definitions .......................................... 14 71 6. Acknowledgments ............................................. 40 72 7. References .................................................. 41 73 8. Security Considerations ..................................... 43 74 9. Authors' Addresses .......................................... 43 75 10. Copyright Section .......................................... 44 77 1. The SNMP Management Framework 79 The SNMP Management Framework presently consists of five major 80 components: 82 o An overall architecture, described in RFC 2571 [1]. 84 o Mechanisms for describing and naming objects and events for 85 the purpose of management. The first version of this 86 Structure of Management Information (SMI) is called SMIv1 and 87 described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The 88 second version, called SMIv2, is described in RFC 2578 [5], 89 RFC 2579 [6] and RFC 2580 [7]. 91 o Message protocols for transferring management information. 92 The first version of the SNMP message protocol is called 93 SNMPv1 and described in RFC 1157 [8]. A second version of the 94 SNMP message protocol, which is not an Internet standards 95 track protocol, is called SNMPv2c and described in RFC 1901 96 [9] and RFC 1906 [10]. The third version of the message 97 protocol is called SNMPv3 and described in RFC 1906 [10], RFC 98 2572 [11] and RFC 2574 [12]. 100 o Protocol operations for accessing management information. The 101 first set of protocol operations and associated PDU formats 102 is described in RFC 1157 [8]. A second set of protocol 103 operations and associated PDU formats is described in RFC 104 1905 [13]. 106 o A set of fundamental applications described in RFC 2573 [14] 107 and the view-based access control mechanism described in RFC 108 2575 [15]. 110 A more detailed introduction to the current SNMP Management Framework 111 can be found in RFC 2570 [16]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. Objects in the MIB are 115 defined using the mechanisms defined in the SMI. 117 This memo specifies a MIB module that is compliant to the SMIv2. A 118 MIB conforming to the SMIv1 can be produced through the appropriate 119 translations. The resulting translated MIB must be semantically 120 equivalent, except where objects or events are omitted because no 121 translation is possible (use of Counter64). Some machine readable 122 information in SMIv2 will be converted into textual descriptions in 123 SMIv1 during the translation process. However, this loss of machine 124 readable information is not considered to change the semantics of the 125 MIB. 127 2. Overview 129 This MIB addresses the items required to manage the Frame Relay 130 Forum's Implementation Agreement for Service Level Definitions 131 (FRF.13 [17]). At present, this applies to these values of the 132 ifType variable in the Internet-standard MIB: 134 o frameRelay (32) 136 o frameRelayService (44) 138 This section provides an overview and background of how to use this 139 MIB. 141 2.1. Frame Relay Service Level Definitions 143 The frame relay service level definitions address specific 144 characteristics of a frame relay service that can be used to 145 facilitate the following tasks: 147 o Evaluation of frame relay service providers, offerings or 148 products. 150 o Measurement of Quality of Service. 152 o Enforcement of Service Level Agreements. 154 o Planning or describing a frame relay network. 156 The following parameters are defined in FRF.13 [17] as a sufficient 157 set of values to accomplish the tasks previously stated. 159 o Delay - The amount of time elapsed, in microseconds, from the 160 time a frame exits the source to the time it reaches the 161 destination. NOTE: FRF.13 [17] defines this value in terms 162 of milliseconds. 164 o Frame Delivery Ratio - The ratio of the number of frames 165 delivered to the destination versus the number of frames sent 166 by the source. This ratio can be further divided by 167 inspecting either only the frames within the CIR or only the 168 frames in excess of the CIR. 170 o Data Delivery Ratio - The ratio of the amount of data 171 delivered to the destination versus the amount of data sent 172 by the source. This ratio can be further divided by 173 inspecting either only the data within the CIR or only the 174 data in excess of the CIR. 176 o Service Availability - The amount of time the frame relay 177 service was not unavailable. There are three types of 178 availability statistics defined in FRF.13 [17]: Virtual 179 Connection Availability, Mean Time to Repair, and Mean Time 180 Between Service Outages. The later two require information 181 about the scheduled outage time. It is assumed that this 182 information will be maintained by the network management 183 software, so it is not included in the MIB. 185 Consult FRF.13 [17] for more details. 187 2.2. Terminology 189 o CIR - The Committed Information Rate (CIR) is the subscriber 190 data rate (expressed in bits/second) that the network commits to 191 deliver under normal network conditions. [18] 193 o DLCI - Data Link Connection Identifier. [18] 195 o Logical Port - This term is used to model the Frame Relay 196 "interface" on a device. [18] 198 o NNI - Network to Network Interface. [18] 200 o Permanent Virtual Connection (PVC) - A virtual connection that 201 has its end-points and bearer capabilities defined at 202 subscription time. [18] 204 o Reference Point (RP) - The point of reference within the network 205 model at which the calculations or data collection takes place. 207 o UNI - User to Network Interface. [18] 209 2.3. Network Model 211 The basic model, as illustrated in figure 1 below, contains two frame 212 relay DTE endpoints connected to a network cloud via a frame relay 213 UNI interface. The network cloud can contain zero or more internal 214 frame relay NNI connections that interconnect multiple networks. The 215 calculations and data collection can be performed at any reference 216 point within the network. 218 +-------------+ +-------------+ 219 | Frame Relay | | Frame Relay | 220 | DTE Device | | DTE Device | 221 +------+------+ +------+------+ 222 | | 223 UNI UNI 224 Connection Connection 225 | | 226 +------+------+ NNI +-------------+ NNI +------+------+ 227 | Network A +------------+ Network B +------------+ Network C | 228 +-------------+ Connection +-------------+ Connection +-------------+ 230 Figure 1 231 Frame Relay Network Reference Model 233 2.4. Reference Points 235 The collection and calculations of the service level definitions 236 apply to two reference points within the network. These two points 237 are the locations where the frames are referenced in the collection 238 of the service level specific information. The reference points used 239 in the MIB are shown in figure 2 below. For completeness, the MIB 240 also allows for a proprietary reference point which can exist 241 anywhere in the network that is not a previously defined reference 242 point. Its meaning is insignificant unless defined by the device 243 manufacturer. 245 +---------------------------+ 246 |+-----------+ +-----------+| 247 || | |Measurement|| 248 ||Frame Relay---Engine --(Source RP)----+ 249 ||DTE | |(If Exists)|| | 250 |+-----------+ +-----------+| | 251 +---------------------------+ | 252 Frame Relay Source | 253 +------------------------------------------+ 254 | Frame Relay Network 255 | +----------------------------------+ 256 | | +------------------------------+ | 257 | | | +---------+ +---------+ | | 258 | | | | | | Traffic | | | 259 +--(Ingress RP)--- L1 / L2 --- Policing| | | 260 | | | Control | | Engine | | | 261 | | +---------+ +----|----+ | | 262 | | | | | 263 | | (Traffic Policing RP)| | 264 | +------------------|-----------+ | 265 | Ingress Node | | 266 | | | 267 | +-----------|-----------+ | 268 | | Intermediate Nodes | | 269 | +-----------|-----------+ | 270 | | | 271 | Egress Node | | 272 | +--------------|-----------+ | 273 | | (Egress Queue Input RP) | | 274 | | | | | 275 | | +-------+------+ | | 276 | | | Egress Queue | | | 277 | | +-------+------+ | | 278 | | | | | 279 | | (Egress Queue Output RP) | | 280 | +--------------|-----------+ | 281 +--------------------|-------------+ 282 Frame Relay Destination | 283 +---------------------------+ +-----------+ 284 |+-----------+ +-----------+| | 285 || | |Measurement|| | 286 ||Frame Relay---Engine --(Destination RP)--+ 287 ||DTE | |(If Exists)|| 288 |+-----------+ +-----------+| 289 +---------------------------+ 291 Figure 2 292 Reference Points (FRF.13 [17]) 294 The MIB variables frsldPvcCtrlSrcRP and frsldPvcCtrlDstRP allow the 295 user to view and, if supported, configure the reference points at 296 which the calculations occur. These variables are specific to the 297 device on which they are located. Frame relay devices act as both 298 frame sources and frame destinations. The definitions in this MIB 299 apply to the interaction of a pair of devices on the network path. 300 The same device can potentially use different reference points for 301 calculation and collection of the statistics based on whether the 302 referenced frame is sent or received by the device. When the device 303 is acting as a frame source, the value of frsldPvcCtrlSrcRP reflects 304 the reference point used for all source calculations pertaining to 305 the specified PVC. When the device is acting as a frame destination, 306 the value of frsldPvcCtrlDstRP reflects the reference point used for 307 all destination calculations pertaining to the specified PVC. 309 For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue 310 measurement domain as a domain in which measurement is performed 311 between an Ingress Reference Point and an Egress Queue Input 312 Reference Point. For this domain between a source device and a 313 destination device, the value of frsldPvcCtrlSrcRP for the source 314 device would be set to ingRP(2) and the value of frsldPvcCtrlDstRP 315 for the destination device would be set to eqiRP(4). While it is 316 usually the case that the reference points would simply swap when 317 looking at frames going in the opposite direction, there is no 318 requirement for them to do so. 320 2.5. Measurement Methodology 322 This document neither recommends nor suggests a method of 323 implementation. This is left to the device manufacturer and should 324 be independent of the data that is actually collected. 326 Periodic collection of this data can be performed through either 327 polling of the data table, use of the sample tables or use of the 328 user history group of RFC 2021 [19]. 330 2.6. Collection Location 332 In order to facilitate implementation independence, the location at 333 which the calculations are performed must be reported. In that these 334 statistics correlate information between two devices (a source- 335 destination node pair), there are multiple locations at which this 336 calculation can actually take place. These locations are specified 337 using the MIB variables frsldPvcCtrlDelayLoc and 338 frsldPvcCtrlDeliveryLoc. The potential values for these variables 339 have the following meanings: 341 o source - All calculations are performed at the source node 342 given statistics from the destination node. This means that 343 the source node collects information from the destination 344 node and reports values that are consistent with the current 345 state of the network. There may be some delay in updating 346 these values due to the cross-network correlation. However, 347 all values should be synchronized such that they act as if 348 collected simultaneously. The method of cross-network 349 communication is implementation independent. 351 The network node being queried is acting as the source node. 352 The network node at the far end of the PVC is the destination 353 node. The values of the "offered" statistics are associated 354 with those frames sent by this node. The values of the 355 "delivered" statistics are associated with those frames 356 actually reaching the destination node. The one-way delay 357 statistics are associated with packets sent from this node to 358 the far-end node. The round-trip delay statistics are 359 associated with packets sent by this node and received by 360 this node. 362 o destination - All calculations are performed at the 363 destination node given statistics from the source node. This 364 means that the destination node collects information from the 365 source node and reports values that are consistent with the 366 current state of the network. There may be some delay in 367 updating these values due to the cross-network correlation. 368 However, all values should be synchronized such that they act 369 as if collected simultaneously. The method of cross-network 370 communication is implementation independent. 372 The network node being queried is acting as the destination 373 node. The network node at the far end of the PVC is the 374 source node. The values of the "offered" statistics are 375 associated with those frames sent by the source node. The 376 values of the "delivered" statistics are associated with 377 those frames actually received by this node. The one-way 378 delay statistics are associated with packets sent by the far 379 end node and received by this node. The round-trip delay 380 statistics are associated with packets sent by the far end 381 node, received by the far end node and reported to this node. 383 o intermediate - All calculations are performed at some 384 intermediate node such as a probe. This means that both the 385 source and the destination node are referenced such that the 386 values reported are consistent with the current state of the 387 network. There may be some delay in updating these values due 388 to the cross-network correlation. However, all values should 389 be synchronized such that they act as if collected 390 simultaneously. The method of cross-network communication is 391 implementation independent. 393 The network node being queried is acting as neither the 394 source nor the destination node. The network node at one far 395 end of the PVC is the source node while the other far end 396 node is the destination node. The values of the "offered" 397 statistics are associated with those frames sent by the 398 source node. The values of the "delivered" statistics are 399 associated with those frames actually received by the 400 destination node. The one-way delay statistics are 401 associated with packets traveling from the source reference 402 point to the destination reference point. The round-trip 403 delay statistics are associated with packets that leave and 404 return to this node. 406 o distributed - There is no cross-network communication 407 performed by the device in the collection of statistics. The 408 values in the MIB objects on this device reflect only 409 information that this device knows about itself. The source 410 specific values reflect information about this device when it 411 acts as the source. Likewise, the destination specific 412 values reflect information about this device when it acts as 413 a destination. It is up to the network management software 414 to communicate to each device to collect the statistics. 416 The network node being queried is acting as both a source and 417 a destination node for separate source-destination node 418 pairs. The values of the "offered" statistics are associated 419 with those frames sent by this node and are valid in the 420 context of the source-destination node pair for which this 421 node is the source. The values of the "delivered" statistics 422 are associated with those frames actually received by this 423 node and are valid in the context of the source-destination 424 node pair for which this node is the destination. All delay 425 statistics for this node are deferred to the node at the far 426 end. 428 2.7. Use of MIB in Calculation of Service Level Definitions 430 The MIB variables can be used to calculate statistics defined in 431 FRF.13 [17]. For the following explanation, it is assumed that 432 statistics can both be collected from the same device, i.e. the 433 location type is not distributed. Should the location be 434 distributed, the manager should collect the source information from 435 the source node and the network information from the network node. 437 Otherwise, all information should be collected from the single device 438 representing the correct end of the PVC. 440 2.7.1. Delay 442 The frame transfer delay is defined as the amount of time elapsed, in 443 microseconds, from the time a frame exits the source to the time it 444 reaches the destination. The average delay can be found using the 445 frsldPvcDataDelayAvg MIB variable. The delay may be calculated as 446 either round trip or one way, and this information is held in the 447 frsldPvcCtrlDelayType MIB variable. Should the delay be calculated as 448 round trip, the value of frsldPvcDataDelayAvg represents the average 449 of the total delays of the round trips. In this case, the manager 450 should dive the value returned by the agent by two to obtain the 451 frame transfer delay. In the case that frsldPvcCtrlDelayType is 452 oneWay, the value of frsldPvcDataDelayAvg represents the average of 453 the frame transfer delays. 455 2.7.2. Frame Delivery Ratio 457 The frame delivery ratio is defined as the total number of frames 458 delivered to the destination divided by the frames offered by the 459 source. The destination values can be obtained using FrDeliveredC 460 and FrDeliveredE. The source values can be obtained using FrOfferedC 461 and FrOfferedE. 463 FrDeliveredC + FrDeliveredE 464 Frame Delivery Ratio = --------------------------- 465 FrOfferedC + FrOfferedE 467 FrDeliveredC 468 Committed Frame Delivery Ratio = ------------ 469 FrOfferedC 471 FrDeliveredE 472 Excess Frame Delivery Ratio = ------------ 473 FrOfferedE 475 2.7.3. Data Delivery Ratio 477 The data delivery ratio is defined as the total amount of data 478 delivered to the destination divided by the data offered by the 479 source. The destination values can be obtained using DataDeliveredC 480 and DataDeliveredE. The source values can be obtained using 481 DataOfferedC and DataOfferedE. 483 DataDeliveredC + DataDeliveredE 484 Data Delivery Ratio = ------------------------------- 485 DataOfferedC + DataOfferedE 487 DataDeliveredC 488 Committed Data Delivery Ratio = -------------- 489 DataOfferedC 491 DataDeliveredE 492 Excess Data Delivery Ratio = -------------- 493 DataOfferedE 495 2.7.4. Service Availability 497 Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0. 499 UnavailableTime 500 Otherwise, FRMTTR = --------------- 501 Unavailables 503 3. Relation to Other MIBs 505 There is no explicit relation to any other frame relay MIB nor are 506 any required to implement this MIB. However, there is a need for 507 knowledge of ifIndexes and some understanding of DLCIs. The ifIndex 508 information can be found in the IF-MIB which is required. The DLCI 509 information can be found in either the Frame Relay DTE MIB (RFC 2115) 510 [20] or the Frame Relay Network Services MIB (RFC 1604) [18]; 511 however, neither is required. 513 Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to 514 active(1) the system can be in one of the following three states: 516 (1) The respective DLCI is known and is active. This corresponds to a 517 state in which frPVCEndptRowStatus is active(1) and 518 frPVCEndptRcvdSigStatus is either active(2) or none(4) for the 519 Frame Relay Network Services MIB (RFC 1604) [18]. For the Frame 520 Relay DTE MIB, the same state is shown by frCircuitRowStatus of 521 active(1) and frCircuitState of active(2). 523 (2) The respective DLCI has not been created. This corresponds to a 524 state in which the row with either frPVCEndptDLCIIndex or 525 frCircuitDlci equal to the respective DLCI does not exist in 526 either the frPVCEndptTable or the frCircuitTable respectively. 528 (3) The respective DLCI has just been removed. This corresponds to a 529 state in which either frPVCEndptRowStatus is no longer active(1) 530 or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for 531 the Frame Relay Network Services MIB (RFC 1604) [18]. For the 532 Frame Relay DTE MIB, the same state is shown when either 533 frCircuitRowStatus is no longer active(1) or frCircuitState is no 534 longer active(2). 536 For the first case, the row in the frsldPvcDataTable will be filled. 537 If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective 538 DLCI is also 'active' the frsldPvcDataSampleTable and 539 frsldPvcAvailSampleTable will be filled as well. 541 For the second case, the respective rows will not be added to any of 542 the data or sample tables and frsldPvcCtrlStatus should be set to 543 notReady(3). 545 For the third case, frsldPvcCtrlDeleteOnPurge should direct the 546 behavior of the system. If all tables are purged, this case will be 547 equivalent to the second case above. Otherwise, frsldPvcCtrlStatus 548 should remain active(1). 550 4. Structure of the MIB 552 The FRSLD-MIB consists of the following components: 554 o frsldPvcCtrlTable 556 o frsldSmplCtrlTable 558 o frsldPvcDataTable 560 o frsldPvcDataSampleTable 562 o frsldPvcAvailSampleTable 564 o frsldCapabilities 566 Refer to the compliance statement defined within for a definition of 567 what objects MUST be implemented. 569 4.1. frsldPvcCtrlTable 571 The frsldPvcCtrlTable is the central control table for operations of 572 the Frame Relay Service Level Definitions MIB. It provides variables 573 to control the parameters required to calculate the objects in the 574 other tables. 576 A row in this table must exist in order for a row to exist in any 577 other table in this MIB. 579 4.2. frsldSmplCtrlTable 581 This is an optional table to allow control of sampling of the data in 582 the data table. 584 4.3. frsldPvcDataTable 586 This table contains the calculated data. It relies on configuration 587 from the control table. 589 4.4. frsldPvcDataSampleTable 591 This table contains samples of the delay and delivery information 592 from the data table. It relies on configuration from both the 593 control table and the sample control table. 595 4.5. frsldPvcAvailSampleTable 597 This table contains samples of the availability information from the 598 data table. It relies on configuration from both the control table 599 and the sample control table. 601 4.6. frsldCapabilities 603 This is a group of objects that define write capabilities of the 604 read-create objects in the tables above. 606 5. Object Definitions 608 FRSLD-MIB DEFINITIONS ::= BEGIN 610 IMPORTS 611 MODULE-IDENTITY, OBJECT-TYPE, 612 Counter32, Gauge32, Integer32, 613 experimental, BITS FROM SNMPv2-SMI 614 TEXTUAL-CONVENTION, RowStatus, 615 TimeStamp FROM SNMPv2-TC 616 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 617 ifIndex FROM IF-MIB; 619 frsldMIB MODULE-IDENTITY 620 LAST-UPDATED "0002060000Z" 621 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" 622 CONTACT-INFO 623 "IETF Frame Relay Service MIB (frnetmib) Working Group 624 General Discussion:frnetmib@sunroof.eng.sun.com 625 To Subscribe: majordomo@sunroof.eng.sun.com 626 In Body: subscribe frnetmib 628 Robert Steinberger 629 Postal: Paradyne Networks 630 Mailstop: LG-132 631 8545 126th Avenue North 632 Largo, FL USA 33773 633 TEL: +1 727 530 2395 634 FAX +1 727 532 5244 635 E-mail: rsteinberger@paradyne.com 637 Orly Nicklass, Ph.D 638 Postal: RAD Data Communications Ltd. 639 12 Hanechoshet Street 640 Tel Aviv, Israel 69710 641 TEL: +972 3 6459588 642 FAX: +972 3 6472675 643 E-mail: orly@radmail.rad.co.il" 644 DESCRIPTION 645 "The MIB module to describe generic objects for 646 Frame Relay Service Level Definitions." 647 REVISION "0002060000Z" 648 DESCRIPTION 649 "o Published as draft-ietf-frnetmib-frmrelay-service- 650 00.txt 651 o Added frsldCapabilities group to define the 652 read/write capabilities 653 o Changed location to experimental 104 654 o Changed name of frsldTables to frsldObjects 655 o Changed MAX-ACCESS of frsldPvcCtrlDelayType to 656 read-create 657 o Unlinked frsldPvcDataDelayMin, frsldPvcDataDelayMax, 658 and frsldPvcDataDelayAvg from the sample period" 660 REVISION "9909030000Z" 661 DESCRIPTION 662 "o Added range to frsldPvcCtrlPacketFreq 663 o Changed range of frsldPvcCtrlDelayTimeOut to match 664 that of frsldPvcCtrlPacketFreq 665 o Clarified what happens when frsldPvcCtrlPacketFreq 666 is set to zero 667 o Changed delay to count in microseconds instead of 668 milliseconds 669 o Created a new sample control table and moved sample 670 specific information into it. 671 o Changed the prefix of 'frsldPvcCtrl' object name to 672 'frsldSmplCtrl' 673 o Added the sample control index to the indices of the 674 sample tables 675 o Changed all occasions of TimeTicks to TimeStamp 676 o Added frsldPvcCtrlPurge to aide in control validity 677 of information due to PVC status changes 678 o Added frsldPvcCtrlDeleteOnPurge object 679 o Added frsldPvcCtrlLastPurgeTime object 680 o Added units clauses to all time related fields. 681 o Reworded the 'change in' syntax to be more explicit" 682 ::= { experimental 104 } 684 FrsldLocation ::= TEXTUAL-CONVENTION 685 STATUS current 686 DESCRIPTION 687 "The location at which the calculations occur." 688 SYNTAX INTEGER { 689 source(1), -- Calculations occur at the 690 -- source device. 691 destination(2), -- Calculations occur at the 692 -- destination device. 693 intermediate(3), -- Calculations occur at some 694 -- intermediate device such as 695 -- a probe. 696 distributed(4) -- Calculations are distributed 697 -- between source and destination 698 -- devices. 699 } 701 FrsldRP ::= TEXTUAL-CONVENTION 702 STATUS current 703 DESCRIPTION 704 "Reference points for calculation of service 705 level definitions." 706 SYNTAX INTEGER { 707 srcRP(1), -- Source Reference Point 708 ingRP(2), -- Ingress Reference Point 709 tpRP(3), -- Traffic Policing Reference Point 710 eqiRP(4), -- Egress Queue Input Reference Point 711 eqoRP(5), -- Egress Queue Output Reference Point 712 desRP(6), -- Destination Reference Point 713 propRP(7) -- Proprietary Reference Point 714 } 716 frsldObjects OBJECT IDENTIFIER ::= { frsldMIB 1 } 717 frsldCapabilities OBJECT IDENTIFIER ::= { frsldMIB 2 } 718 frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 3 } 719 -- The Frame Relay Service Level Definitions PVC Control Table 720 -- 721 -- This table is used to define and display the parameters of 722 -- service level definitions on individual PVCs. 724 frsldPvcCtrlTable OBJECT-TYPE 725 SYNTAX SEQUENCE OF FrsldPvcCtrlEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "The Frame Relay Service Level Definitions 730 PVC control table." 731 ::= { frsldObjects 1 } 733 frsldPvcCtrlEntry OBJECT-TYPE 734 SYNTAX FrsldPvcCtrlEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "An entry in the Frame Relay Service Level 739 Definitions PVC control table." 740 INDEX { ifIndex, frsldPvcCtrlDlci } 741 ::= { frsldPvcCtrlTable 1 } 743 FrsldPvcCtrlEntry ::= 744 SEQUENCE { 745 -- 746 -- Index Control Variables 747 -- 748 frsldPvcCtrlDlci Integer32, 749 frsldPvcCtrlStatus RowStatus, 750 -- 751 -- Service Level Definitions Setup Variables 752 -- 753 frsldPvcCtrlSrcRP FrsldRP, 754 frsldPvcCtrlDstRP FrsldRP, 755 frsldPvcCtrlPacketFreq Integer32, 756 -- 757 -- Delay Specific Setup Variables 758 -- 759 frsldPvcCtrlDelayLoc FrsldLocation, 760 frsldPvcCtrlDelayFrSize Integer32, 761 frsldPvcCtrlDelayType INTEGER, 762 frsldPvcCtrlDelayTimeOut Integer32, 763 -- 764 -- Delivery Specific Setup Variables 765 -- 766 frsldPvcCtrlDeliveryLoc FrsldLocation, 767 -- 768 -- Data Persistence Control Variables 769 -- 770 frsldPvcCtrlPurge Integer32, 771 frsldPvcCtrlDeleteOnPurge INTEGER, 772 frsldPvcCtrlLastPurgeTime TimeStamp 773 } 775 frsldPvcCtrlDlci OBJECT-TYPE 776 SYNTAX Integer32 (16..4194303) 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "The value of this object is equal to the DLCI 781 value for this PVC." 782 ::= { frsldPvcCtrlEntry 1 } 784 frsldPvcCtrlStatus OBJECT-TYPE 785 SYNTAX RowStatus 786 MAX-ACCESS read-create 787 STATUS current 788 DESCRIPTION 789 "The status of the current row. This object is 790 used to add, delete, and disable rows in this 791 table. When the status changes to active the 792 first time, a row will also be added to the data 793 table below. This row should not be removed until 794 the status is changed to deleted. 796 When this object is set to delete, all associated 797 sample and data table rows will also be deleted. 798 When this object is changed from active to any 799 other valid value, the defined purge behavior will 800 affect the data and sample tables. 802 The rows added to this table must have a valid 803 ifIndex and an ifType related to frame relay." 804 ::= { frsldPvcCtrlEntry 2 } 806 frsldPvcCtrlSrcRP OBJECT-TYPE 807 SYNTAX FrsldRP 808 MAX-ACCESS read-create 809 STATUS current 810 DESCRIPTION 811 "The reference point this PVC uses for calculation 812 when it is acting as a source. This object 813 together with frsldPvcCtrlDstRp define the 814 measurement domain." 816 ::= { frsldPvcCtrlEntry 3 } 818 frsldPvcCtrlDstRP OBJECT-TYPE 819 SYNTAX FrsldRP 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "The reference point this PVC uses for calculation 824 when it is acting as a destination. This object 825 together with frsldPvcCtrlDstRP define the 826 measurement domain." 827 ::= { frsldPvcCtrlEntry 4 } 829 frsldPvcCtrlPacketFreq OBJECT-TYPE 830 SYNTAX Integer32 (0..3600) 831 UNITS "seconds" 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "The frequency in seconds between initiation of 836 specialized packets used to collect delay and / or 837 delivery information as supported by the device. 838 A value of zero indicates that no packets will 839 be sent." 840 DEFVAL { 60 } 841 ::= { frsldPvcCtrlEntry 5 } 843 frsldPvcCtrlDelayLoc OBJECT-TYPE 844 SYNTAX FrsldLocation 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "The location at which the calculation of delay for 849 this PVC occurs." 850 ::= { frsldPvcCtrlEntry 6 } 852 frsldPvcCtrlDelayFrSize OBJECT-TYPE 853 SYNTAX Integer32 (1..8188) 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "The size of the payload in the frame used for 858 calculation of network delay." 859 DEFVAL { 128 } 860 ::= { frsldPvcCtrlEntry 7 } 862 frsldPvcCtrlDelayType OBJECT-TYPE 863 SYNTAX INTEGER { 864 oneWay(1), 865 roundTrip(2) 866 } 867 MAX-ACCESS read-create 868 STATUS current 869 DESCRIPTION 870 "The type of delay measurement performed." 871 ::= { frsldPvcCtrlEntry 8 } 873 frsldPvcCtrlDelayTimeOut OBJECT-TYPE 874 SYNTAX Integer32 (1..3600) 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "A delay frame will count as a missed poll if 879 it is not updated in the time specified by 880 frsldPvcCtrlDelayTimeOut." 881 DEFVAL { 60 } 882 ::= { frsldPvcCtrlEntry 9 } 884 frsldPvcCtrlDeliveryLoc OBJECT-TYPE 885 SYNTAX FrsldLocation 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "The location at which the collection of delivery 890 parameters for this PVC occur." 891 ::= { frsldPvcCtrlEntry 10 } 893 frsldPvcCtrlPurge OBJECT-TYPE 894 SYNTAX Integer32 (0..172800) -- up to 48 hours 895 MAX-ACCESS read-create 896 STATUS current 897 DESCRIPTION 898 "This object defines the amount of time the device 899 will wait, after discovering either that a DLCI 900 does not exist or it was deleted, prior to 901 automatically purging the history in the sample 902 tables and resetting the data in the data tables 903 to all zeroes." 904 DEFVAL { 0 } 905 ::= { frsldPvcCtrlEntry 11 } 907 frsldPvcCtrlDeleteOnPurge OBJECT-TYPE 908 SYNTAX INTEGER { 909 none(1), 910 sampleContols(2), 911 all(3) 913 } 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "This object defines whether rows will 918 automatically be deleted from the tables 919 when the information is purged. 921 - A value of none(1) indicates that no rows 922 will deleted. The last known values will 923 be preserved. 924 - A value of sampleControls(2) indicates 925 that all associated sample control rows 926 will be deleted. 927 - A value of all(3) indicates that all 928 associated rows should be deleted." 929 DEFVAL { all } 930 ::= { frsldPvcCtrlEntry 12 } 932 frsldPvcCtrlLastPurgeTime OBJECT-TYPE 933 SYNTAX TimeStamp 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "This object returns the value of sysUpTime 938 at the time the information was last purged. 939 This value should be set to the sysUpTime 940 upon setting frsldPvcCtrlStatus to 941 active(1). If frsldPvcCtrlStatus has never 942 been active(1), this object should return 0." 943 DEFVAL { 0 } 944 ::= { frsldPvcCtrlEntry 13 } 946 -- The Frame Relay Service Level Definitions Sampling Control 947 -- Table 948 -- 949 -- This table is used to define the sample control parameters 950 -- of service level definitions on individual PVCs. 952 frsldSmplCtrlTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF FrsldSmplCtrlEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "The Frame Relay Service Level Definitions 958 sampling control table." 959 ::= { frsldObjects 2 } 961 frsldSmplCtrlEntry OBJECT-TYPE 962 SYNTAX FrsldSmplCtrlEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "An entry in the Frame Relay Service Level 967 Definitions sample control table." 968 INDEX { ifIndex, frsldPvcCtrlDlci, frsldSmplIdx } 969 ::= { frsldSmplCtrlTable 1 } 971 FrsldSmplCtrlEntry ::= 972 SEQUENCE { 973 -- 974 -- Index Control Variables 975 -- 976 frsldSmplIdx Integer32, 977 frsldSmplCtrlStatus RowStatus, 978 -- 979 -- Sampling Control Variables: Delay and Delivery 980 -- 981 frsldSmplCtrlDataColPeriod Integer32, 982 frsldSmplCtrlDataBuckets Integer32, 983 frsldSmplCtrlDataBucketsGranted Integer32, 984 -- 985 -- Sampling Control Variables: Availability 986 -- 987 frsldSmplCtrlAvailColPeriod Integer32, 988 frsldSmplCtrlAvailBuckets Integer32, 989 frsldSmplCtrlAvailBucketsGranted Integer32 990 } 992 frsldSmplIdx OBJECT-TYPE 993 SYNTAX Integer32 (1..256) 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "The unique index for this row in the 998 sample control table." 999 ::= { frsldSmplCtrlEntry 1 } 1001 frsldSmplCtrlStatus OBJECT-TYPE 1002 SYNTAX RowStatus 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "The status of the current row. This object is 1007 used to add, delete, and disable rows in this 1008 table. This row should not be removed until the 1009 status is changed to deleted. When the status 1010 changes to active, the collection in the sample 1011 tables below will be activated. 1013 The rows added to this table must have a valid 1014 ifIndex, an ifType related to frame relay and 1015 frsldPvcCtrlDlci must exist for the specified 1016 ifIndex." 1017 ::= { frsldSmplCtrlEntry 2 } 1019 frsldSmplCtrlDataColPeriod OBJECT-TYPE 1020 SYNTAX Integer32 (1..2147483647) 1021 UNITS "seconds" 1022 MAX-ACCESS read-create 1023 STATUS current 1024 DESCRIPTION 1025 "The amount of time in seconds that defines a 1026 period of collection of the delay and / or 1027 delivery information. At the end of each period, 1028 the delay and / or delivery statistics will be 1029 sampled and a row is added to the data sample 1030 table." 1031 DEFVAL { 900 } -- 15 Minutes 1032 ::= { frsldSmplCtrlEntry 3 } 1034 frsldSmplCtrlDataBuckets OBJECT-TYPE 1035 SYNTAX Integer32 (0..65535) 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "The number of discrete buckets over which the delay 1040 and delivery data statistics are sampled. 1042 A value of zero indicates that no samples are 1043 desired for the delay and delivery statistics. 1045 When this object is created or modified, the device 1046 should attempt to set the frsldSmplCtrlDataBuckets- 1047 Granted to a value as close as is possible 1048 depending upon the implementation and the available 1049 resources." 1050 DEFVAL { 60 } 1051 ::= { frsldSmplCtrlEntry 4 } 1053 frsldSmplCtrlDataBucketsGranted OBJECT-TYPE 1054 SYNTAX Integer32 (0..65535) 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "The number of discrete buckets granted. This 1059 object will return 0 until frsldSmplCtrlStatus is 1060 set to active(1). At that time the buckets will be 1061 allocated depending upon implementation and 1062 available resources." 1063 ::= { frsldSmplCtrlEntry 5 } 1065 frsldSmplCtrlAvailColPeriod OBJECT-TYPE 1066 SYNTAX Integer32 (1..2147483647) 1067 UNITS "seconds" 1068 MAX-ACCESS read-create 1069 STATUS current 1070 DESCRIPTION 1071 "The amount of time in seconds that defines a 1072 period of collection of the availability 1073 statistics. At the end of each period, the 1074 availability statistics will be sampled. 1075 The value at the last sample will be subtracted 1076 from the current value, and the difference will 1077 be stored in a new row in the availability 1078 sample table." 1079 DEFVAL { 86400 } -- 24 hours 1080 ::= { frsldSmplCtrlEntry 6 } 1082 frsldSmplCtrlAvailBuckets OBJECT-TYPE 1083 SYNTAX Integer32 (0..65535) 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "The number of discrete buckets over which the 1088 availability statistics are sampled. 1090 A value of zero indicates that no samples are 1091 desired for the availability statistics. 1093 When this object is created or modified, the device 1094 should attempt to set the frsldSmplCtrlAvail- 1095 BucketsGranted to a value as close as is possible 1096 depending upon the implementation and the available 1097 resources." 1098 DEFVAL { 31 } -- One month 1099 ::= { frsldSmplCtrlEntry 7 } 1101 frsldSmplCtrlAvailBucketsGranted OBJECT-TYPE 1102 SYNTAX Integer32 (0..65535) 1103 MAX-ACCESS read-only 1104 STATUS current 1105 DESCRIPTION 1106 "The number of discrete buckets granted. This 1107 object will return 0 until frsldPvcCtrlStatus is 1108 set to active(1). At that time the buckets will be 1109 allocated depending upon the implementation and 1110 available resources." 1111 ::= { frsldSmplCtrlEntry 8 } 1113 -- The Frame Relay Service Level Definitions PVC Data Table 1114 -- 1115 -- This table contains the accumulated values of 1116 -- the collected data. This table is the table that should 1117 -- be referenced by external polling mechanism should time 1118 -- based polling be desired. 1120 frsldPvcDataTable OBJECT-TYPE 1121 SYNTAX SEQUENCE OF FrsldPvcDataEntry 1122 MAX-ACCESS not-accessible 1123 STATUS current 1124 DESCRIPTION 1125 "The Frame Relay Service Level Definitions 1126 data table." 1127 ::= { frsldObjects 3 } 1129 frsldPvcDataEntry OBJECT-TYPE 1130 SYNTAX FrsldPvcDataEntry 1131 MAX-ACCESS not-accessible 1132 STATUS current 1133 DESCRIPTION 1134 "An entry in the Frame Relay Service Level 1135 Definitions data table." 1136 INDEX { ifIndex, frsldPvcCtrlDlci } 1137 ::= { frsldPvcDataTable 1 } 1139 FrsldPvcDataEntry ::= 1140 SEQUENCE { 1141 frsldPvcDataDelayMin Gauge32, 1142 frsldPvcDataDelayMax Gauge32, 1143 frsldPvcDataDelayAvg Gauge32, 1144 frsldPvcDataMissedPolls Counter32, 1145 frsldPvcDataFrDeliveredC Counter32, 1146 frsldPvcDataFrDeliveredE Counter32, 1147 frsldPvcDataFrOfferedC Counter32, 1148 frsldPvcDataFrOfferedE Counter32, 1149 frsldPvcDataDataDeliveredC Counter32, 1150 frsldPvcDataDataDeliveredE Counter32, 1151 frsldPvcDataDataOfferedC Counter32, 1152 frsldPvcDataDataOfferedE Counter32, 1153 frsldPvcDataUnavailableTime TimeStamp, 1154 frsldPvcDataUnavailables Counter32 1155 } 1157 frsldPvcDataDelayMin OBJECT-TYPE 1158 SYNTAX Gauge32 1159 UNITS "microseconds" 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The minimum delay reported in microseconds. 1165 A value of zero means that no data is available." 1166 ::= { frsldPvcDataEntry 1 } 1168 frsldPvcDataDelayMax OBJECT-TYPE 1169 SYNTAX Gauge32 1170 UNITS "microseconds" 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "The largest delay reported in microseconds. 1176 A value of zero means that no data is available." 1177 ::= { frsldPvcDataEntry 2 } 1179 frsldPvcDataDelayAvg OBJECT-TYPE 1180 SYNTAX Gauge32 1181 UNITS "microseconds" 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The average delay reported in microseconds. 1187 A value of zero means that no data is available." 1188 ::= { frsldPvcDataEntry 3 } 1190 frsldPvcDataMissedPolls OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "The total number of polls that have been missed." 1196 ::= { frsldPvcDataEntry 4 } 1198 frsldPvcDataFrDeliveredC OBJECT-TYPE 1199 SYNTAX Counter32 1200 MAX-ACCESS read-only 1201 STATUS current 1202 DESCRIPTION 1203 "The number of frames that were delivered within 1204 CIR. If the location of calculation is 1205 distributed(4), this value represents the number of 1206 committed frames the far end sent that reached this 1207 device." 1208 ::= { frsldPvcDataEntry 5 } 1210 frsldPvcDataFrDeliveredE OBJECT-TYPE 1211 SYNTAX Counter32 1212 MAX-ACCESS read-only 1213 STATUS current 1214 DESCRIPTION 1215 "The number of frames that were delivered in excess 1216 of the CIR. If the location of calculation is 1217 distributed(4), this value represents the number of 1218 excess frames the far end sent that reached this 1219 device." 1220 ::= { frsldPvcDataEntry 6 } 1222 frsldPvcDataFrOfferedC OBJECT-TYPE 1223 SYNTAX Counter32 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The number of frames that were offered with CIR. 1228 If the location of calculation is distributed(4), 1229 this value represents the number of committed 1230 frames the near end sent." 1231 ::= { frsldPvcDataEntry 7 } 1233 frsldPvcDataFrOfferedE OBJECT-TYPE 1234 SYNTAX Counter32 1235 MAX-ACCESS read-only 1236 STATUS current 1237 DESCRIPTION 1238 "The number of frames that were offered in excess 1239 of the CIR. If the location of calculation is 1240 distributed(4), this value represents the number of 1241 excess frames the near end sent." 1242 ::= { frsldPvcDataEntry 8 } 1244 frsldPvcDataDataDeliveredC OBJECT-TYPE 1245 SYNTAX Counter32 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "The number of octets that were delivered within 1250 CIR. If the location of calculation is 1251 distributed(4), this value represents the number of 1252 committed octets the far end sent that reached this 1253 device." 1254 ::= { frsldPvcDataEntry 9 } 1256 frsldPvcDataDataDeliveredE OBJECT-TYPE 1257 SYNTAX Counter32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The number of octets that were delivered in excess 1262 of the CIR. If the location of calculation is 1263 distributed(4), this value represents the number of 1264 excess octets the far end sent that reached this 1265 device." 1266 ::= { frsldPvcDataEntry 10 } 1268 frsldPvcDataDataOfferedC OBJECT-TYPE 1269 SYNTAX Counter32 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The number of octets that were offered with CIR. 1274 If the location of calculation is distributed(4), 1275 this value represents the number of committed 1276 octets the near end sent." 1277 ::= { frsldPvcDataEntry 11 } 1279 frsldPvcDataDataOfferedE OBJECT-TYPE 1280 SYNTAX Counter32 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "The number of octets that were offered in excess 1285 of the CIR. If the location of calculation is 1286 distributed(4), this value represents the number of 1287 excess octets the near end sent." 1288 ::= { frsldPvcDataEntry 12 } 1290 frsldPvcDataUnavailableTime OBJECT-TYPE 1291 SYNTAX TimeStamp 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "The amount of time this PVC was declared 1296 unavailable for any reason." 1297 ::= { frsldPvcDataEntry 13 } 1299 frsldPvcDataUnavailables OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "The number of times this PVC was declared 1305 unavailable for any reason." 1306 ::= { frsldPvcDataEntry 14 } 1308 -- The Frame Relay Service Level Definitions PVC 1309 -- Data Sample Table 1310 -- 1311 -- This table contains the sampled delay and delivery 1312 -- information. 1314 frsldPvcDataSampleTable OBJECT-TYPE 1315 SYNTAX SEQUENCE OF FrsldPvcDataSampleEntry 1316 MAX-ACCESS not-accessible 1317 STATUS current 1318 DESCRIPTION 1319 "The Frame Relay Service Level Definitions 1320 data sample table." 1321 ::= { frsldObjects 4 } 1323 frsldPvcDataSampleEntry OBJECT-TYPE 1324 SYNTAX FrsldPvcDataSampleEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "An entry in the Frame Relay Service Level 1329 Definitions data sample table." 1330 INDEX { ifIndex, frsldPvcCtrlDlci, 1331 frsldSmplIdx, frsldPvcDataSmplIdx } 1332 ::= { frsldPvcDataSampleTable 1 } 1334 FrsldPvcDataSampleEntry ::= 1335 SEQUENCE { 1336 frsldPvcDataSmplIdx Integer32, 1337 frsldPvcDataDelaySmplMin Gauge32, 1338 frsldPvcDataDelaySmplMax Gauge32, 1339 frsldPvcDataDelaySmplAvg Gauge32, 1340 frsldPvcDataSmplMissedPolls Gauge32, 1341 frsldPvcDataSmplFrDeliveredC Gauge32, 1342 frsldPvcDataSmplFrDeliveredE Gauge32, 1343 frsldPvcDataSmplFrOfferedC Gauge32, 1344 frsldPvcDataSmplFrOfferedE Gauge32, 1345 frsldPvcDataSmplDataDeliveredC Gauge32, 1346 frsldPvcDataSmplDataDeliveredE Gauge32, 1347 frsldPvcDataSmplDataOfferedC Gauge32, 1348 frsldPvcDataSmplDataOfferedE Gauge32, 1349 frsldPvcDataSmplStartTime TimeStamp, 1350 frsldPvcDataSmplEndTime TimeStamp 1351 } 1353 frsldPvcDataSmplIdx OBJECT-TYPE 1354 SYNTAX Integer32 (1..2147483647) 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "The bucket index of the current sample. This 1359 increments once for each new bucket in the 1360 table." 1361 ::= { frsldPvcDataSampleEntry 1 } 1363 frsldPvcDataDelaySmplMin OBJECT-TYPE 1364 SYNTAX Gauge32 1365 UNITS "microseconds" 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "The minimum delay reported in microseconds measured 1370 for any information packet that arrived in this 1371 interval. 1373 A value of zero means that no data is available." 1374 ::= { frsldPvcDataSampleEntry 2 } 1376 frsldPvcDataDelaySmplMax OBJECT-TYPE 1377 SYNTAX Gauge32 1378 UNITS "microseconds" 1379 MAX-ACCESS read-only 1380 STATUS current 1381 DESCRIPTION 1382 "The largest delay reported in microseconds measured 1383 for any information packet that arrived in this 1384 interval. 1386 A value of zero means that no data is available." 1387 ::= { frsldPvcDataSampleEntry 3 } 1389 frsldPvcDataDelaySmplAvg OBJECT-TYPE 1390 SYNTAX Gauge32 1391 UNITS "microseconds" 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The average delay reported in microseconds measured 1396 for all delay packets that arrived in this 1397 interval. 1399 A value of zero means that no data is available." 1400 ::= { frsldPvcDataSampleEntry 4 } 1402 frsldPvcDataSmplMissedPolls OBJECT-TYPE 1403 SYNTAX Gauge32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The total number of polls that were missed during 1408 this polling period." 1409 ::= { frsldPvcDataSampleEntry 5 } 1411 frsldPvcDataSmplFrDeliveredC OBJECT-TYPE 1412 SYNTAX Gauge32 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The change in the value of frsldPvcDataFr- 1417 DeliveredC during this sample interval. 1418 The value at the last sample will be subtracted 1419 from the current value, and the difference will 1420 be contained in this object." 1421 ::= { frsldPvcDataSampleEntry 6 } 1423 frsldPvcDataSmplFrDeliveredE OBJECT-TYPE 1424 SYNTAX Gauge32 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "The change in the value of frsldPvcDataFr- 1429 DeliveredE during this sample interval. 1430 The value at the last sample will be subtracted 1431 from the current value, and the difference will 1432 be contained in this object." 1433 ::= { frsldPvcDataSampleEntry 7 } 1435 frsldPvcDataSmplFrOfferedC OBJECT-TYPE 1436 SYNTAX Gauge32 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The change in the value of frsldPvcDataFrOfferedC 1441 during this sample interval. The value at the last 1442 sample will be subtracted from the current value, 1443 and the difference will be contained in this 1444 object." 1446 ::= { frsldPvcDataSampleEntry 8 } 1448 frsldPvcDataSmplFrOfferedE OBJECT-TYPE 1449 SYNTAX Gauge32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The change in the value of frsldPvcDataFrOfferedE 1454 during this sample interval. The value at the last 1455 sample will be subtracted from the current value, 1456 and the difference will be contained in this 1457 object." 1458 ::= { frsldPvcDataSampleEntry 9 } 1460 frsldPvcDataSmplDataDeliveredC OBJECT-TYPE 1461 SYNTAX Gauge32 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The change in the value of frsldPvcDataData- 1466 DeliveredC during this sample interval. 1467 The value at the last sample will be subtracted 1468 from the current value, and the difference will 1469 be contained in this object." 1470 ::= { frsldPvcDataSampleEntry 10 } 1472 frsldPvcDataSmplDataDeliveredE OBJECT-TYPE 1473 SYNTAX Gauge32 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "The change in the value of frsldPvcDataData- 1478 DeliveredE during this sample interval. 1479 The value at the last sample will be subtracted 1480 from the current value, and the difference will 1481 be contained in this object." 1483 ::= { frsldPvcDataSampleEntry 11 } 1485 frsldPvcDataSmplDataOfferedC OBJECT-TYPE 1486 SYNTAX Gauge32 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "The change in the value of frsldPvcDataDataOfferedC 1491 during this sample interval. The value at the last 1492 sample will be subtracted from the current value, 1493 and the difference will be contained in this 1494 object." 1496 ::= { frsldPvcDataSampleEntry 12 } 1498 frsldPvcDataSmplDataOfferedE OBJECT-TYPE 1499 SYNTAX Gauge32 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "The change in the value of frsldPvcDataData- 1504 OfferedE during this sample interval. 1505 The value at the last sample will be subtracted 1506 from the current value, and the difference will 1507 be contained in this object." 1509 ::= { frsldPvcDataSampleEntry 13 } 1511 frsldPvcDataSmplStartTime OBJECT-TYPE 1512 SYNTAX TimeStamp 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "The value of sysUpTime when this sample period 1517 started." 1518 ::= { frsldPvcDataSampleEntry 14 } 1520 frsldPvcDataSmplEndTime OBJECT-TYPE 1521 SYNTAX TimeStamp 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "The value of sysUpTime when this sample period 1526 ended. No data will be reported and the row will 1527 not appear in the table until the sample has 1528 been collected." 1529 ::= { frsldPvcDataSampleEntry 15 } 1531 -- The Frame Relay Service Level Definitions PVC 1532 -- Availability Sample Table 1533 -- 1534 -- This table contains the sampled availability information. 1536 frsldPvcAvailSampleTable OBJECT-TYPE 1537 SYNTAX SEQUENCE OF FrsldPvcAvailSampleEntry 1538 MAX-ACCESS not-accessible 1539 STATUS current 1540 DESCRIPTION 1541 "The Frame Relay Service Level Definitions 1542 availability sample table." 1543 ::= { frsldObjects 5 } 1545 frsldPvcAvailSampleEntry OBJECT-TYPE 1546 SYNTAX FrsldPvcAvailSampleEntry 1547 MAX-ACCESS not-accessible 1548 STATUS current 1549 DESCRIPTION 1550 "An entry in the Frame Relay Service Level 1551 Definitions availability sample table." 1552 INDEX { ifIndex, frsldPvcCtrlDlci, frsldSmplIdx, 1553 frsldPvcAvailSmplIdx } 1554 ::= { frsldPvcAvailSampleTable 1 } 1556 FrsldPvcAvailSampleEntry ::= 1557 SEQUENCE { 1558 frsldPvcAvailSmplIdx Integer32, 1559 frsldPvcAvailSmplUnavailableTime TimeStamp, 1560 frsldPvcAvailSmplUnavailables Gauge32, 1561 frsldPvcAvailSmplStartTime TimeStamp, 1562 frsldPvcAvailSmplEndTime TimeStamp 1563 } 1565 frsldPvcAvailSmplIdx OBJECT-TYPE 1566 SYNTAX Integer32 (1..2147483647) 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "The bucket index of the current sample. This 1571 increments once for each new bucket in the 1572 table." 1573 ::= { frsldPvcAvailSampleEntry 1 } 1575 frsldPvcAvailSmplUnavailableTime OBJECT-TYPE 1576 SYNTAX TimeStamp 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "The change in the value of frsldPvcData- 1581 UnavailableTime during this sample interval. 1583 The value at the last sample will be subtracted 1584 from the current value, and the difference will 1585 be contained in this object." 1587 ::= { frsldPvcAvailSampleEntry 2 } 1589 frsldPvcAvailSmplUnavailables OBJECT-TYPE 1590 SYNTAX Gauge32 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "The change in the value of frsldPvcData- 1595 Unavailables during this sample interval. 1596 The value at the last sample will be subtracted 1597 from the current value, and the difference will 1598 be contained in this object." 1599 ::= { frsldPvcAvailSampleEntry 3 } 1601 frsldPvcAvailSmplStartTime OBJECT-TYPE 1602 SYNTAX TimeStamp 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The value of sysUpTime when this sample period 1607 started." 1608 ::= { frsldPvcAvailSampleEntry 4 } 1610 frsldPvcAvailSmplEndTime OBJECT-TYPE 1611 SYNTAX TimeStamp 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "The value of sysUpTime when this sample period 1616 ended. No data will be reported and the row will 1617 not appear in the table until the sample has 1618 been collected." 1619 ::= { frsldPvcAvailSampleEntry 5 } 1621 -- Capabilities Group 1623 -- This group provides capabilities objects for the tables 1624 -- that control configuration. 1626 frsldPvcCtrlWriteCaps OBJECT-TYPE 1627 SYNTAX BITS { 1628 frsldPvcCtrlStatus(0), 1629 frsldPvcCtrlSrcRP(1), 1630 frsldPvcCtrlDstRP(2), 1631 frsldPvcCtrlPacketFreq(3), 1632 frsldPvcCtrlDelayLoc(4), 1633 frsldPvcCtrlDelayFrSize(5), 1634 frsldPvcCtrlDelayType(6), 1635 frsldPvcCtrlDelayTimeOut(7), 1636 frsldPvcCtrlDeliveryLoc(8), 1637 frsldPvcCtrlPurge(9), 1638 frsldPvcCtrlDeleteOnPurge(10) 1639 } 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "This object specifies the write capabilities 1644 for the read-create objects of the PVC Control 1645 table. If the corresponding bit is enabled (1), 1646 the agent supports writes to that object." 1647 ::= { frsldCapabilities 1 } 1649 frsldSmplCtrlWriteCaps OBJECT-TYPE 1650 SYNTAX BITS { 1651 frsldSmplCtrlStatus(0), 1652 frsldSmplCtrlDataColPeriod(1), 1653 frsldSmplCtrlDataBuckets(2), 1654 frsldSmplCtrlAvailColPeriod(3), 1655 frsldSmplCtrlAvailBuckets(4) 1656 } 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "This object specifies the write capabilities 1661 for the read-create objects of the Sample Control 1662 table. If the corresponding bit is enabled (1), 1663 the agent supports writes to that object." 1664 ::= { frsldCapabilities 2 } 1666 -- Conformance Information 1668 frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } 1669 frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } 1671 -- 1672 -- Compliance Statements 1673 -- 1675 frsldCompliance MODULE-COMPLIANCE 1676 STATUS current 1677 DESCRIPTION 1678 "The compliance statement for SNMPv2 entities 1679 which support Frame Relay Service Level 1680 Definitions." 1681 MODULE -- this module 1682 MANDATORY-GROUPS { frsldPvcReqCtrlGroup, 1683 frsldPvcReqDataGroup, 1684 frsldCapabilitiesGroup} 1686 OBJECT frsldPvcCtrlSrcRP 1687 MIN-ACCESS read-only 1688 DESCRIPTION 1689 "Write access is not required." 1691 OBJECT frsldPvcCtrlDstRP 1692 MIN-ACCESS read-only 1693 DESCRIPTION 1694 "Write access is not required." 1696 OBJECT frsldPvcCtrlDelayFrSize 1697 MIN-ACCESS read-only 1698 DESCRIPTION 1699 "Write access is not required." 1701 OBJECT frsldPvcCtrlDelayType 1702 MIN-ACCESS read-only 1703 DESCRIPTION 1704 "Write access is not required." 1706 OBJECT frsldPvcCtrlDelayLoc 1707 MIN-ACCESS read-only 1708 DESCRIPTION 1709 "Write access is not required." 1711 OBJECT frsldPvcCtrlDeliveryLoc 1712 MIN-ACCESS read-only 1713 DESCRIPTION 1714 "Write access is not required." 1716 OBJECT frsldPvcCtrlPurge 1717 MIN-ACCESS read-only 1718 DESCRIPTION 1719 "Write access is not required." 1721 OBJECT frsldPvcCtrlDeleteOnPurge 1722 MIN-ACCESS read-only 1723 DESCRIPTION 1724 "Write access is not required." 1726 ::= { frsldMIBCompliances 1 } 1728 -- 1729 -- Units of Conformance 1730 -- 1731 frsldPvcReqCtrlGroup OBJECT-GROUP 1732 OBJECTS { 1733 frsldPvcCtrlSrcRP, 1734 frsldPvcCtrlDstRP, 1735 frsldPvcCtrlDelayLoc, 1736 frsldPvcCtrlDelayFrSize, 1737 frsldPvcCtrlDelayType, 1738 frsldPvcCtrlDeliveryLoc, 1739 frsldPvcCtrlPurge, 1740 frsldPvcCtrlDeleteOnPurge, 1741 frsldPvcCtrlLastPurgeTime 1742 } 1743 STATUS current 1744 DESCRIPTION 1745 "A collection of required objects providing 1746 control information applicable to a PVC which 1747 implements Service Level Definitions." 1748 ::= { frsldMIBGroups 1 } 1750 frsldPvcOptCtrlGroup OBJECT-GROUP 1751 OBJECTS { 1752 frsldPvcCtrlStatus, 1753 frsldPvcCtrlPacketFreq, 1754 frsldPvcCtrlDelayTimeOut, 1755 frsldSmplCtrlStatus, 1756 frsldSmplCtrlDataColPeriod, 1757 frsldSmplCtrlAvailColPeriod, 1758 frsldSmplCtrlDataBuckets, 1759 frsldSmplCtrlDataBucketsGranted, 1760 frsldSmplCtrlAvailBuckets, 1761 frsldSmplCtrlAvailBucketsGranted 1762 } 1763 STATUS current 1764 DESCRIPTION 1765 "A collection of optional objects providing 1766 control information applicable to a PVC which 1767 implements Service Level Definitions." 1768 ::= { frsldMIBGroups 2 } 1770 frsldPvcReqDataGroup OBJECT-GROUP 1771 OBJECTS { 1772 frsldPvcDataDelayAvg, 1773 frsldPvcDataFrDeliveredC, 1774 frsldPvcDataFrDeliveredE, 1775 frsldPvcDataFrOfferedC, 1776 frsldPvcDataFrOfferedE, 1777 frsldPvcDataDataDeliveredC, 1778 frsldPvcDataDataDeliveredE, 1779 frsldPvcDataDataOfferedC, 1780 frsldPvcDataDataOfferedE, 1781 frsldPvcDataUnavailableTime, 1782 frsldPvcDataUnavailables 1783 } 1784 STATUS current 1785 DESCRIPTION 1786 "A collection of required objects providing data 1787 collected on a a PVC which implements Service 1788 Level Definitions." 1789 ::= { frsldMIBGroups 3 } 1791 frsldPvcDataOptGroup OBJECT-GROUP 1792 OBJECTS { 1793 frsldPvcDataDelayMin, 1794 frsldPvcDataDelayMax, 1795 frsldPvcDataMissedPolls 1796 } 1797 STATUS current 1798 DESCRIPTION 1799 "A collection of optional objects providing data 1800 collected on a a PVC which implements Service 1801 Level Definitions." 1802 ::= { frsldMIBGroups 4 } 1804 frsldPvcSampleOptGroup OBJECT-GROUP 1805 OBJECTS { 1806 frsldPvcDataDelaySmplMin, 1807 frsldPvcDataDelaySmplMax, 1808 frsldPvcDataDelaySmplAvg, 1809 frsldPvcDataSmplMissedPolls, 1810 frsldPvcDataSmplFrDeliveredC, 1811 frsldPvcDataSmplFrDeliveredE, 1812 frsldPvcDataSmplFrOfferedC, 1813 frsldPvcDataSmplFrOfferedE, 1814 frsldPvcDataSmplDataDeliveredC, 1815 frsldPvcDataSmplDataDeliveredE, 1816 frsldPvcDataSmplDataOfferedC, 1817 frsldPvcDataSmplDataOfferedE, 1818 frsldPvcDataSmplStartTime, 1819 frsldPvcDataSmplEndTime, 1820 frsldPvcAvailSmplUnavailableTime, 1821 frsldPvcAvailSmplUnavailables, 1822 frsldPvcAvailSmplStartTime, 1823 frsldPvcAvailSmplEndTime 1824 } 1825 STATUS current 1826 DESCRIPTION 1827 "A collection of optional objects providing 1828 the ability to sample the data collected on a 1829 PVC which implements Service Level Definitions." 1830 ::= { frsldMIBGroups 5 } 1832 frsldCapabilitiesGroup OBJECT-GROUP 1833 OBJECTS { 1834 frsldPvcCtrlWriteCaps, 1835 frsldSmplCtrlWriteCaps 1836 } 1837 STATUS current 1838 DESCRIPTION 1839 "A collection of required objects providing 1840 capability information for this MIB." 1841 ::= { frsldMIBGroups 6 } 1842 END 1844 6. Acknowledgments 1846 This document was produced by the Frame Relay Service MIB Working 1847 Group. It is based on the Frame Relay Forum's implementation 1848 agreement on service level definitions, FRF.13 [17]. 1850 7. References 1852 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1853 Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, 1854 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1856 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1857 Management Information for TCP/IP-based Internets", RFC 1155, STD 1858 16, Performance Systems International, Hughes LAN Systems, May 1990 1860 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1861 STD 16, Performance Systems International, Hughes LAN Systems, March 1862 1991 1864 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1865 RFC 1215, Performance Systems International, March 1991 1867 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1868 and S. Waldbusser, "Structure of Management Information Version 2 1869 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1870 Braunschweig, SNMP Research, First Virtual Holdings, International 1871 Network Services, April 1999 1873 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1874 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1875 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1876 Virtual Holdings, International Network Services, April 1999 1878 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1879 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 1880 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1881 Virtual Holdings, International Network Services, April 1999 1883 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1884 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1885 Systems International, Performance Systems International, MIT 1886 Laboratory for Computer Science, May 1990. 1888 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction 1889 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 1890 Systems, Inc., Dover Beach Consulting, Inc., International Network 1891 Services, January 1996. 1893 [10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1894 Mappings for Version 2 of the Simple Network Management Protocol 1895 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 1896 Beach Consulting, Inc., International Network Services, January 1897 1996. 1899 [11]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1900 Processing and Dispatching for the Simple Network Management 1901 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1902 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1904 [12]Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1905 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1906 2574, IBM T. J. Watson Research, April 1999 1908 [13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1909 Operations for Version 2 of the Simple Network Management Protocol 1910 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 1911 Beach Consulting, Inc., International Network Services, January 1912 1996. 1914 [14]Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1915 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1916 Systems, April 1999 1918 [15]Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1919 Control Model (VACM) for the Simple Network Management Protocol 1920 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1921 Cisco Systems, Inc., April 1999 1923 [16]Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1924 Version 3 of the Internet-standard Network Management Framework", 1925 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 1926 Ericsson, Cisco Systems, April 1999 1928 [17]Frame Relay Forum Technical Committee, "Service Level Definitions 1929 Implementations Agreement", FRF.13, August 1998. 1931 [18]Brown, T., "Definitions of Managed Objects for Frame Relay Service", 1932 RFC 1604, Bell Communications Research, March 1994. 1934 [19]Waldbusser, S., "Remote Network Monitoring Management Information 1935 Base Version 2 using SMIv2", RFC 2021, International Network 1936 Service, January 1997. 1938 [20]Brown, C., Baker, F., "Management Information Base for Frame Relay 1939 DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, 1940 September 1997. 1942 8. Security Considerations 1944 There are a number of management objects defined in this MIB that 1945 have a MAX-ACCESS clause of read-write and/or read-create. Such 1946 objects may be considered sensitive or vulnerable in some network 1947 environments. The support for SET operations in a non-secure 1948 environment without proper protection can have a negative effect on 1949 network operations. 1951 SNMPv1 by itself is not a secure environment. Even if the network 1952 itself is secure (for example by using IPSec), even then, there is no 1953 control as to who on the secure network is allowed to access and 1954 GET/SET (read/change/create/delete) the objects in this MIB. 1956 It is recommended that the implementers consider the security 1957 features as provided by the SNMPv3 framework. Specifically, the use 1958 of the User-based Security Model RFC 2274 [12] and the View-based 1959 Access Control Model RFC 2275 [15] is recommended. 1961 It is then a customer/user responsibility to ensure that the SNMP 1962 entity giving access to an instance of this MIB, is properly 1963 configured to give access to the objects only to those principals 1964 (users) that have legitimate rights to indeed GET or SET 1965 (change/create/delete) them. 1967 9. Authors' Addresses 1969 Robert Steinberger 1970 Paradyne Networks 1971 Mailstop: LG-132 1972 8545 126th Avenue North 1973 Largo, FL USA 33773 1975 Phone: 1(727)530-2395 1977 Email: rsteinberger@paradyne.com 1979 Orly Nicklass, Ph.D 1980 RAD Data Communications Ltd. 1981 12 Hanechoshet Street 1982 Tel Aviv, Israel 69710 1984 Phone: 972 3 6459588 1986 Email: orly@radmail.rad.co.il 1988 10. Copyright Section 1990 Copyright (C) The Internet Society (2000). All Rights Reserved. 1992 This document and translations of it may be copied and furnished to 1993 others, and derivative works that comment on or otherwise explain it 1994 or assist in its implementation may be prepared, copied, published 1995 and distributed, in whole or in part, without restriction of any 1996 kind, provided that the above copyright notice and this paragraph are 1997 included on all such copies and derivative works. However, this 1998 document itself may not be modified in any way, such as by removing 1999 the copyright notice or references to the Internet Society or other 2000 Internet organizations, except as needed for the purpose of 2001 developing Internet standards in which case the procedures for 2002 copyrights defined in the Internet Standards process must be 2003 followed, or as required to translate it into languages other than 2004 English. 2006 The limited permissions granted above are perpetual and will not be 2007 revoked by the Internet Society or its successors or assigns. 2009 This document and the information contained herein is provided on an 2010 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2011 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2012 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2013 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2014 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.