Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.1 - Provisioning Frame Relay Services [Cisco MGX 8800 Series Switches]

Table Of Contents

Provisioning Frame Relay Services on MPSM-T3E3-155 and MPSM-16-T1E1

MPSM-T3E3-155 and MPSM-16-T1E1 Connection Types

Frame Relay Quickstart Provisioning Procedures

MPSM to MPSM Frame Relay Configuration Quickstart

MPSM Frame Relay to MPSM ATM Configuration Quickstart

MPSM to Non-MPSM Frame Relay Configuration Quickstart

Frame Relay Configuration Procedures

General Information

Provisioning Frame Relay Ports

Preparing to Add Frame Relay Ports

Adding Frame Relay Ports

Partitioning Port Resources Between Controllers

Selecting the Port Signaling Protocol

Provisioning and Managing SPVCs

Preparing to Add SPVCs

Configuring the Slave Side of SPVCs

Configuring the Master Side of SPVCs

Multilink Frame Relay on the MPSM-T3E3-155

MFR Command Summary

MFR Features

MFR Restrictions

Multilink Frame Relay Quick Start Provisioning Procedure

Multilink Frame Relay General Provisioning Procedures

Creating an MFR Bundle

Configuring an MFR Bundle

Adding Links to an MFR Bundle

Configuring MFR Links

Adding a Port to the MFR Bundle

Adding SPVCs to MFR Bundles

Provisioning Frame Relay Services on MPSM-T3E3-155 and MPSM-16-T1E1

This chapter describes how to provision Frame Relay services on the MPSM-T3E3-155 and MPSM-16-T1E1 cards, and provides procedures for adding Frame Relay ports and connections to the physical lines and paths. The types of links and connections are described in Table 4-1.

Note Before you perform the procedures in this chapter, you must set up the MPSM-T3E3-155 and MPSM-16-T1E1 cards and lines from the PXM controller as described in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication." Make sure that you select the appropriate card SCT for the controller that you are using.

MPSM-T3E3-155 and MPSM-16-T1E1 Connection Types

You can configure an SPVC between two MPSM-T3E3-155 and MPSM-16-T1E1 cards Frame Relay ports in any of the following instances:

•Any two Frame Relay ports on one MPSM-T3E3-155 or MPSM-16-T1E1 card in a Cisco MGX 8850 (PXM1E/PXM45) or Cisco 8830 switch

•Any two Frame Relay ports on different MPSM-T3E3-155 or MPSM-16-T1E1 cards in the same Cisco MGX 8850 (PXM1E/PXM45) or Cisco 8830 switch

•Any two Frame Relay ports on different MPSM-T3E3-155 or MPSM-16-T1E1 cards in different Cisco MGX 8850/8830 switches

Table 4-1 summarizes all supported Frame Relay connections for the MPSM-T3E3-155 and MPSM-16-T1E1 cards.

Table 4-1 Supported MPSM-T3E3-155 and MPSM-16-T1E1 Frame Relay Connections

Remote Card

Restrictions

Procedure

MPSM-T3E3-155

MPSM-T3E3-155 cards do not support NIW or NIW-Replace SPVCs between ATM and Frame Relay ports.

Use the "MPSM to MPSM Frame Relay Configuration Quickstart" to configure an SPVC between two MPSM Frame Relay ports.

Use the "MPSM Frame Relay to MPSM ATM Configuration Quickstart" to configure an SPVC between an MPSM Frame relay port and an MPSM ATM port.

MPSM-16-T1E1

MPSM-T3E3-155 cards do not support NIW or NIW-Replace SPVCs between ATM and Frame Relay ports.

MPSM-8T1E1

MPSM-8T1E1 must be in Frame Relay mode.

FRSM-2CT3

None

Use the "MPSM to Non-MPSM Frame Relay Configuration Quickstart" section to configure an SPVC between an MPSM Frame Relay port and a port on a different card.

FRSM-2T3E3

MPSM-T3E3-155 connections only; FRSM-2CT3 cannot channelize for the MPSM-16-T1E1.

FRSM-8T1E1

None

FRSM-HS2/B

None

FRSM12

MPSM-T3E3-155 connections only; FRSM12 cannot channelize for the MPSM-16-T1E1.

AUSM-8T1E1

AUSM-8T1E1 cards do not support NIW or NIW-Replace SPVCs.

AXSM

AXSM cards do not support NIW and NIW-Replace SPVCs, and AXSM/A and AXSM/B cards do not support ABR-STC SPVCs.

AXSM needs T3 back card for MPSM-16-T1E1 compatibility.

PXM1E

PXM1E cards do not support NIW or NIW-Replace SPVCs.

BXM

BXM-E

BXM-D

BXM-EX

MPSM-T3E3-155 connections only.

RPM

RPM cards do not support NIW or NIW-replace SPVCs.

PXM1

PVC connections only; PXM1 does not support PNNI and SPVCs.

PXM1 cards do not support NIW or NIW-replace SPVCs.

For MPSM-T3E3-155 and MPSM-16-T1E1, NIW connection type is supported for building SPVCS from Frame Relay port to Frame Relay port to a MPSM-8T1E1.

