idnits 2.17.1 draft-ietf-atommib-test-04.txt: ** The Abstract section seems to be numbered 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? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8. Security Considerations' ) ** 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 an Authors' Addresses Section. ** The abstract seems to contain references ([20], [15], [2], [21], [3], [16], [17], [22], [4], [18], [5], [19], [6], [7], [8], [9], [10], [11], [12], [13], [14], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (September 1, 1998) is 9363 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '16' on line 1222 looks like a reference -- Missing reference section? '1' on line 1131 looks like a reference -- Missing reference section? '2' on line 1136 looks like a reference -- Missing reference section? '3' on line 1141 looks like a reference -- Missing reference section? '4' on line 1145 looks like a reference -- Missing reference section? '5' on line 1149 looks like a reference -- Missing reference section? '6' on line 1156 looks like a reference -- Missing reference section? '7' on line 1163 looks like a reference -- Missing reference section? '8' on line 1170 looks like a reference -- Missing reference section? '9' on line 1179 looks like a reference -- Missing reference section? '10' on line 1185 looks like a reference -- Missing reference section? '11' on line 1192 looks like a reference -- Missing reference section? '12' on line 1198 looks like a reference -- Missing reference section? '13' on line 1203 looks like a reference -- Missing reference section? '14' on line 1210 looks like a reference -- Missing reference section? '15' on line 1214 looks like a reference -- Missing reference section? '22' on line 1254 looks like a reference -- Missing reference section? '17' on line 1225 looks like a reference -- Missing reference section? '18' on line 1230 looks like a reference -- Missing reference section? '20' on line 1237 looks like a reference -- Missing reference section? '21' on line 1240 looks like a reference -- Missing reference section? '19' on line 1234 looks like a reference Summary: 15 errors (**), 0 flaws (~~), 3 warnings (==), 23 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Tests 3 for ATM Management 5 September 1, 1998 7 Michael Noto (editor) 8 Network Equipment Technologies 9 mike_noto@net.com 11 Kaj Tesink (editor) 12 Bell Communications Research 13 kaj@cc.bellcore.com 15 1. Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are 18 working documents of the Internet Engineering Task Force 19 (IETF), its areas, and its working groups. Note that other 20 groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet- 26 Drafts as reference material or to cite them other than as 27 ``work in progress.'' 29 To learn the current status of any Internet-Draft, please 30 check the ``1id-abstracts.txt'' listing contained in the 31 Internet- Drafts Shadow Directories on ftp.ietf.org (US East 32 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 33 or munnari.oz.au (Pacific Rim). 35 Copyright Notice 37 Copyright (C) The Internet Society (1998). All Rights 38 Reserved. 40 draft ATM Test Objects September 1, 1998 42 2. Abstract 44 This memo defines a portion of the Management Information Base 45 (MIB) for use with network management protocols in the 46 Internet community. In particular, it describes objects used 47 for managing ATM-based interfaces, devices, networks and 48 services in addition to those defined in the ATM MIB [16], to 49 provide support for the management of ATM Loopback Tests. 51 3. The SNMP Network Management Framework 53 The SNMP Management Framework presently consists of five major 54 components: 56 0 An overall architecture, described in RFC 2271 [1]. 58 0 Mechanisms for describing and naming objects and events 59 for the purpose of management. The first version of this 60 Structure of Management Information (SMI) is called SMIv1 61 and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 62 [4]. The second version, called SMIv2, is described in 63 RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 65 0 Message protocols for transferring management 66 information. The first version of the SNMP message 67 protocol is called SNMPv1 and described in RFC 1157 [8]. 68 A second version of the SNMP message protocol, which is 69 not an Internet standards track protocol, is called 70 SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 71 The third version of the message protocol is called 72 SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and 73 RFC 2274 [12]. 75 0 Protocol operations for accessing management information. 76 The first set of protocol operations and associated PDU 77 formats is described in RFC 1157 [8]. A second set of 78 protocol operations and associated PDU formats is 79 described in RFC 1905 [13]. 81 0 A set of fundamental applications described in RFC 2273 82 [14] and the view-based access control mechanism 83 described in RFC 2275 [15]. 85 draft ATM Test Objects September 1, 1998 87 Managed objects are accessed via a virtual information store, 88 termed the Management Information Base or MIB. Objects in the 89 MIB are defined using the mechanisms defined in the SMI. 91 This memo specifies a MIB module that is compliant to the 92 SMIv2. A MIB conforming to the SMIv1 can be produced through 93 the appropriate translations. The resulting translated MIB 94 must be semantically equivalent, except where objects or 95 events are omitted because no translation is possible (e.g., 96 use of Counter64). Some machine readable information in SMIv2 97 will be converted into textual descriptions in SMIv1 during 98 the translation process. However, this loss of machine 99 readable information is not considered to change the semantics 100 of the MIB. 102 draft ATM Test Objects September 1, 1998 104 4. Overview 106 The purpose of this memo is to provide additional 107 capabilities, not found in the ATM MIB [16], which are needed 108 to manage ATM interfaces. This memo addresses ATM Testing 109 Support and must be used in conjunction with the 110 System/Interface Test MIB [22]. 112 4.1. Background 114 In addition to the MIB module defined in this memo, other MIB 115 modules are necessary to manage ATM interfaces, links and 116 cross-connects. Examples include MIB II for general system 117 [17] and interface management [18], the DS3 or SONET MIBs for 118 management of SONET and DS3 physical interfaces, and, as 119 appropriate, MIB modules for applications that make use of 120 ATM, such as SMDS and LAN Emulation. These MIB modules are 121 outside the scope of this specification. 123 This MIB module requires the use of the ATM MIB module defined 124 in [16] and the System/Interface Test MIB module [22]. 126 This memo defines extensions to the ATM MIB in order to 127 support ATM Loopback Tests. An ATM Loopback Test provides the 128 ability to send out a loopback OAM (Operations and 129 Maintenance) cell to verify the existence of connectivity for 130 a particular connection. 132 draft ATM Test Objects September 1, 1998 134 4.2. Terminology 136 The following terms are defined here and used throughout this 137 MIB: 138 - Virtual Path Link (VPL) 139 - Virtual Path Connection (VPC) 140 - Virtual Path Segment (VP Segment) 141 - Virtual Channel Link (VCL) 142 - Virtual Channel Connection (VCC) 143 - Virtual Channel Segment (VC Segment). 145 _____ _______ _______ _______ _____ 146 | |____| |____| |____| |____| | 147 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 148 | |____| |____| |____| |____| | 149 |_____| |_______| |_______| |_______| |_____| 151 |<----->| Virtual |<----->| Virtual 152 Path Link Path Link 154 |<------------Virtual Path Connection---------->| 155 (between Host1 and Host2) 157 |<--------------->| Virtual Path 158 Segment (between 159 SwitchA and SwitchC) 161 Figure 1: Examples of Virtual Path Links, Virtual Path 162 Connection, and Virtual Path Segment 164 draft ATM Test Objects September 1, 1998 166 _____ _______ _______ _______ _____ 167 | |____| |____| |____| |____| | 168 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 169 | |____| |____| |____| |____| | 170 |_____| |_______| |_______| |_______| |_____| 172 |<----->| Virtual |<----->| Virtual 173 Channel Link Channel Link 175 |<----------Virtual Channel Connection--------->| 176 (between Host1 and Host2) 178 |<--------------->| Virtual Channel 179 Segment (between 180 SwitchA and SwitchC) 182 Figure 2: Examples of Virtual Channel Links, Virtual 183 Channel Connection, and Virtual Channel Segment 185 4.3. Supported Functions 187 The managed ATM objects are organized as follows: 189 (1) ATM Loopback Testing 190 (2) ATM End-Point Tables 192 4.3.1. ATM Loopback Testing 194 The loopback test provides the ability to send out a loopback 195 OAM cell to verify the existence of connectivity for a 196 particular connection. Loopback tests can be performed on 197 either an entire connection (i.e., an end-to-end test), a 198 segment of the connection (i.e., a segment test), a portion of 199 a segment (i.e., a loopback location identifier test), or the 200 network portion of a connection (i.e., a service internal 201 test). 203 The loopback test makes use of the Test Table defined in [22]. 204 For a given interface, a loopback test can be invoked by 205 obtaining ownership of a test and then by setting the value of 206 testType equal to one of the ATM Loopback Test Types defined 207 in Section 5. See procedures in [22] for using the Test Table. 209 draft ATM Test Objects September 1, 1998 211 After invoking a loopback test, the object testResult can be 212 read to determine the outcome of the loopback test (e.g., 213 'success(2)' if the loopback cell made it back to the 214 originator of the test or 'failed(7)' if the loopback cell did 215 not make it back). 217 The following types of loopback tests are defined: 219 - End-to-end Loopback Test 220 - Segment Loopback Test 221 - Loopback Test Using Loopback Location Identifier 222 - Network Loopback Test. 224 1) End-to-end Loopback Test 226 The end-to-end loopback (LB) is self-explanatory. For a VP 227 test, the cell is sent on the given VP, via VCI=4 specified in 228 [20]. For a VC test, the LB cell is sent on the VC under 229 test, with the PTI (Payload Type Indicator) set to 5 as 230 specified in [20]. Figure 3 illustrates the end-to-end 231 loopback test. 233 ____ _______ _______ _______ ____ 234 |Host| | | | | | | |Host| 235 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 236 |_______| |_______| |_______| 238 |<--------------------------------------------->| Test 239 Path 241 Figure 3: End-to-end Loopback Test 243 See Section 5 for more details on how to use the End-to-end 244 Loopback Test. 246 2) Segment Loopback Test 248 The segment LB test is explained in ITU-T I.610[21]. For a VP 249 segment test, the LB cell is sent on the VP under test via 250 VCI=3 as specified in [20], and the Loopback Location ID field 251 is set to all 1's. For a VC segment test, the LB cell is sent 252 on the VC under test, with the PTI set to 4 as specified in 253 draft ATM Test Objects September 1, 1998 255 [20], and the Loopback Location ID field is set to all 1's. 257 This test involves a LB cell being inserted at a pre-defined 258 segment end-point, and looped back at the corresponding 259 segment end-point encountered. The pair of segment end-points 260 define a segment (which is used for the segment loopback 261 test). A VP/VC connection can have multiple segments, but 262 multiple segments cannot overlap. 264 A UNI interface is by definition defined as a segment end- 265 point (hence a UNI would be considered a segment). A segment 266 can also define: 267 - a B-ICI 268 - a public carrier's 'piece' of the connection 269 - a private network's 'piece' of the connection. 271 In order to support this functionality, the VP/VC link 272 termination needs to be able to be defined as a segment. This 273 can be done using either the atmVplSegmentEndPoint or 274 atmVclSegmentEndPoint object depending on whether it is for a 275 VPC or VCC. A segment loopback test is illustrated in Figure 276 4. 278 ____ _______ _______ _______ ____ 279 |Host| | | | | | | |Host| 280 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 281 |_______| |_______| |_______| 283 |<----------------------->| Segment 285 Figure 4: Segment Loopback Test 287 Section 5 describes the use of the ATM Segment Loopback Tests. 289 3) Loopback Test Using Loopback Location Identifier 291 This loopback test is a special type of 2) where the Loopback 292 Location ID field is set to a value that corresponds to a 293 specific node in a given network (Note that the format of this 294 field is not standardized, that is, the value is significant 295 only within an administrative domain). In this case, the 296 device initiating the LB test inserts the appropriate Loop 297 Back Location ID. When the LB cell reaches the corresponding 298 draft ATM Test Objects September 1, 1998 300 device, that device recognizes the Loopback Location ID as its 301 own, and loops it back. This test is useful for performing 302 fault sectionalization without having to provision segment 303 end-points. An additional object, the atmLoopbackID, is 304 defined to determine the loopback point. Figure 5 shows a 305 loopback test using a location identifier. Note that the 306 loopback test using location identifier can be used to perform 307 a loopback test over a portion of a defined segment. See 308 Figure 5. 310 ____ _______ _______ _______ ____ 311 |Host| | | | | | | |Host| 312 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 313 |_______| |_______| |_______| 315 |<---------->| Portion of Segment that 316 Loopback test is 317 performed on 319 |<----------------------->| Segment 321 Figure 5: Loopback Test Using Location Identifier 323 See Section 5 for more details. 325 4) Network Loopback Test 327 This is a loopback test that the manager requests an agent in 328 a network to perform over the internal portion of a designated 329 connection. The Network then initiates the internal network 330 loopback test by inserting an OAM loopback cell at one of the 331 end-points of the internal network portion of the connection. 332 When the loopback cell reaches the other end-point of the 333 internal Network , the cell is looped back. This test is 334 useful for verifying connectivity through a particular 335 network. Figure 6 illustrates the Network loopback test. 337 draft ATM Test Objects September 1, 1998 339 ____ _______ _______ _______ ____ 340 |Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host| 341 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 342 |_______| |_______| |_______| 344 |<----------------------->| LB Test Path 345 thru Network 1 347 Figure 6: Network Loopback Test 349 See Section 5 for more details. 351 4.3.1.1. ATM End-Point Tables 353 There are two ATM End-point tables: the ATM VP End-point Table 354 and the ATM VC End-point Table. The ATM VP End-point Table 355 augments the atmVplTable and defines the 356 atmVplEndptSegmentEndPoint object to represent whether or not 357 a specified VPL is a segment end-point. Similarly for Virtual 358 Channels, the ATM VC End-point Table and the 359 atmVclEndptSegmentEndPoint object are used to represent 360 whether or not a specified VCL is a segment end-point. 362 draft ATM Test Objects September 1, 1998 364 5. Definitions 366 ATMTEST-MIB DEFINITIONS ::= BEGIN 368 IMPORTS 369 MODULE-IDENTITY, OBJECT-IDENTITY, 370 OBJECT-TYPE, mib-2, experimental 371 FROM SNMPv2-SMI 372 MODULE-COMPLIANCE, OBJECT-GROUP 373 FROM SNMPv2-CONF 374 atmVplEntry, atmVclEntry 375 FROM ATM-MIB; 377 atmTESTMIB MODULE-IDENTITY 378 LAST-UPDATED "9809011200Z" 379 ORGANIZATION "IETF AToMMIB Working Group" 380 CONTACT-INFO 381 " Michael Noto 382 Postal: Network Equipment Technologies 383 800 Saginaw Drive RM 21.1.111 384 Redwood City, CA 94063 385 Tel: +1 415 569-7134 386 E-mail: noto@net.com 388 Kaj Tesink 389 Postal: Bell Communications Research 390 331 Newman Springs Road 391 Red Bank, NJ 07701 392 US 393 Tel: +1 732 758 5254 394 Fax: +1 732 758 4177 395 E-mail: kaj@cc.bellcore.com" 396 DESCRIPTION 397 "This MIB Module provides 398 ATM Loopback Tests and supporting objects 399 that must be supported by ATM devices 400 providing ATM Loopback Tests." 401 ::= { experimental XX } 403 -- ******** NOTE TO THE RFC EDITOR / IANA *********** 404 -- Before this module is put on the standards track 405 -- * replace { experimental XX } with { mib-2 YY } 406 -- * remove experimental from the IMPORTS clause 407 -- * assign YY by IANA. 409 draft ATM Test Objects September 1, 1998 411 atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} 413 -- This ATMTEST-MIB Module consists of the following: 414 -- (1) ATM Loopback Testing 415 -- (2) ATM End-Point Tables 417 draft ATM Test Objects September 1, 1998 419 -- ************************************************ 420 -- (1) ATM Loopback Testing 422 -- This concerns information for interfaces 423 -- supporting ATM Loopback Tests and includes: 424 -- 1. ATM Loopback Objects 425 -- 2. List of ATM Loopback Test Types 427 atmLoopbackTestGroup OBJECT IDENTIFIER::= { 428 atmTESTMIBObjects 1} 430 -- 1. ATM Loopback Objects 431 -- The following objects are defined for use in 432 -- performing ATM Loopback Tests. 434 atmLoopbackID OBJECT-TYPE 435 SYNTAX OCTET STRING(SIZE(16)) 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "This identifier is used to identify this local 440 ATM device. The value of this object can be used 441 by other ATM devices to identify this local ATM 442 device as the device that is being requested to 443 loopback the OAM Loopback cell. The default for 444 this field is all 1's, which would indicate a 445 segment OAM Loopback Test. Location Identifiers of 446 less than 16 octets are left justified, and padded 447 with all 0's." 448 DEFVAL { 'ffffffffffffffffffffffffffffffff'H } 449 ::= { atmLoopbackTestGroup 1 } 451 -- 2. List of ATM Loopback Test Types 452 -- The following loopback test types are defined: 453 -- atmLoopbackVpE2e 454 -- atmLoopbackVcE2e 455 -- atmLoopbackVpSegment 456 -- atmLoopbackVcSegment 457 -- atmLoopbackVpLocationID 458 -- atmLoopbackVcLocationID 459 -- atmLoopbackVpServiceInternal 460 -- atmLoopbackVcServiceInternal 462 draft ATM Test Objects September 1, 1998 464 atmLoopbackTestTypes OBJECT IDENTIFIER ::= { 465 atmLoopbackTestGroup 4 } 467 atmLoopbackVpE2e OBJECT-IDENTITY 468 STATUS current 469 DESCRIPTION 470 "This is an end-to-end loopback test performed on a 471 designated VP (Virtual Path). To perform this test 472 an end-to-end loopback OAM cell is inserted at one 473 of the end-points of the designated VP connection 474 (e.g., at a host) via VCI=4 (the VCI value for VP 475 OAM end-to-end cells), travels to the other end- 476 point of the VP connection, and then loops back to 477 the originating end-point on the designated VP. 478 Success is achieved if the loopback OAM cell 479 returns to the originating end-point within 5 480 seconds, otherwise, the test fails. 482 The manager-station performs a loopback test by 483 making use of the testTable defined in [22]. In 484 order to run this test the object testType in the 485 testTable shall be set to atmLoopbackVpE2e, and the 486 object testTarget points to the row in the 487 atmVplTable in [16] corresponding to the VP 488 designated for the test. 490 Before starting a test, a manager-station must 491 first obtain 'ownership' of the entry in the 492 testTable for the interface to be tested (follow 493 procedure defined in [22]). Once the manager- 494 station obtains ownership, a loopback test for a 495 given interface can be invoked by first setting up 496 parameters necessary for the loopback test (e.g., 497 set the testTarget), and then setting the value of 498 testType in the testTable equal to 499 'atmLoopbackVpE2e'. The testRowStatus is used to 500 invoke the atmLoopbackVpE2e test on the VP with the 501 VPI corresponding to the testTarget. 503 After invoking a loopback test, wait for the test 504 completion by polling for the object testResult. A 505 value of 'inProgress(3)' will result if the test is 506 still in progress. Once the test is completed, the 507 object testResult will have a value of 'success(2)' 509 draft ATM Test Objects September 1, 1998 511 if the loopback OAM cell returned to the originator 512 of the test within 5 seconds, if not, a value of 513 'failed(7)' will result. If the ATM system does 514 not support this type of loopback test, then a 515 value of 'notSupported(4)' will be provided. Other 516 possible values for the testResult object are 517 'unAbleToRun(5)' and 'aborted(6)'." 518 ::= { atmLoopbackTestTypes 1 } 520 atmLoopbackVcE2e OBJECT-IDENTITY 521 STATUS current 522 DESCRIPTION 523 "This is an end-to-end loopback test performed on a 524 designated VC (Virtual Channel). To perform this 525 test an end-to-end loopback OAM cell is inserted at 526 one of the end-points of the designated VC 527 connection (e.g., at a host) via PTI=5 (the PTI 528 value used for VC OAM end-to-end cells), travels to 529 the other end-point of the VC connection, and then 530 loops back to the originating end-point on the 531 designated VC. Success is achieved if the loopback 532 OAM cell returns to the originating end-point within 533 5 seconds, otherwise, the test fails. 535 The manager-station performs a loopback test by 536 making use of the testTable defined in [22]. In 537 order to run this test the object testType in the 538 testTable shall be set to atmLoopbackVcE2e, and the 539 object testTarget points to the row in the 540 atmVclTable in [16] corresponding to the VC 541 designated for the test. 543 Before starting a test, a manager-station must first 544 obtain 'ownership' of the entry in the testTable for 545 the interface to be tested (follow procedure defined 546 in [22]). Once the manager-station obtains 547 ownership, a loopback test for a given interface can 548 be invoked by first setting up parameters necessary 549 for the loopback test (e.g., set the testTarget), 550 and then setting the value of testType in the 551 testTable equal to 'atmLoopbackVcE2e'. The 552 testRowStatus is used to invoke the atmLoopbackVcE2e 553 test on the VC with the VPI/VCI corresponding to the 554 testTarget. 556 draft ATM Test Objects September 1, 1998 558 After invoking a loopback test, wait for the test 559 completion by polling for the object testResult. A 560 value of 'inProgress(3)' will result if the test is 561 still in progress. Once the test is completed, the 562 object testResult will have a value of 'success(2)' 563 if the loopback OAM cell returned to the originator 564 of the test within 5 seconds, if not, a value of 565 'failed(7)' will result. If the ATM system does not 566 support this type of loopback test, then a value of 567 'notSupported(4)' will be provided. Other possible 568 values for the testResult object are 569 'unAbleToRun(5)' and 'aborted(6)'." 570 ::= { atmLoopbackTestTypes 2 } 572 atmLoopbackVpSegment OBJECT-IDENTITY 573 STATUS current 574 DESCRIPTION 575 "This is a loopback test performed on a designated 576 segment of a VP (Virtual Path). To perform this test 577 a segment OAM cell is inserted at one of the segment 578 end-points of the designated VP connection (e.g., at 579 a host) via VCI=3 (the VCI used for VP OAM segment 580 cells), travels across the segment on the designated 581 VP to the device pre-configured as the corresponding 582 segment end-point, and then loops back to the 583 originating segment end-point on the designated VP. 584 Success is achieved if the loopback OAM cell returns 585 to the originating end-point within 5 seconds, 586 otherwise, the test fails. 588 In order to use the atmLoopbackVpSegment test, a 589 segment must be defined by setting up segment end- 590 points using the atmVplEndptSegmentEndPoint object 591 from the atmVplEndptTable. The 592 atmVplEndptSegmentEndPoint is set to 593 'isaVpSegmentEndPoint(1)' for each segment end-point. 594 Note that this object is by default set to 595 'isaVpSegmentEndPoint(1)' if the atmVplTable supports 596 one end of a UNI. In such a case, a UNI VP loopback 597 test would be achieved when the atmLoopbackVpSegment 598 test was initiated over the UNI. 600 The manager-station performs a loopback test by 601 making use of the testTable defined in [22]. In 603 draft ATM Test Objects September 1, 1998 605 order to run this test the object testType in the 606 testTable shall be set to atmLoopbackVpE2e, and the 607 object testTarget points to the row in the 608 atmVplTable in [16] corresponding to the VP 609 designated for the test. 611 Before starting a test, a manager-station must first 612 obtain 'ownership' of the entry in the testTable for 613 the interface to be tested (follow procedure defined 614 in [22]). Once the manager-station obtains 615 ownership, a loopback test for a given interface can 616 be invoked by first setting up parameters necessary 617 for the loopback test (e.g., set the testTarget), and 618 then setting the value of testType in the testTable 619 equal to 'atmLoopbackVpSegment'. The testRowStatus is 620 used to invoke the atmLoopbackVpSegment test on the 621 VP with the VPI corresponding to the testTarget. 623 After invoking a loopback test, wait for the test 624 completion by polling for the object testResult. A 625 value of 'inProgress(3)' will result if the test is 626 still in progress. Once the test is completed, the 627 object testResult will have a value of 'success(2)' 628 if the loopback OAM cell returned to the originator 629 of the test within 5 seconds, if not, a value of 630 'failed(7)' will result. If the ATM system does not 631 support this type of loopback test, then a value of 632 'notSupported(4)' will be provided. Other possible 633 values for the testResult object are 'unAbleToRun(5)' 634 and 'aborted(6)'." 635 ::= { atmLoopbackTestTypes 3 } 637 atmLoopbackVcSegment OBJECT-IDENTITY 638 STATUS current 639 DESCRIPTION 640 "This is a loopback test performed on a designated 641 segment of a VC (Virtual Channel). To perform this 642 test a segment OAM cell is inserted at one of the 643 segment end-points of the designated VC connection 644 (e.g., at a host) via PTI=4 (the PTI value used for VC 645 OAM segment cells), travels across the segment on the 646 designated VC to the device pre-configured as the 647 corresponding segment end-point, and then loops back 648 to the originating segment end-point on the designated 650 draft ATM Test Objects September 1, 1998 652 VC. Success is achieved if the loopback OAM cell 653 returns to the originating end-point within 5 seconds, 654 otherwise, the test fails. 656 In order to use the atmLoopbackVcSegment test, a 657 segment must be defined by setting up segment end- 658 points using the atmVclEndptSegmentEndPoint object 659 from the atmVclEndptTable. The 660 atmVclEndptSegmentEndPoint is set to 661 'isaVcSegmentEndPoint(1)' for each segment end-point. 662 Note that this object is by default set to 663 'isaVcSegmentEndPoint(1)' if the atmVclTable supports 664 one end of a UNI. In such a case, a UNI VC loopback 665 test would be achieved when the atmLoopbackVcSegment 666 test was initiated over the UNI. 668 The manager-station performs a loopback test by making 669 use of the testTable defined in [22]. In order to run 670 this test the object testType in the testTable shall 671 be set to atmLoopbackVcE2e, and the object testTarget 672 points to the row in the atmVclTable in [16] 673 corresponding to the VC designated for the test. 675 Before starting a test, a manager-station must first 676 obtain 'ownership' of the entry in the testTable for 677 the interface to be tested (follow procedure defined 678 in [22]). Once the manager-station obtains ownership, 679 a loopback test for a given interface can be invoked 680 by first setting up parameters necessary for the 681 loopback test (e.g., set the testTarget), and then 682 setting the value of testType in the testTable equal 683 to 'atmLoopbackVcSegment'. The testRowStatus is used 684 to invoke the atmLoopbackVcSegment test on the VC with 685 the VPI/VCI corresponding to the testTarget. 687 After invoking a loopback test, wait for the test 688 completion by polling for the object testResult. A 689 value of 'inProgress(3)' will result if the test is 690 still in progress. Once the test is completed, the 691 object testResult will have a value of 'success(2)' if 692 the loopback OAM cell returned to the originator of 693 the test within 5 seconds, if not, a value of 694 'failed(7)' will result. If the ATM system does not 695 support this type of loopback test, then a value of 696 'notSupported(4)' will be provided. Other possible 698 draft ATM Test Objects September 1, 1998 700 values for the testResult object are 'unAbleToRun(5)' 701 and 'aborted(6)'." 702 ::= { atmLoopbackTestTypes 4 } 704 atmLoopbackVpLocationId OBJECT-IDENTITY 705 STATUS current 706 DESCRIPTION 707 "This is a loopback test performed on a portion of a 708 designated VP segment. To perform this test a loopback 709 OAM cell is inserted at a connection point of the 710 designated VP connection (e.g., the end-point or a 711 tandem point) with a value inserted in the Location 712 Identifier ID field of the OAM cell that corresponds to 713 the ATM device where the cell is to be looped back. 714 The loopback cell then travels through the VP 715 connection until it reaches the designated ATM device, 716 where it is looped back to the loopback cell insertion 717 point on the designated VP. Success is achieved if the 718 loopback OAM cell returns to the originating point of 719 insertion within 5 seconds, otherwise, the test fails. 721 The manager-station performs a loopback test by making 722 use of the testTable defined in [22]. In order to run 723 this test the object testType in the testTable shall be 724 set to atmLoopbackVpE2e. The object testTarget points 725 to the row in the atmVplTable in [16] corresponding to 726 the VP designated for the test. The object testMoreInfo 727 contains the desired Loopback Location ID. 729 Before starting a test, a manager-station must first 730 obtain 'ownership' of the entry in the testTable for 731 the interface to be tested (follow procedure defined in 732 [22]). Once the manager-station obtains ownership, a 733 loopback test for a given interface can be invoked by 734 first setting up parameters necessary for the loopback 735 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 736 set the testTarget), and then setting the value of 737 testType in the testTable equal to 738 'atmLoopbackVpSegment'. The testRowStatus is used to 739 invoke the atmLoopbackVpLocationId on the VP with the 740 VPI corresponding to the testTarget and looped back at 741 loopback location ID= AAAABBBBCCCCDDDD. 743 After invoking a loopback test, wait for the test 745 draft ATM Test Objects September 1, 1998 747 completion by polling for the object testResult. A 748 value of 'inProgress(3)' will result if the test is 749 still in progress. Once the test is completed, the 750 object testResult will have a value of 'success(2)' if 751 the loopback OAM cell returned to the originator of the 752 test within 5 seconds, if not, a value of 'failed(7)' 753 will result. If the ATM system does not support this 754 type of loopback test, then a value of 755 'notSupported(4)' will be provided. Other possible 756 values for the testResult object are 'unAbleToRun(5)' 757 and 'aborted(6)'." 758 ::= { atmLoopbackTestTypes 5 } 760 atmLoopbackVcLocationId OBJECT-IDENTITY 761 STATUS current 762 DESCRIPTION 763 "This is a loopback test performed on a portion of a 764 designated Vc segment. To perform this test a loopback 765 OAM cell is inserted at a connection point of the 766 designated VC connection (e.g., the end-point or a 767 tandem point) with a value inserted in the Location 768 Identifier ID field of the OAM cell that corresponds to 769 the ATM device where the cell is to be looped back. 770 The loopback cell then travels through the VC 771 connection until it reaches the designated ATM device, 772 where it is looped back to the loopback cell insertion 773 point on the designated VC. Success is achieved if the 774 loopback OAM cell returns to the originating point of 775 insertion within 5 seconds, otherwise, the test fails. 777 The manager-station performs a loopback test by making 778 use of the testTable defined in [22]. In order to run 779 this test the object testType in the testTable shall be 780 set to atmLoopbackVcE2e. The object testTarget points 781 to the row in the atmVclTable in [16] corresponding to 782 the VC designated for the test. The object testMoreInfo 783 contains the desired Loopback Location ID. 785 Before starting a test, a manager-station must first 786 obtain 'ownership' of the entry in the testTable for 787 the interface to be tested (follow procedure defined in 788 [22]). Once the manager-station obtains ownership, a 789 loopback test for a given interface can be invoked by 790 first setting up parameters necessary for the loopback 792 draft ATM Test Objects September 1, 1998 794 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 795 set the testTarget), and then setting the value of 796 testType in the testTable equal to 797 'atmLoopbackVcSegment.d'. The testRowStatus is used to 798 invoke the atmLoopbackVcLocationId test on the VC with 799 the VPI/VCI corresponding to the testTarget and looped 800 back at loopback location ID= AAAABBBBCCCCDDDD. 802 After invoking a loopback test, wait for the test 803 completion by polling for the object testResult. A 804 value of 'inProgress(3)' will result if the test is 805 still in progress. Once the test is completed, the 806 object testResult will have a value of 'success(2)' if 807 the loopback OAM cell returned to the originator of the 808 test within 5 seconds, if not, a value of 'failed(7)' 809 will result. If the ATM system does not support this 810 type of loopback test, then a value of 811 'notSupported(4)' will be provided. Other possible 812 values for the testResult object are 'unAbleToRun(5)' 813 and 'aborted(6)'." 814 ::= { atmLoopbackTestTypes 6 } 816 atmLoopbackVpServiceInternal OBJECT-IDENTITY 817 STATUS current 818 DESCRIPTION 819 "This is a loopback test that the manager requests an 820 agent to perform over the managed resource's internal 821 portion of a designated VP (i.e., between the ingress 822 and egress interfaces of the VP connection). The agent 823 is provided with the Ingress VPI, Egress Interface, and 824 Egress VPI in order to run this internal test. This 825 test may be useful in proxy situations where the proxy 826 agent represents a network. Implementations of this 827 test may be specific to the managed resource. One 828 implementation in a managed network may be as follows, 829 the managed network inserts a segment loopback OAM cell 830 at the network internal segment end-point 831 (corresponding to the ingress connection point) for the 832 designated VP connection. The loopback cell then 833 travels through the network's portion of the VP 834 connection until it reaches the networks connection 835 point to the egress, where it is looped back to the 836 network's cell insertion point on the designated VP. 837 Success is achieved if the loopback OAM cell returns to 838 the originating internal network segment end-point 840 draft ATM Test Objects September 1, 1998 842 within 5 seconds, otherwise, the test fails. 844 The manager-station performs a loopback test by making 845 use of the testTable defined in [22]. In order to run 846 this test the object testType in the testTable shall be 847 set to atmLoopbackVpServiceInternal, and the object 848 testTarget points to the row in the 849 atmVpCrossConnectTable in [16] corresponding to the VP 850 designated for the test. 852 Before starting a test, a manager-station must first 853 obtain 'ownership' of the entry in the testTable for 854 the interface to be tested (follow procedure defined in 855 [22]). Once the manager-station obtains ownership, a 856 loopback test for a given interface can be invoked by 857 first setting up parameters necessary for the loopback 858 test (e.g., set the testTarget), and then setting the 859 value of testType in the testTable equal to 860 'atmLoopbackVpServiceInternal' The testRowStatus is 861 used to invoke the atmLoopbackVpServiceInternal test on 862 the VP crossconnect with the ingress and egress VPI 863 values corresponding to the testTarget. 865 After invoking a loopback test, wait for the test 866 completion by polling for the object testResult. A 867 value of 'inProgress(3)' will result if the test is 868 still in progress. Once the test is completed, the 869 object testResult will have a value of 'success(2)' if 870 the loopback OAM cell returned to the originator of the 871 test within 5 seconds, if not, a value of 'failed(7)' 872 will result. If the ATM system does not support this 873 type of loopback test, then a value of 874 'notSupported(4)' will be provided. Other possible 875 values for the testResult object are 'unAbleToRun(5)' 876 and 'aborted(6)'." 877 ::= { atmLoopbackTestTypes 7 } 879 atmLoopbackVcServiceInternal OBJECT-IDENTITY 880 STATUS current 881 DESCRIPTION 882 "This is a loopback test that the manager requests an 883 agent to perform over the managed resource's internal 884 portion of a designated VC (i.e., between the ingress 885 and egress interfaces of the VC connection). The agent 886 is provided with the Ingress VPI, Ingress VCI, Egress 888 draft ATM Test Objects September 1, 1998 890 Interface, Egress VPI, and Egress VCI in order to run 891 this internal test. This test may be useful in proxy 892 situations where the proxy agent represents a network. 893 Implementations of this test may be specific to the 894 managed resource. One implemenation in a managed 895 network may be as follows, the managed network inserts 896 a segment loopback OAM cell at the network internal 897 segment end-point (corresponding to the ingress 898 connection point) for the designated VC connection. 899 The loopback cell then travels through the network's 900 portion of the VC connection until it reaches the 901 network's connection point to the egress, where it is 902 looped back to the network's cell insertion point on 903 the designated VC. Success is achieved if the loopback 904 OAM cell returns to the originating internal network 905 segment end-point within 5 seconds, otherwise, the test 906 fails. 908 The manager-station performs a loopback test by making 909 use of the testTable defined in [22]. In order to run 910 this test the object testType in the testTable shall be 911 set to atmLoopbackVcServiceInternal, and the object 912 testTarget points to the row in the 913 atmVcCrossConnectTable in [16] corresponding to the VC 914 designated for the test. 916 Before starting a test, a manager-station must first 917 obtain 'ownership' of the entry in the testTable for 918 the interface to be tested (follow procedure defined in 919 [22]). Once the manager-station obtains ownership, a 920 loopback test for a given interface can be invoked by 921 first setting up parameters necessary for the loopback 922 test (e.g., set the testTarget), and then setting the 923 value of testType in the testTable equal to 924 'atmLoopbackVcServiceInternal'. The testRowStatus is 925 used to invoke the atmLoopbackVcServiceInternal test on 926 the VC crossconnect with the ingress and egress VPI/VCI 927 values corresponding to the testTarget. 929 After invoking a loopback test, wait for the test 930 completion by polling for the object testResult. A 931 value of 'inProgress(3)' will result if the test is 932 still in progress. Once the test is completed, the 933 object testResult will have a value of 'success(2)' if 934 the loopback OAM cell returned to the originator of the 936 draft ATM Test Objects September 1, 1998 938 test within 5 seconds, if not, a value of 'failed(7)' 939 will result. If the ATM system does not support this 940 type of loopback test, then a value of 941 'notSupported(4)' will be provided. Other possible 942 values for the testResult object are 'unAbleToRun(5)' 943 and 'aborted(6)'." 944 ::= { atmLoopbackTestTypes 8 } 946 draft ATM Test Objects September 1, 1998 948 -- ************************************************ 949 -- (2) ATM End-Point Tables 951 -- This concerns information for interfaces 952 -- supporting ATM Loopback Tests and includes: 953 -- 1. ATM VP End-Point Table 954 -- 2. ATM VC End-Point Table 956 atmEndptGroup OBJECT IDENTIFIER::= { 957 atmTESTMIBObjects 2} 959 -- 1. ATM VP End-Point Table 961 atmVplEndptTable OBJECT-TYPE 962 SYNTAX SEQUENCE OF AtmVplEndptEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "End-point Information for each VP." 967 ::= { atmEndptGroup 1 } 969 atmVplEndptEntry OBJECT-TYPE 970 SYNTAX AtmVplEndptEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "An entry with end-point information about the ATM 975 VP." 976 AUGMENTS { atmVplEntry } 977 ::= { atmVplEndptTable 1 } 979 AtmVplEndptEntry ::= 980 SEQUENCE { 981 atmVplEndptSegmentEndPoint INTEGER 982 } 984 atmVplEndptSegmentEndPoint OBJECT-TYPE 985 SYNTAX INTEGER { 986 isaVplSegmentEndPoint(1), 987 notaVplSegmentEndPoint(2) 988 } 990 draft ATM Test Objects September 1, 1998 992 MAX-ACCESS read-create 993 STATUS current 994 DESCRIPTION 995 "An indication of whether or not the VP interface 996 has been configured to represent a VPC Segment 997 End-Point. If the corresponding VP Link is a UNI, 998 the value of this object is permanently set to 999 isaVplSegmentEndPoint(1). Otherwise, the default 1000 is set to notaVplSegmentEndPoint(2)." 1001 ::= { atmVplEndptEntry 1 } 1003 -- 2. ATM VC End-Point Table 1005 atmVclEndptTable OBJECT-TYPE 1006 SYNTAX SEQUENCE OF AtmVclEndptEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "End-point Information for each VC." 1011 ::= { atmEndptGroup 2 } 1013 atmVclEndptEntry OBJECT-TYPE 1014 SYNTAX AtmVclEndptEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "An entry with end-point information about the ATM 1019 VC." 1020 AUGMENTS { atmVclEntry } 1021 ::= { atmVclEndptTable 1 } 1023 AtmVclEndptEntry ::= 1024 SEQUENCE { 1025 atmVclEndptSegmentEndPoint INTEGER 1026 } 1028 atmVclEndptSegmentEndPoint OBJECT-TYPE 1029 SYNTAX INTEGER { 1030 isaVclSegmentEndPoint(1), 1031 notaVclSegmentEndPoint(2) 1032 } 1033 MAX-ACCESS read-create 1035 draft ATM Test Objects September 1, 1998 1037 STATUS current 1038 DESCRIPTION 1039 "An indication of whether or not the VC interface 1040 has been configured to represent a VCC Segment 1041 End-Point. If the corresponding VC Link is a UNI, 1042 the value of this object is permanently set to 1043 isaVclSegmentEndPoint(1). Otherwise, the default 1044 is set to notaVclSegmentEndPoint(2)." 1045 ::= { atmVclEndptEntry 1 } 1047 -- ************************************************ 1049 -- Conformance Information 1051 atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} 1053 atmTESTMIBGroups OBJECT IDENTIFIER 1054 ::= {atmTESTMIBConformance 1} 1056 atmTESTMIBCompliances OBJECT IDENTIFIER 1057 ::= {atmTESTMIBConformance 2} 1059 -- Compliance Statements 1061 atmTESTMIBCompliance MODULE-COMPLIANCE 1062 STATUS current 1063 DESCRIPTION 1064 "The compliance statement for SNMP entities which 1065 represent ATM interfaces. The compliance statements 1066 are used to determine if a particular group or object 1067 applies to hosts, networks/switches, or both." 1069 MODULE -- this module 1071 MANDATORY-GROUPS { atmLoopbackGroup } 1073 -- Objects in the ATM Loopback Test Group 1075 OBJECT atmLoopbackID 1076 MIN-ACCESS read-only 1077 DESCRIPTION 1078 "Write access is not required. This object is 1079 required for ATM systems supporting the 1080 atmLoopbackVpLocationID and atmLoopbackVcLocationID 1081 tests." 1083 draft ATM Test Objects September 1, 1998 1085 OBJECT atmVplEndptSegmentEndPoint 1086 MIN-ACCESS read-only 1087 DESCRIPTION 1088 "Write access is not required. This object is 1089 mandatory for systems that are supporting ATM loopback 1090 tests." 1092 OBJECT atmVclEndptSegmentEndPoint 1093 MIN-ACCESS read-only 1094 DESCRIPTION 1095 "Write access is not required. This object is 1096 mandatory for systems that are supporting ATM loopback 1097 tests." 1099 ::= { atmTESTMIBCompliances 1 } 1101 -- ********************************************** 1103 -- Units of Conformance 1105 atmLoopbackGroup OBJECT-GROUP 1107 OBJECTS { 1108 atmLoopbackID, 1109 atmVplEndptSegmentEndPoint, 1110 atmVclEndptSegmentEndPoint 1111 } 1112 STATUS current 1113 DESCRIPTION 1114 "A collection of objects providing information 1115 for Loopback Tests." 1116 ::= { atmTESTMIBGroups 1 } 1118 END 1119 draft ATM Test Objects September 1, 1998 1121 6. Acknowledgments 1123 This document is a product of the AToMMIB Working Group. The 1124 authors would like to acknowledge Dawn Xie for her valuable 1125 suggestions for this memo. 1127 draft ATM Test Objects September 1, 1998 1129 7. References 1131 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 1132 Architecture for Describing SNMP Management Frameworks", 1133 RFC 2271, Cabletron Systems, Inc., BMC Software, Inc., 1134 IBM T. J. Watson Research, January 1998 1136 [2] Rose, M., and K. McCloghrie, "Structure and 1137 Identification of Management Information for TCP/IP-based 1138 Internets", RFC 1155, Performance Systems International, 1139 Hughes LAN Systems, May 1990 1141 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1142 RFC 1212, Performance Systems International, Hughes LAN 1143 Systems, March 1991 1145 [4] M. Rose, "A Convention for Defining Traps for use with 1146 the SNMP", RFC 1215, Performance Systems International, 1147 March 1991 1149 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1150 and S. Waldbusser, "Structure of Management Information 1151 for Version 2 of the Simple Network Management Protocol 1152 (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Systems, 1153 Inc., Dover Beach Consulting, Inc., International Network 1154 Services, January 1996. 1156 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1157 and S. Waldbusser, "Textual Conventions for Version 2 of 1158 the Simple Network Management Protocol (SNMPv2)", RFC 1159 1903, SNMP Research, Inc., Cisco Systems, Inc., Dover 1160 Beach Consulting, Inc., International Network Services, 1161 January 1996. 1163 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1164 and S. Waldbusser, "Conformance Statements for Version 2 1165 of the Simple Network Management Protocol (SNMPv2)", RFC 1166 1904, SNMP Research, Inc., Cisco Systems, Inc., Dover 1167 Beach Consulting, Inc., International Network Services, 1168 January 1996. 1170 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1171 "Simple Network Management Protocol", RFC 1157, SNMP 1172 Research, Performance Systems International, Performance 1173 Systems International, MIT Laboratory for Computer 1175 draft ATM Test Objects September 1, 1998 1177 Science, May 1990. 1179 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1180 and S. Waldbusser, "Introduction to Community-based 1181 SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems, 1182 Inc., Dover Beach Consulting, Inc., International Network 1183 Services, January 1996. 1185 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1186 and S. Waldbusser, "Transport Mappings for Version 2 of 1187 the Simple Network Management Protocol (SNMPv2)", RFC 1188 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 1189 Beach Consulting, Inc., International Network Services, 1190 January 1996. 1192 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1193 "Message Processing and Dispatching for the Simple 1194 Network Management Protocol (SNMP)", RFC 2272, SNMP 1195 Research, Inc., Cabletron Systems, Inc., BMC Software, 1196 Inc., IBM T. J. Watson Research, January 1998. 1198 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model 1199 (USM) for version 3 of the Simple Network Management 1200 Protocol (SNMPv3)", RFC 2274, IBM T. J. Watson Research, 1201 January 1998. 1203 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1204 and S. Waldbusser, "Protocol Operations for Version 2 of 1205 the Simple Network Management Protocol (SNMPv2)", RFC 1206 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 1207 Beach Consulting, Inc., International Network Services, 1208 January 1996. 1210 [14] Levi, D., Meyer, P., and B. Stewart, SNMPv3 1211 Applications", RFC 2273, SNMP Research, Inc., Secure 1212 Computing Corporation, Cisco Systems, January 1998. 1214 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1215 Access Control Model (VACM) for the Simple Network 1216 Management Protocol (SNMP)", RFC 2275, IBM T. J. Watson 1217 Research, BMC Software, Inc., Cisco Systems, Inc., 1218 January 1998. 1220 draft ATM Test Objects September 1, 1998 1222 [16] Kaj Tesink, "Definitions of Managed Objects for ATM 1223 Management", RFCxxxx, Bellcore, ???? 1998. 1225 [17] McCloghrie, K., and M. Rose, Editors, "Management 1226 Information Base for Network Management of TCP/IP-based 1227 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1228 Performance Systems International, March 1991. 1230 [18] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1231 MIB", RFC2233, cisco Systems, FTP Software, November 1232 1997. 1234 [19] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 1235 3.0) Specification, Part I", 1994. 1237 [20] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 1238 3.1) Specification, Part I", November 1994. 1240 [21] ITU-T Recommendation I.610, "Broadband Integrated Service 1241 Digital Network (B-ISDN) Operation and Maintenance 1242 Principles and Functions", July 1995. 1244 [22] McCloghrie, K., M. Greene, and K. Tesink, "Definitions of 1245 Managed Objects for System and Interface Testing", 1246 RFCxxxx, cisco Systems, Xedia Corp, Bellcore, ???? 1998. 1248 draft ATM Test Objects September 1, 1998 1250 8. Security Considerations 1252 This MIB contains both objects which allow an administrator to 1253 perform tests on ATM interfaces. Tests can only be performed 1254 when using these objects through in conjunction with [22]. 1255 Unauthorized access to the associated objects could cause a 1256 denial of service, or in combination with other (e.g., 1257 physical) security breaches, could cause unauthorized 1258 connectivity to a device. The tests defined in this document 1259 are not service interupting. 1261 9. Authors' Addresses 1263 Michael Noto 1264 Network Equipment Technologies 1265 800 Saginaw Drive RM 21.1.111 1266 Redwood City, CA 94063 1267 Phone +1 415 569-7134 1268 EMail: mike_noto@net.com 1270 Kaj Tesink 1271 Bell Communications Research 1272 331 Newman Springs Road 1273 P.O. Box 7020 1274 Red Bank, NJ 07701-7020 1275 Phone: (732) 758-5254 1276 EMail: kaj@cc.bellcore.com 1278 10. RFC Editor and IANA Considerations 1280 Prior to publication of this memo as an RFC, the RFC Editor 1281 and IANA are requested to make a suitable OBJECT IDENTIFIER 1282 assignment and update the following in the MIB: 1284 -- * replace { experimental XX } with { mib-2 YY } 1285 -- * remove 'experimental' from the IMPORTS clause 1286 -- * assign YY by IANA. 1287 -- * remove this notice in the MIB 1288 draft ATM Test Objects September 1, 1998 1290 11. Full Copyright Statement 1292 Copyright (C) The Internet Society (1998). All Rights 1293 Reserved. 1295 This document and translations of it may be copied and 1296 furnished to others, and derivative works that comment on or 1297 otherwise explain it or assist in its implementation may be 1298 prepared, copied, published and distributed, in whole or in 1299 part, without restriction of any kind, provided that the above 1300 copyright notice and this paragraph are included on all such 1301 copies and derivative works. However, this document itself 1302 may not be modified in any way, such as by removing the 1303 copyright notice or references to the Internet Society or 1304 other Internet organizations, except as needed for the purpose 1305 of developing Internet standards in which case the procedures 1306 for copyrights defined in the Internet Standards process must 1307 be followed, or as required to translate it into languages 1308 other than English. 1310 The limited permissions granted above are perpetual and will 1311 not be revoked by the Internet Society or its successors or 1312 assigns. 1314 This document and the information contained herein is provided 1315 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1316 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1317 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 1318 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1319 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1320 PARTICULAR PURPOSE. 1322 draft ATM Test Objects September 1, 1998 1324 Table of Contents 1326 1 Status of this Memo ................................... 1 1327 2 Abstract .............................................. 2 1328 3 The SNMP Network Management Framework ................. 2 1329 4 Overview .............................................. 4 1330 4.1 Background .......................................... 4 1331 4.2 Terminology ......................................... 5 1332 4.3 Supported Functions ................................. 6 1333 4.3.1 ATM Loopback Testing .............................. 6 1334 4.3.1.1 ATM End-Point Tables ............................ 10 1335 5 Definitions ........................................... 11 1336 6 Acknowledgments ....................................... 29 1337 7 References ............................................ 30 1338 8 Security Considerations ............................... 33 1339 9 Authors' Addresses .................................... 33 1340 10 RFC Editor and IANA Considerations ................... 33 1341 11 Full Copyright Statement ............................. 34