-- extracted from draft-ietf-atommib-test-06.txt -- at Thu Dec 9 07:06:58 1999 ATMTEST-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF atmVplEntry, atmVclEntry, atmInterfaceConfEntry FROM ATM-MIB; atmTESTMIB MODULE-IDENTITY LAST-UPDATED "9911281200Z" ORGANIZATION "IETF AToMMIB Working Group" CONTACT-INFO " Michael Noto Postal: 3Com Corporation 5400 Bayfront Plaza Santa Clara, CA 95052 USA Tel: +1 408 326 2218 E-mail: mike_noto@3com.com Kaj Tesink Postal: Telcordia Technologies 331 Newman Springs Road Red Bank, NJ 07701 USA Tel: +1 732 758 5254 Fax: +1 732 758 2269 E-mail: kaj@research.telcordia.com" DESCRIPTION "This MIB Module provides ATM Loopback Tests and supporting objects that must be supported by ATM devices providing ATM Loopback Tests." REVISION "9911281200Z" DESCRIPTION "Initial version, published as RFCxxxx" ::= { mib-2 XX } -- ******** NOTE TO THE RFC EDITOR / IANA *********** -- * Before this module is put on the standards track -- * fill out RFCxxxx with the RFC number of this document -- * assign XX by IANA. -- * remove this notice from the MIB atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} -- This ATMTEST-MIB Module consists of the following: -- (1) ATM Loopback Testing -- (2) ATM End-Point Tables -- ************************************************ -- (1) ATM Loopback Testing -- This concerns information for interfaces -- supporting ATM Loopback Tests and includes: -- 1. ATM Loopback Objects -- 2. List of ATM Loopback Test Types atmLoopbackTestGroup OBJECT IDENTIFIER ::= { atmTESTMIBObjects 1} -- 1. ATM Loopback Objects -- The following objects are defined for use in -- performing ATM Loopback Tests. atmInterfaceLLIDTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmInterfaceLLIDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Logical Loopback Identifiers (LLID) for ATM interfaces" ::= { atmLoopbackTestGroup 1 } atmInterfaceLLIDEntry OBJECT-TYPE SYNTAX AtmInterfaceLLIDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmInterfaceLLIDTable." AUGMENTS { atmInterfaceConfEntry } ::= { atmInterfaceLLIDTable 1 } AtmInterfaceLLIDEntry ::= SEQUENCE { atmIfLogicalLoopbackId OCTET STRING } atmIfLogicalLoopbackId OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0|16)) MAX-ACCESS read-write STATUS current DESCRIPTION "This identifier is used to identify this local ATM interface for loopback.The value of this object can be used by other ATM devices to identify this local ATM interface as the interface that is being requested to loopback OAM Loopback cells. The default for this field is the zero length string which signifies that loopback at this interface is disabled. To enable loopback set the value to a 16 byte fixed length octet string. Non-zero length identifiers of less than 16 octets signify that loopback checking is enabled and are left justified, and padded with all 0's." DEFVAL {''H } REFERENCE "ITU-T Recommendation I.610, Broadband Integrated Service Digital Network (B-ISDN) Operation and Maintenance Principles and Functions, July 1995" ::= { atmInterfaceLLIDEntry 1 } -- 2. List of ATM Loopback Test Types -- The following loopback test types are defined: -- atmLoopbackVpE2e -- atmLoopbackVcE2e -- atmLoopbackVpSegment -- atmLoopbackVcSegment -- atmLoopbackVpLocationID -- atmLoopbackVcLocationID -- atmLoopbackVpServiceInternal -- atmLoopbackVcServiceInternal atmLoopbackTestTypes OBJECT IDENTIFIER ::= { atmLoopbackTestGroup 4 } atmLoopbackVpE2e OBJECT-IDENTITY STATUS current DESCRIPTION "This is an end-to-end loopback test performed on a designated VP (Virtual Path). To perform this test an end-to-end loopback OAM cell is inserted at one of the end-points of the designated VP connection (e.g., at a host) via VCI=4 (the VCI value for VP OAM end-to-end cells), travels to the other end-point of the VP connection, and then loops back to the originating end-point on the designated VP. Success is achieved if the loopback OAM cell returns to the originating end-point within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVpE2e, and the object testTarget points to the row in the atmVplTable in [TestMIB] corresponding to the VP designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVpE2e'. The testRowStatus is used to invoke the atmLoopbackVpE2e test on the VP with the VPI corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 1 } atmLoopbackVcE2e OBJECT-IDENTITY STATUS current DESCRIPTION "This is an end-to-end loopback test performed on a designated VC (Virtual Channel). To perform this test an end-to-end loopback OAM cell is inserted at one of the end-points of the designated VC connection (e.g., at a host) via PTI=5 (the PTI value used for VC OAM end-to-end cells), travels to the other end-point of the VC connection, and then loops back to the originating end-point on the designated VC. Success is achieved if the loopback OAM cell returns to the originating end-point within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVcE2e, and the object testTarget points to the row in the atmVclTable in [RFC2515] corresponding to the VC designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVcE2e'. The testRowStatus is used to invoke the atmLoopbackVcE2e test on the VC with the VPI/VCI corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 2 } atmLoopbackVpSegment OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test performed on a designated segment of a VP (Virtual Path). To perform this test a segment OAM cell is inserted at one of the segment end-points of the designated VP connection (e.g., at a host) via VCI=3 (the VCI used for VP OAM segment cells), travels across the segment on the designated VP to the device pre-configured as the corresponding segment end-point, and then loops back to the originating segment end-point on the designated VP. Success is achieved if the loopback OAM cell returns to the originating end-point within 5 seconds, otherwise, the test fails. In order to use the atmLoopbackVpSegment test, a segment must be defined by setting up segment end- points using the atmVplEndptSegmentEndPoint object from the atmVplEndptTable. The atmVplEndptSegmentEndPoint is set to 'isaVpSegmentEndPoint(1)' for each segment end-point. Note that this object is by default set to 'isaVpSegmentEndPoint(1)' if the atmVplTable supports one end of a UNI. In such a case, a UNI VP loopback test would be achieved when the atmLoopbackVpSegment test was initiated over the UNI. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVpE2e, and the object testTarget points to the row in the atmVplTable in [RFC2515] corresponding to the VP designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVpSegment'. The testRowStatus is used to invoke the atmLoopbackVpSegment test on the VP with the VPI corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 3 } atmLoopbackVcSegment OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test performed on a designated segment of a VC (Virtual Channel). To perform this test a segment OAM cell is inserted at one of the segment end-points of the designated VC connection (e.g., at a host) via PTI=4 (the PTI value used for VC OAM segment cells), travels across the segment on the designated VC to the device pre-configured as the corresponding segment end-point, and then loops back to the originating segment end-point on the designated VC. Success is achieved if the loopback OAM cell returns to the originating end-point within 5 seconds, otherwise, the test fails. In order to use the atmLoopbackVcSegment test, a segment must be defined by setting up segment end- points using the atmVclEndptSegmentEndPoint object from the atmVclEndptTable. The atmVclEndptSegmentEndPoint is set to 'isaVcSegmentEndPoint(1)' for each segment end-point. Note that this object is by default set to 'isaVcSegmentEndPoint(1)' if the atmVclTable supports one end of a UNI. In such a case, a UNI VC loopback test would be achieved when the atmLoopbackVcSegment test was initiated over the UNI. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVcE2e, and the object testTarget points to the row in the atmVclTable in [RFC2515] corresponding to the VC designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVcSegment'. The testRowStatus is used to invoke the atmLoopbackVcSegment test on the VC with the VPI/VCI corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 4 } atmLoopbackVpLocationId OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test performed on a portion of a designated VP segment. To perform this test a loopback OAM cell is inserted at a connection point of the designated VP connection (e.g., the end-point or a tandem point) with a value inserted in the Location Identifier ID field of the OAM cell that corresponds to the ATM device where the cell is to be looped back. The loopback cell then travels through the VP connection until it reaches the designated ATM device, where it is looped back to the loopback cell insertion point on the designated VP. Success is achieved if the loopback OAM cell returns to the originating point of insertion within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVpE2e. The object testTarget points to the row in the atmVplTable in [RFC2515] corresponding to the VP designated for the test. The object testMoreInfo contains the desired Loopback Location ID. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVpSegment'. The testRowStatus is used to invoke the atmLoopbackVpLocationId on the VP with the VPI corresponding to the testTarget and looped back at loopback location ID= AAAABBBBCCCCDDDD. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 5 } atmLoopbackVcLocationId OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test performed on a portion of a designated Vc segment. To perform this test a loopback OAM cell is inserted at a connection point of the designated VC connection (e.g., the end-point or a tandem point) with a value inserted in the Location Identifier ID field of the OAM cell that corresponds to the ATM device where the cell is to be looped back. The loopback cell then travels through the VC connection until it reaches the designated ATM device, where it is looped back to the loopback cell insertion point on the designated VC. Success is achieved if the loopback OAM cell returns to the originating point of insertion within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVcE2e. The object testTarget points to the row in the atmVclTable in [RFC2515] corresponding to the VC designated for the test. The object testMoreInfo contains the desired Loopback Location ID. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVcSegment.d'. The testRowStatus is used to invoke the atmLoopbackVcLocationId test on the VC with the VPI/VCI corresponding to the testTarget and looped back at loopback location ID= AAAABBBBCCCCDDDD. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 6 } atmLoopbackVpServiceInternal OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test that the manager requests an agent to perform over the managed resource's internal portion of a designated VP (i.e., between the ingress and egress interfaces of the VP connection). The agent is provided with the Ingress VPI, Egress Interface, and Egress VPI in order to run this internal test. This test may be useful in proxy situations where the proxy agent represents a network. Implementations of this test may be specific to the managed resource. One implementation in a managed network may be as follows, the managed network inserts a segment loopback OAM cell at the network internal segment end-point (corresponding to the ingress connection point) for the designated VP connection. The loopback cell then travels through the network's portion of the VP connection until it reaches the networks connection point to the egress, where it is looped back to the network's cell insertion point on the designated VP. Success is achieved if the loopback OAM cell returns to the originating internal network segment end-point within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVpServiceInternal, and the object testTarget points to the row in the atmVpCrossConnectTable in [RFC2515] corresponding to the VP designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVpServiceInternal' The testRowStatus is used to invoke the atmLoopbackVpServiceInternal test on the VP crossconnect with the ingress and egress VPI values corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 7 } atmLoopbackVcServiceInternal OBJECT-IDENTITY STATUS current DESCRIPTION "This is a loopback test that the manager requests an agent to perform over the managed resource's internal portion of a designated VC (i.e., between the ingress and egress interfaces of the VC connection). The agent is provided with the Ingress VPI, Ingress VCI, Egress Interface, Egress VPI, and Egress VCI in order to run this internal test. This test may be useful in proxy situations where the proxy agent represents a network. Implementations of this test may be specific to the managed resource. One implemenation in a managed network may be as follows, the managed network inserts a segment loopback OAM cell at the network internal segment end-point (corresponding to the ingress connection point) for the designated VC connection. The loopback cell then travels through the network's portion of the VC connection until it reaches the network's connection point to the egress, where it is looped back to the network's cell insertion point on the designated VC. Success is achieved if the loopback OAM cell returns to the originating internal network segment end-point within 5 seconds, otherwise, the test fails. The manager-station performs a loopback test by making use of the testTable defined in [TestMIB]. In order to run this test the object testType in the testTable shall be set to atmLoopbackVcServiceInternal, and the object testTarget points to the row in the atmVcCrossConnectTable in [RFC2515] corresponding to the VC designated for the test. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the testTable for the interface to be tested (follow procedure defined in [TestMIB]). Once the manager-station obtains ownership, a loopback test for a given interface can be invoked by first setting up parameters necessary for the loopback test (e.g., set the testTarget), and then setting the value of testType in the testTable equal to 'atmLoopbackVcServiceInternal'. The testRowStatus is used to invoke the atmLoopbackVcServiceInternal test on the VC crossconnect with the ingress and egress VPI/VCI values corresponding to the testTarget. After invoking a loopback test, wait for the test completion by polling for the object testResult. A value of 'inProgress(3)' will result if the test is still in progress. Once the test is completed, the object testResult will have a value of 'success(2)' if the loopback OAM cell returned to the originator of the test within 5 seconds, if not, a value of 'failed(7)' will result. If the ATM system does not support this type of loopback test, then a value of 'notSupported(4)' will be provided. Other possible values for the testResult object are 'unAbleToRun(5)' and 'aborted(6)'." ::= { atmLoopbackTestTypes 8 } -- ************************************************ -- (2) ATM End-Point Tables -- This concerns information for interfaces -- supporting ATM Loopback Tests and includes: -- 1. ATM VP End-Point Table -- 2. ATM VC End-Point Table atmEndptGroup OBJECT IDENTIFIER ::= { atmTESTMIBObjects 2} -- 1. ATM VP End-Point Table atmVplEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVplEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "End-point Information for each VP." ::= { atmEndptGroup 1 } atmVplEndptEntry OBJECT-TYPE SYNTAX AtmVplEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry with end-point information about the ATM VP." AUGMENTS { atmVplEntry } ::= { atmVplEndptTable 1 } AtmVplEndptEntry ::= SEQUENCE { atmVplEndptSegmentEndPoint INTEGER } atmVplEndptSegmentEndPoint OBJECT-TYPE SYNTAX INTEGER { isaVplSegmentEndPoint(1), notaVplSegmentEndPoint(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "An indication of whether or not the VP interface has been configured to represent a VPC Segment End-Point. If the corresponding VP Link is a UNI, the value of this object is permanently set to isaVplSegmentEndPoint(1). Otherwise, the default is set to notaVplSegmentEndPoint(2)." ::= { atmVplEndptEntry 1 } -- 2. ATM VC End-Point Table atmVclEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVclEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "End-point Information for each VC." ::= { atmEndptGroup 2 } atmVclEndptEntry OBJECT-TYPE SYNTAX AtmVclEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry with end-point information about the ATM VC." AUGMENTS { atmVclEntry } ::= { atmVclEndptTable 1 } AtmVclEndptEntry ::= SEQUENCE { atmVclEndptSegmentEndPoint INTEGER } atmVclEndptSegmentEndPoint OBJECT-TYPE SYNTAX INTEGER { isaVclSegmentEndPoint(1), notaVclSegmentEndPoint(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "An indication of whether or not the VC interface has been configured to represent a VCC Segment End-Point. If the corresponding VC Link is a UNI, the value of this object is permanently set to isaVclSegmentEndPoint(1). Otherwise, the default is set to notaVclSegmentEndPoint(2)." ::= { atmVclEndptEntry 1 } -- ************************************************ -- Conformance Information atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} atmTESTMIBGroups OBJECT IDENTIFIER ::= {atmTESTMIBConformance 1} atmTESTMIBCompliances OBJECT IDENTIFIER ::= {atmTESTMIBConformance 2} -- Compliance Statements atmTESTMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which represent ATM interfaces. The compliance statements are used to determine if a particular group or object applies to hosts, networks/switches, or both." MODULE -- this module MANDATORY-GROUPS { atmLoopbackGroup } -- Objects in the ATM Loopback Test Group OBJECT atmIfLogicalLoopbackId MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for ATM systems supporting the atmLoopbackVpLocationID and atmLoopbackVcLocationID tests." OBJECT atmVplEndptSegmentEndPoint MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is mandatory for systems that are supporting ATM loopback tests." OBJECT atmVclEndptSegmentEndPoint MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is mandatory for systems that are supporting ATM loopback tests." ::= { atmTESTMIBCompliances 1 } -- ********************************************** -- Units of Conformance atmLoopbackGroup OBJECT-GROUP OBJECTS { atmIfLogicalLoopbackId, atmVplEndptSegmentEndPoint, atmVclEndptSegmentEndPoint } STATUS current DESCRIPTION "A collection of objects providing information for Loopback Tests." ::= { atmTESTMIBGroups 1 } END -- -- Copyright (C) The Internet Society (1999). All Rights -- Reserved. -- -- This document and translations of it may be copied and -- furnished to others, and derivative works that comment on or -- otherwise explain it or assist in its implementation may be -- prepared, copied, published and distributed, in whole or in -- part, without restriction of any kind, provided that the above -- copyright notice and this paragraph are included on all such -- copies and derivative works. However, this document itself -- may not be modified in any way, such as by removing the -- copyright notice or references to the Internet Society or -- other Internet organizations, except as needed for the purpose -- of developing Internet standards in which case the procedures -- for copyrights defined in the Internet Standards process must -- be followed, or as required to translate it into languages -- other than English. -- -- The limited permissions granted above are perpetual and will -- not be revoked by the Internet Society or its successors or -- assigns. -- -- This document and the information contained herein is provided -- on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET -- ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR -- IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE -- USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR -- ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A -- PARTICULAR PURPOSE. -- -- --