However, you must configure the channel type on either the MPSM-T3E3-155 or MPSM-16-T1E1 as frNIWReplace and on the MPSM-8T1E1 as NIW. If both sides are configured as NIW, the SPVC will not pass traffic.

Frame Relay Quickstart Provisioning Procedures

This section contains abbreviated procedures for provisioning the communication capabilities of MPSM-T3E3-155 cards installed in Cisco MGX 8850/8830 Release 5 switches. These procedures provide a high level overview and summary for users who may already be experienced in configuring Cisco MGX 8850/8830 switches. Most steps in the quickstart procedures refer directly to the section that contains detailed configuration procedures.

This section has the following quickstarts:

•MPSM to MPSM Frame Relay Configuration Quickstart

•MPSM Frame Relay to MPSM ATM Configuration Quickstart

•MPSM to Non-MPSM Frame Relay Configuration Quickstart

Before configuring Frame Relay connections, perform the following tasks:

•Complete the general switch configuration procedures described in Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

•Set up lines and/or paths for the Frame Relay service and its connections, as described in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Note For a detailed description of the commands used in this chapter, refer to "MPSM-T3E3-155 and MPSM-16-T1E1 Command Reference."

Note The equipment at both ends of a Frame Relay line must be configured with compatible settings in order for the link to be logically completed.

MPSM to MPSM Frame Relay Configuration Quickstart

To configure an SPVC between a local MPSM-T3E3-155 or MPSM-16-T1E1 Frame Relay port and a remote Frame Relay port on the same or a different MPSM-T3E3-155 or MPSM-16-T1E1 switch, perform the following steps:

Command

Comments

Step 1

Establish a connection between the MGX switches that hold the MPSM-T3E3-155 or MPSM-16-T1E1 cards to be connected.

If the SPVC endpoints are on different nodes, configure trunks between the nodes and verify PNNI connectivity.

See the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Step 2

username

<password>

Start a configuration session.

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

Step 3

cc

Start a management session with the MPSM-T3E3-155 or MPSM-16-T1E1 card.

Step 4

setctx fr

If the current CLI context is ATM, use the setctx fr command to change to the Frame Relay context.

Step 5

upln <bay.line>

Bring up (activate) the physical lines at both ends of the SPVC.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Remember to select the appropriate service class template (SCT) for the controller, or controllers, that you are using.

Step 6

cnfln <bay.line> <arguments>

If you are configuring a DS3, SONET or SDH line:

cnfpath <path> <arguments>

uppath <path>

Configure the line. If you are using an MPSM-T3E3-155, you must also channelize the line into DS1 paths and bring up the paths at both ends of the SPVC.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Step 7

addport

Related command:

dspports

Add and configure Frame Relay ports on the lines or paths at each end of the SPVC you are creating. This step establishes Frame Relay communication between two Frame Relay devices.

For standard port configuration, see the "Provisioning Frame Relay Ports" section in this chapter.

Step 8

addcon

Related commands:

dspcon

dspcons

Add and configure the slave side of the SPVC. Record the NSAP address that is returned after the connection is added.

See the "Configuring the Slave Side of SPVCs" section.

Step 9

cc

or

username

<password>

cc

Start a configuration session with the card that will host the master end of the connection. If it is not the same card:

•cc to the slot

•Log in to the remote node and cc to the slot

Step 10

addcon

Related commands:

dspcon

dspcons

Add, configure, and connect the master side of the SPVC. Use the NSAP address from the slave connection.

See the "Configuring the Master Side of SPVCs" section.

MPSM Frame Relay to MPSM ATM Configuration Quickstart

To configure an SPVC between a local MPSM-T3E3-155 or MPSM-16-T1E1 Frame Relay port and an ATM port on another MPSM-T3E3-155 or MPSM-16-T1E1 in the same switch or in another switch, perform the following steps:

Command

Comments

Step 1

Establish a connection between the MGX switches that hold the MPSM cards to be connected.

If the SPVC endpoints are on different nodes, configure trunks between the nodes and verify PNNI connectivity.

See the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Step 2

username

<password>

Start a configuration session.

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

Step 3

cc

Start a management session with the card that will host the slave side of the SPVC (if you are configuring a double-ended SPVC).

Step 4

setctx [atm | fr]

Set the current CLI context as appropriate for the slave endpoint of the SPVC you are configuring. If the endpoint is on a Frame Relay port, set the CLI context to fr. Otherwise, set the CLI context to atm.

Step 5

upln <bay.line>

Bring up (activate) the physical lines at each end of the SPVC you are creating.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Remember to select the appropriate service class template (SCT) for the controller, or controllers, that you are using.

Step 6

cnfln <bay.line> <arguments>

If you are configuring a DS3, SONET or SDH line:

cnfpath <path> <arguments>

uppath <path>

Configure the line. If you are using an MPSM-T3E3-155, you must also channelize the line into DS1 paths and bring up the paths at both ends of the SPVC.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Step 7

addport

Related command:

dspports

