Cisco ATM Services (AUSM/MPSM-8-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2 - Provisioning and Managing PVCs [Cisco MGX 8800 Series Switches]

Table Of Contents

Provisioning PVCs (PXM1) on AUSM and MPSM Cards

Preparing for Provisioning

Quickstart Provisioning Procedures

AUSM and MPSM Feeder Connection Configuration Quickstarts

Three Segment Feeder Connection Configuration Quickstart

Two Segment Feeder Connection Configuration Quickstart

AUSM and MPSM Local Connection Configuration Quickstarts

Service Module to Service Module Local Connection Quickstart

Service Module to PXM1 Local Connection Quickstart

General AUSM and MPSM PVC Provisioning Procedures

Configuring PVCs on AUSM and MPSM Cards

Configuring Feeder Connections on AUSM and MPSM Cards

Configuring Local Connections on AUSM and MPSM Cards

Configuring Service Module to Service Module Local Connections

Configuring Service Module to PXM1 Local Connections

Provisioning PVCs (PXM1) on AUSM and MPSM Cards

This chapter describes how to provision ATM Permanent Virtual Circuits (PVCs) on the physical ports of the AUSM-8T1/B, AUSM-8E1/B, MPSM-8T1-ATM, MPSM-8E1-ATM cards using the command-line interface (CLI).

The following sections describe how to provision ATM PVCs on AUSM and MPSM cards:

•Preparing for Provisioning

•Quickstart Provisioning Procedures

•General AUSM and MPSM PVC Provisioning Procedures

Note The easiest way to add connections is by using the Cisco WAN Manager (CWM) application. For full details on how to set up a connection with CWM, refer to the Cisco WAN Manager User's Guide, Release 15.1.

This chapter explains how to provision the PVC connection types described in Table 4-1.

Table 4-1 PVC Connection Types Applicable to AUSM and MPSM Cards

AUSM and MPSM PVC Connection Type

Description

Three-segment Feeder Connection

A Permanent Virtual Circuit (PVC) is a static connection between two ATM ports. A three-segment feeder connection establishes a multi segment PVC connection in a tiered ATM network comprised of two Cisco MGX PXM1 feeder switches and Cisco BPX 8600, Cisco MGX 8850 (PXM45), or Cisco MGX 8950 core switches. Each feeder hosts one segment of the connection, and the core switches host one segment of the connection. Feeder connections provisioned on the PXM1 platform are always master connections.

Two-segment Feeder Connection

A two-segment feeder connection establishes a multi segment PVC connection in a tiered ATM network between one Cisco MGX PXM1 feeder switch and Cisco BPX 8600, Cisco MGX 8850 (PXM45), or Cisco MGX 8950 core switches. The feeder hosts one segment of the connection, and the core switches host one segment of the connection. Feeder connections provisioned on the PXM1 platform are always master connections.

Service Module to Service Module Local Connection (DAX)

A local connection is a PVC established between two interfaces on the same Cisco MGX PXM1 switch. When the switch is in either Feeder mode or Standalone mode, a service module to service module local connection establishes a PVC between two user ports located either on the same service module or on different service modules. Local connections provisioned on the PXM1 platform are made up of master and slave end-points.

Service Module to PXM1 Local Connection

When the Cisco MGX PXM1 switch is in Standalone mode, a service module to PXM1 local connection establishes a PVC between a service module user port and a PXM1 broadband user port. Local connections provisioned on the PXM1 platform are made up of master and slave end-points.

To eliminate redundancy and help experienced users complete configuration tasks quickly and efficiently, this chapter provides configuration quickstart procedures.

The first time you configure a connection type, use the applicable quickstart procedure to get an overview of the tasks to be performed. Then, for more detailed instructions, consult the appropriate section(s) elsewhere in the document that are called out in the quickstart procedure. As you gain experience in configuring AUSM card connections, referring to a quickstart procedure may suffice for performing a particular configuration task.

Tip You can get information about most CLI commands by entering the command without parameters. Ordinarily, experienced users can configure AUSM card connections using just the quickstart procedures and the online help facilities.

Note For a detailed description of the commands used in this chapter, refer to Chapter 6, "AUSM and MPSM Command Reference."

Preparing for Provisioning

Before you can begin provisioning ATM PVCs on AUSM and MPSM cards, you need to bring up the physical lines and add logical ports on the service modules. For instructions on bringing up physical lines and adding logical ports on AUSM and MPSM cards, see "Preparing AUSM and MPSM Lines and Ports for Communications."

Quickstart Provisioning Procedures

These quickstart tasks contain abbreviated procedures for provisioning PVCs on AUSM and MPSM cards installed in Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8850 (PXM1) Release 1.3.10 switches:

•AUSM and MPSM Feeder Connection Configuration Quickstarts

•AUSM and MPSM Local Connection Configuration Quickstarts

These procedures provide a high level overview and serve as a procedural reminder for users already experienced in configuring MGX switches.

AUSM and MPSM Feeder Connection Configuration Quickstarts

The following quickstart procedures describe how to provision three-segment and two-segment feeder connections on AUSM and MPSM cards:

•Three Segment Feeder Connection Configuration Quickstart

•Two Segment Feeder Connection Configuration Quickstart

Three Segment Feeder Connection Configuration Quickstart

To configure a three-segment feeder connection in a tiered network comprised of two Cisco MGX feeder switches and Cisco BPX 8600, Cisco MGX 8850 PXM45, or Cisco MGX 8950 core switches, perform the following steps:

Command

Purpose

Step 1

username

<password>

Start a configuration session.

Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

See the "AUSM and MPSM Line Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Bring up the physical lines at each end of the PVC you are creating.

Step 3

See the "ATM Port Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Configure the ATM ports at each end of the PVC you are creating.

Step 4

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Configure the master side of the feeder connection from the AUSM/MPSM user port to the PXM1 feeder trunk at each end of the PVC you are creating.

Tip Only the master side of the connection is required for feeder segment connections on Cisco MGX PXM1 platforms.

See the "Configuring Feeder Connections on AUSM and MPSM Cards" section that appears later in this chapter.

Step 5

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Add a routing connection through the ATM core network. The ATM core network may be comprised of Cisco BPX 8600, Cisco MGX 8850 (PXM45), and MGX 8950 switches.

Tip Be sure to match the VPI and VCI values in the ATM core network connections with the values used when adding the Cisco MGX feeder connection segments.

Tip Both slave and master connections are required when adding routing connections between AXSMs.

Note Refer the appropriate switch software configuration guide(s) to configure the switches in the ATM core network. See the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 and the Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30.

Two Segment Feeder Connection Configuration Quickstart

To configure a two-segment feeder connection in a tiered network between one Cisco MGX feeder switch and Cisco BPX 8600, Cisco MGX 8850 (PXM45), or Cisco MGX 8950 core switches, perform the following steps:

Command

Purpose

Step 1

username

<password>

Start a configuration session.

Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

See the "AUSM and MPSM Line Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Bring up the physical line at the AUSM/MPSM card end of the PVC you are creating.

Step 3

See the "ATM Port Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Configure the ATM port at the AUSM/MPSM end of the PVC you are creating.

Step 4

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Configure the master side of the feeder connection from the service module user port to the PXM1 feeder trunk at the AUSM/MPSM card end of the PVC you are creating.

Tip Only the master side of the connection is required for feeder segment connections on the Cisco MGX PXM1 platforms.

See the "Configuring Feeder Connections on AUSM and MPSM Cards" section that appears later in this chapter.

Step 5

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Add a routing connection through the ATM core network. The ATM core network may be comprised of Cisco BPX 8600, Cisco MGX 8850 (PXM45), and MGX 8950 switches.

Tip Be sure to match the VPI and VCI values in the ATM core network connections with the values used when adding the Cisco MGX feeder connection segments.

Tip Both slave and master connections are required when adding routing connections between AXSMs.

Note Refer the appropriate switch software configuration guide(s) to configure the switches in the ATM core network. See the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 and the Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30.

AUSM and MPSM Local Connection Configuration Quickstarts

The following quickstart procedures describe how to provision local connections on AUSM and MPSM cards:

•Service Module to Service Module Local Connection Quickstart

•Service Module to PXM1 Local Connection Quickstart

Service Module to Service Module Local Connection Quickstart

To configure a local connection (DAX) on a Cisco MGX Feeder or Standalone mode switch between two service module user ports on the same card or on different cards, perform the following steps:

Command

Purpose

Step 1

username

<password>

Start a configuration session.

Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

See the "AUSM and MPSM Line Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Bring up the physical lines at each end of the PVC you are creating.

Step 3

See the "ATM Port Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Configure the ATM ports at each end of the PVC you are creating.

Step 4

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Configure the slave side of the PVC.

Note The slave side of the connection must be added before the master side of a local connection.

See the "Configuring Service Module to Service Module Local Connections" section that appears later in this chapter.

Step 5

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>
cnfcon <options>

Configure the master side of the PVC.

See the "Configuring Service Module to Service Module Local Connections" section that appears later in this chapter.

Service Module to PXM1 Local Connection Quickstart

To configure a local connection on a Cisco MGX Standalone mode switch between a service module user port and a PXM1 broadband user port, perform the following steps:

Command

Purpose

Step 1

username

<password>

Start a configuration session.

Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.

Step 2

Refer to the appropriate switch software configuration guide for instructions on bringing up the physical line at the PXM1 card end of the PVC you are creating.

Bring up the physical line at the PXM1 card end of the PVC you are creating.

Tip Be sure to configure the switch as a standalone routing node with the PXM1 cnfswfunc command before bringing up the physical line on the PXM1.

Tip After bringing up the physical line on the PXM1, use the PXM1 cnfatmln command to configure the cell header type to UNI.

Note See the Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on bringing up physical lines on PXM1 cards installed in a Cisco MGX 8230 switch.
See the Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on bringing up physical lines on PXM1 cards installed in a Cisco MGX 8250 switch.
See the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on bringing up physical lines on PXM1 cards installed in a Cisco MGX 8850 switch.

Step 3

Refer to the appropriate switch software configuration guide for instructions on configuring logical ports on PXM1 cards.

Configure the logical port at the PXM1 card end of the PVC you are creating.

Note See the Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on configuring logical ports on PXM1 cards installed in a Cisco MGX 8230 switch.
See the Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on configuring logical ports on PXM1 cards installed in a Cisco MGX 8250 switch.
See the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 for instructions on configuring logical ports on PXM1 cards installed in a Cisco MGX 8850 switch.

Step 4

See the "AUSM and MPSM Line Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Bring up the physical line at the AUSM/MPSM card end of the PVC you are creating.

Step 5

See the "ATM Port Configuration Quickstart" section that appears in "Preparing AUSM and MPSM Lines and Ports for Communications."

Configure the ATM port at the AUSM/MPSM end of the PVC you are creating.

Step 6

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Configure the slave side of the PVC.

Note The slave side of the connection must be added before the master side of a local connection.

See the "Configuring Service Module to PXM1 Local Connections" section that appears later in this chapter.

Step 7

addcon <options>

Related commands:
dspcons
dspcon <Port> <VPI> <VCI>

or

dspcon <Port.VPI.VCI>

cnfcon <options>

Configure the master side of the PVC.

See the "Configuring Service Module to PXM1 Local Connections" section that appears later in this chapter.

General AUSM and MPSM PVC Provisioning Procedures

The following sections provide procedures for configuring AUSM and MPSM card communications:

•"Configuring PVCs on AUSM and MPSM Cards"

•"Configuring Feeder Connections on AUSM and MPSM Cards"

•"Configuring Local Connections on AUSM and MPSM Cards"

Configuring PVCs on AUSM and MPSM Cards

A Permanent Virtual Circuit (PVC) is a static connection that does not require call setup and are built between two ports on an ATM switch or between two ports on separate switches. PVCs are full-time connections that use a predefined circuit path that fails altogether if that path is interrupted for any reason. Once a PVC is established, the connection remains in place until it is manually removed by network management action. The network resources that have been allocated to the PVC remain dedicated to the PVC for as long as the PVC remains provisioned.

Each PVC has two endpoints. The master endpoint is responsible for routing functions. The slave endpoint is responsible for responding to requests from the master during connection setup. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration. Both endpoints are configured on the switch or switches to which the CPE connects.

Provisioning PVCs requires careful planning prior to the actual configuration of the PVC. Any Quality of Service (QoS) or traffic contract parameters that differ from the switch defaults need to be defined on a per-connection basis.

On PXM1 platforms, a PVC may originate and terminate on the same service module or on different service modules within the same switch (local switching). It may also terminate on the ATM feeder trunk (broadband port switching) for a PVC that is part of a multi segment network connection.

You can create two types of PVC connections on PXM1 platforms:

•Feeder segment connections

•Local connections.

A feeder segment connection is one that originates on a service module and terminates on the PXM1 feeder trunk attached to an ATM core network. A local connection is one that originates on a user port and terminates on another user port. How each type of PVC is provisioned is dependent upon the configured mode the PXM1 platform (feeder mode or standalone mode) and the terminating port type (feeder trunk or user port).

The switching and PVC connection types supported by AUSM and MPSM cards on the PXM1 platform are described in Table 4-2.

Table 4-2 AUSM and MPSM Switching and Connection Types on the PXM1 Platform

Switching Type

PXM1 Feeder Mode

PXM1 Standalone Mode

Local Switching (DAX)

(SM to SM user ports)

Local Connection¹

Local Connection1

Broadband Port Switching

(PXM Broadband ports to SM user ports²)

Feeder Segment Connection³

(PXM Broadband port configured as Feeder Trunk)

Local Connection1

(PXM Broadband port configured as user port)

¹Local Connections originate from a user port and terminate on another user port on the same switch. User ports may be service module ports or PXM broadband ports. Local Connections consist of Slave and Master connections.

²Broadband Port Switching is also supported between two broadband ports.

³Feeder Segment Connections are always Master connections.

In feeder mode, the PXM1 platform interfaces as a shelf with an ATM core network that may be comprised of Cisco BPX 8600, Cisco MGX 8850 (PXM45), or Cisco MGX 8950 core switches.

To add an end-to-end connection from a local feeder to a remote feeder, a three-segment feeder connection is provisioned. A feeder segment connection from the service module to the PXM1 feeder trunk on the local feeder would be segment 1, a routed connection in the ATM core network would be segment 2, and another feeder segment connection from the service module to the PXM1 feeder trunk on the remote feeder would be segment 3.

To add an end-to-end connection from a local feeder to a routing node, a two-segment feeder connection is provisioned. A feeder segment connection from the service module to the PXM1 feeder trunk on the local feeder would be segment 1, and a routed connection in the ATM core network from the trunk card to the destination routing node's user port would be segment 2.

In standalone mode, the PXM1 platform interfaces with a third party ATM network.

To add an end-to-end connection in a standalone switch, a local connection (DAX) is provisioned between one service module user port and another service module user port on the same switch, or a local connection is provisioned from a service module user port to the PXM1 broadband user port. From that point a connection in the third party network is provisioned to a terminating device.

Local connections (DAX) from one service module user port to another service module user port are also provisioned on PXM1 platforms configured as feeders.

Configuring Feeder Connections on AUSM and MPSM Cards

To configure the feeder segment portion of a three-segment or two-segment feeder connection from an AUSM or MPSM user port to a PXM1 feeder trunk, perform the following steps:

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Enter the addcon command as follows to define a feeder segment connection from a service module user port to the PXM1 feeder trunk.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon <port> <vpi> <vci> <conn_type> <service_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] 
Table 4-3 lists and describes the parameters for the addcon command on AUSM and MSPM cards.

