RFC relevance of associate

As per Relevance of the word associate, we have this rfc below:

Network Working Group M.
Request for Comments: 1695 K.
Category: Standards Track
Bell Communications
August 1994

Definitions of Managed
for ATM Management Version 8.0
using SMIv

Status of this

This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited

Table of

1. Introduction ............................................. 2
2. The SNMPv2 Network Management Framework .................. 2
3. Object Definitions ....................................... 2
4. ATM Terminology .......................................... 3
4.1 VCL/VPL and VCC/VPC ..................................... 3
4.2 PVC and SVC ............................................. 5
4.3 Traffic Management Parameters ........................... 5
4.3.1 Traffic Policing and Traffic Shaping Parameters ...... 5
4.3.2 Cell Loss Priority .................................... 6
4.3.3 QoS Class ............................................. 6
5. Overview ................................................. 7
5.1 Background .............................................. 7
5.2 Structure of the MIB .................................... 7
5.3 ATM Interface Configuration Group ....................... 7
5.4 ATM Interface DS3 PLCP and TC Layer Groups .............. 8
5.5 ATM Virtual Link and Cross-Connect Groups ............... 8
6. Application of MIB II to ATM ............................. 8
6.1 The System Group ........................................ 8
6.2 The Interface Group ..................................... 8
6.2.1 Support of the ATM Cell Layer by ifTable .............. 9
7. Support of the AAL3/4 Based Interfaces ................... 10
8. Support of the AAL5 Managed Objects ...................... 10
8.1 Managing AAL5 in a Switch ............................... 11
8.2 Managing AAL5 in a Host ................................. 12
8.3 Support of AAL5 by ifTable .............................. 13
8.4 Support of Proprietary Virtual Interface by ifT-able .. 14
8.5 AAL5 Connection Performance Statistics Group ............ 15

Ahmed & Tesink [Page 1]

RFC 1695 ATM Management Objects August 1994

9. ILMI MIB and the ATM Managed Objects ..................... 15
10. Definitions ............................................. 18
11. Acknowledgments ......................................... 72
12. References .............................................. 72
13. Security Considerations ................................. 73
14. Authors' Addresses ...................................... 73

1.

This memo defines a 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-
interfaces, devices, networks and services

This memo specifies a MIB module in a manner that is both
to the SNMPv2 SMI, and semantically identical to the peer SNMPv
definitions

2. The SNMPv2 Network Management

The SNMPv2 Network Management Framework consists of four
components. They are

0 RFC 1442 [1] which defines the SMI, the mechanisms
for describing and naming objects for the purpose
management

0 STD 17, RFC 1213 [2] defines MIB-II, the core set
managed objects for the Internet suite of protocols

0 RFC 1445 [3] which defines the administrative and
architectural aspects of the framework

0 RFC 1448 [4] which defines the protocol used for
access to managed objects

The Framework permits new objects to be defined for the purpose
experimentation and evaluation

3. Object

Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,

Ahmed & Tesink [Page 2]

RFC 1695 ATM Management Objects August 1994

often use a textual string, termed the descriptor, to also refer
the object type

4. ATM

Some basic ATM terminologies are described in this section
facilitate defining the ATM managed objects

4.1. VCL/VPL and VCC/

There are two distinct types of ATM virtual connections:
Channel Connections (VCCs) and Virtual Path Connection (VPCs).
shown in Figures 1 and 2, ATM virtual connections consist
concatenated series of virtual links which forms a path between
end points, with each concatenation occurring at an ATM switch
Virtual links of VCCs are called Virtual Channel Links (VCLs).
Virtual links of VPCs are called Virtual Path Links (VPLs). The
and VPI fields in the ATM cell header associate each cell of a
with a particular VCL over a given physical link. The VPI field
the ATM cell header associates each cell of a VPC with a
VPL over a given physical link. Switches route cells between
(or VPLs) via a cross-connect function according to the cells
VCI/VPI (or VPI) values

<-----------------------VCC-------------------------->
------------ -----------
|ATM | |ATM |
|X-Connect | |X-Connect |
VCL1 |Point | VCL2 |Point | VCL
O---------|----X-----|-------|-----|----X-----|-------
| | | |
------------ ------------
ATM Switch ATM

Figure 1: Virtual Channel Links
Virtual Channel

Ahmed & Tesink [Page 3]

RFC 1695 ATM Management Objects August 1994

<-----------------------VPC-------------------------->
------------ -----------
|ATM | |ATM |
|X-Connect | |X-Connect |
VPL1 |Point | VPL2 |Point | VPL
O---------|----X-----|-------|-----|----X-----|-------
| | | |
------------ ------------
ATM Switch ATM

Figure 2: Virtual Path Links
Virtual Path

A single ATM end-system or switch does not support the whole end-to
end span of a VCC (or VPC). Rather, multiple ATM end- systems and/
switches each support one piece of the VCC (or VPC). That is,
ATM end-system at one end of the VCC/VPC supports its end of
VCC/VPC plus the VCLs or VPLs on its external interfaces, and
switch through which the VCC/VPC passes, supports the
VCLs/VPLs on that switch's external interfaces and the cross
connection of those VCLs/VPLs through that switch. Thus, the end
to-end management of a VCC or VPC is achieved only by
management of its individual pieces in combination

Note that for management purposes, an ATM network may be viewed as
large distributed switch by hiding all the network's
connectivity as being internal to the distributed switch (as shown
Figure 2a). This model may for example be used for Customer
Management (CNM) purposes

Ahmed & Tesink [Page 4]

RFC 1695 ATM Management Objects August 1994

<---------------------VCC--------------------------->
--------------------------------------
| |
| ---------- ---------- |
| | ATM | | ATM | |
VCL1 | | Switch | | Switch | | VCL
O-------|-|--------|------/-------|--------|-|------
| | | | | |
| ---------- ---------- |
| |
| ATM Network |
--------------------------------------

Figure 2a: ATM Network modeled as a large