Add a port to the line or path for the SPVC. This port is either a Frame Relay or ATM port, as determined in step 4.

For standard port configuration, see the "Provisioning Frame Relay Ports" section in this chapter.

Step 8

cnfpart

Related commands:

dspparts

dsppart

Optional: Configure trunk resources on the PNNI controller. This step can assign all of the trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.

Note A partition is automatically added when you add a port. Use the cnfpart command to change the configuration of a resource partition.

See the "Partitioning Port Resources Between Controllers" section in this chapter.

Step 9

cc

Start a management session with the PXM card.

Step 10

dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Define the signaling protocol used on the trunk. The default signaling protocol is UNI Version 3.1. Specify pnni10 for PNNI trunks.

See the "Selecting the Port Signaling Protocol" section in this chapter.

Step 11

cc

Start a management session withStart a management session with the MPSM card that will host the slave end of the SPVC.

Step 12

setctx [atm | fr]

Set the current CLI context as appropriate for the slave end of the SPVC you are configuring.

Step 13

addcon

Related commands:

dspcon

dspcons

Add and configure the slave side of an SPVC (if you are configuring a double-ended SPVC). Record the NSAP address that is returned after the connection is added.

See the "Configuring the Slave Side of SPVCs" section.

Step 14

cc

or

username

<password>

cc

Start a configuration session with the card that will host the master end of the connection. If it is not the same card:

•cc to the slot

•Log in to the remote node and cc to the slot

Step 15

addcon

Related commands:

dspcon

dspcons

Add, configure, and connect the master side of an SPVC on the remote card. Use the NSAP address from the slave connection.

See the "Configuring the Master Side of SPVCs" section.

MPSM to Non-MPSM Frame Relay Configuration Quickstart

To configure an SPVC between a local MPSM-T3E3-155 or MPSM-16-T1E1 port and a port on a different card type in the same switch or in another switch, perform the following steps:

Command

Comments

Step 1

Establish a connection between the two switches that hold the cards you plan to connect.

If the SPVC endpoints are on different nodes, configure trunks between the nodes and verify PNNI connectivity.

See the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Step 2

username

<password>

Start a configuration session.

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

Step 3

cc

Start a management session with the MPSM card.

Step 4

setctx fr

Use the setctx fr command to ensure you are using the Frame Relay CLI context.

Step 5

upln <bay.line>

Bring up (activate) the physical lines at each end of the SPVC you are creating.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Remember to select the appropriate service class template (SCT) for the controller, or controllers, that you are using.

Step 6

cnfln <bay.line> <arguments>

If you are configuring a DS3, SONET or SDH line:

cnfpath <path> <arguments>

uppath <path>

Configure the line. If you are using an MPSM-T3E3-155, you must also channelize the line into DS1 paths and bring up the paths at both ends of the SPVC.

See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

Step 7

addport

Related command:

dspports

Add a Frame Relay port on the MPSM card.

For standard port configuration, see the "Provisioning Frame Relay Ports" section.

Step 8

cnfpart

Related commands:

dspparts

dsppart

Optional: Configure trunk resources on the PNNI controller. This step can assign all of the trunk bandwidth to one controller, or it can assign portions of the trunk bandwidth to each controller.

Note A partition is automatically added when you add a port. Use the cnfpart command to change the configuration of a resource partition.

See the "Partitioning Port Resources Between Controllers" section.

Step 9

cc

Start a management session with the PXM card.

Step 10

dnpnport

cnfpnportsig

uppnport

Related commands:

dsppnports

dsppnport

dsppnportsig

Define the signaling protocol used on the trunk. The default signaling protocol is UNI Version 3.1. Specify pnni10 for PNNI trunks.

See the "Selecting the Port Signaling Protocol" section.

Step 11

cc

Start a management session with the MPSM-T3E3-155 or MPSM-16-T1E1 card.

Step 12

addcon

Related commands:

dspcon

dspcons

Add and configure the slave side of an SPVC (if you are configuring a double-ended SPVC). Record the NSAP address that is returned after the connection is added.

If the slave side of the connection is on the MPSM card, see the "Configuring the Slave Side of SPVCs" section.

If the slave side of the connection is on a non-MPSM card, refer to the documentation for that card.

Step 13

getpcrfromcir

Related commands:

dspcon

If you are adding a connection to an ATM card (such as an AXSM card), you must obtain the peak cell rate.

You can calculate the peak cell rate (PCR value) from the CIR you set with the addcon command's <cir> parameter in step 12.

Note Enter the dspcon <ifNum> <dlci> command to view a connection's PCR, SCR, and MCR.

Step 14

cc

or

username

<password>

cc

Start a configuration session with the card that will host the master end of the connection. If it is not the same card:

•cc to the slot

•Log in to the remote node and cc to the slot

Step 15

addcon

Related commands:

dspcon

dspcons

Add, configure, and connect the master side of an SPVC on the other card. Use the NSAP address and cell rates (PCR, SCR, and MBS) from the slave connection, as appropriate for the service type.

If the master side of the connection is on the MPSM card, see the "Configuring the Master Side of SPVCs" section that appears later in this chapter.

