idnits 2.17.1 draft-ietf-atommib-test-03.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-23) 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 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 29 longer pages, the longest (page 2) being 117 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 31 pages 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 (June 1997) is 9809 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 1123 looks like a reference -- Missing reference section? '2' on line 1126 looks like a reference -- Missing reference section? '3' on line 1131 looks like a reference -- Missing reference section? '4' on line 1136 looks like a reference -- Missing reference section? '5' on line 1142 looks like a reference -- Missing reference section? '6' on line 1147 looks like a reference -- Missing reference section? '10' on line 1161 looks like a reference -- Missing reference section? '8' on line 1154 looks like a reference -- Missing reference section? '9' on line 1157 looks like a reference -- Missing reference section? '7' on line 1151 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 3 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Tests 3 for ATM Management 5 June 1997 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 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 June 1997 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 June 1997 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 June 1997 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 June 1997 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 June 1997 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 231 draft ATM Test Objects June 1997 233 The segment LB test is explained in ITU-T I.610[9]. For a VP 234 segment test, the LB cell is sent on the VP under test via 235 VCI=3 as specified in [8], and the Loopback Location ID field 236 is set to all 1's. For a VC segment test, the LB cell is sent 237 on the VC under test, with the PTI set to 4 as specified in 238 [8], and the Loopback Location ID field is set to all 1's. 240 This test involves a LB cell being inserted at a pre-defined 241 segment end-point, and looped back at the corresponding 242 segment end-point encountered. The pair of segment end-points 243 define a segment (which is used for the segment loopback 244 test). A VP/VC connection can have multiple segments, but 245 multiple segments cannot overlap. 247 A UNI interface is by definition defined as a segment end- 248 point (hence a UNI would be considered a segment). A segment 249 can also define: 250 - a B-ICI 251 - a public carrier's 'piece' of the connection 252 - a private network's 'piece' of the connection. 254 In order to support this functionality, the VP/VC link 255 termination needs to be able to be defined as a segment. This 256 can be done using either the atmVplSegmentEndPoint or 257 atmVclSegmentEndPoint object depending on whether it is for a 258 VPC or VCC. A segment loopback test is illustrated in Figure 259 4. 261 ____ _______ _______ _______ ____ 262 |Host| | | | | | | |Host| 263 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 264 |_______| |_______| |_______| 266 |<----------------------->| Segment 268 Figure 4: Segment Loopback Test 270 Section (8) describes the use of the ATM Segment Loopback 271 Tests. 273 3) Loopback Test Using Loopback Location Identifier 275 draft ATM Test Objects June 1997 277 This loopback test is a special type of 2) where the Loopback 278 Location ID field is set to a value that corresponds to a 279 specific node in a given network (Note that the format of this 280 field is not standardized, that is, the value is significant 281 only within an administrative domain). In this case, the 282 device initiating the LB test inserts the appropriate Loop 283 Back Location ID. When the LB cell reaches the corresponding 284 device, that device recognizes the Loopback Location ID as its 285 own, and loops it back. This test is useful for performing 286 fault sectionalization without having to provision segment 287 end-points. An additional object, the atmLoopbackID, is 288 defined to determine the loopback point. Figure 5 shows a 289 loopback test using a location identifier. Note that the 290 loopback test using location identifier can be used to perform 291 a loopback test over a portion of a defined segment. See 292 Figure 5. 294 ____ _______ _______ _______ ____ 295 |Host| | | | | | | |Host| 296 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 297 |_______| |_______| |_______| 299 |<---------->| Portion of Segment that 300 Loopback test is 301 performed on 303 |<----------------------->| Segment 305 Figure 5: Loopback Test Using Location Identifier 307 See Section (8) for more details. 309 4) Network Loopback Test 311 This is a loopback test that the manager requests an agent in 312 a network to perform over the internal portion of a designated 313 connection. The Network then initiates the internal network 314 loopback test by inserting an OAM loopback cell at one of the 315 end-points of the internal network portion of the connection. 316 When the loopback cell reaches the other end-point of the 317 internal Network , the cell is looped back. This test is 318 useful for verifying connectivity through a particular 319 network. Figure 6 illustrates the Network loopback test. 321 draft ATM Test Objects June 1997 323 ____ _______ _______ _______ ____ 324 |Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host| 325 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 326 |_______| |_______| |_______| 328 |<----------------------->| LB Test Path 329 thru Network 1 331 Figure 6: Network Loopback Test 333 See Section (8) for more details. 335 5.3.1.2. ATM End-Point Group 337 The ATM End-Point Group contains two tables: the ATM VP End- 338 point Table and the ATM VC End-point Table. The ATM VP End- 339 point Table augments the atmVplTable and provides the 340 atmVplEndptSegmentEndPoint object to represent whether or not 341 a specified VPL is a segment end-point. Similarly for Virtual 342 Channels, the ATM VC End-point Table and the 343 atmVclEndptSegmentEndPoint object are used to represent 344 whether or not a specified VCL is a segment end-point. 346 draft ATM Test Objects June 1997 348 6. Definitions 350 ATMTEST-MIB DEFINITIONS ::= BEGIN 352 IMPORTS 353 MODULE-IDENTITY, OBJECT-IDENTITY, 354 OBJECT-TYPE, mib-2, experimental 355 FROM SNMPv2-SMI 356 MODULE-COMPLIANCE, OBJECT-GROUP 357 FROM SNMPv2-CONF 358 atmVplEntry, atmVclEntry 359 FROM ATM-MIB; 361 atmTESTMIB MODULE-IDENTITY 362 LAST-UPDATED "9706031200Z" 363 ORGANIZATION "IETF AToMMIB Working Group" 364 CONTACT-INFO 365 " Michael Noto 366 Postal: Network Equipment Technologies 367 800 Saginaw Drive RM 21.1.111 368 Redwood City, CA 94063 369 Tel: +1 415 569-7134 370 E-mail: noto@net.com 372 Kaj Tesink 373 Postal: Bell Communications Research 374 331 Newman Springs Road 375 Red Bank, NJ 07701 376 US 377 Tel: +1 908 758 5254 378 Fax: +1 908 758 4177 379 E-mail: kaj@cc.bellcore.com" 380 DESCRIPTION 381 "This MIB Module provides 382 ATM Loopback Tests and supporting objects 383 that must be supported by ATM devices 384 providing ATM Loopback Tests." 385 ::= { experimental XX } 387 atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} 389 -- ******** NOTE TO THE RFC EDITOR ************** 391 draft ATM Test Objects June 1997 393 -- In case this module is put on the standards track 394 -- replace the following: 395 -- "atmTESTMIB MODULE-IDENTITY ::= {experimental XX}" with 396 -- "atmTESTMIB MODULE-IDENTITY ::= {mib-2 YY}" 397 -- and assign YY by IANA. 399 -- This ATMTEST-MIB Module consists of the following groups: 400 -- ATM Testing Support: 401 -- (1) ATM Loopback Testing Group 402 -- (2) ATM End-Point Group 404 draft ATM Test Objects June 1997 406 -- ************************************************ 407 -- (1) ATM Loopback Testing Group 409 -- This group contains information for interfaces 410 -- supporting ATM Loopback Tests 411 -- This group includes the following: 412 -- 1. ATM Loopback Objects 413 -- 2. List of ATM Loopback Test Types 415 atmLoopbackTestGroup OBJECT IDENTIFIER::= { 416 atmTESTMIBObjects 1} 418 -- 1. ATM Loopback Objects 419 -- The following objects are defined for use in 420 -- performing ATM Loopback Tests. 422 atmLoopbackID OBJECT-TYPE 423 SYNTAX OCTET STRING(SIZE(16)) 424 MAX-ACCESS read-write 425 STATUS current 426 DESCRIPTION 427 "This identifier is used to identify this local 428 ATM device. The value of this object can be used 429 by other ATM devices to identify this local ATM 430 device as the device that is being requested to 431 loopback the OAM Loopback cell. The default for 432 this field is all 1's, which would indicate a 433 segment OAM Loopback Test. Location Identifiers of 434 less than 16 octets are left justified, and padded 435 with all '0's." 436 DEFVAL { 'ffffffffffffffffffffffffffffffff'H } 437 ::= { atmLoopbackTestGroup 1 } 439 -- 2. List of ATM Loopback Test Types 440 -- The following loopback test types are defined: 441 -- atmLoopbackVpE2e 442 -- atmLoopbackVcE2e 443 -- atmLoopbackVpSegment 444 -- atmLoopbackVcSegment 445 -- atmLoopbackVpLocationID 446 -- atmLoopbackVcLocationID 447 -- atmLoopbackVpServcInternal 448 -- atmLoopbackVcServcInternal 450 draft ATM Test Objects June 1997 452 atmLoopbackTestTypes OBJECT IDENTIFIER ::= { 453 atmLoopbackTestGroup 4 } 455 atmLoopbackVpE2e OBJECT-IDENTITY 456 STATUS current 457 DESCRIPTION 458 "This is an end-to-end loopback test performed on a 459 designated VP (Virtual Path). To perform this test 460 an end-to-end loopback OAM cell is inserted at one 461 of the end-points of the designated VP connection 462 (e.g., at a host) via VCI=4 (the VCI value for VP 463 OAM end-to-end cells), travels to the other end- 464 point of the VP connection, and then loops back to 465 the originating end-point on the designated VP. 466 Success is achieved if the loopback OAM cell 467 returns to the originating end-point within 5 468 seconds, otherwise, the test fails. 470 The manager-station performs a loopback test by 471 making use of the testTable) defined in [10]. In 472 order to run this test the object 'testType' in the 473 testTable shall be set to atmLoopbackVpE2e, and the 474 object testTarget points to the row in the 475 atmVplTable in [1] corresponding to the VP 476 designated for the test. 478 Before starting a test, a manager-station must 479 first obtain 'ownership' of the entry in the 480 testTable for the interface to be tested (follow 481 procedure defined in [10]). Once the manager- 482 station obtains ownership, a loopback test for a 483 given interface can be invoked by first setting up 484 parameters necessary for the loopback test (e.g., 485 set the testTarget), and then setting the value of 486 'testType' in the testTable equal to 487 'atmLoopbackVpE2e'. This will cause the 488 atmLoopbackVpE2e test to be invoked on the VP with 489 the VPI corresponding to the testTarget. 491 After invoking a loopback test, wait for the test 492 completion by polling for the object 'testResult'. 493 A value of 'inProgress(3)' will result if the test 494 is still in progress. Once the test is completed, 495 the object 'testResult' will have a value of 497 draft ATM Test Objects June 1997 499 'success(2)' if the loopback OAM cell returned to 500 the originator of the test within 5 seconds, if 501 not, a value of 'failed(7)' will result. If the 502 ATM system does not support this type of loopback 503 test, then a value of 'notSupported(4)' will be 504 provided. Other possible values for the 505 'testResult' object are 'unAbleToRun(5)' and 506 'aborted(6)'." 507 ::= { atmLoopbackTestTypes 1 } 509 atmLoopbackVcE2e OBJECT-IDENTITY 510 STATUS current 511 DESCRIPTION 512 "This is an end-to-end loopback test performed on a 513 designated VC (Virtual Channel). To perform this 514 test an end-to-end loopback OAM cell is inserted at 515 one of the end-points of the designated VC 516 connection (e.g., at a host) via PTI=5 (the PTI 517 value used for VC OAM end-to-end cells), travels to 518 the other end-point of the VC connection, and then 519 loops back to the originating end-point on the 520 designated VC. Success is achieved if the loopback 521 OAM cell returns to the originating end-point within 522 5 seconds, otherwise, the test fails. 524 The manager-station performs a loopback test by 525 making use of the testTable) defined in [10]. In 526 order to run this test the object 'testType' in the 527 testTable shall be set to atmLoopbackVcE2e, and the 528 object testTarget points to the row in the 529 atmVclTable in [1] corresponding to the VC 530 designated for the test. 532 Before starting a test, a manager-station must first 533 obtain 'ownership' of the entry in the testTable for 534 the interface to be tested (follow procedure defined 535 in [10]). Once the manager-station obtains 536 ownership, a loopback test for a given interface can 537 be invoked by first setting up parameters necessary 538 for the loopback test (e.g., set the testTarget), 539 and then setting the value of 'testType' in the 540 testTable equal to 'atmLoopbackVcE2e'. This will 541 cause the atmLoopbackVcE2e test to be invoked on the 542 VC with the VPI/VCI corresponding to the testTarget. 544 draft ATM Test Objects June 1997 546 After invoking a loopback test, wait for the test 547 completion by polling for the object 'testResult'. 548 A value of 'inProgress(3)' will result if the test 549 is still in progress. Once the test is completed, 550 the object 'testResult' will have a value of 551 'success(2)' if the loopback OAM cell returned to 552 the originator of the test within 5 seconds, if not, 553 a value of 'failed(7)' will result. If the ATM 554 system does not support this type of loopback test, 555 then a value of 'notSupported(4)' will be provided. 556 Other possible values for the 'testResult' object 557 are 'unAbleToRun(5)' and 'aborted(6)'." 558 ::= { atmLoopbackTestTypes 2 } 560 atmLoopbackVpSegment OBJECT-IDENTITY 561 STATUS current 562 DESCRIPTION 563 "This is a loopback test performed on a designated 564 segment of a VP (Virtual Path). To perform this test 565 a segment OAM cell is inserted at one of the segment 566 end-points of the designated VP connection (e.g., at 567 a host) via VCI=3 (the VCI used for VP OAM segment 568 cells), travels across the segment on the designated 569 VP to the device pre-configured as the corresponding 570 segment end-point, and then loops back to the 571 originating segment end-point on the designated VP. 572 Success is achieved if the loopback OAM cell returns 573 to the originating end-point within 5 seconds, 574 otherwise, the test fails. 576 In order to use the atmLoopbackVpSegment test, a 577 segment must be defined by setting up segment end- 578 points using the atmVplEndptSegmentEndPoint object 579 from the atmVplEndptTable. The 580 atmVplEndptSegmentEndPoint is set to 581 isaVpSegmentEndPoint(1) for each segment end-point. 582 Note that this object is by default set to 583 isaVpSegmentEndPoint(1) if the atmVplTable supports 584 one end of a UNI. In such a case, a UNI VP loopback 585 test would be achieved when the atmLoopbackVpSegment 586 test was initiated over the UNI. 588 The manager-station performs a loopback test by 589 making use of the testTable) defined in [10]. In 591 draft ATM Test Objects June 1997 593 order to run this test the object 'testType' in the 594 testTable shall be set to atmLoopbackVpE2e, and the 595 object testTarget points to the row in the 596 atmVplTable in [1] corresponding to the VP designated 597 for the test. 599 Before starting a test, a manager-station must first 600 obtain 'ownership' of the entry in the testTable for 601 the interface to be tested (follow procedure defined 602 in [10]). Once the manager-station obtains 603 ownership, a loopback test for a given interface can 604 be invoked by first setting up parameters necessary 605 for the loopback test (e.g., set the testTarget), and 606 then setting the value of 'testType' in the testTable 607 equal to 'atmLoopbackVpSegment'. This will cause the 608 atmLoopbackVpSegment test to be invoked on the VP 609 with the VPI corresponding to the testTarget. 611 After invoking a loopback test, wait for the test 612 completion by polling for the object 'testResult'. A 613 value of 'inProgress(3)' will result if the test is 614 still in progress. Once the test is completed, the 615 object 'testResult' will have a value of 'success(2)' 616 if the loopback OAM cell returned to the originator 617 of the test within 5 seconds, if not, a value of 618 'failed(7)' will result. If the ATM system does not 619 support this type of loopback test, then a value of 620 'notSupported(4)' will be provided. Other possible 621 values for the 'testResult' object are 622 'unAbleToRun(5)' and 'aborted(6)'." 623 ::= { atmLoopbackTestTypes 3 } 625 atmLoopbackVcSegment OBJECT-IDENTITY 626 STATUS current 627 DESCRIPTION 628 "This is a loopback test performed on a designated 629 segment of a VC (Virtual Channel). To perform this 630 test a segment OAM cell is inserted at one of the 631 segment end-points of the designated VC connection 632 (e.g., at a host) via PTI=4 (the PTI value used for VC 633 OAM segment cells), travels across the segment on the 634 designated VC to the device pre-configured as the 635 corresponding segment end-point, and then loops back 636 to the originating segment end-point on the designated 638 draft ATM Test Objects June 1997 640 VC. Success is achieved if the loopback OAM cell 641 returns to the originating end-point within 5 seconds, 642 otherwise, the test fails. 644 In order to use the atmLoopbackVcSegment test, a 645 segment must be defined by setting up segment end- 646 points using the atmVclEndptSegmentEndPoint object 647 from the atmVclEndptTable. The 648 atmVclEndptSegmentEndPoint is set to 649 isaVcSegmentEndPoint(1) for each segment end-point. 650 Note that this object is by default set to 651 isaVcSegmentEndPoint(1) if the atmVclTable supports 652 one end of a UNI. In such a case, a UNI VC loopback 653 test would be achieved when the atmLoopbackVcSegment 654 test was initiated over the UNI. 656 The manager-station performs a loopback test by making 657 use of the testTable) defined in [10]. In order to 658 run this test the object 'testType' in the testTable 659 shall be set to atmLoopbackVcE2e, and the object 660 testTarget points to the row in the atmVclTable in [1] 661 corresponding to the VC designated for the test. 663 Before starting a test, a manager-station must first 664 obtain 'ownership' of the entry in the testTable for 665 the interface to be tested (follow procedure defined 666 in [10]). Once the manager-station obtains ownership, 667 a loopback test for a given interface can be invoked 668 by first setting up parameters necessary for the 669 loopback test (e.g., set the testTarget), and then 670 setting the value of 'testType' in the testTable equal 671 to 'atmLoopbackVcSegment'. This will cause the 672 atmLoopbackVcSegment test to be invoked on the VC with 673 the VPI/VCI corresponding to the testTarget. 675 After invoking a loopback test, wait for the test 676 completion by polling for the object 'testResult'. A 677 value of 'inProgress(3)' will result if the test is 678 still in progress. Once the test is completed, the 679 object 'testResult' will have a value of 'success(2)' 680 if the loopback OAM cell returned to the originator of 681 the test within 5 seconds, if not, a value of 682 'failed(7)' will result. If the ATM system does not 683 support this type of loopback test, then a value of 684 'notSupported(4)' will be provided. Other possible 686 draft ATM Test Objects June 1997 688 values for the 'testResult' object are 689 'unAbleToRun(5)' and 'aborted(6)'." 690 ::= { atmLoopbackTestTypes 4 } 692 atmLoopbackVpLocationId OBJECT-IDENTITY 693 STATUS current 694 DESCRIPTION 695 "This is a loopback test performed on a portion of a 696 designated VP segment. To perform this test a loopback 697 OAM cell is inserted at a connection point of the 698 designated VP connection (e.g., the end-point or a 699 tandem point) with a value inserted in the Location 700 Identifier ID field of the OAM cell that corresponds to 701 the ATM device where the cell is to be looped back. 702 The loopback cell then travels through the VP 703 connection until it reaches the designated ATM device, 704 where it is looped back to the loopback cell insertion 705 point on the designated VP. Success is achieved if the 706 loopback OAM cell returns to the originating point of 707 insertion within 5 seconds, otherwise, the test fails. 709 The manager-station performs a loopback test by making 710 use of the testTable) defined in [10]. In order to run 711 this test the object 'testType' in the testTable shall 712 be set to atmLoopbackVpE2e. The object testTarget 713 points to the row in the atmVplTable in [1] 714 corresponding to the VP designated for the test. The 715 object testMoreInfo contains the desired Loopback 716 Location ID. 718 Before starting a test, a manager-station must first 719 obtain 'ownership' of the entry in the testTable for 720 the interface to be tested (follow procedure defined in 721 [10]). Once the manager-station obtains ownership, a 722 loopback test for a given interface can be invoked by 723 first setting up parameters necessary for the loopback 724 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 725 set the testTarget), and then setting the value of 726 'testType' in the testTable equal to 727 'atmLoopbackVpSegment'. This will cause the 728 atmLoopbackVpLocationId test to be invoked on the VP 729 with the VPI corresponding to the testTarget and looped 730 back at loopback location ID= AAAABBBBCCCCDDDD. 732 draft ATM Test Objects June 1997 734 After invoking a loopback test, wait for the test 735 completion by polling for the object 'testResult'. A 736 value of 'inProgress(3)' will result if the test is 737 still in progress. Once the test is completed, the 738 object 'testResult' will have a value of 'success(2)' 739 if the loopback OAM cell returned to the originator of 740 the test within 5 seconds, if not, a value of 741 'failed(7)' will result. If the ATM system does not 742 support this type of loopback test, then a value of 743 'notSupported(4)' will be provided. Other possible 744 values for the 'testResult' object are 'unAbleToRun(5)' 745 and 'aborted(6)'." 746 ::= { atmLoopbackTestTypes 5 } 748 atmLoopbackVcLocationId OBJECT-IDENTITY 749 STATUS current 750 DESCRIPTION 751 "This is a loopback test performed on a portion of a 752 designated Vc segment. To perform this test a loopback 753 OAM cell is inserted at a connection point of the 754 designated VC connection (e.g., the end-point or a 755 tandem point) with a value inserted in the Location 756 Identifier ID field of the OAM cell that corresponds to 757 the ATM device where the cell is to be looped back. 758 The loopback cell then travels through the VC 759 connection until it reaches the designated ATM device, 760 where it is looped back to the loopback cell insertion 761 point on the designated VC. Success is achieved if the 762 loopback OAM cell returns to the originating point of 763 insertion within 5 seconds, otherwise, the test fails. 765 The manager-station performs a loopback test by making 766 use of the testTable) defined in [10]. In order to run 767 this test the object 'testType' in the testTable shall 768 be set to atmLoopbackVcE2e. The object testTarget 769 points to the row in the atmVclTable in [1] 770 corresponding to the VC designated for the test. The 771 object testMoreInfo contains the desired Loopback 772 Location ID. 774 Before starting a test, a manager-station must first 775 obtain 'ownership' of the entry in the testTable for 776 the interface to be tested (follow procedure defined in 777 [10]). Once the manager-station obtains ownership, a 779 draft ATM Test Objects June 1997 781 loopback test for a given interface can be invoked by 782 first setting up parameters necessary for the loopback 783 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 784 set the testTarget), and then setting the value of 785 'testType' in the testTable equal to 786 'atmLoopbackVcSegment.d'. This will cause the 787 atmLoopbackVcLocationId test to be invoked on the VC 788 with the VPI/VCI corresponding to the testTarget and 789 looped back at loopback location ID= AAAABBBBCCCCDDDD. 791 After invoking a loopback test, wait for the test 792 completion by polling for the object 'testResult'. A 793 value of 'inProgress(3)' will result if the test is 794 still in progress. Once the test is completed, the 795 object 'testResult' will have a value of 'success(2)' 796 if the loopback OAM cell returned to the originator of 797 the test within 5 seconds, if not, a value of 798 'failed(7)' will result. If the ATM system does not 799 support this type of loopback test, then a value of 800 'notSupported(4)' will be provided. Other possible 801 values for the 'testResult' object are 'unAbleToRun(5)' 802 and 'aborted(6)'." 803 ::= { atmLoopbackTestTypes 6 } 805 atmLoopbackVpServcInternal OBJECT-IDENTITY 806 STATUS current 807 DESCRIPTION 808 "This is a loopback test that the manager requests an 809 agent to perform over the managed resource's internal 810 portion of a designated VP (i.e., between the ingress 811 and egress interfaces of the VP connection). The agent 812 is provided with the Ingress VPI, Egress Interface, and 813 Egress VPI in order to run this internal test. This 814 test may be useful in proxy situations where the proxy 815 agent represents a network. Implementations of this 816 test may be specific to the managed resource. One 817 implementation in a managed network may be as follows, 818 the managed network inserts a segment loopback OAM cell 819 at the network internal segment end-point 820 (corresponding to the ingress connection point) for the 821 designated VP connection. The loopback cell then 822 travels through the network's portion of the VP 823 connection until it reaches the networks connection 824 point to the egress, where it is looped back to the 825 network's cell insertion point on the designated VP. 827 draft ATM Test Objects June 1997 829 Success is achieved if the loopback OAM cell returns to 830 the originating internal network segment end-point 831 within 5 seconds, otherwise, the test fails. 833 The manager-station performs a loopback test by making 834 use of the testTable) defined in [10]. In order to run 835 this test the object 'testType' in the testTable shall 836 be set to atmLoopbackVpServcInternal, and the object 837 testTarget points to the row in the 838 atmVpCrossConnectTable in [1] corresponding to the VP 839 designated for the test. 841 Before starting a test, a manager-station must first 842 obtain 'ownership' of the entry in the testTable for 843 the interface to be tested (follow procedure defined in 844 [10]). Once the manager-station obtains ownership, a 845 loopback test for a given interface can be invoked by 846 first setting up parameters necessary for the loopback 847 test (e.g., set the testTarget), and then setting the 848 value of 'testType' in the testTable equal to 849 'atmLoopbackVpServcInternal'. This will cause the 850 atmLoopbackVpServcInternal test to be invoked on the VP 851 crossconnect with the ingress and egress VPI values 852 corresponding to the testTarget. 854 After invoking a loopback test, wait for the test 855 completion by polling for the object 'testResult'. A 856 value of 'inProgress(3)' will result if the test is 857 still in progress. Once the test is completed, the 858 object 'testResult' will have a value of 'success(2)' 859 if the loopback OAM cell returned to the originator of 860 the test within 5 seconds, if not, a value of 861 'failed(7)' will result. If the ATM system does not 862 support this type of loopback test, then a value of 863 'notSupported(4)' will be provided. Other possible 864 values for the 'testResult' object are 'unAbleToRun(5)' 865 and 'aborted(6)'." 866 ::= { atmLoopbackTestTypes 7 } 868 atmLoopbackVcServcInternal OBJECT-IDENTITY 869 STATUS current 870 DESCRIPTION 871 "This is a loopback test that the manager requests an 872 agent to perform over the managed resource's internal 873 portion of a designated VC (i.e., between the ingress 875 draft ATM Test Objects June 1997 877 and egress interfaces of the VC connection). The agent 878 is provided with the Ingress VPI, Ingress VCI, Egress 879 Interface, Egress VPI, and Egress VCI in order to run 880 this internal test. This test may be useful in proxy 881 situations where the proxy agent represents a network. 882 Implementations of this test may be specific to the 883 managed resource. One implemenation in a managed 884 network may be as follows, the managed network inserts 885 a segment loopback OAM cell at the network internal 886 segment end-point (corresponding to the ingress 887 connection point) for the designated VC connection. 888 The loopback cell then travels through the network's 889 portion of the VC connection until it reaches the 890 networks connection point to the egress, where it is 891 looped back to the network's cell insertion point on 892 the designated VC. Success is achieved if the loopback 893 OAM cell returns to the originating internal network 894 segment end-point within 5 seconds, otherwise, the test 895 fails. 897 The manager-station performs a loopback test by making 898 use of the testTable) defined in [10]. In order to run 899 this test the object 'testType' in the testTable shall 900 be set to atmLoopbackVcServcInternal, and the object 901 testTarget points to the row in the 902 atmVcCrossConnectTable in [1] corresponding to the VC 903 designated for the test. 905 Before starting a test, a manager-station must first 906 obtain 'ownership' of the entry in the testTable for 907 the interface to be tested (follow procedure defined in 908 [10]). Once the manager-station obtains ownership, a 909 loopback test for a given interface can be invoked by 910 first setting up parameters necessary for the loopback 911 test (e.g., set the testTarget), and then setting the 912 value of 'testType' in the testTable equal to 913 'atmLoopbackVcServcInternal'. This will cause the 914 atmLoopbackVcServcInternal test to be invoked on the VC 915 crossconnect with the ingress and egress VPI/VCI values 916 corresponding to the testTarget. 918 After invoking a loopback test, wait for the test 919 completion by polling for the object 'testResult'. A 920 value of 'inProgress(3)' will result if the test is 921 still in progress. Once the test is completed, the 923 draft ATM Test Objects June 1997 925 object 'testResult' will have a value of 'success(2)' 926 if the loopback OAM cell returned to the originator of 927 the test within 5 seconds, if not, a value of 928 'failed(7)' will result. If the ATM system does not 929 support this type of loopback test, then a value of 930 'notSupported(4)' will be provided. Other possible 931 values for the 'testResult' object are 'unAbleToRun(5)' 932 and 'aborted(6)'." 933 ::= { atmLoopbackTestTypes 8 } 935 draft ATM Test Objects June 1997 937 -- ************************************************ 938 -- (2) ATM End-Point Group 940 -- This group contains information for interfaces 941 -- supporting ATM Loopback Tests 942 -- This group includes the following: 943 -- 1. ATM VP End-Point Table 944 -- 2. ATM VC End-Point Table 946 atmEndptGroup OBJECT IDENTIFIER::= { 947 atmTESTMIBObjects 2} 949 -- 1. ATM VP End-Point Table 951 atmVplEndptTable OBJECT-TYPE 952 SYNTAX SEQUENCE OF AtmVplEndptEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "End-point Information for each VP." 957 ::= { atmEndptGroup 1 } 959 atmVplEndptEntry OBJECT-TYPE 960 SYNTAX AtmVplEndptEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "An entry with end-point information about the ATM 965 VP." 966 AUGMENTS { atmVplEntry } 967 ::= { atmVplEndptTable 1 } 969 AtmVplEndptEntry ::= 970 SEQUENCE { 971 atmVplEndptSegmentEndPoint INTEGER 972 } 974 atmVplEndptSegmentEndPoint OBJECT-TYPE 975 SYNTAX INTEGER { 976 isaVplSegmentEndPoint(1), 977 notaVplSegmentEndPoint(2) 979 draft ATM Test Objects June 1997 981 } 982 MAX-ACCESS read-create 983 STATUS current 984 DESCRIPTION 985 "An indication of whether or not the VP interface 986 has been configured to represent a VPC Segment 987 End-Point. If the corresponding VP Link is a UNI, 988 the value of this object is permanently set to 1 989 (isaVplSegmentEndPoint). Otherwise, the default is 990 set to 2 (notaVplSegmentEndPoint)." 991 ::= { atmVplEndptEntry 1 } 993 -- 2. ATM VC End-Point Table 995 atmVclEndptTable OBJECT-TYPE 996 SYNTAX SEQUENCE OF AtmVclEndptEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "End-point Information for each VC." 1001 ::= { atmEndptGroup 2 } 1003 atmVclEndptEntry OBJECT-TYPE 1004 SYNTAX AtmVclEndptEntry 1005 MAX-ACCESS not-accessible 1006 STATUS current 1007 DESCRIPTION 1008 "An entry with end-point information about the ATM 1009 VC." 1010 AUGMENTS { atmVclEntry } 1011 ::= { atmVclEndptTable 1 } 1013 AtmVclEndptEntry ::= 1014 SEQUENCE { 1015 atmVclEndptSegmentEndPoint INTEGER 1016 } 1018 atmVclEndptSegmentEndPoint OBJECT-TYPE 1019 SYNTAX INTEGER { 1020 isaVclSegmentEndPoint(1), 1021 notaVclSegmentEndPoint(2) 1022 } 1024 draft ATM Test Objects June 1997 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "An indication of whether or not the VC interface 1030 has been configured to represent a VCC Segment 1031 End-Point. If the corresponding VC Link is a UNI, 1032 the value of this object is permanently set to 1 1033 (isaVclSegmentEndPoint). Otherwise, the default is 1034 set to 2 (notaVclSegmentEndPoint)." 1035 ::= { atmVclEndptEntry 1 } 1037 -- ************************************************ 1039 -- Conformance Information 1041 atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} 1043 atmTESTMIBGroups OBJECT IDENTIFIER 1044 ::= {atmTESTMIBConformance 1} 1046 atmTESTMIBCompliances OBJECT IDENTIFIER 1047 ::= {atmTESTMIBConformance 2} 1049 -- Compliance Statements 1051 atmTESTMIBCompliance MODULE-COMPLIANCE 1052 STATUS current 1053 DESCRIPTION 1054 "The compliance statement for SNMP entities which 1055 represent ATM interfaces. The compliance statements 1056 are used to determine if a particular group or object 1057 applies to hosts, networks/switches, or both." 1059 MODULE -- this module 1061 MANDATORY-GROUPS { atmLoopbackGroup } 1063 -- Objects in the ATM Loopback Test Group 1065 OBJECT atmLoopbackID 1066 MIN-ACCESS read-only 1067 DESCRIPTION 1068 "Write access is not required. This object is 1069 required for ATM systems supporting the 1070 atmLoopbackVpLocationID and atmLoopbackVcLocationID 1072 draft ATM Test Objects June 1997 1074 tests." 1076 OBJECT atmVplEndptSegmentEndPoint 1077 MIN-ACCESS read-only 1078 DESCRIPTION 1079 "Write access is not required. This object is 1080 mandatory for systems that are supporting ATM loopback 1081 tests." 1083 OBJECT atmVclEndptSegmentEndPoint 1084 MIN-ACCESS read-only 1085 DESCRIPTION 1086 "Write access is not required. This object is 1087 mandatory for systems that are supporting ATM loopback 1088 tests." 1090 ::= { atmTESTMIBCompliances 1 } 1092 -- ********************************************** 1094 -- Units of Conformance 1096 atmLoopbackGroup OBJECT-GROUP 1098 OBJECTS { 1099 atmLoopbackID, 1100 atmVplEndptSegmentEndPoint, 1101 atmVclEndptSegmentEndPoint 1102 } 1103 STATUS current 1104 DESCRIPTION 1105 "A collection of objects providing information 1106 for Loopback Tests." 1107 ::= { atmTESTMIBGroups 1 } 1109 END 1111 draft ATM Test Objects June 1997 1113 7. Acknowledgments 1115 This document is a product of the AToMMIB Working Group. The 1116 authors would like to acknowledge Dawn Xie for her valuable 1117 suggestions for this memo. 1119 draft ATM Test Objects June 1997 1121 8. References 1123 [1] Kaj Tesink, "Definitions of Managed Objects for ATM 1124 Management", Internet-Draft, Bellcore, October 1996. 1126 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1127 and S. Waldbusser, "Structure of Management Information 1128 for version 2 of the Simple Network Management Protocol 1129 (SNMPv2)", RFC 1902, January 1996. 1131 [3] McCloghrie, K., and M. Rose, Editors, "Management 1132 Information Base for Network Management of TCP/IP-based 1133 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1134 Performance Systems International, March 1991. 1136 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1137 "Simple Network Management Protocol", RFC 1157, SNMP 1138 Research, Performance Systems International, Performance 1139 Systems International, MIT Laboratory for Computer 1140 Science, May 1990. 1142 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1143 and S. Waldbusser, "Protocol Operations for version 2 of 1144 the Simple Network Management Protocol (SNMPv2)", RFC 1145 1905, January 1996. 1147 [6] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1148 MIB", Internet-Draft, cisco Systems, FTP Software, 1149 February 1996. 1151 [7] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 1152 3.0) Specification, Part I", 1994. 1154 [8] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 1155 3.1) Specification, Part I", November 1994. 1157 [9] ITU-T Recommendation I.610, "Broadband Integrated Service 1158 Digital Network (B-ISDN) Operation and Maintenance 1159 Principles and Functions", July 1995. 1161 [10] McCloghrie, K., M. Greene, and K. Tesink, "Definitions of 1162 Managed Objects for System and Interface Testing", 1163 Internet-Draft, cisco Systems, Ascom Nexion, Bellcore, 1164 November 1996. 1166 draft ATM Test Objects June 1997 1168 9. Security Considerations 1170 Security issues are not discussed in this memo. 1172 10. Authors' Addresses 1174 Michael Noto 1175 Network Equipment Technologies 1176 800 Saginaw Drive RM 21.1.111 1177 Redwood City, CA 94063 1178 Phone +1 415 569-7134 1179 EMail: mike_noto@net.com 1181 Kaj Tesink 1182 Bell Communications Research 1183 331 Newman Springs Road 1184 P.O. Box 7020 1185 Red Bank, NJ 07701-7020 1186 Phone: (908) 758-5254 1187 EMail: kaj@cc.bellcore.com 1189 draft ATM Test Objects June 1997 1191 Table of Contents 1193 1 Status of this Memo ................................... 1 1194 2 Introduction .......................................... 2 1195 3 The SNMPv2 Network Management Framework ............... 2 1196 4 Object Definitions .................................... 3 1197 5 Overview .............................................. 3 1198 5.1 Background .......................................... 3 1199 5.2 Important Definitions ............................... 4 1200 5.3 Supported Functions ................................. 5 1201 5.3.1 ATM Testing Support ............................... 5 1202 5.3.1.1 ATM Loopback Testing Group ...................... 5 1203 5.3.1.2 ATM End-Point Group ............................. 9 1204 6 Definitions ........................................... 10 1205 7 Acknowledgments ....................................... 28 1206 8 References ............................................ 29 1207 9 Security Considerations ............................... 30 1208 10 Authors' Addresses ................................... 30