Table 4-3 Parameters for the addcon Command on the AUSM and MPSM

Parameter

Description

port

Enter the port number to which you will add the connection. To display a list of configured ports, enter the dspports command. The port number is found in the Port column in the format Slot.Port. The port number can be in the range from 1 through 8.

vpi

Enter the virtual path identifier (VPI) to which you will add the connection. The VPI can be in the following ranges:

•For a UNI connection: 0-255

•For a NNI or VNNI connection: 0-4095

Note For a VNNI connection, specify one VPI per port.

vci

Enter the virtual connection identifier (VCI) to which you will add the connection.:

•For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 1-65535. For MPLS, the recommended minimum VCI is 35.

•For a VPC, the vci is 0.

Note For VPCs on an MPSM, the dspcons command display shows the VCI as an asterisk (*). When you want to display or configure a VPC (for example the dspcon or cnfcon commands), you need to enter a "0" for the VCI parameter instead of an asterisk, because the <VCI> parameter will not accept an asterisk.

conn_type

Enter a number that identifies the type of connection you are configuring. Enter 0 to identify a VCC, or enter a number in the range from 1 through 1000 to identify the Local VP Id of the VPC (1 to 1000).

service_type

Specify the service type. Enter a number to specify the service type as follows:

•1 = CBR (Constant Bit Rate)

