idnits 2.17.1 draft-ietf-frnetmib-atmiwf-02.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 ** Missing expiration date. The document expiration date should appear on the first and last 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 45 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 32 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 302: '...fConnectionIndex MUST utilize the same...' RFC 2119 keyword, line 306: '...ctionIndex value MUST agree on which s...' RFC 2119 keyword, line 365: '...relay and ATM PVC endpoints MUST exist...' RFC 2119 keyword, line 667: '...nIndex value and MUST refer to the sam...' RFC 2119 keyword, line 774: '... descriptor MUST be established i...' (11 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 255 has weird spacing: '...onTable in...' == Line 285 has weird spacing: '...onTable in th...' == Line 616 has weird spacing: '...nnIndex when ...' == Line 870 has weird spacing: '...orIndex when...' == Line 1595 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 18, 1999) is 9078 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 1510, 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' ** Obsolete normative reference: RFC 1604 (ref. '19') (Obsoleted by RFC 2954) -- Possible downref: Non-RFC (?) normative reference: ref. '20' Summary: 21 errors (**), 0 flaws (~~), 9 warnings (==), 4 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 18, 1999 7 draft-ietf-frnetmib-atmiwf-02.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) for monitoring 43 and controlling a service interworking function (IWF) for Permanent 44 Virtual Connections (PVC) between Frame Relay and Asynchronous 45 Transfer Mode (ATM) technologies. 47 Copyright Notice 49 Copyright (C) The Internet Society (1999). All Rights Reserved. 51 Table of Contents 53 1 The SNMP Management Framework ................................ 4 54 2 Overview ..................................................... 6 55 2.1 Frame Relay/ATM Service Interworking Background ............ 6 56 2.2 Structure of the MIB ....................................... 6 57 2.3 Relationship to Other MIBs ................................. 7 58 2.3.1 Frame Relay Service MIB .................................. 8 59 2.3.2 Frame Relay DTE MIB ...................................... 9 60 2.3.3 ATM MIB .................................................. 9 61 2.4 Point to Multipoint Considerations ......................... 9 62 2.5 Theory of Operation ........................................ 10 63 2.5.1 Creation Process ......................................... 10 64 2.5.2 Destruction Process ...................................... 12 65 2.5.3 Failure Conditions ....................................... 13 66 2.5.3.1 Creation and Destruction ............................... 13 67 2.5.3.2 PDU Translation Errors ................................. 14 68 3 Object Definitions ........................................... 15 69 4.1 The FR/ATM PVC Service IWF Connection Group ................ 18 70 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 24 71 4.2 The PDU Translation Error Group ............................ 30 72 5 Frame Relay/ATM PVC Service Interworking TRAP ................ 32 73 6 Conformance Information ...................................... 33 74 6.1 Compliance Statement For Equipment ......................... 33 75 6.2 Compliance Statement For Service (CNM Interface) ........... 35 76 6.3 Units of Conformance ....................................... 37 77 6.3.1 Basic FR/ATM IWF PVC Connection Group .................... 37 78 6.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 37 79 6.3.3 The PDU Translation Error Group .......................... 37 80 6.3.4 Notification Group ....................................... 38 81 7 Acknowledgments .............................................. 39 82 8 References ................................................... 40 83 9 Security Considerations ...................................... 43 84 10 Authors' Addresses .......................................... 43 85 11 Copyright Section ........................................... 45 87 1. The SNMP Management Framework 89 The SNMP Management Framework presently consists of five major 90 components: 92 o An overall architecture, described in RFC 2571 [1]. 94 o Mechanisms for describing and naming objects and events for the 95 purpose of management. The first version of this Structure of 96 Management Information (SMI) is called SMIv1 and described in 97 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 98 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 99 2580 [7]. 101 o Message protocols for transferring management information. The 102 first version of the SNMP message protocol is called SNMPv1 and 103 described in RFC 1157 [8]. A second version of the SNMP message 104 protocol, which is not an Internet standards track protocol, is 105 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 106 The third version of the message protocol is called SNMPv3 and 107 described in RFC 1906 [10], RFC 2572 [11] and 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 RFC 1157 [8]. A second set of protocol operations 112 and associated PDU formats is described in RFC 1905 [13]. 114 o A set of fundamental applications described in RFC 2573 [14] and 115 the view-based access control mechanism described in RFC 2575 116 [15]. 118 A more detailed introduction to the current SNMP Management Framework 119 can be found in RFC 2570 [16]. 121 Managed objects are accessed via a virtual information store, termed 122 the Management Information Base or MIB. Objects in the MIB are 123 defined using the mechanisms defined in the SMI. 125 This memo specifies a MIB module that is compliant to the SMIv2. A 126 MIB conforming to the SMIv1 can be produced through the appropriate 127 translations. The resulting translated MIB must be semantically 128 equivalent, except where objects or events are omitted because no 129 translation is possible (use of Counter64). Some machine readable 130 information in SMIv2 will be converted into textual descriptions in 131 SMIv1 during the translation process. However, this loss of machine 132 readable information is not considered to change the semantics of the 133 MIB. 135 2. Overview 137 This document defines a Management Information Base (MIB) for 138 monitoring and controlling a service interworking function (IWF) for 139 Permanent Virtual Connections (PVC) between Frame Relay and 140 Asynchronous Transfer Mode (ATM) technologies. The agreements on 141 which this MIB is based were reached jointly by the Frame Relay Forum 142 and the ATM Forum and are documented in the Frame Relay Forum 143 Document FRF.8 [17]. 145 2.1. Frame Relay/ATM Service Interworking Background 147 Frame relay to ATM interworking is a function that exchanges Protocol 148 Data Units (PDU) between a Frame Relay service user and an ATM 149 service user. Two types of interworking functions are specified for 150 frame relay and ATM permanent virtual connection (PVC) service users: 151 network interworking [20] and service interworking [17]. 153 Network interworking provides PDU forwarding between frame relay 154 service users inter-connected by an ATM service. Both endpoints are 155 frame relay PVCs. 157 Service interworking provides PDU forwarding so that the ATM service 158 user performs no frame relaying service-specific functions and the 159 frame relay service user performs no ATM service-specific functions. 160 Optionally, the service IWF translates particular higher layer 161 protocols to satisfy the requirements of end-systems. 163 This MIB describes management objects used to provision, monitor, and 164 control a Frame Relay/ATM PVC Service IWF. 166 Consult FRF.8 [17] for more details on the operation of a Frame 167 Relay/ATM PVC Service IWF. 169 2.2. Structure of the MIB 171 The Frame Relay/ATM PVC Service IWF managed objects are organized in 172 two tables: 174 (1) FR/ATM PVC Service IWF cross-connect table 176 (2) Connection description table 178 The IWF cross-connect table contains one or more rows for each 179 inter-worked connection. Each inter-worked connection is uniquely 180 identified by the frAtmIwfConnectionIndex object. In the case of 181 point-to-point, a single row is present. In the case of point-to- 182 multipoint, one row exists for each multipoint destination. Index 183 objects for the ATM port, VPI, VCI, Frame Relay port, and frame relay 184 DLCI distinguish the constituent rows used in a point-to-multipoint 185 case. 187 Each inter-worked connection has attributes governing behavior of the 188 IWF. These attributes describe how the IWF should transform a PDU 189 during the forwarding process and provide rules for: 191 (1) Mapping the ATM CLP bit to frame relay DE bit 193 (2) Mapping the ATM congestion notification bit to frame relay 194 congestion bits 196 (3) Mapping higher protocol encapsulations between ATM and frame 197 relay 199 (4) Performing fragmentation and reassembly 201 (5) Performing ARP translation between ATM and frame relay 203 Typically, most connections share the same attributes. The attributes 204 are represented in this MIB by the connection description table. Each 205 row of the connection description table contains the attribute 206 settings common to one or more inter-worked connections. One example 207 would be full mapping and translation. All cross-connect table 208 entries that require full mapping and translation services set the 209 frAtmIwfConnectionDescriptor object to the index value for the 210 connection description table row that contains objects set to values 211 that provide full mapping and translation services. 213 A notification object provides cross-connect status change alerts. 215 2.3. Relationship to Other MIBs 217 The Frame Relay/ATM PVC Service IWF MIB describes the cross- 218 connections between frame relay and ATM service users. Each PVC 219 endpoint is provisioned and managed with a technology-specific MIB as 220 described below. 222 Each technology-specific MIB has a table of PVC endpoints (indexed by 223 ifIndex and logical link address (DLCI or VPI/VCI). Typically, two 224 endpoints are cross-connected via a technology-specific cross connect 225 table. The introduction of the FR/ATM MIB creates the need to have 226 multiple cross-connect tables. As an example, an ATM PVC endpoint 227 might be connected to either: 229 (1) another ATM PVC endpoint via the atmVcCrossConnectTable, or 231 (2) a frame relay PVC endpoint via the frAtmIwfConnectionTable. 233 This issue is not restricted to the case of frame relay to ATM 234 interworking. An implementation supporting the ATM Forum Circuit 235 Emulation Service (CES) is another example of an ATM VPI/VCI that is 236 not cross-connected via the atmVcCrossConnectTable. 238 Currently, the implicit assumption is made that all PVC endpoints are 239 cross-connected via a single cross-connect table. This restriction is 240 being removed via the specifications of this FR/ATM PVC Service IWF 241 MIB. (for detailed description follow the next three sections). 243 2.3.1. Frame Relay Service MIB 245 Frame relay PVC endpoints are provisioned as rows in the Frame Relay 246 Services MIB [19] endpoint table. 248 The Frame Relay/ATM PVC Service IWF MIB cross-connect table is used 249 to cross-connect the frame relay and ATM PVCs. Consequently, the 250 frame relay PVC connect table does not contain an entry for the 251 inter-worked connection and the object frPVCEndptConnectIdentifier is 252 set to zero for the frame relay PVC endpoint at the initialization 253 state. Upon completion of the IWF cross-connect creation and 254 activation, the system will update this object to point to the cross 255 connect index of the relevant row in the frAtmIwfConnectionTable in 256 the FR/ATM PVC Service IWF MIB. 258 To remove the restriction specified above (section 2.3) one new 259 object has been added for each PVC endpoint row, in the Frame Relay 260 Service MIB. [EDITORS NOTE: This anticipates a future change to the 261 Frame Relay Service MIB] The object (named frPVCIwfKind) serves to 262 identify the cross-connect table associated with the PVC endpoint. 263 The object has an OID value that matches the OID of the IWF MIB 264 cross-connect table that applies (e.g., OID of 265 frAtmIwfConnectionTable). A value of zero (or noSuchObject) indicates 266 cross-connection via the technology-specific cross-connect table. 268 2.3.2. Frame Relay DTE MIB 270 The Frame Relay DTE MIB described in [19] has no relevance to the 271 FR/ATM PVC Service IWF MIB. 273 2.3.3. ATM MIB 275 ATM PVC endpoints are provisioned as rows in the ATM MIB [21] virtual 276 connection link table. 278 The Frame Relay/ATM PVC Service IWF MIB cross-connect table is used 279 to cross-connect the ATM and frame relay PVCs. Consequently, the ATM 280 virtual connection link table does not contain an entry for the 281 inter-worked connection and the object atmVclCrossConnectIdentifier 282 is set to zero for the ATM PVC endpoint at the initialization state. 283 Upon completion of the IWF cross-connect creation and activation, the 284 system will update this object to point to the cross connect index of 285 the relevant row in the frAtmIwfConnectionTable in the FR/ATM PVC 286 Service IWF MIB. 288 To remove the restriction specified above (section 2.3) one new 289 object has been added for each PVC endpoint row, in the ATM MIB. The 290 object (named atmPVCIwfKind) serves to identify the cross-connect 291 table associated with the PVC endpoint. [EDITORS NOTE: This 292 anticipates a future change to the ATM MIB] The object has an OID 293 value that matches the OID of the IWF MIB cross-connect table that 294 applies (e.g., OID of frAtmIwfConnectionTable). A value of zero (or 295 noSuchObject) indicates cross-connection via the technology-specific 296 cross-connect table. 298 2.4. Point to Multipoint Considerations 300 This MIB supports IWF implementations providing point-to-multipoint 301 functionality. All rows of the cross-connect table indexed by the 302 same frAtmIwfConnectionIndex MUST utilize the same 303 frAtmIwfConnectionDescriptor value. 305 A group of cross-connect table entries indexed by the same 306 frAtmIwfConnectionIndex value MUST agree on which service the 307 multipoint operation is offered. Two cases are possible: 309 (1) Many frame relay PVCs cross-connected to one ATM PVC, or 311 (2) One frame relay PVC cross-connected to many ATM PVCs 313 2.5. Theory of Operation 315 2.5.1. Creation Process 317 To successfully create a cross connect entry multiple steps are 318 required. First the endpoints must be established and set to 319 administrative status 'up'. Secondly the cross connect descriptor 320 should be defined, and last, the cross connect entry should be fully 321 defined and set to administrative status 'up'. The following is a 322 descriptive example of step by step creation: 324 Step 1 - Create the frame relay PVC endpoint 326 a) Agent receives management request to create a row in 327 frPVCEndptTable for the Frame Relay side 329 b) System creates the row in frPVCEndptTable with the following 330 defaults: 332 - initialize frPVCEndptConnectIdentifier to zero 334 - initialize frPVCIWFKind to 0.0 336 - initialize the remaining columns as needed for DLCI X 337 on ifIndex Y 339 Step 2 - Create the ATM PVC endpoint 341 a) Agent receives management request to create a row in atmVclTable 342 for the ATM side 344 b) System creates the row in atmVclTable with the following defaults: 346 - initialize atmVclCrossConnectIdentifier to zero 348 - initialize atmVclIWFKind to 0.0 350 - initialize the remaining columns as needed for VPI.VCI 351 Q.R on ifIndex S 353 Step 3 - Create the FR/ATM cross-connect 355 a) Manager requests a new cross-connect index value by reading 356 frAtmIwfConnectionIndexNext from the agent 358 b) Agent receives GET request for frAtmIwfConnectionIndexNext 359 and responds with the next available value K 361 c) Manager requests a new cross-connect row entry using the value 362 K as the index 364 d) Agent receives SET request to create the frAtmIwfConnectionTable 365 row entry (note: the frame relay and ATM PVC endpoints MUST exist 366 and 367 be specified as part of the index fields for the row 'K.S.Q.R.Y.X') 369 e) System creates a row in frAtmIwfConnectionTable for the following 370 indices: 372 - frAtmIwfConnectionIndex of K 374 - frAtmIwfConnAtmPort of S 376 - frAtmIwfConnVpi of Q 378 - frAtmIwfConnVci of R 380 - frAtmIwfConnFrPort of Y 382 - frAtmIwfConnDlci of X 384 f) Manager defines the appropriate connection descriptor or 385 uses one of the available entries in the connection descriptor 386 table for the new connection. 388 g) System establishes the appropriate connection descriptor for 389 the IWF (specified by manager in the SET request of 390 frAtmIwfcOnnectionDescriptor for the relevant row) 392 Step 4 - Point the frame relay PVC endpoint row to the FR/ATM cross- 393 connect row (Note: The system may perform these actions as a side- 394 effect of Step 3) 396 a) System sets frPVCEndptConnectIdentifier to K 397 b) System sets frPVCIWFKind to OID of frAtmIwfConnectionTable to 398 point to the FR/ATM PVC IWF cross-connect table 400 Step 5 - Point the ATM PVC endpoint row to the FR/ATM cross-connect 401 row (Note: The system may perform these actions as a side-effect of 402 Step 3) 404 a) System sets atmVclCrossConnectIdentifier to K 406 b) System sets atmVclIWFKind to frAtmIwfConnectionTable 408 Step 6 - Manager signals activation by issuing a SET for the 409 frAtmIwfConnAdminStatus object using the value of 'up' 411 Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus and 412 executes internal system mechanisms to activate each PVC segment and 413 the IWF cross-connect. The successful activation permits the agent to 414 respond with 'active' when a GET request is received for the 415 following fields: 417 - frAtmIwfConnAtm2FrOperStatus 419 - frAtmIwfConnFr2AtmOperStatus 421 - atmVclOperStatus (Note: there is no comparable FRS MIB object) 423 2.5.2. Destruction Process 425 Destruction operation of a cross connect entry is simple in terms of 426 NMS required operation. However, it carries additional implementation 427 specific side effects of system clean up with respect to the removed 428 cross connect. The following are the steps that should be carried 429 thereafter: 431 Step 1 - Agent receives SET request for frAtmIwfConnRowStatus of the 432 relevant entry to 'destroy' and executes internal system clean up 433 mechanisms 434 Step 2 - System removes the relevant cross connect pointer from the 435 frame relay PVC endpoint 437 a) System sets frPVCEndptConnectIdentifier to 0 439 b) System sets frPVCIWFKind to 0.0 441 Step 3 - System removes the relevant cross connect pointer from the 442 ATM PVC endpoint 444 a) System sets atmVclCrossConnectIdentifier to 0 446 b) System sets atmVclIWFKind to 0.0 448 Step 4 - system can sets atmVclOperStatus to 'down'(Note: there is no 449 comparable FRS MIB object) 451 The FR PVC end point, the ATM PVC endpoint and the 452 frAtmIwfcOnnectionDescriptor entries can continue to exist after the 453 cross connect removal. 455 2.5.3. Failure Conditions 457 2.5.3.1. Creation and Destruction 459 The frame relay service MIB must contain an endpoint connection table 460 entry for the frame relay side of the interworked connection before 461 the interworked connection can be activated in this MIB. The same is 462 true for the ATM endpoint connection table. 464 In addition, the connection descriptor table entry must exist before 465 being referenced by the FR/ATM IWF connection table entry. 467 If required table rows do not exist when the connection table is 468 activated, the request will fail as described in the 469 frAtmIwfConnRowStatus object. 471 Destruction of objects must occur in the reverse order of creation. 473 2.5.3.2. PDU Translation Errors 475 When a PDU translation error occurs (e.g. an unknown protocol ID is 476 encountered), the frAtmIwfTransErrCount object is incremented and 477 information about the failure is stored in objects that report the 478 effected connection, direction of travel, and initial octets in the 479 PDU header. 481 3. Object Definitions 483 Managed objects are accessed via a virtual information store, termed 484 the Management Information Base or MIB. Objects in the MIB are 485 defined using the subset of Abstract Syntax Notation One (ASN.1) 486 defined in the SMI. In particular, each object type is named by an 487 OBJECT IDENTIFIER, an administratively assigned name. The object 488 type together with an object instance serves to uniquely identify a 489 specific instantiation of the object. For human convenience, we 490 often use a textual string, termed the descriptor, to refer to the 491 object type. 493 FR-ATM-PVC-SERVICE-INTERWORKING-MIB DEFINITIONS ::= BEGIN 495 IMPORTS 496 MODULE-IDENTITY, OBJECT-TYPE, 497 NOTIFICATION-TYPE, 498 experimental, Integer32, BITS, Counter32 FROM SNMPv2-SMI 500 TEXTUAL-CONVENTION, RowStatus, 501 TimeStamp FROM SNMPv2-TC 503 MODULE-COMPLIANCE, OBJECT-GROUP, 504 NOTIFICATION-GROUP FROM SNMPv2-CONF 506 AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB 508 InterfaceIndex FROM IF-MIB; 510 frAtmIwfMIB MODULE-IDENTITY 511 LAST-UPDATED "9906180000Z" 512 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working 513 Group" 514 CONTACT-INFO 515 "Kenneth Rehbehn 516 Postal: Visual Networks 517 2092 Gaither Road 518 Rockville, MD USA 20850 519 Tel: +1 301 296 2325 520 Fax: +1 301 296 2302 521 E-mail: krehbehn@visualnetworks.com 523 Orly Nicklass 524 Postal: RAD Data Communications Ltd. 525 12 Hanechoshet St. 527 Tel Aviv 69710 528 Israel 529 Tel: +972 (3) 6459588 530 Fax: +972 (3) 6472675 531 E-mail: orly@radmail.rad.co.il 533 George Mouradian 534 Postal: AT&T Labs, Room 1G-325 535 101 Crawfords Corner Road 536 Holmdel, NJ 07733-3030 537 Tel: +1 908 949 7671 538 Email: gvm@att.com" 540 DESCRIPTION 541 "The MIB module for monitoring and controlling the 542 Frame Relay/ATM PVC Service Interworking 543 Function." 545 -- 546 -- Revision History 547 -- 548 REVISION "9906180000Z" 549 DESCRIPTION 550 "Published as draft-ieft-frnetmib-atmiwf-02 551 o Added new PDU translation error group 552 o Clarified theory of operation and relationship 553 to the ATM and Frame Relay Service MIBs 554 o Update MIB boilerplate to conform to the 555 Operations and Management Area requirements 556 for MIBs" 558 REVISION "9902200000Z" 559 DESCRIPTION 560 "Published as draft-ieft-frnetmib-atmiwf-01 561 o Isolated connection description objects 562 in frAtmIwfConnectionDescriptorTable 563 o Improved text for a number of objects 564 o Added OperStatus objects to Notification 565 for both frame and ATM sides 566 o Set OID values 567 o Clean smicng compile" 569 REVISION "9611250000Z" 570 DESCRIPTION 571 "Published as draft-ieft-frnetmib-atmiwf-00" 572 ::= { experimental 97 } 574 -- 575 -- Object Identifiers 576 -- 577 frAtmIwfMIBObjects OBJECT IDENTIFIER 578 ::= { frAtmIwfMIB 1 } 580 frAtmIwfTraps OBJECT IDENTIFIER 581 ::= { frAtmIwfMIB 2 } 582 frAtmIwfTrapsPrefix OBJECT IDENTIFIER 583 ::= { frAtmIwfTraps 0 } 585 frAtmIwfConformance OBJECT IDENTIFIER 586 ::= { frAtmIwfMIB 3 } 587 frAtmIwfGroups OBJECT IDENTIFIER 588 ::= { frAtmIwfConformance 1 } 589 frAtmIwfCompliances OBJECT IDENTIFIER 590 ::= { frAtmIwfConformance 2 } 592 -- 593 -- Textual Conventions 594 -- 596 Dlci ::= TEXTUAL-CONVENTION 597 STATUS current 598 DESCRIPTION 599 "This data type is a DLCI for a PVC segment end-point." 600 SYNTAX Integer32 602 -- 603 -- The FR/ATM PVC Service IWF Group 604 -- 605 -- The Frame Relay/ATM PVC Service Interworking Function 606 -- Connection Table contains all connections utilizing 607 -- the interworking function. 608 -- 610 frAtmIwfConnIndexNext OBJECT-TYPE 611 SYNTAX Integer32 (0..2147483647) 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "This object contains an appropriate value to be 616 used for frAtmIwfConnIndex when creating entries 617 in the frAtmIwfConnectionTable. The value 0 618 indicates that no unassigned entries are 619 available. To obtain the frAtmIwfConnIndexNext 620 value for a new entry, the manager issues a 621 management protocol retrieval operation to obtain 622 the current value of this object. After each 623 retrieval, the agent should modify the value to 624 the next unassigned index." 625 ::= { frAtmIwfMIBObjects 1 } 627 frAtmIwfConnectionTable OBJECT-TYPE 628 SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "A table in which each row represents a Frame 633 Relay/ATM interworking connection." 634 ::= { frAtmIwfMIBObjects 2 } 636 frAtmIwfConnectionEntry OBJECT-TYPE 637 SYNTAX FrAtmIwfConnectionEntry 638 MAX-ACCESS not-accessible 639 STATUS current 640 DESCRIPTION 641 "The FrAtmIwfConnectionEntry provides an entry for 642 an interworking connection between a Frame Relay 643 PVC and one or more ATM PVCs, or an ATM PVC and 644 one or more Frame Relay PVCs. A single Frame 645 Relay PVC connected to a single ATM PVC is 646 referred to as a `point-to-point' connection and 647 is represented by a single row in the FR/ATM IWF 648 Connection Table. The case of a single Frame 649 Relay PVC connected to multiple ATM PVCs (or 650 single ATM PVC connected to multiple Frame Relay 651 PVCs) is referred to as a `point-to-multipoint' 652 connection and is represented by multiple rows in 653 the FR/ATM IWF Connection Table. 655 The object frAtmIwfConnIndex uniquely identifies 656 each point-to-point or point-to-multipoint 657 connection. The manager obtains the 658 frAtmIwfConnIndex value by reading the 659 frAtmIwfConnIndexNext object. 661 After a frAtmIwfConnIndex is assigned for the 662 connection, the manager creates one or more rows 663 in the Cross Connect Table; one for each cross- 664 connection between the frame relay PVC and an ATM 665 PVC. In the case of `point-to-multipoint' 666 connections, all rows are indexed by the same 667 frAtmIwfConnIndex value and MUST refer to the same 668 frame relay PVC or ATM PVC respectively. An entry 669 can be created only when at least one pair of 670 Frame Relay and ATM PVCs exist. 672 A row can be established by one-step set-request 673 with all required parameter values and 674 frAtmIwfConnRowStatus set to createAndGo(4). The 675 Agent should perform all error checking as needed. 676 A pair of cross-connected PVCs, as identified by a 677 particular value of the indexes, is released by 678 setting frAtmIwfConnRowStatus to destroy(6). The 679 Agent may release all associated resources. The 680 manager may remove the related PVCs thereafter. 681 Indexes are persistent across reboots of the 682 system." 683 INDEX { frAtmIwfConnIndex, 684 frAtmIwfConnAtmPort, 685 frAtmIwfConnVpi, 686 frAtmIwfConnVci, 687 frAtmIwfConnFrPort, 688 frAtmIwfConnDlci 689 } 690 ::= { frAtmIwfConnectionTable 1 } 692 FrAtmIwfConnectionEntry ::= 693 SEQUENCE { 694 frAtmIwfConnIndex Integer32, 695 frAtmIwfConnAtmPort InterfaceIndex, 696 frAtmIwfConnVpi AtmVpIdentifier, 697 frAtmIwfConnVci AtmVcIdentifier, 698 frAtmIwfConnFrPort InterfaceIndex, 699 frAtmIwfConnDlci Dlci, 700 frAtmIwfConnRowStatus RowStatus, 701 frAtmIwfConnAdminStatus INTEGER, 702 frAtmIwfConnAtm2FrOperStatus INTEGER, 703 frAtmIwfConnAtm2FrLastChange TimeStamp, 704 frAtmIwfConnFr2AtmOperStatus INTEGER, 705 frAtmIwfConnFr2AtmLastChange TimeStamp, 706 frAtmIwfConnectionDescriptor Integer32 707 } 709 frAtmIwfConnIndex OBJECT-TYPE 710 SYNTAX Integer32 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "A unique index to identify this interworking 715 connection." 716 ::= { frAtmIwfConnectionEntry 1 } 718 frAtmIwfConnAtmPort OBJECT-TYPE 719 SYNTAX InterfaceIndex 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "The index in the ifTable that identifies the ATM 724 port for this interworking connection." 725 ::= { frAtmIwfConnectionEntry 2 } 727 frAtmIwfConnVpi OBJECT-TYPE 728 SYNTAX AtmVpIdentifier 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "The VPI of the ATM PVC end point for this 733 interworking connection." 734 ::= { frAtmIwfConnectionEntry 3 } 736 frAtmIwfConnVci OBJECT-TYPE 737 SYNTAX AtmVcIdentifier 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "The VCI of the ATM PVC end point for this 742 interworking 743 connection." 744 ::= { frAtmIwfConnectionEntry 4 } 746 frAtmIwfConnFrPort OBJECT-TYPE 747 SYNTAX InterfaceIndex 748 MAX-ACCESS not-accessible 749 STATUS current 750 DESCRIPTION 751 "The index in the ifTable that identifies the 752 Frame Relay port for this interworking 753 connection." 754 ::= { frAtmIwfConnectionEntry 5 } 756 frAtmIwfConnDlci OBJECT-TYPE 757 SYNTAX Dlci 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "The DLCI that identifies the Frame Relay PVC end 762 point for this interworking connection." 763 ::= { frAtmIwfConnectionEntry 6 } 765 frAtmIwfConnRowStatus OBJECT-TYPE 766 SYNTAX RowStatus 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "The table row may be created with 'createAndWait' 771 or 'createAndGo'. 773 To activate a connection entry, a valid connection 774 descriptor MUST be established in the 775 frAtmIwfConnectionDescriptor object and the 776 AdminStatus of the corresponding endpoints MUST be 777 'up' & 'active'. 779 This object is set to 'destroy' to delete the 780 table row. To deactivate a connection entry, the 781 AdminStatus of the corresponding endpoints MUST be 782 'down' & operation MUST fail (error code 783 'inconsistentValue')." 784 ::= { frAtmIwfConnectionEntry 7 } 786 frAtmIwfConnAdminStatus OBJECT-TYPE 787 SYNTAX INTEGER { up(1), down(2) } 788 MAX-ACCESS read-create 789 STATUS current 790 DESCRIPTION 791 "The desired operational state for this 792 interworking connection." 793 ::= { frAtmIwfConnectionEntry 8 } 795 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE 796 SYNTAX INTEGER { up(1), down(2) } 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "The current operational state of this 801 interworking connection in the direction from ATM 802 to FR end." 803 ::= { frAtmIwfConnectionEntry 9 } 805 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE 806 SYNTAX TimeStamp 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The value of sysUpTime at the time this 811 interworking connection entered its current 812 operational state in the ATM to FR direction. If 813 the current state was entered prior to the last 814 re-initialization of the local network management 815 subsystem, then this object contains a zero 816 value." 817 ::= { frAtmIwfConnectionEntry 10 } 819 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE 820 SYNTAX INTEGER { up(1), down(2) } 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "The current operational state of this 825 interworking connection in the direction from FR 826 to ATM end." 828 ::= { frAtmIwfConnectionEntry 11 } 830 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE 831 SYNTAX TimeStamp 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "The value of sysUpTime at the time this 836 interworking connection entered its current 837 operational state in the FR to ATM direction. If 838 the current state was entered prior to the last 839 re-initialization of the local network management 840 subsystem, then this object contains a zero 841 value." 842 ::= { frAtmIwfConnectionEntry 12 } 844 frAtmIwfConnectionDescriptor OBJECT-TYPE 845 SYNTAX Integer32 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "The value represents a pointer to the relevant 850 descriptor in the IWF descriptor table. An 851 attempt to set this value to an inactive or non- 852 existant row in the Connection Descriptor Table 853 MUST fail (error code 'inconsistentValue')." 854 ::= { frAtmIwfConnectionEntry 13 } 856 -- 857 -- The FR/ATM PVC Service IWF Connection Descriptor Group 858 -- 859 -- The Frame Relay/ATM PVC Service Interworking Function 860 -- Connection Descriptor table. A descriptor provides the 861 -- attributes for a type of interworked connection. 862 -- 864 frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE 865 SYNTAX Integer32 (0..2147483647) 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "This object contains an appropriate value to be 870 used for frAtmIwfConnectionDescriptorIndex when 871 creating entries in the 872 frAtmIwfConnectionDescriptorTable. The value 0 873 indicates that no unassigned entries are 874 available. To obtain the 875 frAtmIwfConnectionDescriptorIndexNext value for a 876 new entry, the manager issues a management 877 protocol retrieval operation to obtain the current 878 value of this object. After each retrieval, the 879 agent should modify the value to the next 880 unassigned index." 881 ::= { frAtmIwfMIBObjects 3 } 883 frAtmIwfConnectionDescriptorTable OBJECT-TYPE 884 SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry 885 MAX-ACCESS not-accessible 886 STATUS current 887 DESCRIPTION 888 "A table in which each row represents a descriptor 889 for one type of Frame Relay/ATM interworking 890 connection. A descriptor may be assigned to zero 891 or more FR/ATM PVC service IWF connections." 892 ::= { frAtmIwfMIBObjects 4 } 894 frAtmIwfConnectionDescriptorEntry OBJECT-TYPE 895 SYNTAX FrAtmIwfConnectionDescriptorEntry 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "An entry for a descriptor in an interworking 900 connection between a Frame Relay PVC and an ATM 901 PVC." 902 INDEX { frAtmIwfConnectionDescriptorIndex } 903 ::= { frAtmIwfConnectionDescriptorTable 1 } 905 FrAtmIwfConnectionDescriptorEntry ::= 906 SEQUENCE { 907 frAtmIwfConnectionDescriptorIndex Integer32, 908 frAtmIwfConnDescriptorRowStatus RowStatus, 909 frAtmIwfConnDeToClpMappingMode INTEGER, 910 frAtmIwfConnClpToDeMappingMode INTEGER, 911 frAtmIwfConnCongestionMappingMode INTEGER, 912 frAtmIwfConnEncapsulationMappingMode INTEGER, 913 frAtmIwfConnEncapsulationMappings BITS, 914 frAtmIwfConnFragAndReassEnabled INTEGER, 915 frAtmIwfConnArpTranslationEnabled INTEGER 916 } 918 frAtmIwfConnectionDescriptorIndex OBJECT-TYPE 919 SYNTAX Integer32 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "A unique value to identify a descriptor in the 924 table " 925 ::= { frAtmIwfConnectionDescriptorEntry 1 } 927 frAtmIwfConnDescriptorRowStatus OBJECT-TYPE 928 SYNTAX RowStatus 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION 932 "The status of this table row. This object is 933 used to create or delete an entry in the 934 descriptor table. 936 Creation of the row requires a row index (see 937 frAtmIwfConnectionDescriptorIndexNext). If not 938 explicitly set or in existence, all other columns 939 of the row will be created and initialized to the 940 default value. During creation, this object MAY 941 be set to The object MUST contain the value 942 'active' before any connection table entry 943 references the row. 945 To destroy a row in this table, this object is set 946 to the 'destroy' action. Row destruction MUST 947 fail (error code 'inconsistentValue') if any 948 connection references the row." 949 ::= { frAtmIwfConnectionDescriptorEntry 2 } 951 frAtmIwfConnDeToClpMappingMode OBJECT-TYPE 952 SYNTAX INTEGER { 953 mode1(1), 954 mode2Const0(2), 955 mode2Const1(3) 956 } 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "This object describes which mode of translation 961 is in use for loss priority mapping in the Frame 962 Relay to ATM direction. 964 mode1 = the DE field in the Q.922 core frame 965 shall be mapped to the ATM CLP filed 966 of every cell generated by the 967 segmentation process of the AAL5 968 PDU containing the information of 969 that frame. 971 mode2Contst0 = the ATM CLP filed of every cell 972 generated by the segmentation process 973 of the AAL5 PDU containing the 974 information of that frame shall be 975 set to constant 0. 977 mode2Contst1 = the ATM CLP filed of every cell 978 generated by the segmentation process 979 of the AAL5 PDU containing the 980 information of that frame shall be set 981 to constant 1." 982 REFERENCE 983 "FRF.8 [17], Section 4.2.1" 984 DEFVAL { mode1 } 985 ::= { frAtmIwfConnectionDescriptorEntry 3 } 987 frAtmIwfConnClpToDeMappingMode OBJECT-TYPE 988 SYNTAX INTEGER { 989 mode1(1), 990 mode2Const0(2), 991 mode2Const1(3) 992 } 993 MAX-ACCESS read-create 994 STATUS current 995 DESCRIPTION 996 "This object describes which mode of translation 997 is in use for loss priority mapping in the ATM to 998 Frame Relay direction. 1000 mode1 = if one or more cells in a frame has its CLP 1001 field set, the DE field of the Q.922 core 1002 frame should be set. 1004 mode2Const0 = the DE field of the Q.922 core frame should 1005 be set to constant 0. 1007 mode2Const1 = the DE field of the Q.922 core frame should 1008 be set to constant 1." 1010 REFERENCE 1011 "FRF.8 [17], Section 4.2.2" 1012 DEFVAL { mode1 } 1013 ::= { frAtmIwfConnectionDescriptorEntry 4 } 1015 frAtmIwfConnCongestionMappingMode OBJECT-TYPE 1016 SYNTAX INTEGER { 1017 mode1(1), 1018 mode2(2) 1019 } 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "This object describes which mode of translation 1024 is in use for forward congestion indication 1025 mapping in the Frame Relay to ATM direction. 1027 mode1 = The FECN field in the Q.922 core frame shall be 1028 mapped to the ATM EFCI field of every cell 1029 generated by the segmentation process of the 1030 AAL5 PDU containing the information of that 1031 frame. 1033 mode2 = The FECN field in the Q.922 core frame shall not 1034 be mapped to the ATM EFCI field of cells 1035 generated by the segmentation process of the AAL5 1036 PDU containing the information of that frame. 1037 The EFCI field is always set to 'congestion not 1038 experienced'. 1040 In both of the modes above, if there is congestion 1041 in the forward direction in the ATM layer within 1042 the IWF, then the IWF can set the EFCI field to 1043 'congestion experienced'." 1044 REFERENCE 1045 "FRF.8 [17], Section 4.3.1.1" 1046 DEFVAL { mode1 } 1047 ::= { frAtmIwfConnectionDescriptorEntry 5 } 1049 frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE 1050 SYNTAX INTEGER { 1051 transparentMode(1), 1052 translationMode(2) 1053 } 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This object indicates whether the mapping of 1058 upper layer protocol encapsulation is enabled on 1059 this interworking connection. 1061 transparentMode = Forward the encapsulations unaltered. 1063 translationMode = Perform mapping between the two 1064 encapsulations due to the 1065 incompatibilities of the two methods." 1067 REFERENCE 1068 "FRF.8 [17], Section 5.3" 1069 DEFVAL { transparentMode } 1070 ::= { frAtmIwfConnectionDescriptorEntry 6 } 1072 frAtmIwfConnEncapsulationMappings OBJECT-TYPE 1073 SYNTAX BITS { 1074 none (0), -- Transparent mode operation 1075 bridgedPdus(1), -- PID: 0x00-01,-07,-02 or -08 1076 bridged802dot6(2), -- PID: 0x00-0B 1077 bPdus(3), -- PID: 0x00-0E or -0F 1078 routedIp(4), -- NLPID: OxCC 1079 routedOsi(5), -- NLPID: Ox81, 0x82 or 0x83 1080 otherRouted(6), -- 1081 x25Iso8202(7), -- 1082 q933q2931(8) } 1083 MAX-ACCESS read-create 1084 STATUS current 1085 DESCRIPTION 1086 "If upper layer protocol encapsulation mapping is 1087 enabled on this interworking connection, then this 1088 attribute enumerates which of the encapsulation 1089 mappings are supported." 1090 REFERENCE 1091 "FRF.8 [17], Section 5.3.1" 1092 DEFVAL { { none } } 1093 ::= { frAtmIwfConnectionDescriptorEntry 7 } 1095 frAtmIwfConnFragAndReassEnabled OBJECT-TYPE 1096 SYNTAX INTEGER { enabled(1), disabled(2)} 1097 MAX-ACCESS read-create 1098 STATUS current 1099 DESCRIPTION 1100 "The attribute indicates whether fragmentation and 1101 reassembly is enabled for this connection." 1102 REFERENCE 1103 "FRF.8 [17], Section 5.3.1.4" 1104 DEFVAL { disabled } 1105 ::= { frAtmIwfConnectionDescriptorEntry 8 } 1107 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE 1108 SYNTAX INTEGER { enabled(1), disabled(2)} 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION 1112 "The attribute indicates whether ARP translation 1113 is enabled for this connection." 1114 REFERENCE 1115 "FRF.8 [17], Section 5.4" 1116 DEFVAL { disabled } 1117 ::= { frAtmIwfConnectionDescriptorEntry 9 } 1119 -- 1120 -- The PDU Translation Error Group 1121 -- 1122 -- This set of scalars tracks PDU translation errors while in 1123 -- translation mode. When a PDU is discarded due when the 1124 -- protocol is not supported by the IWF, all five objects in 1125 -- this group are updated simultaneously. A read of the five 1126 -- objects in single GET request MUST return information about 1127 -- the last invalid translation incident. A manager MUST NOT 1128 -- access different objects of this group in different GET 1129 -- requests when attempting to report the last translation 1130 -- error. 1131 -- 1133 frAtmIwfTransErrCount OBJECT-TYPE 1134 SYNTAX Counter32 1135 UNITS "Frames" 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "A count of translation error incidents. This 1140 count MUST be incremented when an invalid PDU is 1141 discard." 1142 ::= { frAtmIwfMIBObjects 5 } 1144 frAtmIwfTransErrConnIndex OBJECT-TYPE 1145 SYNTAX Integer32 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "The connection receiving the last invalid PDU. 1150 If no error has occurred, then the value zero is 1151 returned." 1152 ::= { frAtmIwfMIBObjects 6 } 1154 frAtmIwfTransErrDirection OBJECT-TYPE 1155 SYNTAX INTEGER { noTransErr(0), fr2Atm(1), atm2Fr(2) } 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "The direction of PDU travel. If no error has 1160 occurred, then noTransErr MUST be returned." 1161 ::= { frAtmIwfMIBObjects 7 } 1163 frAtmIwfTransErrTime OBJECT-TYPE 1164 SYNTAX TimeStamp 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "The value of sysUpTime at the time this 1169 interworking connection processed an invalid PDU. 1170 If no error has occurred, then the value zero is 1171 returned." 1172 ::= { frAtmIwfMIBObjects 8 } 1174 frAtmIwfTransErrDump OBJECT-TYPE 1175 SYNTAX OCTET STRING (SIZE(8)) 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "A dump of the first 8 octets of the last 1180 unknown/invalid PDU header. The dump begins with 1181 the first octet after the frame relay or ATM 1182 header. Inspection of this dump will reveal the 1183 SNAP encapsulation or NLPID that was not 1184 translated. If no error has occurred, then an 1185 octet string of zeroes is returned. If the 1186 payload is shorter than 8 octets, then the string 1187 is padded with zeroes." 1188 ::= { frAtmIwfMIBObjects 9 } 1190 -- 1191 -- Frame Relay/ATM PVC Service Interworking TRAP 1192 -- 1194 frAtmIwfConnStatusChange NOTIFICATION-TYPE 1195 OBJECTS { frAtmIwfConnAdminStatus, 1196 frAtmIwfConnAtm2FrOperStatus, 1197 frAtmIwfConnFr2AtmOperStatus 1198 } 1199 STATUS current 1200 DESCRIPTION 1201 "An indication that the status of this 1202 interworking connection has changed." 1203 ::= { frAtmIwfTrapsPrefix 1 } 1205 -- 1206 -- Conformance Information 1207 -- 1209 -- 1210 -- Compliance Statement For Equipment 1211 -- 1213 frAtmIwfEquipmentCompliance MODULE-COMPLIANCE 1214 STATUS current 1215 DESCRIPTION 1216 "The compliance statement for equipment that 1217 implements the FR/ATM Interworking MIB." 1219 MODULE -- this module 1220 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1221 frAtmIwfConnectionDescriptorGroup, 1222 frAtmIwfTransErrGroup, 1223 frAtmIwfNotificationsGroup } 1225 OBJECT frAtmIwfConnDeToClpMappingMode 1226 SYNTAX INTEGER { mode1(1) } 1227 DESCRIPTION 1228 "Only support for Mode 1 is required." 1230 OBJECT frAtmIwfConnClpToDeMappingMode 1231 SYNTAX INTEGER { mode1(1) } 1232 DESCRIPTION 1233 "Only support for Mode 1 is required." 1235 OBJECT frAtmIwfConnCongestionMappingMode 1236 SYNTAX INTEGER { mode1(1) } 1237 DESCRIPTION 1238 "Only support for Mode 1 is required." 1240 OBJECT frAtmIwfConnEncapsulationMappingMode 1241 SYNTAX INTEGER { transparentMode(1) } 1242 DESCRIPTION 1243 "Support for Translation Mode is not required." 1245 OBJECT frAtmIwfConnEncapsulationMappings 1246 SYNTAX BITS { none(0) } 1247 DESCRIPTION 1248 "The IWF may provide one, some or none of the 1249 encapsulation translations defined in section 1250 5.3.1 of FRF.8 [17]." 1252 OBJECT frAtmIwfConnFragAndReassEnabled 1253 SYNTAX INTEGER { disabled(2) } 1254 DESCRIPTION 1255 "Only support for Mode 1 is required." 1257 OBJECT frAtmIwfConnArpTranslationEnabled 1258 SYNTAX INTEGER { disabled(2) } 1259 DESCRIPTION 1260 "Support for ARP Translation is not required." 1262 ::= { frAtmIwfCompliances 1 } 1264 -- 1265 -- Compliance Statement For Service (CNM Interface) 1266 -- 1268 frAtmIwfServiceCompliance MODULE-COMPLIANCE 1269 STATUS current 1270 DESCRIPTION 1271 "The compliance statement for a CNM interface that 1272 implements the FR/ATM Interworking MIB." 1274 MODULE -- this module 1275 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1276 frAtmIwfConnectionDescriptorGroup, 1277 frAtmIwfTransErrGroup, 1278 frAtmIwfNotificationsGroup } 1280 -- 1281 -- Exceptions for each object type implemented for a 1282 -- CNM view of the FR/ATM Interworking MIB 1283 -- 1284 OBJECT frAtmIwfConnAdminStatus 1285 MIN-ACCESS read-only 1286 DESCRIPTION 1287 "Write access is not required." 1289 OBJECT frAtmIwfConnDeToClpMappingMode 1290 SYNTAX INTEGER { mode1(1) } 1291 MIN-ACCESS read-only 1292 DESCRIPTION 1293 "Support for Mode 1 is required. Other modes are 1294 optional. Write access is not required." 1296 OBJECT frAtmIwfConnClpToDeMappingMode 1297 SYNTAX INTEGER { mode1(1) } 1298 MIN-ACCESS read-only 1299 DESCRIPTION 1300 "Support for Mode 1 is required. Other modes are 1301 optional. Write access is not required." 1303 OBJECT frAtmIwfConnCongestionMappingMode 1304 SYNTAX INTEGER { mode1(1) } 1305 MIN-ACCESS read-only 1306 DESCRIPTION 1307 "Support for Mode 1 is required. Other modes are 1308 optional. Write access is not required." 1310 OBJECT frAtmIwfConnEncapsulationMappingMode 1311 SYNTAX INTEGER { transparentMode(1) } 1312 MIN-ACCESS read-only 1313 DESCRIPTION 1314 "Support for Transparent Mode is required. 1315 Translation Mode is optional. Write access is not 1316 required." 1318 OBJECT frAtmIwfConnEncapsulationMappings 1319 SYNTAX BITS { none(0) } 1320 MIN-ACCESS read-only 1321 DESCRIPTION 1322 "The IWF may provide one, some or none of the 1323 encapsulation translations defined in section 1324 5.3.1 of FRF.8 [17]. Write access is not 1325 required." 1327 OBJECT frAtmIwfConnFragAndReassEnabled 1328 SYNTAX INTEGER { disabled(2) } 1329 MIN-ACCESS read-only 1330 DESCRIPTION 1331 "Support for Fragmentation and Reassembly is not 1332 required. Write access is not required." 1334 OBJECT frAtmIwfConnArpTranslationEnabled 1335 SYNTAX INTEGER { disabled(2) } 1336 MIN-ACCESS read-only 1337 DESCRIPTION 1338 "Support for ARP Translation is not required. 1339 Write access is not required." 1341 OBJECT frAtmIwfConnRowStatus 1342 MIN-ACCESS read-only 1343 DESCRIPTION 1344 "Write access is not required." 1346 ::= { frAtmIwfCompliances 2 } 1348 -- 1349 -- Units of Conformance 1350 -- 1352 -- 1353 -- Basic FR/ATM IWF PVC Connection Group 1354 -- 1355 frAtmIwfBasicGroup OBJECT-GROUP 1356 OBJECTS { frAtmIwfConnIndexNext, 1357 frAtmIwfConnAdminStatus, 1358 frAtmIwfConnAtm2FrOperStatus, 1359 frAtmIwfConnAtm2FrLastChange, 1360 frAtmIwfConnFr2AtmOperStatus, 1361 frAtmIwfConnFr2AtmLastChange, 1362 frAtmIwfConnectionDescriptor, 1363 frAtmIwfConnRowStatus } 1364 STATUS current 1365 DESCRIPTION 1366 "The collection of basic objects for configuration 1367 and control of FR/ATM interworking connections." 1368 ::= { frAtmIwfGroups 1 } 1370 -- 1371 -- FR/ATM IWF PVC Connection Descriptor Group 1372 -- 1374 frAtmIwfConnectionDescriptorGroup OBJECT-GROUP 1375 OBJECTS { 1376 frAtmIwfConnectionDescriptorIndexNext, 1377 frAtmIwfConnDeToClpMappingMode, 1378 frAtmIwfConnClpToDeMappingMode, 1379 frAtmIwfConnCongestionMappingMode, 1380 frAtmIwfConnEncapsulationMappingMode, 1381 frAtmIwfConnEncapsulationMappings, 1382 frAtmIwfConnFragAndReassEnabled, 1383 frAtmIwfConnArpTranslationEnabled, 1384 frAtmIwfConnDescriptorRowStatus 1385 } 1386 STATUS current 1387 DESCRIPTION 1388 "The collection of basic objects for specification 1389 of FR/ATM interworking connection descriptors." 1390 ::= { frAtmIwfGroups 2 } 1392 -- 1393 -- The PDU Translation Error Group 1394 -- 1396 frAtmIwfTransErrGroup OBJECT-GROUP 1397 OBJECTS { 1398 frAtmIwfTransErrCount, 1399 frAtmIwfTransErrConnIndex, 1400 frAtmIwfTransErrDirection, 1401 frAtmIwfTransErrTime, 1402 frAtmIwfTransErrDump 1403 } 1404 STATUS current 1405 DESCRIPTION 1406 "The collection of objects for reporting on the 1407 last PDU translation error." 1408 ::= { frAtmIwfGroups 3 } 1410 -- 1411 -- Notification Group 1412 -- 1414 frAtmIwfNotificationsGroup NOTIFICATION-GROUP 1415 NOTIFICATIONS { frAtmIwfConnStatusChange } 1416 STATUS current 1417 DESCRIPTION 1418 "The notification for FR/ATM interworking status 1419 change." 1420 ::= { frAtmIwfGroups 4 } 1421 END 1423 7. Acknowledgments 1425 This document was produced by the Frame Relay Service MIB Working 1426 Group. 1428 8. References 1430 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1431 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1432 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1433 1999 1435 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1436 Management Information for TCP/IP-based Internets", RFC 1155, STD 1437 16, Performance Systems International, Hughes LAN Systems, May 1990 1439 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1440 STD 16, Performance Systems International, Hughes LAN Systems, 1441 March 1991 1443 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1444 RFC 1215, Performance Systems International, March 1991 1446 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1447 and S. Waldbusser, "Structure of Management Information Version 2 1448 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1449 Braunschweig, SNMP Research, First Virtual Holdings, International 1450 Network Services, April 1999 1452 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1453 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1454 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1455 Virtual Holdings, International Network Services, April 1999 1457 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1458 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1459 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1460 First Virtual Holdings, International Network Services, April 1999 1462 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1463 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1464 Systems International, Performance Systems International, MIT 1465 Laboratory for Computer Science, May 1990. 1467 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1468 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1469 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1470 International Network Services, January 1996. 1472 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1473 Mappings for Version 2 of the Simple Network Management Protocol 1474 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1475 Dover Beach Consulting, Inc., International Network Services, 1476 January 1996. 1478 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1479 Processing and Dispatching for the Simple Network Management 1480 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1481 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1483 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1484 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1485 2574, IBM T. J. Watson Research, April 1999 1487 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1488 Operations for Version 2 of the Simple Network Management Protocol 1489 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1490 Dover Beach Consulting, Inc., International Network Services, 1491 January 1996. 1493 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1494 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1495 Systems, April 1999 1497 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1498 Control Model (VACM) for the Simple Network Management Protocol 1499 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1500 Cisco Systems, Inc., April 1999 1502 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1503 Version 3 of the Internet-standard Network Management Framework", 1504 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, 1505 Inc., Ericsson, Cisco Systems, April 1999 1507 [17] Frame Relay/ATM PVC Service Interworking Implementation Agreement, 1508 Frame Relay Forum, Document Number FRF.8, April 14, 1995. 1510 [18] Network Working Group, Noto, Spiegel, and Tesink, "Definitions of 1511 Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 1512 2514, February 1999. 1514 [19] Network Working Group, T. Brown, "Definitions of Managed Objects 1515 for Frame Relay Service", RFC 1604, March 1994. [Editors Note: 1516 Replace with new RFC when ready] 1518 [20] Frame Relay/ATM PVC Network Interworking Implementation Agreement, 1519 Frame Relay Forum, Document Number FRF.5, December 20, 1994. 1521 [21] Network Working Group, K. Tesink, "Definitions of Managed Objects 1522 for ATM Management", RFC 2515, February 1999. 1524 9. Security Considerations 1526 There are a number of management objects defined in this MIB that 1527 have a MAX-ACCESS clause of read-write and/or read-create. Such 1528 objects may be considered sensitive or vulnerable in some network 1529 environments. The support for SET operations in a non-secure 1530 environment without proper protection can have a negative effect on 1531 network operations. 1533 No managed objects in this MIB contain sensitive information. 1535 SNMPv1 by itself is not a secure environment. Even if the network 1536 itself is secure (for example by using IPSec), even then, there is no 1537 control as to who on the secure network is allowed to access and 1538 GET/SET (read/change/create/delete) the objects in this MIB. 1540 It is recommended that the implementers consider the security 1541 features as provided by the SNMPv3 framework. Specifically, the use 1542 of the User-based Security Model RFC 2574 [12] and the View-based 1543 Access Control Model RFC 2575 [15] is recommended. 1545 It is then a customer/user responsibility to ensure that the SNMP 1546 entity giving access to an instance of this MIB, is properly 1547 configured to give access to the objects only to those principals 1548 (users) that have legitimate rights to indeed GET or SET 1549 (change/create/delete) them. 1551 10. Authors' Addresses 1553 Kenneth Rehbehn 1554 Visual Networks 1555 2092 Gaither Road 1556 Rockville, MD, USA 20850 1558 Phone: +1 301 296-2325 1560 EMail: krehbehn@visualnetworks.com 1562 Orly Nicklass 1563 RAD Data Communications, Ltd. 1564 12 Hanechoshet St. 1565 Tel Aviv 69710 1566 Israel 1568 Phone: +972 (3) 6459588 1570 E-mail: orly@radmail.rad.co.il 1572 George Mouradian 1573 AT&T Labs, Room 1G-325 1574 101 Crawfords Corner Road 1575 Holmdel, NJ USA 07733 1577 Phone: +1 908 949 7671 1579 EMail: gvm@att.com 1581 11. Copyright Section 1583 Copyright (C) The Internet Society (1999). All Rights 1584 Reserved. 1586 This document and translations of it may be copied and 1587 furnished to others, and derivative works that comment on or 1588 otherwise explain it or assist in its implementation may be 1589 prepared, copied, published and distributed, in whole or in 1590 part, without restriction of any kind, provided that the above 1591 copyright notice and this paragraph are included on all such 1592 copies and derivative works. However, this document itself may 1593 not be modified in any way, such as by removing the copyright 1594 notice or references to the Internet Society or other Internet 1595 organizations, except as needed for the purpose of developing 1596 Internet standards in which case the procedures for copyrights 1597 defined in the Internet Standards process must be followed, or 1598 as required to translate it into languages other than English. 1600 The limited permissions granted above are perpetual and will 1601 not be revoked by the Internet Society or its successors or 1602 assigns. 1604 This document and the information contained herein is provided 1605 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1606 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1607 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1608 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1609 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1610 PARTICULAR PURPOSE.