Cisco Circuit Emulation Services (CESM/MPSM-8-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2
Provisioning PVCs (PXM1) on CESM and MPSM Cards
Download this chapter
Provisioning PVCs (PXM1) on CESM and MPSM CardsProvisioning PVCs (PXM1) on CESM and MPSM Cards
Download the complete book
PDF Copy, Cisco Circuit Emulation (CESM/MPSM-8-T1E1) Configuration and Command Reference Guide for MGX Switches, Release 5.2PDF Copy, Cisco Circuit Emulation (CESM/MPSM-8-T1E1) Configuration and Command Reference Guide for MGX Switches, Release 5.2 (PDF - 4 MB)
give_us_feedback

Table Of Contents

Provisioning PVCs (PXM1) on CESM and MPSM Cards

Preparing for Provisioning

Quickstart Provisioning Procedures

CESM and MPSM Feeder Connection Configuration Quickstarts

Three-Segment Feeder Connection Configuration Quickstart

Two-Segment Feeder Connection Configuration Quickstart

CESM and MPSM Local Connection Configuration Quickstarts

Service Module to Service Module Local Connection Quickstart

Service Module to PXM1 Local Connection Quickstart

General CESM and MPSM PVC Provisioning Procedures

Configuring PVCs on CESM and MPSM Cards

Configuring Feeder Connections on CESM and MPSM Cards

Configuring Local Connections on CESM and MPSM Cards

Configuring Service Module to Service Module Local Connections

Configuring Service Module to PXM1 Local Connections


Provisioning PVCs (PXM1) on CESM and MPSM Cards

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

These topics describe how to provision Circuit Emulation PVCs on CESM and MPSM cards:

•Preparing for Provisioning

•Quickstart Provisioning Procedures

•General CESM 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 CESM and MPSM Cards 

CESM 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 CESM 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 CESM card connections using just the quickstart procedures and the online help facilities.

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

Preparing for Provisioning

Before you can begin provisioning Circuit Emulation PVCs on CESM 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 CESM and MPSM cards, see "Preparing CESM and MPSM Lines and Ports for Communications."

Quickstart Provisioning Procedures

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

•CESM and MPSM Feeder Connection Configuration Quickstarts

•CESM 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.

CESM and MPSM Feeder Connection Configuration Quickstarts

These quickstart procedures describe how to provision three-segment and two-segment feeder connections on CESM 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 "CESM and MPSM Line Configuration Quickstart" section in "Preparing CESM 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 "CESM and MPSM Port Configuration Quickstart" section in "Preparing CESM and MPSM Lines and Ports for Communications."

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

Step 4 

addcon <options>

Related commands:
dspcons
dspcon <Port>
cnfcon <options>

Configure the master side of the feeder connection from the CESM/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 CESM and MPSM Cards" section that appears later in this chapter.

Step 5 

addcon <options>

Related commands:
dspcons
dspcon <Port>
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.

Refer to the software configuration guides for the switches in the ATM core network for configuration instructions. See the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 or 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 "CESM and MPSM Line Configuration Quickstart" section in "Preparing CESM and MPSM Lines and Ports for Communications."

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

Step 3 

See the "CESM and MPSM Port Configuration Quickstart" section in "Preparing CESM and MPSM Lines and Ports for Communications."

Configure the Circuit Emulation port at the CESM/MPSM end of the PVC you are creating.

Step 4 

addcon <options>

Related commands:
dspcons
dspcon <Port>
cnfcon <options>

Configure the master side of the feeder connection from the service module user port to the PXM1 feeder trunk at the CESM/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 CESM and MPSM Cards" section that appears later in this chapter.

Step 5 

addcon <options>

Related commands:
dspcons
dspcon <Port>
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.

Refer to the software configuration guides for the switches in the ATM core network for configuration instructions. See the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 or the Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30.

CESM and MPSM Local Connection Configuration Quickstarts

These quickstart procedures describe how to provision local connections on CESM 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 "CESM and MPSM Line Configuration Quickstart" section in "Preparing CESM 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 "CESM and MPSM Port Configuration Quickstart" section in "Preparing CESM and MPSM Lines and Ports for Communications."

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

Step 4 

addcon <options>

Related commands:
dspcons
dspcon <Port>
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>
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 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 for PXM1 configuration instructions.

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.

Step 3 

Refer to the PXM1 documentation outlined in Step 2 for configuration instructions.

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

Step 4 

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

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

Step 5 

See the "CESM and MPSM Port Configuration Quickstart" section in "Preparing CESM and MPSM Lines and Ports for Communications."

Configure the Circuit Emulation port at the CESM/MPSM end of the PVC you are creating.

Step 6 

addcon <options>

Related commands:
dspcons
dspcon <Port>
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>
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 CESM and MPSM PVC Provisioning Procedures

This section describes the following procedures for configuring CESM and MPSM card communications:

•Configuring PVCs on CESM and MPSM Cards

•Configuring Feeder Connections on CESM and MPSM Cards

•Configuring Local Connections on CESM and MPSM Cards

Configuring PVCs on CESM and MPSM Cards

The CESM and MPSM card configured for circuit emulation services can communicate only with cards that understand AAL1 encapsulation or are transparent to the encapsulation type, and that support CBR class of service.

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 Frame Relay 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 CESM and MPSM cards on the PXM1 platform are described in Table 4-2.

Table 4-2 CESM 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 Connection1

Local Connection1

Broadband Port Switching

(PXM Broadband ports to SM user ports2 )

Feeder Segment Connection3

(PXM Broadband port configured as Feeder Trunk)

Local Connection1

(PXM Broadband port configured as user port)

1 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.

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

3 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 CESM and MPSM Cards

To configure the feeder segment portion of a three-segment or two-segment feeder connection from a CESM 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 to define a feeder segment connection from a service module user port to the PXM1 feeder trunk: 

M8250_SJ.1.3.CESM.a > addcon <port_num> <sig_type> <partial_fill> <cond_data> 
<cond_signalling> [<controller_type> [<mastership> [<remoteConnId>]]]

Table 4-3 lists and describes the parameters for the addcon command on CESM and MPSM cards.

Note To configure CBR1, CBR2, or CBR3 connection service types, use the -cos option of the xcnfchan or xcnfcon commands.

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

Parameter
Description

port_num

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.Line.Port. The port number range varies with the card type:

•CESM-8T1/B, CESM-8T1, MPSM-8T1-CES range: 1-192

•CESM-8E1, MPSM-8E1-CES range: 1-248

sig_type

Channel associated signaling (CAS) value.

•Basic = 1

•E1 CAS = 2

•DS1 superframe CAS = 3

•DS1 extended superframe CAS = 4

•CCS = 5 (PXM1E, PXM45 only)

•Conditioned E1 CAS = 6

•1x64 Basic without AAL1 Pointer = 7

•DS1 SF CAS MF (available with multiframe option enabled) = 8 (Supported only on CESM-8T1/B)

•DS1 ESF CAS MF (available with multiframe option enabled) = 9 (Supported only on CESM-8T1/B)

Note The channels on a particular line can be either all MF (SF MF or ESF MF) or all non-MF (SF or ESF). The first connection type added on a particular line (MF/non-MF) decides the sync. mode. The second connection must have the same cesCAS type, and so on.

partial_fill

Partial fill for ATM cells. This option determines how many bytes must be assembled before an ATM cell is sent across the network. Partially filled cells take less time to assemble and reduce transmission delay. However, partially filled cells consume more ATM network bandwidth. You can select the number of bytes for ATM cells as follows:

•Fully filled (48 bytes) = 0

•Structured T1 range = 25 to 47

•Structured E1 range = 20 to 47

•Unstructured T1/E1 range = 33 to 47

Note For structured connections other than Basic and 1x64 Basic without AAL1 Pointer, the partial fill value should be greater than the number of DS0s assigned to port + 1.

cond_data

Conditional data is the bit pattern that is used in the data timeslots when there is an underflow or when there is a loss of signal (LOS). For a voice connection, the larger the ConditionalData value, the louder the hiss heard during LOS. The data pattern is configured as a base-10 number to represent an 8-bit binary code.

•UDT = 255

•SDT range = 0 to 255

cond_signalling

Conditional signaling is the signaling bits that are sent on the line when there is an underflow and also toward the network when forming dummy cells. Conditional signaling is a string of bits that you specify with a base-10 number in the range 0-15, where, for example, 15=1111, and 0=0000. These bits represent the four binary signaling bits (A, B, C, and D) to the line or network when an underflow occurs.

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)