•2 = VBR (Variable Bit Rate)

•3 = Standard ABR (Standard Available Bit Rate implementation)

•4 = UBR (Unspecified Bit Rate2)

•5 = rt-VBR (real-time Variable Bit Rate)

•6 = Foresight ABR (Cisco's prestandard ABR implementation)

Controller_Type

The Virtual Switch Interface (VSI) controller type that manages the connection. On PXM1 platforms:

•1 = PAR (PVC) (Default)

•2 = PNNI (SPVC)

mastership

Mastership role of connection. Select from the following options:

•1 = Master

•2 = Slave (default)

remoteConnId

Remote connection ID. This option is used when defining the master end of a connection. After issuing the addcon command to create the slave side of a double-ended connection, use the generated slave connection ID with this option. On PXM1 platforms the format can be one of the following:

•NodeName.SlotNo.PortNo.VPI.VCI for ATM end point (Use a value of 0 when SlotNo = PXM)

•NodeName.SlotNo.PortNo.0.DLCI for FR end point

Tip You can view the address components for a slave or master connection using the dspcon or dspchan command.

In the following example, the addcon command defines a service module user port as the master side of a feeder segment connection. Feeder connections are always master connections provisioned on the service module user port. When defining the remote connection ID, use a value of 0 for the PXM slot number.

In the following example, the user adds an rt-VBR master feeder segment VCC connection to user port 3 on the current MPSM card, using VPI 100, VCI 100, and a PAR controller. The remote connection ID is M8250_SJ.0.1.100.100.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon 3 100 100 0 5 1 1 M8250_SJ.0.1.100.100
M8250_SJ.1.22.MPSM8T1.ATM.a > 
Step 3 Enter the dspcons command to verify the addition of the feeder segment connection, as shown in the following example:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcons
  ConnId                    Chan ConnType Service Type   PCR[0+1]  Q-Depth State  
  ------------------------  ---- -------  ------------  ---------  ------- -------
  M8250_SJ.22.3.100.100     29   VCC      rt-VBR        3622       1000    Alarm  
  ChanNumNextAvailable     :  30
  Local VpId NextAvailable :  1
M8250_SJ.1.22.MPSM8T1.ATM.a >  
Note In this example, the feeder segment connection is in alarm. Keep in mind that the connection will remain in alarm until you add the routing segment of a three-segment or two-segment feeder connection in the ATM core network
Configuring Local Connections on AUSM and MPSM Cards

The following procedures describe local connections configuration on AUSM and MPSM cards:

•Configuring Service Module to Service Module Local Connections

•Configuring Service Module to PXM1 Local Connections

Configuring Service Module to Service Module Local Connections

To configure a local connection between two service module user ports located on the same card or on different cards, perform the following steps:

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Enter the addcon command to define the slave side of the local connection.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon <port> <vpi> <vci> <conn_type> <service_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] 
Table 4-3 lists and describes the parameters for the addcon command on AUSM and MPSM cards.