If the master side of the connection is on a non-MPSM card, refer to the documentation for that card.

Note You can obtain the peak cell rate (PCR value) from the CIR you set with the addcon command's <cir> parameter in step 12.

•For additional details about configuring SPVCs on AXSM cards, see the Cisco ATM Services (AXSM) Software Configuration Guide, Release 5.

•For additional details about configuring SPVCs on PXM1E cards, see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

•For additional details about configuring SPVCs on PXM1 cards, see the MGX PXM Software Configuration Guide.

•For additional details about configuring SPVCs on BXM cards, see the BPX 8600 Series Installation and Configuration documentation.

•For additional details about configuring SPVCs on RPM cards, see the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 or the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1.

Frame Relay Configuration Procedures

This section describes the following Frame Relay concepts and general configuration procedures:

•Provisioning Frame Relay Ports

•Partitioning Port Resources Between Controllers

•Selecting the Port Signaling Protocol

•Provisioning and Managing SPVCs

General Information

To do the procedures in this chapter you must start a CLI session on the appropriate MPSM card by logging in with a username and password with GROUP 1 privileges or higher. For detailed information about usernames, passwords, and logging into the CLI, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

The descriptions and procedures in this chapter operate in the Frame Relay Service CLI context. See "MPSM-T3E3-155 and MPSM-16-T1E1 Command Reference" for detailed descriptions about the MPSM-T3E3-155 and MPSM-16-T1E1 Frame Relay service commands and parameters.

See Table 1-2 in "Introduction" for a list of the MPSM-T3E3-155 and MPSM-16-T1E1 model numbers, back cards, and the number of possible connections.

Some of the procedures in this section use PXM commands and PNNI commands. Refer to the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 5 for descriptions of the PXM and PNNI commands and parameters.

For more information on port signaling, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.

Provisioning Frame Relay Ports

On an MPSM card, a logical port is also called a virtual interface and is represented by the ifNum variable. The cards can have the following types of Frame Relay interfaces:

•Frame Relay —This is a port that sends and receives standard Frame Relay frames as defined by ITU-T Q.922. Multiple virtual circuits (VCs) can terminate on one Frame Relay port and are differentiated by their data-link connection identifiers (DLCIs).

•FrameForwarding—This is a port that sends and receives frame-based traffic that is similar to Frame Relay frames such as HDLC, SDLC, and X.25 over Frame Relay interfaces. You can transport any protocol across an ATM network, as long as it supports the HDLC, SDLC, or X.25 format. Application examples include routers interconnected through PPP, mainframes or hosts connected by X.25/HDLC, SNA/SDLC links, and video CODECs that use a frame-based protocol. Frame Forwarding is often used for the aggregation of point-to-point (PPP) traffic into an ATM network, then exiting the ATM network through an ATM interface over multiple VCs into routers supporting PPP over ATM. Frame Forwarding features include:

–No translation or mapping is attempted between the frame header bits and ATM layer EFCI and CLP bits. Because the port is unable to read the address and control information in the frame, all traffic must be forwarded to one destination frame forwarding port.

–Only one frame forwarding VC is allowed per port.

–If a connection is set up, all frames are routed to and from that connection, otherwise the frame is discarded.

–One set of Frame Relay traffic access parameters (for example, CIR) is configured for the logical port in frame forwarding mode. All arriving frames are treated as if they arrived without a set DE bit. If the frame is determined to exceed committed rate (exceeding CIR), the CLP of all cells associated with that frame is set to indicate low priority. If the frame exceeds the total rate allowed for committed and uncommitted traffic, the frame is discarded.

–Support for PPP encapsulation over AAL5 and frame is based on RFC 1483 and RFC 1490.

Preparing to Add Frame Relay Ports

Before you can add Frame Relay ports, you must perform the following tasks:

•Bring up (activate) and configure the physical lines, for example the line payload type. See the "Setting Up Lines" section in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,"

•Channelize SONET, SDH, and DS3 lines into paths. See the "Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines" in "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication,"

Bringing up a line or path establishes physical layer connectivity between two network devices. When you add a Frame Relay port to a line or path, you enable Frame Relay communication by means of that line.

Adding Frame Relay Ports

To add a Frame Relay port to a line or path, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Enter the cc command to start a management session with the active MPSM-T3E3-155 card on which you want to add a port.

Step 3 Identify the line or path number on which you will add the port.

If you are adding a port to a line, enter the dsplns command to determine the line number on which to add the Frame Relay port, as shown in the following MPSM-16-T1E1 example.
M8850_SF.27.MPSM16T1E1[FR].a > dsplns
  Line Line      Line      Line      Length     Valid    Alarm
  Num  State     Type      Lpbk      (meters)   Intvls   State
  ---- ----- ----------- ----------- -------- ---------- -------
   1.1    Up     dsx1ESF      NoLoop        1         96 Clear
   1.2    Up     dsx1ESF      NoLoop        1         96 Clear
   1.3    Up     dsx1ESF      NoLoop        1         96 Clear
   1.4    Up     dsx1ESF      NoLoop        1         96 Clear
   1.5    Up     dsx1ESF      NoLoop        1         96 Clear
   1.6    Up     dsx1ESF      NoLoop        1         96 Clear
   1.7  Down     dsx1ESF      NoLoop        1          0 Clear
   1.8    Up     dsx1ESF      NoLoop        1         96 Clear
   ...
