Cisco Systems Cisco MGX 8850 addcon

7-6

Cisco MGX 8850 Routing Switch Command Reference

Release 2.0, Part Number 78-10467-04 Rev C0, October 2001

Chapter7 SPVC and SVC Commands

addcon

addcon

Add Connection

Adds a logical connection as an SPV C on a service module. The switc h assigns a 20 octet NSAP address

to the slave endpoint, which is sent back to the master and uniquely identifies the endpoint on the

network. An AXSM front card can support a maximum of 64K SPVCs. This command does not apply

to SVCs.

Before you can add an SPVC, the following tasks must have been completed:

1. The switch must have a network controller (see addcontroller description).

2. A physical line must be active. Use the upln command or the CiscoView application.

3. At least one logical port mus t exist o n the active physical line. Use the addpo rt command or the

CiscoView application to create the port. If necessary, modify the port through cnfport.)

4. At least one resource partition must exist on the logical port. Use the addrscprtn (or addpart,)

command or the CiscoView application . T he resource partition should b e a ss oc iat ed w it h th e

controller you add in step 1.

Adding a connection requires you first to provision a slave endpoint. Subsequently, you again execute

addcon to provision a master endpoint. The master endpoint of the connection initiates the routing of

the call and can be viewed as the “cal ling” party. The slave endpoint is the called en dpo in t. Th e

following are characteristics o f th is master-slave arrangement:

•When you add a slave endpoint, the system returns a slave endpoint identifier. You subsequently

need to provide this slave endpoint id en ti fier w h en s p eci f yi ng t he master endpoint.

•When you add the master endpoint, you must provide the slave endpoint identifier. (A copy and

paste operation is probably more convenient than writing down the slave endpoint identifier.) After

you finish adding the master endpoint, the switch starts routing the connection.

To modify the bandwidth p ar ameters or configure usage parameter con t r o l ( U P C) , us e cnfcon for all

service types. In addition, ABR connections require more configurable parameters for implementing

closed loop control. Use cnfabr to configure the ABR parameters. (Note, however, that ABR VSVD is

not supported in the current release.)

Usage Guidelines

The following sections deta il th e a pplication of certain addcon pa ra m e t e r s .

Traffic para meters such as PCR, SCR, MBS are entered at both the master and slave endpoints fo r both

the forward and reverse directions. B e sure that the value entered as “local” on one en d i s eq u al to th e

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 vers a when you provision the connection at the other end. If

you modify traffic parameters after creating an SPVC, you just mod ify them at either the master end point

or the slave endpoint.