The following addcon command defines an MPSM user port as the slave side of the local connection. Note the slave Local Connection ID shown in the display.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon 2 20 200 1 2 1 2 
Local Connection Id is : M8250_SJ.22.2.20.0
M8250_SJ.1.22.MPSM8T1.ATM.a >
Step 3 Write down the Local Connection ID displayed when the addcon command output is completed. You will need the Local Connection ID to configure the master side of the local connection.

Tip If you create the master side of the local connection from the same workstation you used to create the slave connection, you can do a copy and paste sequence to avoid data entry errors.

Step 4 Enter the dspcons command, which displays all configured PVCs, to verify the addition of the slave side of the local connection:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcons
  ConnId                    Chan ConnType Service Type   PCR[0+1]  Q-Depth State  
  ------------------------  ---- -------  ------------  ---------  ------- -------
  M8250_SJ.22.2.20.*        45   VPC      VBR           3622       1000    Active 
  ChanNumNextAvailable     :  47
  Local VpId NextAvailable :  2
M8250_SJ.1.22.MPSM8T1.ATM.a >  
Step 5 Enter the addcon command to define the master side of the local connection.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon <port> <vpi> <vci> <conn_type> <service_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] 
Table 4-3 lists and describes the parameters for the addcon command on AUSM and MPSM cards.