If you are adding a port to a path, enter the dsppaths command to determine the path number on which to add the Frame Relay port. The following MPSM-T3E3-155 example shows the DS1 paths previously configured on line 1.1.1. The first two paths are dedicated to a Multilink Frame Relay bundle, but the third one is available for Frame Relay.
M8850_SF.9.MPSM155[FR].a > dsppaths -ds1
   Path       Path   Admin     DS1         Path    Alarm    Oper     Path      
              Type   Status    Type        Lpbk    Status   State    Service   
 ----------- ----- -------- ----------- -------- -------- -------- ------------
    1.1.1:1   ds1       Up      dsx1ESF   NoLoop    Clear       Up          mfr
    1.1.1:2   ds1       Up      dsx1ESF   NoLoop    Clear       Up          mfr
    1.1.1:3   ds1       Up      dsx1ESF   NoLoop    Clear       Up  unspecified
    1.1.1:4   ds1     Down      dsx1ESF   NoLoop  Unknown     Down      invalid
    1.1.1:5   ds1     Down      dsx1ESF   NoLoop  Unknown     Down      invalid
    1.1.1:6   ds1     Down      dsx1ESF   NoLoop  Unknown     Down      invalid
    1.1.1:7   ds1     Down      dsx1ESF   NoLoop  Unknown     Down      invalid
    1.1.1:8   ds1     Down      dsx1ESF   NoLoop  Unknown     Down      invalid
    ...
Note You cannot add a port directly on a SONET or SDH line; you must channelize it first.

Step 4 Verify that the Line State, or Admin Status is up (active). If necessary, use the upln or uppath commands to bring up the line or path.

Step 5 Verify that the line/path and port number you want to use is not already configured. To display a list of the configured ports on the card, enter the dspports command.

The dspports command shows the number of all existing ports in the ifNum (interface number) column. When you add a port, you must specify a unique port number on the card. For example, if port number 2 is assigned to line 1.1 (bay 1, line 1), you cannot use port 2 on any other line on that card.

Step 6 Enter the addport command as follows to add a Frame Relay port to an active line or path.
M8850_SF.9.MPSM155[FR].a > addport <ifNum> <path> <portType> <sctId> 
[-dlciLen <dlciLen>] [-flags <portFlagsBetweenFrames>] [-rat <PortEqueueServiceRatio>] 
[-csum <checksum>] [-oversub <overSubscribeEnable>] [-lmiSig <lmiSigType>] 
[-asynUpdt <updateType>] [-elmi <elmiState>] [-segLmi <segLmiStatus>] 
[-t391 <t391Value>] [-t392 <t392Value>] [-n391 <n391Value>]  
[-n392 <n392Value>] [-n393 <n393Value>]  
[-ds0speed <ds0speed>] [-ds0beg <ds0beg>] [-ds0num <ds0num>]  
[-fragEnable <fragEnable>] [-fragSize <fragSize>] [-hdlcinv <hdlcinv>]
Table 4-2 lists and describes the keywords and arguments for adding a logical port to a physical line by means of the addport command.

Table 4-2 Arguments for the addport Command

Argument

Description

ifNum

Specifies the interface number (port number) of the port you are adding.

•MPSM-16-T1E1 range: 4-499

•MPSM-T3E3-155 range: 4-1003

Note Port numbers 1 through 3 are reserved for broadband Frame Relay ports.

path_num

Identifies the line or path on which to add the port:

•DS1/E1 or DS3/E3 line: bay.line[:ds1/e1]

•DS3 payload: bay.line[.sts]:[ds1]

•VT payload: bay.line[.sts]:[vtg.vt]

•VT structured: bay.line[.sts]:[tug3.vtg.vt]

where: bay=1, line=1-3, sts=0-3, ds1=1-28,
tug3=1-3, vtg=1-7, vt=1-4(VT15) or 1-3(VT2)

Note Use the dsppaths command to see the path numbers for all available paths. Use the dsplns command to see line numbers for all available lines.

Note On a BNC-3-T3 or BNC-3-E3 back card, you can add a port on a physical line, or on a path. On an SFP-2-155 and the SMB-2-155-EL OC3 back card, you can add a port on a path only.

portType

Specifies the type of port:

•1 = Frame Relay Service

•3 = Frame Forward

sctId

Specifies the number of the Service class template (SCT) for the port:

Range: 0-255

Default: 0

-dlciLen

Specifies the DLCI header length:

•1 = Two-byte DLCI header

•2 = Four-byte DLC header (Broadband ports only)

-flags

Specifies the flags between frames:

•1 = 1 flag

•2 = 2 flags

•3 = 4 flags

•4 = 8 flags

•5 = 16 flags

