Specifications

3-55
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 3 Provisioning ATM Services
General AXSM Configuration Procedures
Cisco MGX PXM1E-based and PXM45-based switches support two types of SPVCs/SPVPs:
• Single-ended SPVCs
• Double-ended SPVCs
Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave
endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After
configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature
to work correctly, the destination endpoint must support single-ended SPVCs. Single-ended SPVCs are
non-persistent. Non-persistent SPVCs will attempt to route on the specified path first. If the configured
path is unavailable, the non-persistent SPVC will attempt to route over another available path.
Note The AXSM supports only the origination of single-ended SPVCs. This means that you can configure
master endpoints for single-ended SPVCs that terminate on other card types, such as the FRSM12. If
both SPVC endpoints must terminate on AXSM cards, you must create a double-ended SPVC.
Double-ended SPVCs and SPVPs require separate configuration of the master and slave endpoints. The
slave endpoint must be configured first because this step generates a slave address that must be entered
during master endpoint configuration Double-ended SPVCs are persistent, because they will follow only
the specified path. If that path is unavailable, the persistent SPVC/SPVP will not route.
The following sections describe how to configure slave and master SPVC and SPVP connections.
Tip The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI
0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI.
Configuring the Slave Side of SPVCs and SPVPs
To configure the slave side of an SPVC or SPVP, use the following procedure.
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Define the slave side of the SPVC or SPVP by entering the following command:
M8950_DC.5.AXSM.a > addcon < ifNum > < vpi > < vci > < serviceType > < mastership >
[-slave
atmAddr . vpi . vci ] [-lpcr < cellrate >] [-rpcr < cellrate >] [-lscr < cellrate >]
[-rscr <
cellrate >] [-lmbs < cells >] [-rmbs < cells >] [-lcdv < time >] [-rcdv < time >]
[-lctd <
time >] [-rctd < time >] [-lmcr < cellrate >] [-rmcr < cellrate >] [-cdvt < time >]
[-cc <1|0>] [-stat <1|0>] [-frame <1|0>] [-mc <
maxCost >][-lputil <local>]
[-rputil <remote>] [-rtngprio <routingPriority>]
Caution After you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections
have been deleted. The procedure for changing the SPVC prefix is described in the Cisco MGX
8800/8900 Series Configuration Guide, Release 5.2.
Step 3 Enter the dspcon <portid> <vpi> <vci> command to verify that the SPVC or SPVP was associated with
the preferred route.
Tip The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. To override the default
values for any option, enter the option with a new value.