The following addcon command defines an MPSM user port as the master side of the local connection:
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon 3 30 300 2 2 1 1 M8250_SJ.22.2.20.0
M8250_SJ.1.22.MPSM8T1.ATM.a > 
In the above example, the master side of the local connection is added to the slave side of the local connection that was created in Step 2. Note that the <remoteConnID> parameter is the Local Connection ID that was generated when the slave side of the local connection was added.

Step 6 Enter the dspcons command to verify the addition of the master side of the local connection:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcons
  ConnId                    Chan ConnType Service Type   PCR[0+1]  Q-Depth State  
  ------------------------  ---- -------  ------------  ---------  ------- -------
  M8250_SJ.22.2.20.*        45   VPC      VBR           3622       1000    Active 
  M8250_SJ.22.3.30.*        46   VPC      VBR           3622       1000    Active 
  ChanNumNextAvailable     :  47
  Local VpId NextAvailable :  3
M8250_SJ.1.22.MPSM8T1.ATM.a > 
The above example shows the successful addition of both the slave and master endpoints of the local connection. Both endpoints of the local connection are not in alarm.

Step 7 Enter the dspcon command to display the configuration information for a specific local connection endpoint:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcon <Port VPI VCI> 
or
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcon <Port.VPI.VCI>
Replace the <Port VPI VCI> or <Port.VPI.VCI> parameter with the port number, VPI, and VCI for the connection you want to display. The port number, VPI, and VCI parameters are listed in the dspcons command display in the ConnID column, in the format Nodename.Slot.Port.0.VPI.VCI.

