idnits 2.17.1 draft-ietf-frnetmib-atmiwf-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 47 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 are 43 instances of too long lines in the document, the longest one being 10 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 639 has weird spacing: '...nnIndex when ...' == Line 1016 has weird spacing: '...orIndex when...' == Line 1676 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 (October 1999) is 8922 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 1563, 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: 18 errors (**), 0 flaws (~~), 9 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft FR/ATM Service Interworking MIB October 1999 3 Definitions of Managed Objects 4 for Monitoring and Controlling the 5 Frame Relay/ATM PVC Service Interworking Function 7 October 5, 1999 9 draft-ietf-frnetmib-atmiwf-03.txt 11 Kenneth Rehbehn 12 Visual Networks 13 krehbehn@visualnetworks.com 15 Orly Nicklass 16 RAD Data Communications, Ltd. 17 Orly_n@rad.co.il 19 George Mouradian 20 AT&T Labs 21 gvm@att.com 23 Status of this Memo 25 This document is an Internet-Draft and is in full conformance with 26 all provisions of Section 10 of RFC2026. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, 28 and its working groups. Note that other groups may also distribute 29 working documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference 34 material or to cite them other than as ``work in progress.'' 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 Abstract 44 This memo defines a Management Information Base (MIB) to configure, 45 monitor, and control a service interworking function (IWF) for 46 Permanent Virtual Connections (PVC) between Frame Relay and 47 Asynchronous Transfer Mode (ATM) technologies. 49 Copyright Notice 51 Copyright (C) The Internet Society (1999). All Rights Reserved. 53 Table of Contents 55 1 The SNMP Management Framework ................................ 4 56 2 Conventions .................................................. 5 57 3 Overview ..................................................... 6 58 3.1 Frame Relay/ATM Service Interworking Background ............ 6 59 3.2 Structure of the MIB ....................................... 7 60 3.3 Relationship to Other MIBs ................................. 8 61 3.3.1 Frame Relay Service MIB .................................. 8 62 3.3.2 Frame Relay DTE MIB ...................................... 8 63 3.3.3 ATM MIB .................................................. 9 64 3.3.4 IF MIB ................................................... 9 65 3.4 Point to Multipoint Considerations ......................... 9 66 3.5 Theory of Operation ........................................ 9 67 3.5.1 Creation Process ......................................... 9 68 3.5.2 Destruction Process ...................................... 13 69 3.5.3 Modification Process ..................................... 14 70 4 Object Definitions ........................................... 15 71 4.1 The FR/ATM PVC Service IWF Connection Group ................ 18 72 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 27 73 5 Frame Relay/ATM PVC Service Interworking NOTIFICATION ........ 34 74 6 Conformance Information ...................................... 35 75 6.1 Compliance Statement For Equipment ......................... 35 76 6.2 Compliance Statement For Service (CNM Interface) ........... 37 77 6.3 Units of Conformance ....................................... 39 78 6.3.1 Basic FR/ATM IWF PVC Connection Group .................... 39 79 6.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 39 80 6.3.4 Notification Group ....................................... 40 81 7 Acknowledgments .............................................. 41 82 8 References ................................................... 42 83 9 Security Considerations ...................................... 44 84 10 Authors' Addresses .......................................... 45 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 frAtmIwfConnectionIndex object. In the case of 197 point-to-point, a single row is present. In the case of point-to- 198 multipoint, one row exists for each multipoint destination. Index 199 objects for the ATM port, VPI, VCI, frame relay port, and frame relay 200 DLCI distinguish the constituent rows used in a point-to-multipoint 201 case. 203 Each inter-worked connection has attributes governing behavior of the 204 IWF. These attributes describe how the IWF should transform a PDU 205 during the forwarding process and provide rules for: 207 (1) Mapping the ATM CLP bit to frame relay DE bit 209 (2) Mapping the ATM congestion notification bit to frame relay 210 congestion bits 212 (3) Mapping higher protocol encapsulations between ATM and frame 213 relay 215 (4) Performing fragmentation and reassembly 217 (5) Performing ARP translation between ATM and frame relay 219 Typically, most connections share the same attributes. The attributes 220 are represented in this MIB by the connection description table. Each 221 row of the connection description table contains the attribute 222 settings common to one or more inter-worked connections. One example 223 would be full mapping and translation. All cross-connect table 224 entries that require full mapping and translation services set the 225 frAtmIwfConnectionDescriptor object to the index value for the 226 connection description table row that contains objects set to values 227 that provide full mapping and translation services. 229 A notification object provides cross-connect status change alerts. 231 3.3. Relationship to Other MIBs 233 The Frame Relay/ATM PVC Service IWF MIB describes the cross- 234 connections between frame relay and ATM service users. Each PVC 235 endpoint is provisioned and managed with a technology-specific MIB as 236 described below. 238 Each technology-specific MIB has a table of PVC endpoints (indexed by 239 ifIndex and logical link address such as the DLCI or VPI/VCI). In the 240 absence of interworking, two endpoints are cross-connected via a 241 technology-specific cross connect table (e.g., the 242 atmVcCrossConnectTable in the ATM MIB). However, a connection 243 between a frame relay endpoint and an ATM endpoint requires a cross- 244 connect in the ATM IWF MIB. 246 The following sections describe the relationship between the 247 different technology-specific MIBs. 249 3.3.1. Frame Relay Service MIB 251 Frame relay PVC endpoints are provisioned as rows in the Frame Relay 252 Services MIB [19] endpoint table. 254 The Frame Relay Services MIB PVC entry object frPVCEndptConnKind 255 identifies the type of connection and appropriate cross-connect 256 table. When frPVCEndptConnKind contains the value 257 fr2AtmServiceIWF(3), then frPVCEndptConnectIdentifier is interpreted 258 as an index to the relevant row in the frAtmIwfConnectionTable of the 259 FR/ATM PVC Service IWF MIB. 261 The frame relay PVC cross-connect table does not contain an entry for 262 the inter-worked connection. 264 3.3.2. Frame Relay DTE MIB 266 The Frame Relay DTE MIB described in [19] has no relevance to the 267 FR/ATM PVC Service IWF MIB. 269 3.3.3. ATM MIB 271 ATM PVC endpoints are provisioned as rows in the ATM MIB [21] virtual 272 connection link table. 274 The ATM MIB Virtual Channel Link (VCL) entry object atmVclConnKind 275 identifies the type of connection and appropriate cross-connect 276 table. When atmVclConnKind contains the value atm2frServiceIWF(6), 277 then atmVclCrossConnectIdentifier is interpreted as an index to the 278 relevant row in the atmVcCrossConnectTable of the ATM MIB. 280 3.3.4. IF MIB 282 The ifIndex defined in the IF MIB [22] identifies the specific frame 283 relay and ATM endpoint interfaces. The values frAtmIwfConnAtmPort 284 and frAtmIwfConnFrPort is used in this MIB as a component in the 285 index list for the frAtmIwfConnectionTable rows. 287 3.4. Point to Multipoint Considerations 289 This MIB supports IWF implementations providing point-to-multipoint 290 functionality. All rows of the cross-connect table indexed by the 291 same frAtmIwfConnectionIndex MUST utilize the same 292 frAtmIwfConnectionDescriptor value. 294 A group of cross-connect table entries indexed by the same 295 frAtmIwfConnectionIndex value MUST agree on which service the 296 multipoint operation is offered. Two cases are possible: 298 (1) Many frame relay PVCs cross-connected to one ATM PVC, or 300 (2) One frame relay PVC cross-connected to many ATM PVCs 302 3.5. Theory of Operation 304 3.5.1. Creation Process 306 Multiple steps are required to create a frame relay to ATM cross- 307 connection. First, rows must be created in the following tables: 309 (1) The Frame Relay Service MIB frPVCEndptTable 310 (2) The ATM MIB atmVclTable 312 (3) The FR/ATM Service IWF MIB frAtmIwfConnectionDescriptorTable 314 (4) The FR/ATM Service IWF MIB frAtmIwfConnectionTable 316 Second, the newly created rows are cross-linked. 318 Finally, the administrative and operational status objects are set to 319 'up'. 321 A step-by-step example is provided to illustrate the creation 322 process. In this example, the term "Manager" refers to a network 323 management system that issues SNMP protocol actions to an "Agent". 324 The agent is integrated with the system that implements the frame 325 relay to ATM service IWF. In this example, the following cross- 326 connection is created: 327 +-------------------------------------+ 328 +---------+ | FR/ATM PVC Service IWF | 329 | Frame | | ------------------------------ | +-----------+ 330 | Relay | +---------> frAtmIwfConnIndex K <---------+ | ATM | 331 |Endpoint | | | V | | | Endpoint | 332 | ------- | | | | | | | --------- | 333 | DLCI X | | | +------------+ | | |VPI.VCI Q.R| 334 | on |<-+ | | | +->| on | 335 |ifIndex Y| | V | | ifIndex S | 336 +---------+ | frAtmIwfConnectionDescriptorIndex L | +-----------+ 337 +-------------------------------------+ 339 Step 1 - Create the frame relay PVC endpoint 341 a) Manager requests creation of a new row in the frPVCEndptTable 343 b) Agent receives management request to create a row in 344 frPVCEndptTable for the frame relay side 346 c) A new row is created in frPVCEndptTable as follows: 348 - frPVCEndptConnectIdentifier initialized to zero 350 - frPVCEndptConnKind initialized to fr2AtmServiceIWF(3) 352 - remaining row objects initialized as needed for DLCI X 353 on ifIndex Y 355 Step 2 - Create the ATM PVC endpoint 357 a) Agent receives management request to create a row in atmVclTable 358 for the ATM side 360 b) A new row is created in atmVclTable as follows: 362 - atmVclCrossConnectIdentifier initialized to zero 364 - atmVclConnKind initialized to atm2frServiceIWF 366 - remaining row objects initialized as needed for VPI.VCI 367 Q.R on ifIndex S 369 Step 3 - Create the FR/ATM connection descriptor 371 a) If an existing connection descriptor is appropriate for the 372 new connection, go to Step 4 using the selected connection 373 descriptor index value L 375 b) Manager request a new connection descriptor index value by 376 reading frAtmIwfConnectionDescriptorIndexNext from the agent 378 c) Agent receives GET request for 379 frAtmIwfConnectionDescriptorIndexNext and responds with the 380 next available value L 382 d) Manager requests a new connection descriptor row entry using 383 the value L as the index 385 e) Agent receives SET request to create the 386 frAtmIwfConnectionDescriptorTable row entry causes the system 387 to create a row in the table. 389 Step 4 - Create the FR/ATM cross-connect 391 a) Manager requests a new cross-connect index value by reading 392 frAtmIwfConnectionIndexNext from the agent 394 b) Agent receives GET request for frAtmIwfConnectionIndexNext 395 and responds with the next available value K 397 c) Manager requests a new cross-connect row entry using the value 398 K as the index 400 d) Agent receives SET request to create the frAtmIwfConnectionTable 401 row entry (note: the frame relay and ATM PVC endpoints MUST exist 402 and be specified as part of the index fields for the 403 row 'K.S.Q.R.Y.X') 405 e) System creates a row in frAtmIwfConnectionTable for the following 406 indices: 408 - frAtmIwfConnectionIndex of K 410 - frAtmIwfConnAtmPort of S 412 - frAtmIwfConnVpi of Q 414 - frAtmIwfConnVci of R 416 - frAtmIwfConnFrPort of Y 418 - frAtmIwfConnDlci of X 420 - frAtmIwfConnectionDescriptor of L 422 Step 5 - Point the frame relay PVC endpoint and ATM VCL rows to the 423 FR/ATM cross-connect row (Note: The system may perform these actions 424 as a side-effect of Step 4) 426 a) System sets frPVCEndptConnectIdentifier to K 428 b) System sets atmVclCrossConnectIdentifier to K 430 Step 6 - Manager signals activation by issuing a SET for the 431 frAtmIwfConnAdminStatus object using the value of 'up' 433 Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus and 434 executes internal system mechanisms to activate each PVC segment and 435 the IWF cross-connect. The successful activation permits the agent to 436 respond with 'active' when a GET request is received for the 437 following fields: 439 - frAtmIwfConnAtm2FrOperStatus 440 - frAtmIwfConnFr2AtmOperStatus 442 - atmVclOperStatus (Note: there is no comparable FRS MIB object) 444 3.5.2. Destruction Process 446 Destruction of the frame relay to ATM cross-connection is initiated 447 by the network management system. The agent's processing of the 448 request stimulates implementation-specific system clean-up actions. 449 Following removal of the row in the cross-connection table, the 450 atmVclCrossConnectIdentifier in the ATM MIB endpoint table and 451 frPVCEndptConnectIdentifier in the Frame Relay Service MIB endpoint 452 table are both re-initialized to zero. 454 A step-by-step example is provided to illustrate the destruction 455 process. 457 Step 1 - Manager requests destruction of an existing row in the 458 frAtmIwfConnectionTable by setting frAtmIwfConnRowStatus to 459 destroy(6) 461 Step 2 - Agent receives the SET request and performs implementation- 462 specific system clean-up actions for the cross-connection row 464 Step 3 - System updates the relevant cross connect information for 465 the frame relay PVC endpoint 467 a) System sets frPVCEndptConnectIdentifier to 0 469 b) System sets frPVCEndptConnKind to none(1) 471 Step 4 - System updates the relevant cross connect information for 472 the ATM PVC endpoint 474 a) System sets atmVclCrossConnectIdentifier to 0 476 b) The atmVclConnKind value remains unchanged 478 c) System sets atmVclOperStatus to 'down' (Note: there is no 479 comparable FRS MIB object) 481 Following the destruction of the FR/ATM cross-connection entry, the 482 manager MAY set the frPVCConnectRowStatus and/or atmVclRowStatus to 483 destroy(6) the associated endpoint entries. 485 3.5.3. Modification Process 487 At the discretion of the agent, a FR/ATM cross-connect may be 488 reconfigured by adding and/or deleting leafs to/from the IWF topology 489 as per the FR/ATM IWF cross-connect creation/destruction procedures. 490 Reconfiguration of traffic/service category parameter values requires 491 release of the FR/ATM IWF cross-connect before those parameter values 492 may be changed for individual frame relay or ATM endpoint segments. 494 4. Object Definitions 496 Managed objects are accessed via a virtual information store, termed 497 the Management Information Base or MIB. Objects in the MIB are 498 defined using the subset of Abstract Syntax Notation One (ASN.1) 499 defined in the SMI. In particular, each object type is named by an 500 OBJECT IDENTIFIER, an administratively assigned name. The object 501 type together with an object instance serves to uniquely identify a 502 specific instantiation of the object. For human convenience, we 503 often use a textual string, termed the descriptor, to refer to the 504 object type. 506 FR-ATM-PVC-SERVICE-IWF-MIB-EXP DEFINITIONS ::= BEGIN 508 IMPORTS 509 MODULE-IDENTITY, OBJECT-TYPE, 510 NOTIFICATION-TYPE, 511 experimental, Integer32, BITS, Counter32 FROM SNMPv2-SMI 513 TEXTUAL-CONVENTION, RowStatus, 514 TimeStamp FROM SNMPv2-TC 516 MODULE-COMPLIANCE, OBJECT-GROUP, 517 NOTIFICATION-GROUP FROM SNMPv2-CONF 519 AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB 521 InterfaceIndex FROM IF-MIB; 523 frAtmIwfMIB MODULE-IDENTITY 524 LAST-UPDATED "9910050000Z" 525 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working 526 Group" 527 CONTACT-INFO 528 "Kenneth Rehbehn 529 Postal: Visual Networks 530 2092 Gaither Road 531 Rockville, MD USA 20850 532 Tel: +1 301 296 2325 533 Fax: +1 301 296 2302 534 E-mail: krehbehn@visualnetworks.com 536 Orly Nicklass 537 Postal: RAD Data Communications Ltd. 538 12 Hanechoshet St. 540 Tel Aviv 69710 541 Israel 542 Tel: +972 (3) 6459588 543 Fax: +972 (3) 6472675 544 E-mail: orly@radmail.rad.co.il 546 George Mouradian 547 Postal: AT&T Labs, Room 1G-325 548 101 Crawfords Corner Road 549 Holmdel, NJ 07733-3030 550 Tel: +1 908 949 7671 551 Email: gvm@att.com" 553 DESCRIPTION 554 "The MIB module for monitoring and controlling the 555 Frame Relay/ATM PVC Service Interworking 556 Function." 558 -- 559 -- Revision History 560 -- 561 REVISION "9910050000Z" 562 DESCRIPTION 563 "Published as draft-ieft-frnetmib-atmiwf-03 564 o Removed PDU translation error group 565 o State that Pt-to-MP is a MAY 566 o Provide translationModeAll 567 o Added oversized frame count 568 o Come to closure on cross-connect strategy 569 o Name change to FR-ATM-PVC-SERVICE-IWF-MIB-EXP" 571 REVISION "9906180000Z" 572 DESCRIPTION 573 "Published as draft-ieft-frnetmib-atmiwf-02 574 o Added new PDU translation error group 575 o Clarified theory of operation and relationship 576 to the ATM and Frame Relay Service MIBs 577 o Update MIB boilerplate to conform to the 578 Operations and Management Area requirements 579 for MIBs" 581 REVISION "9902200000Z" 582 DESCRIPTION 583 "Published as draft-ieft-frnetmib-atmiwf-01 584 o Isolated connection description objects 585 in frAtmIwfConnectionDescriptorTable 586 o Improved text for a number of objects 587 o Added OperStatus objects to Notification 588 for both frame and ATM sides 589 o Set OID values 590 o Clean smicng compile" 592 REVISION "9611250000Z" 593 DESCRIPTION 594 "Published as draft-ieft-frnetmib-atmiwf-00" 595 ::= { experimental 97 } 597 -- 598 -- Object Identifiers 599 -- 600 frAtmIwfMIBObjects OBJECT IDENTIFIER 601 ::= { frAtmIwfMIB 1 } 603 frAtmIwfTraps OBJECT IDENTIFIER 604 ::= { frAtmIwfMIB 2 } 605 frAtmIwfTrapsPrefix OBJECT IDENTIFIER 606 ::= { frAtmIwfTraps 0 } 608 frAtmIwfConformance OBJECT IDENTIFIER 609 ::= { frAtmIwfMIB 3 } 610 frAtmIwfGroups OBJECT IDENTIFIER 611 ::= { frAtmIwfConformance 1 } 612 frAtmIwfCompliances OBJECT IDENTIFIER 613 ::= { frAtmIwfConformance 2 } 615 -- 616 -- Textual Conventions 617 -- 619 Dlci ::= TEXTUAL-CONVENTION 620 STATUS current 621 DESCRIPTION 622 "This data type is a DLCI for a PVC segment end-point." 623 SYNTAX Integer32 (16..4194303) 625 -- 626 -- The FR/ATM PVC Service IWF Group 627 -- 628 -- The Frame Relay/ATM PVC Service Interworking Function 629 -- Connection Table contains all connections utilizing 630 -- the interworking function. 631 -- 633 frAtmIwfConnIndexNext OBJECT-TYPE 634 SYNTAX Integer32 (0..2147483647) 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "This object contains an appropriate value to be 639 used for frAtmIwfConnIndex when creating entries 640 in the frAtmIwfConnectionTable. The value 0 641 indicates that no unassigned entries are 642 available. To obtain the frAtmIwfConnIndexNext 643 value for a new entry, the manager issues a 644 management protocol retrieval operation to obtain 645 the current value of this object. After each 646 retrieval, the agent should modify the value to 647 the next unassigned index." 648 ::= { frAtmIwfMIBObjects 1 } 650 frAtmIwfConnectionTable OBJECT-TYPE 651 SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry 652 MAX-ACCESS not-accessible 653 STATUS current 654 DESCRIPTION 655 "A table in which each row represents a Frame 656 Relay/ATM interworking connection." 657 ::= { frAtmIwfMIBObjects 2 } 659 frAtmIwfConnectionEntry OBJECT-TYPE 660 SYNTAX FrAtmIwfConnectionEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "The FrAtmIwfConnectionEntry provides an entry for 665 an interworking connection between a frame relay 666 PVC and one or more ATM PVCs, or an ATM PVC and 667 one or more frame relay PVCs. A single frame 668 relay PVC connected to a single ATM PVC is 669 referred to as a `point-to-point' connection and 670 is represented by a single row in the FR/ATM IWF 671 Connection Table. The case of a single frame 672 relay PVC connected to multiple ATM PVCs (or 673 single ATM PVC connected to multiple frame relay 674 PVCs) is referred to as a `point-to-multipoint' 675 connection and is represented by multiple rows in 676 the FR/ATM IWF Connection Table. 678 The object frAtmIwfConnIndex uniquely identifies 679 each point-to-point or point-to-multipoint 680 connection. The manager obtains the 681 frAtmIwfConnIndex value by reading the 682 frAtmIwfConnIndexNext object. 684 After a frAtmIwfConnIndex is assigned for the 685 connection, the manager creates one or more rows 686 in the Cross Connect Table; one for each cross- 687 connection between the frame relay PVC and an ATM 688 PVC. In the case of `point-to-multipoint' 689 connections, all rows are indexed by the same 690 frAtmIwfConnIndex value and MUST refer to the same 691 frame relay PVC or ATM PVC respectively. An entry 692 can be created only when at least one pair of 693 frame relay and ATM PVCs exist. 695 A row can be established by one-step set-request 696 with all required parameter values and 697 frAtmIwfConnRowStatus set to createAndGo(4). The 698 Agent should perform all error checking as needed. 699 A pair of cross-connected PVCs, as identified by a 700 particular value of the indexes, is released by 701 setting frAtmIwfConnRowStatus to destroy(6). The 702 Agent may release all associated resources. The 703 manager may remove the related PVCs thereafter. 704 Indexes are persistent across reboots of the 705 system." 706 INDEX { frAtmIwfConnIndex, 707 frAtmIwfConnAtmPort, 708 frAtmIwfConnVpi, 709 frAtmIwfConnVci, 710 frAtmIwfConnFrPort, 711 frAtmIwfConnDlci 712 } 713 ::= { frAtmIwfConnectionTable 1 } 715 FrAtmIwfConnectionEntry ::= 716 SEQUENCE { 717 frAtmIwfConnIndex Integer32, 718 frAtmIwfConnAtmPort InterfaceIndex, 719 frAtmIwfConnVpi AtmVpIdentifier, 720 frAtmIwfConnVci AtmVcIdentifier, 721 frAtmIwfConnFrPort InterfaceIndex, 722 frAtmIwfConnDlci Dlci, 723 frAtmIwfConnRowStatus RowStatus, 724 frAtmIwfConnAdminStatus INTEGER, 725 frAtmIwfConnAtm2FrOperStatus INTEGER, 726 frAtmIwfConnAtm2FrLastChange TimeStamp, 727 frAtmIwfConnFr2AtmOperStatus INTEGER, 728 frAtmIwfConnFr2AtmLastChange TimeStamp, 729 frAtmIwfConnectionDescriptor Integer32, 730 frAtmIwfConnFailedFrameTranslate Counter32, 731 frAtmIwfConnOverSizedFrames Counter32, 732 frAtmIwfConnFailedAal5PduTranslate Counter32, 733 frAtmIwfConnOverSizedSDUs Counter32, 734 frAtmIwfConnCrcErrors Counter32, 735 frAtmIwfConnSarTimeOuts Counter32 736 } 738 frAtmIwfConnIndex OBJECT-TYPE 739 SYNTAX Integer32 (1..2147483647) 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "A unique index to identify this interworking 744 connection." 745 ::= { frAtmIwfConnectionEntry 1 } 747 frAtmIwfConnAtmPort OBJECT-TYPE 748 SYNTAX InterfaceIndex 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "The index in the ifTable that identifies the ATM 753 port for this interworking connection." 754 ::= { frAtmIwfConnectionEntry 2 } 756 frAtmIwfConnVpi OBJECT-TYPE 757 SYNTAX AtmVpIdentifier 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "The VPI of the ATM PVC end point for this 762 interworking connection." 763 ::= { frAtmIwfConnectionEntry 3 } 765 frAtmIwfConnVci OBJECT-TYPE 766 SYNTAX AtmVcIdentifier 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "The VCI of the ATM PVC end point for this 771 interworking 772 connection." 773 ::= { frAtmIwfConnectionEntry 4 } 775 frAtmIwfConnFrPort OBJECT-TYPE 776 SYNTAX InterfaceIndex 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "The index in the ifTable that identifies the 781 frame relay port for this interworking 782 connection." 783 ::= { frAtmIwfConnectionEntry 5 } 785 frAtmIwfConnDlci OBJECT-TYPE 786 SYNTAX Dlci 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "The DLCI that identifies the frame relay PVC end 791 point for this interworking connection." 792 ::= { frAtmIwfConnectionEntry 6 } 794 frAtmIwfConnRowStatus OBJECT-TYPE 795 SYNTAX RowStatus 796 MAX-ACCESS read-create 797 STATUS current 798 DESCRIPTION 799 "The table row may be created with 'createAndWait' 800 or 'createAndGo'. 802 To activate a connection entry, a valid connection 803 descriptor MUST be established in the 804 frAtmIwfConnectionDescriptor object and the 805 AdminStatus of the corresponding endpoints MUST be 806 'up' & 'active'. 808 This object is set to 'destroy' to delete the 809 table row. To deactivate a connection entry, the 810 AdminStatus of the corresponding endpoints MUST be 811 'down' & 'inactive'. Otherwise, 'destroy' 812 operation MUST fail (error code 813 'inconsistentValue')." 814 ::= { frAtmIwfConnectionEntry 7 } 816 frAtmIwfConnAdminStatus OBJECT-TYPE 817 SYNTAX INTEGER { up(1), down(2) } 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 "The desired operational state for this 822 interworking connection." 823 ::= { frAtmIwfConnectionEntry 8 } 825 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE 826 SYNTAX INTEGER { up(1), down(2) } 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The current operational state of this 831 interworking connection in the direction from ATM 832 to FR end." 833 ::= { frAtmIwfConnectionEntry 9 } 835 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE 836 SYNTAX TimeStamp 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The value of sysUpTime at the time this 841 interworking connection entered its current 842 operational state in the ATM to FR direction. If 843 the current state was entered prior to the last 844 re-initialization of the local network management 845 subsystem, then this object contains a zero 846 value." 847 ::= { frAtmIwfConnectionEntry 10 } 849 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE 850 SYNTAX INTEGER { up(1), down(2) } 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The current operational state of this 855 interworking connection in the direction from FR 856 to ATM end." 857 ::= { frAtmIwfConnectionEntry 11 } 859 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE 860 SYNTAX TimeStamp 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The value of sysUpTime at the time this 865 interworking connection entered its current 866 operational state in the FR to ATM direction. If 867 the current state was entered prior to the last 868 re-initialization of the local network management 869 subsystem, then this object contains a zero 870 value." 871 ::= { frAtmIwfConnectionEntry 12 } 873 frAtmIwfConnectionDescriptor OBJECT-TYPE 874 SYNTAX Integer32 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "The value represents a pointer to the relevant 879 descriptor in the IWF descriptor table. An 880 attempt to set this value to an inactive or non- 881 existant row in the Connection Descriptor Table 882 MUST fail (error code 'inconsistentValue')." 883 ::= { frAtmIwfConnectionEntry 13 } 885 frAtmIwfConnFailedFrameTranslate OBJECT-TYPE 886 SYNTAX Counter32 887 UNITS "Frames" 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "This object counts the number of frames discarded 892 by the IWF because, while operating in Translation 893 Mode, the IWF is unable to decode the incoming 894 frame payload header according to the mapping 895 rules. (i.e., payload header not recognized by the 896 IWF). 898 Frame relay frames are received in the frame relay 899 to ATM direction of the PVC. 901 When operating in Transparent Mode, the IWF MUST 902 return noSuchInstance." 903 REFERENCE 904 "FRF.8 [17], Section 5.3.1" 905 ::= { frAtmIwfConnectionEntry 14 } 907 frAtmIwfConnOverSizedFrames OBJECT-TYPE 908 SYNTAX Counter32 909 UNITS "Frames" 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "Count of frames discarded by the IWF because the 914 frame is too large to be processed by the AAL5 915 segmentation procedure. Specifically, the frame 916 does not conform to the size specified in the 917 atmVccAal5CpcsTransmitSduSize object associated 918 with the atmVclEntry at the ATM endpoint. 920 Frame relay frames are received in the frame relay 921 to ATM direction of the PVC." 922 REFERENCE 923 "ATM MIB [21], atmVclTable 924 FRF.8 [17], 5.3.1.4" 925 ::= { frAtmIwfConnectionEntry 15 } 927 frAtmIwfConnFailedAal5PduTranslate OBJECT-TYPE 928 SYNTAX Counter32 929 UNITS "PDUs" 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION 933 "This attribute counts the number of AAL5 PDUs 934 discarded by the IWF because, while operating in 935 Translation Mode, the IWF is unable to decode the 936 incoming AAL5 PDU payload header according to the 937 mapping rules. (i.e., payload header not 938 recognized by the IWF). 940 AAL5 PDUs are received in the ATM to frame relay 941 direction of the PVC. 943 When operating in Transparent Mode, the IWF MUST 944 return noSuchInstance." 945 REFERENCE 946 "FRF.8 [17], Section 5.3.1" 947 ::= { frAtmIwfConnectionEntry 16 } 949 frAtmIwfConnOverSizedSDUs OBJECT-TYPE 950 SYNTAX Counter32 951 UNITS "SDUs" 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "Count of AAL5 SDUs discarded by the IWF because 956 the SDU is too large to be forwarded on the frame 957 relay segment of the connection. Specifically, 958 the frame does not conform to the size specified 959 in the frLportFragSize object of the FRS MIB [19]. 961 AAL5 PDUs are received in the ATM to frame relay 962 direction of the PVC." 963 REFERENCE 964 "FRS MIB [19], frLportTable 965 FRF.8 [17], 5.3.1.4" 966 ::= { frAtmIwfConnectionEntry 17 } 968 frAtmIwfConnCrcErrors OBJECT-TYPE 969 SYNTAX Counter32 970 UNITS "PDUs" 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "The number of AAL5 CPCS PDUs received with CRC-32 975 errors on this AAL5 VCC at the IWF. 977 AAL5 PDUs are received in the ATM to frame relay 978 direction of the PVC." 979 REFERENCE 980 "ATM MIB [21], atmVclTable" 981 ::= { frAtmIwfConnectionEntry 18 } 983 frAtmIwfConnSarTimeOuts OBJECT-TYPE 984 SYNTAX Counter32 985 UNITS "PDUs" 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "The number of partially re-assembled AAL5 CPCS 990 PDUs which were discarded on this AAL5 VCC at the 991 IWF because they were not fully re-assembled 992 within the required time period. If the re- 993 assembly timer is not supported, then this object 994 contains a zero value. 996 AAL5 PDUs are received in the ATM to frame relay 997 direction of the PVC." 998 REFERENCE 999 "ATM MIB [21], atmVclTable" 1000 ::= { frAtmIwfConnectionEntry 19 } 1002 -- 1003 -- The FR/ATM PVC Service IWF Connection Descriptor Group 1004 -- 1005 -- The Frame Relay/ATM PVC Service Interworking Function 1006 -- Connection Descriptor table. A descriptor provides the 1007 -- attributes for a type of interworked connection. 1008 -- 1010 frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE 1011 SYNTAX Integer32 (0..2147483647) 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "This object contains an appropriate value to be 1016 used for frAtmIwfConnectionDescriptorIndex when 1017 creating entries in the 1018 frAtmIwfConnectionDescriptorTable. The value 0 1019 indicates that no unassigned entries are 1020 available. To obtain the 1021 frAtmIwfConnectionDescriptorIndexNext value for a 1022 new entry, the manager issues a management 1023 protocol retrieval operation to obtain the current 1024 value of this object. After each retrieval, the 1025 agent should modify the value to the next 1026 unassigned index." 1027 ::= { frAtmIwfMIBObjects 3 } 1029 frAtmIwfConnectionDescriptorTable OBJECT-TYPE 1030 SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "A table in which each row represents a descriptor 1035 for one type of Frame Relay/ATM interworking 1036 connection. A descriptor may be assigned to zero 1037 or more FR/ATM PVC service IWF connections." 1038 ::= { frAtmIwfMIBObjects 4 } 1040 frAtmIwfConnectionDescriptorEntry OBJECT-TYPE 1041 SYNTAX FrAtmIwfConnectionDescriptorEntry 1042 MAX-ACCESS not-accessible 1043 STATUS current 1044 DESCRIPTION 1045 "An entry for a descriptor in an interworking 1046 connection between a frame relay PVC and an ATM 1047 PVC." 1048 INDEX { frAtmIwfConnectionDescriptorIndex } 1049 ::= { frAtmIwfConnectionDescriptorTable 1 } 1051 FrAtmIwfConnectionDescriptorEntry ::= 1052 SEQUENCE { 1053 frAtmIwfConnectionDescriptorIndex Integer32, 1054 frAtmIwfConnDescriptorRowStatus RowStatus, 1055 frAtmIwfConnDeToClpMappingMode INTEGER, 1056 frAtmIwfConnClpToDeMappingMode INTEGER, 1057 frAtmIwfConnCongestionMappingMode INTEGER, 1058 frAtmIwfConnEncapsulationMappingMode INTEGER, 1059 frAtmIwfConnEncapsulationMappings BITS, 1060 frAtmIwfConnFragAndReassEnabled INTEGER, 1061 frAtmIwfConnArpTranslationEnabled INTEGER 1062 } 1064 frAtmIwfConnectionDescriptorIndex OBJECT-TYPE 1065 SYNTAX Integer32 (1..2147483647) 1066 MAX-ACCESS not-accessible 1067 STATUS current 1068 DESCRIPTION 1069 "A unique value to identify a descriptor in the 1070 table " 1071 ::= { frAtmIwfConnectionDescriptorEntry 1 } 1073 frAtmIwfConnDescriptorRowStatus OBJECT-TYPE 1074 SYNTAX RowStatus 1075 MAX-ACCESS read-create 1076 STATUS current 1077 DESCRIPTION 1078 "The status of this table row. This object is 1079 used to create or delete an entry in the 1080 descriptor table. 1082 Creation of the row requires a row index (see 1083 frAtmIwfConnectionDescriptorIndexNext). If not 1084 explicitly set or in existence, all other columns 1085 of the row will be created and initialized to the 1086 default value. During creation, this object MAY 1087 be set to The object MUST contain the value 1088 'active' before any connection table entry 1089 references the row. 1091 To destroy a row in this table, this object is set 1092 to the 'destroy' action. Row destruction MUST 1093 fail (error code 'inconsistentValue') if any 1094 connection references the row." 1095 ::= { frAtmIwfConnectionDescriptorEntry 2 } 1097 frAtmIwfConnDeToClpMappingMode OBJECT-TYPE 1098 SYNTAX INTEGER { 1099 mode1(1), 1100 mode2Const0(2), 1101 mode2Const1(3) 1102 } 1103 MAX-ACCESS read-create 1104 STATUS current 1105 DESCRIPTION 1106 "This object describes which mode of translation 1107 is in use for loss priority mapping in the frame 1108 relay to ATM direction. 1110 mode1 = the DE field in the Q.922 core frame 1111 shall be mapped to the ATM CLP filed 1112 of every cell generated by the 1113 segmentation process of the AAL5 1114 PDU containing the information of 1115 that frame. 1117 mode2Contst0 = the ATM CLP filed of every cell 1118 generated by the segmentation process 1119 of the AAL5 PDU containing the 1120 information of that frame shall be 1121 set to constant 0. 1123 mode2Contst1 = the ATM CLP filed of every cell 1124 generated by the segmentation process 1125 of the AAL5 PDU containing the 1126 information of that frame shall be set 1127 to constant 1." 1128 REFERENCE 1129 "FRF.8 [17], Section 4.2.1" 1130 DEFVAL { mode1 } 1131 ::= { frAtmIwfConnectionDescriptorEntry 3 } 1133 frAtmIwfConnClpToDeMappingMode OBJECT-TYPE 1134 SYNTAX INTEGER { 1135 mode1(1), 1136 mode2Const0(2), 1137 mode2Const1(3) 1138 } 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "This object describes which mode of translation 1143 is in use for loss priority mapping in the ATM to 1144 frame relay direction. 1146 mode1 = if one or more cells in a frame has its CLP 1147 field set, the DE field of the Q.922 core 1148 frame should be set. 1150 mode2Const0 = the DE field of the Q.922 core frame should 1151 be set to constant 0. 1153 mode2Const1 = the DE field of the Q.922 core frame should 1154 be set to constant 1." 1156 REFERENCE 1157 "FRF.8 [17], Section 4.2.2" 1158 DEFVAL { mode1 } 1159 ::= { frAtmIwfConnectionDescriptorEntry 4 } 1161 frAtmIwfConnCongestionMappingMode OBJECT-TYPE 1162 SYNTAX INTEGER { 1163 mode1(1), 1164 mode2(2) 1165 } 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "This object describes which mode of translation 1170 is in use for forward congestion indication 1171 mapping in the frame relay to ATM direction. 1173 mode1 = The FECN field in the Q.922 core frame shall be 1174 mapped to the ATM EFCI field of every cell 1175 generated by the segmentation process of the 1176 AAL5 PDU containing the information of that 1177 frame. 1179 mode2 = The FECN field in the Q.922 core frame shall not 1180 be mapped to the ATM EFCI field of cells 1181 generated by the segmentation process of the AAL5 1182 PDU containing the information of that frame. 1183 The EFCI field is always set to 'congestion not 1184 experienced'. 1186 In both of the modes above, if there is congestion 1187 in the forward direction in the ATM layer within 1188 the IWF, then the IWF can set the EFCI field to 1189 'congestion experienced'." 1190 REFERENCE 1191 "FRF.8 [17], Section 4.3.1.1" 1192 DEFVAL { mode1 } 1193 ::= { frAtmIwfConnectionDescriptorEntry 5 } 1195 frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE 1196 SYNTAX INTEGER { 1197 transparentMode(1), 1198 translationMode(2), 1199 translationModeAll(3) 1200 } 1201 MAX-ACCESS read-create 1202 STATUS current 1203 DESCRIPTION 1204 "This object indicates whether the mapping of 1205 upper layer protocol encapsulation is enabled on 1206 this interworking connection. 1208 transparentMode = Forward the encapsulations unaltered. 1210 translationMode = Perform mapping between the two 1211 encapsulations due to the 1212 incompatibilities of the two methods. 1213 Mapping is provided for a subset of the 1214 potential encapsulations as itemized in 1215 frAtmIwfConnEncapsulationMappings. 1217 translationModeAll = Perform mapping between the two 1218 encapsulations due to the 1219 incompatibilities of the two methods. 1220 All encapsulations are translated." 1221 REFERENCE 1222 "FRF.8 [17], Section 5.3" 1223 DEFVAL { transparentMode } 1224 ::= { frAtmIwfConnectionDescriptorEntry 6 } 1226 frAtmIwfConnEncapsulationMappings OBJECT-TYPE 1227 SYNTAX BITS { 1228 none (0), -- Transparent mode operation 1229 bridgedPdus(1), -- PID: 0x00-01,-07,-02 or -08 1230 bridged802dot6(2), -- PID: 0x00-0B 1231 bPdus(3), -- PID: 0x00-0E or -0F 1232 routedIp(4), -- NLPID: OxCC 1233 routedOsi(5), -- NLPID: Ox81, 0x82 or 0x83 1234 otherRouted(6), -- 1235 x25Iso8202(7), -- 1236 q933q2931(8) } 1237 MAX-ACCESS read-create 1238 STATUS current 1239 DESCRIPTION 1240 "If upper layer protocol encapsulation mapping is 1241 enabled on this interworking connection, then this 1242 attribute enumerates which of the encapsulation 1243 mappings are supported." 1244 REFERENCE 1245 "FRF.8 [17], Section 5.3.1" 1246 DEFVAL { { none } } 1247 ::= { frAtmIwfConnectionDescriptorEntry 7 } 1249 frAtmIwfConnFragAndReassEnabled OBJECT-TYPE 1250 SYNTAX INTEGER { enabled(1), disabled(2)} 1251 MAX-ACCESS read-create 1252 STATUS current 1253 DESCRIPTION 1254 "The attribute indicates whether fragmentation and 1255 reassembly is enabled for this connection." 1256 REFERENCE 1257 "FRF.8 [17], Section 5.3.1.4" 1258 DEFVAL { disabled } 1259 ::= { frAtmIwfConnectionDescriptorEntry 8 } 1261 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE 1262 SYNTAX INTEGER { enabled(1), disabled(2)} 1263 MAX-ACCESS read-create 1264 STATUS current 1265 DESCRIPTION 1266 "The attribute indicates whether ARP translation 1267 is enabled for this connection." 1268 REFERENCE 1269 "FRF.8 [17], Section 5.4" 1270 DEFVAL { disabled } 1271 ::= { frAtmIwfConnectionDescriptorEntry 9 } 1273 -- 1274 -- Frame Relay/ATM PVC Service Interworking NOTIFICATION 1275 -- 1277 frAtmIwfConnStatusChange NOTIFICATION-TYPE 1278 OBJECTS { frAtmIwfConnAdminStatus, 1279 frAtmIwfConnAtm2FrOperStatus, 1280 frAtmIwfConnFr2AtmOperStatus 1281 } 1282 STATUS current 1283 DESCRIPTION 1284 "An indication that the status of this 1285 interworking connection has changed." 1286 ::= { frAtmIwfTrapsPrefix 1 } 1288 -- 1289 -- Conformance Information 1290 -- 1292 -- 1293 -- Compliance Statement For Equipment 1294 -- 1296 frAtmIwfEquipmentCompliance MODULE-COMPLIANCE 1297 STATUS current 1298 DESCRIPTION 1299 "The compliance statement for equipment that 1300 implements the FR/ATM Interworking MIB." 1302 MODULE -- this module 1303 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1304 frAtmIwfConnectionDescriptorGroup, 1305 frAtmIwfNotificationsGroup } 1307 OBJECT frAtmIwfConnDeToClpMappingMode 1308 SYNTAX INTEGER { mode1(1) } 1309 DESCRIPTION 1310 "Only support for Mode 1 is REQUIRED." 1312 OBJECT frAtmIwfConnClpToDeMappingMode 1313 SYNTAX INTEGER { mode1(1) } 1314 DESCRIPTION 1315 "Only support for Mode 1 is REQUIRED." 1317 OBJECT frAtmIwfConnCongestionMappingMode 1318 SYNTAX INTEGER { mode1(1) } 1319 DESCRIPTION 1320 "Only support for Mode 1 is REQUIRED." 1322 OBJECT frAtmIwfConnEncapsulationMappingMode 1323 SYNTAX INTEGER { transparentMode(1) } 1324 DESCRIPTION 1325 "Support for Translation Mode is OPTIONAL." 1327 OBJECT frAtmIwfConnEncapsulationMappings 1328 SYNTAX BITS { none(0) } 1329 DESCRIPTION 1330 "The IWF may provide one, some or none of the 1331 encapsulation translations defined in section 1332 5.3.1 of FRF.8 [17]." 1334 OBJECT frAtmIwfConnFragAndReassEnabled 1335 SYNTAX INTEGER { disabled(2) } 1336 DESCRIPTION 1337 "Only support for Mode 1 is REQUIRED." 1339 OBJECT frAtmIwfConnArpTranslationEnabled 1340 SYNTAX INTEGER { disabled(2) } 1341 DESCRIPTION 1342 "Support for ARP Translation is NOT REQUIRED." 1344 ::= { frAtmIwfCompliances 1 } 1346 -- 1347 -- Compliance Statement For Service (CNM Interface) 1348 -- 1350 frAtmIwfServiceCompliance MODULE-COMPLIANCE 1351 STATUS current 1352 DESCRIPTION 1353 "The compliance statement for a CNM interface that 1354 implements the FR/ATM Interworking MIB." 1356 MODULE -- this module 1357 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1358 frAtmIwfConnectionDescriptorGroup, 1359 frAtmIwfNotificationsGroup } 1361 -- 1362 -- Exceptions for each object type implemented for a 1363 -- CNM view of the FR/ATM Interworking MIB 1364 -- 1365 OBJECT frAtmIwfConnAdminStatus 1366 MIN-ACCESS read-only 1367 DESCRIPTION 1368 "Write access is not REQUIRED." 1370 OBJECT frAtmIwfConnDeToClpMappingMode 1371 SYNTAX INTEGER { mode1(1) } 1372 MIN-ACCESS read-only 1373 DESCRIPTION 1374 "Support for Mode 1 is REQUIRED. Other modes are 1375 OPTIONAL. Write access is NOT REQUIRED." 1377 OBJECT frAtmIwfConnClpToDeMappingMode 1378 SYNTAX INTEGER { mode1(1) } 1379 MIN-ACCESS read-only 1380 DESCRIPTION 1381 "Support for Mode 1 is REQUIRED. Other modes are 1382 OPTIONAL. Write access is NOT REQUIRED." 1384 OBJECT frAtmIwfConnCongestionMappingMode 1385 SYNTAX INTEGER { mode1(1) } 1386 MIN-ACCESS read-only 1387 DESCRIPTION 1388 "Support for Mode 1 is REQUIRED. Other modes are 1389 OPTIONAL. Write access is NOT REQUIRED." 1391 OBJECT frAtmIwfConnEncapsulationMappingMode 1392 SYNTAX INTEGER { transparentMode(1) } 1393 MIN-ACCESS read-only 1394 DESCRIPTION 1395 "Support for Transparent Mode is REQUIRED. 1396 Translation Mode is OPTIONAL. Write access is not 1397 required." 1399 OBJECT frAtmIwfConnEncapsulationMappings 1400 SYNTAX BITS { none(0) } 1401 MIN-ACCESS read-only 1402 DESCRIPTION 1403 "The IWF may provide one, some or none of the 1404 encapsulation translations defined in section 1405 5.3.1 of FRF.8 [17]. Write access is not 1406 required." 1408 OBJECT frAtmIwfConnFragAndReassEnabled 1409 SYNTAX INTEGER { disabled(2) } 1410 MIN-ACCESS read-only 1411 DESCRIPTION 1412 "Support for Fragmentation and Reassembly is NOT 1413 REQUIRED. Write access is not required." 1415 OBJECT frAtmIwfConnArpTranslationEnabled 1416 SYNTAX INTEGER { disabled(2) } 1417 MIN-ACCESS read-only 1418 DESCRIPTION 1419 "Support for ARP Translation is not required. 1420 Write access is not required." 1422 OBJECT frAtmIwfConnRowStatus 1423 MIN-ACCESS read-only 1424 DESCRIPTION 1425 "Write access is not required." 1427 ::= { frAtmIwfCompliances 2 } 1429 -- 1430 -- Units of Conformance 1431 -- 1433 -- 1434 -- Basic FR/ATM IWF PVC Connection Group 1435 -- 1436 frAtmIwfBasicGroup OBJECT-GROUP 1437 OBJECTS { frAtmIwfConnIndexNext, 1438 frAtmIwfConnAdminStatus, 1439 frAtmIwfConnAtm2FrOperStatus, 1440 frAtmIwfConnAtm2FrLastChange, 1441 frAtmIwfConnFr2AtmOperStatus, 1442 frAtmIwfConnFr2AtmLastChange, 1443 frAtmIwfConnectionDescriptor, 1444 frAtmIwfConnFailedFrameTranslate, 1445 frAtmIwfConnOverSizedFrames, 1446 frAtmIwfConnFailedAal5PduTranslate, 1447 frAtmIwfConnOverSizedSDUs, 1448 frAtmIwfConnCrcErrors, 1449 frAtmIwfConnSarTimeOuts, 1450 frAtmIwfConnRowStatus } 1451 STATUS current 1452 DESCRIPTION 1453 "The collection of basic objects for configuration 1454 and control of FR/ATM interworking connections." 1455 ::= { frAtmIwfGroups 1 } 1457 -- 1458 -- FR/ATM IWF PVC Connection Descriptor Group 1459 -- 1461 frAtmIwfConnectionDescriptorGroup OBJECT-GROUP 1462 OBJECTS { 1463 frAtmIwfConnectionDescriptorIndexNext, 1464 frAtmIwfConnDeToClpMappingMode, 1465 frAtmIwfConnClpToDeMappingMode, 1466 frAtmIwfConnCongestionMappingMode, 1467 frAtmIwfConnEncapsulationMappingMode, 1468 frAtmIwfConnEncapsulationMappings, 1469 frAtmIwfConnFragAndReassEnabled, 1470 frAtmIwfConnArpTranslationEnabled, 1471 frAtmIwfConnDescriptorRowStatus 1472 } 1473 STATUS current 1474 DESCRIPTION 1475 "The collection of basic objects for specification 1476 of FR/ATM interworking connection descriptors." 1477 ::= { frAtmIwfGroups 2 } 1479 -- 1480 -- Notification Group 1481 -- 1483 frAtmIwfNotificationsGroup NOTIFICATION-GROUP 1484 NOTIFICATIONS { frAtmIwfConnStatusChange } 1485 STATUS current 1486 DESCRIPTION 1487 "The notification for FR/ATM interworking status 1488 change." 1489 ::= { frAtmIwfGroups 4 } 1490 END 1492 7. Acknowledgments 1494 This document was produced by the Frame Relay Service MIB Working 1495 Group. 1497 The Editors thank Bert Wijnen and Kaj Tesink for their helpful 1498 comments and suggestions. 1500 8. References 1502 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1503 Describing SNMP Management Frameworks", RFC 2571, April 1999 1505 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1506 Management Information for TCP/IP-based Internets", STD 16, RFC 1507 1155, May 1990 1509 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1510 1212, March 1991 1512 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1513 RFC 1215, March 1991 1515 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1516 and S. Waldbusser, "Structure of Management Information Version 2 1517 (SMIv2)", STD 58, RFC 2578, April 1999 1519 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1520 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1521 2579, April 1999 1523 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1524 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1525 2580, April 1999 1527 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1528 Management Protocol", STD 15, RFC 1157, May 1990. 1530 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1531 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1533 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1534 Mappings for Version 2 of the Simple Network Management Protocol 1535 (SNMPv2)", RFC 1906, January 1996. 1537 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1538 Processing and Dispatching for the Simple Network Management 1539 Protocol (SNMP)", RFC 2572, April 1999 1541 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1542 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1543 2574, April 1999 1545 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1546 Operations for Version 2 of the Simple Network Management Protocol 1547 (SNMPv2)", RFC 1905, January 1996. 1549 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1550 2573, April 1999 1552 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1553 Control Model (VACM) for the Simple Network Management Protocol 1554 (SNMP)", RFC 2575, April 1999 1556 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1557 Version 3 of the Internet-standard Network Management Framework", 1558 RFC 2570, April 1999 1560 [17] Frame Relay/ATM PVC Service Interworking Implementation Agreement, 1561 Frame Relay Forum, Document Number FRF.8, April 14, 1995. 1563 [18] Network Working Group, Noto, Spiegel, and Tesink, "Definitions of 1564 Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 1565 2514, February 1999. 1567 [19] Network Working Group, Rehbehn, K., and D. Fowler, "Definitions of 1568 Managed Objects for Frame Relay Service", RFC xxFRSMIBv2xxx, 1569 October 1999. 1571 [20] Frame Relay/ATM PVC Network Interworking Implementation Agreement, 1572 Frame Relay Forum, Document Number FRF.5, December 20, 1994. 1574 [21] Network Working Group, K. Tesink, "Definitions of Managed Objects 1575 for ATM Management", RFC 2515, February 1999. 1577 [22] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 1578 2233, Cisco Systems, FTP Software, November 1997. 1580 [23] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1581 Levels", BCP 14, RFC 2119, March 1997. 1583 9. Security Considerations 1585 There are a number of management objects defined in this MIB that 1586 have a MAX-ACCESS clause of read-write and/or read-create. Such 1587 objects may be considered sensitive or vulnerable in some network 1588 environments. The support for SET operations in a non-secure 1589 environment without proper protection can have a negative effect on 1590 network operations. 1592 No managed objects in this MIB contain sensitive information. 1594 SNMPv1 by itself is not a secure environment. Even if the network 1595 itself is secure (for example by using IPSec), even then, there is no 1596 control as to who on the secure network is allowed to access and 1597 GET/SET (read/change/create/delete) the objects in this MIB. 1599 It is recommended that the implementers consider the security 1600 features as provided by the SNMPv3 framework. Specifically, the use 1601 of the User-based Security Model RFC 2574 [12] and the View-based 1602 Access Control Model RFC 2575 [15] is recommended. 1604 It is then a customer/user responsibility to ensure that the SNMP 1605 entity giving access to an instance of this MIB, is properly 1606 configured to give access to the objects only to those principals 1607 (users) that have legitimate rights to indeed GET or SET 1608 (change/create/delete) them. 1610 10. Authors' Addresses 1612 Kenneth Rehbehn 1613 Visual Networks 1614 2092 Gaither Road 1615 Rockville, MD, USA 20850 1617 Phone: +1 301 296-2325 1619 EMail: krehbehn@visualnetworks.com 1621 Orly Nicklass 1622 RAD Data Communications, Ltd. 1623 12 Hanechoshet St. 1624 Tel Aviv 69710 1625 Israel 1627 Phone: +972 (3) 6459588 1629 E-mail: orly@radmail.rad.co.il 1631 George Mouradian 1632 AT&T Labs, Room 1G-325 1633 101 Crawfords Corner Road 1634 Holmdel, NJ USA 07733 1636 Phone: +1 908 949 7671 1638 EMail: gvm@att.com 1640 Intellectual Property Rights 1642 The IETF takes no position regarding the validity or scope of any 1643 intellectual property or other rights that might be claimed to 1644 pertain to the implementation or use of the technology described in 1645 this document or the extent to which any license under such rights 1646 might or might not be available; neither does it represent that it 1647 has made any effort to identify any such rights. Information on the 1648 IETF's procedures with respect to rights in standards-track and 1649 standards-related documentation can be found in BCP-11. Copies of 1650 claims of rights made available for publication and any assurances of 1651 licenses to be made available, or the result of an attempt made to 1652 obtain a general license or permission for the use of such 1653 proprietary rights by implementors or users of this specification can 1654 be obtained from the IETF Secretariat. 1656 The IETF invites any interested party to bring to its attention any 1657 copyrights, patents or patent applications, or other proprietary 1658 rights which may cover technology that may be required to practice 1659 this standard. Please address the information to the IETF Executive 1660 Director. 1662 Full Copyright Statement 1664 Copyright (C) The Internet Society (1999). All Rights 1665 Reserved. 1667 This document and translations of it may be copied and 1668 furnished to others, and derivative works that comment on or 1669 otherwise explain it or assist in its implementation may be 1670 prepared, copied, published and distributed, in whole or in 1671 part, without restriction of any kind, provided that the above 1672 copyright notice and this paragraph are included on all such 1673 copies and derivative works. However, this document itself may 1674 not be modified in any way, such as by removing the copyright 1675 notice or references to the Internet Society or other Internet 1676 organizations, except as needed for the purpose of developing 1677 Internet standards in which case the procedures for copyrights 1678 defined in the Internet Standards process must be followed, or 1679 as required to translate it into languages other than English. 1681 The limited permissions granted above are perpetual and will 1682 not be revoked by the Internet Society or its successors or 1683 assigns. 1685 This document and the information contained herein is provided 1686 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1687 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1688 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1689 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1690 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1691 PARTICULAR PURPOSE.