Provisioning Frame Relay Services

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

Partitioning Port Resources Between Controllers

Selecting the Port Signaling Protocol

Provisioning and Managing 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 Chapter 2, "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.

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 8800/8900 Series Configuration Guide, Release 5.2.

•Set up lines and/or paths for the Frame Relay service and its connections, as described in Chapter 2, "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 Chapter 7, "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 8800/8900 Series Configuration Guide, Release 5.2.

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 Chapter 2, "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 Chapter 2, "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 8800/8900 Series Configuration Guide, Release 5.2.

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 Chapter 2, "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 Chapter 2, "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 8800/8900 Series Configuration Guide, Release 5.2.

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 Chapter 2, "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 Chapter 2, "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 8800/8900 Series Configuration Guide, Release 5.2.

•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 5.2 or the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 5.2.

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 8800/8900 Series Configuration Guide, Release 5.2.

The descriptions and procedures in this chapter operate in the Frame Relay Service CLI context. See Chapter 7, "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 Chapter 1, "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 8800/8900 Series Command Reference, Release 5.2 for descriptions of the PXM and PNNI commands and parameters.

For more information on port signaling, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

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 Chapter 2, "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 Chapter 2, "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 Chapter 7, "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 Enter the dnpnport <portid> command to bring down the port you want to configure. Replace the <portid> argument in the dnpnport command using the format slot[:bay].line[:ifNum]. The port identification arguments are listed and described in Table 4-4.

Note A port is automatically brought up when you add it. Therefore, you must bring down the port before you can change the signaling protocol for that port.

Table 4-4 Port Identification Arguments

Argument

Description

slot

Enter the slot number for the card that hosts the port you are configuring.

bay

Replace the <bay> argument with the value 1 if the line is connected to a back card in the upper bay; replace the <bay> argument with the value 2 if the line is connected to a back card in the lower bay. Note that the bay number is always 1.

line

Replace the <line> argument with the number that corresponds to the back card port to which the line is connected.

ifNum

An ATM port is also called an interface. Enter a number from 1 to 60 to identify this interface.

The interface number must be unique on the card to which it is assigned. An ATM port is defined by its slot, bay, line, and interface number. You need not enter a slot number during port configuration because you identify the slot number when you select the card.

In the following example, the user brings down port 13.5:

M8850_NY.7.PXM.a > dnpnport 13.5

Step 4 Enter the dsppnports command as shown in the following example to confirm that the specified port is down.

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: #Total:
p2p: 0 0 17 0 0 0 17
p2mp: 0 0 0 0 0 0 0

Total= 17/50000

Summary of total SPVC endpoints
(P=Persistent, NP=Non-Persistent)
Type #SpvcR-P #SpvcR-NP #SpvpR-P #SpvpR-NP #SpvcD #SpvpD Total
p2p: 1 0 0 0 34 0 35
p2mp: 0 0 0 0 0 0 0
Total=35

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

EndPoint Grand Total = 35/100000

Type <CR> to continue, Q<CR> to stop:
DSPPNPORTSPer-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

4:1.1:1 17045505 down up NotApplicable 11

4:1.2:1 17045505 provisioning up NotApplicable 0

4:1.2:2 17045506 up up NotApplicable 11

Step 5 Enter the cnfpnportsig command as follows to define the signaling protocol for the specified port.

M8850_NY.7.PXM45.a > cnfpnportsig <portid> -univer none

Table 4-4 describes the elements of the <portid> argument.

Tip With some CLI commands, you can refer to a port using only the interface number. Other commands require that you enter a complete port identification number, which includes the slot, bay, line, and interface numbers. When entering commands at the PXM card prompt, you always need to specify the complete port identification number. When entering commands at the card prompt, you need enter only the interface number, because the interface number on the card is unique.

In the following example, the user configures an NNI port to use the PNNI Version 1.0 signaling protocol.

M8850_NY.7.PXM45.a > cnfpnportsig 4:1.1:1 -univer none

Step 6 Enter the uppnport command as follows to bring up the port you just configured.

M8850_NY.7.PXM45.a > uppnport <portid>

Replace the <portid> argument using the format slot:bay.line:ifNum.

Table 4-4 describes the elements of the <portid> argument.

Step 7 Enter the dsppnports command to verify that the port you brought up in Step 6 is in the "up" state in the Admin_st column.

Step 8 Enter the dsppnport <portid> command as follows to display the configuration of a specific PNNI port. Replace the <portid> argument using the format slot:bay.line:ifNum.

Note Table 4-4 describes the elements of the <portid> argument.

M8850_NY.7.PXM45.a > dsppnport 4:1.2:2

Port: 4:1.2:2 Logical ID: 17045506
IF status: up Admin Status: up
UCSM: disable SVC Routing Pri: 8
Auto-config: disable Addrs-reg: disable
IF-side: network IF-type: uni
UniType: private Version: none
PassAlongCapab: n/a
Input filter: 0 Output filter: 0
minSvccVpi: 0 maxSvccVpi: 0
minSvccVci: 100 maxSvccVci: 32867
minSvpcVpi: 1 maxSvpcVpi: 0

(P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)
#Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct:
p2p : 11 0 11 0 0 0
p2mp: 0 0 0 0 0 0
#Svcc: #Svpc: Total:
p2p : 0 0 11
p2mp: 0 0 0
Total: 11
Provisioning and Managing SPVCs

A soft permanent virtual circuit (SPVC), a variant of a permanent virtual circuit (PVC), can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. Each SPVC has a master and slave endpoint. The master endpoint of the SPVC is responsible for routing and rerouting functions. The slave endpoint of the SPVC is responsible for responding to requests from the master endpoint during connection setup and rerouting. Both endpoints are configured on the switch or switches to which the Frame Relay CPE connects. Such endpoints can be in the same switch or in different switches.

Both PVCs and SPVCs are full-time connections. A PVC uses a predefined circuit path that fails if the path is interrupted for any reason. In contrast to a PVC, if a link along an SPVC path fails, or if that link cannot provide the required bandwidth, the PNNI protocol reroutes that link to maintain the connection and supply the necessary bandwidth for the connection.

The master/slave relationship exists for each SPVC and applies only to that SPVC. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another SPVC with the master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs among network nodes to distribute route processing functions.

Preparing to Add SPVCs

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