•6 = 32 flags

•7 = 64 flags

•8 = 128 flags

-rat

This keyword and argument defines the egress service ratio between the high priority and the low priority queues.

Enter the keyword followed by a number that indicates the egress service ratio, in the range from 1 to 15.

•Enter 1 to indicate that no service ratio is configured. In this case, bandwidth is allocated to both the high priority and the low priority queues on demand, which means that traffic is dynamically allocated on a first-come, first-serve basis.

•The default setting is 1. In this case, the traffic of the CBR and rt-VBR service categories is allocated to the high priority queue, while the traffic of the nrt-VBR, ABR, and UBR service categories is allocated to the low priority queue.

-csum

Checksum type indicator:

•1 = crc16

•2 = crc32

-oversub

Oversubscription indicator:

•1 = enable

•2 = disable

-lmiSig

LMI signaling type indicator:

•2 = No Signaling

•3 = StrataLMI

•4 = AnnexAUNI

•5 = AnnexDUNI

•6 = AnnexANNI

•7 = AnnexDNNI

-asynUpdt

Enables or disables asynchronous updates. Asynchronous updates are an extension to the LMI protocol that notify the user immediately of changes in PVC and Multicast status. Before enabling this feature, make sure that any DTE equipment you are connected to supports asynchronous updates from the network.

Asynchronous update control:

•1 = Disable both Asynchronous Status Updates and Unsolicited Full Status

•2 = Enable Asynchronous Status Updates

•3 = Enable Unsolicited Full Status

•4 = Enable Asynchronous Status Updates and Unsolicited Full Status

-elmi

Enable or disable enhanced LMI. Enhanced LMI enables the automatic exchange of Frame Relay QoS parameter information between the DTE and DCE. When enabled on both the DTE and the MPSM port, this allows the DTE device to learn QoS parameters from the frame relay port and use them for traffic shaping, configuration, or management purposes. Enter a number to enable/disable enhanced LMI on the port.

•1 = enable

•2 = disable

-segLmi

Segmented LMI control:

•1 = enable

•2 = disable

-t391

T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends Status Enquiry messages to the network (DCE) every T391 seconds. An error is recorded if a Status message is not received within T391 seconds. The T391 counter always applies to the user equipment. It applies to the user and network if NNI bidirectional polling is present. Range 5 to 30.

-t392

T392 timer. This is the Polling Verification timer. The network (DCE) expects Status Enquiry messages from the user (DTE) every T392 seconds. If the network does not receive a Status Enquiry message from the user within T392 seconds and the timer expires, then the network records a missing Status Enquiry message by incrementing the N392 counter. This timer value must be set greater than the T391 timer. The T392 timer always applies to the network. It applies to the network and user if NNI bidirectional polling is present. Range 5 to 30.

-n391

N391 counter. This setting establishes the Full Status (status of all PVCs) polling cycle. The user (DTE) sends a Full Report Status Enquiry to the network (DCE) every N391 polls. The N391 counter always applies to the user equipment. It applies to the user and network if NNI bidirectional polling is present. Range1 to 255. Default: 6

-n392

N392 counter. This setting specifies the UNI/NNI error threshold. This is the number of errors during N393 events that will cause an error condition. This counter should be less than or equal to the N393 counter. This counter can apply to both the user (DTE) and the network (DCE). Range 1to 10.

-n393

N393 counter. This setting is the monitored UNI/NNI events count, which must be greater than the N392 counter. N392 errors during N393 events will cause an error condition. If the N393 counter is set to a value much less than the N391 counter, the port could go in and out of an error condition without notification to either the user equipment or the network. This counter can apply to both the user (DTE) and the network (DCE). The value of this parameter should be greater than that for the -n392 parameter. Range: 1-10.

-ds0speed

Specifies the speed of the DS0 channel:

•1 = 56 Kbps

•2 = 64 Kbps.

-ds0beg

Specifies the beginning DS0 number:

•T1 paths: 1- 24

•E1MF and E1CRCMF paths: 2-16, 18-32 (17 is reserved)

•other E1 paths = 2-32

-ds0num

Specifies the number DS0 time slots that will follow the beginning DS0:

•T1 paths: 1- 24

•E1MF and E1CRCMF paths: 1-30

•other E1 paths: 1-31

-fragEnable

Enables or disables fragmentation on the port.

•1 = enable

•2 = disable

-fragSize

Specifies the size of the fragments in bytes:

•40

•64

•128

•256

•512

-hdlcinv

Enables/disables HDLC inversion on the port:

•1 = enable

•2 = disable

In the following example, the user adds Frame Relay port 113 to DS1 path 1.1.1:3, using the default SCT:
M8850_SF.9.MPSM155[FR].a > addport 113 1.1.1:3 1 0
Step 7 Enter the dspports command to verify that the port you added appears in the ifNum (interface number) column. The following example confirms the addition of port 113:
M8850_SF.9.MPSM155[FR].a > dspports
ESR: Egress queue Service Ratio                                                
                                SCT DS0    Port                 E   FRF        
