Definitions of Tests
for ATM Management
January 1996
Michael Noto (editor)
Bell Communications Research
noto@cc.bellcore.com
Kaj Tesink (editor)
Bell Communications Research
kaj@cc.bellcore.com
<draft-ietf-atommib-test-00.txt>
1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as a
"work in progress".
To learn the current status of any Internet-Draft, please
check the "1id-abstracts.txt" listing contained in the
Internet-Drafts Shadow Directories on ds.internic.net (US East
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast),
or munnari.oz.au (Pacific Rim).
draft ATM Test Objects January 1996
2. Introduction
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it
describes objects used for managing ATM-based interfaces,
devices, networks and services in addition to those defined in
the ATM MIB [1], to provide additional support for the
management of ATM Loopback Tests.
3. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
0 RFC 1442 [2] which defines the SMI, the mechanisms used
for describing and naming objects for the purpose of
management.
0 STD 17, RFC 1213 [3] defines MIB-II, the core set of
managed objects for the Internet suite of protocols.
0 RFC 1445 [4] which defines the administrative and other
architectural aspects of the framework.
0 RFC 1448 [5] which defines the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
Expires in six months [Page 2]
draft ATM Test Objects January 1996
4. Object Definitions
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) defined in the SMI. In particular, each object
type is named by an OBJECT IDENTIFIER, an administratively
assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation
of the object. For human convenience, we often use a textual
string, termed the descriptor, to also refer to the object
type.
5. Overview
The purpose of this memo is to provide additional
capabilities, not found in the ATM MIB [1], which are needed
to manage ATM interfaces. This memo addresses ATM Testing
Support.
5.1. Background
In addition to the MIB module defined in this memo, other MIB
modules are necessary to manage ATM interfaces, links and
cross-connects. Examples include MIB II for general system
and interface management (RFC 1213 and RFC 1573), the DS3 or
SONET MIBs for management of SONET and DS3 physical
interfaces, and, as appropriate, MIB modules for applications
that make use of ATM, such as SMDS and LAN Emulation. These
MIB modules are outside the scope of this specification.
This MIB module also requires the use of the ATM MIB module
defined in [1].
This memo proposes extensions to the ATM MIB in order to
support ATM Loopback Tests. An ATM Loopback Test provides the
ability to send out a loopback OAM (Operations and
Maintenance) cell to verify the exisitence of connectivity for
a particular connection.
The current specification of this supplemental ATM MIB is
based on SNMPv2 SMI.
Expires in six months [Page 3]
draft ATM Test Objects January 1996
5.2. Important Definitions
The following terms are defined here and used throughout this
MIB:
- Virtual Path Link (VPL)
- Virtual Path Connection (VPC)
- Virtual Path Segment (VP Segment)
- Virtual Channel Link (VCL)
- Virtual Channel Connection (VCC)
- Virtual Channel Segment (VC Segment).
_____ _______ _______ _______ _____
| |____| |____| |____| |____| |
|Host1| |SwitchA| |SwitchB| |SwitchC| |Host2|
| |____| |____| |____| |____| |
|_____| |_______| |_______| |_______| |_____|
|<----->| Virtual |<----->| Virtual
Path Link Path Link
|<------------Virtual Path Connection---------->|
(between Host1 and Host2)
|<--------------->| Virtual Path
Segment (between
SwitchA and SwitchC)
Figure 1: Examples of Virtual Path Links, Virtual Path
Connection, and Virtual Path Segment
Expires in six months [Page 4]
draft ATM Test Objects January 1996
_____ _______ _______ _______ _____
| |____| |____| |____| |____| |
|Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2|
| |____| |____| |____| |____| |
|_____| |_______| |_______| |_______| |_____|
|<----->| Virtual |<----->| Virtual
Channel Link Channel Link
|<----------Virtual Channel Connection--------->|
(between Host1 and Host2)
|<--------------->| Virtual Channel
Segment (between
SwitchA and SwitchC)
Figure 2: Examples of Virtual Channel Links, Virtual
Channel Connection, and Virtual Channel Segment
5.3. Supported Functions
The managed ATM objects are arranged into the following
groups:
I. ATM Testing Support:
(1) ATM Loopback Testing Group
(2) ATM End-Point Group.
5.3.1. ATM Testing Support
5.3.1.1. ATM Loopback Testing Group
The loopback test provides the ability to send out a loopback
OAM cell to verify the existence of connectivity for a
particular connection. Loopback tests can be performed on
either an entire connection (i.e., an end-to-end test), a
segment of the connection (i.e., a segment test), a portion of
a segment (i.e., a loopback location identifier test), or the
network portion of a connection (i.e., a service internal
test).
Expires in six months [Page 5]
draft ATM Test Objects January 1996
The loopback test makes use of the Interface Test Table
defined in RFC 1573. For a given interface, a loopback test
can be invoked by obtaining ownership of a test and then by
setting the value of 'ifTestType' equal to one of the ATM
Loopback Test Types defined in Section (8). See procedures in
RFC 1573 for using the Interface Test Table. After invoking a
loopback test, the object 'ifTestResult' can be read to
determine the outcome of the loopback test (e.g., success(2)
if the loopback cell made it back to the originator of the
test or failed(7) if the loopback cell did not make it back).
This group contains the following types of loopback tests:
- End-to-end Loopback Test
- Segment Loopback Test
- Loopback Test Using Loopback Location Identifier
- Network Loopback Test.
1) End-to-end Loopback Test
The end-to-end loopback (LB) is self-explanatory. For a VP
test, the cell is sent on the given VP, via VCI=4 specified in
[8]. For a VC test, the LB cell is sent on the VC under test,
with the PTI (Payload Type Indicator) set to 5 as specified in
[8]. Figure 3 illustrates the end-to-end loopback test.
____ _______ _______ _______ ____
|Host| | | | | | | |Host|
|____|----|SwitchA|----|SwitchB|----|SwitchC|----|____|
|_______| |_______| |_______|
|<--------------------------------------------->| Test
Path
Figure 3: End-to-end Loopback Test
See Section (8) for more details on how to use the End-to-end
Loopback Test.
2) Segment Loopback Test
Expires in six months [Page 6]
draft ATM Test Objects January 1996
The segment LB test is explained in ITU-T I.610[9]. For a VP
segment test, the LB cell is sent on the VP under test via
VCI=3 as specified in [8], and the Loopback Location ID field
is set to all 1's. For a VC segment test, the LB cell is sent
on the VC under test, with the PTI set to 4 as specified in
[8], and the Loopback Location ID field is set to all 1's.
This test involves a LB cell being inserted at a pre-defined
segment end-point, and looped back at the corresponding
segment end-point encountered. The pair of segment end-points
define a segment (which is used for the segment loopback
test). A VP/VC connection can have multiple segments, but
multiple segments cannot overlap.
A UNI interface is by definition defined as a segment end-
point (hence a UNI would be considered a segment). A segment
can also define:
- a B-ICI
- a public carrier's 'piece' of the connection
- a private network's 'piece' of the connection.
In order to support this functionality, the VP/VC link
termination needs to be able to be defined as a segment. This
can be done using either the atmVplSegmentEndPoint or
atmVclSegmentEndPoint object depending on whether it is for a
VPC or VCC. A segment loopback test is illustrated in Figure
4.
____ _______ _______ _______ ____
|Host| | | | | | | |Host|
|____|----|SwitchA|----|SwitchB|----|SwitchC|----|____|
|_______| |_______| |_______|
|<----------------------->| Segment
Figure 4: Segment Loopback Test
Section (8) describes the use of the ATM Segment Loopback
Tests.
3) Loopback Test Using Loopback Location Identifier
Expires in six months [Page 7]
draft ATM Test Objects January 1996
This loopback test is a special type of 2) where the Loopback
Location ID field is set to a value that corresponds to a
specific node in a given network (Note that the format of this
field is not standardized, that is, the value is significant
only within an administrative domain). In this case, the
device initiating the LB test inserts the appropriate Loop
Back Location ID. When the LB cell reaches the corresponding
device, that device recognizes the Loopback Location ID as its
own, and loops it back. This test is useful for performing
fault sectionalization without having to provision segment
end-points. An additional object, the loopbackLocationID, is
defined to determine the loopback point. Figure 5 shows a
loopback test using a location identifier. Note that the
loopback test using location identifier can be used to perform
a loopback test over a portion of a defined segment. See
Figure 5.
____ _______ _______ _______ ____
|Host| | | | | | | |Host|
|____|----|SwitchA|----|SwitchB|----|SwitchC|----|____|
|_______| |_______| |_______|
|<---------->| Portion of Segment that
Loopback test is
performed on
|<----------------------->| Segment
Figure 5: Loopback Test Using Location Identifier
See Section (8) for more details.
4) Network Loopback Test
This is a loopback test that the manager requests an agent in
a network to perform over the internal portion of a designated
connection. The Network then initiates the internal network
loopback test by inserting an OAM loopback cell at one of the
end-points of the internal network portion of the connection.
When the loopback cell reaches the other end-point of the
internal Network , the cell is looped back. This test is
useful for verifying connectivity through a particular
network. Figure 6 illustrates the Network loopback test.
Expires in six months [Page 8]
draft ATM Test Objects January 1996
____ _______ _______ _______ ____
|Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host|
|____|----|SwitchA|----|SwitchB|----|SwitchC|----|____|
|_______| |_______| |_______|
|<----------------------->| LB Test Path
thru Network 1
Figure 6: Network Loopback Test
See Section (8) for more details.
5.3.1.2. ATM End-Point Group
The ATM End-Point Group contains two tables: the ATM VP End-
point Table and the ATM VC End-point Table. The ATM VP End-
point Table augments the atmVplTable and provides the
atmVplEndptSegmentEndPoint object to represent whether or not
a specified VPL is a segment end-point. Similarly for Virtual
Channels, the ATM VC End-point Table and the
atmVclEndptSegmentEndPoint object are used to represent
whether or not a specified VCL is a segment end-point.
Expires in six months [Page 9]
draft ATM Test Objects January 1996
6. Definitions
ATMTEST-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY,
OBJECT-TYPE, Integer32, experimental
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
atmMIBObjects, atmVplEntry, atmVclEntry
FROM ATM-MIB;
atmTESTMIB MODULE-IDENTITY
LAST-UPDATED "9610181200Z"
ORGANIZATION "IETF AToMMIB Working Group"
CONTACT-INFO
" Michael Noto
Postal: Bell Communications Research
331 Newman Springs Road
Red Bank, NJ 07701
US
Tel: +1 908 758 5104
Fax: +1 908 758 4177
E-mail: noto@cc.bellcore.com
Kaj Tesink
Postal: Bell Communications Research
331 Newman Springs Road
Red Bank, NJ 07701
US
Tel: +1 908 758 5254
Fax: +1 908 758 4177
E-mail: kaj@cc.bellcore.com"
DESCRIPTION
"This MIB Module provides
ATM Loopback Tests and supporting objects
that must be supported by ATM devices
providing ATM Loopback Tests."
::= { experimental XX }
atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1}
-- ******** NOTE TO THE RFC EDITOR **************
Expires in six months [Page 10]
draft ATM Test Objects January 1996
-- In case this module is put on the standards track
-- replace the following:
-- "atmTESTMIB MODULE-IDENTITY ::= {experimental XX}" with
-- "atmTESTMIB MODULE-IDENTITY ::= {atmMIBObjects 14}"
-- and include atmMIBObjects in the IMPORT clause.
-- This ATMTEST-MIB Module consists of the following groups:
-- ATM Testing Support:
-- (1) ATM Loopback Testing Group
-- (2) ATM End-Point Group
Expires in six months [Page 11]
draft ATM Test Objects January 1996
-- ************************************************
-- (1) ATM Loopback Testing Group
-- This group contains information for interfaces
-- supporting ATM Loopback Tests
-- This group includes the following:
-- 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.
atmLoopbackID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This identifier is used to identify this local
ATM device. The value of this object can be used
by other ATM devices to identify this local ATM
device as the device that is being requested to
loopback the OAM Loopback cell. An other ATM
device would accomplish this by placing the value
defined for this value in either the
atmLoopbackLocID or the atmLoopbackSrcID and then
performing a desired loopback test. The default
for this field is all 1's, which would indicate a
segment OAM Loopback Test. Location Identifiers of
less than 16 octets are left justified, and padded
with all '0's."
DEFVAL { 'ffffffffffffffffffffffffffffffff'H }
::= { atmLoopbackTestGroup 1 }
atmLoopbackLocID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..16))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This parameter represents the identity of the ATM
device that is being requested to loopback the OAM
Expires in six months [Page 12]
draft ATM Test Objects January 1996
Loopback cell. The default for this field is all
1's, which would indicate a segment OAM Loopback
Test. Location Identifiers of less than 16 octets
are left justified, and padded with all '0's. This
object is required for the atmLoopbackVpLocationID
and atmLoopbackVcLocationID tests."
DEFVAL { 'ffffffffffffffffffffffffffffffff'H }
::= { atmLoopbackTestGroup 2 }
atmLoopbackSrcID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..16))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This optional parameter identifies the source
(e.g., the switch) originating the Loopback cell.
The default value of all '1's (binary) represents no
identification of the source. Source Identifiers of
less than 16 octets are left justified, and padded
with all '0's."
DEFVAL { 'ffffffffffffffffffffffffffffffff'H}
::= { atmLoopbackTestGroup 3 }
-- 2. List of ATM Loopback Test Types
-- The following loopback test types are defined:
-- atmLoopbackVpE2e
-- atmLoopbackVcE2e
-- atmLoopbackVpSegment
-- atmLoopbackVcSegment
-- atmLoopbackVpLocationID
-- atmLoopbackVcLocationID
-- atmLoopbackVpServcInternal
-- atmLoopbackVcServcInternal
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
Expires in six months [Page 13]
draft ATM Test Objects January 1996
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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVpE2e.p) , where the subidentifier
'p' is the instance of the atmVplVpi corresponding to
the VP designated for the test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable
for the interface to be tested (follow procedure
defined in RFC 1573). 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.,
p=1), and then setting the value of 'ifTestType' in
the ifTestTable equal to 'atmLoopbackVpE2e'. This
will cause the atmLoopbackVpE2e test to be invoked on
the VP with VPI=1.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'.
A value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' object are
'unAbleToRun(5)' and 'aborted(6)'."
::= { atmLoopbackTestTypes 1 }
atmLoopbackVcE2e OBJECT-IDENTITY
Expires in six months [Page 14]
draft ATM Test Objects January 1996
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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVcE2e.p.c) , where the
subidentifier 'p' is the instance of the atmVclVpi
corresponding to the VC designated for the test and
the subidentifier 'c' is the instance of the atmVclVci
corresponding to the VC designated for the test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined
in RFC 1573). 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., p=1, c=33), and then
setting the value of 'ifTestType' in the ifTestTable
equal to 'atmLoopbackVcE2e'. This will cause the
atmLoopbackVcE2e test to be invoked on the VC with
VPI=1 and VCI=33.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'.
A value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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
Expires in six months [Page 15]
draft ATM Test Objects January 1996
value of 'notSupported(4)' will be provided. Other
possible values for the 'ifTestResult' 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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVpSegment.p) , where the
subidentifier 'p' is the instance of the atmVplVpi
corresponding to the VP designated for the test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). Once the manager-station obtains ownership,
a loopback test for a given interface can be invoked by
Expires in six months [Page 16]
draft ATM Test Objects January 1996
first setting up parameters necessary for the loopback
test (e.g., p=1), and then setting the value of
'ifTestType' in the ifTestTable equal to
'atmLoopbackVpSegment'. This will cause the
atmLoopbackVpSegment test to be invoked on the VP with
VPI=1.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' 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
Expires in six months [Page 17]
draft ATM Test Objects January 1996
would be achieved when the atmLoopbackVcSegment test
was initiated over the UNI.
The manager-station can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVcSegment.p.c) , where the
subidentifier 'p' is the instance of the atmVclVpi
corresponding to the VP designated for the test and the
subidentifier 'c' is the instance of the atmVclVci
corresponding to the VC designated for the test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). 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., p=1, c=33), and then setting the value of
'ifTestType' in the ifTestTable equal to
'atmLoopbackVcSegment'. This will cause the
atmLoopbackVcSegment test to be invoked on the VC with
VPI=1 and VCI=33.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' 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
Expires in six months [Page 18]
draft ATM Test Objects January 1996
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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVpLocationId.p.d) , where the
subidentifier 'p' is the instance of the atmVplVpi
corresponding to the VP designated for the test and 'd'
consists of 16 subidentifiers, where each subidentifier
corresponds to the value of a subsequent octet of the
Loopback Location ID defined in I.610[9] starting with
the most significant octet.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). 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., p=1, d=AAAABBBBCCCCDDDD), and then setting
the value of 'ifTestType' in the ifTestTable equal to
'atmLoopbackVpLocationId'. This will cause the
atmLoopbackVpLocationId test to be invoked on the VP
with VPI=1 and looped back at loopback location ID=
AAAABBBBCCCCDDDD.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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
Expires in six months [Page 19]
draft ATM Test Objects January 1996
support this type of loopback test, then a value of
'notSupported(4)' will be provided. Other possible
values for the 'ifTestResult' 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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVcLocationId.p.c.d) , where the
subidentifier 'p' is the instance of the atmVclVpi
corresponding to the VC designated for the test, the
subidentifier 'c' is the instance of the atmVclVci
corresponding to the VC designated for the test, and
'd' consists of 16 subidentifiers, where each
subidentifier corresponds to the value of a subsequent
octet of the Loopback Location ID defined in I.610[9]
starting with the most significant octet.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). 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., p=1, c=33, d= AAAABBBBCCCCDDDD), and then
Expires in six months [Page 20]
draft ATM Test Objects January 1996
setting the value of 'ifTestType' in the ifTestTable
equal to 'atmLoopbackVcLocationId'. This will cause
the atmLoopbackVcLocationId test to be invoked on the
VC with VPI=1/VCI=33 and looped back at loopback
location ID= AAAABBBBCCCCDDDD.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' object are
'unAbleToRun(5)' and 'aborted(6)'."
::= { atmLoopbackTestTypes 6 }
atmLoopbackVpServcInternal 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
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 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.
Expires in six months [Page 21]
draft ATM Test Objects January 1996
The manager-station can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVpServcInternal.pi.ie.pe) , where
the subidentifier 'pi' is the instance of the atmVplVpi
for the ingress corresponding to the VP designated for
the test, the subidentifier 'ie' is the instance of the
ifIndex for the egress corresponding to the VP
designated for the test, and 'pe' is the instance of
the atmVplVpi corresponding to the egress for the VP
designated for this test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). Once the manager-station obtains ownership,
a request is sent to the network to initiate the
network loopback test on the ingress interface
(ifIndex=2) along with the necessary parameters (e.g.,
pi=1, ie=4, pe=2), and then setting the value of
'ifTestType.2' in the ifTestTable equal to
'atmLoopbackVpServcInternal'. This will cause the
atmLoopbackVpServcInternal test to be invoked on the
network's internal section of the VP between the
ingress interface (ifIndex=2) with VPI=1 and the egress
interface with ifIndex=4 and VPI=2.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' object are
'unAbleToRun(5)' and 'aborted(6)'."
::= { atmLoopbackTestTypes 7 }
atmLoopbackVcServcInternal OBJECT-IDENTITY
STATUS current
DESCRIPTION
Expires in six months [Page 22]
draft ATM Test Objects January 1996
"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
networks 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 can perform a loopback test by
making use of the Interface Test Table (ifTestTable)
defined in RFC 1573. In order to run this test the
object type 'ifTestType' in the ifTestTable shall be
set to (atmLoopbackVcServcInternal.pi.ci.ie.pe.ce) ,
where the subidentifier 'pi' is the instance of the
atmVclVpi for the ingress corresponding to the VC
designated for the test, the subidentifier 'ci' is the
instance of the atmVclVci for the ingress corresponding
to the VC designated for the test, the subidentifier
'ie' is the instance of the ifIndex for the egress
corresponding to the VC designated for the test, 'pe'
is the instance of the atmVclVpi corresponding to the
egress for the VC designated for this test, and 'ce' is
the instance of the atmVclVci corresponding to the
egress for the VC designated for this test.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the ifTestTable for
the interface to be tested (follow procedure defined in
RFC 1573). Once the manager-station obtains ownership,
a request is sent to the network to initiate the
Expires in six months [Page 23]
draft ATM Test Objects January 1996
network loopback test on the ingress interface
(ifIndex=2) along with the necessary parameters (e.g.,
pi=1, ci=33, ie=4, pe=2, ce=41), and then setting the
value of 'ifTestType.2' in the ifTestTable equal to
'atmLoopbackVcServcInternal'. This will cause the
atmLoopbackVcServcInternal test to be invoked on the
network's internal section of the VC between the
ingress interface (ifIndex=2) with VPI=1/VCI=33 and the
egress interface with ifIndex=4 and VPI=2/VCI=41.
After invoking a loopback test, wait for the test
completion by polling for the object 'ifTestResult'. A
value of 'inProgress(3)' will result if the test is
still in progress. Once the test is completed, the
object 'ifTestResult' 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 'ifTestResult' object are
'unAbleToRun(5)' and 'aborted(6)'."
::= { atmLoopbackTestTypes 8 }
Expires in six months [Page 24]
draft ATM Test Objects January 1996
-- ************************************************
-- (2) ATM End-Point Group
-- This group contains information for interfaces
-- supporting ATM Loopback Tests
-- This group includes the following:
-- 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)
Expires in six months [Page 25]
draft ATM Test Objects January 1996
}
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 1
(isaVplSegmentEndPoint). Otherwise, the default is
set to 2 (notaVplSegmentEndPoint)."
::= { 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)
}
Expires in six months [Page 26]
draft ATM Test Objects January 1996
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 1
(isaVclSegmentEndPoint). Otherwise, the default is
set to 2 (notaVclSegmentEndPoint)."
::= { 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 atmLoopbackLocID
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required. This object is
required for ATM systems supporting the
atmLoopbackVpLocationID and atmLoopbackVcLocationID
Expires in six months [Page 27]
draft ATM Test Objects January 1996
tests."
OBJECT atmLoopbackSrcID
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
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 {
atmLoopbackID,
atmLoopbackLocID,
atmLoopbackSrcID,
atmVplEndptSegmentEndPoint,
atmVclEndptSegmentEndPoint
}
STATUS current
DESCRIPTION
"A collection of objects providing information
for Loopback Tests."
::= { atmTESTMIBGroups 1 }
Expires in six months [Page 28]
draft ATM Test Objects January 1996
END
Expires in six months [Page 29]
draft ATM Test Objects January 1996
7. Acknowledgments
This document is a product of the AToMMIB Working Group.
Expires in six months [Page 30]
draft ATM Test Objects January 1996
8. References
[1] Ahmed, M., Tesink, K., "Definitions of Managed Objects
for ATM Management Version 8.0 using SMIv2", RFC 1695,
Bell Communications Research, August 1994.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Structure of Management Information for version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC 1442,
SNMP Research,Inc., Hughes LAN Systems, Dover Beach
Consulting, Inc., Carnegie Mellon University, April 1993.
[3] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991.
[4] Galvin, J., and K. McCloghrie, "Administrative Model for
version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1445, Trusted Information Systems, Hughes
LAN Systems, April 1993.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1448, SNMP
Research,Inc., Hughes LAN Systems, Dover Beach
Consulting, Inc., Carnegie Mellon University, April 1993.
[6] McCloghrie, K. and F. Kastenholz, "Evolution of the
Interfaces Group of MIB-II", RFC 1573, Hughes LAN
Systems, FTP Software, January 1994.
[7] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI
3.0) Specification, Part I", 1994.
[8] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI
3.1) Specification, Part I", November 1994.
[9] ITU-T Recommendation I.610, "Broadband Integrated Service
Digital Network (B-ISDN) Operation and Maintenance
Principles and Functions", July 1995.
Expires in six months [Page 31]
draft ATM Test Objects January 1996
9. Security Considerations
Security issues are not discussed in this memo.
10. Authors' Addresses
Michael Noto
Bell Communications Research
Room 1E-348
331 Newman Springs Road
P.O. Box 7020
Red Bank, NJ 07701-7020
Phone: (908) 758-5104
EMail: noto@cc.bellcore.com
Kaj Tesink
Bell Communications Research
Room 1A-427
331 Newman Springs Road
P.O. Box 7020
Red Bank, NJ 07701-7020
Phone: (908) 758-5254
EMail: kaj@cc.bellcore.com
Expires in six months [Page 32]
draft ATM Test Objects January 1996
Table of Contents
1 Status of this Memo ................................... 1
2 Introduction .......................................... 2
3 The SNMPv2 Network Management Framework ............... 2
4 Object Definitions .................................... 3
5 Overview .............................................. 3
5.1 Background .......................................... 3
5.2 Important Definitions ............................... 4
5.3 Supported Functions ................................. 5
5.3.1 ATM Testing Support ............................... 5
5.3.1.1 ATM Loopback Testing Group ...................... 5
5.3.1.2 ATM End-Point Group ............................. 9
6 Definitions ........................................... 10
7 Acknowledgments ....................................... 30
8 References ............................................ 31
9 Security Considerations ............................... 32
10 Authors' Addresses ................................... 32
Expires in six months [Page 33]