1. The switch must have a network controller (see the addcontroller command in the Cisco MGX 8800/8900 Series Command Reference, Release 5.2.

2. A physical line must be active. Use the upln command or the Cisco WAN Manager application to bring up a line.

3. A path must be active. Use the uppath command or the Cisco WAN Manager application to bring up a path.

4. At least one logical port must exist on the active path. Use the addport command or the Cisco WAN Manager application to create the port. If necessary, modify the port through cnfport.

5. At least one resource partition must exist on the logical port. A resource partition is automatically added when you add a port. Use cnfpart command to modify the configuration for the existing resource partition, or delete the existing partition and enter the addpart command to create a new resource partition on the port. The resource partition should be associated with the controller added in Step 1.

You can create two types of SPVCs:

•Single-ended SPVCs

•Double-ended SPVCs

Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature to work correctly, the destination endpoint must support single-ended SPVCs.

Note In this software release for the Cisco MGX 8850/8830, the card supports only the origination of single-ended SPVCs. This means that you can configure master endpoints for single-ended SPVCs that terminate on another card.

Double-ended SPVCs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration.

The following sections describe how to configure double-ended connections that have separate slave and master SPVC connections.

Configuring the Slave Side of SPVCs

If you wish to configure a double-ended SPVC, you must first configure the slave endpoint for the connection. If you are configuring a single-ended SPVC, you need not configure a slave endpoint.

To configure the slave side of a double-ended SPVC, perform the following steps:

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

Step 2 Enter the cc <slotnumber> command as follows to start a management session with the card that hosts the slave side of the SPVC connection.

mgx8850a.7.PXM45.a > cc <slotnumber>

Replace <slotnumber> with the number of the slot in which the MPSM card is installed.

Step 3 Enter the dspports command to identify the port to connect. In the following example, port 113 is the one to host the slave endpoint.

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 4 Enter the addcon command as follows to define the slave side of the SPVC:

mgx8850a.10.MPSM-155[FR] .a > addcon <ifNum> <dlci> <chanType> <serviceType> <mastership> <cir> [-slave <value>] [-slavepersflag <slavepers>] [-eir <zeroCirEir>] [-bc <Burst Commit>] [-be <Burst Excess>] [-detag <DE Tagging Enable>] [-igde <Ignore Incoming DE>] [-fecnmap <FECN map>] [-demap <DE to CLP map>] [-clpmap <CLP to DE map>] [-eqsel <Egress Q Select>] [-ingut <Ingress Perc Util>] [-egut <Egress Perc Util>] [-egrat <Egress Service Rate>] [-rtngprio <Routing Priority>] [-upc <UPC Cnfg>] [-lpcr <local-remote PCR>] [-rpcr <remote-local PCR>] [-lscr <local-remote SCR>] [-rscr <remote-local SCR>] [-lmcr <local-remote MCR>] [-rmcr <remote-local MCR>] [-prefrte <routeId>] [-directrte <yes|no>] [-rmbs<remote MBS>] [-cc <OAM CC Cnfg>]

Table 4-5 describes the keywords and arguments for the addcon command. The local and remote terms used in this table refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an optional argument, a default value for that argument is used for SPVC configuration.

Caution After you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in the document entitled Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Table 4-5 Arguments for the addcon Command

Argument

Description

ifNum

Interface number (port number) of the port to connect.

•MPSM-16-T1E1 range: 1-499

•MPSM-T3E3-155 range: 1-1003

Note Use the dspports command in the Frame Relay CLI context to see the port numbers for all active Frame Relay ports.

dlci

Specifies the Data-Link Connection Identifier.

•2-byte header range: 1-1006 and 1008-1022

•4-byte header range: 1-8257534 and 8257536-8388607

chanType

Specifies the channel type. Enter a number to indicate one of the following channel types:

•1 = frNIW: Frame Relay Network Interworking

•2 = frSIWtransparent: Service Interworking without any SDU translation

•3 = frSIWtranslate: Service Interworking with SDU translation

•5 = frForward: Frame Forwarding

•6 = frNIWReplace: Frame Relay Network Interworking Replace

serviceType

Specifies the service type for the connection. Enter a number to indicate one of the following service types:

•1 = highpriority (use cbr1 at ATM endpoints)

•2 = rtVBR: real-time variable bit rate (use vbr3rt at ATM endpoints)

•3 = nrtVBR: non-real-time variable bit rate (use vbr3rt at ATM endpoints)

•5 = uBR: unspecified bit rate (use ubr at ATM endpoints)

•9 = stdABR: available bit rate (use stdabr at ATM endpoints)

mastership

Controls whether this end of a connection is a master or slave endpoint. Enter a number to indicate the mastership of the endpoint as follows:

•1 = master

•2 = slave

cir

Specifies the CIR for the connection.

•MPSM-T3E3-155 range—T3: 0-44209688, E3_G832: 0-33920000, and E3_G751: 0-33831000 bps.

•MPSM-16-T1E1 range: 0-1984000 bps.

-slave

Identifies the slave endpoint of the connection, in the following format:

slave_nsap_address.vpi.vci

Note This parameter is required when you configure a master endpoint.

-slavepersflag

Controls whether the endpoint is persistent or non-persistent. Enter a number to indicate the endpoint's persistency as follows:

•0 = persistent (default)

•1 = nonpersistent

-eir

Specifies the excess information rate for the connection.

•MPSM-T3E3-155 range—T3: 0-44209688, E3_G832: 0-33920000, and E3_G751: 0-33831000 bps.

•MPSM-16-T1E1 range: 0-1984000 bps.

-bc

Specifies the Burst Commit size for the connection. Range: 0-2097151 bytes

The default Frame Relay value is 5100, and the default Frame Forwarding value is 10300.

-be

Specifies the Burst Excess size for the connection. Range: 0-2097151 bytes

The default Frame Relay value is 5100, and the default Frame Forwarding value is 10300.

-detag

Enables or disables Discard Enable Tagging on the connection. This parameter enables or disables tagging of the DE bit on ingress frames as the result of the policing mechanism. Enter a number to enable or disable DE tagging as follows:

•1 = enable

•2 = disable (default)

-igde

Enables or disables a connection's response to incoming Discard Enable tags. Enter a number to ignore (disable) or accept (enable) incoming DE tags as follows:

•1 = enable

•2 = disable (default)

-fecnmap

Specifies the mapping between FECN and EFCI for this connection. Enter a number to set the configuration of the FECN map as follows:

•1 = mapEFCI

•2 = setEFCIzero (default)

-demap

Specifies the mapping between DE and CLP for this connection. Enter a number to set the DE to CLP mapping, as follows:

•1 = mapCLP (default)

•2 = setCLPzero

•3 = setCLPone

-clpmap

Specifies the mapping between CLP and DE for this connection. Enter a number to set the CLP to DE mapping, as follows:

•1 = mapDE (default)

•2 = setDEzero

•3 = setDEone

•4 = ignoreCLP

-eqsel

Selects the egress queue for this connection. Enter a number to indicate one of the following options:

•1 = highPriority

•2 = lowPriority

•3 = notSupported

The default value depends on the service type.

-ingut

Specifies the ingress percent utilization for this connection. This value controls the bandwidth allocated for the connection and allows you to oversubscribe the network resources. Range: 1-100 percent

Default: 100 percent.

-egut

Specifies egress percent utilization for this connections. This value controls the bandwidth allocated for the connection and allows you to oversubscribe the network resources. Range: 1-100 percent

Default: 100 percent

-egrat

Specifies the egress service rate. This value is used for CAC to determine if the port can support the connection.

•MPSM-T3E3-155 range: 2400-44209688 bps

•MPSM-16-T1E1 range: 2400 and 1984000 bps

-rtngprio

Specifies the routing priority for this connections, in the range 1-15.

Default: 8

-upc

Enables or disables UPC configuration on the connection. Enter a number to enable/disable UPC configuration on the connection, as follows:

•1 = enable (default)

•2 = disable

-lpcr

Specifies the peak cell rate for this connection in the local to remote direction. The PCR of the local and remote endpoints must match to successfully create a connection.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-rpcr

Specifies the peak cell rate for this connection in the remote to local direction. The PCR of the local and remote endpoints must match to successfully create a connection.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-lscr

Specifies the sustainable cell rate for this connection in the local to remote direction. The SCR of the local and remote endpoints must match for variable bit rate connections.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-rscr

Specifies the sustainable cell rate for this connection in the remote to local direction. The SCR of the local and remote endpoints must match for variable bit rate connections.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-lmcr

Specifies the minimum cell rate for available bit rate connections in the local to remote direction.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-rmcr

Specifies the minimum cell rate for available bit rate connections in the remote to local direction.

•MPSM-T3E3-155 range: 10-165787 cps

•MPSM-16-T1E1 range: 10-36064 cps

-prefrte

This option associates a preferred route to the connection. Use this parameter at the master endpoint only. Be sure the route exists before you associate it with the connection because the system does not check it. Use the dspprefs command at the PXM card to display preferred routes.

The following values are valid:

•0: Disassociate a connection from a route (default)

•1-65535: The preferred route id

Note Before you delete the route, disassociate all connections from the route; otherwise, a dangling preferred route path remains. Use the dspcons [-rteid <pref rte id> ] command at the PXM card to display all connections associated with a route.

Note An SPVC can be associated with one preferred route. For an XPVC, you can associate the preferred route with only the SPVC portion of the XPVC.

-directrte

Enables or disables a direct route for this connection. When enabled (yes), the preferred route is the only permissible route for this connection. Should the directed preferred route be unavailable, the connection fails. When disabled (no), the connection tries another alternate route if the preferred route is unavailable.

The values are as follows:

•1 = yes (make the preferred route required)

•0 = no (do not require the connection to take the preferred route)

Default: 0

-rmbs

Specifies the Maximum Burst Size for variable bit rate connections in the remote to local direction. MBS is the maximum number of cells that can burst at the PCR and still be compliant. Range 0-5000000 cells

cc

Operations, administration, and maintenance continuity check (OAM CC):

•1 = enable

•0 = disable (default)

Continuity checking invokes a round trip of an OAM cell simply to confirm that both directions of the connection are intact.

To provision continuity checking, enable this function at both ends of the connection; otherwise, a connection alarm results. When you add a connection and include this parameter, the connection goes into alarm until both ends of the connection are added.

Tip If you omit one or more of the configuration arguments when entering the addcon command, the SPVC connection uses the default values listed in Table 4-5, as appropriate. To override the default value for a given argument, enter the argument with a desired value.

Note Enter the cnfchanstdabr command to configure additional ABR arguments. For more information about the cnfchanstdabr command, refer to Chapter 7, "Command Reference"

In the following example, the addcon command add the slave side of an SPVC connection to Frame Relay port 113, DLCI 200.

M8850_SF.9.MPSM155[FR].a > addcon 113 200 1 1 2 1536000
slave endpoint added successfully
slave endpoint id : 47009181000000000164444B61000001091FFF00.224.200

Step 5 Write down the NSAP address displayed when the addcon command output is successful. You will need the NSAP address to configure the master side of the SPVC connection.

Tip When you set up the master side of the SPVC, you must enter the slave ATM address reported by the addcon command. If you maintain the current session or use the CLI copy command to copy the ATM address now, you can use the CLI paste command to complete the addcon command on the switch that hosts the master side of the SPVC.

Step 6 Enter the dspcons command as follows to verify the addition of the slave side of the SPVC connection. The dspcons command displays all information for the SPVCs.

M8850_SF.9.MPSM155[FR].a > dspcons
record Identifier SrvcType M/S Upld Admn Alarm
------ ---------- -------- --- ---- ---- ---------------------
0 113 0000200 High Priority S 00000001 UP Condn(A bit from n/w)

Step 7 Enter the dspcon command to view connection details.

M8850_SF.9.MPSM155[FR].a > dspcon 113 200
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(S) 47009181000000000164444B61000001091FFF00 224 200
Remote : NSAP Address vpi vci
(M) 0000000000000000000000000000000000000000 0 0
--------------------------------------------------------------------------
Port Number : 113 DLCI : 200
Conn. Type : frNIW Chan Service Type: High Priority
Conn Service Type : cbr1 Egress Queue Type: highPriority
Admn Status : UP Oper Status : FAILED
Slave Persist : N/A Max Cost : N/A
CIR (bps) : 1536000 BC (bytes) : 5100
BE (bytes) : 5100 FECN Config : setEFCIzero
ChanDEtoCLPmap : mapCLP ChanCLPtoDEmap : mapDE
IngrPercentUtil : 100 EgrPercentUtil : 100
EgrSrvRate (bps) : 1536000 ZeroCirEir (bps) : N/A
DE Tagging : DISABLED IgnoreIncomingDE : DISABLED
Pref Rte Id : 0 Directed Route : NO
Upload : 00000001 Routing Priority : 0
OAM CC Config : DISABLED Statistics : ENABLED
Local Loopback : DISABLED UPC : ENABLED
--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop:
Local PCR (cps) : 5760 Remote PCR (cps) : 5760
Local SCR (cps) : N/A Remote SCR (cps) : N/A
Local MCR (cps) : N/A Remote MCR (cps) : N/A
: Remote MBS (cps) : N/A
--------------------------------------------------------------------------
Xmt Abit State : A equal 0 Rcv Abit State : OFF
Xmt ATM State : Not Sending Rcv ATM State : Not Recving
--------------------------------------------------------------------------
E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT
NO YES NO NO NO NO
--------------------------------------------------------------------------

Step 8 Write down the Local PCR, SCR, and MCR values. Depending on the service type, and other factors, you need these values when adding the master endpoint.

Configuring the Master Side of SPVCs

When you add a master connection, the software checks the configuration at the slave end to be sure the remote connection configuration is compatible. If the local and remote configuration parameters are not compatible, the connection is not added. Table 4-6 shows the connection parameters that are checked when you create a connection.

Table 4-6 Connection Parameters that Must Match

Connection Type

Parameters Checked

addcon Keyword

CBR

PCR

-lpcr

VBRrt and VBRnrt

PCR, SCR, MBS

-lpcr, -lscr, and -lmbs

stdABR

PCR and MCR

-lpcr and -lmcr

UBR

PCR

-lpcr

Use the values you previously recorded when adding the slave connection. Setting these parameters when adding the connection is especially important when connection to non-MPSM cards, where the default connection parameters might be different.

To configure the master side of an SPVC, perform the following steps:

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

Step 2 Enter the cc <slotnumber> command as follows to start a management session with the MPSM card that hosts the master side of the SPVC connection.

mgx8850a.7.PXM45.a > cc <slotnumber>

Replace <slotnumber> with the number of the slot in which the MPSM card is installed.

Step 3 Enter the addcon command as follows to define the master side of the SPVC connection.

mgx8850a.10.MPSM-155[FR] .a > addcon <ifNum> <dlci> <chanType> <serviceType> <mastership> <cir> [-slave <value>] [-slavepersflag <slavepers>] [-eir <zeroCirEir>] [-bc <Burst Commit>] [-be <Burst Excess>] [-detag <DE Tagging Enable>] [-igde <Ignore Incoming DE>] [-fecnmap <FECN map>] [-demap <DE to CLP map>] [-clpmap <CLP to DE map>] [-eqsel <Egress Q Select>] [-ingut <Ingress Perc Util>] [-egut <Egress Perc Util>] [-egrat <Egress Service Rate>] [-rtngprio <Routing Priority>] [-upc <UPC Cnfg>] [-lpcr <local-remote PCR>] [-rpcr <remote-local PCR>] [-lscr <local-remote SCR>] [-rscr <remote-local SCR>] [-lmcr <local-remote MCR>] [-rmcr <remote-local MCR>] [-prefrte <routeId>] [-directrte <yes|no>] [-rmbs<remote MBS>] [-cc <OAM CC Cnfg>]

Table 4-5 lists and describes the keywords and arguments for the addcon command.

Tip If you omit one or more of the optional arguments when entering the addcon command, the connection uses the default values listed in Table 4-5. To override the default value for a given argument, enter the argument with the desired value.

In the following example, the user adds the master side of a double-ended SPVC, specifying the slave NSAP address and slave PCR. Use the values recorded when adding the slave endpoint.

M8830_SF.6.MPSM155[FR].a > addcon 113 300 1 1 1 1536000 -slave 47009181000000000164444B61000001091FFF00.224.200 -lpcr 5760
master endpoint added successfully
master endpoint id : 47009181000000003094095DF6000001061FFF00.224.300

Step 4 Enter the dspcons command as follows to verify the master-side of the new SPVC connection.

M8830_SF.6.MPSM155[FR].a > dspcons
record Identifier SrvcType M/S Upld Admn Alarm
------ ---------- -------- --- ---- ---- ---------------------
0 113 0000300 High Priority M 00000001 UP None

The dspcons command displays all connections for the MPSM card.

Step 5 Enter the dspcon command as follows to display the configuration information for a specific SPVC.

M8850_NY.13.MPSM155[FR].a> dspcon <ifNum> <dlci>

Replace the <ifNum> argument with the interface or port number of the card. The <dlci> argument (see Table 4-5) establishes the DLCI for the SPVC endpoint.

The following is sample output from the dspcon command.

M8830_SF.6.MPSM155[FR].a > dspcon 113 300
--------------------------------------------------------------------------
Local : NSAP Address vpi vci
(M) 47009181000000003094095DF6000001061FFF00 224 300
Remote : NSAP Address vpi vci
(S) 47009181000000000164444B61000001091FFF00 224 200
--------------------------------------------------------------------------
Port Number : 113 DLCI : 300
Conn. Type : frNIW Chan Service Type: High Priority
Conn Service Type : cbr1 Egress Queue Type: highPriority
Admn Status : UP Oper Status : OK
Slave Persist : YES Max Cost : -1
CIR (bps) : 1536000 BC (bytes) : 5100
BE (bytes) : 5100 FECN Config : setEFCIzero
ChanDEtoCLPmap : mapCLP ChanCLPtoDEmap : mapDE
IngrPercentUtil : 100 EgrPercentUtil : 100
EgrSrvRate (bps) : 1536000 ZeroCirEir (bps) : N/A
DE Tagging : DISABLED IgnoreIncomingDE : DISABLED
Pref Rte Id : 0 Directed Route : NO
Upload : 00000001 Routing Priority : 8
OAM CC Config : DISABLED Statistics : ENABLED
Local Loopback : DISABLED UPC : ENABLED
--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop:
Local PCR (cps) : 5760 Remote PCR (cps) : 5760
Local SCR (cps) : N/A Remote SCR (cps) : N/A
Local MCR (cps) : N/A Remote MCR (cps) : N/A
: Remote MBS (cps) : N/A
--------------------------------------------------------------------------
Xmt Abit State : A equal 1 Rcv Abit State : OFF
Xmt ATM State : Not Sending Rcv ATM State : Not Recving
--------------------------------------------------------------------------
E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT
NO NO NO NO NO NO
--------------------------------------------------------------------------

Step 6 Enter the cc command to start a management session with the active PXM card.

M8830_SF.6.MPSM155[FR].a > cc 1

(session redirected)

Step 7 Enter the dspcon command to display all connections for the switch.

M8830_SF.1.PXM.a > dspcons

Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency
----------------------+------------------------+---------+-------+---+-----------
6.65535 224 300 Routed 224 200 OK MASTER 8 Persistent
Local Addr: 47.009181000000003094095df6.000001061fff.00
Remote Addr: 47.009181000000000164444b61.000001091fff.00
Preferred Route ID:- Cast Type: P2P

Multilink Frame Relay on the MPSM-T3E3-155

Multilink Frame Relay (MFR) combines multiple individual links into one logical interface, called an MFR bundle. Multilink bundles help bridge the gap between DS1 and DS3 bandwidths, and can increase resiliency because the failure of a link usually does not bring down the whole bundle. In the MPSM-T3E3-155, each link is a T1 path on a channelized DS3 line or path.

The bundle interface serves as the Frame Relay data link, and performs the same functions as a physical Frame Relay interface. The bundle interface is visible to peers, so you configure Frame Relay functionality on the bundle interface. This section describes how to provision Mulitlink Frame Relay (MFR) services on the MPSM-T3E3-155 card.

Note Before you perform the procedures in this section you must first configure the MPSM-T3E3-155 card and lines as described in Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."

MFR Command Summary

Table 4-7 lists and describes the MFR commands on the MPSM-T3E3-155 card.

Table 4-7 MPSM-T3E3-155 Multilink Frame Relay Commands and Descriptions

Command

Description

addmfrbundle

Adds the MFR bundle

addmfrlnk

Adds the MFR link to a MFR bundle

addmfrport

Adds the MFR port and configures the Frame Relay parameters for the MFR bundle

clrmfrbundlecnt

Clears all of the counts associated with a MFR bundle

clrmfrbundlecnts

Clears all of the counts associated with all MFR bundles provisioned on the card

clrmfrlnkcnt

Clears the counters associated with a link on a specific MFR bundle

clrmfrlnkcnts

Clears the counters associated with all links on a specific MFR bundle

cnfmfrbundle

Modifies the configuration of the MFR bundle

cnfmfrlnk

Configures the MFR link in a MFR bundle

delmfrbundle

Deletes the MFR bundle

delmfrlnk

Deletes a specific link belonging to a specific bundle

dnmfrbundle

Puts the MFR bundle in administratively DOWN state

dspmfrbundle

Displays the configuration of a MFR bundle

dspmfrbundlealm

Displays alarm status for a MFR bundle

dspmfrbundlealms

Displays alarm status for all MFR bundles provisioned on the card

dspmfrbundlebucketcnt

Displays the MFR bundle bucket counters

dspmfrbundlecnt

Displays the counters associated with a MFR bundle

dspmfrbundles

Displays all of the MFR bundles provisioned on the card

dspmfrlnk

Displays the configuration of a MFR link

dspmfrlnkalm

Displays alarm status of all links associated with a specific MFR bundle

dspmfrlnkalms

Displays alarm status of all links associated with a specific MFR bundle

dspmfrlnkbucketcnt

Displays the MFR link bucket counters

dspmfrlnkcnt

Displays the counters associated with a MFR link

dspmfrlnks

Displays all links associated with an MFR bundle

upmfrbundle

Puts the MFR bundle in administratively UP state

MFR Features

For information about MFR features, see the "MPSM-T3E3-155 Card Features" section on page 1-4.

MFR Restrictions

The MPSM-T3E3-155 has the following restrictions:

•Aggregation of full T1 links only; MFR bundles with n x DS0 links are not supported

•Blending T1 and E1 is not supported

•Two-byte Frame Relay header (for example, 10 bit DLCI) is supported

•Four-byte Frame Relay header for extended addressing is not supported. Frame Relay extended addressing uses a 23-bit DLCI field that enables support for thousands of DLCIs in NNI networks.

•Frame Relay fragmentation is not supported.

•Super Frame (SF) mode is not supported. Only ESF (Extended Super Frame) mode is supported for MFR services.

•MFR is supported on the 3-port channelized T3 back card and 2-port channelized OC-3 back card.

•FRF2.1 Annex 1 is supported on NNI-type bundle interfaces.

•A maximum of 200 DLCIs per bundle is supported.

Multilink Frame Relay Quick Start Provisioning Procedure

This section provides quick start procedures for provisioning MRF on the MPSM-T3E3-155.

Command

Comments

Step 1

addmfrbundle
Related commands:

dspmfrbundle
cnfmfrbundle
delmfrbundle

Add a MFR bundle using default parameters. Refer to Creating an MFR Bundle for detailed instructions on adding an MFR bundle.

Step 2

cnfmfrbundle
Related commands:

addmfrbundle
cnfmfrbundle
delmfrbundle

Configure MFR bundle parameters. Refer to Configuring an MFR Bundle for detailed instructions on configuring an MFR bundle.

Step 3

addmfrlnk
Related commands:

cnfmfrlnk
dspmfrlnk
delmfrlnk

Add links to the MFR bundle. Refer to Adding Links to an MFR Bundle for detailed instructions on adding an MFR link.

Step 4

addmfrport
Related commands:

dspmfport
cnfrport
delrport

Add an MFR port. Refer to Adding a Port to the MFR Bundle for detailed instructions on adding an MFR port.

Step 5

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 6

addcon

Related commands:

cnfcon
dspcon
delcon

Add SPVCs for the MFR service. See the Provisioning and Managing SPVCs

Multilink Frame Relay General Provisioning Procedures

This section contains procedures for provisioning MFR on the MPSM-T3E3-155.

Note Both ends of an MFR connection must support MFR, and the MFR configuration on both ends must match.

Creating an MFR Bundle

The MPSM-T3E3-155 implements MFR service using MFR bundles, which contain one or more serial links. When you add a bundle, the MPSM-T3E3-155 creates the corresponding Frame Relay data link layer interface for the service. After adding a bundle, you can then add MFR links to the bundle.

When you add a bundle using the addmfrbundle command, you specify the bundle number and activation class only; all other bundle parameters assume default values. You subsequently configure other bundle parameters using the cnfmfrbundle command. For example, after adding a Class C bundle you also need to configure the minimum number of links that must be operational before the bundle is operational.

To create an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Create an MFR bundle using the addmfrbundle command

M8850_SF.10.MPSM155[FR].a > addmfrbundle <bundleNum> <activationClass>

Table 4-8 describes the parameters for the addmfrbundle command.

Table 4-8 addmfrbundle Command Parameters

Parameter

Description

bundleNum

Bundle Number, range 1-42

activationClass

Bundle activation class:

•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2=Class B—All of the bundle links must be operational for the MFR Bundle to be operational

•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

This command creates a MFR bundle with the default configuration shown in Table 4-9.

Table 4-9 MFR Bundle Default Configuration

Parameter

Description

minimumLinks

Specifies the minimum number of active links required for a Class-C MFR bundle to be operational. The default value is 1 link

helloTimer

Specifies the interval in seconds at which to send hello messages. The default is 10 seconds.

ackTimer

Specifies the maximum time period to wait for an acknowledgement message from the far end. The default is 4 seconds.

maxRetry

Specifies maximum number of times to re-try sending a hello message to the far end if an acknowledgement message is not returned. The default is 2 retries.

bundleName

Identifies the near-end bundle. The default bundle name is of the form node.slot.bundle, for example M8850_SF.Slot10.Bundle03

The following example creates MFR bundle 3 with Class A service type using default bundle parameters:

M8850_SF.10.MPSM155[FR].a > addmfrbundle 4 3

Step 3 To verify that the MFR bundle has been created, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle.

M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
Bundle Number : 4
Activation Class : C
Minimum Links : 1
Admin state : Up
Oper State : Down
Hello Timer (seconds) : 10
Ack Timer (seconds) : 4
Max Retry Count : 2
Maximum Bundle Links : 12
Configured Number of Links : 0
Active Number of Links : 0
Available Bandwidth : 0
Near End Bundle Name : M8850_SF.Slot10.Bundle04
Far End Bundle Name : <not defined>

Configuring an MFR Bundle

When you add an MFR bundle, most of the configuration options are defaults (See Table 4-9). For example, if you want to add a bundle with a minimum number of links that is greater than one, you have to configure the minimum number of links is this procedure.

To configure an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 If the MFR bundle is administratively up, bring it down by entering the dnmfrbundle <bundleNum> command.

Step 3 Configure MFR bundle parameters using the cnfmfrbundle command.

M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle <bundleNum> [-class <activationclass>] [-minlinks <minimumlinks>] [-hellotimer <hellotimer>] [-acktimer <acktime>] [-maxretry <maxretry>] [-bname <bundleName>]

Table 4-10 describes the parameters for the cnfmfrbundle command.

Table 4-10 cnfmfrbundle Command Parameters

Parameter

Description

-bundle

MFR bundle number, range 1-42

-class

Bundle activation class:

•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2=Class B—All of the bundle links must be operational for the MFR Bundle to be operational

•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational

-minlinks

Minimum number of links for Class-C activation class, range 1-12.

-hellotimer

Interval for sending hello messages, range 1-180 seconds

-acktimer

Maximum time period to wait for an acknowledgement from the far end, range 1-10 seconds

-maxretry

Maximum number of retries (Maximum retries), range 1-5 retries.

-bname

Near-end bundle name:

A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters, with a maximum of 49 characters.

In the following example, the user increases the minimum number of links for a Class C MFR bundle to 4 and sets the maximum number of retries to 4.

M8850_SF.9.MPSM155[FR].a > dnmfrbundle 4
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle 4 -minlinks 4 -maxretry 4

Step 4 Restore the bundle to the administrative up state by entering the upmfrbundle <bundleNum> command.

Step 5 To verify MFR bundle configuration, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle you want to display.

M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
Bundle Number : 4
Activation Class : C
Minimum Links : 4
Admin state : Up
Oper State : Down
Hello Timer (seconds) : 10
Ack Timer (seconds) : 4
Max Retry Count : 4
Maximum Bundle Links : 12
Configured Number of Links : 0
Active Number of Links : 0
Available Bandwidth : 0
Near End Bundle Name : M8850_SF.Slot10.Bundle04
Far End Bundle Name : <not defined>

Adding Links to an MFR Bundle

After you have established and configured an MFR bundle, you can add links to the bundle. Adding a link sends an Add-Link request message to the far-end of the bundle. A link is actively operating in a bundle only after the following conditions are met:

•An Add-Link acknowledgement is received from the Far end for the transmitted Add-Link message.

•An Add-Link request is received from the Far-end.

After both messages are received from the far-end, the MFR link is ready to transmit and receive data. Depending on the Activation Class of the bundle, the Bundle Up Indication is sent by the MFR Bundle layer to the Frame Relay Data Link layer under the following conditions.

•Class A bundles—After receiving link activation confirmation for one link.

•Class B bundles—After receiving link activation confirmation for all links in the bundle.

•Class C bundles—After a predefined number of links in the bundle confirm activation.

To add a link to an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Bring up the links (paths) that you want to add to the MFR bundle by entering the uppath [-path_filter] <path_num> command. To display all available paths, enter the dsppaths -all command.

Step 3 Add links to the MFR bundle by entering the addmfrlnk command. The new link has a default name with the format node.card.link.

M8850_SF.10.MPSM155[FR].a > addmfrlnk <link> <bundleNum>

Table 4-11 describes the parameters for the addmfrlnk command.

Table 4-11 addmfrlnk Command Parameters

Parameter

Description

link

Specifies a DS1 or E1 path:

•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 Enter the dsppaths -all command to display all available paths on the card.

bundleNum

Bundle number, in the range 1-42

Note Enter the dspmfrbundles command to display all bundles on the card.

The following example adds link 1.1:11 (bay 1, DS3 1, DS1 11) to bundle 4.

M8850_SF.10.MPSM155[FR].a > addmfrlnk 1.1:11 4

Step 4 To verify that the link was added to the MFR bundle, enter the dspmfrlnk <linkNum> command, specifying the number of the bundle.

M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
Link Number : 1.1:11
Bundle Number : 4
Link State : Down
Link Alarm State : Other
Link Delay (Rtt in msec) : 0
Link Near End Name : M8850_SF.Slot10.Link11
Link Far End Name : <not defined>
Link Far End Bundle Name : <not defined>
Link PHY Operational Status : Down

Configuring MFR Links

Optionally, reconfigure the near-end name of the MFR link. Links have a default near-end name in the format node.slot.link, for example M8850_SF.Slot10.Link11.

To rename a link, perform the following steps.

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Reconfigure the link by entering the cnfmfrlnk command.

M8850_SF.10.MPSM155[FR].a > cnfmfrlnk -link <lnkNum> -lname <linkname>

Table 4-12 describes the parameters for the cnfmfrlnk command.

Table 4-12 cnfmfrlnk Command Parameters

Parameter

Description

-link

Specifies the MFR link number:

Note Enter the dspmfrlnks command to display all MFR links on the card.

-lname

Near-end link name:

A null -terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters with a maximum of 49 characters.

In the following example, the user changes the MFR link name to M8850_SF.Slot09.Bundle04.Link11.

M8850_SF.9.MPSM155[FR].a > cnfmfrlnk -link 1.1.1:1 -lname M8850_SF.Slot09.Bundle04.Link11

Step 3 To verify MFR link configuration, enter the dspmfrlnk <lnkNum> command.

M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
Link Number : 1.1:11
Bundle Number : 4
Link State : Down
Link Alarm State : Other
Link Delay (Rtt in msec) : 0
Link Near End Name : M8850_SF.Slot09.Bundle04.Link11
Link Far End Name : <not defined>
Link Far End Bundle Name : <not defined>
Link PHY Operational Status : Down

Adding a Port to the MFR Bundle

You need to add a port to an MFR bundle before you can provision SPVCs.

To add a port to an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a username with Group1 privileges or higher.

Step 2 Prepare to add a port to the MFR bundle:

a. Determine the bundle number on which you will add the port. To display a list of the MFR bundle numbers, enter the dspmfrbundles command.

b. Verify that the link and port number you want to use are not already configured. To display a list of the Frame Relay ports already configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context.

When you add a port, you must specify a port number that is unique on the MPSM-T3E3-155 card. For example, if port number (If Num) 5 is assigned, you cannot use port 5 on any other line or bundle on that MPSM-T3E3-155 card.

Step 3 Add and configure an MFR port for the MFR bundle by entering the addmfrport command:

M8850_SF.10.MPSM155[FR].a >addmfrport <ifNum> <bundle> <portType> <sct> [-rat <rat>] [-oversub <oversub>] [-lmiSig <lmiSigType> ] [-asynUpdt <updateType>] [-elmi <elmiState>][-segLmi <segLmiStatus>] [-t391 <t391Value>] [-t392 <t392Value>] [-n391 <n391Value>] [-n392 <n392Value>][-n393 <n393Value>]

Table 4-13 lists the parameter descriptions for adding MFR ports.

Table 4-13 addmfrport Command Parameters

Parameter

Description

ifNum

A number for the port, in the range 1-1003.

bundleNum

The MFR bundle number, in the range 1-42.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

portType

Type of logical interface (port):

•1 = Frame Relay Service

•3 = Frame Forward (not applicable for MFR bundles)

sct

The Service class template (SCT) for the port, range 0-255.

Default: 0

Note The port SCT file must exist and be registered on the PXM disk before it is available for use. Enter the PXM dspscts command to view all registered SCT files on the PXM card.

-rat

The egress service ratio of the high priority and the low priority queues, range 0-15.

•Enter 0 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.

-oversub

Oversubscription control:

•1 = enable

•2 = disable (default)

-lmiSig

LMI signaling protocol type:

•2 = No Signaling (default)

•3 = StrataLMI

•4 = AnnexAUNI

•5= AnnexDUNI

•6 = AnnexANNI

•7 = AnnexDNNI

Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.

-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 (default)

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

•1 = enable

•2 = disable (default)

-segLmi

Segmented LMI control:

•1 = enable

•2 = disable (default)

-t391

T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends status inquiry 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-30. Default: 10

-t392

T392 timer. This is the polling verification timer. The network (DCE) expects status inquiry messages from the user (DTE) every T392 seconds. If the network does not receive a status inquiry message from the user within T392 seconds and the timer expires, then the network records a missing status inquiry 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-30. Default: 15

-n391

N391 counter. This setting establishes the full status (status of all PVCs) polling cycle. The user (DTE) sends a full report status inquiry 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. Range 1- 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 1-10. Default: 3

-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. Default: 4

Step 4 To display a list of all Frame Relay ports configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.

In the following example, the user adds MFR port 4 to bundle number 4 with service class template 0.

M8850_SF.10.MPSM155[FR].a > addmfrport 4 4 1 0

Step 5 To verify the port, enter the dspports command:

M8850_SF.10.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
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------
4 N/A Up LLDn FR 0 N/A 1532 1 None Off Off 4
11 1.1:1 Up Up FR 0 1(24) 1536 1 None Off Off N/A
12 1.1:2 Up Up FR 0 1(4) 256 1 None Off Off N/A
13 N/A Up Up FR 0 N/A 6131 1 None Off Off 1
21 1.2:1 Up Up FR 0 1(24) 1536 1 None Off Off N/A
22 1.2:2 Up Up FR 0 1(4) 256 1 None Off Off N/A
23 N/A Up Up FR 0 N/A 6131 1 None Off Off 2

Adding SPVCs to MFR Bundles

You create SPVCs for MFR the same way that you create Frame Relay SPVCs. For more information, see the "Provisioning and Managing SPVCs" section.

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.

	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 8800/8900 Series Configuration Guide, Release 5.2.
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 Chapter 2, "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 Chapter 2, "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.

	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 8800/8900 Series Configuration Guide, Release 5.2.
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 Chapter 2, "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 Chapter 2, "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.

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

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.

Argument	Description
slot	Enter the slot number for the card that hosts the port you are configuring.
bay	Replace the <bay> argument with the value 1 if the line is connected to a back card in the upper bay; replace the <bay> argument with the value 2 if the line is connected to a back card in the lower bay. Note that the bay number is always 1.
line	Replace the <line> argument with the number that corresponds to the back card port to which the line is connected.
ifNum	An ATM port is also called an interface. Enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. An ATM port is defined by its slot, bay, line, and interface number. You need not enter a slot number during port configuration because you identify the slot number when you select the card.

Argument	Description
ifNum	Interface number (port number) of the port to connect. •MPSM-16-T1E1 range: 1-499 •MPSM-T3E3-155 range: 1-1003 Note Use the dspports command in the Frame Relay CLI context to see the port numbers for all active Frame Relay ports.
dlci	Specifies the Data-Link Connection Identifier. •2-byte header range: 1-1006 and 1008-1022 •4-byte header range: 1-8257534 and 8257536-8388607
chanType	Specifies the channel type. Enter a number to indicate one of the following channel types: •1 = frNIW: Frame Relay Network Interworking •2 = frSIWtransparent: Service Interworking without any SDU translation •3 = frSIWtranslate: Service Interworking with SDU translation •5 = frForward: Frame Forwarding •6 = frNIWReplace: Frame Relay Network Interworking Replace
serviceType	Specifies the service type for the connection. Enter a number to indicate one of the following service types: •1 = highpriority (use cbr1 at ATM endpoints) •2 = rtVBR: real-time variable bit rate (use vbr3rt at ATM endpoints) •3 = nrtVBR: non-real-time variable bit rate (use vbr3rt at ATM endpoints) •5 = uBR: unspecified bit rate (use ubr at ATM endpoints) •9 = stdABR: available bit rate (use stdabr at ATM endpoints)
mastership	Controls whether this end of a connection is a master or slave endpoint. Enter a number to indicate the mastership of the endpoint as follows: •1 = master •2 = slave
cir	Specifies the CIR for the connection. •MPSM-T3E3-155 range—T3: 0-44209688, E3_G832: 0-33920000, and E3_G751: 0-33831000 bps. •MPSM-16-T1E1 range: 0-1984000 bps.
-slave	Identifies the slave endpoint of the connection, in the following format: slave_nsap_address.vpi.vci Note This parameter is required when you configure a master endpoint.
-slavepersflag	Controls whether the endpoint is persistent or non-persistent. Enter a number to indicate the endpoint's persistency as follows: •0 = persistent (default) •1 = nonpersistent
-eir	Specifies the excess information rate for the connection. •MPSM-T3E3-155 range—T3: 0-44209688, E3_G832: 0-33920000, and E3_G751: 0-33831000 bps. •MPSM-16-T1E1 range: 0-1984000 bps.
-bc	Specifies the Burst Commit size for the connection. Range: 0-2097151 bytes The default Frame Relay value is 5100, and the default Frame Forwarding value is 10300.
-be	Specifies the Burst Excess size for the connection. Range: 0-2097151 bytes The default Frame Relay value is 5100, and the default Frame Forwarding value is 10300.
-detag	Enables or disables Discard Enable Tagging on the connection. This parameter enables or disables tagging of the DE bit on ingress frames as the result of the policing mechanism. Enter a number to enable or disable DE tagging as follows: •1 = enable •2 = disable (default)
-igde	Enables or disables a connection's response to incoming Discard Enable tags. Enter a number to ignore (disable) or accept (enable) incoming DE tags as follows: •1 = enable •2 = disable (default)
-fecnmap	Specifies the mapping between FECN and EFCI for this connection. Enter a number to set the configuration of the FECN map as follows: •1 = mapEFCI •2 = setEFCIzero (default)
-demap	Specifies the mapping between DE and CLP for this connection. Enter a number to set the DE to CLP mapping, as follows: •1 = mapCLP (default) •2 = setCLPzero •3 = setCLPone
-clpmap	Specifies the mapping between CLP and DE for this connection. Enter a number to set the CLP to DE mapping, as follows: •1 = mapDE (default) •2 = setDEzero •3 = setDEone •4 = ignoreCLP
-eqsel	Selects the egress queue for this connection. Enter a number to indicate one of the following options: •1 = highPriority •2 = lowPriority •3 = notSupported The default value depends on the service type.
-ingut	Specifies the ingress percent utilization for this connection. This value controls the bandwidth allocated for the connection and allows you to oversubscribe the network resources. Range: 1-100 percent Default: 100 percent.
-egut	Specifies egress percent utilization for this connections. This value controls the bandwidth allocated for the connection and allows you to oversubscribe the network resources. Range: 1-100 percent Default: 100 percent
-egrat	Specifies the egress service rate. This value is used for CAC to determine if the port can support the connection. •MPSM-T3E3-155 range: 2400-44209688 bps •MPSM-16-T1E1 range: 2400 and 1984000 bps
-rtngprio	Specifies the routing priority for this connections, in the range 1-15. Default: 8
-upc	Enables or disables UPC configuration on the connection. Enter a number to enable/disable UPC configuration on the connection, as follows: •1 = enable (default) •2 = disable
-lpcr	Specifies the peak cell rate for this connection in the local to remote direction. The PCR of the local and remote endpoints must match to successfully create a connection. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-rpcr	Specifies the peak cell rate for this connection in the remote to local direction. The PCR of the local and remote endpoints must match to successfully create a connection. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-lscr	Specifies the sustainable cell rate for this connection in the local to remote direction. The SCR of the local and remote endpoints must match for variable bit rate connections. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-rscr	Specifies the sustainable cell rate for this connection in the remote to local direction. The SCR of the local and remote endpoints must match for variable bit rate connections. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-lmcr	Specifies the minimum cell rate for available bit rate connections in the local to remote direction. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-rmcr	Specifies the minimum cell rate for available bit rate connections in the remote to local direction. •MPSM-T3E3-155 range: 10-165787 cps •MPSM-16-T1E1 range: 10-36064 cps
-prefrte	This option associates a preferred route to the connection. Use this parameter at the master endpoint only. Be sure the route exists before you associate it with the connection because the system does not check it. Use the dspprefs command at the PXM card to display preferred routes. The following values are valid: •0: Disassociate a connection from a route (default) •1-65535: The preferred route id Note Before you delete the route, disassociate all connections from the route; otherwise, a dangling preferred route path remains. Use the dspcons [-rteid <pref rte id> ] command at the PXM card to display all connections associated with a route. Note An SPVC can be associated with one preferred route. For an XPVC, you can associate the preferred route with only the SPVC portion of the XPVC.
-directrte	Enables or disables a direct route for this connection. When enabled (yes), the preferred route is the only permissible route for this connection. Should the directed preferred route be unavailable, the connection fails. When disabled (no), the connection tries another alternate route if the preferred route is unavailable. The values are as follows: •1 = yes (make the preferred route required) •0 = no (do not require the connection to take the preferred route) Default: 0
-rmbs	Specifies the Maximum Burst Size for variable bit rate connections in the remote to local direction. MBS is the maximum number of cells that can burst at the PCR and still be compliant. Range 0-5000000 cells
cc	Operations, administration, and maintenance continuity check (OAM CC): •1 = enable •0 = disable (default) Continuity checking invokes a round trip of an OAM cell simply to confirm that both directions of the connection are intact. To provision continuity checking, enable this function at both ends of the connection; otherwise, a connection alarm results. When you add a connection and include this parameter, the connection goes into alarm until both ends of the connection are added.

Connection Type	Parameters Checked	addcon Keyword
CBR	PCR	-lpcr
VBRrt and VBRnrt	PCR, SCR, MBS	-lpcr, -lscr, and -lmbs
stdABR	PCR and MCR	-lpcr and -lmcr
UBR	PCR	-lpcr

Command	Description
addmfrbundle	Adds the MFR bundle
addmfrlnk	Adds the MFR link to a MFR bundle
addmfrport	Adds the MFR port and configures the Frame Relay parameters for the MFR bundle
clrmfrbundlecnt	Clears all of the counts associated with a MFR bundle
clrmfrbundlecnts	Clears all of the counts associated with all MFR bundles provisioned on the card
clrmfrlnkcnt	Clears the counters associated with a link on a specific MFR bundle
clrmfrlnkcnts	Clears the counters associated with all links on a specific MFR bundle
cnfmfrbundle	Modifies the configuration of the MFR bundle
cnfmfrlnk	Configures the MFR link in a MFR bundle
delmfrbundle	Deletes the MFR bundle
delmfrlnk	Deletes a specific link belonging to a specific bundle
dnmfrbundle	Puts the MFR bundle in administratively DOWN state
dspmfrbundle	Displays the configuration of a MFR bundle
dspmfrbundlealm	Displays alarm status for a MFR bundle
dspmfrbundlealms	Displays alarm status for all MFR bundles provisioned on the card
dspmfrbundlebucketcnt	Displays the MFR bundle bucket counters
dspmfrbundlecnt	Displays the counters associated with a MFR bundle
dspmfrbundles	Displays all of the MFR bundles provisioned on the card
dspmfrlnk	Displays the configuration of a MFR link
dspmfrlnkalm	Displays alarm status of all links associated with a specific MFR bundle
dspmfrlnkalms	Displays alarm status of all links associated with a specific MFR bundle
dspmfrlnkbucketcnt	Displays the MFR link bucket counters
dspmfrlnkcnt	Displays the counters associated with a MFR link
dspmfrlnks	Displays all links associated with an MFR bundle
upmfrbundle	Puts the MFR bundle in administratively UP state

	Command	Comments
Step 1	addmfrbundle Related commands: dspmfrbundle cnfmfrbundle delmfrbundle	Add a MFR bundle using default parameters. Refer to Creating an MFR Bundle for detailed instructions on adding an MFR bundle.
Step 2	cnfmfrbundle Related commands: addmfrbundle cnfmfrbundle delmfrbundle	Configure MFR bundle parameters. Refer to Configuring an MFR Bundle for detailed instructions on configuring an MFR bundle.
Step 3	addmfrlnk Related commands: cnfmfrlnk dspmfrlnk delmfrlnk	Add links to the MFR bundle. Refer to Adding Links to an MFR Bundle for detailed instructions on adding an MFR link.
Step 4	addmfrport Related commands: dspmfport cnfrport delrport	Add an MFR port. Refer to Adding a Port to the MFR Bundle for detailed instructions on adding an MFR port.
Step 5	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 6	addcon Related commands: cnfcon dspcon delcon	Add SPVCs for the MFR service. See the Provisioning and Managing SPVCs

Parameter	Description
bundleNum	Bundle Number, range 1-42
activationClass	Bundle activation class: •1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational •2=Class B—All of the bundle links must be operational for the MFR Bundle to be operational •3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

Parameter	Description
minimumLinks	Specifies the minimum number of active links required for a Class-C MFR bundle to be operational. The default value is 1 link
helloTimer	Specifies the interval in seconds at which to send hello messages. The default is 10 seconds.
ackTimer	Specifies the maximum time period to wait for an acknowledgement message from the far end. The default is 4 seconds.
maxRetry	Specifies maximum number of times to re-try sending a hello message to the far end if an acknowledgement message is not returned. The default is 2 retries.
bundleName	Identifies the near-end bundle. The default bundle name is of the form node.slot.bundle, for example M8850_SF.Slot10.Bundle03

Parameter	Description
-bundle	MFR bundle number, range 1-42
-class	Bundle activation class: •1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational •2=Class B—All of the bundle links must be operational for the MFR Bundle to be operational •3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational
-minlinks	Minimum number of links for Class-C activation class, range 1-12.
-hellotimer	Interval for sending hello messages, range 1-180 seconds
-acktimer	Maximum time period to wait for an acknowledgement from the far end, range 1-10 seconds
-maxretry	Maximum number of retries (Maximum retries), range 1-5 retries.
-bname	Near-end bundle name: A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters, with a maximum of 49 characters.

Parameter	Description
link	Specifies a DS1 or E1 path: •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 Enter the dsppaths -all command to display all available paths on the card.
bundleNum	Bundle number, in the range 1-42 Note Enter the dspmfrbundles command to display all bundles on the card.

Parameter	Description
-link	Specifies the MFR link number: Note Enter the dspmfrlnks command to display all MFR links on the card.
-lname	Near-end link name: A null -terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters with a maximum of 49 characters.

Parameter	Description
ifNum	A number for the port, in the range 1-1003.
bundleNum	The MFR bundle number, in the range 1-42. Note Enter the dspmfrbundles command to display all MFR bundles on the card.
portType	Type of logical interface (port): •1 = Frame Relay Service •3 = Frame Forward (not applicable for MFR bundles)
sct	The Service class template (SCT) for the port, range 0-255. Default: 0 Note The port SCT file must exist and be registered on the PXM disk before it is available for use. Enter the PXM dspscts command to view all registered SCT files on the PXM card.
-rat	The egress service ratio of the high priority and the low priority queues, range 0-15. •Enter 0 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.
-oversub	Oversubscription control: •1 = enable •2 = disable (default)
-lmiSig	LMI signaling protocol type: •2 = No Signaling (default) •3 = StrataLMI •4 = AnnexAUNI •5= AnnexDUNI •6 = AnnexANNI •7 = AnnexDNNI Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.
-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 (default) •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. •1 = enable •2 = disable (default)
-segLmi	Segmented LMI control: •1 = enable •2 = disable (default)
-t391	T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends status inquiry 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-30. Default: 10
-t392	T392 timer. This is the polling verification timer. The network (DCE) expects status inquiry messages from the user (DTE) every T392 seconds. If the network does not receive a status inquiry message from the user within T392 seconds and the timer expires, then the network records a missing status inquiry 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-30. Default: 15
-n391	N391 counter. This setting establishes the full status (status of all PVCs) polling cycle. The user (DTE) sends a full report status inquiry 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. Range 1- 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 1-10. Default: 3
-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. Default: 4