Cisco Systems OL-7396-01 Configuring Nondefault Well-Known PVCs

7-74
ATM Switch Router Software Configuration Guide
OL-7396-01
Chapter7 Configuring Virtual Connections
Configuring Nondefault Well-Known PVCs
Configuring Nondefault Well-Known PVCs
Normally the default well-known VCs are automatically created with default virtual channel identifiers
(VCIs). However, for the unusual instances where the ATM switch router interfaces with nonstandard
equipment, you can configure nondefault well-known VCI values on a per-interface basis.
For overview information about the well-known PVCs, refer to the Guide to ATM Technology.
Table 7 -2 lists the default well-known VCs and their default configuration.
Caution Do not change the well-known channels to use a VC where the remote end is sending AAL5 messages
not intended for the well-known VC. For example, do not swap VC values bet ween two types of
well-known VCs.
When you configure well-known VCs on physical interfaces using the CBR service category, the VC
scheduling on the external interface is the same as the CBR VC configuration. This means that the VCs
are allocated the bandwidth specified and are limited to that same bandwidth (shaped).
Note The connection from an external interface to the route processor is never shaped.
Overview of Nondefault PVC Configuration
Following is an overview of the steps needed to configure nondefault well-known VCs:
Step1 Enable manual well-known VC configuration.
Step2 Delete any existing automatically created well-known VCs.
Step3 Configure the individual encapsulation type as follows:
•Signalling (QSAAL)
•ILMI
•PNNI
•Tag switching
Step4 Copy the running-configuration file to the startup-configuration file.
Table7-2 Well-Known Virtual Channels
Channel Type Virtual Path Identifier Virtual Channel Identifier
Signalling 0 5
ILMI 0 16
PNNI 0 18
Tag switching 0 32