•3 = Unknown (MPSM-8T1/E1-CES on PXM1 only)

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.0.0 for CES end point

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

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

The following 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. 

M8250_SJ.1.3.CESM.a > addcon 8 1 0 255 15 1 1 M8250_SJ.0.1.80.80


M8250_SJ.1.3.CESM.a >

This example adds a master feeder segment connection to user port 8 on the current CESM card using basic signaling, fully filled ATM cells, a conditional data bit pattern of 255, a conditional signaling bit pattern of 15, a PAR controller, a VPI value of 80, and a VCI value of 80 to port 1 on the PXM1.

Step 3 Enter the dspcons command, which displays all configured PVCs, to verify the addition of the feeder segment connection: 

M8250_SJ.1.3.CESM.a > dspcons


  Line     ConnId           ChNum Status CDVT  BufSize CLIP  CBRserv  Alarm

  ---- -------------------- ----- ------ ----- ------- ----- -------- -----

     8 M8250_SJ.3.8.0        39   Add     1000   384    2500   struct Alarm


  ChanNumNextAvailable:  40


M8250_SJ.1.3.CESM.a >

In this example, note that the feeder segment connection is in alarm. 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 CESM and MPSM Cards

These procedures describe configuring Local Connections on CESM 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.3.CESM.a > addcon <port_num> <sig_type> <partial_fill> <cond_data> 
<cond_signalling> [<controller_type> [<mastership> [<remoteConnId>]]]

