idnits 2.17.1 draft-ietf-atommib-test-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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. == 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. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 9. 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. ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (November 1996) is 10017 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? '1' on line 1183 looks like a reference -- Missing reference section? '2' on line 1186 looks like a reference -- Missing reference section? '3' on line 1191 looks like a reference -- Missing reference section? '4' on line 1196 looks like a reference -- Missing reference section? '5' on line 1202 looks like a reference -- Missing reference section? '6' on line 1207 looks like a reference -- Missing reference section? '10' on line 1221 looks like a reference -- Missing reference section? '8' on line 1214 looks like a reference -- Missing reference section? '9' on line 1217 looks like a reference -- Missing reference section? '7' on line 1211 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 1 warning (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT 2 4 Definitions of Tests 5 for ATM Management 7 November 1996 9 Michael Noto (editor) 10 Bell Communications Research 11 noto@cc.bellcore.com 13 Kaj Tesink (editor) 14 Bell Communications Research 15 kaj@cc.bellcore.com 17 1. Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are 20 working documents of the Internet Engineering Task Force 21 (IETF), its Areas, and its Working Groups. Note that other 22 groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as a 29 "work in progress". 31 To learn the current status of any Internet-Draft, please 32 check the "1id-abstracts.txt" listing contained in the 33 Internet-Drafts Shadow Directories on ds.internic.net (US East 34 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 35 or munnari.oz.au (Pacific Rim). 37 draft ATM Test Objects November 1996 39 2. Introduction 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management 43 protocols in the Internet community. In particular, it 44 describes objects used for managing ATM-based interfaces, 45 devices, networks and services in addition to those defined in 46 the ATM MIB [1], to provide additional support for the 47 management of ATM Loopback Tests. 49 3. The SNMPv2 Network Management Framework 51 The SNMPv2 Network Management Framework consists of four major 52 components. They are: 54 0 RFC 1902 [2] which defines the SMI, the mechanisms used 55 for describing and naming objects for the purpose of 56 management. 58 0 STD 17, RFC 1213 [3] defines MIB-II, the core set of 59 managed objects for the Internet suite of protocols. 61 0 RFC 1157 [4] and RFC 1905 [5] which define two versions 62 of the protocol used for network access to managed 63 objects. 65 The Framework permits new objects to be defined for the 66 purpose of experimentation and evaluation. 68 draft ATM Test Objects November 1996 70 4. Object Definitions 72 Managed objects are accessed via a virtual information store, 73 termed the Management Information Base or MIB. Objects in the 74 MIB are defined using the subset of Abstract Syntax Notation 75 One (ASN.1) defined in the SMI. In particular, each object 76 type is named by an OBJECT IDENTIFIER, an administratively 77 assigned name. The object type together with an object 78 instance serves to uniquely identify a specific instantiation 79 of the object. For human convenience, we often use a textual 80 string, termed the descriptor, to also refer to the object 81 type. 83 5. Overview 85 The purpose of this memo is to provide additional 86 capabilities, not found in the ATM MIB [1], which are needed 87 to manage ATM interfaces. This memo addresses ATM Testing 88 Support. 90 5.1. Background 92 In addition to the MIB module defined in this memo, other MIB 93 modules are necessary to manage ATM interfaces, links and 94 cross-connects. Examples include MIB II for general system 95 [3] and interface management [6], the DS3 or SONET MIBs for 96 management of SONET and DS3 physical interfaces, and, as 97 appropriate, MIB modules for applications that make use of 98 ATM, such as SMDS and LAN Emulation. These MIB modules are 99 outside the scope of this specification. 101 This MIB module also requires the use of the ATM MIB module 102 defined in [1]. 104 This memo proposes extensions to the ATM MIB in order to 105 support ATM Loopback Tests. An ATM Loopback Test provides the 106 ability to send out a loopback OAM (Operations and 107 Maintenance) cell to verify the exisitence of connectivity for 108 a particular connection. 110 The current specification of this supplemental ATM MIB is 111 based on SNMPv2 SMI. 113 draft ATM Test Objects November 1996 115 5.2. Important Definitions 117 The following terms are defined here and used throughout this 118 MIB: 119 - Virtual Path Link (VPL) 120 - Virtual Path Connection (VPC) 121 - Virtual Path Segment (VP Segment) 122 - Virtual Channel Link (VCL) 123 - Virtual Channel Connection (VCC) 124 - Virtual Channel Segment (VC Segment). 126 _____ _______ _______ _______ _____ 127 | |____| |____| |____| |____| | 128 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 129 | |____| |____| |____| |____| | 130 |_____| |_______| |_______| |_______| |_____| 132 |<----->| Virtual |<----->| Virtual 133 Path Link Path Link 135 |<------------Virtual Path Connection---------->| 136 (between Host1 and Host2) 138 |<--------------->| Virtual Path 139 Segment (between 140 SwitchA and SwitchC) 142 Figure 1: Examples of Virtual Path Links, Virtual Path 143 Connection, and Virtual Path Segment 145 draft ATM Test Objects November 1996 147 _____ _______ _______ _______ _____ 148 | |____| |____| |____| |____| | 149 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 150 | |____| |____| |____| |____| | 151 |_____| |_______| |_______| |_______| |_____| 153 |<----->| Virtual |<----->| Virtual 154 Channel Link Channel Link 156 |<----------Virtual Channel Connection--------->| 157 (between Host1 and Host2) 159 |<--------------->| Virtual Channel 160 Segment (between 161 SwitchA and SwitchC) 163 Figure 2: Examples of Virtual Channel Links, Virtual 164 Channel Connection, and Virtual Channel Segment 166 5.3. Supported Functions 168 The managed ATM objects are arranged into the following 169 groups: 171 I. ATM Testing Support: 172 (1) ATM Loopback Testing Group 173 (2) ATM End-Point Group. 175 5.3.1. ATM Testing Support 177 5.3.1.1. ATM Loopback Testing Group 179 The loopback test provides the ability to send out a loopback 180 OAM cell to verify the existence of connectivity for a 181 particular connection. Loopback tests can be performed on 182 either an entire connection (i.e., an end-to-end test), a 183 segment of the connection (i.e., a segment test), a portion of 184 a segment (i.e., a loopback location identifier test), or the 185 network portion of a connection (i.e., a service internal 186 test). 188 draft ATM Test Objects November 1996 190 The loopback test makes use of the Test Table defined in [10]. 191 For a given interface, a loopback test can be invoked by 192 obtaining ownership of a test and then by setting the value of 193 'testType' equal to one of the ATM Loopback Test Types defined 194 in Section (8). See procedures in [10] for using the Test 195 Table. After invoking a loopback test, the object 196 'testResult' can be read to determine the outcome of the 197 loopback test (e.g., success(2) if the loopback cell made it 198 back to the originator of the test or failed(7) if the 199 loopback cell did not make it back). 201 This group contains the following types of loopback tests: 203 - End-to-end Loopback Test 204 - Segment Loopback Test 205 - Loopback Test Using Loopback Location Identifier 206 - Network Loopback Test. 208 1) End-to-end Loopback Test 210 The end-to-end loopback (LB) is self-explanatory. For a VP 211 test, the cell is sent on the given VP, via VCI=4 specified in 212 [8]. For a VC test, the LB cell is sent on the VC under test, 213 with the PTI (Payload Type Indicator) set to 5 as specified in 214 [8]. Figure 3 illustrates the end-to-end loopback test. 216 ____ _______ _______ _______ ____ 217 |Host| | | | | | | |Host| 218 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 219 |_______| |_______| |_______| 221 |<--------------------------------------------->| Test 222 Path 224 Figure 3: End-to-end Loopback Test 226 See Section (8) for more details on how to use the End-to-end 227 Loopback Test. 229 2) Segment Loopback Test 230 draft ATM Test Objects November 1996 232 The segment LB test is explained in ITU-T I.610[9]. For a VP 233 segment test, the LB cell is sent on the VP under test via 234 VCI=3 as specified in [8], and the Loopback Location ID field 235 is set to all 1's. For a VC segment test, the LB cell is sent 236 on the VC under test, with the PTI set to 4 as specified in 237 [8], and the Loopback Location ID field is set to all 1's. 239 This test involves a LB cell being inserted at a pre-defined 240 segment end-point, and looped back at the corresponding 241 segment end-point encountered. The pair of segment end-points 242 define a segment (which is used for the segment loopback 243 test). A VP/VC connection can have multiple segments, but 244 multiple segments cannot overlap. 246 A UNI interface is by definition defined as a segment end- 247 point (hence a UNI would be considered a segment). A segment 248 can also define: 249 - a B-ICI 250 - a public carrier's 'piece' of the connection 251 - a private network's 'piece' of the connection. 253 In order to support this functionality, the VP/VC link 254 termination needs to be able to be defined as a segment. This 255 can be done using either the atmVplSegmentEndPoint or 256 atmVclSegmentEndPoint object depending on whether it is for a 257 VPC or VCC. A segment loopback test is illustrated in Figure 258 4. 260 ____ _______ _______ _______ ____ 261 |Host| | | | | | | |Host| 262 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 263 |_______| |_______| |_______| 265 |<----------------------->| Segment 267 Figure 4: Segment Loopback Test 269 Section (8) describes the use of the ATM Segment Loopback 270 Tests. 272 3) Loopback Test Using Loopback Location Identifier 273 draft ATM Test Objects November 1996 275 This loopback test is a special type of 2) where the Loopback 276 Location ID field is set to a value that corresponds to a 277 specific node in a given network (Note that the format of this 278 field is not standardized, that is, the value is significant 279 only within an administrative domain). In this case, the 280 device initiating the LB test inserts the appropriate Loop 281 Back Location ID. When the LB cell reaches the corresponding 282 device, that device recognizes the Loopback Location ID as its 283 own, and loops it back. This test is useful for performing 284 fault sectionalization without having to provision segment 285 end-points. An additional object, the loopbackLocationID, is 286 defined to determine the loopback point. Figure 5 shows a 287 loopback test using a location identifier. Note that the 288 loopback test using location identifier can be used to perform 289 a loopback test over a portion of a defined segment. See 290 Figure 5. 292 ____ _______ _______ _______ ____ 293 |Host| | | | | | | |Host| 294 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 295 |_______| |_______| |_______| 297 |<---------->| Portion of Segment that 298 Loopback test is 299 performed on 301 |<----------------------->| Segment 303 Figure 5: Loopback Test Using Location Identifier 305 See Section (8) for more details. 307 4) Network Loopback Test 309 This is a loopback test that the manager requests an agent in 310 a network to perform over the internal portion of a designated 311 connection. The Network then initiates the internal network 312 loopback test by inserting an OAM loopback cell at one of the 313 end-points of the internal network portion of the connection. 314 When the loopback cell reaches the other end-point of the 315 internal Network , the cell is looped back. This test is 316 useful for verifying connectivity through a particular 317 network. Figure 6 illustrates the Network loopback test. 319 draft ATM Test Objects November 1996 321 ____ _______ _______ _______ ____ 322 |Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host| 323 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 324 |_______| |_______| |_______| 326 |<----------------------->| LB Test Path 327 thru Network 1 329 Figure 6: Network Loopback Test 331 See Section (8) for more details. 333 5.3.1.2. ATM End-Point Group 335 The ATM End-Point Group contains two tables: the ATM VP End- 336 point Table and the ATM VC End-point Table. The ATM VP End- 337 point Table augments the atmVplTable and provides the 338 atmVplEndptSegmentEndPoint object to represent whether or not 339 a specified VPL is a segment end-point. Similarly for Virtual 340 Channels, the ATM VC End-point Table and the 341 atmVclEndptSegmentEndPoint object are used to represent 342 whether or not a specified VCL is a segment end-point. 344 draft ATM Test Objects November 1996 346 6. Definitions 348 ATMTEST-MIB DEFINITIONS ::= BEGIN 350 IMPORTS 351 MODULE-IDENTITY, OBJECT-IDENTITY, 352 OBJECT-TYPE, experimental 353 FROM SNMPv2-SMI 354 MODULE-COMPLIANCE, OBJECT-GROUP 355 FROM SNMPv2-CONF 356 mib-2 357 FROM RFC1213-MIB 358 atmVplEntry, atmVclEntry 359 FROM ATM-MIB; 361 atmTESTMIB MODULE-IDENTITY 362 LAST-UPDATED "9611051200Z" 363 ORGANIZATION "IETF AToMMIB Working Group" 364 CONTACT-INFO 365 " Michael Noto 366 Postal: Bell Communications Research 367 331 Newman Springs Road 368 Red Bank, NJ 07701 369 US 370 Tel: +1 908 758 5104 371 Fax: +1 908 758 4177 372 E-mail: noto@cc.bellcore.com 374 Kaj Tesink 375 Postal: Bell Communications Research 376 331 Newman Springs Road 377 Red Bank, NJ 07701 378 US 379 Tel: +1 908 758 5254 380 Fax: +1 908 758 4177 381 E-mail: kaj@cc.bellcore.com" 382 DESCRIPTION 383 "This MIB Module provides 384 ATM Loopback Tests and supporting objects 385 that must be supported by ATM devices 386 providing ATM Loopback Tests." 387 ::= { experimental XX } 389 atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} 391 draft ATM Test Objects November 1996 393 -- ******** NOTE TO THE RFC EDITOR ************** 394 -- In case this module is put on the standards track 395 -- replace the following: 396 -- "atmTESTMIB MODULE-IDENTITY ::= {experimental XX}" with 397 -- "atmTESTMIB MODULE-IDENTITY ::= {mib-2 YY}" 398 -- and assign YY by IANA. 400 -- This ATMTEST-MIB Module consists of the following groups: 401 -- ATM Testing Support: 402 -- (1) ATM Loopback Testing Group 403 -- (2) ATM End-Point Group 405 draft ATM Test Objects November 1996 407 -- ************************************************ 408 -- (1) ATM Loopback Testing Group 410 -- This group contains information for interfaces 411 -- supporting ATM Loopback Tests 412 -- This group includes the following: 413 -- 1. ATM Loopback Objects 414 -- 2. List of ATM Loopback Test Types 416 atmLoopbackTestGroup OBJECT IDENTIFIER::= { 417 atmTESTMIBObjects 1} 419 -- 1. ATM Loopback Objects 420 -- The following objects are defined for use in 421 -- performing ATM Loopback Tests. 423 atmLoopbackID OBJECT-TYPE 424 SYNTAX OCTET STRING(SIZE(16)) 425 MAX-ACCESS read-only 426 STATUS current 427 DESCRIPTION 428 "This identifier is used to identify this local 429 ATM device. The value of this object can be used 430 by other ATM devices to identify this local ATM 431 device as the device that is being requested to 432 loopback the OAM Loopback cell. An other ATM 433 device would accomplish this by placing the value 434 defined for this value in either the 435 atmLoopbackLocID or the atmLoopbackSrcID and then 436 performing a desired loopback test. The default 437 for this field is all 1's, which would indicate a 438 segment OAM Loopback Test. Location Identifiers of 439 less than 16 octets are left justified, and padded 440 with all '0's." 441 DEFVAL { 'ffffffffffffffffffffffffffffffff'H } 442 ::= { atmLoopbackTestGroup 1 } 444 atmLoopbackLocID OBJECT-TYPE 445 SYNTAX OCTET STRING(SIZE(16)) 446 MAX-ACCESS read-write 447 STATUS current 448 DESCRIPTION 449 "This parameter represents the identity of the ATM 450 device that is being requested to loopback the OAM 452 draft ATM Test Objects November 1996 454 Loopback cell. The default for this field is all 455 1's, which would indicate a segment OAM Loopback 456 Test. Location Identifiers of less than 16 octets 457 are left justified, and padded with all '0's. This 458 object is required for the atmLoopbackVpLocationID 459 and atmLoopbackVcLocationID tests." 460 DEFVAL { 'ffffffffffffffffffffffffffffffff'H } 461 ::= { atmLoopbackTestGroup 2 } 463 atmLoopbackSrcID OBJECT-TYPE 464 SYNTAX OCTET STRING(SIZE(16)) 465 MAX-ACCESS read-write 466 STATUS current 467 DESCRIPTION 468 "This optional parameter identifies the source 469 (e.g., the switch) originating the Loopback cell. 470 The default value of all '1's (binary) represents no 471 identification of the source. Source Identifiers of 472 less than 16 octets are left justified, and padded 473 with all '0's." 474 DEFVAL { 'ffffffffffffffffffffffffffffffff'H} 475 ::= { atmLoopbackTestGroup 3 } 477 -- 2. List of ATM Loopback Test Types 478 -- The following loopback test types are defined: 479 -- atmLoopbackVpE2e 480 -- atmLoopbackVcE2e 481 -- atmLoopbackVpSegment 482 -- atmLoopbackVcSegment 483 -- atmLoopbackVpLocationID 484 -- atmLoopbackVcLocationID 485 -- atmLoopbackVpServcInternal 486 -- atmLoopbackVcServcInternal 488 atmLoopbackTestTypes OBJECT IDENTIFIER ::= { 489 atmLoopbackTestGroup 4 } 491 atmLoopbackVpE2e OBJECT-IDENTITY 492 STATUS current 493 DESCRIPTION 494 "This is an end-to-end loopback test performed on a 495 designated VP (Virtual Path). To perform this test 496 an end-to-end loopback OAM cell is inserted at one of 498 draft ATM Test Objects November 1996 500 the end-points of the designated VP connection (e.g., 501 at a host) via VCI=4 (the VCI value for VP OAM end- 502 to-end cells), travels to the other end-point of the 503 VP connection, and then loops back to the originating 504 end-point on the designated VP. Success is achieved 505 if the loopback OAM cell returns to the originating 506 end-point within 5 seconds, otherwise, the test 507 fails. 509 The manager-station performs a loopback test by 510 making use of the testTable) defined in [10]. In 511 order to run this test the object 'testType' in the 512 testTable shall be set to atmLoopbackVpE2e, and the 513 object testTarget points to the row in the 514 atmVplTable in [1] corresponding to the VP designated 515 for the test. 517 Before starting a test, a manager-station must first 518 obtain 'ownership' of the entry in the testTable for 519 the interface to be tested (follow procedure defined 520 in [10]). Once the manager-station obtains 521 ownership, a loopback test for a given interface can 522 be invoked by first setting up parameters necessary 523 for the loopback test (e.g., set the testTarget), and 524 then setting the value of 'testType' in the testTable 525 equal to 'atmLoopbackVpE2e'. This will cause the 526 atmLoopbackVpE2e test to be invoked on the VP with 527 the VPI corresponding to the testTarget. 529 After invoking a loopback test, wait for the test 530 completion by polling for the object 'testResult'. A 531 value of 'inProgress(3)' will result if the test is 532 still in progress. Once the test is completed, the 533 object 'testResult' will have a value of 'success(2)' 534 if the loopback OAM cell returned to the originator 535 of the test within 5 seconds, if not, a value of 536 'failed(7)' will result. If the ATM system does not 537 support this type of loopback test, then a value of 538 'notSupported(4)' will be provided. Other possible 539 values for the 'testResult' object are 540 'unAbleToRun(5)' and 'aborted(6)'. 542 Test results are logged in the testLogTable [10]." 543 ::= { atmLoopbackTestTypes 1 } 545 draft ATM Test Objects November 1996 547 atmLoopbackVcE2e OBJECT-IDENTITY 548 STATUS current 549 DESCRIPTION 550 "This is an end-to-end loopback test performed on a 551 designated VC (Virtual Channel). To perform this test 552 an end-to-end loopback OAM cell is inserted at one of 553 the end-points of the designated VC connection (e.g., 554 at a host) via PTI=5 (the PTI value used for VC OAM 555 end-to-end cells), travels to the other end-point of 556 the VC connection, and then loops back to the 557 originating end-point on the designated VC. Success 558 is achieved if the loopback OAM cell returns to the 559 originating end-point within 5 seconds, otherwise, the 560 test fails. 562 The manager-station performs a loopback test by making 563 use of the testTable) defined in [10]. In order to 564 run this test the object 'testType' in the testTable 565 shall be set to atmLoopbackVcE2e, and the object 566 testTarget points to the row in the atmVclTable in [1] 567 corresponding to the VC designated for the test. 569 Before starting a test, a manager-station must first 570 obtain 'ownership' of the entry in the testTable for 571 the interface to be tested (follow procedure defined 572 in [10]). Once the manager-station obtains ownership, 573 a loopback test for a given interface can be invoked 574 by first setting up parameters necessary for the 575 loopback test (e.g., set the testTarget), and then 576 setting the value of 'testType' in the testTable equal 577 to 'atmLoopbackVcE2e'. This will cause the 578 atmLoopbackVcE2e test to be invoked on the VC with the 579 VPI/VCI corresponding to the testTarget. 581 After invoking a loopback test, wait for the test 582 completion by polling for the object 'testResult'. A 583 value of 'inProgress(3)' will result if the test is 584 still in progress. Once the test is completed, the 585 object 'testResult' will have a value of 'success(2)' 586 if the loopback OAM cell returned to the originator of 587 the test within 5 seconds, if not, a value of 588 'failed(7)' will result. If the ATM system does not 589 support this type of loopback test, then a value of 590 'notSupported(4)' will be provided. Other possible 591 values for the 'testResult' object are 593 draft ATM Test Objects November 1996 595 'unAbleToRun(5)' and 'aborted(6)'. 597 Test results are logged in the testLogTable [10]." 598 ::= { atmLoopbackTestTypes 2 } 600 atmLoopbackVpSegment OBJECT-IDENTITY 601 STATUS current 602 DESCRIPTION 603 "This is a loopback test performed on a designated 604 segment of a VP (Virtual Path). To perform this test a 605 segment OAM cell is inserted at one of the segment 606 end-points of the designated VP connection (e.g., at a 607 host) via VCI=3 (the VCI used for VP OAM segment 608 cells), travels across the segment on the designated VP 609 to the device pre-configured as the corresponding 610 segment end-point, and then loops back to the 611 originating segment end-point on the designated VP. 612 Success is achieved if the loopback OAM cell returns to 613 the originating end-point within 5 seconds, otherwise, 614 the test fails. 616 In order to use the atmLoopbackVpSegment test, a 617 segment must be defined by setting up segment end- 618 points using the atmVplEndptSegmentEndPoint object from 619 the atmVplEndptTable. The atmVplEndptSegmentEndPoint 620 is set to isaVpSegmentEndPoint(1) for each segment 621 end-point. Note that this object is by default set to 622 isaVpSegmentEndPoint(1) if the atmVplTable supports one 623 end of a UNI. In such a case, a UNI VP loopback test 624 would be achieved when the atmLoopbackVpSegment test 625 was initiated over the UNI. 627 The manager-station performs a loopback test by making 628 use of the testTable) defined in [10]. In order to run 629 this test the object 'testType' in the testTable shall 630 be set to atmLoopbackVpE2e, and the object testTarget 631 points to the row in the atmVplTable in [1] 632 corresponding to the VP designated for the test. 634 Before starting a test, a manager-station must first 635 obtain 'ownership' of the entry in the testTable for 636 the interface to be tested (follow procedure defined in 637 [10]). Once the manager-station obtains ownership, a 638 loopback test for a given interface can be invoked by 640 draft ATM Test Objects November 1996 642 first setting up parameters necessary for the loopback 643 test (e.g., set the testTarget), and then setting the 644 value of 'testType' in the testTable equal to 645 'atmLoopbackVpSegment'. This will cause the 646 atmLoopbackVpSegment test to be invoked on the VP with 647 the VPI corresponding to the testTarget. 649 After invoking a loopback test, wait for the test 650 completion by polling for the object 'testResult'. A 651 value of 'inProgress(3)' will result if the test is 652 still in progress. Once the test is completed, the 653 object 'testResult' will have a value of 'success(2)' 654 if the loopback OAM cell returned to the originator of 655 the test within 5 seconds, if not, a value of 656 'failed(7)' will result. If the ATM system does not 657 support this type of loopback test, then a value of 658 'notSupported(4)' will be provided. Other possible 659 values for the 'testResult' object are 'unAbleToRun(5)' 660 and 'aborted(6)'. 662 Test results are logged in the testLogTable [10]." 663 ::= { atmLoopbackTestTypes 3 } 665 atmLoopbackVcSegment OBJECT-IDENTITY 666 STATUS current 667 DESCRIPTION 668 "This is a loopback test performed on a designated 669 segment of a VC (Virtual Channel). To perform this 670 test a segment OAM cell is inserted at one of the 671 segment end-points of the designated VC connection 672 (e.g., at a host) via PTI=4 (the PTI value used for VC 673 OAM segment cells), travels across the segment on the 674 designated VC to the device pre-configured as the 675 corresponding segment end-point, and then loops back to 676 the originating segment end-point on the designated VC. 677 Success is achieved if the loopback OAM cell returns to 678 the originating end-point within 5 seconds, otherwise, 679 the test fails. 681 In order to use the atmLoopbackVcSegment test, a 682 segment must be defined by setting up segment end- 683 points using the atmVclEndptSegmentEndPoint object from 684 the atmVclEndptTable. The atmVclEndptSegmentEndPoint 685 is set to isaVcSegmentEndPoint(1) for each segment 687 draft ATM Test Objects November 1996 689 end-point. Note that this object is by default set to 690 isaVcSegmentEndPoint(1) if the atmVclTable supports one 691 end of a UNI. In such a case, a UNI VC loopback test 692 would be achieved when the atmLoopbackVcSegment test 693 was initiated over the UNI. 695 The manager-station performs a loopback test by making 696 use of the testTable) defined in [10]. In order to run 697 this test the object 'testType' in the testTable shall 698 be set to atmLoopbackVcE2e, and the object testTarget 699 points to the row in the atmVclTable in [1] 700 corresponding to the VC designated for the test. 702 Before starting a test, a manager-station must first 703 obtain 'ownership' of the entry in the testTable for 704 the interface to be tested (follow procedure defined in 705 [10]). Once the manager-station obtains ownership, a 706 loopback test for a given interface can be invoked by 707 first setting up parameters necessary for the loopback 708 test (e.g., set the testTarget), and then setting the 709 value of 'testType' in the testTable equal to 710 'atmLoopbackVcSegment'. This will cause the 711 atmLoopbackVcSegment test to be invoked on the VC with 712 the VPI/VCI corresponding to the testTarget. 714 After invoking a loopback test, wait for the test 715 completion by polling for the object 'testResult'. A 716 value of 'inProgress(3)' will result if the test is 717 still in progress. Once the test is completed, the 718 object 'testResult' will have a value of 'success(2)' 719 if the loopback OAM cell returned to the originator of 720 the test within 5 seconds, if not, a value of 721 'failed(7)' will result. If the ATM system does not 722 support this type of loopback test, then a value of 723 'notSupported(4)' will be provided. Other possible 724 values for the 'testResult' object are 'unAbleToRun(5)' 725 and 'aborted(6)'. 727 Test results are logged in the testLogTable [10]." 728 ::= { atmLoopbackTestTypes 4 } 730 atmLoopbackVpLocationId OBJECT-IDENTITY 731 STATUS current 732 DESCRIPTION 734 draft ATM Test Objects November 1996 736 "This is a loopback test performed on a portion of a 737 designated VP segment. To perform this test a loopback 738 OAM cell is inserted at a connection point of the 739 designated VP connection (e.g., the end-point or a 740 tandem point) with a value inserted in the Location 741 Identifier ID field of the OAM cell that corresponds to 742 the ATM device where the cell is to be looped back. 743 The loopback cell then travels through the VP 744 connection until it reaches the designated ATM device, 745 where it is looped back to the loopback cell insertion 746 point on the designated VP. Success is achieved if the 747 loopback OAM cell returns to the originating point of 748 insertion within 5 seconds, otherwise, the test fails. 750 The manager-station performs a loopback test by making 751 use of the testTable) defined in [10]. In order to run 752 this test the object 'testType' in the testTable shall 753 be set to atmLoopbackVpE2e.d, where the subidentifier 754 'd' consists of 16 subidentifiers with each 755 subidentifier corresponding to the value of a 756 subsequent octet of the Loopback Location ID defined in 757 I.610[9] starting with the most significant octet. The 758 object testTarget points to the row in the atmVplTable 759 in [1] corresponding to the VP designated for the test. 761 Before starting a test, a manager-station must first 762 obtain 'ownership' of the entry in the testTable for 763 the interface to be tested (follow procedure defined in 764 [10]). Once the manager-station obtains ownership, a 765 loopback test for a given interface can be invoked by 766 first setting up parameters necessary for the loopback 767 test (e.g., set d to AAAABBBBCCCCDDDD and set the 768 testTarget), and then setting the value of 'testType' 769 in the testTable equal to 'atmLoopbackVpSegment.d'. 770 This will cause the atmLoopbackVpLocationId test to be 771 invoked on the VP with the VPI corresponding to the 772 testTarget and looped back at loopback location ID= 773 AAAABBBBCCCCDDDD. 775 After invoking a loopback test, wait for the test 776 completion by polling for the object 'testResult'. A 777 value of 'inProgress(3)' will result if the test is 778 still in progress. Once the test is completed, the 779 object 'testResult' will have a value of 'success(2)' 780 if the loopback OAM cell returned to the originator of 782 draft ATM Test Objects November 1996 784 the test within 5 seconds, if not, a value of 785 'failed(7)' will result. If the ATM system does not 786 support this type of loopback test, then a value of 787 'notSupported(4)' will be provided. Other possible 788 values for the 'testResult' object are 'unAbleToRun(5)' 789 and 'aborted(6)'. 791 Test results are logged in the testLogTable [10]." 792 ::= { atmLoopbackTestTypes 5 } 794 atmLoopbackVcLocationId OBJECT-IDENTITY 795 STATUS current 796 DESCRIPTION 797 "This is a loopback test performed on a portion of a 798 designated Vc segment. To perform this test a loopback 799 OAM cell is inserted at a connection point of the 800 designated VC connection (e.g., the end-point or a 801 tandem point) with a value inserted in the Location 802 Identifier ID field of the OAM cell that corresponds to 803 the ATM device where the cell is to be looped back. 804 The loopback cell then travels through the VC 805 connection until it reaches the designated ATM device, 806 where it is looped back to the loopback cell insertion 807 point on the designated VC. Success is achieved if the 808 loopback OAM cell returns to the originating point of 809 insertion within 5 seconds, otherwise, the test fails. 811 The manager-station performs a loopback test by making 812 use of the testTable) defined in [10]. In order to run 813 this test the object 'testType' in the testTable shall 814 be set to atmLoopbackVcE2e.d, where the subidentifier 815 'd' consists of 16 subidentifiers with each 816 subidentifier corresponding to the value of a 817 subsequent octet of the Loopback Location ID defined in 818 I.610[9] starting with the most significant octet. The 819 object testTarget points to the row in the atmVclTable 820 in [1] corresponding to the VC designated for the test. 822 Before starting a test, a manager-station must first 823 obtain 'ownership' of the entry in the testTable for 824 the interface to be tested (follow procedure defined in 825 [10]). Once the manager-station obtains ownership, a 826 loopback test for a given interface can be invoked by 827 first setting up parameters necessary for the loopback 829 draft ATM Test Objects November 1996 831 test (e.g., set d to AAAABBBBCCCCDDDD and set the 832 testTarget), and then setting the value of 'testType' 833 in the testTable equal to 'atmLoopbackVcSegment.d'. 834 This will cause the atmLoopbackVcLocationId test to be 835 invoked on the VC with the VPI/VCI corresponding to the 836 testTarget and looped back at loopback location ID= 837 AAAABBBBCCCCDDDD. 839 After invoking a loopback test, wait for the test 840 completion by polling for the object 'testResult'. A 841 value of 'inProgress(3)' will result if the test is 842 still in progress. Once the test is completed, the 843 object 'testResult' will have a value of 'success(2)' 844 if the loopback OAM cell returned to the originator of 845 the test within 5 seconds, if not, a value of 846 'failed(7)' will result. If the ATM system does not 847 support this type of loopback test, then a value of 848 'notSupported(4)' will be provided. Other possible 849 values for the 'testResult' object are 'unAbleToRun(5)' 850 and 'aborted(6)'. 852 Test results are logged in the testLogTable [10]." 853 ::= { atmLoopbackTestTypes 6 } 855 atmLoopbackVpServcInternal OBJECT-IDENTITY 856 STATUS current 857 DESCRIPTION 858 "This is a loopback test that the manager requests an 859 agent to perform over the managed resource's internal 860 portion of a designated VP (i.e., between the ingress 861 and egress interfaces of the VP connection). The agent 862 is provided with the Ingress VPI, Egress Interface, and 863 Egress VPI in order to run this internal test. This 864 test may be useful in proxy situations where the proxy 865 agent represents a network. Implementations of this 866 test may be specific to the managed resource. One 867 implementation in a managed network may be as follows, 868 the managed network inserts a segment loopback OAM cell 869 at the network internal segment end-point 870 (corresponding to the ingress connection point) for the 871 designated VP connection. The loopback cell then 872 travels through the network's portion of the VP 873 connection until it reaches the networks connection 874 point to the egress, where it is looped back to the 875 network's cell insertion point on the designated VP. 877 draft ATM Test Objects November 1996 879 Success is achieved if the loopback OAM cell returns to 880 the originating internal network segment end-point 881 within 5 seconds, otherwise, the test fails. 883 The manager-station performs a loopback test by making 884 use of the testTable) defined in [10]. In order to run 885 this test the object 'testType' in the testTable shall 886 be set to atmLoopbackVpServcInternal, and the object 887 testTarget points to the row in the 888 atmVpCrossConnectTable in [1] corresponding to the VP 889 designated for the test. 891 Before starting a test, a manager-station must first 892 obtain 'ownership' of the entry in the testTable for 893 the interface to be tested (follow procedure defined in 894 [10]). Once the manager-station obtains ownership, a 895 loopback test for a given interface can be invoked by 896 first setting up parameters necessary for the loopback 897 test (e.g., set the testTarget), and then setting the 898 value of 'testType' in the testTable equal to 899 'atmLoopbackVpServcInternal'. This will cause the 900 atmLoopbackVpServcInternal test to be invoked on the VP 901 crossconnect with the ingress and egress VPI values 902 corresponding to the testTarget. 904 After invoking a loopback test, wait for the test 905 completion by polling for the object 'testResult'. A 906 value of 'inProgress(3)' will result if the test is 907 still in progress. Once the test is completed, the 908 object 'testResult' will have a value of 'success(2)' 909 if the loopback OAM cell returned to the originator of 910 the test within 5 seconds, if not, a value of 911 'failed(7)' will result. If the ATM system does not 912 support this type of loopback test, then a value of 913 'notSupported(4)' will be provided. Other possible 914 values for the 'testResult' object are 'unAbleToRun(5)' 915 and 'aborted(6)'. 917 Test results are logged in the testLogTable [10]." 918 ::= { atmLoopbackTestTypes 7 } 920 atmLoopbackVcServcInternal OBJECT-IDENTITY 921 STATUS current 922 DESCRIPTION 923 "This is a loopback test that the manager requests an 925 draft ATM Test Objects November 1996 927 agent to perform over the managed resource's internal 928 portion of a designated VC (i.e., between the ingress 929 and egress interfaces of the VC connection). The agent 930 is provided with the Ingress VPI, Ingress VCI, Egress 931 Interface, Egress VPI, and Egress VCI in order to run 932 this internal test. This test may be useful in proxy 933 situations where the proxy agent represents a network. 934 Implementations of this test may be specific to the 935 managed resource. One implemenation in a managed 936 network may be as follows, the managed network inserts 937 a segment loopback OAM cell at the network internal 938 segment end-point (corresponding to the ingress 939 connection point) for the designated VC connection. 940 The loopback cell then travels through the network's 941 portion of the VC connection until it reaches the 942 networks connection point to the egress, where it is 943 looped back to the network's cell insertion point on 944 the designated VC. Success is achieved if the loopback 945 OAM cell returns to the originating internal network 946 segment end-point within 5 seconds, otherwise, the test 947 fails. 949 The manager-station performs a loopback test by making 950 use of the testTable) defined in [10]. In order to run 951 this test the object 'testType' in the testTable shall 952 be set to atmLoopbackVcServcInternal, and the object 953 testTarget points to the row in the 954 atmVcCrossConnectTable in [1] corresponding to the VC 955 designated for the test. 957 Before starting a test, a manager-station must first 958 obtain 'ownership' of the entry in the testTable for 959 the interface to be tested (follow procedure defined in 960 [10]). Once the manager-station obtains ownership, a 961 loopback test for a given interface can be invoked by 962 first setting up parameters necessary for the loopback 963 test (e.g., set the testTarget), and then setting the 964 value of 'testType' in the testTable equal to 965 'atmLoopbackVcServcInternal'. This will cause the 966 atmLoopbackVcServcInternal test to be invoked on the VC 967 crossconnect with the ingress and egress VPI/VCI values 968 corresponding to the testTarget. 970 After invoking a loopback test, wait for the test 971 completion by polling for the object 'testResult'. A 973 draft ATM Test Objects November 1996 975 value of 'inProgress(3)' will result if the test is 976 still in progress. Once the test is completed, the 977 object 'testResult' will have a value of 'success(2)' 978 if the loopback OAM cell returned to the originator of 979 the test within 5 seconds, if not, a value of 980 'failed(7)' will result. If the ATM system does not 981 support this type of loopback test, then a value of 982 'notSupported(4)' will be provided. Other possible 983 values for the 'testResult' object are 'unAbleToRun(5)' 984 and 'aborted(6)'. 986 Test results are logged in the testLogTable [10]." 987 ::= { atmLoopbackTestTypes 8 } 989 draft ATM Test Objects November 1996 991 -- ************************************************ 992 -- (2) ATM End-Point Group 994 -- This group contains information for interfaces 995 -- supporting ATM Loopback Tests 996 -- This group includes the following: 997 -- 1. ATM VP End-Point Table 998 -- 2. ATM VC End-Point Table 1000 atmEndptGroup OBJECT IDENTIFIER::= { 1001 atmTESTMIBObjects 2} 1003 -- 1. ATM VP End-Point Table 1005 atmVplEndptTable OBJECT-TYPE 1006 SYNTAX SEQUENCE OF AtmVplEndptEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "End-point Information for each VP." 1011 ::= { atmEndptGroup 1 } 1013 atmVplEndptEntry OBJECT-TYPE 1014 SYNTAX AtmVplEndptEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "An entry with end-point information about the ATM 1019 VP." 1020 AUGMENTS { atmVplEntry } 1021 ::= { atmVplEndptTable 1 } 1023 AtmVplEndptEntry ::= 1024 SEQUENCE { 1025 atmVplEndptSegmentEndPoint INTEGER 1026 } 1028 atmVplEndptSegmentEndPoint OBJECT-TYPE 1029 SYNTAX INTEGER { 1030 isaVplSegmentEndPoint(1), 1031 notaVplSegmentEndPoint(2) 1033 draft ATM Test Objects November 1996 1035 } 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "An indication of whether or not the VP interface 1040 has been configured to represent a VPC Segment 1041 End-Point. If the corresponding VP Link is a UNI, 1042 the value of this object is permanently set to 1 1043 (isaVplSegmentEndPoint). Otherwise, the default is 1044 set to 2 (notaVplSegmentEndPoint)." 1045 ::= { atmVplEndptEntry 1 } 1047 -- 2. ATM VC End-Point Table 1049 atmVclEndptTable OBJECT-TYPE 1050 SYNTAX SEQUENCE OF AtmVclEndptEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "End-point Information for each VC." 1055 ::= { atmEndptGroup 2 } 1057 atmVclEndptEntry OBJECT-TYPE 1058 SYNTAX AtmVclEndptEntry 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "An entry with end-point information about the ATM 1063 VC." 1064 AUGMENTS { atmVclEntry } 1065 ::= { atmVclEndptTable 1 } 1067 AtmVclEndptEntry ::= 1068 SEQUENCE { 1069 atmVclEndptSegmentEndPoint INTEGER 1070 } 1072 atmVclEndptSegmentEndPoint OBJECT-TYPE 1073 SYNTAX INTEGER { 1074 isaVclSegmentEndPoint(1), 1075 notaVclSegmentEndPoint(2) 1076 } 1078 draft ATM Test Objects November 1996 1080 MAX-ACCESS read-create 1081 STATUS current 1082 DESCRIPTION 1083 "An indication of whether or not the VC interface 1084 has been configured to represent a VCC Segment 1085 End-Point. If the corresponding VC Link is a UNI, 1086 the value of this object is permanently set to 1 1087 (isaVclSegmentEndPoint). Otherwise, the default is 1088 set to 2 (notaVclSegmentEndPoint)." 1089 ::= { atmVclEndptEntry 1 } 1091 -- ************************************************ 1093 -- Conformance Information 1095 atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} 1097 atmTESTMIBGroups OBJECT IDENTIFIER 1098 ::= {atmTESTMIBConformance 1} 1100 atmTESTMIBCompliances OBJECT IDENTIFIER 1101 ::= {atmTESTMIBConformance 2} 1103 -- Compliance Statements 1105 atmTESTMIBCompliance MODULE-COMPLIANCE 1106 STATUS current 1107 DESCRIPTION 1108 "The compliance statement for SNMP entities which 1109 represent ATM interfaces. The compliance statements 1110 are used to determine if a particular group or object 1111 applies to hosts, networks/switches, or both." 1113 MODULE -- this module 1115 MANDATORY-GROUPS { atmLoopbackGroup } 1117 -- Objects in the ATM Loopback Test Group 1119 OBJECT atmLoopbackLocID 1120 MIN-ACCESS read-only 1121 DESCRIPTION 1122 "Write access is not required. This object is 1123 required for ATM systems supporting the 1124 atmLoopbackVpLocationID and atmLoopbackVcLocationID 1126 draft ATM Test Objects November 1996 1128 tests." 1130 OBJECT atmLoopbackSrcID 1131 MIN-ACCESS read-only 1132 DESCRIPTION 1133 "Write access is not required." 1135 OBJECT atmVplEndptSegmentEndPoint 1136 MIN-ACCESS read-only 1137 DESCRIPTION 1138 "Write access is not required. This object is 1139 mandatory for systems that are supporting ATM loopback 1140 tests." 1142 OBJECT atmVclEndptSegmentEndPoint 1143 MIN-ACCESS read-only 1144 DESCRIPTION 1145 "Write access is not required. This object is 1146 mandatory for systems that are supporting ATM loopback 1147 tests." 1149 ::= { atmTESTMIBCompliances 1 } 1151 -- ********************************************** 1153 -- Units of Conformance 1155 atmLoopbackGroup OBJECT-GROUP 1157 OBJECTS { 1158 atmLoopbackID, 1159 atmLoopbackLocID, 1160 atmLoopbackSrcID, 1161 atmVplEndptSegmentEndPoint, 1162 atmVclEndptSegmentEndPoint 1163 } 1164 STATUS current 1165 DESCRIPTION 1166 "A collection of objects providing information 1167 for Loopback Tests." 1168 ::= { atmTESTMIBGroups 1 } 1170 draft ATM Test Objects November 1996 1172 END 1173 draft ATM Test Objects November 1996 1175 7. Acknowledgments 1177 This document is a product of the AToMMIB Working Group. 1179 draft ATM Test Objects November 1996 1181 8. References 1183 [1] Kaj Tesink, "Definitions of Managed Objects for ATM 1184 Management", Internet-Draft, Bellcore, October 1996. 1186 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1187 and S. Waldbusser, "Structure of Management Information 1188 for version 2 of the Simple Network Management Protocol 1189 (SNMPv2)", RFC 1902, January 1996. 1191 [3] McCloghrie, K., and M. Rose, Editors, "Management 1192 Information Base for Network Management of TCP/IP-based 1193 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1194 Performance Systems International, March 1991. 1196 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1197 "Simple Network Management Protocol", RFC 1157, SNMP 1198 Research, Performance Systems International, Performance 1199 Systems International, MIT Laboratory for Computer 1200 Science, May 1990. 1202 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1203 and S. Waldbusser, "Protocol Operations for version 2 of 1204 the Simple Network Management Protocol (SNMPv2)", RFC 1205 1905, January 1996. 1207 [6] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1208 MIB", Internet-Draft, cisco Systems, FTP Software, 1209 February 1996. 1211 [7] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 1212 3.0) Specification, Part I", 1994. 1214 [8] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 1215 3.1) Specification, Part I", November 1994. 1217 [9] ITU-T Recommendation I.610, "Broadband Integrated Service 1218 Digital Network (B-ISDN) Operation and Maintenance 1219 Principles and Functions", July 1995. 1221 [10] McCloghrie, K., M. Greene, and K. Tesink, "Definitions of 1222 Managed Objects for System and Interface Testing", 1223 Internet-Draft, cisco Systems, Ascom Nexion, Bellcore, 1224 November 1996. 1226 draft ATM Test Objects November 1996 1228 9. Security Considerations 1230 Security issues are not discussed in this memo. 1232 10. Authors' Addresses 1234 Michael Noto 1235 Bell Communications Research 1236 Room 1E-348 1237 331 Newman Springs Road 1238 P.O. Box 7020 1239 Red Bank, NJ 07701-7020 1240 Phone: (908) 758-5104 1241 EMail: noto@cc.bellcore.com 1243 Kaj Tesink 1244 Bell Communications Research 1245 Room 1A-427 1246 331 Newman Springs Road 1247 P.O. Box 7020 1248 Red Bank, NJ 07701-7020 1249 Phone: (908) 758-5254 1250 EMail: kaj@cc.bellcore.com 1252 draft ATM Test Objects November 1996 1254 Table of Contents 1256 1 Status of this Memo ................................... 1 1257 2 Introduction .......................................... 2 1258 3 The SNMPv2 Network Management Framework ............... 2 1259 4 Object Definitions .................................... 3 1260 5 Overview .............................................. 3 1261 5.1 Background .......................................... 3 1262 5.2 Important Definitions ............................... 4 1263 5.3 Supported Functions ................................. 5 1264 5.3.1 ATM Testing Support ............................... 5 1265 5.3.1.1 ATM Loopback Testing Group ...................... 5 1266 5.3.1.2 ATM End-Point Group ............................. 9 1267 6 Definitions ........................................... 10 1268 7 Acknowledgments ....................................... 30 1269 8 References ............................................ 31 1270 9 Security Considerations ............................... 32 1271 10 Authors' Addresses ................................... 32