If   Line/Path   Admn Oper if   In  Start  Speed      Signaling LMI 12   MFR   
Num  Num         Stat Stat Type Use (Num)  kbps   ESR Type      St  Frg Bundle   
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------ 
113     1.1.1:3   Up   Up   FR   0  1(24)   1536   1      None Off Off N/A
Step 8 To view detailed configuration information for the port, enter the dspport <ifNum> command. The following example shows detailed information for Frame Relay port 113:
M8850_SF.9.MPSM155[FR].a > dspport 113
  Interface Number                 : 113
  Line Number                      : 1.1.1:3
  MFR bundle Number                : N/A
  DS0 Speed                        : unused
  DS0 Configuration Bit Map        : 1(24)
  Admin State                      : Up     
  Operational State                : Up            
  Port State                       : Active
  Port Signaling State             : No Signaling Failure
  Interface Type                   : Frame Relay
  SCT Id                           : 0/0 =Def
  Frame Header Length              : Two Bytes
  Flags Between Frames             : 1
  Equeue Service Ratio             : 1
  Port Speed                       : 1536 kbps
  Checksum type                    : crc16
  Over-subscription                : Disabled
  Signaling Protocol Type          : None
  Enhanced LMI                     : Disabled
  FRF 1.2 Support                  : Disabled
  Asynchronous Updates             : Disabled
  T391 Link Integrity Timer        : 10 secs
Type <CR> to continue, Q<CR> to stop: 
  T392 Polling Verification Timer  : 15 secs
  N391 Full Status Polling Counter : 6
  N392 Error Threshold             : 3
  N393 Monitored Event Count       : 4
  FRF.12 Fragmentation             : Disabled
  FRF.12 Fragment Size             : 64 Bytes
  Port HDLC Frame Inversion        : Disabled
  Number of Partitions             : 1
  Number of SPVC                   : 0
Tip To change the port configuration, enter the cnfport command. To delete the port configuration, enter the delport command. You can also activate or deactivate a port using the upport and dnport commands. For more information about these commands, refer to "MPSM-T3E3-155 and MPSM-16-T1E1 Command Reference."

Partitioning Port Resources Between Controllers

After you add a Frame Relay port, you can define how the port resources are to be used by the PNNI controller. Although the Cisco MGX 8850/8830 software allows you to distribute port resources to multiple controllers, the PNNI controller is the only controller supported on Frame Relay ports in Release 5 of the MPSM-T3E3-155. Therefore, you assign all resources to the PNNI controller. These resources include the following:

•Range of DLCI values

•Maximum percent of bandwidth in the ingress and egress directions

•Maximum number of connections

•Minimum and Maximum DLCI values

You configure partitions to control how these connection resources are distributed among the switch, card, and ports within the Cisco MGX 8850/8830 switch. Without these partitions, two or three busy ports could consume all of the available connections, thereby disabling communication on all other ports.

A partition is automatically added when you add a port. This new partition has the same number as the port. You can change the resource partition configuration with the cnfpart command.

Note To create additional resource partitions for a port, use the addpart command. The partition ID you use when you create the resource partition can be any number in the range from 1 to 255. After you assign a partition ID to any resource partition on the card, you must use the same partition ID for all other resource partitions on that card. Consider using 2 for the partition ID so that it matches the controller ID. If you do likewise on the other cards in your switch, there will be less confusion in managing partitions on different types of cards.

To configure a port resource partition, use the following procedure:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Enter the dspports command to display a list of all logical ports. Determine the port number for which you want to configure resources.

Note All port numbers appear in the ifNum (interface number) column. The partition number is the same as the interface number for automatically-added partitions.
M8850_SF.9.MPSM155[FR].a > dspports
ESR: Egress queue Service Ratio                                                
                                SCT DS0    Port                 E   FRF        
If   Line/Path   Admn Oper if   In  Start  Speed      Signaling LMI 12   MFR   
Num  Num         Stat Stat Type Use (Num)  kbps   ESR Type      St  Frg Bundle  
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------ 
 110         N/A   Up   Up   FR   0    N/A   3065   1      None Off Off   1
 113     1.1.1:3   Up   Up   FR   0  1(24)   1536   1      None Off Off N/A
Step 3 Enter the cnfpart command as follows to create a resource partition.
M8850_SF.9.MPSM155[FR].a > cnfpart <ifNum> <ctrlNum> [-lcn <available connections>] 
[-dlcimin <minDlci>] [-dlcimax <maxDlci>] [-ibw <ingPctBw>] [-ebw <egrPctBw>]
Table 4-3 describes the arguments for the cnfpart command.

Table 4-3 Arguments for the cnfpart Command

Argument

Description

ifNum

Specifies the interface number (partition number) of the partition to add.

•MPSM-16-T1E1 range: 1-499

•MPSM-T3E3-155 range: 1-1003

Identifies the logical interface to which you want to add a resource partition.

Note Use the dspparts command in the Frame Relay CLI context to see all active partitions.

ctrlNum

Specifies a network controller protocol. Enter 2 to specify the PNNI controller.