Note For VPCs on an MPSM, the dspcons command display shows the VCI as an asterisk (*). When you want to display or configure a VPC (for example the dspcon or cnfcon commands), you need to enter a "0" for the VCI parameter instead of an asterisk, because the <VCI> parameter will not accept an asterisk.

The following is sample output from the dspcon command for the master side of the local connection created in the Step 5. Notice that once the master connection is added, the dspcon report shows the NSAP IDs for both ends of the connection.
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcon 2 20 0
  ChanNum:                           45
  RowStatus:                         Add
  ConnectionType:                    VPC
  ServiceType:                       VBR
  ChanSvcFlag:                       PVC
  PortNum:                           2
  VPI:                               20
  VCI (For VCC):                     *
  Local VPId(for VPC):               1
  EgressQNum:                        3
  IngressQDepth(cells):              1000
  IngressDiscardOption:              CLP hysterisis
  IngressFrameDiscardThreshold       1000
  IngressQCLPHigh(cells):            900
  IngressQCLPLow(cells):             800
  QCLPState:                         LOW
  IngressEfciThreshold(cells):       1000
  UPCEnable:                         Enabled
  PeakCellRate[0+1](cells/sec):      3622
  CellDelayVariation[0+1]:           10000 (micro secs)
Type <CR> to continue, Q<CR> to stop: 
  PeakCellRate[0](cells/sec):        3622
  CellDelayVariation[0]:             250000 (micro secs)
  SustainedCellRate(cells/sec):      3622
  MaximumBurstSize(cells):           1000
  SCRPolicing:                       CLP[0]
  CLPTagEnable:                      Enabled
  FrameGCRAEnable:                   Disable
  InitialBurstSize(cells):           0
  ForesightEnable:                   Disable
  ForeSightPeakCellRate(cells/sec):  3622
  MinimumCellRate(cells/sec):        3622
  InitialCellRate(cells/sec):        3622
  LocalRemoteLpbkState:              Disable
  ChanTestType:                      No Test
  ChanTestState:                     Not In Progress
  ChanRTDresult:                     65535 ms
  Ingress percentage util:           100
  Egress percentage util :           100
