Specifications

5-123

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 5 AXSM Command Reference

cnfcon

Configure Connection—AXSM, AXSM-E, AXSM-32-T1E1-E, AXSM-XG

Modifies the bandwidth, policing, and routing parameters of an existing endpoint. This command applies

to only an SPVC or SPVP.

Note Use the cnfabr command to configure VSVD-specific parameters for ABR connections on AXSM-E and

AXSM-XG cards. The cnfabr command is not available on AXSM/A and AXSM/B cards.

The command parameters consist of:

• A logical port, VPI, and VCI to identify the connection

• Bandwidth parameters for the local (master) end then the remote (slave) end

• Policing parameters for the connection as a whole

After you specify the mandatory connection identifier, all other parameters are optional.

Note To enable VS/VD, or to modify a connection which has VS/VD enabled, ABR COSB WFQ should be

enabled in port SCT.

Warning

Changing connection parameters will result in a momentary loss of traffic.

Warning

Changing routing parameters will not take effect on the slave endpoint of a DAX connection.

Usage Guidelines

The following sections discuss the application of certain cnfcon parameters.

Note On DAX connections, using cnfcon at the slave end has no effect. For DAX connections, use cnfcon at

the master end only, and the parameters will take effect on the controller as well.

If you modify a point-to-point (P2MP) connection, all parties on that connection are re-routed. The

“Cast-type” field in the dspcon output shows whether the connection is P2P or P2MP.

Traffic Parameters

Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both

the forward and reverse directions. For PCR in the cnfcon command, however, specify lpcr and rpcr at

the master endpoint only (the connection manager ignores PCR entries at the slave end for the cnfcon

command). Be sure that the value entered as “local” on one end is equal to the value entered as “remote”

on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master

endpoint and vice versa when you provision the connection at the other end. If you modify traffic

parameters after creating an SPVC, you just modify them at either the master endpoint or the slave

endpoint.