idnits 2.17.1 draft-ietf-frnetmib-atmiwf-06.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. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 614 has weird spacing: '...nnIndex when ...' == Line 1014 has weird spacing: '...orIndex when...' == Line 1765 has weird spacing: '...for the purpo...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The exact meaning of the all-uppercase expression 'NOT REQUIRED' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 14, 2000) is 8716 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) == Unused Reference: '18' is defined on line 1654, but no explicit reference was found in the text ** 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') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '19' -- Possible downref: Non-RFC (?) normative reference: ref. '20' ** Obsolete normative reference: RFC 2233 (ref. '22') (Obsoleted by RFC 2863) Summary: 19 errors (**), 0 flaws (~~), 8 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Managed Objects 2 for Monitoring and Controlling the 3 Frame Relay/ATM PVC Service Interworking Function 5 June 14, 2000 7 draft-ietf-frnetmib-atmiwf-06.txt 9 Kenneth Rehbehn 10 Visual Networks 11 krehbehn@visualnetworks.com 13 Orly Nicklass 14 RAD Data Communications, Ltd. 15 Orly_n@rad.co.il 17 George Mouradian 18 AT&T Labs 19 gvm@att.com 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with 24 all provisions of Section 10 of RFC2026. Internet-Drafts are working 25 documents of the Internet Engineering Task Force (IETF), its areas, 26 and its working groups. Note that other groups may also distribute 27 working documents as Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as ``work in progress.'' 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Abstract 42 This memo defines a Management Information Base (MIB) to configure, 43 monitor, and control a service interworking function (IWF) for 44 Permanent Virtual Connections (PVC) between Frame Relay and 45 Asynchronous Transfer Mode (ATM) technologies. 47 Copyright Notice 49 Copyright (C) The Internet Society (2000). All Rights Reserved. 51 Table of Contents 53 1 The SNMP Management Framework ................................ 4 54 2 Conventions .................................................. 5 55 3 Overview ..................................................... 6 56 3.1 Frame Relay/ATM Service Interworking Background ............ 6 57 3.2 Structure of the MIB ....................................... 7 58 3.3 Relationship to Other MIBs ................................. 8 59 3.3.1 Frame Relay Service MIB .................................. 8 60 3.3.2 Frame Relay DTE MIB ...................................... 9 61 3.3.3 ATM MIB .................................................. 9 62 3.3.4 IF MIB ................................................... 9 63 3.4 Point to Multipoint Considerations ......................... 10 64 3.5 Theory of Operation ........................................ 11 65 3.5.1 Creation Process ......................................... 11 66 3.5.2 Destruction Process ...................................... 14 67 3.5.3 Modification Process ..................................... 15 68 4 Object Definitions ........................................... 16 69 4.1 The FR/ATM PVC Service IWF Connection Group ................ 18 70 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 27 71 5 Augmentation of ATM MIB VCL Endpoint Entry (atmVclEntry) ..... 34 72 6 Frame Relay/ATM PVC Service Interworking NOTIFICATION ........ 36 73 7 Conformance Information ...................................... 37 74 7.1 Compliance Statement For Equipment ......................... 37 75 7.2 Compliance Statement For Service (CNM Interface) ........... 39 76 7.3 Units of Conformance ....................................... 41 77 7.3.1 Basic FR/ATM IWF PVC Connection Group .................... 41 78 7.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 41 79 7.3.3 ATM MIB VCL Endpoint Table Augmentation .................. 42 80 7.3.4 Notification Group ....................................... 42 81 8 Acknowledgments .............................................. 43 82 9 References ................................................... 44 83 9 Security Considerations ...................................... 46 84 10 Authors' Addresses .......................................... 47 86 1. The SNMP Management Framework 88 The SNMP Management Framework presently consists of five major 89 components: 91 o An overall architecture, described in RFC 2571 [1]. 93 o Mechanisms for describing and naming objects and events for the 94 purpose of management. The first version of this Structure of 95 Management Information (SMI) is called SMIv1 and described in 96 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The 97 second version, called SMIv2, is described in STD 58, RFC 2578 98 [5], RFC 2579 [6] and RFC 2580 [7]. 100 o Message protocols for transferring management information. The 101 first version of the SNMP message protocol is called SNMPv1 and 102 described in STD 15, RFC 1157 [8]. A second version of the SNMP 103 message protocol, which is not an Internet standards track 104 protocol, is called SNMPv2c and described in RFC 1901 [9] and 105 RFC 1906 [10]. The third version of the message protocol is 106 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 107 RFC 2574 [12]. 109 o Protocol operations for accessing management information. The 110 first set of protocol operations and associated PDU formats is 111 described in STD 15, RFC 1157 [8]. A second set of protocol 112 operations and associated PDU formats is described in RFC 1905 113 [13]. 115 o A set of fundamental applications described in RFC 2573 [14] and 116 the view-based access control mechanism described in RFC 2575 117 [15]. 119 A more detailed introduction to the current SNMP Management Framework 120 can be found in RFC 2570 [16]. 122 Managed objects are accessed via a virtual information store, termed 123 the Management Information Base or MIB. Objects in the MIB are 124 defined using the mechanisms defined in the SMI. 126 This memo specifies a MIB module that is compliant to the SMIv2. A 127 MIB conforming to the SMIv1 can be produced through the appropriate 128 translations. The resulting translated MIB must be semantically 129 equivalent, except where objects or events are omitted because no 130 translation is possible (use of Counter64). Some machine readable 131 information in SMIv2 will be converted into textual descriptions in 132 SMIv1 during the translation process. However, this loss of machine 133 readable information is not considered to change the semantics of the 134 MIB. 136 2. Conventions 138 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 139 SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when 140 they appear in this document, are to be interpreted as described in 141 RFC 2119 [23]. 143 3. Overview 145 This document defines a Management Information Base (MIB) for 146 monitoring and controlling a service interworking function (IWF) for 147 Permanent Virtual Connections (PVC) between Frame Relay and 148 Asynchronous Transfer Mode (ATM) technologies. The agreements on 149 which this MIB is based were reached jointly by the Frame Relay Forum 150 and the ATM Forum and are documented in the Frame Relay Forum 151 Document FRF.8 [17]. 153 3.1. Frame Relay/ATM Service Interworking Background 155 Frame relay to ATM interworking is a function that exchanges Protocol 156 Data Units (PDU) between a frame relay service user and an ATM 157 service user. Two types of interworking functions are specified for 158 frame relay and ATM permanent virtual connection (PVC) service users: 159 network interworking and service interworking. 161 Network interworking provides PDU forwarding between frame relay 162 service users inter-connected by an ATM service. Both endpoints are 163 frame relay PVCs. Frame Relay to ATM PVC Network Interworking is 164 defined in [20]. 166 Service interworking provides PDU forwarding so that the ATM service 167 user performs no frame relaying service-specific functions and the 168 frame relay service user performs no ATM service-specific functions. 169 Optionally, the service IWF translates particular higher layer 170 protocols to satisfy the requirements of end-systems. Frame Relay to 171 ATM PVC Service Interworking is defined in [20]. 173 This MIB describes management objects used to provision, monitor, and 174 control a Frame Relay/ATM PVC Service IWF. 176 FRF.8 [17] does not address point-to-multipoint applications of the 177 IWF. Implementations MAY provide support for point-to-multipoint 178 capability using this MIB. 180 Consult FRF.8 [17] for more details on the operation of a Frame 181 Relay/ATM PVC Service IWF. 183 3.2. Structure of the MIB 185 The Frame Relay/ATM PVC Service IWF managed objects are organized as 186 follows: 188 (1) FR/ATM PVC Service IWF cross-connect table, 190 (2) Connection description table, and 192 (3) Notification object 194 The IWF cross-connect table contains one or more rows for each 195 inter-worked connection. Each inter-worked connection is uniquely 196 identified by the frAtmIwfConnIndex object. In the case of point-to- 197 point, a single row is present. In the case of point-to-multipoint, 198 one row exists for each multipoint destination. Index objects for 199 the ATM port, VPI, VCI, frame relay port, and frame relay DLCI 200 distinguish the constituent rows used in a point-to-multipoint case. 202 Each inter-worked connection has attributes governing behavior of the 203 IWF. These attributes describe how the IWF should transform a PDU 204 during the forwarding process and provide rules for: 206 (1) Mapping the ATM CLP bit to frame relay DE bit 208 (2) Mapping the ATM congestion notification bit to frame relay 209 congestion bits 211 (3) Mapping higher protocol encapsulations between ATM and frame 212 relay 214 (4) Performing fragmentation and reassembly 216 (5) Performing ARP translation between ATM and frame relay 218 Typically, most connections share the same attributes. The attributes 219 are represented in this MIB by the connection description table. Each 220 row of the connection description table contains the attribute 221 settings common to one or more inter-worked connections. One example 222 would be full mapping and translation. All cross-connect table 223 entries that require full mapping and translation services set the 224 frAtmIwfConnectionDescriptor object to the index value for the 225 connection description table row that contains objects set to values 226 that provide full mapping and translation services. 228 A notification object provides cross-connect status change alerts. 230 3.3. Relationship to Other MIBs 232 The Frame Relay/ATM PVC Service IWF MIB describes the cross- 233 connections between frame relay and ATM service users. Each PVC 234 endpoint is provisioned and managed with a technology-specific MIB as 235 described below. 237 Each technology-specific MIB has a table of PVC endpoints (indexed by 238 ifIndex and logical link address such as the DLCI or VPI/VCI). In the 239 absence of interworking, two endpoints are cross-connected via a 240 technology-specific cross connect table (e.g., the 241 atmVcCrossConnectTable in the ATM MIB). However, a connection 242 between a frame relay endpoint and an ATM endpoint requires a cross- 243 connect in the ATM IWF MIB. 245 The following sections describe the relationship between the 246 technology-specific MIBs and the FR/ATM PVC Service IWF MIB. 248 3.3.1. Frame Relay Service MIB 250 Frame relay PVC endpoints are provisioned as rows in the Frame Relay 251 Services MIB [19] endpoint table. 253 Each frame relay PVC endpoint is described in the frPVCEndptTable. A 254 connection between two frame relay endpoints is described by an entry 255 in the frame relay PVC cross-connect table frPVCConnectTable. The 256 frPVCEndptConnectIdentifier object of each endpoint points to the 257 frPVCConnectTable cross-connect table row for the connection. 259 In the case of an inter-worked connection, the 260 frPVCEndptConnectIdentifier object is set to zero. Instead, the 261 frPVCEndptAtmIwfConnIndex object is set to the index of the FR/ATM 262 IWF cross-connect table row. 264 The frame relay PVC cross-connect table (frPVCConnectTable) does not 265 contain an entry for the FR/ATM inter-worked connection. 267 Note that the frPVCEndptConnectIdentifier and 268 frPVCEndptAtmIwfConnIndex objects are set by the system as a side- 269 effect of cross-connect establishment. Consequently, these objects 270 are read-only. 272 3.3.2. Frame Relay DTE MIB 274 The Frame Relay DTE MIB described in [19] has no relevance to the 275 FR/ATM PVC Service IWF MIB. 277 3.3.3. ATM MIB 279 ATM PVC endpoints are provisioned as rows in the ATM MIB [21] virtual 280 connection link table. 282 Each ATM connection endpoint is described in the atmVclTable. A 283 connection between two ATM endpoints is described by an entry in the 284 ATM VCL cross-connect table atmVcCrossConnectTable. The 285 atmVclCrossConnectIdentifier object of each endpoint points to the 286 atmVcCrossConnectTable row for the connection. 288 In the case of an inter-worked connection, the 289 atmVclCrossConnectIdentifier object is set to zero. Instead, the 290 frAtmIwfVclCrossConnectIdentifier object in the frAtmIwfVclEntry is 291 set to the index of the applicable FR/ATM IWF cross-connect table 292 row. 294 Note that the frAtmIwfVclCrossConnectIdentifier object is defined not 295 in the ATM MIB but in Section 5 of this MIB. Specifically, the 296 object is defined as a column object in a table that AUGMENTs the ATM 297 MIB VCL table. 299 The ATM VCL cross-connect table (atmVcCrossConnectTable) does not 300 contain an entry for the inter-worked connection. 302 Note that the atmVclCrossConnectIdentifier and 303 frAtmIwfVclCrossConnectIdentifier objects are set by the system as a 304 side-effect of cross-connect establishment. Consequently, these 305 objects are read-only. 307 3.3.4. IF MIB 309 The ifIndex defined in the IF MIB [22] identifies the specific frame 310 relay and ATM endpoint interfaces. The values frAtmIwfConnAtmPort 311 and frAtmIwfConnFrPort is used in this MIB as a component in the 312 index list for the frAtmIwfConnectionTable rows. 314 3.4. Point to Multipoint Considerations 316 This MIB supports IWF implementations providing point-to-multipoint 317 functionality. All rows of the cross-connect table indexed by the 318 same frAtmIwfConnIndex MUST utilize the same 319 frAtmIwfConnectionDescriptor value. 321 A group of cross-connect table entries indexed by the same 322 frAtmIwfConnIndex value MUST agree on which service the multipoint 323 operation is offered. Two cases are possible: 325 (1) Many frame relay PVCs cross-connected to one ATM PVC, or 327 (2) One frame relay PVC cross-connected to many ATM PVCs 329 3.5. Theory of Operation 331 3.5.1. Creation Process 333 Multiple steps are required to create a frame relay to ATM cross- 334 connection. First, rows must be created in the following tables: 336 (1) The Frame Relay Service MIB frPVCEndptTable 338 (2) The ATM MIB atmVclTable 340 (3) The FR/ATM Service IWF MIB frAtmIwfConnectionDescriptorTable 342 (4) The FR/ATM Service IWF MIB frAtmIwfConnectionTable 344 Second, the newly created rows are cross-linked. 346 Finally, the administrative and operational status objects are set to 347 'up(1)'. 349 A step-by-step example is provided to illustrate the creation 350 process. In this example, the term "Manager" refers to a network 351 management system that issues SNMP protocol actions to an "Agent". 352 The agent is integrated with the system that implements the frame 353 relay to ATM service IWF. In this example, the following cross- 354 connection is created: 355 +-----------------------------------+ 356 +---------+ | FR/ATM PVC Service IWF | 357 | Frame | | ------------------------------ | +-----------+ 358 | Relay | +--------> frAtmIwfConnIndex K <--------+ | ATM | 359 |Endpoint | | | V | | | Endpoint | 360 | ------- | | | | | | | --------- | 361 | DLCI X | | | +------------+ | | |VPI.VCI Q.R| 362 | on |<-+ | | | +->| on | 363 |ifIndex Y| | V | | ifIndex S | 364 +---------+ |frAtmIwfConnectionDescriptorIndex L| +-----------+ 365 +-----------------------------------+ 367 Step 1 - Create the frame relay PVC endpoint 369 a) Manager requests creation of a new row in the frPVCEndptTable 371 b) Agent receives management request to create a row in 372 frPVCEndptTable for the frame relay side 374 c) A new row is created in frPVCEndptTable as follows: 376 - frPVCEndptConnectIdentifier initialized to zero 378 - frPVCEndptAtmIwfConnIndex initialized to zero 380 - remaining row objects initialized as needed for DLCI X 381 on ifIndex Y 383 Step 2 - Create the ATM PVC endpoint 385 a) Agent receives management request to create a row in atmVclTable 386 for the ATM side 388 b) A new row is created in atmVclTable and frAtmIwfVclTable (the 389 AUGMENT to the atmVclTable) as follows: 391 - atmVclCrossConnectIdentifier initialized to zero 393 - frAtmIwfVclCrossConnectIdentifier initialized to zero 395 - atmVclConnKind initialized to pvc(1) 397 - remaining row objects initialized as needed for VPI.VCI 398 Q.R on ifIndex S 400 Step 3 - Create the FR/ATM connection descriptor 402 a) If an existing connection descriptor is appropriate for the 403 new connection, go to Step 4 using the selected connection 404 descriptor index value L 406 b) Manager request a new connection descriptor index value by 407 reading frAtmIwfConnectionDescriptorIndexNext from the agent 409 c) Agent receives GET request for 410 frAtmIwfConnectionDescriptorIndexNext and responds with the 411 next available value L 413 d) Manager requests a new connection descriptor row entry using 414 the value L as the index 416 e) Agent receives SET request to create the 417 frAtmIwfConnectionDescriptorTable row entry causes the system 418 to create a row in the table. 420 Step 4 - Create the FR/ATM cross-connect 422 a) Manager requests a new cross-connect index value by reading 423 frAtmIwfConnIndexNext from the agent 425 b) Agent receives GET request for frAtmIwfConnIndexNext 426 and responds with the next available value K 428 c) Manager requests a new cross-connect row entry using the value 429 K as the index 431 d) Agent receives SET request to create the frAtmIwfConnectionTable 432 row entry (note: the frame relay and ATM PVC endpoints MUST exist 433 and be specified as part of the index fields for the 434 row 'K.S.Q.R.Y.X') 436 e) System creates a row in frAtmIwfConnectionTable for the following 437 indices: 439 - frAtmIwfConnIndex of K 441 - frAtmIwfConnAtmPort of S 443 - frAtmIwfConnVpi of Q 445 - frAtmIwfConnVci of R 447 - frAtmIwfConnFrPort of Y 449 - frAtmIwfConnDlci of X 451 - frAtmIwfConnectionDescriptor of L 453 Step 5 - The system sets the frame relay PVC endpoint and ATM VCL 454 endpoint to point to the FR/ATM cross-connect row (as a side-effect 455 of Step 4). 457 a) System sets frPVCEndptAtmIwfConnIndex to K 459 b) System sets frAtmIwfVclCrossConnectIdentifier to K 460 Step 6 - Manager signals activation by issuing a SET for the 461 frAtmIwfConnAdminStatus object using the value of 'up(1)' 463 Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus and 464 executes internal system mechanisms to activate each PVC segment and 465 the IWF cross-connect. The successful activation permits the agent to 466 respond with 'up(1)' when a GET request is received for the following 467 fields: 469 - frAtmIwfConnAtm2FrOperStatus 471 - frAtmIwfConnFr2AtmOperStatus 473 - atmVclOperStatus (Note: there is no comparable FRS MIB object) 475 3.5.2. Destruction Process 477 Destruction of the frame relay to ATM cross-connection is initiated 478 by the network management system. The agent's processing of the 479 request stimulates implementation-specific system clean-up actions. 480 Following removal of the row in the cross-connection table, the 481 frAtmIwfVclCrossConnectIdentifier in the frAtmIwfVclTable (AUGMENT of 482 the ATM MIB endpoint table) and frPVCEndptAtmIwfConnIndex in the 483 Frame Relay Service MIB endpoint table are both re-initialized to 484 zero. 486 A step-by-step example is provided to illustrate the destruction 487 process. 489 Step 1 - Manager requests destruction of an existing row in the 490 frAtmIwfConnectionTable by setting frAtmIwfConnRowStatus to 491 destroy(6) 493 Step 2 - Agent receives the SET request and performs implementation- 494 specific system clean-up actions for the cross-connection row 496 Step 3 - System updates the relevant cross connect information for 497 the frame relay PVC endpoint by setting frPVCEndptAtmIwfConnIndex to 498 0 499 Step 4 - System updates the relevant cross connect information for 500 the ATM PVC endpoint as follows: 502 a) System sets frAtmIwfVclCrossConnectIdentifier to 0 504 b) System sets atmVclOperStatus to 'down(2)' (Note: there is no 505 comparable FRS MIB object) 507 Following the destruction of the FR/ATM cross-connection entry, the 508 manager MAY set the frPVCConnectRowStatus and/or atmVclRowStatus to 509 destroy(6) the associated endpoint entries. 511 3.5.3. Modification Process 513 At the discretion of the agent, a FR/ATM cross-connect may be 514 reconfigured by adding and/or deleting leafs to/from the IWF topology 515 as per the FR/ATM IWF cross-connect creation/destruction procedures. 516 Reconfiguration of traffic/service category parameter values requires 517 release of the FR/ATM IWF cross-connect before those parameter values 518 may be changed for individual frame relay or ATM endpoint segments. 520 4. Object Definitions 522 FR-ATM-PVC-SERVICE-IWF-MIB DEFINITIONS ::= BEGIN 524 IMPORTS 525 MODULE-IDENTITY, OBJECT-TYPE, 526 NOTIFICATION-TYPE, 527 mib-2, Integer32, Counter32 FROM SNMPv2-SMI 529 RowStatus, TimeStamp FROM SNMPv2-TC 531 MODULE-COMPLIANCE, OBJECT-GROUP, 532 NOTIFICATION-GROUP FROM SNMPv2-CONF 534 AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB 536 atmVclEntry FROM ATM-MIB 538 InterfaceIndex FROM IF-MIB; 540 frAtmIwfMIB MODULE-IDENTITY 541 LAST-UPDATED "200006140000Z" -- June 14, 2000 542 ORGANIZATION "IETF Frame Relay Service MIB Working Group" 543 CONTACT-INFO 544 "WG Charter: 545 http://www.ietf.org/html.charters/frnetmib-charter 546 WG-email: 547 frnetmib@sunroof.eng.sun.com 548 Subscribe: 549 frnetmib-request@sunroof.eng.sun.com 550 Email Archive: 551 ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 553 Chair: Andy Malis 554 Lucent Technologies 555 Email: amalis@lucent.com 557 WG editor: Kenneth Rehbehn 558 Visual Networks, Inc. 559 Email: krehbehn@visualnetworks.com 561 Co-author: Orly Nicklass 562 RAD Data Communications Ltd. 563 EMail: orly@radmail.rad.co.il 564 Co-author: George Mouradian 565 AT&T Labs 566 EMail: gvm@att.com" 568 DESCRIPTION 569 "The MIB module for monitoring and controlling the 570 Frame Relay/ATM PVC Service Interworking 571 Function." 573 -- 574 -- Revision History 575 -- 576 REVISION "200006140000Z" 577 DESCRIPTION 578 "Published as RFC xxx" -- RFC editor assigns xxx 580 ::= { mib-2 xxx } -- RFC editor - IANA assigns xxx 582 -- 583 -- Object Identifiers 584 -- 585 frAtmIwfMIBObjects OBJECT IDENTIFIER 586 ::= { frAtmIwfMIB 1 } 588 frAtmIwfTraps OBJECT IDENTIFIER 589 ::= { frAtmIwfMIB 2 } 590 frAtmIwfTrapsPrefix OBJECT IDENTIFIER 591 ::= { frAtmIwfTraps 0 } 593 frAtmIwfConformance OBJECT IDENTIFIER 594 ::= { frAtmIwfMIB 3 } 595 frAtmIwfGroups OBJECT IDENTIFIER 596 ::= { frAtmIwfConformance 1 } 597 frAtmIwfCompliances OBJECT IDENTIFIER 598 ::= { frAtmIwfConformance 2 } 600 -- 601 -- The FR/ATM PVC Service IWF Group 602 -- 603 -- The Frame Relay/ATM PVC Service Interworking Function 604 -- Connection Table contains all connections utilizing 605 -- the interworking function. 606 -- 608 frAtmIwfConnIndexNext OBJECT-TYPE 609 SYNTAX Integer32 (0..2147483647) 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "This object contains an appropriate value to be 614 used for frAtmIwfConnIndex when creating entries 615 in the frAtmIwfConnectionTable. The value 0 616 indicates that no unassigned entries are 617 available. To obtain the frAtmIwfConnIndexNext 618 value for a new entry, the manager issues a 619 management protocol retrieval operation to obtain 620 the current value of this object. After each 621 retrieval, the agent should modify the value to 622 the next unassigned index." 623 ::= { frAtmIwfMIBObjects 1 } 625 frAtmIwfConnectionTable OBJECT-TYPE 626 SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "A table in which each row represents a Frame 631 Relay/ATM interworking connection." 632 ::= { frAtmIwfMIBObjects 2 } 634 frAtmIwfConnectionEntry OBJECT-TYPE 635 SYNTAX FrAtmIwfConnectionEntry 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "The FrAtmIwfConnectionEntry provides an entry for 640 an interworking connection between a frame relay 641 PVC and one or more ATM PVCs, or an ATM PVC and 642 one or more frame relay PVCs. A single frame 643 relay PVC connected to a single ATM PVC is 644 referred to as a `point-to-point' connection and 645 is represented by a single row in the FR/ATM IWF 646 Connection Table. The case of a single frame 647 relay PVC connected to multiple ATM PVCs (or 648 single ATM PVC connected to multiple frame relay 649 PVCs) is referred to as a `point-to-multipoint' 650 connection and is represented by multiple rows in 651 the FR/ATM IWF Connection Table. 653 The object frAtmIwfConnIndex uniquely identifies 654 each point-to-point or point-to-multipoint 655 connection. The manager obtains the 656 frAtmIwfConnIndex value by reading the 657 frAtmIwfConnIndexNext object. 659 After a frAtmIwfConnIndex is assigned for the 660 connection, the manager creates one or more rows 661 in the Cross Connect Table; one for each cross- 662 connection between the frame relay PVC and an ATM 663 PVC. In the case of `point-to-multipoint' 664 connections, all rows are indexed by the same 665 frAtmIwfConnIndex value and MUST refer to the same 666 frame relay PVC or ATM PVC respectively. An entry 667 can be created only when at least one pair of 668 frame relay and ATM PVCs exist. 670 A row can be established by one-step set-request 671 with all required parameter values and 672 frAtmIwfConnRowStatus set to createAndGo(4). The 673 Agent should perform all error checking as needed. 674 A pair of cross-connected PVCs, as identified by a 675 particular value of the indexes, is released by 676 setting frAtmIwfConnRowStatus to destroy(6). The 677 Agent may release all associated resources. The 678 manager may remove the related PVCs thereafter. 679 Indexes are persistent across reboots of the 680 system." 681 INDEX { frAtmIwfConnIndex, 682 frAtmIwfConnAtmPort, 683 frAtmIwfConnVpi, 684 frAtmIwfConnVci, 685 frAtmIwfConnFrPort, 686 frAtmIwfConnDlci 687 } 688 ::= { frAtmIwfConnectionTable 1 } 690 FrAtmIwfConnectionEntry ::= 691 SEQUENCE { 692 frAtmIwfConnIndex Integer32, 693 frAtmIwfConnAtmPort InterfaceIndex, 694 frAtmIwfConnVpi AtmVpIdentifier, 695 frAtmIwfConnVci AtmVcIdentifier, 696 frAtmIwfConnFrPort InterfaceIndex, 697 frAtmIwfConnDlci Integer32, 698 frAtmIwfConnRowStatus RowStatus, 699 frAtmIwfConnAdminStatus INTEGER, 700 frAtmIwfConnAtm2FrOperStatus INTEGER, 701 frAtmIwfConnAtm2FrLastChange TimeStamp, 702 frAtmIwfConnFr2AtmOperStatus INTEGER, 703 frAtmIwfConnFr2AtmLastChange TimeStamp, 704 frAtmIwfConnectionDescriptor Integer32, 705 frAtmIwfConnFailedFrameTranslate Counter32, 706 frAtmIwfConnOverSizedFrames Counter32, 707 frAtmIwfConnFailedAal5PduTranslate Counter32, 708 frAtmIwfConnOverSizedSDUs Counter32, 709 frAtmIwfConnCrcErrors Counter32, 710 frAtmIwfConnSarTimeOuts Counter32 711 } 713 frAtmIwfConnIndex OBJECT-TYPE 714 SYNTAX Integer32 (1..2147483647) 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION 718 "A unique value for each point-to-point or point- 719 to-multipoint connection. The manager obtains the 720 frAtmIwfConnIndex value by reading the 721 frAtmIwfConnIndexNext object. A point-to- 722 multipoint connection will be represented in the 723 frAtmIwfConnectionTable with multiple entries that 724 share the same frAtmIwfConnIndex value." 725 ::= { frAtmIwfConnectionEntry 1 } 727 frAtmIwfConnAtmPort OBJECT-TYPE 728 SYNTAX InterfaceIndex 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "The index in the ifTable that identifies the ATM 733 port for this interworking connection." 734 ::= { frAtmIwfConnectionEntry 2 } 736 frAtmIwfConnVpi OBJECT-TYPE 737 SYNTAX AtmVpIdentifier 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "The VPI of the ATM PVC end point for this 742 interworking connection." 743 ::= { frAtmIwfConnectionEntry 3 } 745 frAtmIwfConnVci OBJECT-TYPE 746 SYNTAX AtmVcIdentifier 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "The VCI of the ATM PVC end point for this 751 interworking 752 connection." 753 ::= { frAtmIwfConnectionEntry 4 } 755 frAtmIwfConnFrPort OBJECT-TYPE 756 SYNTAX InterfaceIndex 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "The index in the ifTable that identifies the 761 frame relay port for this interworking 762 connection." 763 ::= { frAtmIwfConnectionEntry 5 } 765 frAtmIwfConnDlci OBJECT-TYPE 766 SYNTAX Integer32 (16..4194303) 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "The DLCI that identifies the frame relay PVC end 771 point for this interworking connection." 772 ::= { frAtmIwfConnectionEntry 6 } 774 frAtmIwfConnRowStatus OBJECT-TYPE 775 SYNTAX RowStatus 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The table row may be created with 780 'createAndWait(5)' or 'createAndGo(4)'. 782 To activate a connection entry, a valid connection 783 descriptor MUST be established in the 784 frAtmIwfConnectionDescriptor object. 786 This object is set to 'destroy(6)' to delete the 787 table row. Before the table row is destroyed, the 788 OperStatus/AdminStatus of the corresponding 789 endpoints MUST be 'down(2)'. The deactivation of 790 the ATM endppoint MAY occur as a side-effect of 791 deleting the FR/ATM IWF cross-connection table 792 row. Otherwise, 'destroy(6)' operation MUST fail 793 (error code 'inconsistentValue')." 794 ::= { frAtmIwfConnectionEntry 7 } 796 frAtmIwfConnAdminStatus OBJECT-TYPE 797 SYNTAX INTEGER { up(1), down(2) } 798 MAX-ACCESS read-create 799 STATUS current 800 DESCRIPTION 801 "The desired operational state for this FR/ATM 802 interworked connection. 804 up(1) = Activate the connection. Before the 805 activation can be completed, the 806 OperStatus/AdminStatus of the 807 corresponding endpoints MUST be 808 'up(1)'. The activation of the 809 corresponding endpoints MAY occur as 810 a side-effect of activating the 811 FR/ATM IWF cross-connection. 813 down(2) = Deactivate the connection. Before 814 the deactivation can be completed, 815 the atmVclAdminStatus of the 816 corresponding ATM endpoint MUST be 817 'down(2)'. The deactivation of the 818 ATM endppoint MAY occur as a 819 side-effect of deactivating the 820 FR/ATM IWF cross-connection." 821 ::= { frAtmIwfConnectionEntry 8 } 823 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE 824 SYNTAX INTEGER { up(1), down(2) } 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The current operational state of this 829 interworking connection in the direction from ATM 830 to FR end." 831 ::= { frAtmIwfConnectionEntry 9 } 833 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE 834 SYNTAX TimeStamp 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "The value of sysUpTime at the time this 839 interworking connection entered its current 840 operational state in the ATM to FR direction. If 841 the current state was entered prior to the last 842 re-initialization of the local network management 843 subsystem, then this object contains a zero 844 value." 845 ::= { frAtmIwfConnectionEntry 10 } 847 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE 848 SYNTAX INTEGER { up(1), down(2) } 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "The current operational state of this 853 interworking connection in the direction from FR 854 to ATM end." 855 ::= { frAtmIwfConnectionEntry 11 } 857 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE 858 SYNTAX TimeStamp 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The value of sysUpTime at the time this 863 interworking connection entered its current 864 operational state in the FR to ATM direction. If 865 the current state was entered prior to the last 866 re-initialization of the local network management 867 subsystem, then this object contains a zero 868 value." 869 ::= { frAtmIwfConnectionEntry 12 } 871 frAtmIwfConnectionDescriptor OBJECT-TYPE 872 SYNTAX Integer32 873 MAX-ACCESS read-create 874 STATUS current 875 DESCRIPTION 876 "The value represents a pointer to the relevant 877 descriptor in the IWF descriptor table. An 878 attempt to set this value to an inactive or non- 879 existant row in the Connection Descriptor Table 880 MUST fail (error code 'inconsistentValue')." 881 ::= { frAtmIwfConnectionEntry 13 } 883 frAtmIwfConnFailedFrameTranslate OBJECT-TYPE 884 SYNTAX Counter32 885 UNITS "Frames" 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "This object counts the number of frames discarded 890 by the IWF because, while operating in Translation 891 Mode, the IWF is unable to decode the incoming 892 frame payload header according to the mapping 893 rules. (i.e., payload header not recognized by the 894 IWF). 896 Frame relay frames are received in the frame relay 897 to ATM direction of the PVC. 899 When operating in Transparent Mode, the IWF MUST 900 return noSuchInstance." 901 REFERENCE 902 "FRF.8 [17], Section 5.3.1" 903 ::= { frAtmIwfConnectionEntry 14 } 905 frAtmIwfConnOverSizedFrames OBJECT-TYPE 906 SYNTAX Counter32 907 UNITS "Frames" 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "Count of frames discarded by the IWF because the 912 frame is too large to be processed by the AAL5 913 segmentation procedure. Specifically, the frame 914 does not conform to the size specified in the 915 atmVccAal5CpcsTransmitSduSize object associated 916 with the atmVclEntry at the ATM endpoint. 918 Frame relay frames are received in the frame relay 919 to ATM direction of the PVC." 920 REFERENCE 921 "ATM MIB [21], atmVclTable 922 FRF.8 [17], 5.3.1.4" 923 ::= { frAtmIwfConnectionEntry 15 } 925 frAtmIwfConnFailedAal5PduTranslate OBJECT-TYPE 926 SYNTAX Counter32 927 UNITS "PDUs" 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "This attribute counts the number of AAL5 PDUs 932 discarded by the IWF because, while operating in 933 Translation Mode, the IWF is unable to decode the 934 incoming AAL5 PDU payload header according to the 935 mapping rules. (i.e., payload header not 936 recognized by the IWF). 938 AAL5 PDUs are received in the ATM to frame relay 939 direction of the PVC. 941 When operating in Transparent Mode, the IWF MUST 942 return noSuchInstance." 943 REFERENCE 944 "FRF.8 [17], Section 5.3.1" 945 ::= { frAtmIwfConnectionEntry 16 } 947 frAtmIwfConnOverSizedSDUs OBJECT-TYPE 948 SYNTAX Counter32 949 UNITS "SDUs" 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Count of AAL5 SDUs discarded by the IWF because 954 the SDU is too large to be forwarded on the frame 955 relay segment of the connection. Specifically, 956 the frame does not conform to the size specified 957 in the frLportFragSize object of the FRS MIB [19]. 959 AAL5 PDUs are received in the ATM to frame relay 960 direction of the PVC." 961 REFERENCE 962 "FRS MIB [19], frLportTable 963 FRF.8 [17], 5.3.1.4" 964 ::= { frAtmIwfConnectionEntry 17 } 966 frAtmIwfConnCrcErrors OBJECT-TYPE 967 SYNTAX Counter32 968 UNITS "PDUs" 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The number of AAL5 CPCS PDUs received with CRC-32 973 errors on this AAL5 VCC at the IWF. 975 AAL5 PDUs are received in the ATM to frame relay 976 direction of the PVC." 977 REFERENCE 978 "ATM MIB [21], atmVclTable" 979 ::= { frAtmIwfConnectionEntry 18 } 981 frAtmIwfConnSarTimeOuts OBJECT-TYPE 982 SYNTAX Counter32 983 UNITS "PDUs" 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "The number of partially re-assembled AAL5 CPCS 988 PDUs which were discarded on this AAL5 VCC at the 989 IWF because they were not fully re-assembled 990 within the required time period. If the re- 991 assembly timer is not supported, then this object 992 contains a zero value. 994 AAL5 PDUs are received in the ATM to frame relay 995 direction of the PVC." 996 REFERENCE 997 "ATM MIB [21], atmVclTable" 998 ::= { frAtmIwfConnectionEntry 19 } 1000 -- 1001 -- The FR/ATM PVC Service IWF Connection Descriptor Group 1002 -- 1003 -- The Frame Relay/ATM PVC Service Interworking Function 1004 -- Connection Descriptor table. A descriptor provides the 1005 -- attributes for a type of interworked connection. 1006 -- 1008 frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE 1009 SYNTAX Integer32 (0..2147483647) 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "This object contains an appropriate value to be 1014 used for frAtmIwfConnectionDescriptorIndex when 1015 creating entries in the 1016 frAtmIwfConnectionDescriptorTable. The value 0 1017 indicates that no unassigned entries are 1018 available. To obtain the 1019 frAtmIwfConnectionDescriptorIndexNext value for a 1020 new entry, the manager issues a management 1021 protocol retrieval operation to obtain the current 1022 value of this object. After each retrieval, the 1023 agent should modify the value to the next 1024 unassigned index." 1025 ::= { frAtmIwfMIBObjects 3 } 1027 frAtmIwfConnectionDescriptorTable OBJECT-TYPE 1028 SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry 1029 MAX-ACCESS not-accessible 1030 STATUS current 1031 DESCRIPTION 1032 "A table in which each row represents a descriptor 1033 for one type of Frame Relay/ATM interworking 1034 connection. A descriptor may be assigned to zero 1035 or more FR/ATM PVC service IWF connections." 1036 ::= { frAtmIwfMIBObjects 4 } 1038 frAtmIwfConnectionDescriptorEntry OBJECT-TYPE 1039 SYNTAX FrAtmIwfConnectionDescriptorEntry 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "An entry for a descriptor in an interworking 1044 connection between a frame relay PVC and an ATM 1045 PVC." 1046 INDEX { frAtmIwfConnectionDescriptorIndex } 1047 ::= { frAtmIwfConnectionDescriptorTable 1 } 1049 FrAtmIwfConnectionDescriptorEntry ::= 1050 SEQUENCE { 1051 frAtmIwfConnectionDescriptorIndex Integer32, 1052 frAtmIwfConnDescriptorRowStatus RowStatus, 1053 frAtmIwfConnDeToClpMappingMode INTEGER, 1054 frAtmIwfConnClpToDeMappingMode INTEGER, 1055 frAtmIwfConnCongestionMappingMode INTEGER, 1056 frAtmIwfConnEncapsulationMappingMode INTEGER, 1057 frAtmIwfConnEncapsulationMappings BITS, 1058 frAtmIwfConnFragAndReassEnabled INTEGER, 1059 frAtmIwfConnArpTranslationEnabled INTEGER 1060 } 1062 frAtmIwfConnectionDescriptorIndex OBJECT-TYPE 1063 SYNTAX Integer32 (1..2147483647) 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "A unique value to identify a descriptor in the 1068 table " 1069 ::= { frAtmIwfConnectionDescriptorEntry 1 } 1071 frAtmIwfConnDescriptorRowStatus OBJECT-TYPE 1072 SYNTAX RowStatus 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "The status of this table row. This object is 1077 used to create or delete an entry in the 1078 descriptor table. 1080 Creation of the row requires a row index (see 1081 frAtmIwfConnectionDescriptorIndexNext). If not 1082 explicitly set or in existence, all other columns 1083 of the row will be created and initialized to the 1084 default value. During creation, this object MAY 1085 be set to 'createAndGo(4)' or 'createAndWait(5)'. 1086 The object MUST contain the value 'active(1)' 1087 before any connection table entry references the 1088 row. 1090 To destroy a row in this table, this object is set 1091 to the 'destroy(6)' action. Row destruction MUST 1092 fail (error code 'inconsistentValue') if any 1093 connection references the row." 1094 ::= { frAtmIwfConnectionDescriptorEntry 2 } 1096 frAtmIwfConnDeToClpMappingMode OBJECT-TYPE 1097 SYNTAX INTEGER { 1098 mode1(1), 1099 mode2Const0(2), 1100 mode2Const1(3) 1101 } 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "This object describes which mode of translation 1106 is in use for loss priority mapping in the frame 1107 relay to ATM direction. 1109 mode1(1) = the DE field in the Q.922 core 1110 frame shall be mapped to the ATM 1111 CLP field of every cell 1112 generated by the segmentation 1113 process of the AAL5 PDU 1114 containing the information of 1115 that frame. 1117 mode2Contst0(2) = the ATM CLP field of every cell 1118 generated by the segmentation 1119 process of the AAL5 PDU 1120 containing the information of 1121 that frame shall be set to 1122 constant 0. 1124 mode2Contst1(3) = the ATM CLP field of every cell 1125 generated by the segmentation 1126 process of the AAL5 PDU 1127 containing the information of 1128 that frame shall be set to 1129 constant 1." 1130 REFERENCE 1131 "FRF.8 [17], Section 4.2.1" 1132 DEFVAL { mode1 } 1133 ::= { frAtmIwfConnectionDescriptorEntry 3 } 1135 frAtmIwfConnClpToDeMappingMode OBJECT-TYPE 1136 SYNTAX INTEGER { 1137 mode1(1), 1138 mode2Const0(2), 1139 mode2Const1(3) 1140 } 1141 MAX-ACCESS read-create 1142 STATUS current 1143 DESCRIPTION 1144 "This object describes which mode of translation 1145 is in use for loss priority mapping in the ATM to 1146 frame relay direction. 1148 mode1(1) = if one or more cells in a frame 1149 has its CLP field set, the DE 1150 field of the Q.922 core frame 1151 should be set. 1153 mode2Const0(2) = the DE field of the Q.922 core 1154 frame should be set to the 1155 constant 0. 1157 mode2Const1(3) = the DE field of the Q.922 core 1158 frame should be set to the 1159 constant 1." 1160 REFERENCE 1161 "FRF.8 [17], Section 4.2.2" 1162 DEFVAL { mode1 } 1163 ::= { frAtmIwfConnectionDescriptorEntry 4 } 1165 frAtmIwfConnCongestionMappingMode OBJECT-TYPE 1166 SYNTAX INTEGER { 1167 mode1(1), 1168 mode2(2) 1169 } 1170 MAX-ACCESS read-create 1171 STATUS current 1172 DESCRIPTION 1173 "This object describes which mode of translation 1174 is in use for forward congestion indication 1175 mapping in the frame relay to ATM direction. 1177 mode1(1) = The FECN field in the Q.922 core frame 1178 shall be mapped to the ATM EFCI field 1179 of every cell generated by the 1180 segmentation process of the AAL5 PDU 1181 containing the information of that 1182 frame. 1184 mode2(2) = The FECN field in the Q.922 core frame 1185 shall not be mapped to the ATM EFCI 1186 field of cells generated by the 1187 segmentation process of the AAL5 PDU 1188 containing the information of that 1189 frame. The EFCI field is always set to 1190 'congestion not experienced'. 1192 In both of the modes above, if there is congestion 1193 in the forward direction in the ATM layer within 1194 the IWF, then the IWF can set the EFCI field to 1195 'congestion experienced'." 1196 REFERENCE 1197 "FRF.8 [17], Section 4.3.1.1" 1198 DEFVAL { mode1 } 1199 ::= { frAtmIwfConnectionDescriptorEntry 5 } 1201 frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE 1202 SYNTAX INTEGER { 1203 transparentMode(1), 1204 translationMode(2), 1205 translationModeAll(3) 1206 } 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "This object indicates whether the mapping of 1211 upper layer protocol encapsulation is enabled on 1212 this interworking connection. 1214 transparentMode(1) = Forward the encapsulations 1215 unaltered. 1217 translationMode(2) = Perform mapping between the 1218 two encapsulations due to the 1219 incompatibilities of the two 1220 methods. Mapping is provided 1221 for a subset of the potential 1222 encapsulations as itemized in 1223 frAtmIwfConnEncapsulationMapp 1224 ings. 1226 translationModeAll(3) = Perform mapping between 1227 the two encapsulations due to 1228 the incompatibilities of the 1229 two methods. All 1230 encapsulations are 1231 translated." 1232 REFERENCE 1233 "FRF.8 [17], Section 5.3" 1234 DEFVAL { transparentMode } 1235 ::= { frAtmIwfConnectionDescriptorEntry 6 } 1237 frAtmIwfConnEncapsulationMappings OBJECT-TYPE 1238 SYNTAX BITS { 1239 none (0), 1240 bridgedPdus(1), 1241 bridged802dot6(2), 1242 bPdus(3), 1243 routedIp(4), 1244 routedOsi(5), 1245 otherRouted(6), 1246 x25Iso8202(7), 1247 q933q2931(8) } 1248 MAX-ACCESS read-create 1249 STATUS current 1250 DESCRIPTION 1251 "If upper layer protocol encapsulation mapping is 1252 enabled on this interworking connection, then this 1253 attribute enumerates which of the encapsulation 1254 mappings are supported. 1256 none(0) = Transparent mode operation 1257 bridgedPdus(1) = PID: 0x00-01,-07,-02 or -08 1258 bridged802dot6(2) = PID: 0x00-0B 1259 bPdus(3) = PID: 0x00-0E or -0F 1260 routedIp(4) = NLPID: OxCC 1261 routedOsi(5) = NLPID: Ox81, 0x82 or 0x83 1262 otherRouted(6) = Other routed protocols 1263 x25Iso8202(7) = X25 1264 q933q2931(8) = Q.933 and Q.2931" 1265 REFERENCE 1266 "FRF.8 [17], Section 5.3.1" 1267 DEFVAL { { none } } 1268 ::= { frAtmIwfConnectionDescriptorEntry 7 } 1270 frAtmIwfConnFragAndReassEnabled OBJECT-TYPE 1271 SYNTAX INTEGER { enabled(1), disabled(2)} 1272 MAX-ACCESS read-create 1273 STATUS current 1274 DESCRIPTION 1275 "The attribute indicates whether fragmentation and 1276 reassembly is enabled for this connection." 1277 REFERENCE 1278 "FRF.8 [17], Section 5.3.1.4" 1279 DEFVAL { disabled } 1280 ::= { frAtmIwfConnectionDescriptorEntry 8 } 1282 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE 1283 SYNTAX INTEGER { enabled(1), disabled(2)} 1284 MAX-ACCESS read-create 1285 STATUS current 1286 DESCRIPTION 1287 "The attribute indicates whether ARP translation 1288 is enabled for this connection." 1289 REFERENCE 1290 "FRF.8 [17], Section 5.4" 1291 DEFVAL { disabled } 1292 ::= { frAtmIwfConnectionDescriptorEntry 9 } 1294 -- 1295 -- Augmentation of ATM MIB VCL Endpoint Table (atmVclTable) 1296 -- 1297 frAtmIwfVclTable OBJECT-TYPE 1298 SYNTAX SEQUENCE OF FrAtmIwfVclEntry 1299 MAX-ACCESS not-accessible 1300 STATUS current 1301 DESCRIPTION 1302 "The FR/ATM IWF VCL Table augments the ATM MIB VCL 1303 Endpoint table." 1304 ::= { frAtmIwfMIBObjects 5 } 1306 frAtmIwfVclEntry OBJECT-TYPE 1307 SYNTAX FrAtmIwfVclEntry 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "Entries in this table are created only by the 1312 agent. One entry exists for each ATM VCL managed 1313 by the agent." 1314 AUGMENTS { atmVclEntry } 1315 ::= { frAtmIwfVclTable 1 } 1317 FrAtmIwfVclEntry ::= SEQUENCE { 1318 frAtmIwfVclCrossConnectIdentifier Integer32 1319 } 1321 frAtmIwfVclCrossConnectIdentifier OBJECT-TYPE 1322 SYNTAX Integer32 (1..2147483647) 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "This object contains the index value of the 1327 FR/ATM cross-connect table entry used to link the 1328 ATM VCL with a frame relay PVC. 1330 Each row of the atmVclTable that is not cross- 1331 connected with a frame relay PVC MUST return the 1332 value zero when this object is read. 1334 In the case of (frame relay) point to (ATM) 1335 multipoint, multiple ATM VCLs will have the same 1336 value of this object, and all their cross- 1337 connections are identified by entries that are 1338 indexed by the same value of 1339 frAtmIwfVclCrossConnectIdentifier in the 1340 frAtmIwfConnectionTable of this MIB module. 1342 The value of this object is initialized by the 1343 agent after the associated entries in the 1344 frAtmIwfConnectionTable have been created." 1345 ::= { frAtmIwfVclEntry 1 } 1347 -- 1348 -- Frame Relay/ATM PVC Service Interworking NOTIFICATION 1349 -- 1351 frAtmIwfConnStatusChange NOTIFICATION-TYPE 1352 OBJECTS { frAtmIwfConnAdminStatus, 1353 frAtmIwfConnAtm2FrOperStatus, 1354 frAtmIwfConnFr2AtmOperStatus 1355 } 1356 STATUS current 1357 DESCRIPTION 1358 "An indication that the status of this 1359 interworking connection has changed." 1360 ::= { frAtmIwfTrapsPrefix 1 } 1362 -- 1363 -- Conformance Information 1364 -- 1366 -- 1367 -- Compliance Statement For Equipment 1368 -- 1370 frAtmIwfEquipmentCompliance MODULE-COMPLIANCE 1371 STATUS current 1372 DESCRIPTION 1373 "The compliance statement for equipment that 1374 implements the FR/ATM Interworking MIB." 1376 MODULE -- this module 1377 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1378 frAtmIwfConnectionDescriptorGroup, 1379 frAtmIwfAtmVclTableAugmentGroup, 1380 frAtmIwfNotificationsGroup } 1382 OBJECT frAtmIwfConnDeToClpMappingMode 1383 SYNTAX INTEGER { mode1(1) } 1384 DESCRIPTION 1385 "Only support for Mode 1 is REQUIRED." 1387 OBJECT frAtmIwfConnClpToDeMappingMode 1388 SYNTAX INTEGER { mode1(1) } 1389 DESCRIPTION 1390 "Only support for Mode 1 is REQUIRED." 1392 OBJECT frAtmIwfConnCongestionMappingMode 1393 SYNTAX INTEGER { mode1(1) } 1394 DESCRIPTION 1395 "Only support for Mode 1 is REQUIRED." 1397 OBJECT frAtmIwfConnEncapsulationMappingMode 1398 SYNTAX INTEGER { transparentMode(1) } 1399 DESCRIPTION 1400 "Support for Translation Mode is OPTIONAL." 1402 OBJECT frAtmIwfConnEncapsulationMappings 1403 SYNTAX BITS { none(0) } 1404 DESCRIPTION 1405 "The IWF may provide one, some or none of the 1406 encapsulation translations defined in section 1407 5.3.1 of FRF.8 [17]." 1409 OBJECT frAtmIwfConnFragAndReassEnabled 1410 SYNTAX INTEGER { disabled(2) } 1411 DESCRIPTION 1412 "Only support for Mode 1 is REQUIRED." 1414 OBJECT frAtmIwfConnArpTranslationEnabled 1415 SYNTAX INTEGER { disabled(2) } 1416 DESCRIPTION 1417 "Support for ARP Translation is NOT REQUIRED." 1419 ::= { frAtmIwfCompliances 1 } 1421 -- 1422 -- Compliance Statement For Service (CNM Interface) 1423 -- 1425 frAtmIwfServiceCompliance MODULE-COMPLIANCE 1426 STATUS current 1427 DESCRIPTION 1428 "The compliance statement for a CNM interface that 1429 implements the FR/ATM Interworking MIB." 1431 MODULE -- this module 1432 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1433 frAtmIwfConnectionDescriptorGroup, 1434 frAtmIwfAtmVclTableAugmentGroup, 1435 frAtmIwfNotificationsGroup } 1437 -- 1438 -- Exceptions for each object type implemented for a 1439 -- CNM view of the FR/ATM Interworking MIB 1440 -- 1441 OBJECT frAtmIwfConnAdminStatus 1442 MIN-ACCESS read-only 1443 DESCRIPTION 1444 "Write access is not REQUIRED." 1446 OBJECT frAtmIwfConnDeToClpMappingMode 1447 SYNTAX INTEGER { mode1(1) } 1448 MIN-ACCESS read-only 1449 DESCRIPTION 1450 "Support for Mode 1 is REQUIRED. Other modes are 1451 OPTIONAL. Write access is NOT REQUIRED." 1453 OBJECT frAtmIwfConnClpToDeMappingMode 1454 SYNTAX INTEGER { mode1(1) } 1455 MIN-ACCESS read-only 1456 DESCRIPTION 1457 "Support for Mode 1 is REQUIRED. Other modes are 1458 OPTIONAL. Write access is NOT REQUIRED." 1460 OBJECT frAtmIwfConnCongestionMappingMode 1461 SYNTAX INTEGER { mode1(1) } 1462 MIN-ACCESS read-only 1463 DESCRIPTION 1464 "Support for Mode 1 is REQUIRED. Other modes are 1465 OPTIONAL. Write access is NOT REQUIRED." 1467 OBJECT frAtmIwfConnEncapsulationMappingMode 1468 SYNTAX INTEGER { transparentMode(1) } 1469 MIN-ACCESS read-only 1470 DESCRIPTION 1471 "Support for Transparent Mode is REQUIRED. 1472 Translation Mode is OPTIONAL. Write access is not 1473 required." 1475 OBJECT frAtmIwfConnEncapsulationMappings 1476 SYNTAX BITS { none(0) } 1477 MIN-ACCESS read-only 1478 DESCRIPTION 1479 "The IWF may provide one, some or none of the 1480 encapsulation translations defined in section 1481 5.3.1 of FRF.8 [17]. Write access is not 1482 required." 1484 OBJECT frAtmIwfConnFragAndReassEnabled 1485 SYNTAX INTEGER { disabled(2) } 1486 MIN-ACCESS read-only 1487 DESCRIPTION 1488 "Support for Fragmentation and Reassembly is NOT 1489 REQUIRED. Write access is not required." 1491 OBJECT frAtmIwfConnArpTranslationEnabled 1492 SYNTAX INTEGER { disabled(2) } 1493 MIN-ACCESS read-only 1494 DESCRIPTION 1495 "Support for ARP Translation is not required. 1496 Write access is not required." 1498 OBJECT frAtmIwfConnRowStatus 1499 MIN-ACCESS read-only 1500 DESCRIPTION 1501 "Write access is not required." 1503 ::= { frAtmIwfCompliances 2 } 1505 -- 1506 -- Units of Conformance 1507 -- 1509 -- 1510 -- Basic FR/ATM IWF PVC Connection Group 1511 -- 1512 frAtmIwfBasicGroup OBJECT-GROUP 1513 OBJECTS { frAtmIwfConnIndexNext, 1514 frAtmIwfConnAdminStatus, 1515 frAtmIwfConnAtm2FrOperStatus, 1516 frAtmIwfConnAtm2FrLastChange, 1517 frAtmIwfConnFr2AtmOperStatus, 1518 frAtmIwfConnFr2AtmLastChange, 1519 frAtmIwfConnectionDescriptor, 1520 frAtmIwfConnFailedFrameTranslate, 1521 frAtmIwfConnOverSizedFrames, 1522 frAtmIwfConnFailedAal5PduTranslate, 1523 frAtmIwfConnOverSizedSDUs, 1524 frAtmIwfConnCrcErrors, 1525 frAtmIwfConnSarTimeOuts, 1526 frAtmIwfConnRowStatus } 1527 STATUS current 1528 DESCRIPTION 1529 "The collection of basic objects for configuration 1530 and control of FR/ATM interworking connections." 1531 ::= { frAtmIwfGroups 1 } 1533 -- 1534 -- FR/ATM IWF PVC Connection Descriptor Group 1535 -- 1537 frAtmIwfConnectionDescriptorGroup OBJECT-GROUP 1538 OBJECTS { 1539 frAtmIwfConnectionDescriptorIndexNext, 1540 frAtmIwfConnDeToClpMappingMode, 1541 frAtmIwfConnClpToDeMappingMode, 1542 frAtmIwfConnCongestionMappingMode, 1543 frAtmIwfConnEncapsulationMappingMode, 1544 frAtmIwfConnEncapsulationMappings, 1545 frAtmIwfConnFragAndReassEnabled, 1546 frAtmIwfConnArpTranslationEnabled, 1547 frAtmIwfConnDescriptorRowStatus 1548 } 1549 STATUS current 1550 DESCRIPTION 1551 "The collection of basic objects for specification 1552 of FR/ATM interworking connection descriptors." 1553 ::= { frAtmIwfGroups 2 } 1555 -- 1556 -- ATM MIB VCL Endpoint Table Augmentation Group 1557 -- 1559 frAtmIwfAtmVclTableAugmentGroup OBJECT-GROUP 1560 OBJECTS { 1561 frAtmIwfVclCrossConnectIdentifier 1562 } 1563 STATUS current 1564 DESCRIPTION 1565 "The ATM MIB VCL Endpoint Table AUGMENT object 1566 contained in the FR/ATM PVC Service Interworking 1567 MIB." 1568 ::= { frAtmIwfGroups 3 } 1570 -- 1571 -- Notification Group 1572 -- 1574 frAtmIwfNotificationsGroup NOTIFICATION-GROUP 1575 NOTIFICATIONS { frAtmIwfConnStatusChange } 1576 STATUS current 1577 DESCRIPTION 1578 "The notification for FR/ATM interworking status 1579 change." 1580 ::= { frAtmIwfGroups 4 } 1581 END 1583 8. Acknowledgments 1585 This document was produced by the Frame Relay Service MIB Working 1586 Group. 1588 The Editors thank Bert Wijnen, Kaj Tesink, Keith McCloghrie , and 1589 David Perkins for providing many helpful comments and suggestions. 1591 9. References 1593 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1594 Describing SNMP Management Frameworks", RFC 2571, April 1999 1596 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1597 Management Information for TCP/IP-based Internets", STD 16, RFC 1598 1155, May 1990 1600 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1601 1212, March 1991 1603 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1604 RFC 1215, March 1991 1606 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1607 and S. Waldbusser, "Structure of Management Information Version 2 1608 (SMIv2)", STD 58, RFC 2578, April 1999 1610 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1611 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1612 2579, April 1999 1614 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1615 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1616 2580, April 1999 1618 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1619 Management Protocol", STD 15, RFC 1157, May 1990. 1621 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1622 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1624 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1625 Mappings for Version 2 of the Simple Network Management Protocol 1626 (SNMPv2)", RFC 1906, January 1996. 1628 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1629 Processing and Dispatching for the Simple Network Management 1630 Protocol (SNMP)", RFC 2572, April 1999 1632 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1633 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1634 2574, April 1999 1636 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1637 Operations for Version 2 of the Simple Network Management Protocol 1638 (SNMPv2)", RFC 1905, January 1996. 1640 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1641 2573, April 1999 1643 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1644 Control Model (VACM) for the Simple Network Management Protocol 1645 (SNMP)", RFC 2575, April 1999 1647 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1648 Version 3 of the Internet-standard Network Management Framework", 1649 RFC 2570, April 1999 1651 [17] Frame Relay/ATM PVC Service Interworking Implementation Agreement, 1652 Frame Relay Forum, Document Number FRF.8.1, March, 2000. 1654 [18] Network Working Group, Noto, Spiegel, and Tesink, "Definitions of 1655 Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 1656 2514, February 1999. 1658 [19] Network Working Group, Rehbehn, K., and D. Fowler, "Definitions of 1659 Managed Objects for Frame Relay Service", RFC xxxFRSMIBv2 RFC 1660 Editor assigns xxx, xxxAprilxxx 2000. 1662 [20] Frame Relay/ATM PVC Network Interworking Implementation Agreement, 1663 Frame Relay Forum, Document Number FRF.5, December 20, 1994. 1665 [21] Network Working Group, K. Tesink, "Definitions of Managed Objects 1666 for ATM Management", RFC 2515, February 1999. 1668 [22] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 1669 2233, Cisco Systems, FTP Software, November 1997. 1671 [23] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1672 Levels", BCP 14, RFC 2119, March 1997. 1674 9. Security Considerations 1676 There are a number of management objects defined in this MIB that 1677 have a MAX-ACCESS clause of read-write and/or read-create. Such 1678 objects may be considered sensitive or vulnerable in some network 1679 environments. The support for SET operations in a non-secure 1680 environment without proper protection can have a negative effect on 1681 network operations. 1683 No managed objects in this MIB contain sensitive information. 1685 SNMPv1 by itself is not a secure environment. Even if the network 1686 itself is secure (for example by using IPSec), even then, there is no 1687 control as to who on the secure network is allowed to access and 1688 GET/SET (read/change/create/delete) the objects in this MIB. 1690 It is recommended that the implementers consider the security 1691 features as provided by the SNMPv3 framework. Specifically, the use 1692 of the User-based Security Model RFC 2574 [12] and the View-based 1693 Access Control Model RFC 2575 [15] is recommended. 1695 It is then a customer/user responsibility to ensure that the SNMP 1696 entity giving access to an instance of this MIB, is properly 1697 configured to give access to the objects only to those principals 1698 (users) that have legitimate rights to indeed GET or SET 1699 (change/create/delete) them. 1701 10. Authors' Addresses 1703 Kenneth Rehbehn 1704 Visual Networks 1705 2092 Gaither Road 1706 Rockville, MD, USA 20850 1708 Phone: +1 301 296-2325 1710 EMail: krehbehn@visualnetworks.com 1712 Orly Nicklass 1713 RAD Data Communications, Ltd. 1714 12 Hanechoshet St. 1715 Tel Aviv 69710 1716 Israel 1718 Phone: +972 (3) 6459588 1720 E-mail: orly@radmail.rad.co.il 1722 George Mouradian 1723 AT&T Labs, Room 1G-325 1724 101 Crawfords Corner Road 1725 Holmdel, NJ USA 07733 1727 Phone: +1 908 949 7671 1729 EMail: gvm@att.com 1731 Intellectual Property Rights 1733 The IETF takes no position regarding the validity or scope of any 1734 intellectual property or other rights that might be claimed to 1735 pertain to the implementation or use of the technology described in 1736 this document or the extent to which any license under such rights 1737 might or might not be available; neither does it represent that it 1738 has made any effort to identify any such rights. Information on the 1739 IETF's procedures with respect to rights in standards-track and 1740 standards-related documentation can be found in BCP-11. Copies of 1741 claims of rights made available for publication and any assurances of 1742 licenses to be made available, or the result of an attempt made to 1743 obtain a general license or permission for the use of such 1744 proprietary rights by implementors or users of this specification can 1745 be obtained from the IETF Secretariat. 1747 The IETF invites any interested party to bring to its attention any 1748 copyrights, patents or patent applications, or other proprietary 1749 rights which may cover technology that may be required to practice 1750 this standard. Please address the information to the IETF Executive 1751 Director. 1753 Full Copyright Statement 1755 Copyright (C) The Internet Society (2000). All Rights Reserved. 1757 This document and translations of it may be copied and furnished to 1758 others, and derivative works that comment on or otherwise explain it 1759 or assist in its implementation may be prepared, copied, published 1760 and distributed, in whole or in part, without restriction of any 1761 kind, provided that the above copyright notice and this paragraph are 1762 included on all such copies and derivative works. However, this 1763 document itself may not be modified in any way, such as by removing 1764 the copyright notice or references to the Internet Society or other 1765 Internet organizations, except as needed for the purpose of 1766 developing Internet standards in which case the procedures for 1767 copyrights defined in the Internet Standards process must be 1768 followed, or as required to translate it into languages other than 1769 English. 1771 The limited permissions granted above are perpetual and will not be 1772 revoked by the Internet Society or its successors or assigns. 1774 This document and the information contained herein is provided on an 1775 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1776 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1777 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1778 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1779 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.