Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 - Provisioning PVCs (PXM1) on FRSM and MPSM Cards [Cisco MGX 8800 Series Switches]

Table Of Contents

Provisioning PVCs (PXM1) on FRSM and MPSM Cards

Preparing for Provisioning

Quickstart Provisioning Procedures

FRSM and MPSM Feeder Connection Configuration Quickstarts

Three-Segment Feeder Connection Configuration Quickstart

Two-Segment Feeder Connection Configuration Quickstart

FRSM and MPSM Local Connection Configuration Quickstarts

Service Module to Service Module Local Connection Quickstart

Service Module to PXM1 Local Connection Quickstart

General FRSM and MPSM PVC Provisioning Procedures

Configuring PVCs on FRSM and MPSM Cards

Configuring Feeder Connections on FRSM and MPSM Cards

Configuring Local Connections on FRSM and MPSM Cards

Configuring Service Module to Service Module Local Connections

Configuring Service Module to PXM1 Local Connections

Provisioning PVCs (PXM1) on FRSM and MPSM Cards

This chapter describes how to provision Frame Relay Permanent Virtual Circuits (PVCs) on the physical ports of the FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2/B cards using the command-line interface (CLI).

These topics describe how to provision Frame Relay PVCs on FRSM and MPSM cards:

•Preparing for Provisioning

•Quickstart Provisioning Procedures

•General FRSM 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.

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

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

FRSM 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 FRSM 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 FRSM 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, "FRSM and MPSM Command Reference."

Preparing for Provisioning

Before you can begin provisioning Frame Relay PVCs on FRSM 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, see "Preparing FRSM and MPSM Lines and Ports for Communications."

Quickstart Provisioning Procedures

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

•FRSM and MPSM Feeder Connection Configuration Quickstarts

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

FRSM and MPSM Feeder Connection Configuration Quickstarts

These quickstart procedures describe how to provision three-segment and two-segment feeder connections on FRSM 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 "FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, MPSM-8T1-FRM, MPSM-8E1-FRM, and FRSM-HS2/B Line Configuration Quickstart" or the "FRSM-2T3E3 and FRSM-2CT3 Line Configuration Quickstart" sections that appears in "Preparing FRSM 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 "Frame Relay Port Configuration Quickstart" section that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

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

Step 4

addcon <options>

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

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

Step 5

addcon <options>

Related commands:
dspcons
dspcon <Port.DLCI>
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 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5 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 "FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, MPSM-8T1-FRM, MPSM-8E1-FRM, and FRSM-HS2/B Line Configuration Quickstart" or the "FRSM-2T3E3 and FRSM-2CT3 Line Configuration Quickstart" sections that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

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

Step 3

See the "Frame Relay Port Configuration Quickstart" section that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

Configure the Frame Relay port at the FRSM/MPSM end of the PVC you are creating.

Step 4

addcon <options>

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

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

Step 5

addcon <options>

Related commands:
dspcons
dspcon <Port.DLCI>
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 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5 or the Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30.

FRSM and MPSM Local Connection Configuration Quickstarts

These quickstart procedures describe how to provision local connections on FRSM 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 "FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, MPSM-8T1-FRM, MPSM-8E1-FRM, and FRSM-HS2/B Line Configuration Quickstart" or the "FRSM-2T3E3 and FRSM-2CT3 Line Configuration Quickstart" sections that appears in "Preparing FRSM 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 "Frame Relay Port Configuration Quickstart" section that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

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

Step 4

addcon <options>

Related commands:
dspcons
dspcon <Port.DLCI>
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.DLCI>
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 "FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, MPSM-8T1-FRM, MPSM-8E1-FRM, and FRSM-HS2/B Line Configuration Quickstart" or the "FRSM-2T3E3 and FRSM-2CT3 Line Configuration Quickstart" sections that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

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

Step 5

See the "Frame Relay Port Configuration Quickstart" section that appears in "Preparing FRSM and MPSM Lines and Ports for Communications."

Configure the Frame Relay port at the FRSM/MPSM end of the PVC you are creating.

Step 6

addcon <options>

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

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

•Configuring PVCs on FRSM and MPSM Cards

•Configuring Feeder Connections on FRSM and MPSM Cards

•Configuring Local Connections on FRSM and MPSM Cards

Configuring PVCs on FRSM 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 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 FRSM and MPSM cards on the PXM1 platform are described in Table 4-2.

Table 4-2 FRSM 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 FRSM and MPSM Cards

To configure the feeder segment portion of a three-segment or two-segment feeder connection from a FRSM 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.

On MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, and FRSM-8E1-C cards, use the following addcon command syntax:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcon <port> <dlci> <cir> <chan_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] [<serv_type>]
On FRSM-2T3E3, FRSM-2CT3, and FRSM-HS2/B cards, use the following addcon command syntax:
M8250_SJ.1.11.VHS2CT3.a > addcon <port> <dlci> <cir> <chan_type> <serv_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>]
Table 4-3 lists and describes the parameters for the addcon command on FRSM and MPSM cards.

Table 4-3 Parameters for the addcon Command on the FRSM 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.Line.Port. The port number range varies with the card type:

•FRSM-8T1, FRSM-8T1-C, MPSM-8T1-FRM = 1-192

•FRSM-8E1, FRSM-8E1-C, MPSM-8E1-FRM = 1-248

•FRSM-2T3E3 = 1 to 2

•FRSM-2CT3 = 1 to 256

•FRSM-HS2/B = 1-2 (HSSI back card)

•FRSM-HS2/B = 1-8 (12IN1-8S back card)

dlci

Data-link connection identifier (DLCI) value.

Range: 0-1023

Note If you are adding a connection to a port that has LMI signalling enabled, you can not use DLCI number 0 (ANNEX A & D) or 1023 (STRATA LMI).

cir

Committed information rate (CIR) bps value. The CIR should be less than the configured port speed. Range by card type:

•FRSM-8T1, FRSM-8T1-C, MPSM-8T1-FRM = 0-1536000

•FRSM-8E1, FRSM-8E1-C, MPSM-8E1-FRM = 0-2048000

•FRSM-2T3 = 0-44210000

•FRSM-2E3 = 0-34010000

•FRSM-2CT3 = 0-1536000

•FRSM-HS2/B = 0-51840000 (HSSI back card)

•FRSM-HS2/B = 0-8192000 (12IN1-8S back card)

To calculate the CIR (bps) from cells per second (cps) use the following formula: ( ( (cps * 38400) / 144) + 1) or use the cpstobps command where:

•cps = remote PCR for High Priority (CBR) or UBR

•cps = remote SCR for rtVBR or nrtVBR

•cps = remote MCR for stdABR

chan_type

Channel internetworking type. Set this option to one of the following:

•On MPSM-8T1-FRM, MPSM-8E1-FRM:

–1 = Frame Relay to ATM Network Interworking (NIW, FRF.5—default)

–2 = Frame Relay to ATM service interworking (SIW) transparent (FRF.8.1, no protocol ID translation)

–3 = Frame Relay to ATM service interworking (SIW) translational (FRF.8.1, protocol ID translation)

–4 = ATM Forum FUNI (Frame Relay UNI) mode 1A

–5 = Frame Forwarding (no translation or mapping of header contents, CRC evaluated)

•On FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C, FRSM-2T3E3, FRSM-2CT3, FRSM-HS2/B:

–1 = Frame Relay to ATM Network Interworking (NIW, FRF.5—default)

–2 = Frame Relay to ATM service interworking (SIW) transparent (FRF.8, no protocol ID translation)

–3 = Frame Relay to ATM service interworking (SIW) translational (FRF.8, protocol ID translation)

–4 = ATM Forum FUNI (Frame Relay UNI) mode 1A

–5 = Frame Forwarding (no translation or mapping of header contents, CRC evaluated)

CAC

Connection Admission Control.

•1 = Enable

•2 = Disable (Default)

Controller_Type

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

•1 = PAR (PVC) (Default)

•2 = PNNI (SPVC)

Note PNNI is not supported on PXM1 platforms.

mastership

Mastership role of connection. Select from the following options:

•1 = Master

•2 = Slave (default)