Type <CR> to continue, Q<CR> to stop: 
  Egress Service Rate:               3622
  LocalVpi:                          20
  LocalVci:                          *
  LocalNSAP:                         4d383235305f534a000000000000000016000200
  RemoteVpi:                         0
  RemoteVci:                         0
  RemoteNSAP:                        NULL NSAP
  Mastership:                        Slave
  VpcFlag:                           Vpc
  ConnServiceType:                   VBR
  RoutingPriority:                   1
  MaxCost:                           2147483647
  RestrictTrunkType:                 No Restriction
  ConnPCR:                           3622
  ConnMCR:                           3622
  ConnPercentUtil:                   100
  ChanOvrSubOvrRide:                 Enabled
  Stdabr Parameters:
  Minimum Cell Rate:                 10 Cells per second
  Peak Cell Rate:                    10 Cells per second
  Initial Cell rate:                 10 Cells per second
Type <CR> to continue, Q<CR> to stop: 
  Rate Increase Factor:              64
  Rate Decrease Factor:              16
  Nrm -- Inrate Cell Count:          64
  Trm -- Time limit for Frm:         255 milliseconds
  Transient Buffer Exposure:         16777215 Cells
  Fixed Round Trip Time:             0 milliseconds
  ACR Decrease Time Factor:          500 milliseconds
  Cutoff Decrease Factor:            16
  AbrType:                           Switch behavior without VS/VD
  ChanNumNextAvailable     :  48
  Local VpId NextAvailable :  3
M8250_SJ.1.22.MPSM8T1.ATM.a >  
Configuring Service Module to PXM1 Local Connections

To configure a local connection between a service module user port and the PXM1 broadband user port, perform the following steps:

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Enter the addcon command as follows to define the slave side of the local connection on the service module:
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon <port> <vpi> <vci> <conn_type> <service_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] 
Table 4-3 lists and describes the parameters for the addcon command on AUSM and MPSM cards.

The following addcon command defines an MPSM user port as the slave side of the local connection. Note the slave Local Connection ID shown in the display.
M8250_SJ.1.22.MPSM8T1.ATM.a > addcon 2 10 0 1 2 1 2
Local Connection Id is : M8250_SJ.17.2.10.0
There are no restrictions on which cards can host the slave or master endpoints of a local connection. In this step we have chosen to add the slave side of the local connection to the service module user port. We could also add the slave side of the local connection to the PXM1 broadband user port, and then add the master side of the local connection to the service module user port to complete the connection.

Step 3 Write down the Local Connection ID displayed when the addcon command output is completed. You will need the Local Connection ID to configure the master side of the local connection.

Tip If you create the master side of the local connection from the same workstation you used to create the slave connection, you can do a copy and paste sequence to avoid data entry errors.

Step 4 Enter the dspcons command to verify the addition of the slave side of the local connection:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcons
  ConnId                    Chan ConnType Service Type   PCR[0+1]  Q-Depth State  
  ------------------------  ---- -------  ------------  ---------  ------- -------
  M8250_SJ.22.2.10.*        51   VPC      VBR           3622       1000    Alarm  
  ChanNumNextAvailable     :  52
  Local VpId NextAvailable :  2
M8250_SJ.1.22.MPSM8T1.ATM.a > 
Note In the above example, the VCI of the connection appears as an asterisk (*). When you want to display or configure a VPC on an MPSM, you need to enter a "0" for the VCI parameter instead of an asterisk, because the <VCI> parameter will not accept an asterisk.

Step 5 Enter the cc <slotNumber> command to change to the active PXM1:
M8250_SJ.1.22.MPSM8T1.ATM.a > cc 7
(session redirected)
M8250_SJ.1.7.PXM.a > 
Step 6 Enter the addcon command to define the master side of the local connection on the PXM1:
M8230_CH.1.1.PXM.a > addcon <port> <conn_type> <local_VPI> <local_VCI> <service_type> 
[<CAC>] [<mastership>] [<remoteConnId>]
Table 4-4 lists and describes the parameters for the addcon command on the PXM1 card.

