< draft-ietf-atommib-atm1ng-05.txt   draft-ietf-atommib-atm1ng-06.txt >
Definitions of Managed Objects Definitions of Managed Objects
for ATM Management for ATM Management
August 15, 1998 October 19, 1998
Kaj Tesink (editor) Kaj Tesink (editor)
Bell Communications Research Bell Communications Research
331 Newman Springs Road 331 Newman Springs Road
Red Bank, NJ 07701 Red Bank, NJ 07701
kaj@cc.bellcore.com kaj@bellcore.com
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 2, line ? skipping to change at page 2, line ?
check the ``1id-abstracts.txt'' listing contained in the check the ``1id-abstracts.txt'' listing contained in the
Internet- Drafts Shadow Directories on ftp.ietf.org (US East Internet- Drafts Shadow Directories on ftp.ietf.org (US East
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast),
or munnari.oz.au (Pacific Rim). or munnari.oz.au (Pacific Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Copyright (C) The Internet Society (1998). All Rights
Reserved. Reserved.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines a portion of the Management Information Base
Information Base (MIB) for use with network management (MIB) for use with network management protocols in the
protocols in the Internet community. In particular, it Internet community. In particular, it describes objects used
describes objects used for managing ATM-based interfaces, for managing ATM-based interfaces, devices, networks and
devices, networks and services. services.
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.
This memo specifies a MIB module in a manner that is both This memo replaces RFC1695[24].Changes relative to RFC1695 are
compliant to the SNMPv2 SMI[5], and semantically identical to summarized in the MIB module's REVISION clause.
the peer SNMPv1 definitions.
Textual Conventions used in this MIB are defined in [6] and Textual Conventions used in this MIB are defined in [6] and
[19]. [19].
3. The SNMP Network Management Framework 2. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
0 An overall architecture, described in RFC 2271 [1]. 0 An overall architecture, described in RFC 2271 [1].
0 Mechanisms for describing and naming objects and events 0 Mechanisms for describing and naming objects and events
for the purpose of management. The first version of this for the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 Structure of Management Information (SMI) is called SMIv1
and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215
skipping to change at page 3, line 4 skipping to change at page 2, line ?
RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
0 Message protocols for transferring management 0 Message protocols for transferring management
information. The first version of the SNMP message information. The first version of the SNMP message
protocol is called SNMPv1 and described in RFC 1157 [8]. protocol is called SNMPv1 and described in RFC 1157 [8].
A second version of the SNMP message protocol, which is A second version of the SNMP message protocol, which is
not an Internet standards track protocol, is called not an Internet standards track protocol, is called
SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called The third version of the message protocol is called
SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and
draft ATM Management Objects August 15, 1998
RFC 2274 [12]. RFC 2274 [12].
0 Protocol operations for accessing management information. 0 Protocol operations for accessing management information.
The first set of protocol operations and associated PDU The first set of protocol operations and associated PDU
formats is described in RFC 1157 [8]. A second set of formats is described in RFC 1157 [8]. A second set of
protocol operations and associated PDU formats is protocol operations and associated PDU formats is
described in RFC 1905 [13]. described in RFC 1905 [13].
draft ATM Management Objects October 19, 1998
0 A set of fundamental applications described in RFC 2273 0 A set of fundamental applications described in RFC 2273
[14] and the view-based access control mechanism [14] and the view-based access control mechanism
described in RFC 2275 [15]. described in RFC 2275 [15].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the termed the Management Information Base or MIB. Objects in the
MIB are defined using the mechanisms defined in the SMI. MIB are defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the This memo specifies a MIB module that is compliant to the
SMIv2. A MIB conforming to the SMIv1 can be produced through SMIv2. A MIB conforming to the SMIv1 can be produced through
the appropriate translations. The resulting translated MIB the appropriate translations. The resulting translated MIB
must be semantically equivalent, except where objects or must be semantically equivalent, except where objects or
events are omitted because no translation is possible (e.g., events are omitted because no translation is possible (e.g.,
use of Counter64). Some machine readable information in SMIv2 use of Counter64). Some machine readable information in SMIv2
will be converted into textual descriptions in SMIv1 during will be converted into textual descriptions in SMIv1 during
the translation process. However, this loss of machine the translation process. However, this loss of machine
readable information is not considered to change the semantics readable information is not considered to change the semantics
of the MIB. of the MIB.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
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.
draft ATM Management Objects August 15, 1998
5. ATM Terminology 3. ATM Terminology
Some basic ATM terminologies are described in this section to Some basic ATM terminologies are described in this section to
facilitate defining the ATM managed objects. facilitate defining the ATM managed objects.
5.1. VCL/VPL and VCC/VPC 3.1. VCL/VPL and VCC/VPC
There are two distinct types of ATM virtual connections: There are two distinct types of ATM virtual connections:
Virtual Channel Connections (VCCs) and Virtual Path Connection Virtual Channel Connections (VCCs) and Virtual Path Connection
(VPCs). As shown in Figures 1 and 2, ATM virtual connections (VPCs). As shown in Figures 1 and 2, ATM virtual connections
consist of concatenated series of virtual links which forms a consist of concatenated series of virtual links which forms a
path between two end points, with each concatenation occurring path between two end points, with each concatenation occurring
at an ATM switch. Virtual links of VCCs are called Virtual at an ATM switch. Virtual links of VCCs are called Virtual
Channel Links (VCLs). Virtual links of VPCs are called Virtual Channel Links (VCLs). Virtual links of VPCs are called Virtual
Path Links (VPLs). The VCI and VPI fields in the ATM cell Path Links (VPLs). The VCI and VPI fields in the ATM cell
header associate each cell of a VCC with a particular VCL over header associate each cell of a VCC with a particular VCL over
skipping to change at page 6, line 5 skipping to change at page 5, line 5
|X-Connect | |X-Connect | |X-Connect | |X-Connect |
VCL1 |Point | VCL2 |Point | VCL3 VCL1 |Point | VCL2 |Point | VCL3
O---------|----X-----|-------|-----|----X-----|-------O O---------|----X-----|-------|-----|----X-----|-------O
| | | | | | | |
------------ ------------ ------------ ------------
ATM Switch ATM Switch ATM Switch ATM Switch
Figure 1: Virtual Channel Links and Figure 1: Virtual Channel Links and
Virtual Channel Connection Virtual Channel Connection
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
<-----------------------VPC--------------------------> <-----------------------VPC-------------------------->
------------ ----------- ------------ -----------
|ATM | |ATM | |ATM | |ATM |
|X-Connect | |X-Connect | |X-Connect | |X-Connect |
VPL1 |Point | VPL2 |Point | VPL3 VPL1 |Point | VPL2 |Point | VPL3
O---------|----X-----|-------|-----|----X-----|-------O O---------|----X-----|-------|-----|----X-----|-------O
| | | | | | | |
------------ ------------ ------------ ------------
ATM Switch ATM Switch ATM Switch ATM Switch
skipping to change at page 7, line 5 skipping to change at page 6, line 5
achieved only by appropriate management of its individual achieved only by appropriate management of its individual
pieces in combination. pieces in combination.
Note that for management purposes, an ATM network may be Note that for management purposes, an ATM network may be
viewed as a large distributed switch by hiding all the viewed as a large distributed switch by hiding all the
network's internal connectivity as being internal to the network's internal connectivity as being internal to the
distributed switch (as shown in Figure 2a). This model may distributed switch (as shown in Figure 2a). This model may
for example be used for Customer Network Management (CNM) for example be used for Customer Network Management (CNM)
purposes. purposes.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
<---------------------VCC---------------------------> <---------------------VCC--------------------------->
-------------------------------------- --------------------------------------
| | | |
| ---------- ---------- | | ---------- ---------- |
| | ATM | | ATM | | | | ATM | | ATM | |
VCL1 | | Switch | | Switch | | VCL3 VCL1 | | Switch | | Switch | | VCL3
O-------|-|--------|------/-------|--------|-|------O O-------|-|--------|------/-------|--------|-|------O
| | | | | | | | | | | |
| ---------- ---------- | | ---------- ---------- |
skipping to change at page 7, line 37 skipping to change at page 6, line 37
traffic parameters in the two directions of a connection can traffic parameters in the two directions of a connection can
be symmetric or asymmetric, i.e., the two directions can have be symmetric or asymmetric, i.e., the two directions can have
the same or different traffic flows. A uni-directional the same or different traffic flows. A uni-directional
traffic flow across a VCC is achieved by assigning a zero traffic flow across a VCC is achieved by assigning a zero
bandwidth in one direction. Note that in addition to the bandwidth in one direction. Note that in addition to the
bandwidth required by the user traffic flow, bandwidth is also bandwidth required by the user traffic flow, bandwidth is also
required for OAM cell flows, even for the zero-bandwidth required for OAM cell flows, even for the zero-bandwidth
direction of a uni-directional connection. These same direction of a uni-directional connection. These same
principles apply to VPCs. principles apply to VPCs.
5.2. PVC, SVC and Soft PVC 3.2. PVC, SVC and Soft PVC
A Permanent Virtual Connection (PVC) is a provisioned VCC or A Permanent Virtual Connection (PVC) is a provisioned VCC or
VPC. A Switched Virtual Connection (SVC) is a switched VCC or VPC. A Switched Virtual Connection (SVC) is a switched VCC or
VPC that is set up in real-time via call set-up signaling VPC that is set up in real-time via call set-up signaling
procedures. A PVC (or an SVC) can be a point-to-point, procedures. A PVC (or an SVC) can be a point-to-point,
point-to-multipoint, or multipoint-to-multipoint VCC or VPC. point-to-multipoint, or multipoint-to-multipoint VCC or VPC.
A Soft PVC is a connection of which portions are switched, A Soft PVC is a connection of which portions are switched,
while other portions are permanent (see Figure 3 and [22]). while other portions are permanent (see Figure 3 and [22]).
+--------+ +--------+ +--------+ draft ATM Management Objects October 19, 1998
draft ATM Management Objects August 15, 1998
+--------+ +--------+ +--------+
pvc| ATM |svc svc | ATM |svc svc | ATM |pvc pvc| ATM |svc svc | ATM |svc svc | ATM |pvc
----| Switch |-----------| Switch |-----------| Switch |---- ----| Switch |-----------| Switch |-----------| Switch |----
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+
Figure 3: An example of a Soft PVC Figure 3: An example of a Soft PVC
5.3. Traffic Management Parameters 3.3. Traffic Management Parameters
5.3.1. Traffic Policing and Traffic Shaping Parameters 3.3.1. Traffic Policing and Traffic Shaping Parameters
In order to allocate resources fairly among different users, In order to allocate resources fairly among different users,
some networks police traffic at resource access points. The some networks police traffic at resource access points. The
traffic enforcement or policing taken at a UNI is called Usage traffic enforcement or policing taken at a UNI is called Usage
Parameter Control (UPC) and is conceptually activated on an Parameter Control (UPC) and is conceptually activated on an
incoming VCL or VPL as shown in Figure 4. The use of the incoming VCL or VPL as shown in Figure 4. The use of the
traffic enforcer at the ingress of the connection is to make traffic enforcer at the ingress of the connection is to make
sure that the user traffic does not exceed the negotiated sure that the user traffic does not exceed the negotiated
traffic parameters such as the peak cell rate associated with traffic parameters such as the peak cell rate associated with
a specific traffic descriptor type. a specific traffic descriptor type.
skipping to change at page 8, line 44 skipping to change at page 8, line 5
Figure 4: An Example of a UPC Figure 4: An Example of a UPC
In addition, traffic shaping may be performed on an outgoing In addition, traffic shaping may be performed on an outgoing
VPL or VCL at a given ATM interface. The function of the ATM VPL or VCL at a given ATM interface. The function of the ATM
traffic shaper, conceptually either at the source or an egress traffic shaper, conceptually either at the source or an egress
point of the connection, is to smooth the outgoing cell point of the connection, is to smooth the outgoing cell
traffic inter-arrival time. If policing or shaping is not traffic inter-arrival time. If policing or shaping is not
performed then the policing or shaping algorithm is not performed then the policing or shaping algorithm is not
activated. activated.
5.3.2. Cell Loss Priority draft ATM Management Objects October 19, 1998
3.3.2. Cell Loss Priority
To prioritize traffic during resource congestion, ATM cells To prioritize traffic during resource congestion, ATM cells
are assigned one of the two types of Cell Loss Priority (CLP), are assigned one of the two types of Cell Loss Priority (CLP),
draft ATM Management Objects August 15, 1998
CLP=0 and CLP=1. ATM cells with CLP=0 have a higher priority CLP=0 and CLP=1. ATM cells with CLP=0 have a higher priority
in regard to cell loss than ATM cells with CLP=1. Therefore, in regard to cell loss than ATM cells with CLP=1. Therefore,
during resource congestions, CLP=1 cells are dropped before during resource congestions, CLP=1 cells are dropped before
any CLP=0 cell is dropped. any CLP=0 cell is dropped.
5.3.3. QoS Class 3.3.3. QoS Class
RFC1695 specified that one of a number of Quality of Service RFC1695 specified that one of a number of Quality of Service
(QoS) classes is assigned to a VCC or VPC by associating the (QoS) classes is assigned to a VCC or VPC by associating the
object atmTrafficQoSClass with each VCL or VPL. However, new object atmTrafficQoSClass with each VCL or VPL. However, new
insights in ATM traffic management have caused this object to insights in ATM traffic management have caused this object to
be deprecated. be deprecated.
5.3.4. Service Category 3.3.4. Service Category
Replacing QoS Class, VPLs and VCLs are qualified in terms of Replacing QoS Class, VPLs and VCLs are qualified in terms of
their service category (atmServiceCategory). When properly their service category (atmServiceCategory). When properly
configured, VCLs (or VPLs) concatenated to form a VCC (or VPC) configured, VCLs (or VPLs) concatenated to form a VCC (or VPC)
will all have the same service category class as that of the will all have the same service category class as that of the
VCC (or VPC). VCC (or VPC).
5.4. Max Active and Max Current VPI and VCI Bits 3.4. Max Active and Max Current VPI and VCI Bits
A manager may wish to configure the maximum number of VPI and A manager may wish to configure the maximum number of VPI and
VCI bits that can be used to identify VPIs and VCIs on a given VCI bits that can be used to identify VPIs and VCIs on a given
ATM interface. This value can be less than or equal to the ATM interface. This value can be less than or equal to the
maximum number of bits supported by the interface hardware, maximum number of bits supported by the interface hardware,
and is referred to in the MIB as the Max Active VPI Bits and and is referred to in the MIB as the Max Active VPI Bits and
Max Active VCI Bits. Max Active VCI Bits.
However, a manager may not be able to configure the Max Active However, a manager may not be able to configure the Max Active
Bits on both ends of an ATM link. For example, the manager Bits on both ends of an ATM link. For example, the manager
may not be allowed write access to the peer's MIB, or there may not be allowed write access to the peer's MIB, or there
may be hardware limitations on the peer device. Therefore, may be hardware limitations on the peer device. Therefore,
the two ATM devices may use ILMI to negotiate "Max Current" the two ATM devices may use ILMI to negotiate "Max Current"
VPI and VCI bits, which is the maximum number of bits that VPI and VCI bits, which is the maximum number of bits that
both interfaces are willing to support. This is illustrated both interfaces are willing to support. This is illustrated
in Figure 5. The relationship between the different parameters in Figure 5. The relationship between the different parameters
draft ATM Management Objects October 19, 1998
is illustrated in Figure 6. Note that if ILMI negotiation is is illustrated in Figure 6. Note that if ILMI negotiation is
not supported, then the devices have no choice but to use the not supported, then the devices have no choice but to use the
configured Max Active bits, and assume that it has been configured Max Active bits, and assume that it has been
configured to the same value on both ends of the link. configured to the same value on both ends of the link.
draft ATM Management Objects August 15, 1998
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+
| ATM | IF a IF b | ATM | IF c IF d | ATM | | ATM | IF a IF b | ATM | IF c IF d | ATM |
| Device |--------------| Device |--------------| Device | | Device |--------------| Device |--------------| Device |
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+
IF a: Max Active VPI Bits = 6 (configured) IF a: Max Active VPI Bits = 6 (configured)
Max Current VPI Bits = 6 (negotiated) Max Current VPI Bits = 6 (negotiated)
IF b: Max Active VPI Bits = 8 (configured) IF b: Max Active VPI Bits = 8 (configured)
Max Current VPI Bits = 6 (negotiated) Max Current VPI Bits = 6 (negotiated)
skipping to change at page 10, line 44 skipping to change at page 10, line 5
| | | | | | | | | |
+----------------------------------------------------+ +----------------------------------------------------+
^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | |
Max bits Max Bits Max Max Max bits Max Bits Max Max
supported supported Active (config.) current (negotiated) supported supported Active (config.) current (negotiated)
by MIB by h/w Bits Bits by MIB by h/w Bits Bits
Figure 6 Figure 6
6. Overview draft ATM Management Objects October 19, 1998
4. Overview
ATM management objects are used to manage ATM interfaces, ATM ATM management objects are used to manage ATM interfaces, ATM
virtual links, ATM cross-connects, AAL5 entities and AAL5 virtual links, ATM cross-connects, AAL5 entities and AAL5
connections supported by ATM hosts, ATM switches and ATM connections supported by ATM hosts, ATM switches and ATM
draft ATM Management Objects August 15, 1998
networks. This section provides an overview and background of networks. This section provides an overview and background of
how to use this MIB and other potential MIBs for this purpose. how to use this MIB and other potential MIBs for this purpose.
The purpose of this memo is primarily to manage ATM PVCs. ATM The purpose of this memo is primarily to manage ATM PVCs. ATM
SVCs are also represented by the management information in SVCs are also represented by the management information in
this MIB. However, full management of SVCs may require this MIB. However, full management of SVCs may require
additional capabilities which are beyond the scope of this additional capabilities which are beyond the scope of this
memo. memo.
6.1. Background 4.1. Background
In addition to the MIB module defined in this memo, other MIB In addition to the MIB module defined in this memo, other MIB
modules are necessary to manage ATM interfaces, links and modules are necessary to manage ATM interfaces, links and
cross-connects. Examples include MIB II for general system cross-connects. Examples include MIB II for general system
and interface management [16][17], the DS3 or SONET MIBs for and interface management [16][17], the DS3 or SONET MIBs for
management of physical interfaces, and, as appropriate, MIB management of physical interfaces, and, as appropriate, MIB
modules for applications that make use of ATM, such as SMDS. modules for applications that make use of ATM, such as SMDS.
These MIB modules are outside the scope of this specification. These MIB modules are outside the scope of this specification.
The current specification of this ATM MIB is based on SNMPv2- The current specification of this ATM MIB is based on SNMPv2-
SMI. SMI.
6.2. Structure of the MIB 4.2. Structure of the MIB
The managed ATM objects are arranged into the following The managed ATM objects are arranged into the following
tables: tables:
(1) ATM interface configuration table (1) ATM interface configuration table
(2) ATM interface DS3 PLCP and TC sublayer tables (2) ATM interface DS3 PLCP and TC sublayer tables
(3) ATM traffic parameter table (3) ATM traffic parameter table
(4) ATM interface virtual link (VPL/VCL) configuration (4) ATM interface virtual link (VPL/VCL) configuration
tables tables
(5) ATM VP/VC cross-connect tables (5) ATM VP/VC cross-connect tables
(6) AAL5 connection performance statistics table (6) AAL5 connection performance statistics table
Note that, managed objects for activation/deactivation of OAM Note that, managed objects for activation/deactivation of OAM
cell flows and ATM traps notifying virtual connection or cell flows and ATM traps notifying virtual connection or
virtual link failures are outside the scope of this memo. virtual link failures are outside the scope of this memo.
6.3. ATM Interface Configuration Table draft ATM Management Objects October 19, 1998
4.3. ATM Interface Configuration Table
This table contains information on ATM cell layer This table contains information on ATM cell layer
configuration of local ATM interfaces on an ATM device in configuration of local ATM interfaces on an ATM device in
addition to the information on such interfaces contained in addition to the information on such interfaces contained in
draft ATM Management Objects August 15, 1998
the ifTable. the ifTable.
6.4. ATM Interface DS3 PLCP and TC Layer Tables 4.4. ATM Interface DS3 PLCP and TC Layer Tables
These tables provide performance statistics of the DS3 PLCP These tables provide performance statistics of the DS3 PLCP
and TC sublayer of local ATM interfaces on a managed ATM and TC sublayer of local ATM interfaces on a managed ATM
device. DS3 PLCP and TC sublayer are currently used to carry device. DS3 PLCP and TC sublayer are currently used to carry
ATM cells respectively over DS3 and SONET transmission paths. ATM cells respectively over DS3 and SONET transmission paths.
6.5. ATM Virtual Link and Cross-Connect Tables 4.5. ATM Virtual Link and Cross-Connect Tables
ATM virtual link and cross-connect tables model bi-directional ATM virtual link and cross-connect tables model bi-directional
ATM virtual links and ATM cross-connects. The ATM VP/VC link ATM virtual links and ATM cross-connects. The ATM VP/VC link
tables are implemented in an ATM host, ATM switch and ATM tables are implemented in an ATM host, ATM switch and ATM
network. The ATM switch and ATM network also implement the network. The ATM switch and ATM network also implement the
ATM VP/VC cross-connect tables. Both link and cross-connect ATM VP/VC cross-connect tables. Both link and cross-connect
tables are implemented in a carrier's network for Customer tables are implemented in a carrier's network for Customer
Network Management (CNM) purposes. Network Management (CNM) purposes.
The ATM virtual link tables are used to create, delete or The ATM virtual link tables are used to create, delete or
skipping to change at page 12, line 46 skipping to change at page 12, line 4
atmVcCrossConnectTable of the ATM-MIB, indexed by the atmVcCrossConnectTable of the ATM-MIB, indexed by the
atmVclCrossConnectIdentifier values for the two VCLs. atmVclCrossConnectIdentifier values for the two VCLs.
For an SVC or Soft PVC the VPL and VCL tables defined in this For an SVC or Soft PVC the VPL and VCL tables defined in this
memo are used. Hoewever, for an SVC or Soft PVC the cross- memo are used. Hoewever, for an SVC or Soft PVC the cross-
connect between two VPLs is represented in the connect between two VPLs is represented in the
atmSvcVpCrossConnectTable of the ATM2-MIB, indexed by the atmSvcVpCrossConnectTable of the ATM2-MIB, indexed by the
atmVplCrossConnectIdentifier values for the two VPLs, and the atmVplCrossConnectIdentifier values for the two VPLs, and the
cross-connect between two VCLs is represented in the cross-connect between two VCLs is represented in the
atmSvcVcCrossConnectTable of the ATM2-MIB, indexed by the atmSvcVcCrossConnectTable of the ATM2-MIB, indexed by the
draft ATM Management Objects October 19, 1998
atmVclCrossConnectIdentifier values for the two VCLs. atmVclCrossConnectIdentifier values for the two VCLs.
Note: The ATM2-MIB module was being defined in a separate memo Note: The ATM2-MIB module was being defined in a separate memo
at the time of this publication. Please consult the RFC at the time of this publication. Please consult the RFC
draft ATM Management Objects August 15, 1998
directory for an exact reference. directory for an exact reference.
7. Application of MIB II to ATM 5. Application of MIB II to ATM
7.1. The System Group 5.1. The System Group
For the purposes of the sysServices object in the System Group For the purposes of the sysServices object in the System Group
of MIB II [16], ATM is a data link layer protocol. Thus, for of MIB II [16], ATM is a data link layer protocol. Thus, for
ATM switches and ATM networks, sysServices will have the value ATM switches and ATM networks, sysServices will have the value
"2". "2".
7.2. The Interface Group 5.2. The Interface Group
The Interfaces Group of MIB II defines generic managed objects The Interfaces Group of MIB II defines generic managed objects
for managing interfaces. This memo contains the media- for managing interfaces. This memo contains the media-
specific extensions to the Interfaces Group for managing ATM specific extensions to the Interfaces Group for managing ATM
interfaces. interfaces.
This memo assumes the interpretation of the Interfaces Group This memo assumes the interpretation of the Interfaces Group
to be in accordance with [17] which states that the interfaces to be in accordance with [17] which states that the interfaces
table (ifTable) contains information on the managed resource's table (ifTable) contains information on the managed resource's
interfaces and that each sub-layer below the internetwork interfaces and that each sub-layer below the internetwork
layer of a network interface is considered an interface. layer of a network interface is considered an interface.
Thus, the ATM cell layer interface is represented as an entry Thus, the ATM cell layer interface is represented as an entry
in the ifTable. This entry is concerned with the ATM cell in the ifTable. This entry is concerned with the ATM cell
layer as a whole, and not with individual virtual connections layer as a whole, and not with individual virtual connections
which are managed via the ATM-specific managed objects which are managed via the ATM-specific managed objects
specified in this memo. The inter-relation of entries in the specified in this memo. The inter-relation of entries in the
ifTable is defined by Interfaces Stack Group defined in [17]. ifTable is defined by Interfaces Stack Group defined in [17].
7.2.1. Support of the ATM Cell Layer by ifTable 5.2.1. Support of the ATM Cell Layer by ifTable
Some specific interpretations of ifTable for the ATM cell Some specific interpretations of ifTable for the ATM cell
layer follow. layer follow.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
Object Use for the generic ATM layer Object Use for the generic ATM layer
====== ============================= ====== =============================
ifIndex Each ATM port is represented by an ifEntry. ifIndex Each ATM port is represented by an ifEntry.
ifDescr Description of the ATM interface. ifDescr Description of the ATM interface.
ifType The value that is allocated for ATM is 37. ifType The value that is allocated for ATM is 37.
skipping to change at page 15, line 5 skipping to change at page 14, line 5
side of a public network UNI) may be represented side of a public network UNI) may be represented
through atmInterfaceSubscrAddress. through atmInterfaceSubscrAddress.
ifAdminStatus See [17]. ifAdminStatus See [17].
ifOperStatus Assumes the value down(2) if the ATM cell ifOperStatus Assumes the value down(2) if the ATM cell
layer is down. layer is down.
ifLastChange See [17]. ifLastChange See [17].
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
ifInOctets The number of received octets over the ifInOctets The number of received octets over the
interface, i.e., the number of received, interface, i.e., the number of received,
assigned cells multiplied by 53. assigned cells multiplied by 53.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the
interface, i.e., the number of transmitted, interface, i.e., the number of transmitted,
assigned cells multiplied by 53. assigned cells multiplied by 53.
ifInErrors The number of cells dropped due to ifInErrors The number of cells dropped due to
skipping to change at page 15, line 45 skipping to change at page 14, line 45
ifHCInOctets The 64-bit version of ifInOctets; supported ifHCInOctets The 64-bit version of ifInOctets; supported
if required by the compliance statements in [17]. if required by the compliance statements in [17].
ifHCOutOctets The 64-bit version of ifOutOctets; supported ifHCOutOctets The 64-bit version of ifOutOctets; supported
if required by the compliance statements in [17]. if required by the compliance statements in [17].
ifAlias The non-volatile 'alias' name for the interface ifAlias The non-volatile 'alias' name for the interface
as specified by a network manager. as specified by a network manager.
8. Support of the AAL3/4 Based Interfaces 6. Support of the AAL3/4 Based Interfaces
For the management of AAL3/4 CPCS layer, see [18]. For the management of AAL3/4 CPCS layer, see [18].
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
9. Support of the AAL5 Managed Objects 7. Support of the AAL5 Managed Objects
Support of AAL5 managed objects in an ATM switch and ATM host Support of AAL5 managed objects in an ATM switch and ATM host
are described below. are described below.
9.1. Managing AAL5 in a Switch 7.1. Managing AAL5 in a Switch
Managing AAL5 in a switch involves: Managing AAL5 in a switch involves:
(1) performance management of an AAL5 entity as (1) performance management of an AAL5 entity as
an internal resource in a switch an internal resource in a switch
(2) performance management of AAL5 per virtual connection (2) performance management of AAL5 per virtual connection
AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5 AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5
will be managed in a switch for only those virtual connections will be managed in a switch for only those virtual connections
skipping to change at page 17, line 5 skipping to change at page 16, line 5
interface and the ATM virtual link at the ATM interface will interface and the ATM virtual link at the ATM interface will
be derived from the virtual channel cross-connect table and be derived from the virtual channel cross-connect table and
the virtual channel link table in the ATM MIB. Note that for the virtual channel link table in the ATM MIB. Note that for
the proprietary virtual interface the traffic transmit and the proprietary virtual interface the traffic transmit and
receive conventions in the virtual channel link table are as receive conventions in the virtual channel link table are as
follows: follows:
Transmitting traffic: ATM Entity ---> AAL5 Entity Transmitting traffic: ATM Entity ---> AAL5 Entity
Receiving traffic: ATM Entity <--- AAL5 Entity Receiving traffic: ATM Entity <--- AAL5 Entity
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
___________________________ ___________________________
| | | |
| ============= | | ============= |
| | AAL5 | | | | AAL5 | |
| | Entity | | | | Entity | |
| ============= | | ============= |
| | | | | |
| -----Prop. Virtual Interface | -----Prop. Virtual Interface
| | | | | |
skipping to change at page 17, line 40 skipping to change at page 16, line 40
| | | |
| AAL5 | | AAL5 |
|________________| |________________|
| | | |
| Prop. Virtual | | Prop. Virtual |
| Interface | | Interface |
|________________| |________________|
Figure 8: AAL5 Entity's Interface Stack in a Switch Figure 8: AAL5 Entity's Interface Stack in a Switch
9.2. Managing AAL5 in a Host 7.2. Managing AAL5 in a Host
Managing AAL5 in a host involves managing the AAL5 sublayer Managing AAL5 in a host involves managing the AAL5 sublayer
interface as shown in Figure 9 and 10. The AAL5 sublayer is interface as shown in Figure 9 and 10. The AAL5 sublayer is
stacked directly over the ATM sublayer. The ifTable is stacked directly over the ATM sublayer. The ifTable is
applied to the AAL5 sublayer as defined in Section 10.3. applied to the AAL5 sublayer as defined in Section 10.3.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
___________________________ ___________________________
| | | |
| ============= | | ============= |
| | AAL5 | | | | AAL5 | |
| | Entity | | | | Entity | |
| ============= | | ============= |
| | ATM | | | | ATM | |
| | Entity | | | | Entity | |
| ============= | | ============= |
skipping to change at page 19, line 5 skipping to change at page 18, line 5
|________________| |________________|
| | | |
| ATM Layer | | ATM Layer |
|________________| |________________|
| | | |
| Physical Layer| | Physical Layer|
|________________| |________________|
Figure 10: AAL5 Entity's Interface Stack in a Host Figure 10: AAL5 Entity's Interface Stack in a Host
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
9.3. Support of AAL5 by ifTable 7.3. Support of AAL5 by ifTable
The AAL5 entity in an ATM device (e.g., switch or host) is The AAL5 entity in an ATM device (e.g., switch or host) is
managed using the ifTable. There are additional counters managed using the ifTable. There are additional counters
specified for AAL5 than those specified in the ATM B-ICI specified for AAL5 than those specified in the ATM B-ICI
document [21]. Specific interpretations of ifTable for the document [21]. Specific interpretations of ifTable for the
AAL5 CPCS layer are as follows. AAL5 CPCS layer are as follows.
Object Use for AAL5 CPCS layer entity Object Use for AAL5 CPCS layer entity
====== ============================== ====== ==============================
skipping to change at page 20, line 5 skipping to change at page 19, line 5
ifInUcastPkts The number of received AAL5 CPCS PDUs passed ifInUcastPkts The number of received AAL5 CPCS PDUs passed
to a higher-layer. to a higher-layer.
ifOutUcastPkts The number of AAL5 CPCS PDUs received from a ifOutUcastPkts The number of AAL5 CPCS PDUs received from a
higher-layer for transmission. higher-layer for transmission.
[Note: The number of AAL5 PDUs actually [Note: The number of AAL5 PDUs actually
transmitted is the number received from a transmitted is the number received from a
higher-layer for transmission minus any which higher-layer for transmission minus any which
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
are counted by ifOutErrors and ifOutDiscards.] are counted by ifOutErrors and ifOutDiscards.]
ifInErrors Number of errored AAL5 CPCS PDUs received. ifInErrors Number of errored AAL5 CPCS PDUs received.
The types of errors counted include CRC-32 errors, The types of errors counted include CRC-32 errors,
SAR time-out errors, and oversized SDU errors. SAR time-out errors, and oversized SDU errors.
ifInUnknownProtos Set to 0. ifInUnknownProtos Set to 0.
ifInDiscards Number of received AAL5 CPCS PDUs discarded. ifInDiscards Number of received AAL5 CPCS PDUs discarded.
skipping to change at page 21, line 5 skipping to change at page 20, line 5
ifConnectorPresent Set to false (2). ifConnectorPresent Set to false (2).
ifPromiscuousMode Set to false(2). ifPromiscuousMode Set to false(2).
ifLinkUpDownTrapEnable Default is disabled (2). ifLinkUpDownTrapEnable Default is disabled (2).
ifAlias The non-volatile 'alias' name for the interface ifAlias The non-volatile 'alias' name for the interface
as specified by a network manager. as specified by a network manager.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
9.4. Support of Proprietary Virtual Interface by ifTable 7.4. Support of Proprietary Virtual Interface by ifTable
Specific interpretations of ifTable for the proprietary Specific interpretations of ifTable for the proprietary
virtual, internal interface associated with an AAL5 entity in virtual, internal interface associated with an AAL5 entity in
an ATM switch are as follows. an ATM switch are as follows.
draft ATM Management Objects August 15, 1998
Object Use for proprietary virtual, internal interface Object Use for proprietary virtual, internal interface
associated with AAL entities associated with AAL entities
====== =============================================== ====== ===============================================
ifIndex Each proprietary virtual, internal interface ifIndex Each proprietary virtual, internal interface
associated with AAL entities is represented by an associated with AAL entities is represented by an
ifEntry. ifEntry.
ifDescr Description of the proprietary virtual, internal ifDescr Description of the proprietary virtual, internal
interface associated with AAL entities. interface associated with AAL entities.
skipping to change at page 22, line 45 skipping to change at page 21, line 5
ifHighSpeed See [17]. Set to 0 if the speed is not known. ifHighSpeed See [17]. Set to 0 if the speed is not known.
ifConnectorPresent Set to false (2). ifConnectorPresent Set to false (2).
ifLinkUpDownTrapEnable Default is disabled (2). ifLinkUpDownTrapEnable Default is disabled (2).
ifAlias The non-volatile 'alias' name for the interface ifAlias The non-volatile 'alias' name for the interface
as specified by a network manager. as specified by a network manager.
9.5. AAL5 Connection Performance Statistics Table draft ATM Management Objects October 19, 1998
7.5. AAL5 Connection Performance Statistics Table
An AAL5 connection table is used to provide AAL5 performance An AAL5 connection table is used to provide AAL5 performance
information for each AAL5 virtual connection that is information for each AAL5 virtual connection that is
terminated at the AAL5 entity contained within an ATM switch terminated at the AAL5 entity contained within an ATM switch
or host. or host.
draft ATM Management Objects August 15, 1998 8. ILMI MIBs and the ATM Managed Objects
10. ILMI MIBs and the ATM Managed Objects
The ILMI MIBs are specified by the ATM Forum as a set of The ILMI MIBs are specified by the ATM Forum as a set of
several MIBs, all currently defined in the ILMI Specification several MIBs, all currently defined in the ILMI Specification
[23]. The ILMI protocols and MIBs allow two connected ATM [23]. The ILMI protocols and MIBs allow two connected ATM
Interface Management Entities (IMEs) to exchange bi- Interface Management Entities (IMEs) to exchange bi-
directional parameters, mainly to facilitate auto- directional parameters, mainly to facilitate auto-
configuration between ATM peer entities. The support of the configuration between ATM peer entities. The support of the
ATM management functions by the ILMI MIBs and those contained ATM management functions by the ILMI MIBs and those contained
in this memo are compared in Table 1. In this table, "yes" in in this memo are compared in Table 1. In this table, "yes" in
the "ILMI MIBs" column indicates that the management the "ILMI MIBs" column indicates that the management
functions are supported by the ILMI MIBs. The parenthesized functions are supported by the ILMI MIBs. The parenthesized
numbers in the "This memo" column correspond to the sets of numbers in the "This memo" column correspond to the sets of
tables enumerated in Section 6.2. tables enumerated in Section 6.2.
For that subset of management information which the ILMI MIBs For that subset of management information which the ILMI MIBs
and this memo have in common, every effort has been made to and this memo have in common, every effort has been made to
retain identical semantics and syntax, even though the MIB retain identical semantics and syntax, even though the MIB
objects are identified using different OBJECT IDENTIFIERs. objects are identified using different OBJECT IDENTIFIERs.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
Table 1 - Structuring of ATM Managed Objects Table 1 - Structuring of ATM Managed Objects
______________________________________________________________ ______________________________________________________________
| |This |ILMI| | |This |ILMI|
ATM Mgmt.Inf. |ATM Managed Objects |memo |MIBs| ATM Mgmt.Inf. |ATM Managed Objects |memo |MIBs|
______________|_________________________________|_______|____| ______________|_________________________________|_______|____|
Local Interface Information: Local Interface Information:
_____________________________________________________________ _____________________________________________________________
ATM interface:| (1) port identifier |ATM MIB| | ATM interface:| (1) port identifier |ATM MIB| |
skipping to change at page 25, line 4 skipping to change at page 23, line 4
|(3)VCL/VPL administrative status | |*** | |(3)VCL/VPL administrative status | |*** |
|(4)VCL/VPL last change status | | | |(4)VCL/VPL last change status | | |
|(5)transmit/receive traffic/ | | | |(5)transmit/receive traffic/ | | |
| service category parameters | | | | service category parameters | | |
|(6)AAL type | | | |(6)AAL type | | |
|(7)transmit/receive AAL5 SDU size| | | |(7)transmit/receive AAL5 SDU size| | |
|(8)AAL5 encapsulation type | | | |(8)AAL5 encapsulation type | | |
|(9)connection topology type | | | |(9)connection topology type | | |
|(10)use of call control | | | |(10)use of call control | | |
_____________________________________________________________ _____________________________________________________________
draft ATM Management Objects October 19, 1998
draft ATM Management Objects August 15, 1998
_____________________________________________________________ _____________________________________________________________
VP/VC |(1)cross-connect identifier | | | VP/VC |(1)cross-connect identifier | | |
Cross-connect:|(2)port identifier of one | | | Cross-connect:|(2)port identifier of one | | |
configuration | end | | | configuration | end | | |
|(3)port identifier of the other |ATM MIB| | |(3)port identifier of the other |ATM MIB| |
| end | (5)|no | | end | (5)|no |
|(4)VPI or VPI/VCI value | | | |(4)VPI or VPI/VCI value | | |
| of one end | | | | of one end | | |
|(5)VPI or VPI/VCI value of | | | |(5)VPI or VPI/VCI value of | | |
skipping to change at page 26, line 5 skipping to change at page 24, line 5
the ATM interface. the ATM interface.
** The ILMI MIB contains read-only objects for various ** The ILMI MIB contains read-only objects for various
parameters at the ATM interface level. parameters at the ATM interface level.
***The ILMI MIBs contain local and end-to-end operational ***The ILMI MIBs contain local and end-to-end operational
status of the VPC/VCC segment. However, it does not contain status of the VPC/VCC segment. However, it does not contain
the VPC/VCC administrative and last change status and the VCC the VPC/VCC administrative and last change status and the VCC
AAL information. AAL information.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
11. Definitions 9. Definitions
ATM-MIB DEFINITIONS ::= BEGIN ATM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
experimental, Counter32, Integer32, IpAddress, mib-2 Counter32, Integer32, IpAddress, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString, RowStatus, TruthValue DisplayString, RowStatus, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndex, ifIndex InterfaceIndex, ifIndex
FROM IF-MIB FROM IF-MIB
AtmAddr, AtmConnKind, AtmConnCastType, AtmAddr, AtmConnKind, AtmConnCastType,
AtmServiceCategory, AtmTrafficDescrParamIndex, AtmServiceCategory, AtmTrafficDescrParamIndex,
AtmVpIdentifier, AtmVcIdentifier, AtmVpIdentifier, AtmVcIdentifier,
AtmVorXAdminStatus, AtmVorXLastChange, AtmVorXAdminStatus, AtmVorXLastChange,
AtmVorXOperStatus, atmNoClpNoScr AtmVorXOperStatus, atmNoClpNoScr
FROM ATM-TC-MIB; FROM ATM-TC-MIB;
atmMIB MODULE-IDENTITY atmMIB MODULE-IDENTITY
LAST-UPDATED "9808151200Z" LAST-UPDATED "9810191200Z"
ORGANIZATION "IETF AToM MIB Working Group" ORGANIZATION "IETF AToM MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Kaj Tesink " Kaj Tesink
Postal: Bellcore Postal: Bellcore
331 Newman Springs Road 331 Newman Springs Road
Red Bank, NJ 07701 Red Bank, NJ 07701
Tel: 732-758-5254 Tel: 732-758-5254
Fax: 732-758-2269 Fax: 732-758-2269
E-mail: kaj@cc.bellcore.com" E-mail: kaj@bellcore.com"
DESCRIPTION DESCRIPTION
"This is the MIB Module for ATM and AAL5-related "This is the MIB Module for ATM and AAL5-related
objects for managing ATM interfaces, ATM virtual objects for managing ATM interfaces, ATM virtual
links, ATM cross-connects, AAL5 entities, and links, ATM cross-connects, AAL5 entities, and
and AAL5 connections." and AAL5 connections."
REVISION "9406072245Z" REVISION "9810191200Z"
DESCRIPTION DESCRIPTION
"The initial revision of this module was published "The initial revision of this module was published
as RFC 1695." as RFC 1695. Key revisions include:
::= { experimental 41 } o Textual Conventions and OBJECT IDENTITIES have
been moved to a separate MIB module.
-- **************************************** o Applicability of objects to PVCs, SVCs and Soft
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- * Note to RFC editor * PVCs has been clarified.
-- * Replace {experimental 41} with * o DEFVAL clauses have been added.
-- * { mib-2 37 } when publishing this * o The relationship of ifIndex values with different
-- * MIB as RFC * layers and sublayers related to ATM has been
-- **************************************** clarified.
o atmTrafficQosClass has been deprecated
and replaced with atmServiceCategory.
o atmInterfaceCurrentMaxVpiBits and
atmInterfaceCurrentMaxVciBits have been added with
a description on their relationship with other
objects.
o atmInterfaceAddressType and atmInterfaceAdminAddress
have been deprecated and replaced by
atmInterfaceSubscrAddress.
o atmInterfaceTCAlarmState has been clarified.
o atmTrafficDescrParamIndexNext has been introduced
in order to provide a manager a free
atmTrafficDescrParamIndex value.
o The atmTrafficFrameDiscard capability has been added.
o A connection topology type (atmVpl/VclCastType) and
a call control type (atmVpl/VclConnKind) have been
added.
o aal2 has been added to atmVccAalType."
REVISION "9406072245Z"
DESCRIPTION
"The RFC1695 version of this MIB module."
::= { mib-2 37 }
atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1} atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1}
-- {atmMIBObjects 1} has been moved to a separate -- {atmMIBObjects 1} has been moved to a separate
-- specification [19]. -- specification [19].
draft ATM Management Objects August 15, 1998
-- This ATM MIB Module consists of the following tables: -- This ATM MIB Module consists of the following tables:
-- (1) ATM Interface configuration table -- (1) ATM Interface configuration table
-- (2) ATM Interface DS3 PLCP table -- (2) ATM Interface DS3 PLCP table
-- (3) ATM Interface TC Sublayer table -- (3) ATM Interface TC Sublayer table
-- (4) Atm Traffic Descriptor table -- (4) Atm Traffic Descriptor table
-- (5) ATM Interface VPL configuration table -- (5) ATM Interface VPL configuration table
-- (6) ATM Interface VCL configuration table -- (6) ATM Interface VCL configuration table
-- (7) ATM VP Cross Connect table (for PVCs) -- (7) ATM VP Cross Connect table (for PVCs)
-- (8) ATM VC Cross Connect table (for PVCs) -- (8) ATM VC Cross Connect table (for PVCs)
-- (9) ATM Interface AAL5 VCC performance statistics -- (9) ATM Interface AAL5 VCC performance statistics
draft ATM Management Objects October 19, 1998
-- table -- table
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Interface Configuration Parameters Table -- ATM Interface Configuration Parameters Table
-- This table contains ATM specific -- This table contains ATM specific
-- configuration information associated with -- configuration information associated with
-- an ATM interface beyond those -- an ATM interface beyond those
-- supported using the ifTable. -- supported using the ifTable.
atmInterfaceConfTable OBJECT-TYPE atmInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmInterfaceConfEntry SYNTAX SEQUENCE OF AtmInterfaceConfEntry
skipping to change at page 30, line 5 skipping to change at page 28, line 5
atmInterfaceMaxActiveVpiBits INTEGER, atmInterfaceMaxActiveVpiBits INTEGER,
atmInterfaceMaxActiveVciBits INTEGER, atmInterfaceMaxActiveVciBits INTEGER,
atmInterfaceIlmiVpi AtmVpIdentifier, atmInterfaceIlmiVpi AtmVpIdentifier,
atmInterfaceIlmiVci AtmVcIdentifier, atmInterfaceIlmiVci AtmVcIdentifier,
atmInterfaceAddressType INTEGER, atmInterfaceAddressType INTEGER,
atmInterfaceAdminAddress AtmAddr, atmInterfaceAdminAddress AtmAddr,
atmInterfaceMyNeighborIpAddress IpAddress, atmInterfaceMyNeighborIpAddress IpAddress,
atmInterfaceMyNeighborIfName DisplayString, atmInterfaceMyNeighborIfName DisplayString,
atmInterfaceCurrentMaxVpiBits INTEGER, atmInterfaceCurrentMaxVpiBits INTEGER,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmInterfaceCurrentMaxVciBits INTEGER, atmInterfaceCurrentMaxVciBits INTEGER,
atmInterfaceSubscrAddress AtmAddr atmInterfaceSubscrAddress AtmAddr
} }
atmInterfaceMaxVpcs OBJECT-TYPE atmInterfaceMaxVpcs OBJECT-TYPE
SYNTAX INTEGER (0..4096) SYNTAX INTEGER (0..4096)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 31, line 5 skipping to change at page 29, line 5
At the ATM UNI, the configured number of At the ATM UNI, the configured number of
VPCs (PVPCs and SVPCs) can range from VPCs (PVPCs and SVPCs) can range from
0 to 256 only." 0 to 256 only."
::= { atmInterfaceConfEntry 3} ::= { atmInterfaceConfEntry 3}
atmInterfaceConfVccs OBJECT-TYPE atmInterfaceConfVccs OBJECT-TYPE
SYNTAX INTEGER (0..65536) SYNTAX INTEGER (0..65536)
MAX-ACCESS read-only MAX-ACCESS read-only
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of VCCs (PVCC, Soft PVCC and SVCC) "The number of VCCs (PVCC, Soft PVCC and SVCC)
currently in use at this ATM interface. It includes currently in use at this ATM interface. It includes
the number of PVCCs and Soft PVCCs that are configured the number of PVCCs and Soft PVCCs that are configured
at the interface, plus the number of SVCCs at the interface, plus the number of SVCCs
that are currently established at the that are currently established at the
interface." interface."
::= { atmInterfaceConfEntry 4} ::= { atmInterfaceConfEntry 4}
skipping to change at page 32, line 5 skipping to change at page 30, line 5
"The VPI value of the VCC supporting "The VPI value of the VCC supporting
the ILMI at this ATM interface. If the values of the ILMI at this ATM interface. If the values of
atmInterfaceIlmiVpi and atmInterfaceIlmiVci are atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
both equal to zero then the ILMI is not both equal to zero then the ILMI is not
supported at this ATM interface." supported at this ATM interface."
DEFVAL { 0 } DEFVAL { 0 }
::= { atmInterfaceConfEntry 7} ::= { atmInterfaceConfEntry 7}
atmInterfaceIlmiVci OBJECT-TYPE atmInterfaceIlmiVci OBJECT-TYPE
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
SYNTAX AtmVcIdentifier SYNTAX AtmVcIdentifier
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VCI value of the VCC supporting "The VCI value of the VCC supporting
the ILMI at this ATM interface. If the values of the ILMI at this ATM interface. If the values of
atmInterfaceIlmiVpi and atmInterfaceIlmiVci are atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
both equal to zero then the ILMI is not both equal to zero then the ILMI is not
supported at this ATM interface." supported at this ATM interface."
skipping to change at page 33, line 5 skipping to change at page 31, line 5
service provider side of a public network UNI service provider side of a public network UNI
(thus, the value of this address corresponds (thus, the value of this address corresponds
with the value of ifPhysAddress at the host side). with the value of ifPhysAddress at the host side).
If this interface has no assigned administrative If this interface has no assigned administrative
address, or when the address used for address, or when the address used for
administrative purposes is the same as that used administrative purposes is the same as that used
for ifPhysAddress, then this is an octet string of for ifPhysAddress, then this is an octet string of
zero length." zero length."
::= { atmInterfaceConfEntry 10 } ::= { atmInterfaceConfEntry 10 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmInterfaceMyNeighborIpAddress OBJECT-TYPE atmInterfaceMyNeighborIpAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the neighbor system connected to "The IP address of the neighbor system connected to
the far end of this interface, to which a Network the far end of this interface, to which a Network
Management Station can send SNMP messages, as IP Management Station can send SNMP messages, as IP
datagrams sent to UDP port 161, in order to access datagrams sent to UDP port 161, in order to access
skipping to change at page 34, line 5 skipping to change at page 32, line 5
atmInterfaceCurrentMaxVpiBits OBJECT-TYPE atmInterfaceCurrentMaxVpiBits OBJECT-TYPE
SYNTAX INTEGER (0..12) SYNTAX INTEGER (0..12)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of VPI Bits that may "The maximum number of VPI Bits that may
currently be used at this ATM interface. currently be used at this ATM interface.
The value is the minimum of The value is the minimum of
atmInterfaceMaxActiveVpiBits, and the atmInterfaceMaxActiveVpiBits, and the
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmInterfaceMaxActiveVpiBits of the interface's atmInterfaceMaxActiveVpiBits of the interface's
UNI/NNI peer. UNI/NNI peer.
If the interface does not negotiate with If the interface does not negotiate with
its peer to determine the number of VPI Bits its peer to determine the number of VPI Bits
that can be used on the interface, then the that can be used on the interface, then the
value of this object must equal value of this object must equal
atmInterfaceMaxActiveVpiBits." atmInterfaceMaxActiveVpiBits."
::= { atmInterfaceConfEntry 13 } ::= { atmInterfaceConfEntry 13 }
skipping to change at page 35, line 5 skipping to change at page 33, line 5
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier assigned by a service provider "The identifier assigned by a service provider
to the network side of a public network UNI. to the network side of a public network UNI.
If this interface has no assigned service provider If this interface has no assigned service provider
address, or for other interfaces this is an octet string address, or for other interfaces this is an octet string
of zero length." of zero length."
::= { atmInterfaceConfEntry 15 } ::= { atmInterfaceConfEntry 15 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- The ATM Interface DS3 PLCP Table -- The ATM Interface DS3 PLCP Table
-- This table contains the DS3 PLCP configuration and -- This table contains the DS3 PLCP configuration and
-- state parameters of those ATM interfaces -- state parameters of those ATM interfaces
-- which use DS3 PLCP for carrying ATM cells over DS3. -- which use DS3 PLCP for carrying ATM cells over DS3.
atmInterfaceDs3PlcpTable OBJECT-TYPE atmInterfaceDs3PlcpTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 36, line 5 skipping to change at page 34, line 5
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DS3 PLCP Severely Errored Framing "The number of DS3 PLCP Severely Errored Framing
Seconds (SEFS). Each SEFS represents a Seconds (SEFS). Each SEFS represents a
one-second interval which contains one-second interval which contains
one or more SEF events." one or more SEF events."
::= { atmInterfaceDs3PlcpEntry 1} ::= { atmInterfaceDs3PlcpEntry 1}
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmInterfaceDs3PlcpAlarmState OBJECT-TYPE atmInterfaceDs3PlcpAlarmState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noAlarm(1), noAlarm(1),
receivedFarEndAlarm(2), receivedFarEndAlarm(2),
incomingLOF(3) incomingLOF(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 37, line 5 skipping to change at page 35, line 5
atmInterfaceDs3PlcpUASs OBJECT-TYPE atmInterfaceDs3PlcpUASs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The counter associated with the number of "The counter associated with the number of
Unavailable Seconds encountered by the PLCP." Unavailable Seconds encountered by the PLCP."
::= { atmInterfaceDs3PlcpEntry 3} ::= { atmInterfaceDs3PlcpEntry 3}
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- The ATM Interface TC Sublayer Table -- The ATM Interface TC Sublayer Table
-- This table contains TC sublayer configuration and -- This table contains TC sublayer configuration and
-- state parameters of those ATM interfaces -- state parameters of those ATM interfaces
-- which use TC sublayer for carrying ATM cells over -- which use TC sublayer for carrying ATM cells over
-- SONET/SDH or DS3. -- SONET/SDH or DS3.
atmInterfaceTCTable OBJECT-TYPE atmInterfaceTCTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmInterfaceTCEntry SYNTAX SEQUENCE OF AtmInterfaceTCEntry
skipping to change at page 38, line 5 skipping to change at page 36, line 5
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times the Out of Cell "The number of times the Out of Cell
Delineation (OCD) events occur. If seven Delineation (OCD) events occur. If seven
consecutive ATM cells have Header Error consecutive ATM cells have Header Error
Control (HEC) violations, an OCD event occurs. Control (HEC) violations, an OCD event occurs.
A high number of OCD events may indicate a A high number of OCD events may indicate a
problem with the TC Sublayer." problem with the TC Sublayer."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
::= { atmInterfaceTCEntry 1} ::= { atmInterfaceTCEntry 1}
atmInterfaceTCAlarmState OBJECT-TYPE atmInterfaceTCAlarmState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noAlarm(1), noAlarm(1),
lcdFailure(2) lcdFailure(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 39, line 5 skipping to change at page 37, line 5
"This variable indicates if there is an "This variable indicates if there is an
alarm present for the TC Sublayer. The value alarm present for the TC Sublayer. The value
lcdFailure(2) indicates that the TC Sublayer lcdFailure(2) indicates that the TC Sublayer
is currently in the Loss of Cell Delineation is currently in the Loss of Cell Delineation
(LCD) defect maintenance state. The value (LCD) defect maintenance state. The value
noAlarm(1) indicates that the TC Sublayer noAlarm(1) indicates that the TC Sublayer
is currently not in the LCD defect is currently not in the LCD defect
maintenance state." maintenance state."
::= { atmInterfaceTCEntry 2} ::= { atmInterfaceTCEntry 2}
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Traffic Descriptor Parameter Table -- ATM Traffic Descriptor Parameter Table
-- This table contains a set of self-consistent -- This table contains a set of self-consistent
-- ATM traffic parameters including the -- ATM traffic parameters including the
-- ATM traffic service category. -- ATM traffic service category.
-- The ATM virtual link tables (i.e., VPL and VCL tables) -- The ATM virtual link tables (i.e., VPL and VCL tables)
-- will use this ATM Traffic Descriptor table -- will use this ATM Traffic Descriptor table
-- to assign traffic parameters and service category -- to assign traffic parameters and service category
skipping to change at page 40, line 5 skipping to change at page 38, line 5
-- use. -- use.
-- The ATM Traffic Descriptor Parameter Table -- The ATM Traffic Descriptor Parameter Table
atmTrafficDescrParamTable OBJECT-TYPE atmTrafficDescrParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
"This table contains information on ATM traffic "This table contains information on ATM traffic
descriptor type and the associated parameters." descriptor type and the associated parameters."
::= { atmMIBObjects 5} ::= { atmMIBObjects 5}
atmTrafficDescrParamEntry OBJECT-TYPE atmTrafficDescrParamEntry OBJECT-TYPE
SYNTAX AtmTrafficDescrParamEntry SYNTAX AtmTrafficDescrParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 40, line 36 skipping to change at page 38, line 36
atmTrafficDescrParam3 Integer32, atmTrafficDescrParam3 Integer32,
atmTrafficDescrParam4 Integer32, atmTrafficDescrParam4 Integer32,
atmTrafficDescrParam5 Integer32, atmTrafficDescrParam5 Integer32,
atmTrafficQoSClass INTEGER, atmTrafficQoSClass INTEGER,
atmTrafficDescrRowStatus RowStatus, atmTrafficDescrRowStatus RowStatus,
atmServiceCategory AtmServiceCategory, atmServiceCategory AtmServiceCategory,
atmTrafficFrameDiscard TruthValue atmTrafficFrameDiscard TruthValue
} }
atmTrafficDescrParamIndex OBJECT-TYPE atmTrafficDescrParamIndex OBJECT-TYPE
SYNTAX AtmTrafficDescrParamIndex SYNTAX AtmTrafficDescrParamIndex (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used by the virtual link "This object is used by the virtual link
table (i.e., VPL or VCL table) table (i.e., VPL or VCL table)
to identify the row of this table. to identify the row of this table.
When creating a new row in the table When creating a new row in the table
the value of this index may be obtained the value of this index may be obtained
by retrieving the value of by retrieving the value of
atmTrafficDescrParamIndexNext." atmTrafficDescrParamIndexNext."
::= { atmTrafficDescrParamEntry 1} ::= { atmTrafficDescrParamEntry 1}
atmTrafficDescrType OBJECT-TYPE atmTrafficDescrType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the type "The value of this object identifies the type
of ATM traffic descriptor. of ATM traffic descriptor.
The type may indicate no traffic descriptor or The type may indicate no traffic descriptor or
traffic descriptor with one or more parameters. traffic descriptor with one or more parameters.
These parameters are specified as a parameter These parameters are specified as a parameter
vector, in the corresponding instances of the vector, in the corresponding instances of the
objects: objects:
skipping to change at page 42, line 5 skipping to change at page 40, line 5
DEFVAL { 0 } DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 4} ::= { atmTrafficDescrParamEntry 4}
atmTrafficDescrParam3 OBJECT-TYPE atmTrafficDescrParam3 OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The third parameter of the ATM traffic descriptor "The third parameter of the ATM traffic descriptor
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
used according to the value of used according to the value of
atmTrafficDescrType." atmTrafficDescrType."
DEFVAL { 0 } DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 5} ::= { atmTrafficDescrParamEntry 5}
atmTrafficDescrParam4 OBJECT-TYPE atmTrafficDescrParam4 OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 43, line 5 skipping to change at page 41, line 5
Circuit emulation Circuit emulation
Service Class B: Variable bit rate video/audio Service Class B: Variable bit rate video/audio
Service Class C: Connection-oriented data Service Class C: Connection-oriented data
Service Class D: Connectionless data Service Class D: Connectionless data
Four QoS classes numbered 1, 2, 3, and 4 have Four QoS classes numbered 1, 2, 3, and 4 have
been specified with the aim to support service been specified with the aim to support service
classes A, B, C, and D respectively. classes A, B, C, and D respectively.
An unspecified QoS Class numbered `0' is used An unspecified QoS Class numbered `0' is used
for best effort traffic." for best effort traffic."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DEFVAL { 0 } DEFVAL { 0 }
::= { atmTrafficDescrParamEntry 8} ::= { atmTrafficDescrParamEntry 8}
atmTrafficDescrRowStatus OBJECT-TYPE atmTrafficDescrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create "This object is used to create
skipping to change at page 44, line 5 skipping to change at page 42, line 5
"If set to 'true', this object indicates that the network "If set to 'true', this object indicates that the network
is requested to treat data for this connection, in the is requested to treat data for this connection, in the
given direction, as frames (e.g. AAL5 CPCS_PDU's) rather given direction, as frames (e.g. AAL5 CPCS_PDU's) rather
than as individual cells. While the precise than as individual cells. While the precise
implementation is network-specific, this treatment may implementation is network-specific, this treatment may
for example involve discarding entire frames during for example involve discarding entire frames during
congestion, rather than a few cells from many frames." congestion, rather than a few cells from many frames."
DEFVAL { true } DEFVAL { true }
::= { atmTrafficDescrParamEntry 11 } ::= { atmTrafficDescrParamEntry 11 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Interface Virtual Path Link (VPL) Table -- ATM Interface Virtual Path Link (VPL) Table
-- This table contains configuration and state -- This table contains configuration and state
-- information of a bi-directional Virtual Path Link -- information of a bi-directional Virtual Path Link
-- (VPL) -- (VPL)
-- This table can be used to create, delete or modify -- This table can be used to create, delete or modify
-- a VPL that is terminated in an ATM host or switch. -- a VPL that is terminated in an ATM host or switch.
-- This table can also be used to create, delete or -- This table can also be used to create, delete or
skipping to change at page 45, line 5 skipping to change at page 43, line 5
SYNTAX SEQUENCE OF AtmVplEntry SYNTAX SEQUENCE OF AtmVplEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Virtual Path Link (VPL) table. A "The Virtual Path Link (VPL) table. A
bi-directional VPL is modeled as one entry bi-directional VPL is modeled as one entry
in this table. This table can be used for in this table. This table can be used for
PVCs, SVCs and Soft PVCs. PVCs, SVCs and Soft PVCs.
Entries are not present in this table for Entries are not present in this table for
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
the VPIs used by entries in the atmVclTable." the VPIs used by entries in the atmVclTable."
::= { atmMIBObjects 6} ::= { atmMIBObjects 6}
atmVplEntry OBJECT-TYPE atmVplEntry OBJECT-TYPE
SYNTAX AtmVplEntry SYNTAX AtmVplEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the VPL table. This entry is "An entry in the VPL table. This entry is
skipping to change at page 46, line 5 skipping to change at page 44, line 5
parameters through setting the parameters through setting the
atmVplReceiveTrafficDescrIndex and the atmVplReceiveTrafficDescrIndex and the
atmVplTransmitTrafficDescrIndex values atmVplTransmitTrafficDescrIndex values
in the VPL table, which point to the rows in the VPL table, which point to the rows
containing desired ATM traffic parameter values containing desired ATM traffic parameter values
in the atmTrafficDescrParamTable. The agent in the atmTrafficDescrParamTable. The agent
will check the availability of resources and will check the availability of resources and
may refuse the request. may refuse the request.
If the transmit and receive service categories If the transmit and receive service categories
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
are inconsistent, the agent should refuse the are inconsistent, the agent should refuse the
request. request.
(3) The manager activates the VPL by setting the (3) The manager activates the VPL by setting the
the atmVplRowStatus to active(1). the atmVplRowStatus to active(1).
If this set is successful, the agent has If this set is successful, the agent has
reserved the resources to satisfy the requested reserved the resources to satisfy the requested
traffic parameter values and the service category traffic parameter values and the service category
for that VPL. for that VPL.
skipping to change at page 47, line 5 skipping to change at page 45, line 5
destroy(6), and the agent may release all destroy(6), and the agent may release all
associated resources." associated resources."
INDEX {ifIndex, atmVplVpi } INDEX {ifIndex, atmVplVpi }
::= { atmVplTable 1} ::= { atmVplTable 1}
AtmVplEntry ::= SEQUENCE { AtmVplEntry ::= SEQUENCE {
atmVplVpi AtmVpIdentifier, atmVplVpi AtmVpIdentifier,
atmVplAdminStatus AtmVorXAdminStatus, atmVplAdminStatus AtmVorXAdminStatus,
atmVplOperStatus AtmVorXOperStatus, atmVplOperStatus AtmVorXOperStatus,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmVplLastChange AtmVorXLastChange, atmVplLastChange AtmVorXLastChange,
atmVplReceiveTrafficDescrIndex atmVplReceiveTrafficDescrIndex
AtmTrafficDescrParamIndex, AtmTrafficDescrParamIndex,
atmVplTransmitTrafficDescrIndex atmVplTransmitTrafficDescrIndex
AtmTrafficDescrParamIndex, AtmTrafficDescrParamIndex,
atmVplCrossConnectIdentifier INTEGER, atmVplCrossConnectIdentifier INTEGER,
atmVplRowStatus RowStatus, atmVplRowStatus RowStatus,
atmVplCastType AtmConnCastType, atmVplCastType AtmConnCastType,
atmVplConnKind AtmConnKind atmVplConnKind AtmConnKind
skipping to change at page 48, line 5 skipping to change at page 46, line 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of the VPL." "The current operational status of the VPL."
::= { atmVplEntry 3} ::= { atmVplEntry 3}
atmVplLastChange OBJECT-TYPE atmVplLastChange OBJECT-TYPE
SYNTAX AtmVorXLastChange SYNTAX AtmVorXLastChange
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
VPL entered its current operational state." VPL entered its current operational state."
::= { atmVplEntry 4 } ::= { atmVplEntry 4 }
atmVplReceiveTrafficDescrIndex OBJECT-TYPE atmVplReceiveTrafficDescrIndex OBJECT-TYPE
SYNTAX AtmTrafficDescrParamIndex SYNTAX AtmTrafficDescrParamIndex
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 49, line 5 skipping to change at page 47, line 5
object, and all their cross-connections are object, and all their cross-connections are
identified either by entries that are indexed identified either by entries that are indexed
by the same value of atmVpCrossConnectIndex in by the same value of atmVpCrossConnectIndex in
the atmVpCrossConnectTable of this MIB module or by the atmVpCrossConnectTable of this MIB module or by
the same value of the cross-connect index in the same value of the cross-connect index in
the cross-connect table for SVCs and Soft PVCs the cross-connect table for SVCs and Soft PVCs
(defined in a separate MIB module). (defined in a separate MIB module).
At no time should entries in these respective At no time should entries in these respective
cross-connect tables exist simultaneously cross-connect tables exist simultaneously
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
with the same cross-connect index value. with the same cross-connect index value.
The value of this object is initialized by the The value of this object is initialized by the
agent after the associated entries in the agent after the associated entries in the
atmVpCrossConnectTable have been created." atmVpCrossConnectTable have been created."
::= {atmVplEntry 7} ::= {atmVplEntry 7}
atmVplRowStatus OBJECT-TYPE atmVplRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
skipping to change at page 49, line 28 skipping to change at page 47, line 28
DESCRIPTION DESCRIPTION
"This object is used to create, delete "This object is used to create, delete
or modify a row in this table. or modify a row in this table.
To create a new VCL, this object is To create a new VCL, this object is
initially set to 'createAndWait' or initially set to 'createAndWait' or
'createAndGo'. This object should not be 'createAndGo'. This object should not be
set to 'active' unless the following columnar set to 'active' unless the following columnar
objects have been set to their desired value objects have been set to their desired value
in this row: in this row:
atmVplReceiveTrafficDescrIndex and atmVplReceiveTrafficDescrIndex and
atmVplTransmitTrafficDescrIndex." atmVplTransmitTrafficDescrIndex.
DEFVAL { active } The DESCRIPTION of atmVplEntry provides
further guidance to row treatment in this table."
DEFVAL { createAndWait }
::= {atmVplEntry 8} ::= {atmVplEntry 8}
atmVplCastType OBJECT-TYPE atmVplCastType OBJECT-TYPE
SYNTAX AtmConnCastType SYNTAX AtmConnCastType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The connection topology type." "The connection topology type."
DEFVAL { p2p } DEFVAL { p2p }
::= {atmVplEntry 9} ::= {atmVplEntry 9}
atmVplConnKind OBJECT-TYPE atmVplConnKind OBJECT-TYPE
SYNTAX AtmConnKind SYNTAX AtmConnKind
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The use of call control." "The use of call control."
DEFVAL { pvc } DEFVAL { pvc }
::= {atmVplEntry 10} ::= {atmVplEntry 10}
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Interface Virtual Channel Link (VCL) Table -- ATM Interface Virtual Channel Link (VCL) Table
-- This table contains configuration and state -- This table contains configuration and state
-- information of a bi-directional Virtual Channel -- information of a bi-directional Virtual Channel
-- Link (VCL) at an ATM interface. -- Link (VCL) at an ATM interface.
-- This table can be used to create, delete or modify -- This table can be used to create, delete or modify
-- a VCL that is terminated in an ATM host or switch. -- a VCL that is terminated in an ATM host or switch.
-- This table can also be -- This table can also be
skipping to change at page 51, line 5 skipping to change at page 49, line 5
Negotiated VCL establishment Negotiated VCL establishment
(1) The management application creates (1) The management application creates
a VCL entry in the atmVclTable a VCL entry in the atmVclTable
by setting atmVclRowStatus to createAndWait(5). by setting atmVclRowStatus to createAndWait(5).
This may fail for the following reasons: This may fail for the following reasons:
- The selected VPI/VCI values are unavailable, - The selected VPI/VCI values are unavailable,
- The selected VPI/VCI values are in use. - The selected VPI/VCI values are in use.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
Otherwise, the agent creates a row and Otherwise, the agent creates a row and
reserves the VPI/VCI values on that port. reserves the VPI/VCI values on that port.
(2) The manager selects an existing row(s) in the (2) The manager selects an existing row(s) in the
atmTrafficDescrParamTable, atmTrafficDescrParamTable,
thereby, selecting a set of self-consistent thereby, selecting a set of self-consistent
ATM traffic parameters and the service category ATM traffic parameters and the service category
for receive and transmit directions of the VCL. for receive and transmit directions of the VCL.
skipping to change at page 52, line 5 skipping to change at page 50, line 5
(4) If the VCL terminates a VCC in the ATM host (4) If the VCL terminates a VCC in the ATM host
or switch, the manager turns on the or switch, the manager turns on the
atmVclAdminStatus to up(1) to turn the VCL atmVclAdminStatus to up(1) to turn the VCL
traffic flow on. Otherwise, the traffic flow on. Otherwise, the
atmVcCrossConnectTable must be used atmVcCrossConnectTable must be used
to cross-connect the VCL to another VCL(s) to cross-connect the VCL to another VCL(s)
in an ATM switch or network. in an ATM switch or network.
One-Shot VCL Establishment One-Shot VCL Establishment
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
A VCL may also be established in one step by a A VCL may also be established in one step by a
set-request with all necessary VCL parameter set-request with all necessary VCL parameter
values and atmVclRowStatus set to createAndGo(4). values and atmVclRowStatus set to createAndGo(4).
In contrast to the negotiated VCL establishment In contrast to the negotiated VCL establishment
which allows for detailed error checking which allows for detailed error checking
(i.e., set errors are explicitly linked to (i.e., set errors are explicitly linked to
particular resource acquisition failures), particular resource acquisition failures),
the one-shot VCL establishment the one-shot VCL establishment
skipping to change at page 53, line 5 skipping to change at page 51, line 5
atmVclRowStatus RowStatus, atmVclRowStatus RowStatus,
atmVclCastType AtmConnCastType, atmVclCastType AtmConnCastType,
atmVclConnKind AtmConnKind atmVclConnKind AtmConnKind
} }
atmVclVpi OBJECT-TYPE atmVclVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DESCRIPTION DESCRIPTION
"The VPI value of the VCL." "The VPI value of the VCL."
::= { atmVclEntry 1} ::= { atmVclEntry 1}
atmVclVci OBJECT-TYPE atmVclVci OBJECT-TYPE
SYNTAX AtmVcIdentifier SYNTAX AtmVcIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 54, line 5 skipping to change at page 52, line 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this VCL "The value of sysUpTime at the time this VCL
entered its current operational state." entered its current operational state."
::= { atmVclEntry 5 } ::= { atmVclEntry 5 }
atmVclReceiveTrafficDescrIndex OBJECT-TYPE atmVclReceiveTrafficDescrIndex OBJECT-TYPE
SYNTAX AtmTrafficDescrParamIndex SYNTAX AtmTrafficDescrParamIndex
MAX-ACCESS read-create MAX-ACCESS read-create
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row "The value of this object identifies the row
in the ATM Traffic Descriptor Table which in the ATM Traffic Descriptor Table which
applies to the receive direction of this VCL." applies to the receive direction of this VCL."
DEFVAL { 0 } DEFVAL { 0 }
::= { atmVclEntry 6} ::= { atmVclEntry 6}
atmVclTransmitTrafficDescrIndex OBJECT-TYPE atmVclTransmitTrafficDescrIndex OBJECT-TYPE
skipping to change at page 55, line 5 skipping to change at page 53, line 5
and AAL5. The other(4) may be user-defined and AAL5. The other(4) may be user-defined
AAL type. The unknown type indicates that AAL type. The unknown type indicates that
the AAL type cannot be determined." the AAL type cannot be determined."
DEFVAL { aal5 } DEFVAL { aal5 }
::= { atmVclEntry 8 } ::= { atmVclEntry 8 }
atmVccAal5CpcsTransmitSduSize OBJECT-TYPE atmVccAal5CpcsTransmitSduSize OBJECT-TYPE
SYNTAX INTEGER (1..65535) SYNTAX INTEGER (1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this object only exists when the "An instance of this object only exists when the
local VCL end-point is also the VCC end-point, local VCL end-point is also the VCC end-point,
and AAL5 is in use. and AAL5 is in use.
The maximum AAL5 CPCS SDU size in octets that is The maximum AAL5 CPCS SDU size in octets that is
supported on the transmit direction of this VCC." supported on the transmit direction of this VCC."
DEFVAL { 9188 } DEFVAL { 9188 }
::= { atmVclEntry 9 } ::= { atmVclEntry 9 }
skipping to change at page 56, line 5 skipping to change at page 54, line 5
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this object only exists when the "An instance of this object only exists when the
local VCL end-point is also the VCC end-point, local VCL end-point is also the VCC end-point,
and AAL5 is in use. and AAL5 is in use.
The type of data encapsulation used over The type of data encapsulation used over
the AAL5 SSCS layer. The definitions reference the AAL5 SSCS layer. The definitions reference
RFC 1483 Multiprotocol Encapsulation RFC 1483 Multiprotocol Encapsulation
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
over ATM AAL5 and to the ATM Forum over ATM AAL5 and to the ATM Forum
LAN Emulation specification." LAN Emulation specification."
DEFVAL { llcEncapsulation } DEFVAL { llcEncapsulation }
::= { atmVclEntry 11 } ::= { atmVclEntry 11 }
atmVclCrossConnectIdentifier OBJECT-TYPE atmVclCrossConnectIdentifier OBJECT-TYPE
SYNTAX INTEGER (0..2147483647) SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 57, line 5 skipping to change at page 55, line 5
"This object is used to create, delete or "This object is used to create, delete or
modify a row in this table. To create modify a row in this table. To create
a new VCL, this object is initially set a new VCL, this object is initially set
to 'createAndWait' or 'createAndGo'. to 'createAndWait' or 'createAndGo'.
This object should not be This object should not be
set to 'active' unless the following columnar set to 'active' unless the following columnar
objects have been set to their desired value objects have been set to their desired value
in this row: in this row:
atmVclReceiveTrafficDescrIndex, atmVclReceiveTrafficDescrIndex,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmVclTransmitTrafficDescrIndex. atmVclTransmitTrafficDescrIndex.
In addition, if the local VCL end-point In addition, if the local VCL end-point
is also the VCC end-point: is also the VCC end-point:
atmVccAalType. atmVccAalType.
In addition, for AAL5 connections only: In addition, for AAL5 connections only:
atmVccAal5CpcsTransmitSduSize, atmVccAal5CpcsTransmitSduSize,
atmVccAal5CpcsReceiveSduSize, and atmVccAal5CpcsReceiveSduSize, and
atmVccAal5EncapsType. (The existence atmVccAal5EncapsType. (The existence
of these objects imply the AAL connection type.)" of these objects imply the AAL connection type.).
DEFVAL { active } The DESCRIPTION of atmVclEntry provides
further guidance to row treatment in this table."
DEFVAL { createAndWait }
::= {atmVclEntry 13} ::= {atmVclEntry 13}
atmVclCastType OBJECT-TYPE atmVclCastType OBJECT-TYPE
SYNTAX AtmConnCastType SYNTAX AtmConnCastType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The connection topology type." "The connection topology type."
DEFVAL { p2p } DEFVAL { p2p }
::= {atmVclEntry 14} ::= {atmVclEntry 14}
atmVclConnKind OBJECT-TYPE atmVclConnKind OBJECT-TYPE
SYNTAX AtmConnKind SYNTAX AtmConnKind
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The use of call control." "The use of call control."
DEFVAL { pvc } DEFVAL { pvc }
::= {atmVclEntry 15} ::= {atmVclEntry 15}
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Virtual Path (VP) Cross Connect Table -- ATM Virtual Path (VP) Cross Connect Table
-- This table contains configuration and state -- This table contains configuration and state
-- information of point-to-point, -- information of point-to-point,
-- point-to-multipoint, or multipoint-to-multipoint -- point-to-multipoint, or multipoint-to-multipoint
-- VP cross-connects for PVCs. -- VP cross-connects for PVCs.
-- This table has read-create access and can be used -- This table has read-create access and can be used
-- to cross-connect the VPLs together in an ATM switch -- to cross-connect the VPLs together in an ATM switch
skipping to change at page 59, line 5 skipping to change at page 57, line 5
-- The terms low and high are chosen to represent -- The terms low and high are chosen to represent
-- numerical ordering of the two interfaces associated -- numerical ordering of the two interfaces associated
-- with a VPC cross-connect. That is, the ATM interface -- with a VPC cross-connect. That is, the ATM interface
-- with the lower value of ifIndex is termed 'low', -- with the lower value of ifIndex is termed 'low',
-- while the other ATM interface associated with the -- while the other ATM interface associated with the
-- VPC cross-connect is termed 'high'. This terminology -- VPC cross-connect is termed 'high'. This terminology
-- is used to provide directional information; for -- is used to provide directional information; for
-- example, the atmVpCrossConnectL2HOperStatus applies -- example, the atmVpCrossConnectL2HOperStatus applies
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- to the low->high direction, and -- to the low->high direction, and
-- atmVpCrossConnectH2LOperStatus applies to the -- atmVpCrossConnectH2LOperStatus applies to the
-- high->low direction, as illustrated above. -- high->low direction, as illustrated above.
atmVpCrossConnectIndexNext OBJECT-TYPE atmVpCrossConnectIndexNext OBJECT-TYPE
SYNTAX INTEGER (0..2147483647) SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to "This object contains an appropriate value to
be used for atmVpCrossConnectIndex when creating be used for atmVpCrossConnectIndex when creating
entries in the atmVpCrossConnectTable. The value entries in the atmVpCrossConnectTable. The value
0 indicates that no unassigned entries are 0 indicates that no unassigned entries are
available. To obtain the atmVpCrossConnectIndex available. To obtain the atmVpCrossConnectIndex
value for a new entry, the manager issues a value for a new entry, the manager issues a
management protocol retrieval operation to obtain management protocol retrieval operation to obtain
the current value of this object. After each the current value of this object. After each
retrieval, the agent should modify the value to retrieval, the agent should modify the value to
the next unassigned index." the next unassigned index.
After a manager retrieves a value the agent will
determine through its local policy when this index
value will be made available for reuse."
::= { atmMIBObjects 8 } ::= { atmMIBObjects 8 }
-- The ATM VP Cross Connect Table -- The ATM VP Cross Connect Table
atmVpCrossConnectTable OBJECT-TYPE atmVpCrossConnectTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmVpCrossConnectEntry SYNTAX SEQUENCE OF AtmVpCrossConnectEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ATM VP Cross Connect table for PVCs. "The ATM VP Cross Connect table for PVCs.
An entry in this table models two An entry in this table models two
cross-connected VPLs. cross-connected VPLs.
Each VPL must have its atmConnKind set Each VPL must have its atmConnKind set
to pvc(1)." to pvc(1)."
::= { atmMIBObjects 9 } ::= { atmMIBObjects 9 }
atmVpCrossConnectEntry OBJECT-TYPE atmVpCrossConnectEntry OBJECT-TYPE
draft ATM Management Objects October 19, 1998
SYNTAX AtmVpCrossConnectEntry SYNTAX AtmVpCrossConnectEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft ATM Management Objects August 15, 1998
DESCRIPTION DESCRIPTION
"An entry in the ATM VP Cross Connect table. "An entry in the ATM VP Cross Connect table.
This entry is used to model a bi-directional This entry is used to model a bi-directional
ATM VP cross-connect which cross-connects ATM VP cross-connect which cross-connects
two VPLs. two VPLs.
Step-wise Procedures to set up a VP Cross-connect Step-wise Procedures to set up a VP Cross-connect
Once the entries in the atmVplTable are created, Once the entries in the atmVplTable are created,
the following procedures are used the following procedures are used
skipping to change at page 60, line 49 skipping to change at page 59, line 4
the ATM traffic parameters and the ATM traffic parameters and
service categories, i.e., the row creation service categories, i.e., the row creation
fails if: fails if:
- the requested topology is incompatible with - the requested topology is incompatible with
associated values of atmVplCastType, associated values of atmVplCastType,
- the requested topology is not supported - the requested topology is not supported
by the agent, by the agent,
- the traffic/service category parameter values - the traffic/service category parameter values
associated with the requested row are associated with the requested row are
incompatible with those of already existing incompatible with those of already existing
draft ATM Management Objects October 19, 1998
rows for this VP cross-connect. rows for this VP cross-connect.
[For example, for setting up [For example, for setting up
a point-to-point VP cross-connect, the a point-to-point VP cross-connect, the
draft ATM Management Objects August 15, 1998
ATM traffic parameters in the receive direction ATM traffic parameters in the receive direction
of a VPL at the low end of the cross-connect of a VPL at the low end of the cross-connect
must equal to the traffic parameters in the must equal to the traffic parameters in the
transmit direction of the other VPL at the transmit direction of the other VPL at the
high end of the cross-connect, high end of the cross-connect,
otherwise, the row creation fails.] otherwise, the row creation fails.]
The agent also checks for internal errors The agent also checks for internal errors
in building the cross-connect. in building the cross-connect.
The atmVpCrossConnectIndex values in the The atmVpCrossConnectIndex values in the
skipping to change at page 61, line 49 skipping to change at page 60, line 5
set to createAndGo(4). set to createAndGo(4).
In contrast to the negotiated VP cross-connect In contrast to the negotiated VP cross-connect
establishment which allows for detailed error establishment which allows for detailed error
checking (i.e., set errors are explicitly linked checking (i.e., set errors are explicitly linked
to particular resource acquisition failures), to particular resource acquisition failures),
the one-shot VP cross-connect establishment the one-shot VP cross-connect establishment
performs the setup on one operation but does not performs the setup on one operation but does not
have the advantage of step-wise error checking. have the advantage of step-wise error checking.
VP Cross-Connect Retirement draft ATM Management Objects October 19, 1998
draft ATM Management Objects August 15, 1998 VP Cross-Connect Retirement
A VP cross-connect identified by a particular A VP cross-connect identified by a particular
value of atmVpCrossConnectIndex is released by: value of atmVpCrossConnectIndex is released by:
(1) Setting atmVpCrossConnectRowStatus of all (1) Setting atmVpCrossConnectRowStatus of all
rows identified by this value of rows identified by this value of
atmVpCrossConnectIndex to destroy(6). atmVpCrossConnectIndex to destroy(6).
The agent may release all The agent may release all
associated resources, and the associated resources, and the
atmVpCrossConnectIndex values in the atmVpCrossConnectIndex values in the
skipping to change at page 62, line 50 skipping to change at page 61, line 4
atmVpCrossConnectLowIfIndex, atmVpCrossConnectLowIfIndex,
atmVpCrossConnectLowVpi, atmVpCrossConnectLowVpi,
atmVpCrossConnectHighIfIndex, atmVpCrossConnectHighIfIndex,
atmVpCrossConnectHighVpi } atmVpCrossConnectHighVpi }
::= { atmVpCrossConnectTable 1 } ::= { atmVpCrossConnectTable 1 }
AtmVpCrossConnectEntry ::= SEQUENCE { AtmVpCrossConnectEntry ::= SEQUENCE {
atmVpCrossConnectIndex INTEGER, atmVpCrossConnectIndex INTEGER,
atmVpCrossConnectLowIfIndex InterfaceIndex, atmVpCrossConnectLowIfIndex InterfaceIndex,
atmVpCrossConnectLowVpi AtmVpIdentifier, atmVpCrossConnectLowVpi AtmVpIdentifier,
atmVpCrossConnectHighIfIndex InterfaceIndex,
atmVpCrossConnectHighVpi AtmVpIdentifier,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmVpCrossConnectHighIfIndex InterfaceIndex,
atmVpCrossConnectHighVpi AtmVpIdentifier,
atmVpCrossConnectAdminStatus AtmVorXAdminStatus, atmVpCrossConnectAdminStatus AtmVorXAdminStatus,
atmVpCrossConnectL2HOperStatus AtmVorXOperStatus, atmVpCrossConnectL2HOperStatus AtmVorXOperStatus,
atmVpCrossConnectH2LOperStatus AtmVorXOperStatus, atmVpCrossConnectH2LOperStatus AtmVorXOperStatus,
atmVpCrossConnectL2HLastChange AtmVorXLastChange, atmVpCrossConnectL2HLastChange AtmVorXLastChange,
atmVpCrossConnectH2LLastChange AtmVorXLastChange, atmVpCrossConnectH2LLastChange AtmVorXLastChange,
atmVpCrossConnectRowStatus RowStatus atmVpCrossConnectRowStatus RowStatus
} }
atmVpCrossConnectIndex OBJECT-TYPE atmVpCrossConnectIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
skipping to change at page 63, line 50 skipping to change at page 62, line 4
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VPI value at the ATM interface "The VPI value at the ATM interface
associated with the VP cross-connect that is associated with the VP cross-connect that is
identified by atmVpCrossConnectLowIfIndex." identified by atmVpCrossConnectLowIfIndex."
::= { atmVpCrossConnectEntry 3 } ::= { atmVpCrossConnectEntry 3 }
atmVpCrossConnectHighIfIndex OBJECT-TYPE atmVpCrossConnectHighIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the ATM interface for "The ifIndex value of the ATM interface for
this VP cross-connect. The term high implies that this VP cross-connect. The term high implies that
this ATM interface has the numerically higher this ATM interface has the numerically higher
ifIndex value than the other ATM interface ifIndex value than the other ATM interface
identified in the same atmVpCrossConnectEntry." identified in the same atmVpCrossConnectEntry."
::= { atmVpCrossConnectEntry 4 } ::= { atmVpCrossConnectEntry 4 }
atmVpCrossConnectHighVpi OBJECT-TYPE atmVpCrossConnectHighVpi OBJECT-TYPE
skipping to change at page 64, line 50 skipping to change at page 63, line 4
DESCRIPTION DESCRIPTION
"The operational status of the VP cross-connect "The operational status of the VP cross-connect
in one direction; (i.e., from the low to in one direction; (i.e., from the low to
high direction)." high direction)."
::= { atmVpCrossConnectEntry 7 } ::= { atmVpCrossConnectEntry 7 }
atmVpCrossConnectH2LOperStatus OBJECT-TYPE atmVpCrossConnectH2LOperStatus OBJECT-TYPE
SYNTAX AtmVorXOperStatus SYNTAX AtmVorXOperStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION
"The operational status of the VP cross-connect
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DESCRIPTION
"The operational status of the VP cross-connect
in one direction; (i.e., from the high to in one direction; (i.e., from the high to
low direction)." low direction)."
::= { atmVpCrossConnectEntry 8 } ::= { atmVpCrossConnectEntry 8 }
atmVpCrossConnectL2HLastChange OBJECT-TYPE atmVpCrossConnectL2HLastChange OBJECT-TYPE
SYNTAX AtmVorXLastChange SYNTAX AtmVorXLastChange
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
skipping to change at page 65, line 46 skipping to change at page 63, line 48
"The status of this entry in the "The status of this entry in the
atmVpCrossConnectTable. This object is used to atmVpCrossConnectTable. This object is used to
create a cross-connect for cross-connecting create a cross-connect for cross-connecting
VPLs which are created using the atmVplTable VPLs which are created using the atmVplTable
or to change or delete an existing cross-connect. or to change or delete an existing cross-connect.
This object must be initially set This object must be initially set
to `createAndWait' or 'createAndGo'. to `createAndWait' or 'createAndGo'.
To turn on a VP cross-connect, To turn on a VP cross-connect,
the atmVpCrossConnectAdminStatus the atmVpCrossConnectAdminStatus
is set to `up'." is set to `up'."
DEFVAL { active } DEFVAL { createAndWait }
::= { atmVpCrossConnectEntry 11 } ::= { atmVpCrossConnectEntry 11 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- ATM Virtual Channel (VC) Cross Connect Table -- ATM Virtual Channel (VC) Cross Connect Table
-- This table contains configuration and state -- This table contains configuration and state
-- information of point-to-point, -- information of point-to-point,
-- point-to-multipoint or multipoint-to-multipoint -- point-to-multipoint or multipoint-to-multipoint
-- VC cross-connects for PVCs. -- VC cross-connects for PVCs.
-- This table has read-create access and is used -- This table has read-create access and is used
-- to cross-connect the VCLs together in an ATM switch -- to cross-connect the VCLs together in an ATM switch
skipping to change at page 66, line 38 skipping to change at page 64, line 38
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to "This object contains an appropriate value to
be used for atmVcCrossConnectIndex when creating be used for atmVcCrossConnectIndex when creating
entries in the atmVcCrossConnectTable. The value entries in the atmVcCrossConnectTable. The value
0 indicates that no unassigned entries are 0 indicates that no unassigned entries are
available. To obtain the atmVcCrossConnectIndex available. To obtain the atmVcCrossConnectIndex
value for a new entry, the manager issues a value for a new entry, the manager issues a
management protocol retrieval operation to obtain management protocol retrieval operation to obtain
the current value of this object. After each the current value of this object. After each
retrieval, the agent should modify the value to retrieval, the agent should modify the value to
the next unassigned index." the next unassigned index.
After a manager retrieves a value the agent will
determine through its local policy when this index
value will be made available for reuse."
::= { atmMIBObjects 10 } ::= { atmMIBObjects 10 }
-- The ATM VC Cross Connect Table -- The ATM VC Cross Connect Table
atmVcCrossConnectTable OBJECT-TYPE atmVcCrossConnectTable OBJECT-TYPE
draft ATM Management Objects October 19, 1998
SYNTAX SEQUENCE OF AtmVcCrossConnectEntry SYNTAX SEQUENCE OF AtmVcCrossConnectEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft ATM Management Objects August 15, 1998
DESCRIPTION DESCRIPTION
"The ATM VC Cross Connect table for PVCs. "The ATM VC Cross Connect table for PVCs.
An entry in this table models two An entry in this table models two
cross-connected VCLs. cross-connected VCLs.
Each VCL must have its atmConnKind set Each VCL must have its atmConnKind set
to pvc(1)." to pvc(1)."
::= { atmMIBObjects 11 } ::= { atmMIBObjects 11 }
atmVcCrossConnectEntry OBJECT-TYPE atmVcCrossConnectEntry OBJECT-TYPE
SYNTAX AtmVcCrossConnectEntry SYNTAX AtmVcCrossConnectEntry
skipping to change at page 67, line 48 skipping to change at page 66, line 4
two VCLs. Each row is indexed by the ATM two VCLs. Each row is indexed by the ATM
interface port numbers and VPI/VCI values of interface port numbers and VPI/VCI values of
the two ends of that cross-connection. the two ends of that cross-connection.
This set of rows specifies the topology of the This set of rows specifies the topology of the
VCC cross-connect and is identified by a single VCC cross-connect and is identified by a single
value of atmVcCrossConnectIndex. value of atmVcCrossConnectIndex.
Negotiated VC Cross-Connect Establishment Negotiated VC Cross-Connect Establishment
(2a) The manager creates a row in this table by (2a) The manager creates a row in this table by
draft ATM Management Objects October 19, 1998
setting atmVcCrossConnectRowStatus to setting atmVcCrossConnectRowStatus to
createAndWait(5). The agent checks the createAndWait(5). The agent checks the
requested topology and the mutual sanity of requested topology and the mutual sanity of
draft ATM Management Objects August 15, 1998
the ATM traffic parameters and the ATM traffic parameters and
service categories, i.e., the row creation service categories, i.e., the row creation
fails if: fails if:
- the requested topology is incompatible with - the requested topology is incompatible with
associated values of atmVclCastType, associated values of atmVclCastType,
- the requested topology is not supported - the requested topology is not supported
by the agent, by the agent,
- the traffic/service category parameter values - the traffic/service category parameter values
associated with the requested row are associated with the requested row are
incompatible with those of already existing incompatible with those of already existing
skipping to change at page 68, line 49 skipping to change at page 67, line 5
for each direction of the VC cross-connect for each direction of the VC cross-connect
in an ATM switch or network. in an ATM switch or network.
(3) The manager sets the (3) The manager sets the
atmVcCrossConnectAdminStatus to up(1) atmVcCrossConnectAdminStatus to up(1)
in all rows of this VC cross-connect to in all rows of this VC cross-connect to
turn the traffic flow on. turn the traffic flow on.
One-Shot VC Cross-Connect Establishment One-Shot VC Cross-Connect Establishment
draft ATM Management Objects October 19, 1998
A VC cross-connect may also be established in A VC cross-connect may also be established in
one step by a set-request with all necessary one step by a set-request with all necessary
draft ATM Management Objects August 15, 1998
parameter values and atmVcCrossConnectRowStatus parameter values and atmVcCrossConnectRowStatus
set to createAndGo(4). set to createAndGo(4).
In contrast to the negotiated VC cross-connect In contrast to the negotiated VC cross-connect
establishment which allows for detailed error establishment which allows for detailed error
checking i.e., set errors are explicitly linked to checking i.e., set errors are explicitly linked to
particular resource acquisition failures), the particular resource acquisition failures), the
one-shot VC cross-connect establishment one-shot VC cross-connect establishment
performs the setup on one operation but does performs the setup on one operation but does
not have the advantage of step-wise error not have the advantage of step-wise error
skipping to change at page 69, line 50 skipping to change at page 68, line 4
rows in the atmVclTable. rows in the atmVclTable.
VC Cross-Connect Reconfiguration VC Cross-Connect Reconfiguration
At the discretion of the agent, a VC At the discretion of the agent, a VC
cross-connect may be reconfigured by cross-connect may be reconfigured by
adding and/or deleting leafs to/from adding and/or deleting leafs to/from
the VC topology as per the VC cross-connect the VC topology as per the VC cross-connect
establishment/retirement procedures. establishment/retirement procedures.
Reconfiguration of traffic/service category parameter Reconfiguration of traffic/service category parameter
values requires release of the VC cross-connect
before those parameter values may by changed
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
values requires release of the VC cross-connect
before those parameter values may by changed
for individual VCLs." for individual VCLs."
INDEX { atmVcCrossConnectIndex, INDEX { atmVcCrossConnectIndex,
atmVcCrossConnectLowIfIndex, atmVcCrossConnectLowIfIndex,
atmVcCrossConnectLowVpi, atmVcCrossConnectLowVpi,
atmVcCrossConnectLowVci, atmVcCrossConnectLowVci,
atmVcCrossConnectHighIfIndex, atmVcCrossConnectHighIfIndex,
atmVcCrossConnectHighVpi, atmVcCrossConnectHighVpi,
atmVcCrossConnectHighVci } atmVcCrossConnectHighVci }
::= { atmVcCrossConnectTable 1 } ::= { atmVcCrossConnectTable 1 }
skipping to change at page 70, line 50 skipping to change at page 69, line 4
the agent reports this cross-connect index value the agent reports this cross-connect index value
in the atmVclCrossConnectIdentifier attribute of in the atmVclCrossConnectIdentifier attribute of
the corresponding atmVclTable entries." the corresponding atmVclTable entries."
::= { atmVcCrossConnectEntry 1 } ::= { atmVcCrossConnectEntry 1 }
atmVcCrossConnectLowIfIndex OBJECT-TYPE atmVcCrossConnectLowIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the ATM interface for this
VC cross-connect. The term low implies
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
"The ifIndex value of the ATM interface for this
VC cross-connect. The term low implies
that this ATM interface has the numerically lower that this ATM interface has the numerically lower
ifIndex value than the other ATM interface ifIndex value than the other ATM interface
identified in the same atmVcCrossConnectEntry." identified in the same atmVcCrossConnectEntry."
::= { atmVcCrossConnectEntry 2 } ::= { atmVcCrossConnectEntry 2 }
atmVcCrossConnectLowVpi OBJECT-TYPE atmVcCrossConnectLowVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 71, line 50 skipping to change at page 70, line 4
ifIndex value than the other ATM interface ifIndex value than the other ATM interface
identified in the same atmVcCrossConnectEntry." identified in the same atmVcCrossConnectEntry."
::= { atmVcCrossConnectEntry 5 } ::= { atmVcCrossConnectEntry 5 }
atmVcCrossConnectHighVpi OBJECT-TYPE atmVcCrossConnectHighVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VPI value at the ATM interface "The VPI value at the ATM interface
associated with the VC cross-connect that is
identified by atmVcCrossConnectHighIfIndex."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
associated with the VC cross-connect that is
identified by atmVcCrossConnectHighIfIndex."
::= { atmVcCrossConnectEntry 6 } ::= { atmVcCrossConnectEntry 6 }
atmVcCrossConnectHighVci OBJECT-TYPE atmVcCrossConnectHighVci OBJECT-TYPE
SYNTAX AtmVcIdentifier SYNTAX AtmVcIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VCI value at the ATM interface "The VCI value at the ATM interface
associated with the VC cross-connect that is associated with the VC cross-connect that is
identified by atmVcCrossConnectHighIfIndex." identified by atmVcCrossConnectHighIfIndex."
skipping to change at page 72, line 49 skipping to change at page 71, line 5
atmVcCrossConnectH2LOperStatus OBJECT-TYPE atmVcCrossConnectH2LOperStatus OBJECT-TYPE
SYNTAX AtmVorXOperStatus SYNTAX AtmVorXOperStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of the "The current operational status of the
VC cross-connect in one direction; (i.e., VC cross-connect in one direction; (i.e.,
from the high to low direction)." from the high to low direction)."
::= { atmVcCrossConnectEntry 10 } ::= { atmVcCrossConnectEntry 10 }
draft ATM Management Objects October 19, 1998
atmVcCrossConnectL2HLastChange OBJECT-TYPE atmVcCrossConnectL2HLastChange OBJECT-TYPE
SYNTAX AtmVorXLastChange SYNTAX AtmVorXLastChange
draft ATM Management Objects August 15, 1998
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
VC cross-connect entered its current VC cross-connect entered its current
operational state in low to high direction." operational state in low to high direction."
::= { atmVcCrossConnectEntry 11 } ::= { atmVcCrossConnectEntry 11 }
atmVcCrossConnectH2LLastChange OBJECT-TYPE atmVcCrossConnectH2LLastChange OBJECT-TYPE
SYNTAX AtmVorXLastChange SYNTAX AtmVorXLastChange
skipping to change at page 73, line 40 skipping to change at page 71, line 42
"The status of this entry in the "The status of this entry in the
atmVcCrossConnectTable. This object is used to atmVcCrossConnectTable. This object is used to
create a new cross-connect for cross-connecting create a new cross-connect for cross-connecting
VCLs which are created using the atmVclTable VCLs which are created using the atmVclTable
or to change or delete existing cross-connect. or to change or delete existing cross-connect.
This object must be initially set to This object must be initially set to
`createAndWait' or 'createAndGo'. `createAndWait' or 'createAndGo'.
To turn on a VC cross-connect, To turn on a VC cross-connect,
the atmVcCrossConnectAdminStatus the atmVcCrossConnectAdminStatus
is set to `up'." is set to `up'."
DEFVAL { active } DEFVAL { createAndWait }
::= { atmVcCrossConnectEntry 13 } ::= { atmVcCrossConnectEntry 13 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- AAL5 Virtual Channel Connection Performance Statistics -- AAL5 Virtual Channel Connection Performance Statistics
-- Table -- Table
-- This table contains the AAL5 -- This table contains the AAL5
-- performance statistics of a VCC at the -- performance statistics of a VCC at the
-- interface associated with an AAL5 entity in an ATM -- interface associated with an AAL5 entity in an ATM
-- host or ATM switch. -- host or ATM switch.
aal5VccTable OBJECT-TYPE aal5VccTable OBJECT-TYPE
skipping to change at page 75, line 5 skipping to change at page 73, line 5
aal5VccOverSizedSDUs Counter32 aal5VccOverSizedSDUs Counter32
} }
aal5VccVpi OBJECT-TYPE aal5VccVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VPI value of the AAL5 VCC at the "The VPI value of the AAL5 VCC at the
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
interface identified by the ifIndex." interface identified by the ifIndex."
::= { aal5VccEntry 1 } ::= { aal5VccEntry 1 }
aal5VccVci OBJECT-TYPE aal5VccVci OBJECT-TYPE
SYNTAX AtmVcIdentifier SYNTAX AtmVcIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VCI value of the AAL5 VCC at the "The VCI value of the AAL5 VCC at the
skipping to change at page 76, line 5 skipping to change at page 74, line 5
aal5VccOverSizedSDUs OBJECT-TYPE aal5VccOverSizedSDUs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of AAL5 CPCS PDUs discarded "The number of AAL5 CPCS PDUs discarded
on this AAL5 VCC at the interface on this AAL5 VCC at the interface
associated with an AAL5 entity because the associated with an AAL5 entity because the
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
AAL5 SDUs were too large." AAL5 SDUs were too large."
::= { aal5VccEntry 5 } ::= { aal5VccEntry 5 }
-- --
-- The following object may be used in conjunction with -- The following object may be used in conjunction with
-- the atmTrafficDescrParamTable for the creation of -- the atmTrafficDescrParamTable for the creation of
-- new table entries. -- new table entries.
-- --
skipping to change at page 76, line 32 skipping to change at page 74, line 32
be used for atmTrafficDescrParamIndex when be used for atmTrafficDescrParamIndex when
creating entries in the creating entries in the
atmTrafficDescrParamTable. atmTrafficDescrParamTable.
The value 0 indicates that no unassigned The value 0 indicates that no unassigned
entries are available. To obtain the entries are available. To obtain the
atmTrafficDescrParamIndex value for a new atmTrafficDescrParamIndex value for a new
entry, the manager issues a management entry, the manager issues a management
protocol retrieval operation to obtain the protocol retrieval operation to obtain the
current value of this object. After each current value of this object. After each
retrieval, the agent should modify the value retrieval, the agent should modify the value
to the next unassigned index." to the next unassigned index.
After a manager retrieves a value the agent will
determine through its local policy when this index
value will be made available for reuse."
::= { atmMIBObjects 13 } ::= { atmMIBObjects 13 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- Conformance Information -- Conformance Information
atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 } atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 }
atmMIBGroups OBJECT IDENTIFIER atmMIBGroups OBJECT IDENTIFIER
::= { atmMIBConformance 1 } ::= { atmMIBConformance 1 }
atmMIBCompliances OBJECT IDENTIFIER atmMIBCompliances OBJECT IDENTIFIER
::= { atmMIBConformance 2 } ::= { atmMIBConformance 2 }
skipping to change at page 78, line 5 skipping to change at page 76, line 5
OBJECT atmInterfaceMaxActiveVpiBits OBJECT atmInterfaceMaxActiveVpiBits
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. "Write access is not required.
At the ATM UNI the maximum number of At the ATM UNI the maximum number of
active VPI bits configured for use ranges active VPI bits configured for use ranges
from 0 to 8 only. from 0 to 8 only.
Implementations may support smaller ranges." Implementations may support smaller ranges."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
OBJECT atmInterfaceMaxActiveVciBits OBJECT atmInterfaceMaxActiveVciBits
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. "Write access is not required.
Implementations may support smaller ranges." Implementations may support smaller ranges."
OBJECT atmInterfaceIlmiVpi OBJECT atmInterfaceIlmiVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 79, line 5 skipping to change at page 77, line 5
OBJECT atmTrafficDescrType OBJECT atmTrafficDescrType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmTrafficDescrParam1 OBJECT atmTrafficDescrParam1
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
"Write access is not required." "Write access is not required."
OBJECT atmTrafficDescrParam2 OBJECT atmTrafficDescrParam2
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmTrafficDescrParam3 OBJECT atmTrafficDescrParam3
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 80, line 5 skipping to change at page 78, line 5
OBJECT atmTrafficFrameDiscard OBJECT atmTrafficFrameDiscard
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- --
-- ****** DS3 PLCP Support ************************** -- ****** DS3 PLCP Support **************************
-- --
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
GROUP atmInterfaceDs3PlcpGroup GROUP atmInterfaceDs3PlcpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those "This group is mandatory only for those
ATM interfaces which implement the ATM interfaces which implement the
DS3 PLCP layer." DS3 PLCP layer."
-- --
-- ****** TC Sublayer Support ******************************** -- ****** TC Sublayer Support ********************************
-- --
GROUP atmInterfaceTCGroup GROUP atmInterfaceTCGroup
skipping to change at page 81, line 5 skipping to change at page 79, line 5
VPLs that are not associated with VCLs VPLs that are not associated with VCLs
and are cross-connected to other VPLs and are cross-connected to other VPLs
for permanent VPCs (i.e., PVCs). for permanent VPCs (i.e., PVCs).
This group is not used to crossconnect This group is not used to crossconnect
a PVC with an SVC to form a Soft PVC." a PVC with an SVC to form a Soft PVC."
OBJECT atmVplAdminStatus OBJECT atmVplAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
"Write access is not required." "Write access is not required."
OBJECT atmVplReceiveTrafficDescrIndex OBJECT atmVplReceiveTrafficDescrIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVplTransmitTrafficDescrIndex OBJECT atmVplTransmitTrafficDescrIndex
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 82, line 5 skipping to change at page 80, line 5
OBJECT atmVpCrossConnectRowStatus OBJECT atmVpCrossConnectRowStatus
SYNTAX INTEGER {active(1)} SYNTAX INTEGER {active(1)}
-- subset of RowStatus -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required, and only one
of the six enumerated values for the of the six enumerated values for the
RowStatus textual convention need be RowStatus textual convention need be
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
supported, specifically: active(1)." supported, specifically: active(1)."
-- --
-- ****** VCC Support ******************************* -- ****** VCC Support *******************************
-- --
GROUP atmVccTerminationGroup2 GROUP atmVccTerminationGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory only for those "This group is mandatory only for those
ATM interfaces which implement ATM ATM interfaces which implement ATM
skipping to change at page 83, line 5 skipping to change at page 81, line 5
"Write access is not required." "Write access is not required."
OBJECT atmVclTransmitTrafficDescrIndex OBJECT atmVclTransmitTrafficDescrIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVccAalType OBJECT atmVccAalType
MIN-ACCESS read-only MIN-ACCESS read-only
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVclRowStatus OBJECT atmVclRowStatus
SYNTAX INTEGER {active(1)} SYNTAX INTEGER {active(1)}
-- subset of RowStatus -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required, and only one
skipping to change at page 84, line 5 skipping to change at page 82, line 5
RowStatus textual convention need be RowStatus textual convention need be
supported, specifically: active(1)." supported, specifically: active(1)."
-- --
-- ****** AAL5 Support ****************************** -- ****** AAL5 Support ******************************
-- --
GROUP aal5VccGroup GROUP aal5VccGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for the "This group is mandatory for the
AAL5 virtual connections only." AAL5 virtual connections only."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
OBJECT atmVccAal5CpcsTransmitSduSize OBJECT atmVccAal5CpcsTransmitSduSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVccAal5CpcsReceiveSduSize OBJECT atmVccAal5CpcsReceiveSduSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVccAal5EncapsType OBJECT atmVccAal5EncapsType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { atmMIBCompliances 2 } ::= { atmMIBCompliances 2 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- Units of Conformance -- Units of Conformance
atmInterfaceDs3PlcpGroup OBJECT-GROUP atmInterfaceDs3PlcpGroup OBJECT-GROUP
OBJECTS {atmInterfaceDs3PlcpSEFSs, OBJECTS {atmInterfaceDs3PlcpSEFSs,
atmInterfaceDs3PlcpAlarmState, atmInterfaceDs3PlcpAlarmState,
atmInterfaceDs3PlcpUASs} atmInterfaceDs3PlcpUASs}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information "A collection of objects providing information
skipping to change at page 86, line 5 skipping to change at page 84, line 5
atmInterfaceMaxVpcs, atmInterfaceMaxVccs, atmInterfaceMaxVpcs, atmInterfaceMaxVccs,
atmInterfaceConfVpcs, atmInterfaceConfVccs, atmInterfaceConfVpcs, atmInterfaceConfVccs,
atmInterfaceMaxActiveVpiBits, atmInterfaceMaxActiveVpiBits,
atmInterfaceMaxActiveVciBits, atmInterfaceMaxActiveVciBits,
atmInterfaceIlmiVpi, atmInterfaceIlmiVpi,
atmInterfaceIlmiVci, atmInterfaceIlmiVci,
atmInterfaceMyNeighborIpAddress, atmInterfaceMyNeighborIpAddress,
atmInterfaceMyNeighborIfName, atmInterfaceMyNeighborIfName,
atmInterfaceCurrentMaxVpiBits, atmInterfaceCurrentMaxVpiBits,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
atmInterfaceCurrentMaxVciBits, atmInterfaceCurrentMaxVciBits,
atmInterfaceSubscrAddress } atmInterfaceSubscrAddress }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information about an ATM interface." information about an ATM interface."
::= { atmMIBGroups 10 } ::= { atmMIBGroups 10 }
atmTrafficDescrGroup2 OBJECT-GROUP atmTrafficDescrGroup2 OBJECT-GROUP
skipping to change at page 87, line 5 skipping to change at page 85, line 5
::= { atmMIBGroups 12 } ::= { atmMIBGroups 12 }
atmVccTerminationGroup2 OBJECT-GROUP atmVccTerminationGroup2 OBJECT-GROUP
OBJECTS {atmVclOperStatus, atmVclAdminStatus, OBJECTS {atmVclOperStatus, atmVclAdminStatus,
atmVclLastChange, atmVclLastChange,
atmVclReceiveTrafficDescrIndex, atmVclReceiveTrafficDescrIndex,
atmVclTransmitTrafficDescrIndex, atmVclTransmitTrafficDescrIndex,
atmVccAalType, atmVclRowStatus, atmVccAalType, atmVclRowStatus,
atmVclCastType, atmVclConnKind } atmVclCastType, atmVclConnKind }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information "A collection of objects providing information
about a VCL at an ATM interface about a VCL at an ATM interface
which terminates a VCC (i.e., one which is which terminates a VCC (i.e., one which is
NOT cross-connected to other VCLs)." NOT cross-connected to other VCLs)."
::= { atmMIBGroups 13 } ::= { atmMIBGroups 13 }
atmVplCrossConnectGroup OBJECT-GROUP atmVplCrossConnectGroup OBJECT-GROUP
skipping to change at page 88, line 5 skipping to change at page 86, line 5
::= { atmMIBGroups 15 } ::= { atmMIBGroups 15 }
atmVclCrossConnectGroup OBJECT-GROUP atmVclCrossConnectGroup OBJECT-GROUP
OBJECTS { atmVclReceiveTrafficDescrIndex, OBJECTS { atmVclReceiveTrafficDescrIndex,
atmVclTransmitTrafficDescrIndex, atmVclTransmitTrafficDescrIndex,
atmVclOperStatus, atmVclLastChange, atmVclOperStatus, atmVclLastChange,
atmVclRowStatus, atmVclRowStatus,
atmVclCastType, atmVclConnKind } atmVclCastType, atmVclConnKind }
STATUS current STATUS current
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
DESCRIPTION DESCRIPTION
"A collection of objects providing "A collection of objects providing
information about the VCLs that information about the VCLs that
are cross-connected together." are cross-connected together."
::= { atmMIBGroups 16 } ::= { atmMIBGroups 16 }
atmVcPvcCrossConnectGroup OBJECT-GROUP atmVcPvcCrossConnectGroup OBJECT-GROUP
OBJECTS { atmVcCrossConnectAdminStatus, OBJECTS { atmVcCrossConnectAdminStatus,
atmVcCrossConnectL2HOperStatus, atmVcCrossConnectL2HOperStatus,
skipping to change at page 89, line 5 skipping to change at page 87, line 5
atmVclCrossConnectIdentifier, atmVclCrossConnectIdentifier,
atmVcCrossConnectIndexNext } atmVcCrossConnectIndexNext }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing "A collection of objects providing
information about a VC cross-connect information about a VC cross-connect
for PVCs. These objects are not used for PVCs. These objects are not used
for Soft PVCs or SVCs." for Soft PVCs or SVCs."
::= { atmMIBGroups 17 } ::= { atmMIBGroups 17 }
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
-- Deprecated Definitions - Objects -- Deprecated Definitions - Objects
-- atmInterfaceAddressType -- atmInterfaceAddressType
-- atmTrafficQoSClass -- atmTrafficQoSClass
-- Deprecated Definitions - Compliance -- Deprecated Definitions - Compliance
atmMIBCompliance MODULE-COMPLIANCE atmMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
skipping to change at page 90, line 5 skipping to change at page 88, line 5
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmInterfaceIlmiVpi OBJECT atmInterfaceIlmiVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmInterfaceIlmiVci OBJECT atmInterfaceIlmiVci
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmInterfaceMyNeighborIpAddress OBJECT atmInterfaceMyNeighborIpAddress
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 91, line 5 skipping to change at page 89, line 5
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmTrafficDescrParam5 OBJECT atmTrafficDescrParam5
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmTrafficQoSClass OBJECT atmTrafficQoSClass
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmTrafficDescrRowStatus OBJECT atmTrafficDescrRowStatus
SYNTAX INTEGER {active(1)} SYNTAX INTEGER {active(1)}
-- subset of RowStatus -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 92, line 5 skipping to change at page 90, line 5
"This group is mandatory only for those "This group is mandatory only for those
ATM interfaces which implement ATM ATM interfaces which implement ATM
VPLs that are not associated with VCLs VPLs that are not associated with VCLs
and are cross-connected to other VPLs." and are cross-connected to other VPLs."
OBJECT atmVplAdminStatus OBJECT atmVplAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
OBJECT atmVplReceiveTrafficDescrIndex OBJECT atmVplReceiveTrafficDescrIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVplTransmitTrafficDescrIndex OBJECT atmVplTransmitTrafficDescrIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 93, line 5 skipping to change at page 91, line 5
DESCRIPTION DESCRIPTION
"This group is mandatory only for those "This group is mandatory only for those
ATM interfaces which implement ATM ATM interfaces which implement ATM
VCLs that terminate VCCs (i.e., ones which VCLs that terminate VCCs (i.e., ones which
are NOT cross-connected to other VCLs)." are NOT cross-connected to other VCLs)."
GROUP atmVcCrossConnectGroup GROUP atmVcCrossConnectGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those "This group is mandatory only for those
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
ATM interfaces which implement ATM ATM interfaces which implement ATM
VCLs that are cross-connected to VCLs that are cross-connected to
other VCLs." other VCLs."
OBJECT atmVclAdminStatus OBJECT atmVclAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 94, line 5 skipping to change at page 92, line 5
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT atmVcCrossConnectRowStatus OBJECT atmVcCrossConnectRowStatus
SYNTAX INTEGER { active(1)} SYNTAX INTEGER { active(1)}
-- subset of RowStatus -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required, and only one
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
of the six enumerated values for the of the six enumerated values for the
RowStatus textual convention need be RowStatus textual convention need be
supported, specifically: active(1)." supported, specifically: active(1)."
GROUP aal5VccGroup GROUP aal5VccGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for the "This group is mandatory for the
AAL5 virtual connections only." AAL5 virtual connections only."
skipping to change at page 95, line 5 skipping to change at page 93, line 5
atmInterfaceIlmiVci, atmInterfaceIlmiVci,
atmInterfaceAddressType, atmInterfaceAddressType,
atmInterfaceAdminAddress, atmInterfaceAdminAddress,
atmInterfaceMyNeighborIpAddress, atmInterfaceMyNeighborIpAddress,
atmInterfaceMyNeighborIfName } atmInterfaceMyNeighborIfName }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information about an ATM interface." information about an ATM interface."
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
::= { atmMIBGroups 1 } ::= { atmMIBGroups 1 }
atmTrafficDescrGroup OBJECT-GROUP atmTrafficDescrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
atmTrafficDescrType, atmTrafficDescrParam1, atmTrafficDescrType, atmTrafficDescrParam1,
atmTrafficDescrParam2, atmTrafficDescrParam3, atmTrafficDescrParam2, atmTrafficDescrParam3,
atmTrafficDescrParam4, atmTrafficDescrParam5, atmTrafficDescrParam4, atmTrafficDescrParam5,
atmTrafficQoSClass, atmTrafficDescrRowStatus} atmTrafficQoSClass, atmTrafficDescrRowStatus}
STATUS deprecated STATUS deprecated
skipping to change at page 96, line 5 skipping to change at page 94, line 5
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing information "A collection of objects providing information
about a VCL at an ATM interface about a VCL at an ATM interface
which terminates a VCC (i.e., one which is which terminates a VCC (i.e., one which is
NOT cross-connected to other VCLs)." NOT cross-connected to other VCLs)."
::= { atmMIBGroups 6 } ::= { atmMIBGroups 6 }
atmVpCrossConnectGroup OBJECT-GROUP atmVpCrossConnectGroup OBJECT-GROUP
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
OBJECTS { atmVplReceiveTrafficDescrIndex, OBJECTS { atmVplReceiveTrafficDescrIndex,
atmVplTransmitTrafficDescrIndex, atmVplTransmitTrafficDescrIndex,
atmVplOperStatus, atmVplRowStatus, atmVplOperStatus, atmVplRowStatus,
atmVpCrossConnectAdminStatus, atmVpCrossConnectAdminStatus,
atmVpCrossConnectL2HOperStatus, atmVpCrossConnectL2HOperStatus,
atmVpCrossConnectH2LOperStatus, atmVpCrossConnectH2LOperStatus,
atmVpCrossConnectL2HLastChange, atmVpCrossConnectL2HLastChange,
atmVpCrossConnectH2LLastChange, atmVpCrossConnectH2LLastChange,
atmVpCrossConnectRowStatus, atmVpCrossConnectRowStatus,
skipping to change at page 97, line 5 skipping to change at page 95, line 5
"A collection of objects providing "A collection of objects providing
information about a VC cross-connect information about a VC cross-connect
and the associated VCLs that are and the associated VCLs that are
cross-connected together." cross-connected together."
::= { atmMIBGroups 8 } ::= { atmMIBGroups 8 }
-- {atmMIB 3} has been used by [19]. -- {atmMIB 3} has been used by [19].
END END
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
12. Acknowledgments 10. Acknowledgments
This memo is the result of the work of the AToMMIB Working This memo is the result of the work of the AToMMIB Working
Group. Group.
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
13. References 11. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An [1] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2271, Cabletron Systems, Inc., BMC Software, Inc., RFC 2271, Cabletron Systems, Inc., BMC Software, Inc.,
IBM T. J. Watson Research, January 1998 IBM T. J. Watson Research, January 1998
[2] Rose, M., and K. McCloghrie, "Structure and [2] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-based Identification of Management Information for TCP/IP-based
Internets", RFC 1155, Performance Systems International, Internets", RFC 1155, Performance Systems International,
Hughes LAN Systems, May 1990 Hughes LAN Systems, May 1990
skipping to change at page 99, line 5 skipping to change at page 97, line 5
of the Simple Network Management Protocol (SNMPv2)", RFC of the Simple Network Management Protocol (SNMPv2)", RFC
1904, SNMP Research, Inc., Cisco Systems, Inc., Dover 1904, SNMP Research, Inc., Cisco Systems, Inc., Dover
Beach Consulting, Inc., International Network Services, Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", RFC 1157, SNMP "Simple Network Management Protocol", RFC 1157, SNMP
Research, Performance Systems International, Performance Research, Performance Systems International, Performance
Systems International, MIT Laboratory for Computer Systems International, MIT Laboratory for Computer
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
Science, May 1990. Science, May 1990.
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
and S. Waldbusser, "Introduction to Community-based and S. Waldbusser, "Introduction to Community-based
SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems, SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems,
Inc., Dover Beach Consulting, Inc., International Network Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996. Services, January 1996.
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
skipping to change at page 99, line 28 skipping to change at page 97, line 28
1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover
Beach Consulting, Inc., International Network Services, Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, [11] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2272, SNMP Network Management Protocol (SNMP)", RFC 2272, SNMP
Research, Inc., Cabletron Systems, Inc., BMC Software, Research, Inc., Cabletron Systems, Inc., BMC Software,
Inc., IBM T. J. Watson Research, January 1998. Inc., IBM T. J. Watson Research, January 1998.
[12] version 3 of the Simple Network Management Protocol [12] Blumenthal, U., and B. Wijnen, "User-based Security Model
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January (USM) for version 3 of the Simple Network Management
1998. Protocol (SNMPv3)", RFC 2274, IBM T. J. Watson Research,
January 1998.
[13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
and S. Waldbusser, "Protocol Operations for Version 2 of and S. Waldbusser, "Protocol Operations for Version 2 of
the Simple Network Management Protocol (SNMPv2)", RFC the Simple Network Management Protocol (SNMPv2)", RFC
1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover
Beach Consulting, Inc., International Network Services, Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, MPv3 Applications", [14] Levi, D., Meyer, P., and B. Stewart, MPv3 Applications",
RFC 2273, SNMP Research, Inc., Secure Computing RFC 2273, SNMP Research, Inc., Secure Computing
Corporation, Cisco Systems, January 1998. Corporation, Cisco Systems, January 1998.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2275, IBM T. J. Watson Management Protocol (SNMP)", RFC 2275, IBM T. J. Watson
Research, BMC Software, Inc., Cisco Systems, Inc., Research, BMC Software, Inc., Cisco Systems, Inc.,
January 1998. January 1998.
[16] McCloghrie, K., and M. Rose, Editors, "Management [16] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991. Performance Systems International, March 1991.
[17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC2233, cisco Systems, FTP Software, November MIB", RFC2233, cisco Systems, FTP Software, November
1997. 1997.
[18] Brown, T.A. and K. Tesink, "Definitions of Managed [18] Brown, T.A. and K. Tesink, "Definitions of Managed
Objects for SMDS Interfaces", RFC 1694, Bellcore, May Objects for SMDS Interfaces", RFC 1694, Bellcore, May
1994. 1994.
skipping to change at page 101, line 5 skipping to change at page 98, line 36
0013.002, November 1995. 0013.002, November 1995.
[22] "ATM Forum Private Network-Network Interface [22] "ATM Forum Private Network-Network Interface
Specification, Version 1.0 (PNNI 1.0)", af-sig-0055.000, Specification, Version 1.0 (PNNI 1.0)", af-sig-0055.000,
March 1996. March 1996.
[23] "ATM Forum Integrated Local Management Interface (ILMI) [23] "ATM Forum Integrated Local Management Interface (ILMI)
Specification", Version 4.0", af-ilmi-0065.000, September Specification", Version 4.0", af-ilmi-0065.000, September
1996. 1996.
draft ATM Management Objects August 15, 1998 [24] Ahmed, M. and K. Tesink, "Definitions of Managed Objects
for ATM Management Version 8.0 using SMIv2", RFC1695,
Bell Communications Research, August 1994.
14. Security Considerations draft ATM Management Objects October 19, 1998
This MIB contains both readable objects whose values provide 12. Security Considerations
the number and status of a device's network interfaces, and
write-able objects which allow an administrator to control the
interfaces and to perform tests on the interfaces.
Unauthorized access to the readable objects is relatively
innocuous. Unauthorized access to the write- able objects
could cause a denial of service, or in combination with other
(e.g., physical) security breaches, could cause unauthorized
connectivity to a device.
15. Author's Address There are a number of management objects defined in this MIB
that have a MAX-ACCESS clause of read-write and/or read-
create. Such objects may be considered sensitive or
vulnerable in some network environments. The support for SET
operations in a non-secure environment without proper
protection can have a negative effect on network operations.
The managed objects in this MIB contain sensitive information
since, collectively, they allow tracing and influencing of
virtual connections in ATM switches or networks and provide
information of their traffic characteristics.
It is thus important to control even GET access to these
objects and possibly to even encrypt the values of these
object when sending them over the network via SNMP. Not all
versions of SNMP provide features for such a secure
environment.
SNMPv1 by itself is not a secure environment. Even if the
network itself is secure (for example by using IPSec), even
then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the
objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically,
the use of the User-based Security Model RFC 2274 [12] and the
View-based Access Control Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the
SNMP entity giving access to an instance of this MIB, is
properly configured to give access to the objects only to
those principals (users) that have legitimate rights to indeed
GET or SET (change/create/delete) them.
13. Author's Address
Kaj Tesink Kaj Tesink
Bellcore Bellcore
331 Newman Springs Road 331 Newman Springs Road
P.O. Box 7020 P.O. Box 7020
Red Bank, NJ 07701-7020 Red Bank, NJ 07701-7020
draft ATM Management Objects October 19, 1998
Phone: (732) 758-5254 Phone: (732) 758-5254
EMail: kaj@cc.bellcore.com EMail: kaj@bellcore.com
draft ATM Management Objects August 15, 1998 draft ATM Management Objects October 19, 1998
16. Full Copyright Statement 14. Intellectual Property
The IETF takes no position regarding the validity or scope of
any intellectual property or other rights that might be
claimed to pertain to the implementation or use of the
technology described in this document or the extent to which
any license under such rights might or might not be available;
neither does it represent that it has made any effort to
identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11.
Copies of claims of rights made available for publication and
any assurances of licenses to be made available, or the result
of an attempt made to obtain a general license or permission
for the use of such proprietary rights by implementors or
users of this specification can be obtained from the IETF
Secretariat.
The IETF invites any interested party to bring to its
attention any copyrights, patents or patent applications, or
other proprietary rights which may cover technology that may
be required to practice this standard. Please address the
information to the IETF Executive Director.
draft ATM Management Objects October 19, 1998
15. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Copyright (C) The Internet Society (1998). All Rights
Reserved. Reserved.
This document and translations of it may be copied and This document and translations of it may be copied and
furnished to others, and derivative works that comment on or furnished to others, and derivative works that comment on or
otherwise explain it or assist in its implementation may be otherwise explain it or assist in its implementation may be
prepared, copied, published and distributed, in whole or in prepared, copied, published and distributed, in whole or in
part, without restriction of any kind, provided that the above part, without restriction of any kind, provided that the above
copyright notice and this paragraph are included on all such copyright notice and this paragraph are included on all such
skipping to change at page 103, line 4 skipping to change at page 103, line 4
not be revoked by the Internet Society or its successors or not be revoked by the Internet Society or its successors or
assigns. assigns.
This document and the information contained herein is provided This document and the information contained herein is provided
on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE." PARTICULAR PURPOSE."
draft ATM Management Objects October 19, 1998
draft ATM Management Objects August 15, 1998
Table of Contents Table of Contents
1 Status of this Memo ................................... 1 1 Status of this Memo ................................... 1
2 Introduction .......................................... 2 2 The SNMP Network Management Framework ................. 2
3 The SNMP Network Management Framework ................. 2 3 ATM Terminology ....................................... 4
4 Object Definitions .................................... 4 3.1 VCL/VPL and VCC/VPC ................................. 4
5 ATM Terminology ....................................... 5 3.2 PVC, SVC and Soft PVC ............................... 6
5.1 VCL/VPL and VCC/VPC ................................. 5 3.3 Traffic Management Parameters ....................... 7
5.2 PVC, SVC and Soft PVC ............................... 7 3.3.1 Traffic Policing and Traffic Shaping Parameters
5.3 Traffic Management Parameters ....................... 8 .................................................... 7
5.3.1 Traffic Policing and Traffic Shaping Parameters 3.3.2 Cell Loss Priority ................................ 8
.................................................... 8 3.3.3 QoS Class ......................................... 8
5.3.2 Cell Loss Priority ................................ 8 3.3.4 Service Category .................................. 8
5.3.3 QoS Class ......................................... 9 3.4 Max Active and Max Current VPI and VCI Bits ......... 8
5.3.4 Service Category .................................. 9 4 Overview .............................................. 10
5.4 Max Active and Max Current VPI and VCI Bits ......... 9 4.1 Background .......................................... 10
6 Overview .............................................. 10 4.2 Structure of the MIB ................................ 10
6.1 Background .......................................... 11 4.3 ATM Interface Configuration Table ................... 11
6.2 Structure of the MIB ................................ 11 4.4 ATM Interface DS3 PLCP and TC Layer Tables .......... 11
6.3 ATM Interface Configuration Table ................... 11 4.5 ATM Virtual Link and Cross-Connect Tables ........... 11
6.4 ATM Interface DS3 PLCP and TC Layer Tables .......... 12 5 Application of MIB II to ATM .......................... 12
6.5 ATM Virtual Link and Cross-Connect Tables ........... 12 5.1 The System Group .................................... 12
7 Application of MIB II to ATM .......................... 13 5.2 The Interface Group ................................. 12
7.1 The System Group .................................... 13 5.2.1 Support of the ATM Cell Layer by ifTable .......... 12
7.2 The Interface Group ................................. 13 6 Support of the AAL3/4 Based Interfaces ................ 14
7.2.1 Support of the ATM Cell Layer by ifTable .......... 13 7 Support of the AAL5 Managed Objects ................... 15
8 Support of the AAL3/4 Based Interfaces ................ 15 7.1 Managing AAL5 in a Switch ........................... 15
9 Support of the AAL5 Managed Objects ................... 16 7.2 Managing AAL5 in a Host ............................. 16
9.1 Managing AAL5 in a Switch ........................... 16 7.3 Support of AAL5 by ifTable .......................... 18
9.2 Managing AAL5 in a Host ............................. 17 7.4 Support of Proprietary Virtual Interface by ifT-
9.3 Support of AAL5 by ifTable .......................... 19 able ............................................... 20
9.4 Support of Proprietary Virtual Interface by ifT- 7.5 AAL5 Connection Performance Statistics Table ........ 21
able ............................................... 21 8 ILMI MIBs and the ATM Managed Objects ................. 21
9.5 AAL5 Connection Performance Statistics Table ........ 22 9 Definitions ........................................... 24
10 ILMI MIBs and the ATM Managed Objects ................ 23 10 Acknowledgments ...................................... 95
11 Definitions .......................................... 26 11 References ........................................... 96
12 Acknowledgments ...................................... 97 12 Security Considerations .............................. 99
13 References ........................................... 98 13 Author's Address ..................................... 99
14 Security Considerations .............................. 101 14 Intellectual Property ................................ 101
15 Author's Address ..................................... 101 15 Full Copyright Statement ............................. 102
16 Full Copyright Statement ............................. 102
 End of changes. 183 change blocks. 
248 lines changed or deleted 307 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/