Table 4-3 lists and describes the parameters for the addcon command on CESM and MPSM cards.

The following addcon command defines a CESM user port as the slave side of the local connection. Note the slave Local Connection ID shown in the display. 

M8250_SJ.1.3.CESM.a > addcon 8 1 0 255 15


Local Connection Id is : M8250_SJ.3.8.0.0


M8250_SJ.1.3.CESM.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.3.CESM.a > dspcons


  Line     ConnId           ChNum Status CDVT  BufSize CLIP  CBRserv  Alarm

  ---- -------------------- ----- ------ ----- ------- ----- -------- -----

     8 M8250_SJ.3.8.0        39   Add     1000   384    2500   struct Alarm


  ChanNumNextAvailable:  40


M8250_SJ.1.3.CESM.a >

Step 5 Enter the addcon command to define the master side of the local connection: 

M8250_SJ.1.3.CESM.a > addcon <port_num> <sig_type> <partial_fill> <cond_data> 
<cond_signalling> [<controller_type> [<mastership> [<remoteConnId>]]]

Table 4-3 lists and describes the parameters for the addcon command on CESM and MPSM cards.

The following addcon command defines a CESM user port as the master side of the local connection: 

M8250_SJ.1.3.CESM.a > addcon 7 1 0 255 15 1 1 M8250_SJ.3.8.0.0


M8250_SJ.1.3.CESM.a >

In this example, we added the master side of the local connection to the same CESM card that we added the slave side of the local connection. The remoteConnID parameter entered 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.3.CESM.a > dspcons


  Line     ConnId           ChNum Status CDVT  BufSize CLIP  CBRserv  Alarm

  ---- -------------------- ----- ------ ----- ------- ----- -------- -----

     7 M8250_SJ.3.7.0        38   Add     1000   384    2500   struct  Okay

     8 M8250_SJ.3.8.0        39   Add     1000   384    2500   struct  Okay


  ChanNumNextAvailable:  40


M8250_SJ.1.3.CESM.a >

Note In this example the successful addition of both the slave and master endpoints of the local connection. Both endpoints are not in alarm and display an Okay status.

Step 7 Enter the dspcon command to display the configuration information for a specific local connection endpoint: 

M8250_SJ.1.3.CESM.a > dspcon <Port>

Replace the port parameter with the port number for the connection you want to display. The port number is listed in the dspcons command display in the ConnID column in the format Nodename.Slot.Port.0.

The following is sample output from the dspcon command for the master side of the local connection created in 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.3.CESM.a > dspcon 7

  ChanNum:                  38

  ChanRowStatus:            Add

  ChanLineNum:              7

  ChanMapVpi:               3

  ChanMapVci:               38

  ChanCBRService:           struct

  ChanClockMode:            Synchronous

  ChanCAS:                  Basic

  ChanPartialFill:          47

  ChanMaxBufSize:           384 bytes

  ChanCDVT:                  1000 micro seconds

  C L I P:                  2500 milliseconds

  ChanLocalRemoteLpbkState: Disabled

  ChanTestType:             TestOff

  ChanTestState:            NotInProgress

  ChanRTDresult:            65535 ms

  ChanPortNum               7

  ChanConnType              PVC

  ISDetType                 DetectionDisabled

  CondData                  255

  CondSignalling            15

  ExtISTrig                 DisableIdleSupression

  ISIntgnPeriod             3 seconds 

  ISSignallingCode          0

  OnHookCode                1

  ChanLocalVpi:             0

  ChanLocalVci:             0

  ChanLocalNSAP:            4d383235305f534a000000000000000003000700

  ChanRemoteVpi:            0

  ChanRemoteVci:            0

  ChanRemoteNSAP:           4d383235305f534a000000000000000003000800

  ChanMastership:           Master

  ChanVpcFlag:              Vcc

  ChanConnServiceType:      CBR

  ChanRoutingPriority:      1

  ChanMaxCost:              2147483647

  ChanRestrictTrunkType:    No Restriction

  ChanConnPCR:              4096

  ChanConnMCR:              4096

  ChanConnPercentUtil:      100

  ChanNumNextAvailable:  40