A VCC has a set of traffic characteristics (i.e.,
parameters, QoS Class parameters, etc.). VCLs inherit their
characteristics from the VCC of which they are a part. VCCs are bi
directional by definition. However, the traffic parameters in
two directions of a connection can be symmetric or asymmetric, i.e.,
the two directions can have the same or different traffic flows.
uni-directional traffic flow across a VCC is achieved by assigning
zero bandwidth in one direction. Note that in addition to
bandwidth required by the user traffic flow, bandwidth is
required for OAM cell flows, even for the zero-bandwidth direction
a uni-directional connection. These same principles apply to VPCs

4.2. PVC and

A Permanent Virtual Connection (PVC) is a provisioned VCC or VPC.
Switched Virtual Connection (SVC) is a switched VCC or VPC that
set up in real-time via call set-up signaling procedures. A PVC (
an SVC) can be a point-to-point, point-to-multipoint, or multipoint
to-multipoint VCC or VPC

4.3. Traffic Management

4.3.1. Traffic Policing and Traffic Shaping

In order to allocate resources fairly among different users,
networks police traffic at resource access points. The
enforcement or policing taken at a UNI is called Usage
Control (UPC) and is activated on an incoming VCL or VPL as shown
Figure 3. The use of the traffic enforcer at the ingress of
connection is to make sure that the user traffic does not exceed

Ahmed & Tesink [Page 5]

RFC 1695 ATM Management Objects August 1994

negotiated traffic parameters such as the peak cell rate
with a specific traffic descriptor type

---------- ----------
UNI | ATM | NNI | ATM |
| | switch | | | switch | |
O<---|---->X(UPC) |<----|------>| (UPC)X<-----|--->
| VCL | | | VCL | | VCL |
---------- ----------

Figure 3: An Example of a

In addition, traffic shaping may be performed on an outgoing VPL
VCL at a given ATM interface. The function of the ATM traffic
either at the source or an egress point of the connection is
smooth the outgoing cell traffic inter-arrival time. If policing
shaping is not performed then the policing or shaping algorithm
not activated. ATM Forum has specified seven traffic
types including one for the best effort traffic [9].

4.3.2. Cell Loss

To prioritize traffic during resource congestion, ATM cells
assigned one of the two types of Cell Loss Priority (CLP), CLP=0
CLP=1. ATM cells with CLP=0 have a higher priority in regard to
loss than ATM cells with CLP=1. Therefore, during
congestions, CLP=1 cells are dropped before any CLP=0 cell
dropped

4.3.3. QoS

A VCC or VPC is associated with one of a number of Quality of
(QoS) classes. The following service classes have been specified

Service Class A: Constant bit rate video and

Service Class B: Variable bit rate video/
Service Class C: Connection-oriented
Service Class D: Connectionless