Note Release 5 of the MPSM-T3E3-155 supports the PNNI controller (option 2) only. Options 1 (TAG switching) and 3 (MPLS) are not supported.

-lcn

Maximum number of connections.

•MPSM-16-T1E1 range: 0-2000

•MPSM-T3E3-155 range: 0-4000

-dlcimin

Minimum DLCI value.

•2-byte header range: 0-1023.

•4-byte header range: 0-8355840, in multiples of 32768.

For example, you can enter one of the following numbers as the minimum DLCI value, or any other number that is a multiple of 32768:
0 = (0 x 32768)
163840 = (5 x 32768)
8355840 = (255 x 32768)

Unless your provisioning plan calls for a specific range of DLCI values on a port or card, specify the minimum DLCI value as 0.

-dlcimax

Maximum DLCI value.

•2-byte header range: 0-1023.

•4-byte header range: 32767-8355840, in multiples of 32768, minus 1.

For example, you can enter one of the following numbers as the maximum DLCI value, or any other number that is a multiple of 32768 minus l:
32767 = (32768 * 1)-1
163839 = (32768 * 5)-1
6520831 = (32768 * 199)-1

Unless your provisioning plan calls for a specific range of DLCI value on a port or card, specify the maximum DLCI value as 8388607.

-ibw

Maximum ingress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.

-ebw

Maximum egress port bandwidth percentage for the controller type specified with the ctrlrNum argument, in the range 0-100 percent.

The following example changes the maximum number of connections to 1000:
M8850_SF.9.MPSM155[FR].a > cnfpart 113 2 -lcn 1000
Step 4 Enter the dsppart <ifNum> <ctrlrNum> command to display the configuration of a particular partition. Replace <ifNum> with the interface number, and replace <ctrlrNum> with the controller number, as shown in the following example:
The following example shows the output from a dsppart command:
M8850_SF.9.MPSM155[FR].a > dsppart 113 2
  Interface Number               : 113
  Partition Id                   : pnni        Number of SPVC: 0
  Controller Id                  : 2      
  Available LCNs                 : 1000   
  Min DLCI                       : 0
  Max DLCI                       : 1023
  Ingress Percentage Bandwidth   : 100    
  Egress Percentage Bandwidth    : 100 
Selecting the Port Signaling Protocol

The default signaling protocol for new Frame Relay ports is none.

To change the signaling protocol from the default setting, perform the following steps:

Step 1 Establish a configuration session with the active PXM using a username with Group1 privileges or higher.

Step 2 Enter the dsppnports command as follows to display a list of PNNI ports available for configuration.
M8850_NY.7.PXM45.a > dsppnports
Summary of total connections
(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)
Type   #Svcc:   #Svpc:   #SpvcD:  #SpvpD:  #SpvcR:  #SpvpR:  #Ctrl #Total:
p2p:   0        0        30       0        0        0        0        30     
p2mp:  0        0        0        0        0        0        0        0      
    Total(User cons) =      30/50000,   Total(Ctrl cons) = 0      
            Total=30      
Summary of total SPVC endpoints
(P=Persistent, NP=Non-Persistent)
Type   #SpvcR-P  #SpvcR-NP #SpvpR-P  #SpvpR-NP #SpvcD   #SpvpD   Total
p2p:   0         0         0         0         60        0         60     
p2mp:  0         0         0         0         0         0         0      
                         Total=60     
Summary of total active SVC/SPVC intermediate endpoints
Type   #Svcc    #Svpc     #SpvcR   #SpvpR   Total
p2p:   0         0         0         0         0      
p2mp:  0         0         0         0         0      
                         Total=0      
Type <CR> to continue, Q<CR> to stop: 
DSPPNPORTS          EndPoint Grand Total =     60/100000 
Per-port status summary
PortId      LogicalId    IF status      Admin status  ILMI state        #Conns
7.35         17251107    up             up            NotApplicable     0       
7.36         17251108    up             up            NotApplicable     0       
7.37         17251109    up             up            NotApplicable     0       
7.38         17251110    up             up            NotApplicable     0       
11:1.1:1     17504257    provisioning   up            NotApplicable     5       
11:1.2:2     17504258    provisioning   up            NotApplicable     5       
11:1.3:3     17504259    provisioning   up            NotApplicable     5       
11:1.4:4     17504260    provisioning   up            NotApplicable     5       
11:1.5:5     17504261    provisioning   up            NotApplicable     5       
Type <CR> to continue, Q<CR> to stop: 
PortId      LogicalId    IF status      Admin status  ILMI state        #Conns
11:1.6:6     17504262    provisioning   up            NotApplicable     5       
11:2.1:7     17504263    provisioning   up            NotApplicable     5       
11:2.2:8     17504264    provisioning   up            NotApplicable     5       
11:2.3:9     17504265    provisioning   up            NotApplicable     5       
11:2.4:10    17504266    provisioning   up            NotApplicable     5       
11:2.5:11    17504267    provisioning   up            NotApplicable     5       
11:2.6:12    17504268    provisioning   up            NotApplicable     5       
M8850_NY.7.PXM45.a > 
Step 3