M8250_SJ.1.3.CESM.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 to define the slave side of the local connection on the service module: 

M8230_CH.1.6.CESM.a >addcon <port_num> <sig_type> <partial_fill> <cond_data> 
<cond_signalling> [<controller_type> [<mastership> [<remoteConnId>]]]

Table 4-3 lists and describes the parameters for the addcon command on CESM and MPSM cards.

The following addcon command defines a CESM user port as the slave side of the local connection. Note the slave Local Connection ID shown in the display. 

M8230_CH.1.6.CESM.a > addcon 5 1 0 255 15


Local Connection Id is : M8230_CH.6.5.0.0


M8230_CH.1.6.CESM.a >

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, which displays all configured PVCs, to verify the addition of the slave side of the local connection: 

M8230_CH.1.6.CESM.a > dspcons


  Line     ConnId           ChNum Status CDVT  BufSize CLIP  CBRserv  Alarm

  ---- -------------------- ----- ------ ----- ------- ----- -------- -----

     5 M8230_CH.6.5.0        36   Add     1000   480    2500   struct Alarm


  ChanNumNextAvailable:  37


M8230_CH.1.6.CESM.a >

Step 5 Enter the addcon command to define the master side of the local connection on the PXM1: 

M8230_CH.1.1.PXM.a > addcon <port_no> <conn_type> <local_VPI> <local_VCI> <service> 

    [<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). Range is 0 to 65535.

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: 

M8230_CH.1.1.PXM.a > addcon 2 2 50 50 1 2 1 M8230_CH.6.5.0.0


    Connection ID: M8230_CH.0.2.50.50


M8230_CH.1.1.PXM.a >

This example adds the master side of the local connection to PXM1 broadband user port 2. 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 6 Enter the PXM1 dspcons command, which displays all configured PVCs, to verify the addition of the master side of the local connection: 

M8230_CH.1.1.PXM.a > dspcons

This End        Node Name       Other End       Status


1.2.50.50       M8230_CH        6.5.0.0         OK

6.5.0.0         M8230_CH        1.2.50.50       OK

M8230_CH.1.1.PXM.a >

Note In this example the successful addition of both the slave and master endpoints of the local connection added to the CESM and PXM1 cards. Both endpoints are not in alarm and display an OK status.

Step 7 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_CH.1.6.CESM.a > dspcon <Port>

Replace the port parameter with the port number for the connection you want to display. The port number is listed in the dspcons command display in the ConnID column in the format Nodename.Slot.Port.0.

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 5: 

M8230_CH.1.1.PXM.a > dspcon 1.2.50.50

    Conn Par Addr       : 1.2.50.50

    Vc Index            : 805306371

    Conn SM Addr        : Ept:      vpi = 50 vci = 50 vpc = 0

    ifNum = 0x2        conNum = 0x7ffc     glcn = 0x8009     lcn = 32

    qosFwd = 1028 qosBwd = 1028 pcrFwd = 50 pcrBwd = 50 mcrFwd = 50 mcrBwd = 50

    Remote Node Name    : M8230_CH

    Remote Conn PAR Addr: 6.5.0.0

    Remote Conn SM  Addr: Ept:      vpi = 0 vci = 0 vpc = 0

    ifNum = 0x60005    conNum = 0x7ffc     glcn = 0x2c9      lcn = 36

    qosFwd = 1028 qosBwd = 1028 pcrFwd = 50 pcrBwd = 50 mcrFwd = 50 mcrBwd = 50

    OE VC Index         : 805306371

    Oper Status         : OK

    Conn Failure Reason : 

    RRT Failure Reason  : 

    Admin Status        : UP

    Route               : 

M8230_CH.1.1.PXM.a >