•3 = Unknown (MPSM-8T1/E1-FRM 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.DLCI for FR 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.

serv_type

Service class type. This parameter determines which class of service (CoS) queue is used by the connection.

•MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, FRSM-8E1-C on PXM1 platforms:

–1 = High Priority

–2 = rtVBR

–3 = nrtVBR

–4 = fstABR

–5 = UBR

–9 = stdABR

–0 = Not configured (Default)

•FRSM-2T3E3, FRSM-2CT3, FRSM-HS2/B on PXM1 platforms (Egress Service Type):

–1 = High Priority queue

–2 = rtVBR queue

–3 = nrtVBR queue

–4 = fstABR queue

–5 = UBR queue

–9 = stdABR queue

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.22.MPSM8T1.FRM.a > addcon 1 16 1536000 1 1 1 1 M8250_SJ.0.1.10.10 3
M8250_SJ.1.22.MPSM8T1.FRM.a > 
This example adds a nrtVBR master feeder segment connection to user port 1 on the current MPSM card using DLCI 16, a CIR of 1536000 bps, Frame Relay to ATM network interworking (NIW), CAC enabled, a PAR controller, a VPI value of 10, and a VCI value of 10 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.22.MPSM8T1.FRM.a > dspcons
  Line       ConnId          Chan EQ ServType I/EQDepth   I/EQDEThre  I/EECNThre  Fst/ DE Type   LocRmtLpbk  Alarm
  --- -------------------    ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- -----  ---------  ------
  1   M8250_SJ.22.1.0.16     16   Lo nrtVBR   65535/65535 32767/32767  6553/6553  Dis/Dis NIW    Disabled  Yes 
  ChanNumNextAvailable:  17
M8250_SJ.1.22.MPSM8T1.FRM.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 FRSM and MPSM Cards

These procedures describe configuring Local Connections on FRSM 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.

On MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, and FRSM-8E1-C cards, use the following addcon command syntax:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcon <port> <dlci> <cir> <chan_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] [<serv_type>]
On FRSM-2T3E3, FRSM-2CT3, and FRSM-HS2/B cards, use the following addcon command syntax:
M8250_SJ.1.11.VHS2CT3.a > addcon <port> <dlci> <cir> <chan_type> <serv_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>]
Table 4-3 lists and describes the parameters for the addcon command on FRSM 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.FRM.a > addcon 1 100 1536000 1  
Local Connection ID is : M8250_SJ.22.1.0.100
M8250_SJ.1.22.MPSM8T1.FRM.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.FRM.a > dspcons
  Line       ConnId          Chan EQ ServType I/EQDepth   I/EQDEThre  I/EECNThre  Fst/ DE Type   LocRmtLpbk  Alarm
  --- -------------------    ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- -----  ---------  ------
  1   M8250_SJ.22.1.0.100    17   Lo NotConf  65535/65535 32767/32767  6553/6553  Dis/Dis NIW    Disabled  Yes 
  ChanNumNextAvailable:  18
M8250_SJ.1.22.MPSM8T1.FRM.a 
Step 5 Enter the addcon command to define the master side of the local connection.

On MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, and FRSM-8E1-C cards, use the following addcon command syntax:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcon <port> <dlci> <cir> <chan_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] [<serv_type>]
On FRSM-2T3E3, FRSM-2CT3, and FRSM-HS2/B cards, use the following addcon command syntax:
M8250_SJ.1.11.VHS2CT3.a > addcon <port> <dlci> <cir> <chan_type> <serv_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>]
Table 4-3 lists and describes the parameters for the addcon command on FRSM and MPSM cards.

The following addcon command defines a MPSM user port as the master side of the local connection:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcon 2 200 1536000 1 1 1 1 M8250_SJ.22.1.0.100
M8250_SJ.1.22.MPSM8T1.FRM.a 
In this example, we added the master side of the local connection to the same MPSM 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.22.MPSM8T1.FRM.a > dspcons
  Line       ConnId          Chan EQ ServType I/EQDepth   I/EQDEThre  I/EECNThre  Fst/ DE Type   LocRmtLpbk  Alarm
  --- -------------------    ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- -----  ---------  ------
  1   M8250_SJ.22.1.0.100    17   Lo NotConf  65535/65535 32767/32767  6553/6553  Dis/Dis NIW    Disabled  No  
  2   M8250_SJ.22.2.0.200    19   Lo NotConf  65535/65535 32767/32767  6553/6553  Dis/Dis NIW    Disabled  No  
  ChanNumNextAvailable:  20
M8250_SJ.1.22.MPSM8T1.FRM.a > 
Note in this example 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.FRM.a > dspcon <Port.DLCI>
Replace the Port.DLCI parameter with the port number and the DLCI for the connection you want to display. The port number and DLCI is listed in the dspcons command display in the ConnID column in the format Nodename.Slot.Port.0.DLCI.

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.FRM.a > dspcon 2.200
  ChanNum:                  19
  ChanRowStatus:            Add
  ChanPortNum:              2
  ChanDLCI:                 200
  EgressQSelect:            Lo
  ChanServType:             NotConf
  IngressQDepth:            65535
  IngressQDEThresh:         32767
  IngressQECNThresh:        6553
  EgressQDepth:             65535
  EgressQDEThresh:          32767
  EgressQECNThresh:         6553
  DETaggingEnable:          Disabled
  CIR:                      1536000
  Bc:                       5100
  Be:                       5100
  IBS:                      100
  ForeSightEnable:          Disabled
  QIR:                      4000
  MIR:                      4000
  PIR:                      4000
  ICR:                      0
  MCR:                      0
  PCR:                      0
  RIF:                      64
  RDF:                      16
  Nrm:                      64
  Trm:                      255 ms
  TBE:                      16777215 Cells
  FRTT:                     0 ms
  ADTF:                     500 ms
  CDF:                      16
  ChanLocalRemoteLpbkState: Disabled
  ChanTestType:             TestOff
  ChanTestState:            NotInProgress
  ChanRTDresult:            65535 ms
  ChanType:                 NIW         
  ChanFECNmap:              setEFCIzero
  ChanDEtoCLPmap:           mapCLP    
  ChanCLPtoDEmap:           mapDE    
  ChanFrConnType:           PVC
  ChanIngrPercentUtil:      100
  ChanEgrPercentUtil:       100
  ChanEgrSrvRate:           1536000
  ChanOvrSubOvrRide:        Enabled
  ChanLocalVpi:             0
  ChanLocalVci:             200
  ChanLocalNSAP:            4d383235305f534a000000000000000016000200
  ChanRemoteVpi:            0
  ChanRemoteVci:            100
  ChanRemoteNSAP:           4d383235305f534a000000000000000016000100
  ChanMastership:           Master
  ChanVpcFlag:              Vcc
  ChanConnServiceType:      ATFR
  ChanRoutingPriority:      1
  ChanMaxCost:              2147483647
  ChanRestrictTrunkType:    No Restriction
  ChanConnPCR:              4000 cps
  ChanConnMCR:              4000 cps
  ChanConnPercentUtil:      100
  ChanServiceRateOverride:  disabled
  ChanServiceRate:          4000 cps
  ChanZeroCirEir:           0 bps
  ChanNumNextAvailable:  20
