Request for Comments: 3606 Pedestal Networks
Category: Standards Track M. Noto
Cisco Systems
A. Smith
Consultant
E. Spiegel
Cisco Systems
K. Tesink
Telcordia Technologies
November 2003
Definitions of Supplemental Managed Objects for ATM Interface
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This memo defines objects used for managing ATM-based interfaces,
devices, and services, in addition to those defined in RFC 2515, the
ATM-MIB, to provide additional support for the management of ATM
Switched Virtual Connections (SVCs) and ATM Permanent Virtual
Connections (PVCs).
Table of Contents
1. The Internet-Standard Management Framework. . . . . . . . . 3
2. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Background. . . . . . . . . . . . . . . . . . . . . . 3
2.2. Important Definitions . . . . . . . . . . . . . . . . 4
3. Conventions used in the MIB . . . . . . . . . . . . . . . . 6
3.1. Structure . . . . . . . . . . . . . . . . . . . . . . 6
3.1.1. ATM SVC VP Cross-Connect Table. . . . . . . . 6
3.1.2. ATM SVC VC Cross-Connect Table. . . . . . . . 7
3.1.3. ATM Interface Signalling Statistics Table . . 8
3.1.4. ATM Signalling Capability Support . . . . . . 9
3.1.5. Signalling Descriptor Parameter Table . . . . 10
3.1.6. ATM Interface Registered Address Table. . . . 10
3.1.7. ATM VPI/VCI to Address Mapping Table. . . . . 11
3.1.8. ATM Address to VPI/VCI Mapping Table. . . . . 11
3.1.9. ATM VPL Statistics Table. . . . . . . . . . . 11
3.1.10. ATM VPL Logical Port Table. . . . . . . . . . 12
3.1.11. ATM VCL Statistics Table. . . . . . . . . . . 15
3.1.12. ATM VC General Information Table. . . . . . . 15
3.1.13. ATM Interface Configuration Extension Table . 16
3.1.14. ATM ILMI Service Registry Table . . . . . . . 17
3.1.15. ILMI Network Prefix Table . . . . . . . . . . 19
3.1.16. ATM Switch Address Table. . . . . . . . . . . 19
3.1.17. AAL5 per-VCC Statistics Table . . . . . . . . 19
3.1.18. ATM VP Cross-Connect Extension Table. . . . . 20
3.1.19. ATM VC Cross-Connect Extension Table. . . . . 20
3.1.20. Currently Failing PVPL Table. . . . . . . . . 20
3.1.21. Currently Failing PVCL Table. . . . . . . . . 20
3.1.22. Leaf Initiated Join Counter support . . . . . 20
3.2. Network and User Addresses. . . . . . . . . . . . . . 20
3.3. Configuration of VPLs, VCLs, and Cross-Connects . . . 20
3.4. ATM-related Trap Support. . . . . . . . . . . . . . . 20
4. Conformance and Compliance. . . . . . . . . . . . . . . . . 21
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 21
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 89
7. References. . . . . . . . . . . . . . . . . . . . . . . . . 89
7.1. Normative References. . . . . . . . . . . . . . . . . 89
7.2. Informative References. . . . . . . . . . . . . . . . 90
8. Security Considerations . . . . . . . . . . . . . . . . . . 90
9. Intellectual Property Statement . . . . . . . . . . . . . . 92
10. Authors’ Addresses. . . . . . . . . . . . . . . . . . . . . 93
11. Full Copyright Statement. . . . . . . . . . . . . . . . . . 94
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
2. Overview
The purpose of this memo is to provide additional capabilities, not
found in the ATM-MIB [RFC2515], which are needed to manage ATM
interfaces. This memo addresses the following areas:
- ATM Switch Support
- ATM Service Support
- ATM Host Support
In addition, this memo also provides ATM trap support.
2.1. Background
In addition to the MIB module defined in this memo, other MIB modules
are necessary to manage ATM interfaces, links and cross-connects.
Examples include MIB II for general system and interface management
([RFC2863]), the DS3 ([RFC2496]) or SONET MIBs ([RFC3592]) for
management of SONET and DS3 physical interfaces, and, as appropriate,
MIB modules for applications that make use of ATM, such as SMDS
[RFC1694] and LAN Emulation [ATM Forum LANE]. These MIB modules are
outside the scope of this specification.
This MIB module also requires the use of the ATM-MIB module defined
in [RFC2515] and ATM-specific textual conventions defined in
[RFC2514].
ATM Endpoint applications such as ATM LAN Emulation or Classical IP-
over-ATM Clients and Servers use ATM to establish SVC/PVC connections
for exchanging control and data information. The agents of these ATM
applications must provide the network manager with information on the
SVC/PVCs in use and which applications are using them. The
information can be made generic so as to apply to all ATM
applications. This memo defines extensions to the ATM-MIB [RFC2515]
in order to support this.
The current specification of this supplemental ATM2-MIB is based on
SNMPv2 SMI.
2.2. Important Definitions
The following terms are defined here and used throughout this MIB:
- Virtual Path Link (VPL)
- Virtual Path Connection (VPC)
- Virtual Path Segment (VP Segment)
- Virtual Channel Link (VCL)
- Virtual Channel Connection (VCC)
- Virtual Channel Segment (VC Segment).
The figures on the next page show how these terms apply in typical
ATM network topologies. Additional terms relevant to this MIB are
defined and illustrated in the ATM Terminology section 3 of
[RFC2515].
_____ _______ _______ _______ _____
| |____| |____| |____| |____| |
|Host1| |SwitchA| |SwitchB| |SwitchC| |Host2|
| |____| |____| |____| |____| |
|_____| |_______| |_______| |_______| |_____|
|<-->| |<-->|
Virtual Path Link Virtual Path Link
|<----------------------------------------->|
Virtual Path Connection
(between Host1 and Host2)
|<--------------->|
Virtual Path Segment
(between SwitchA and SwitchC)
Figure 1: Examples of Virtual Path Links, Virtual Path
Connection, and Virtual Path Segment
_____ _______ _______ _______ _____
| |____| |____| |____| |____| |
|Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2|
| |____| |____| |____| |____| |
|_____| |_______| |_______| |_______| |_____|
|<-->| |<-->|
Virtual Channel Link Virtual Channel Link
|<----------------------------------------->|
Virtual Channel Connection
(between Host1 and Host2)
|<--------------->|
Virtual Channel Segment
(between SwitchA and SwitchC)
Figure 2: Examples of Virtual Channel Links, Virtual
Channel Connection, and Virtual Channel Segment
3. Conventions used in the MIB
3.1. Structure
The managed ATM objects are arranged as follows:
Table Host Switch Service
_____________________________________________________
atmSvcVcCrossConnectTable | | Y | Y |
atmSvcVpCrossConnectTable | | Y | Y |
atmSigStatTable | Y | Y | Y |
atmSigSupportTable | | Y | Y |
atmSigDescrParamTable | Y | | |
atmIfRegisteredAddrTable | | Y | Y |
atmVclAddrTable | Y | | |
atmAddrVclTable | Y | | |
atmVplStatTable | Y | Y | Y |
atmVplLogicalPortTable | Y | Y | Y |
atmVclStatTable | Y | Y | Y |
atmAal5VclStatTable | Y | | |
atmVclGenTable | Y | | |
atmInterfaceExtTable | Y | Y | Y |
atmIlmiSrvcRegTable | | Y | Y |
atmIlmiNetworkPrefixTable | | Y | Y |
atmSwitchAddressTable | | Y | |
atmVpCrossConnectXTable | | | Y |
atmVcCrossConnectXTable | | | Y |
atmCurrentlyFailingPVplTable | Y | Y | Y |
atmCurrentlyFailingPVclTable | Y | Y | Y |
Table 1: MIB structure
3.1.1. ATM SVC VP Cross-Connect Table
This table provides the SVC VP Cross-Connect (SVPC) information. The
equivalent PVC VP Cross-Connect table is defined in [RFC2515]. This
table also includes cross-connect information for Soft PVPs.
This table contains configuration and state information of all SVC VP
point-to-point, point-to-multipoint, or multipoint-to-multipoint VP
cross-connects.
This table has read-only access and can be used to monitor the
cross-connects which connect the VPLs together in an ATM switch or
network. The atmSvcVpCrossConnectIndex is used to associate the
related SVC VPLs that are cross-connected together. The
atmSvcVpCrossConnectRowStatus object has read-write access to allow
for tear-down.
The ATM SVC VP Cross-Connect Table models each bi-directional
Switched Virtual Circuit (SVC) VP cross-connect as a set of entries
in the atmSvcVpCrossConnectTable. A point-to-point VPC cross-connect
is modeled as one entry; a point-to-multipoint (N leafs) VPC cross-
connect as N entries in this table; and a multipoint-to-multipoint (N
parties) VPC cross-connect as N(N-1)/2 entries in this table. In the
latter cases, all the N (or N(N-1)/2) entries are associated with a
single VPC cross-connect by having the same value of
atmSvcVpCrossConnectIndex.
_________________________________________
| |
Low | ATM Switch or Network | High
port| | port
_____|>> from low to high VPC traffic flow >>|______
|<< from high to low VPC traffic flow <<|
|_______________________________________|
Figure 3: VPC Cross-Connect Model
The terms low and high are chosen to represent numerical ordering of
the two interfaces associated with a VPC cross-connect. That is, the
ATM interface with the lower value of ifIndex is termed ’low’, while
the other ATM interface associated with the VPC cross-connect is
termed ’high’.
3.1.2. ATM SVC VC Cross-Connect Table
This table provides the SVC Cross-Connect (SVCC) information. The
equivalent PVC VC Cross-Connect table is defined in [RFC2515]. This
table also includes cross-connect information for Soft PVCs.
This table is used to model a bi-directional point-to-point, point-
to-multipoint or multipoint-to-multipoint SVC VC cross-connect.
This table has read-only access and is used to monitor the cross-
connects which connect the VCLs together in an ATM switch or network
that belong to a VC connection. The atmSvcVcCrossConnectIndex is
used to associate the related SVC VCLs that are cross-connected
together. The atmSvcVcCrossConnectRowStatus object has read-write
access to allow for tear-down.
The ATM SVC VC Cross-Connect Table models each bi-directional
Switched Virtual Circuit (SVC) VC cross-connect as a set of entries
in the atmSvcVcCrossConnectTable. A point-to-point VC cross-connect
is modeled as one entry; a point-to-multipoint (N leafs) VC cross-
connect as N entries in this table; and a multipoint-to-multipoint (N
parties) VPC cross-connect as N(N-1)/2 entries in this table. In the
latter cases, all the N (or N(N-1)/2) entries are associated with a
single VPC cross-connect by having the same value of
atmSvcVcCrossConnectIndex.
______________________________________
| |
Low | ATM Switch or Network | High
port| | port
_____|>> from low to high VC traffic flow >>|______
|<< from high to low VC traffic flow <<|
|______________________________________|
Figure 4: VC Cross-Connect Model
The terms low and high are chosen to represent numerical ordering of
the two interfaces associated with a VPC cross-connect. That is, the
ATM interface with the lower value of ifIndex is termed ’low’, while
the other ATM interface associated with the VPC cross-connect is
termed ’high’.
3.1.3. ATM Interface Signalling Statistics Table
This table provides statistical information of the signalling entity.
A signalling entity can be deployed over an ATM interface as defined
in the atmInterfaceConfTable [RFC2515], a logical ATM interface
defined in section 5.1.10.1 in this document, or a proprietary
virtual interface as described in the atmInterfaceExtTable. To
monitor the signalling entity, a few counters are provided. They are
defined as:
atmSigSSCOPConEvents
atmSigSSCOPErrdPdus
atmSigDetectSetupAttempts
atmSigEmitSetupAttempts
atmSigDetectUnavailRoutes
atmSigEmitUnavailRoutes
atmSigDetectUnavailResrcs
atmSigEmitUnavailResrcs
atmSigDetectCldPtyEvents
atmSigEmitCldPtyEvents
atmSigDetectMsgErrors
atmSigEmitMsgErrors
atmSigDetectClgPtyEvents
atmSigEmitClgPtyEvents
atmSigDetectTimerExpireds
atmSigEmitTimerExpireds
atmSigDetectRestarts
atmSigEmitRestarts
atmSigInEstabls
atmSigOutEstabls
3.1.4. ATM Signalling Capability Support
A number of Information Elements may or may not be supported by ATM
switches or ATM Services. Hence, for trouble isolation it is
important to keep track which particular Information Elements are
supported. The corresponding group of objects must be supported by
switches or services supporting SVCs, and indicate whether the
following Information Elements are enabled/disabled:
1) Calling party number
2) Calling party subaddress
3) Called party subaddress
4) Broadband high layer information
5) Broadband low layer information
6) Broadband Repeat Indicator
7) AAL parameters
The last parameter, Preferred Carrier Pre-Subscription, identifies
the carrier to which intercarrier calls originated from this
interface are routed when transit network selection information is
not provided by the calling party.
3.1.5. Signalling Descriptor Parameter Table
This table extends the ATM VCL table of the ATM-MIB [RFC2515] to
include all other necessary signalling information as specified in
the ATM Forum UNI Specifications [ATM Forum 3.0] and [ATM Forum UNI
3.1]. A user can create an entry with all signalling parameters and
later use that entry to specify the signalling characteristics of
SVCs.
Some of the signalling parameters, such as the AAL5 parameters
information element, are reflected in the VCL and VPL tables, and
this table only contains the remaining AAL5 parameters.
Signalling attributes can be grouped into following categories:
1) ATM Adaptation Layer Parameters
Information in this group is captured in the ATM Signalling
Descriptor Parameter Table defined in this memo. Please refer to
section 5.4.5.5 of [ATM Forum 3.0] and [ATM Forum UNI 3.1].
2) Broadband High Layer Information
Information in this group is captured by the ATM Signalling
Descriptor Parameter Table defined in this memo. Please refer to
section 5.4.5.8 of [ATM Forum 3.0] and [ATM Forum UNI 3.1].
3) Broadband Low Layer Information
Information in this group is captured by the ATM Signalling
Descriptor Parameter Table defined in this memo. Please refer to
section 5.4.5.9 of [ATM Forum 3.0] and [ATM Forum UNI 3.1].
3.1.6. ATM Interface Registered Address Table
This table contains a list of ATM addresses that can be used for
calls to and from a given interface by a switch or service. The ATM
addresses are either registered by the endsystem via ILMI or
statically configured. This table does not expose PNNI reachability
information. This table only applies to switches and network
services. See also Section 5.2.
3.1.7. ATM VPI/VCI to Address Mapping Table
In the atmVclAddrTable, the object atmVclAddrAddr can either be an
ATM Local Address or an ATM Remote Address which represent the two
endpoint addresses of a VCL. ATM Local Address identifies the local
endpoint of the VCL represented by this agent. The ATM Remote
address represents the address of the ATM application at the other
end of the VCL.
3.1.8. ATM Address to VPI/VCI Mapping Table
This table provides an alternative way to retrieve the atmVclTable.
This table can be used to retrieve the indexing to the atmVclTable by
an ATM address.
3.1.9. ATM VPL Statistics Table
The atmVplStatTable includes per-VPL cell counters. The VPL cell
counters count the valid ATM cells. The valid ATM cells include the
user and OAM cells but exclude the physical layer (e.g., idle cells)
and unassigned cells. Cells coming into an ATM managed system are
counted differently with the high Cell Loss Priority (CLP=0) or low
Cell Loss Priority (CLP=1). The cells are tagged, passed or
discarded depending on the incoming CLP value and the policed cell
rate by the "traffic policing" entity in the ATM managed system.
Refer to [ATM Forum 3.0] and [ATM Forum UNI 3.1] for a description of
the traffic policing.
In the switch where the traffic policing is not supported, cells are
passed or discarded depending on the bandwidth and buffering capacity
of the switching fabric. The Output Tagged Cells counter, in this
case, is always zero.
_______________
| ATM Managed |
Input | System | Output
CLP=0 cells| | CLP=0 cells
---------->| |----------->
CLP=1 cells| (traffic | CLP=1 cells
---------->| policing |----------->
| entity) | Tagged cells (CLP=1)
|_____________|----------->