Four QoS classes numbered 1, 2, 3, and 4 have been specified with
aim of supporting service classes A, B, C, and D respectively.
VCLs (or VPLs) concatenated to form a VCC (or VPC) will all have
same QoS class as that of the VCC (or VPC). The Cell Loss
(CLR), Cell Delay Variation (CDV), and end-to-end Cell Delay (CD
parameters are defined as part of QoS Class definition. In addition

Ahmed & Tesink [Page 6]

RFC 1695 ATM Management Objects August 1994

an unspecified QoS Class numbered 0 is specified for best
traffic

5.

ATM management objects are used to manage ATM interfaces, ATM
links, ATM cross-connects, AAL5 entities and AAL5
supported by ATM hosts, ATM switches and ATM networks. This
provides an overview and background of how to use this MIB and
potential MIBs for this purpose

The purpose of this memo is primarily to manage ATM PVCs. ATM
are also represented by the management information in this MIB
However, full management of SVCs may require additional
which are beyond the scope of this memo

5.1.

In addition to the MIB module defined in this memo, other MIB
are necessary to manage ATM interfaces, links and cross-connects
Examples include MIB II for general system and interface
(RFC 1213 and RFC 1573), the DS3 or SONET MIBs for management
physical interfaces, and, as appropriate, MIB modules
applications that make use of ATM, such as SMDS. These MIB
are outside the scope of this specification

The current specification of this ATM MIB is based on SNMPv2.

5.2. Structure of the

The managed ATM objects are arranged into the following groups

(1) ATM interface configuration
(2) ATM interface DS3 PLCP
(3) ATM interface TC Sublayer
(4) ATM interface virtual link (VPL/VCL)

(5) ATM VP/VC cross-connect
(6) AAL5 connection performance statistics

Note that, managed objects for activation/deactivation of OAM
flows and ATM traps notifying virtual connection or virtual
failures are outside the scope of this memo

5.3. ATM Interface Configuration

This group contains information on ATM cell layer configuration
local ATM interfaces on an ATM device in addition to the

Ahmed & Tesink [Page 7]

RFC 1695 ATM Management Objects August 1994

on such interfaces contained in the ifTable

5.4. ATM Interface DS3 PLCP and TC Layer

These groups provide performance statistics of the DS3 PLCP and
sublayer of local ATM interfaces on a managed ATM device. DS3
and TC sublayer are currently used to carry ATM cells
over DS3 and SONET transmission paths

5.5. ATM Virtual Link and Cross-Connect

ATM virtual link and cross-connect groups model bi-directional
virtual links and ATM cross-connects. The ATM VP/VC link groups
implemented in an ATM host, ATM switch and ATM network. The
switch and ATM network also implement the ATM VP/VC cross-
groups. Both link and cross-connect groups are implemented in
carrier's network for Customer Network Management (CNM) purposes

The ATM virtual link groups are used to create, delete or modify
virtual links in an ATM host, ATM switch and ATM network.
virtual link groups along with the cross-connect groups are used
create, delete or modify ATM cross-connects in an ATM switch or
network (e.g., for CNM purposes).

6. Application of MIB II to

6.1. The System

For the purposes of the sysServices object in the System Group of
II [2], ATM is a data link layer protocol. Thus, for ATM
and ATM networks, sysServices will have the value "2".

6.2. The Interface

The Interfaces Group of MIB II defines generic managed objects
managing interfaces. This memo contains the media-
extensions to the Interfaces Group for managing ATM interfaces

This memo assumes the interpretation of the Interfaces Group to be
accordance with [5] which states that the interfaces table (ifTable
contains information on the managed resource's interfaces and
each sub-layer below the internetwork layer of a network interface
considered an interface. Thus, the ATM cell layer interface
represented as an entry in the ifTable. This entry is concerned
the ATM cell layer as a whole, and not with individual
connections which are managed via the ATM-specific managed
specified in this memo. The inter-relation of entries in the
is defined by Interfaces Stack Group defined in [5].

Ahmed & Tesink [Page 8]

RFC 1695 ATM Management Objects August 1994

6.2.1. Support of the ATM Cell Layer by

Some specific interpretations of ifTable for the ATM cell
follow

Object Use for the generic ATM
====== =============================

ifIndex Each ATM port is represented by an ifEntry

ifDescr Description of the ATM interface

ifType The value that is allocated for ATM is 37.

ifSpeed The total bandwidth in bits per
for use by the ATM layer

ifPhysAddress The interface's address at the ATM
sublayer; the ATM address which would be
as the value of the Called Party
Information Element (IE) of a
message for a connection which either
- would terminate at this interface,
- for which the Called Party Address
would need to be replaced by the
Party SubAddress IE before the
was forwarded to any other interface
For an interface on which signalling
not supported, then the interface does
necessarily have an address, but if
does, then ifPhysAddress is the address
would be used as above in the event
signalling were supported. If the
has multiple such addresses, then
is its primary address. If the interface
no addresses, then ifPhysAddress is an
string of zero length. Address encoding is
per [9]. Note that addresses assigned
purposes other than those listed above (e.g.,
an address associated with the service
side of a public network UNI) may be
through atmInterfaceAdminAddress

ifAdminStatus See [5].

ifOperStatus Assumes the value down(2) if the ATM
layer or any layer below that layer is down

Ahmed & Tesink [Page 9]

RFC 1695 ATM Management Objects August 1994

ifLastChange See [5].

ifInOctets The number of received octets over
interface, i.e., the number of received
assigned cells multiplied by 53.

ifOutOctets The number of transmitted octets over
interface, i.e., the number of transmitted
assigned cells multiplied by 53.

ifInErrors The number of cells dropped due
uncorrectable HEC errors

ifInUnknownProtos The number of received cells
during cell header validation,
cells with unrecognized VPI/VCI values
and cells with invalid cell header patterns
If cells with undefined PTI values are discarded
they are also counted here

ifOutErrors See [5].

ifName Textual name (unique on this system) of
interface or an octet string of zero length

ifLinkUpDownTrapEnable Default is disabled (2).

ifConnectorPresent Set to false (2).

ifPromiscuousMode Set to false(2).

ifHighSpeed See [5].

ifHCInOctets The 64-bit version of ifInOctets;
if required by the compliance statements in [5].

ifHCOutOctets The 64-bit version of ifOutOctets;
if required by the compliance statements in [5].

7. Support of the AAL3/4 Based

For the management of AAL3/4 CPCS layer, see [6].

8. Support of the AAL5 Managed

Support of AAL5 managed objects in an ATM switch and ATM host
described below

Ahmed & Tesink [Page 10]

RFC 1695 ATM Management Objects August 1994

8.1. Managing AAL5 in a

Managing AAL5 in a switch involves

(1) performance management of an AAL5 entity
an internal resource in a

(2) performance management of AAL5 per virtual

AAL5 in a switch is modeled as shown in Figures 4 and 5. AAL5
be managed in a switch for only those virtual connections that
AAL5 and are terminated at the AAL5 entity in the switch. Note that
the virtual channels within the ATM UNIs carrying AAL5 will
switched by the ATM switching fabric (termed as ATM Entity in
figure) to the virtual channels on a proprietary internal
associated with the AAL5 process (termed as AAL5 Entity in
figure). Therefore, performance management of the AAL5 resource
the switch will be modeled using the ifTable through an
(pseudo-ATM) virtual interface and the AAL5 performance
per virtual connection will be supported using an additional AAL
connection table in the ATM MIB. The association between the AAL
virtual link at the proprietary virtual, internal interface and
ATM virtual link at the ATM interface will be derived from
virtual channel cross-connect table and the virtual channel
table in the ATM MIB

___________________________
| |
| ============= |
| | AAL5 | |
| | Entity | |
| ============= |
| | |
| -----Prop. Virtual
| | |
| ============= |
| | ATM | |
| | Entity | |
| ============= |
|_____|__|__|__|__|_______|
| | | | |
---------------- ATM
| | | | |
| | | | |
v v v v

Figure 4 : Model of an AAL5 Entity in a

Ahmed & Tesink [Page 11]

RFC 1695 ATM Management Objects August 1994

__________________
| |
| AAL5 |
|________________|
| |
| Prop. Virtual |
| Interface |
|________________|

Figure 5 : AAL5 Entity's Interface Stack in a

8.2. Managing AAL5 in a

Managing AAL5 in a host involves managing the AAL5 sublayer
as shown in Figures 6 and 7. The AAL5 sublayer is stacked
over the ATM sublayer. The ifTable is applied to the AAL5
as defined in Section 8.3.

___________________________
| |
| ============= |
| | AAL5 | |
| | Entity | |
| ============= |
| | ATM | |
| | Entity | |
| ============= |
|___________|_____________|
|
__|__ ATM
|
|

Figure 6 : Model of an AAL5 Entity in a

__________________
| |
| AAL5 |
|________________|
| |
| ATM Layer |
|________________|
| |
| Physical Layer
|________________|

Ahmed & Tesink [Page 12]

RFC 1695 ATM Management Objects August 1994

Figure 7 : AAL5 Entity's Interface Stack in a

8.3. Support of AAL5 by

The AAL5 entity in an ATM device (e.g., switch or host) is
using the ifTable. There are additional counters specified for AAL
than those specified in the ATM B-ICI document [10].
interpretations of ifTable for the AAL5 CPCS layer are as follows

Object Use for AAL5 CPCS layer
====== ==============================

ifIndex Each AAL5 entity is represented by an ifEntry

ifDescr Description of the AAL5 entity

ifType The value that is allocated for AAL5 is 49.

ifMtu Set to the largest PDU size for
AAL5 CPCS layer that can be
by the AAL5 entity

ifSpeed Set to 0.

ifPhysAddress An octet string of zero length

ifAdminStatus See [5].

ifOperStatus Assumes the value down(2) if the AAL5
any layer below that layer is down

ifLastChange See [5].

ifInOctets The number of received AAL5 CPCS PDU octets

ifOutOctets The number of AAL5 CPCS PDU
transmitted

ifInUcastPkts The number of received AAL5 CPCS PDUs
to a higher-layer

ifOutUcastPkts The number of AAL5 CPCS PDUs received from
higher-layer for transmission
[Note: The number of AAL5 PDUs
transmitted is the number received from
higher-layer for transmission minus any
are counted by ifOutErrors and ifOutDiscards.]

Ahmed & Tesink [Page 13]

RFC 1695 ATM Management Objects August 1994

ifInErrors Number of errored AAL5 CPCS PDUs received
The types of errors counted include CRC-32 errors
SAR time-out errors, and oversized SDU errors

ifInUnknownProtos Set to 0.

ifInDiscards Number of received AAL5 CPCS PDUs discarded
Possible reason may be input buffer overflow

ifOutErrors Number of AAL5 CPCS PDUs that could
be transmitted due to errors

ifOutDiscards Number of AAL5 CPCS PDUs received
transmission that are discarded
Possible reason may be output
overflow

ifInMulticastPkts Set to 0.

ifInBroadcastPkts Set to 0.

ifOutMulticastPkts Set to 0.

ifOutBroadcastPkts Set to 0.

ifName Textual name (unique on this system) of
AAL5 entity or an octet string of zero length

ifHighSpeed Set to 0.

ifConnectorPresent Set to false (2).

ifPromiscuousMode Set to false(2).

ifLinkUpDownTrapEnable Default is disabled (2).

8.4. Support of Proprietary Virtual Interface by

Specific interpretations of ifTable for the proprietary virtual
internal interface associated with an AAL5 entity in an ATM
are as follows

Object Use for proprietary virtual, internal
associated with AAL
====== ===============================================

ifIndex Each proprietary virtual, internal
associated with AAL entities is represented by

Ahmed & Tesink [Page 14]

RFC 1695 ATM Management Objects August 1994

ifEntry

ifDescr Description of the proprietary virtual,
interface associated with AAL entities

ifType The value that is allocated for
virtual, internal interface is 53.

ifSpeed See [5]. Set to 0 if the speed is
known

ifPhysAddress See [5]. An octet string of zero
if no address is used for this interface

ifAdminStatus See [5].

ifOperStatus See [5].

ifLastChange See [5].

ifName Textual name (unique on this system) of
interface or an octet string of zero length

ifHighSpeed See [5]. Set to 0 if the speed is not known

ifConnectorPresent Set to false (2).

ifLinkUpDownTrapEnable Default is disabled (2).

8.5. AAL5 Connection Performance Statistics

An AAL5 connection table is used to provide AAL5
information for each AAL5 virtual connection that is terminated
the AAL5 entity contained within an ATM switch or host

9. ILMI MIB and the ATM Managed

The ILMI MIB is specified by the ATM Forum in UNI specification [9],
to manage local ATM UNIs. The support of the ATM
functions by the ILMI MIB and those contained in this memo
compared in Table 1. In this table, "yes" in the "ILMI MIB"
indicates that the management functions are supported by the
MIB. The MIB groups in the "This memo" column are the groups
in Section 5.2.

For that subset of management information which the ILMI MIB and
memo have in common, every effort has been made to retain
semantics and syntax, even though the MIB objects are

Ahmed & Tesink [Page 15]

RFC 1695 ATM Management Objects August 1994

using different OBJECT IDENTIFIERs

Table 1 - Structuring of ATM Managed

______________________________________________________________
| |This |ILMI
ATM Mgmt.Inf. |ATM Managed Objects |memo |MIB |
______________|_________________________________|_______|____|

Local Interface Information
_____________________________________________________________
ATM interface:| (1) port identifier |ATM MIB| |
physical layer| (2) physical transmission types | gr.1*|yes*|
configuration | (3) operational status |MIB II | |
| (4) administrative status | | |
| (5) last change status | | |
_____________________________________________________________
ATM interface:| (1) active VPI/VCI fields |ATM MIB| |
cell layer | (2) maximum number of VPCs/VCCs | gr.1 |yes |
configuration | (3) configured VPCs/VCCs | | ** |
| (4) ILMI VPI/VCI values | | |
| (5) ATM address type | | |
| (6) ATM administrative address | | |
_____________________________________________________________
ATM interface:|(1) received/transmitted cells | | |
cell layer |(2) cells with HEC error |MIB II |yes |
performance |(3) cell header validation errors| | |
_____________________________________________________________
ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| |
PLCP & TC | framing seconds | gr.2,3| |
layer |(2)DS3 PLCP unavailable seconds | |no |
performance |(3)DS3 PLCP alarm state | | |
|(4)out of cell delineation events| | |
|(5)TC alarm state | | |
_____________________________________________________________
VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| |
configuration |(2)VCL or VPL operational status | gr. 4|yes |
|(3)VCL/VPL administrative status | |*** |
|(4)VCL/VPL last change status | | |
|(5)transmit/receive traffic/QoS | | |
| parameters | | |
|(6)AAL type | | |
|(7)transmit/receive AAL5 SDU size| | |
|(8)AAL5 encapsulation type | | |
_____________________________________________________________

Ahmed & Tesink [Page 16]

RFC 1695 ATM Management Objects August 1994

_____________________________________________________________
VP/VC |(1)cross-connect identifier | | |
Cross-connect:|(2)port identifier of one | | |
configuration | end | | |
|(3)port identifier of the other |ATM MIB| |
| end | gr. 5|no |
|(4)VPI or VPI/VCI value | | |
| of one end | | |
|(5)VPI or VPI/VCI value of | | |
| the other end | | |
|(6)VC/VP cross-connect | | |
| operational status | | |
|(7)VC/VP cross-connect | | |
| administrative status | | |
|(8)VC/VP last change status | | |
_____________________________________________________________
VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| |
layer: |(2)PDUs discarded due to | gr.6 | |
performance | reassembly time out | |no |
|(3)PDUs discarded due to large | | |
| SDUs | | |
_____________________________________________________________
AAL5 entity: |(1)received/transmitted PDUs | | |
|(2)PDUs discarded due to | | |
| protocol errors |MIB II |no |
|(3)a set of configuration/state | | |
| parameters | | |
_____________________________________________________________

*The operational, administrative, and last change status
the ATM interface and the physical transmission type shall
supported by the interface table in MIB II (RFC 1213,
1573). ILMI does not contain the administrative and
change status of the ATM interface

** The ILMI MIB does not contain information on the
address type and the ATM administrative address assigned
the ATM interface

***The ILMI MIB contains local and end-to-end
status of the VPC/VCC segment. However, it does not
the VPC/VCC administrative and last change status and the
AAL information

Ahmed & Tesink [Page 17]

RFC 1695 ATM Management Objects August 1994

10.

ATM-MIB DEFINITIONS ::=

MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY
Counter32, Integer32,
FROM SNMPv2-
TEXTUAL-CONVENTION, DisplayString
TimeStamp,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
ifIndex, mib-2
FROM RFC1213-MIB

atmMIB MODULE-
LAST-UPDATED "9406072245Z
ORGANIZATION "IETF AToM MIB Working Group
CONTACT-
" Masuma
Postal:
331 Newman Springs
Red Bank, NJ 07701

Tel: +1 908 758 2515
Fax: +1 908 758 4131
E-mail: mxa@mail.bellcore.

Kaj
Postal:
331 Newman Springs
Red Bank, NJ 07701

Tel: +1 908 758 5254
Fax: +1 908 758 4196
E-mail: kaj@cc.bellcore.com

"This is the MIB Module for ATM and AAL5-
objects for managing ATM interfaces, ATM
links, ATM cross-connects, AAL5 entities,
and AAL5 connections."
::= { mib-2 37 }

atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1}

-- This ATM MIB Module consists of the following groups

Ahmed & Tesink [Page 18]

RFC 1695 ATM Management Objects August 1994

-- (1) ATM Interface configuration
-- (2) ATM Interface DS3 PLCP
-- (3) ATM Interface TC Sublayer
-- (4) ATM Interface VPL configuration
-- (5) ATM Interface VCL configuration
-- (6) ATM VP Cross Connect
-- (7) ATM VC Cross Connect
-- (8) ATM Interface AAL5 VCC performance
--

IfIndex ::= TEXTUAL-
STATUS

"The value of this object identifies the
for which the entry contains
information. The value of this object for
particular interface has the same value as
ifIndex object, defined in RFC 1213, for the
interface."
SYNTAX Integer32

AtmTrafficDescrParamIndex ::= TEXTUAL-
STATUS

"The value of this object identifies the
in the atmTrafficDescrParamTable."
SYNTAX Integer32

atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=
{atmMIBObjects 1}

-- The following values are defined for use
-- possible values of the ATM traffic descriptor type
-- ATM Forum specified seven types of ATM
-- descriptors

atmNoTrafficDescriptor OBJECT-
STATUS

"This identifies the no ATM traffic
type. Parameters 1, 2, 3, 4, and 5 are not used
This traffic descriptor type can be used
best effort traffic."
::= { atmTrafficDescriptorTypes 1}

atmNoClpNoScr OBJECT-

Ahmed & Tesink [Page 19]

RFC 1695 ATM Management Objects August 1994

STATUS

"This traffic descriptor is for no CLP
no Sustained Cell Rate. The use of
parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: not
Parameter 3: not
Parameter 4: not
Parameter 5: not used
This traffic descriptor type can be
for best effort traffic."
::= { atmTrafficDescriptorTypes 2}

atmClpNoTaggingNoScr OBJECT-
STATUS

"This traffic descriptor is for no CLP
tagging and no Sustained Cell Rate. The
of the parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: CLP=0 peak cell rate
cells per
Parameter 3: not
Parameter 4: not
Parameter 5: not used."
::= { atmTrafficDescriptorTypes 3}

atmClpTaggingNoScr OBJECT-
STATUS

"This traffic descriptor is for CLP
tagging and no Sustained Cell Rate.
use of the parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: CLP=0 peak cell rate
cells per second with
traffic tagged as CLP=1
Parameter 3: not
Parameter 4: not
Parameter 5: not used."
::= { atmTrafficDescriptorTypes 4}

atmNoClpScr OBJECT-
STATUS

Ahmed & Tesink [Page 20]

RFC 1695 ATM Management Objects August 1994

"This traffic descriptor is for no
with Sustained Cell Rate.
use of the parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: CLP=0+1 sustained cell rate
cells per
Parameter 3: CLP=0+1 maximum burst
in
Parameter 4: not
Parameter 5: not used."
::= { atmTrafficDescriptorTypes 5}

atmClpNoTaggingScr OBJECT-
STATUS

"This traffic descriptor is for
with Sustained Cell Rate and no tagging
The use of the parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: CLP=0 sustained cell rate
cells per
Parameter 3: CLP=0 maximum burst size in
Parameter 4: not
Parameter 5: not used."
::= { atmTrafficDescriptorTypes 6}

atmClpTaggingScr OBJECT-
STATUS

"This traffic descriptor is for
with tagging and Sustained Cell Rate
The use of the parameter vector for this type
Parameter 1: CLP=0+1 peak cell rate
cells per
Parameter 2: CLP=0 sustained cell rate
cells per second with
traffic tagged as CLP=1
Parameter 3: CLP=0 maximum burst size in
Parameter 4: not
Parameter 5: not used."
::= { atmTrafficDescriptorTypes 7}

-- ATM Interface Configuration Parameters

Ahmed & Tesink [Page 21]

RFC 1695 ATM Management Objects August 1994

-- This group contains ATM
-- configuration information associated
-- an ATM interface beyond
-- supported using the ifTable

atmInterfaceConfTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table contains ATM local
configuration parameters, one entry per
interface port."
::= { atmMIBObjects 2 }

atmInterfaceConfEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"This list contains ATM interface
parameters and state variables."
INDEX { ifIndex }
::= { atmInterfaceConfTable 1}

AtmInterfaceConfEntry ::= SEQUENCE {
atmInterfaceMaxVpcs INTEGER
atmInterfaceMaxVccs INTEGER
atmInterfaceConfVpcs INTEGER
atmInterfaceConfVccs INTEGER
atmInterfaceMaxActiveVpiBits INTEGER
atmInterfaceMaxActiveVciBits INTEGER
atmInterfaceIlmiVpi INTEGER
atmInterfaceIlmiVci INTEGER
atmInterfaceAddressType INTEGER
atmInterfaceAdminAddress OCTET STRING
atmInterfaceMyNeighborIpAddress IpAddress
atmInterfaceMyNeighborIfName
}

atmInterfaceMaxVpcs OBJECT-
SYNTAX INTEGER (0..4096)
MAX-ACCESS read-
STATUS

"The maximum number of VPCs (PVCs and SVCs
supported at this ATM interface. At the ATM UNI

Ahmed & Tesink [Page 22]

RFC 1695 ATM Management Objects August 1994

the maximum number of VPCs (PVCs and SVCs
ranges from 0 to 256 only."
::= { atmInterfaceConfEntry 1}

atmInterfaceMaxVccs OBJECT-
SYNTAX INTEGER (0..65536)
MAX-ACCESS read-
STATUS

"The maximum number of VCCs (PVCs and SVCs
supported at this ATM interface."
::= { atmInterfaceConfEntry 2}

atmInterfaceConfVpcs OBJECT-
SYNTAX INTEGER (0..4096)
MAX-ACCESS read-
STATUS

"The number of VPCs (PVCs and SVCs
configured for use at this ATM interface
At the ATM UNI, the configured number
VPCs (PVCs and SVCs) can range
0 to 256 only."
::= { atmInterfaceConfEntry 3}

atmInterfaceConfVccs OBJECT-
SYNTAX INTEGER (0..65536)
MAX-ACCESS read-
STATUS

"The number of VCCs (PVCs and SVCs
configured for use at the ATM interface."
::= { atmInterfaceConfEntry 4}

atmInterfaceMaxActiveVpiBits OBJECT-
SYNTAX INTEGER (0..12)
MAX-ACCESS read-
STATUS

"The maximum number of active VPI
configured for use at the ATM interface
At the ATM UNI, the maximum number of
VPI bits configured for use ranges
0 to 8 only."
::= { atmInterfaceConfEntry 5}

atmInterfaceMaxActiveVciBits OBJECT-
SYNTAX INTEGER (0..16)

Ahmed & Tesink [Page 23]

RFC 1695 ATM Management Objects August 1994

MAX-ACCESS read-
STATUS

"The maximum number of active VCI
configured for use at this ATM interface."
::= { atmInterfaceConfEntry 6}

atmInterfaceIlmiVpi OBJECT-
SYNTAX INTEGER (0..255)
MAX-ACCESS read-
STATUS

"The VPI value of the VCC
the ILMI at this ATM interface. If the values
atmInterfaceIlmiVpi and atmInterfaceIlmiVci
both equal to zero then the ILMI is
supported at this ATM interface."
DEFVAL { 0 }
::= { atmInterfaceConfEntry 7}

atmInterfaceIlmiVci OBJECT-
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-
STATUS

"The VCI value of the VCC
the ILMI at this ATM interface. If the values
atmInterfaceIlmiVpi and atmInterfaceIlmiVci
both equal to zero then the ILMI is
supported at this ATM interface."
DEFVAL { 16 }
::= { atmInterfaceConfEntry 8}

atmInterfaceAddressType OBJECT-
SYNTAX INTEGER {
private(1),
nsapE164(2),
nativeE164(3),
other(4)
}
MAX-ACCESS read-
STATUS

"The type of primary ATM address
for use at this ATM interface."
::= { atmInterfaceConfEntry 9 }

atmInterfaceAdminAddress OBJECT-

Ahmed & Tesink [Page 24]

RFC 1695 ATM Management Objects August 1994

SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-
STATUS

"An address assigned for administrative purposes
for example, an address associated with
service provider side of a public network UNI
If this interface has no assigned
address, or when the address used
administrative purposes is the same as that
for ifPhysAddress, then this is an octet string
zero length."
::= { atmInterfaceConfEntry 10 }

atmInterfaceMyNeighborIpAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The IP address of the neighbor system connected
the far end of this interface, to which a
Management Station can send SNMP messages, as
datagrams sent to UDP port 161, in order to
network management information concerning
operation of that system. Note that the
of this object may be obtained in different ways
e.g., by manual configuration, or through
interaction with the neighbor system."
::= { atmInterfaceConfEntry 11 }

atmInterfaceMyNeighborIfName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The textual name of the interface on the
system on the far end of this interface, and
which this interface connects. If the
system is manageable through SNMP and
the object ifName, the value of this object
be identical with that of ifName for the
of the lowest level physical
for this port. If this interface does not have
textual name, the value of this object is a
length string. Note that the value of this
may be obtained in different ways, e.g., by
configuration, or through ILMI interaction
the neighbor system."

Ahmed & Tesink [Page 25]

RFC 1695 ATM Management Objects August 1994

::= { atmInterfaceConfEntry 12 }

-- The ATM Interface DS3 PLCP

-- This group contains the DS3 PLCP configuration
-- state parameters of those ATM
-- which use DS3 PLCP for carrying ATM cells over DS3.

atmInterfaceDs3PlcpTable OBJECT-
SYNTAX SEQUENCE OF AtmInterfaceDs3
MAX-ACCESS not-
STATUS

"This table contains ATM interface DS3
parameters and state variables, one entry
ATM interface port."
::= { atmMIBObjects 3}

atmInterfaceDs3PlcpEntry OBJECT-
SYNTAX AtmInterfaceDs3
MAX-ACCESS not-
STATUS

"This list contains DS3 PLCP parameters
state variables at the ATM interface."
INDEX {ifIndex }
::= { atmInterfaceDs3PlcpTable 1}

AtmInterfaceDs3PlcpEntry ::= SEQUENCE {
atmInterfaceDs3PlcpSEFSs Counter32,
atmInterfaceDs3PlcpAlarmState INTEGER
atmInterfaceDs3PlcpUASs Counter32
}

atmInterfaceDs3PlcpSEFSs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The number of DS3 PLCP Severely Errored
Second (SEFS). Each SEFS represents
one-second interval which
one or more SEF event."
::= { atmInterfaceDs3PlcpEntry 1}

atmInterfaceDs3PlcpAlarmState OBJECT-

Ahmed & Tesink [Page 26]

RFC 1695 ATM Management Objects August 1994

SYNTAX INTEGER {
noAlarm(1),
receivedFarEndAlarm(2),
incomingLOF(3)
}
MAX-ACCESS read-
STATUS

"This variable indicates if there is
alarm present for the DS3 PLCP. The
receivedFarEndAlarm means that the DS3
has received an incoming
Signal, the value incomingLOF means
the DS3 PLCP has declared a loss of frame (LOF
failure condition, and the value
means that there are no alarms present
Transition from the failure to the no alarm
occurs when no defects (e.g., LOF) are
for more than 10 seconds."
::= { atmInterfaceDs3PlcpEntry 2}

atmInterfaceDs3PlcpUASs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The counter associated with the number
Unavailable Seconds encountered by the PLCP."
::= { atmInterfaceDs3PlcpEntry 3}

-- The ATM Interface TC Sublayer

-- This group contains TC sublayer configuration
-- state parameters of those ATM
-- which use TC sublayer for carrying ATM cells
-- SONET or DS3.

atmInterfaceTCTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table contains ATM interface
Sublayer parameters and state variables
one entry per ATM interface port."
::= { atmMIBObjects 4}

Ahmed & Tesink [Page 27]

RFC 1695 ATM Management Objects August 1994

atmInterfaceTCEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"This list contains TC Sublayer
and state variables at the ATM interface."
INDEX {ifIndex }
::= { atmInterfaceTCTable 1}

AtmInterfaceTCEntry ::= SEQUENCE {
atmInterfaceOCDEvents Counter32,
atmInterfaceTCAlarmState
}

atmInterfaceOCDEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS

"The number of times the Out of
Delineation (OCD) events occur. If
consecutive ATM cells have Header
Control (HEC) violations, an OCD event occurs
A high number of OCD events may indicate
problem with the TC Sublayer."
::= { atmInterfaceTCEntry 1}

atmInterfaceTCAlarmState OBJECT-
SYNTAX INTEGER {
noAlarm(1),
lcdFailure(2)
}
MAX-ACCESS read-
STATUS

"This variable indicates if there is
alarm present for the TC Sublayer. The
lcdFailure indicates that a Loss
Cell Delineation (LCD) failure state has
declared for the TC Sublayer. Transition
failure to the no alarm state
when 6 consecutive ATM
are received with valid HEC, followed
about 10 seconds of acceptable working signal."
::= { atmInterfaceTCEntry 2}

Ahmed & Tesink [Page 28]

RFC 1695 ATM Management Objects August 1994

-- ATM Traffic Descriptor Parameter

-- This group contains a set of self-
-- ATM traffic parameters including
-- ATM traffic QoS Class

-- The ATM virtual link tables (i.e., VPL and VCL tables
-- will use this ATM Traffic Descriptor
-- to assign traffic parameters and QoS
-- to the receive and transmit directions
-- the ATM virtual links (i.e., VPLs and VCLs).
-- The ATM VPL or VCL table will indicate a
-- in the
-- using its atmTrafficDescrParamIndex value
-- The management application can then compare a set
-- ATM traffic parameters with a single value

-- If no suitable row(s) in the
-- exists, the manager must create a new row(s) in
-- table. If such a row is created, agent checks
-- sanity of that set of ATM traffic parameter values

-- When creating a new row, the parameter
-- will be checked for self-consistency
-- Predefined/template rows may be supported

-- A row in the atmTrafficDescrParamTable is
-- by setting the atmTrafficDescrRowStatus to destroy(6).
-- The agent will check whether this row is still in
-- by any entry of the atmVplTable or atmVclTable
-- The agent denies the request if the row is still
-- use

-- The ATM Traffic Descriptor Parameter

atmTrafficDescrParamTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"This table contains information on ATM
descriptor type and the associated parameters."
::= { atmMIBObjects 5}

atmTrafficDescrParamEntry OBJECT-
SYNTAX
MAX-ACCESS not-

Ahmed & Tesink [Page 29]

RFC 1695 ATM Management Objects August 1994

STATUS

"This list contains ATM traffic
type and the associated parameters."
INDEX {atmTrafficDescrParamIndex
::= { atmTrafficDescrParamTable 1}

AtmTrafficDescrParamEntry ::= SEQUENCE {
atmTrafficDescrParamIndex AtmTrafficDescrParamIndex
atmTrafficDescrType OBJECT IDENTIFIER
atmTrafficDescrParam1 Integer32,
atmTrafficDescrParam2 Integer32,
atmTrafficDescrParam3 Integer32,
atmTrafficDescrParam4 Integer32,
atmTrafficDescrParam5 Integer32,
atmTrafficQoSClass INTEGER
atmTrafficDescrRowStatus
}

atmTrafficDescrParamIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"This object is used by the virtual
table (i.e., VPL or VCL table
to identify the row of this table."
::= { atmTrafficDescrParamEntry 1}

atmTrafficDescrType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS

"The value of this object identifies the
of ATM traffic descriptor
The type may indicate no traffic descriptor
traffic descriptor with one or more parameters
These parameters are specified as a
vector, in the corresponding instances of
objects
atmTrafficDescrParam
atmTrafficDescrParam
atmTrafficDescrParam
atmTrafficDescrParam
atmTrafficDescrParam5."
DEFVAL { atmNoTrafficDescriptor }
::= { atmTrafficDescrParamEntry 2}

Ahmed & Tesink [Page 30]

RFC 1695 ATM Management Objects August 1994

atmTrafficDescrParam1 OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The first parameter of the ATM traffic
used according to the value
atmTrafficDescrType."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 3}

atmTrafficDescrParam2 OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The second parameter of the ATM traffic
used according to the value
atmTrafficDescrType."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 4}

atmTrafficDescrParam3 OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The third parameter of the ATM traffic
used according to the value
atmTrafficDescrType."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 5}

atmTrafficDescrParam4 OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The fourth parameter of the ATM traffic
used according to the value
atmTrafficDescrType."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 6}

atmTrafficDescrParam5 OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

Ahmed & Tesink [Page 31]

RFC 1695 ATM Management Objects August 1994

"The fifth parameter of the ATM traffic
used according to the value
atmTrafficDescrType."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 7}

atmTrafficQoSClass OBJECT-
SYNTAX INTEGER (0..255)
MAX-ACCESS read-
STATUS

"The value of this object identifies the QoS Class
Four Service classes have
specified in the ATM Forum UNI Specification
Service Class A: Constant bit rate video
Circuit
Service Class B: Variable bit rate video/
Service Class C: Connection-oriented
Service Class D: Connectionless
Four QoS classes numbered 1, 2, 3, and 4
been specified with the aim to support
classes A, B, C, and D respectively
An unspecified QoS Class numbered `0' is
for best effort traffic."
DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 8}

atmTrafficDescrRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"This object is used to
a new row or modify or delete
existing row in this table."
DEFVAL { active }
::= {atmTrafficDescrParamEntry 9}

-- ATM Interface Virtual Path Link (VPL)

-- This group contains configuration and
-- information of a bi-directional Virtual Path
-- (VPL

-- This table can be used to create, delete or

Ahmed & Tesink [Page 32]

RFC 1695 ATM Management Objects August 1994

-- a VPL that is terminated in an ATM host or switch
-- This table can also be used to create, delete
-- modify a VPL which is cross-connected to
-- VPL

-- In the example below, the traffic flows on the
-- and transmit directions of the VPLs are
-- by atmVplReceiveTrafficDescrIndex
-- atmVplTransmitTrafficDescrIndex respectively
-- The cross-connected VPLs are identified
-- atmVplCrossConnectIdentifier

-- ________________________________
-- | |
-- VPL | ATM Host, Switch, or Network |
-- receive | |
-- ========> X X <=======
-- <======== X X ========>
-- transmit | |
-- |______________________________|

-- The ATM Interface VPL

atmVplTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The Virtual Path Link (VPL) table.
bi-directional VPL is modeled as one
in this table."
::= { atmMIBObjects 6}

atmVplEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry in the VPL table. This entry
used to model a bi-directional VPL
To create a VPL at an ATM interface
either of the following procedures are used

Ahmed & Tesink [Page 33]

RFC 1695 ATM Management Objects August 1994

Negotiated VPL

(1) The management application
a VPL entry in the
by setting atmVplRowStatus to createAndWait(5).
This may fail for the following reasons
- The selected VPI value is unavailable
- The selected VPI value is in use
Otherwise, the agent creates a row
reserves the VPI value on that port

(2) The manager selects an existing row(s) in
atmTrafficDescrParamTable
thereby, selecting a set of self-
ATM traffic parameters and the QoS
for receive and transmit directions of the VPL

(2a) If no suitable row(s) in
atmTrafficDescrParamTable exists
the manager must create a new row(s
in that table

(2b) The manager characterizes the VPL's
parameters through setting
atmVplReceiveTrafficDescrIndex and
atmVplTransmitTrafficDescrIndex
in the VPL table, which point to the
containing desired ATM traffic parameter
in the atmTrafficDescrParamTable. The
will check the availability of resources
may refuse the request

(3) The manager activates the VPL by setting
the atmVplRowStatus to active(1).
If this set is successful, the agent
reserved the resources to satisfy the
traffic parameter values and the QoS
for that VPL
(4) If the VPL terminates a VPC in the ATM
or switch, the manager turns on
atmVplAdminStatus to up(1) to turn the
traffic flow on. Otherwise,
atmVpCrossConnectTable must be
to cross-connect the VPL to another VPL(s
in an ATM switch or network

One-Shot VPL

Ahmed & Tesink [Page 34]

RFC 1695 ATM Management Objects August 1994

A VPL may also be established in one step by
set-request with all necessary VPL
values and atmVplRowStatus set to createAndGo(4).

In contrast to the negotiated VPL
which allows for detailed error
(i.e., set errors are explicitly linked
particular resource acquisition failures),
the one-shot VPL
performs the setup on one operation
does not have the advantage of step-
error checking

VPL

A VPL is released by setting atmVplRowStatus
destroy(6), and the agent may release
associated resources."
INDEX {ifIndex, atmVplVpi }
::= { atmVplTable 1}

AtmVplEntry ::= SEQUENCE {
atmVplVpi INTEGER
atmVplAdminStatus INTEGER
atmVplOperStatus INTEGER
atmVplLastChange TimeStamp

AtmTrafficDescrParamIndex

AtmTrafficDescrParamIndex
atmVplCrossConnectIdentifier INTEGER
atmVplRowStatus
}

atmVplVpi OBJECT-
SYNTAX INTEGER (1..4095)
MAX-ACCESS not-
STATUS

"The VPI value of the VPL
Note that the VPI=0 is not
for a VPL not associated with a VCL
The maximum VPI value
exceed the value allowable by
atmInterfaceMaxVpiBits."
::= { atmVplEntry 1}

Ahmed & Tesink [Page 35]

RFC 1695 ATM Management Objects August 1994

atmVplAdminStatus OBJECT-
SYNTAX INTEGER {
up(1),
down(2)
}
MAX-ACCESS read-
STATUS

"This object is implemented only for a VPL
terminates a VPC (i.e.,
one which is NOT cross-connected to other VPLs).
Its value specifies the desired
state of the VPL. The up and down states
that the traffic flow is enabled and
respectively for this VPL."
DEFVAL { down }
::= { atmVplEntry 2}

atmVplOperStatus OBJECT-
SYNTAX INTEGER {
up(1),
down(2),
unknown(3)
}
MAX-ACCESS read-
STATUS

"This object indicates the current
status of the VPL. The up and down
indicate that the VPL is
operational, or not operational, respectively
The unknown state indicates that