M8250_SJ.1.22.MPSM8T1.FRM.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:

On MPSM-8T1-FRM, MPSM-8E1-FRM, FRSM-8T1, FRSM-8T1-C, FRSM-8E1, and FRSM-8E1-C cards, use the following addcon command syntax:
M8250_SJ.1.22.MPSM8T1.FRM.a > addcon <port> <dlci> <cir> <chan_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>] [<serv_type>]
On FRSM-2T3E3, FRSM-2CT3, and FRSM-HS2/B cards, use the following addcon command syntax:
M8250_SJ.1.11.VHS2CT3.a > addcon <port> <dlci> <cir> <chan_type> <serv_type> [<CAC>] 
[<Controller_Type>] [<mastership>] [<remoteConnId>]
Table 4-3 lists and describes the parameters for the addcon command on FRSM and MPSM cards.

The following addcon command defines a FRSM user port as the slave side of the local connection. Note the slave Local Connection ID shown in the display.
M8230_CH.1.13.FRSM.a > addcon 1 100 1536000 1
Local Connection ID is : M8230_CH.13.1.0.100
M8230_CH.1.13.FRSM.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.13.FRSM.a > dspcons
  Line       ConnId          Chan EQ ServType I/EQDepth   I/EQDEThre  I/EECNThre  Fst/ DE Type   LocRmtLpbk  Alarm
  --- -------------------    ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- -----  ---------  ------
  1   M8230_CH.13.1.0.100    16   Lo NotConf  65535/65535 32767/32767  6553/6553  Dis/Dis NIW    Disabled  Yes 
  ChanNumNextAvailable:  17
M8230_CH.1.13.FRSM.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 100 100 2 1 1 M8230_CH.13.1.0.100
    Connection ID: M8230_CH.0.2.100.100
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.100.100     M8230_CH        13.1.0.100      OK
13.1.0.100      M8230_CH        1.2.100.100     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 FRSM 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:
M8230_CH.1.13.FRSM.a > dspcon <Port.DLCI>
Replace the Port.DLCI parameter with the port number and the DLCI for the connection you want to display. The port number and DLCI is listed in the dspcons command display in the ConnID column in the format Nodename.Slot.Port.0.DLCI.

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.100.100
    Conn Par Addr       : 1.2.100.100
    Vc Index            : 805306372
    Conn SM Addr        : Ept:      vpi = 100 vci = 100 vpc = 0
    ifNum = 0x2        conNum = 0x7ffb     glcn = 0x800a     lcn = 34
    qosFwd = 1027 qosBwd = 1027 pcrFwd = 50 pcrBwd = 50 mcrFwd = 50 mcrBwd = 50
    Remote Node Name    : M8230_CH
    Remote Conn PAR Addr: 13.1.0.100
    Remote Conn SM  Addr: Ept:      vpi = 0 vci = 100 vpc = 0
    ifNum = 0xd0001    conNum = 0x7ffb     glcn = 0x2ca      lcn = 16
    qosFwd = 1027 qosBwd = 1027 pcrFwd = 50 pcrBwd = 50 mcrFwd = 50 mcrBwd = 50
    OE VC Index         : 805306372
    Oper Status         : OK
    Conn Failure Reason : 
    RRT Failure Reason  : 
    Admin Status        : UP
    Route               : 
M8230_CH.1.1.PXM.a >