Note For detailed instructions on PXM1 configuration, refer to the Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3, the Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3, or the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 documentation.

Table 4-4 Parameters for the addcon Command on the PXM1

Parameter

Description

port_no

Enter the port number to which you will add the connection. To display a list of configured ports, enter the dspports command. The port number is found in the Port column. Port range is from 1 to 32.

conn_type

Connection Type.

•1 = Virtual Path Connection (VPC)

•2 = Virtual Channel Connection (VCC)

local_VPI

Local Virtual Path Identifier (VPI). Range is 0 to 4095.

local_VCI

Local Virtual Channel Identifier (VCI).

•For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 1-65535. For MPLS, the recommended minimum VCI is 35.

•For a VPC, the vci is 0.

Note For VPCs, the dspcons command display shows the VCI as an asterisk (*). On PXM1 card, you can enter the * in place of the <VCI> parameter.

service

Connection Service Type.

•1 = CBR

•2 = VBR

•3 = ABR

•4 = UBR

•5 = VBRrt

CAC

Connection Admission Control.

•1 = Enable

•2 = Disable (default)

mastership

Mastership role of connection.

•1 = Master

•2 = Slave (default)

remoteConnID

Remote connection ID. This option is used when defining the master end of a connection. After issuing the addcon command to create the slave side of a double-ended connection, use the generated slave connection ID with this option. Format is NodeName.SlotNo.PortNo.VPI.VCI

The following addcon command defines a PXM1 broadband user port as the master side of a local connection:
M8250_SJ.1.7.PXM.a > addcon 3 1 20 0 2 2 1 M8250_SJ.17.2.10.0
    Connection ID: M8250_SJ.0.3.20.0
This example adds the master side of the local connection to PXM1 broadband user port 3. The remoteConnID parameter is the Local Connection ID that was generated when the slave side of the local connection was added. After adding the master side of the local connection, a master side Connection ID is generated.

Step 7 Enter the PXM1 dspcons command to verify the addition of the master side of the local connection:
M8250_SJ.1.7.PXM.a > dspcons
This End        Node Name       Other End       Status
7.3.20.*        M8250_SJ        17.2.10.*       OK
17.2.10.*       M8250_SJ        7.3.20.*        OK
M8250_SJ.1.7.PXM.a > 
The above example shows the successful addition of both the slave and master endpoints of the local connection on MPSM and PXM1 cards. Both endpoints are not in alarm and display an OK status.

Step 8 Enter the dspcon command to display the configuration information for a specific local connection endpoint.

On the service module end of the local connection, enter the dspcon command in the following format:
M8250_SJ.1.22.MPSM8T1.ATM.a > dspcon <Port> <vpi> <vci>
Replace the Port, VPI, and VCI parameters with the port number, VPI, and VCI a for the connection you want to display. The port number, VPI, and VCI are listed in the dspcons command display in the ConnID column, in the format Nodename.Slot.Port.0.VPI.VCI.

On the PXM1 end of the local connection, enter the dspcon command in the following format:
M8230_CH.1.1.PXM.a > dspcon <SlotNo.PortNo.VPI.VCI>
Replace the SlotNo.PortNo.VPI.VCI parameter with the Connection ID for the connection you want to display. The Connection ID is listed in the PXM1 dspcons command display in the This End or Other End columns in the format SlotNo.PortNo.VPI.VCI.

The following is sample output from the PXM1 dspcon command for the master side of the local connection created in Step 6:
M8250_SJ.1.7.PXM.a > dspcon 7.3.20.*
    Conn Par Addr       : 7.3.20.* 
    Vc Index            : 805306373
    Conn SM Addr        : 
    Remote Node Name    : M8250_SJ
    Remote Conn PAR Addr: 17.2.10.* 
    Remote Conn SM  Addr: 
    OE VC Index         : 805306373
    Oper Status         : OK
    Conn Failure Reason : 
    RRT Failure Reason  : 
    Admin Status        : UP
    Route               : 
M8250_SJ.1.7.PXM.a > 