Table of Contents

Card and Service Configuration

This chapter includes instructions to configure MGX 8250 cards and services. This chapter includes the following sections:

• Tasks and Rules to Configure Cards and Services
  
  
• Processor Switching Module
  
  
• ATM Universal Service Module (AUSM)
  
  
• Frame Service Module Features
  
  
• Configuring Frame Relay Service
  
  
• Circuit Emulation Service Module for T3 and E3
  
  
• Eight-Port Circuit Emulation Service Modules
  
  
• Service Resource Module
  
  
• Online Diagnostics Test
  
  
• DS3 Loopback Test
  
  

---

Note   The instructions in this chapter presume that a plan exists for your network. Some of the information related to network planning is reviewed in this chapter.

---

---

Note   For configuration information on the Voice Interworking Service Module (VISM), refer to the Cisco Voice Interworking Service Module Installation and Configuration Guide

---

---

Note   For configuration information on the Route Processor Module (RPM), refer to the Cisco MGX Route Processor Module Installation and Configuration Guide.

---

---

Note   General instructions to physically insert and remove cards are in ""Enclosure and Card Installation"

---

Tasks and Rules to Configure Cards and Services

This section contains a general description of the sequence of tasks to configure cards and services. Tasks for individual cards appear in the subsequent sections.

This section contains the following topics:

• Sequence of Configuration Tasks.
  
  
• Modifying the Resource Partitioning.
  
  
• Rules for Adding Connections.
  
  
• • Rules for Adding a DAX Connection
    
    
  • Rules for Adding Three-Segment Connections
    
    
  • Rules for Adding Management Connections
    
    

Sequence of Configuration Tasks

In a new shelf, the common approach is to perform the same configuration task for all cards at once. For example, adding logical ports to all applicable cards.

When installing a single card, the likely sequence is to first specify the card-level features, and continue until you have configured every connection.

The following list outlines the common tasks for configuring cards in a new shelf:

Modifying the Resource Partitioning

A resource partition at the card level consists of a number of logical connection numbers (LCNs). At the port level, a resource partition consists of a percentage of bandwidth, a DLCI or VPI/VCI range, and the number of LCNs available to a network control application. On the PXM1, the connections are global logical connection numbers (GLCNs).

By default, all resources on a a card or logical port are available to any controller on a first-come, first-served basis. If necessary, you can modify the resource partitioning at the card level or logical port level. Port-level resource modification follows card-level modification, so the available port-level resources depend on whether and how much you change the card-level resource partitioning. You do not have to change the resource partitioning for the card before changing resource partitioning for a port.

The current network control application is Portable AutoRoute (PAR). Planning considerations should include the possibility of modifying the partitioning of resources for the interface. For example, the MGX 8250 has the capacity to support a Cisco Multiprotocol Label Switching (MPLS) controller or a private network-to-network interface (PNNI) controller.

Rules for Adding Connections

This section includes rules for adding the following types of connections:

• Rules for Adding a DAX Connection—Local-only, digital access, and cross-connect (DAX) connections.
  
  
• Rules for Adding Three-Segment Connections—Connections across an ATM or Frame Relay network.
  
  
• Rules for Adding Management Connections—In-band connection that allow a workstation to control a local or remote MGX 8250 through a service module. Although the rules include references to CLI syntax, they also apply to the Cisco WAN Manager application.
  
  

Rules for Adding a DAX Connection

A DAX connection is a connection whose endpoints for the entire connection exist on the same shelf. The following rules apply to the MGX 8250:

addcon <local parameters>

Slave is the default case, so you actually do not explicitly have to specify it. When you press Return, the system returns a connection identifier. The identifier includes the port and DLCI or VPI and VCI.

Use the identifier to specify the slave endpoint when you subsequently add the connection at the master end. The slave endpoint is specified as the remote parameters in item 5.

addcon <local parameters> <remote parameters>

Rules for Adding Three-Segment Connections

A three-segment connection consists of a local segment on each MGX 8250 at the edges of the network cloud, and a middle segment across the network cloud.

The MGX 8250 requirements are:

addcon <local parameters> <remote parameters>

Rules for Adding Management Connections

This section describes the requirements for adding an inband ATM PVC for managing an MGX 8250 in stand-alone node. A management connection lets a workstation connected through a router control either the local MGX 8250 node or a remote MGX 8250 node that has no workstation. The typical configuration has as the connecting router feed an AUSM/B, FRSM, RPM, or PXM1 UNI port.

A management connection can be either a DAX connection or a three-segment connection. The maximum number of management connections is eight. The DAX connection exists between a service module or PXM1 UNI and port 34 of the local PXM1. PXM1 port 34 is a reserved port for management connections on a stand-alone node. The network in Figure 6-1 shows FRSMs in a feeder application.

A three-segment management connection includes the following segments:

The path from "A" to "B" in Figure 6-1 consists of three segments. A segment exists between the FRSM and the PXM1 on each MGX 8250. The middle segment exists between the BXMs at the edges of the ATM cloud and may traverse BPX 8600 via nodes in the cloud. The VPI and VCI at each BPX 8600 series switch connected to an MGX 8250 feeder must match the VPI and VCI on the slave endpoint of the connected PXM1. The VPIs and VCIs at the endpoints of the middle segment do not have to match. If you use the CLI rather than the Cisco WAN Manager application, add each segment through the CLI at each switch.

Processor Switching Module

This section describes how to activate and configure the card-level parameters, lines, and ports on the PXM1 uplink card. This section also describes how to add connections to the PXM1 in a stand-alone node.

The descriptions include instructions to complete the following tasks:

• Modify the resource partitioning at the card level (optional).
  
  
• Activate a line on the uplink card. On a stand-alone node, you can activate more than one line if the uplink card has multiple lines. One physical line must be the trunk to a network routing node.
  
  
• Optionally configure a clock source on the PXM1 or a service module. Note that a service module line must be active before you can configure it as a clock source. See the "Configuring Synchronization for the Shelf" section for more information.
  
  
• If the shelf has a pair of SRMs for bulk distribution and you use the CLI rather than the CiscoView application, activate the SRM lines from the PXM1.
  
  
• Optionally modify the resource partitioning at the port level.
  
  
• Create logical ports.
  
  
• On a stand-alone node, specify the cell header type. UNI cell headers typically apply where a workstation connects to a UNI port on the uplink card rather than a port on the PXM1-UI card. Such an implementation is not common.
  
  
• On a stand-alone node, add standard connections and optional management connections.
  
  
• On a stand-alone node, configure Automatic Protection Switching (APS).
  
  
• For a feeder, complete the steps on the connected BPX 8600 series switch to make the feeder an available resource in the network.
  
  

---

Note   For a description of the bit error rate test (BERT) functions, see the "Bit Error Rate Testing Through an MGX-SRM-3T3" section.

---

Configuring Synchronization for the Shelf

This section defines the clock sources for the MGX 8250, then describes how to configure each source.

Clock Sources

The available clock sources are as follows:

• The internal clock comes from an oscillator on the PXM1. It is the default source when the shelf first comes up and it remains until a different clock source is specified. This default source is a Stratum-4 clock. Stratum-3 can also be used as an internal clock source.
  
  
• The trunk interface clock originates on a BPX 8600 series node or another vendor's switch and comes through the line on the PXM1s back card.
  
  
• An external clock source comes from an external timing source and arrives at the T1 or E1 connections on the PXM1 user interface back card. Frequently, the external device is a highly reliable, dedicated device.
  
  
• For external Stratum-4 clock sources, the PXM1-UI back card must be used.
  
  
• For external Stratum-3 clock sources, the PXM-UI-S3 back card must be used.
  
  

---

Note   See the "Making External Clock Connections" section for information on the physical connections for external clocking.

---

• An additional step is necessary to configure an external clock source (see below).
  
  
• A UNI interface on a service module or PXM1 UNI port can be a clock source. A line must be active before you can specify it as a clock source.
  
  

Clock Source Types

The clock types are: primary, secondary, and tertiary.

For example, you could configure an external clock source as the primary source, a line as a secondary source, and the internal oscillator as the tertiary source. Note that if you specify a tertiary source, it is always the internal oscillator.

Clock Source Configuration

After the PXM1 broadband interfaces and the service module lines are configured, you can configure the clock sources through the CiscoView application or the CLI. If you use the CLI, enter the cnfclksrc command on the active PXM1 one time for each clock source.

cnfclksrc <slot.port> <clktyp>

Caution   Be careful not to set multiple primary and secondaries.

Configuration Example

For example, to configure the inband interface as the primary clock source and an external clock device as the secondary source, enter the following commands.

Step 1   Specify the clock source.

popeye1r.1.8.PXM.a > cnfclksrc 7.35 S

popeye1r.1.8.PXM.a > cnfclksrc 7.1 P

Step 2   To check the configuration by entering the dspclksrc command.

If you have specified an external clock source, use the CiscoView application or the CLI command cnfextclk to select the T1 or E1 line and the impedance of the line. The syntax for cnfextclk is

cnfextclk <ClockType> <Impedance>

Step 3   Specify the Stratum level of the clock source (Stratum-3 or Stratum-4).

cnfclklevel <level>

---

Note   For external clocking sources, Stratum-3 is supported by the PXM-UI-S3 card; Stratum-4 sources are supported by the PXM1-UI back card. Either Stratum-3 or Stratum-4 can be used as internal clocking sources.

---

Configuring PXM1 Card-Level Parameters, Lines, and Ports

This section describes how to configure card-level features, activate a physical line, and configure logical elements such as a port.

See the "Tasks and Rules to Configure Cards and Services" section for background information on these types of tasks.

Step 1   Optionally, to modify the resource partitioning for the whole card by entering the cnfcdrscprtn command. You can view resource partitioning through the dspcdrscprtn command.

cnfcdrscprtn <number_PAR_conns> <number_PNNI_conns> <number_TAG_conns>

• number_PAR_conns is the number of connections in the range 0-32767 for PAR.
  
  
• number_PNNI_conns is the number in the range 0-32767 available to PNNI.
  
  
• number_TAG_conns is the number of connections in the range 0-32767 for MPLS.
  
  

For example, to reserve 10,000 connections for each controller on a PXM1 with

cnfcdrscprtn 10000 10000 10000

Step 2   Activate a line by entering the addln command.

addln -ds3 <slot.line> | -e3 <slot.line> | -sonet <slot.line>

For a feeder, you can activate only one line. For a stand-alone, you can activate more than one line if the back card has multiple lines. One line must serve as the trunk to the ATM network. With an OC-3, T3, or E3 card, remaining lines can serve as UNI ports to CPE.

Step 3   If necessary, modify the characteristics of a line by entering the cnfln command.

Step 4   Configure logical ports for the physical line by entering the addport command. Enter the addport command once for each logical port. Related commands are cnfport, dspports, and delport.

addport <port_num> <line_num> <pct_bw> <min_vpi> <max_vpi>

The following example uses 100% of the bandwidth on one logical port 1

addport 1 1 100 1 200

• The first "1" is the logical port number.
  
  
• The second "1" is the line number on the PXM1 back card to which you are assigning this logical port number.
  
  
• "100" is the percentage of bandwidth this port has in both directions;
  
  
• The VPI range is 1-200.
  
  

Step 5   If necessary, enter the cnfportrscprtn command to modify port-level resources for a controller

cnfportrscprtn <port_no> <controller> <ingress_%BW> <egress_%BW> <min_VPI> <max_VPI> <min_VCI> <max_VCI> <max_GLCNs>

Step 6   On a stand-alone node, specify the cell header type as needed by entering the cnfatmln command.

cnfatmln <line_num> <type>

• line_numer_Id	The line number in the range 1-4
  type	The ATM interface type: 2 for UNI or 3 for NNI (the default)

  
  
  line_num is the line number in the range 1-4.
  
  

UNI cell headers typically apply where a workstation connects through a line to a PXM1 UNI port (rather than a SLIP-based port on the PXM1-UI card). Such an implementation is not common, so entering cnfatmln is not necessary.

Automatic Protection Switching on the PXM1

Automatic Protection Switching (APS) provides redundancy for an OC-3 or OC-12 line on the PXM1 (if a failure occurs someplace other than the PXM1 front card). The failure can originate on the daughter card, uplink card, or any part of the physical line.

With APS, the active PXM1 remains active and passes the cells from the failed line-path through the redundant line. The advantage of APS is that a line switchover requires significantly less time than a full PXM1 switchover.

Note   A failure of the PXM1 front card in a redundant system causes the entire PXM1 card set to switch over.

As defined in GR-253, a variety of APS modalities are possible (see the command summaries that follow).

APS Requirements

The current requirements for APS service on an MGX 8250 shelf are

• Redundant PXM1s (currently, the PXM1 does not support an APS configuration where the working and protection lines on the same uplink card).
  
  
• A "B" version of an OC-3 or OC-12 back card (SMLR-1-622/B, and so on).
  
  
• The connected network shelf or CPE must also support APS.
  
  

APS Configuration

Initial APS specification consists of the working and protection slot and line and the mode for APS. After the initial APS specification, you can configure additional APS parameters, give commands for switching lines, and display the APS configuration. The CiscoView application and CLI provide access to the APS feature. For detailed descriptions of the CLI commands, refer to the Cisco MGX 8250 Multiservice Gateway Command Reference. Note that APS is available for only the "B" versions of the SONET cards—SMLR-1-622/B, and so on. The applicable CLI commands are

• addapsln to specify the lines and mode for APS
  
  
• cnfapsln to modify the following details of the APS operation:
  
  
• • error thresholds
    
    
  • wait period before the PXM1 restores the working line after errors clear
    
    
  • unidirectional or bidirectional switchover, which specifies whether one or both directions of a line are switched when the criteria for a hard or soft failure are met for one direction
    
    
  • revertive recovery, where the working line automatically returns to operation after errors clear and any wait period has elapsed
    
    
  • enable use of K1 and K2 bytes in the line-level frame for equipment at both ends to exchange APS-related information
    
    
• delapsln to delete the APS configuration
  
  
• dspapsln to display the configuration for an APS-configured line
  
  
• switchapsln to issue commands for line switching that:
  
  
• • clear previous user requests
    
    
  • lock out (block) line switching
    
    
  • manually switch to the protection line if the following conditions are true: no errors exist, the working line is active, and your request has an equal or higher priority than the last switch request.
    
    
  • force a line switch regardless of existing errors if the following conditions are true: the working line is active and your request has an equal or higher priority than the last switch request.
    
    
  • switch all traffic to either the working lines or protection lines so you can remove a card (applies to only the currently supported configuration of 1+1 mode on two uplink cards).
    
    

To specify APS, use the following syntax:

addapsln <workline> <workingslot> <protectionline> <protectionslot> <archmode>

Adding Connections on a PXM1 in a Stand-Alone Node

This section describes the CLI commands for provisioning connections on a PXM1 in a stand-alone node. Connection addition conforms to the rules for a standard connection or a management connection. (See the "Rules for Adding Connections" section). In addition, this section describes the commands for modifying specific features for a connection and policing connections by way of usage parameter control (UPC).

The CLI commands correspond to functions in the Cisco WAN Manager application. The preferred CLI command is addcon. (If the application requires NSAP addressing, enter the addchan command to add a connection and the cnfchan command to modify a connection. To see the syntax for these two commands, refer to the command reference.)

Complete the following steps on the PXM1 CLI:

Step 1   Enter the addcon command according to the following syntax:

addcon <port_num> <conn_type> <local_VPI> <local_VCI> <service> [CAC] [mastership] [remoteConnId]

---

Note   The slot number of the active PXM1 is always 0 when you add a connection.

---

Step 2   If necessary, modify a connection by entering cnfcon:

cnfcon <conn_ID> <route_priority> <max_cost> <restrict_trunk_type> [CAC]

Step 3   As needed, specify usage parameter control according to the connection type. Enter either cnfupccbr, cnfupcvbr, cnfupcabr, or cnfupcubr.

This step defines the parameters for each of these commands. Note that the parameters for cnfupcvbr and cnfupcabr are the same. Also, the polType parameter has numerous variations in accordance with ATM Forum v4.0. For a list of these variations, see Table 6-1 after the syntax descriptions.

cnfupccbr <conn_ID> <polType> <pcr[0+1]> <cdvt[0+1]> <IngPcUtil> <EgSrvRate> <EgPcUtil>

cnfupcvbr or cnfupcabr <conn_ID> <polType> <pcr[0+1]> <cdvt[0+1]> <scr> <scr> <IngPcUtil> <EgSrvRate> <EgPcUtil>

cnfupcubr <conn_ID> <polType> <pcr[0+1] >< cdvt[0+1]> <IngPcUtil>

ATM Universal Service Module (AUSM)

The MGX-AUSM/B-8T1 and MGX-AUSM/B-8E1 ATM Universal Service Modules are eight port multipurpose card sets for T1 or E1 lines. This section includes the following instructions for the CLI:

• Summary of AUSM Features
  
  
• Configure the Card, Lines, and Ports
  
  
• Configure Inverse Multiplexing
  
  
• Adding and Configuring Connections on the AUSM/B
  
  

Summary of AUSM Features

The ATM Universal Service Modules (AUSM) include the following features:

• ATM UNI with high port-density for the CPE—With AUSMs in all 24 service module slots, an MGX 8250 shelf can support up to 192 individual T1 or E1 lines. An individual card set can support 1000 data connections and 16 management connections.
  
  
• Inverse multiplexing for ATM (IMA) that complies with ATM Forum v3.0 and v3.1—The 8-port AUSM can provide nxT1 or nxE1 logical ports up to maximum rates of 12 Mbps for T1 or 16 Mbps for E1.
  
  
• Classes of Service (CoS)—CBR, ABR, non-real-time VBR, real-time VBR, and UBR with per-VC queuing on ingress and multiple class of service queues on egress. ABR includes support of both ForeSight ABR and standard ABR (TM 4.0 compliant).
  
  
• Statistics collection.
  
  
• Virtual path connections (VPCs).
  
  
• Network synchronization derived from one of its lines.
  
  
• Bit error rate test (BERT) functionality with loop back pattern generation and verification on individual lines or logical port. For a description of the BERT functions, see the "Bit Error Rate Testing Through an MGX-SRM-3T3" section.
  
  
• 1:N redundancy through the optional MGX-SRM-3T3/C card.
  
  
• Automatic card-restore.
  
  
• SNMP and TFTP to support card and connection management.
  
  
• Resource partitions for individual network control applications.
  
  

---

Note   See the "ATM UNI Service Module (AUSM)" section for additional information on AUSM features.

---

Configure the Card, Lines, and Ports

You can activate and configure the AUSM card, lines, and ports with either the CLI or the CiscoView application. This section includes descriptions of the CLI commands used to perform the following tasks:

• Optionally modify resource partitioning at the card level
  
  
• Activate and configure a line
  
  
• Create and configure a logical port
  
  
• Optionally modify resource partitioning at the port level
  
  
• Configure usage parameters
  
  
• Configure queue depths
  
  
• Configure the ForeSight ABR feature
  
  
• Configure standard ABR
  
  
• Configure a line as a clock source
  
  

---

Note   For connection-related tasks, seethe "Adding and Configuring Connections on the AUSM/B" section.

---

Perform the following steps on the CLI of the AUSM/B:

Step 1   If necessary, modify the resource partitioning for the whole card by entering the cnfcdrscprtn command. You can view resource partitioning through dspcdrscprtn.

cnfcdrscprtn <number_PAR_conns | number_PNNI_conns | number_TAG_conns>

For example, you could reserve 300 connections for each controller on the AUSM with

cnfcdrscprtn 300 300 300

Step 2   Activate a physical line by entering addln for each of the eight lines as needed.

addln <line_number>

Step 3   Optionally, enter the cnfln command to specify line coding, line length, and clock source.

cnfln <line_num> <line_code> <line_len> <clk_src> [E1-signaling]

Step 4   Enter upport to activate the logical operation of the line.

upport <port_number>,

where port_number is in the range 1-8.

Step 5   If necessary, enter cnfportq to modify the egress queues.

cnfportq <port_num> <q_num> <q_algo> <q_depth> <clp_high> <clp_low> <efci_thres>

Step 6   If necessary, configure resources at the port level by entering cnfportrscprtn. Enter dspportrscprtn to see the current resource partitioning.

cnfportrscprtn <port_num> <controller> <ingress_%BW> <egress_%BW> <number_of_cons> <VPImin/VPImax> [VCImin/VCImax]

Configure Inverse Multiplexing

This section describes the CLI command sequence for configuring the IMA feature.

Step 1   addln on all constituent links.

Step 2   cnfln if not already properly configured.

Step 3   addimagrp (or addaimgrp) to create the IMA group by using the following syntax:

addimagrp <group_num> <port_type> <list_of_links> <minNumLink>

For example the following command creates IMA group 1 with lines 3, 4, and 5. The minimum is 3.

IMA-related commands are dspimagrp, dspimagrpcnt, dspimagrps, dspimainfo, and dspimalncnt. Refer to the Cisco MGX 8800 Series Switch Command Reference for descriptions.

Adding and Configuring Connections on the AUSM/B

Connections can be added and modified through the Cisco WAN Manager or the CLI. Refer to applicable documentation if you use the Cisco WAN Manager application.

This section describes how to add an ATM connection through the CLI according to the rules for adding a standard connection or a management connection in the form of either a DAX con or a three-segment connection. See the "Rules for Adding Connections" section.

Perform the following steps on the CLI of the AUSM/B:

Step 1   Enter the addcon command.

When you add a connection with addcon, the system automatically assigns the next available channel number, so addcon does not require it. However, some related commands require a channel number—cnfchanfst, cnfchanq, cnfconstdabr, and cnfupcabr. To see the channel number after you add a connection, enter dspcons.

The addcon syntax is

addcon <port_number> <vpi> <vci> <ConType> <SrvType> [Controller_Type] [mastership] [remoteConnID]

---

Note   To migrate between ForeSight ABR and TM 4.0 ABR, the connections must be manually deleted and then re-added. This migration is not possible at run-time.

---

Step 2   To configure usage parameter control (UPC) for the connection (channel), use cnfupccbr, cnfupcvbr, cnfupcrtvbr, cnfupcabr, or cnfupcubr. Enter dspcons to obtain the channel number.

cnfupccbr <port.vpi.vci> <enable/disable> <pcr[0+1]> <cdvt[0+1]> <IngPcUtil> <EgSrvRate> <EgPcUtil>

cnfupcvbr has the same syntax and parameters as cnfupcabr

cnfupcvbr or cnfupcabr <port.vpi.vci> <enable> <pcr[0+1]> <cdvt[0+1]> <scr> <scr_police> <mbs> <IngPcUtil> <EgSrvRate> <EgPcUtil> <clp_tag>

cnfupcubr <port.VPI.VCI> <enable> <pcr[0-1]> <cdvt[0-1]> <IngPcUtil> <clp_tag>

Step 3   Enter cnfchanfst to configure the parameters for a ForeSight channel, if necessary.

ForeSight ABR is a connection-level feature that require the Rate Control Feature to be enabled on the card.

cnfchanfst <port.vpi.vci> <enable> <fgcra_enable> <ibs> <pcr> <mcr> <icr>

Step 4   Enter cnfconstdabr to configure the parameters for a standard ABR (TM 4.0 compliant).

cnfconstdabr <Chan_Num ABRType> <mcr> <pcr> <icr> <rif> <rdf> <nrm> <trm> <tbe> <frtt> <adtf> <cdf>.

Please note the following items.

• Standard ABR is a connection-level feature that requires the Rate Control Feature to be enabled on the card.
  
  
• Virtual Source/Virtual Destination behavior (VS/VD) is not supported.
  
  
• Standard ABR does not support Explicit Rate (ER) marking of RM cells.
  
  
• cnfconabrrates can be used to modify the rates:
  Usage: cnfconabrrates <Port.Vpi.Vci/Chan_Num> <mcr> <pcr> <icr>
  
  
• cnfconabrparams can be used to modify the parameters:
  Usage: cnfconabrparams <Port.Vpi.Vci/Chan_num> <ABRType> <rif> <rdf> <nrm> <trm> <tbe> <rtt> <adtf>
  
  
• rif and rdf values for a Standard ABR connection need to be configured to be <= PCR for the connection.
  
  

Step 5   If necessary, change the queue depths by using cnfchanq.

cnfchanq <port.vpi.vci> <discard_option> <vc_q_depth> <clp_thresh_high> <clp_thresh_low | epd_threshold> <efci_thresh>

BPX 8600-to-BPX 8600 Segment

For the middle segment, be sure to use the connection type as the local segments on the MGX 8250 node (CBR, VBR, ABR, or UBR). The parameters directly map from those specified at the connection endpoint.

Frame Service Module Features

This section describes the features available on each of the Frame Service Modules (FRSMs). The primary function of the FRSM is to convert between the Frame Relay formatted data and ATM/AAL5 cell-formatted data. For an individual connection, you can configure network interworking (NIW), service interworking (SIW), ATM-to-Frame Relay UNI (FUNI), or frame forwarding.

Note   See the "Frame Relay Service Modules" section for more information on the features of FRSM service modules.

An FRSM converts the header format and translates the address for

• Frame Relay port number and DLCI
  
  
• ATM-Frame UNI (FUNI) port number and frame address or frame forwarding port
  
  
• ATM virtual connection identifier (VPI/VCI)
  
  

This section includes the following topics:

• Summary of Frame Service Module Features
  
  
• Configuring the FRSM Cards, Lines, and Ports
  
  

Summary of Frame Service Module Features

This section contains a summary of the features common to all FRSM models. The following sections contain summaries of the features unique to each type of FRSM.

All FRSMs support:

• Frame Relay-to-ATM Network Interworking (NIW) as defined in FRF.5.
  
  
• Frame Relay-to-ATM Service Interworking (SIW) with or without translation as in FRF.8.
  
  
• Frame Forwarding.
  
  
• ATM Frame-UNI.
  
  
• Maximum frame sizes of 4510 bytes for Frame Relay and 4096 bytes for ATM-FUNI.
  
  
• Per-virtual circuit (VC) queuing in the ingress direction (toward the cell bus). Traffic arriving at the network on a connection has a dynamically assigned buffer at the entrance to the shelf. Buffer size depends on the amount of traffic and the service-level agreement (SLA).
  
  
• Advanced buffer management. When a frame arrives, the depth of the queue for the LCN is compared against the peak queue depth scaled down by a specified factor. The scale-down factor depends on the amount of congestion in the free buffer pool. As the free buffer pool begins to empty, the scale-down factor is increased, preventing an excessive number of buffers from being held up by any single LCN.
  
  
• Multiple, priority-level queuing to support class of service on the egress. The FRSM services egress queues according to a weighted priority. The priority depends on the percentage of logical port bandwidth needed by all connections of a particular type on a port. FRSM supports
  
  
• • High-priority queue
    
    
  • Real-time variable bit rate (rt-VBR) queue
    
    
  • Common queue for non-real-time variable bit rate (nrt-VBR) and ABR connections
    
    
  • UBR queue
    
    
• Initial burst per channel. After a period of silence, the FRSM sends a configurable number of bytes at a peak service rate.
  
  
• ForeSight option (except on MGX-FRSM-HS1/B). This Cisco mechanism for managing congestion and optimizing bandwidth monitors the utilization of ATM trunks. It proactively adjusts the bandwidth for connections to avoid queuing delays and cell discards.
  
  
• Consolidated Link Layer Management (CLLM), an out-of-band mechanism to transport congestion-related information to the far end.
  
  
• Dual leaky bucket policing. Within the basic parameters such as committed burst, excess burst, and CIR, incoming frames go into two buckets: those to be checked for compliance with the committed burst rate and those to be checked for compliance with the excess burst rate. Frames that overflow the first bucket go into the second bucket. The buckets "leak" by a certain amount to allow for policing without disruption or delay of service.
  
  
• Standards-based management tools. Each FRSM supports SNMP, TFTP for configuration and statistics collection, and a command line interface. The Cisco WAN Manager application provides full graphical user interface support for connection management. The CiscoView application provides equipment management.
  
  
• MGX 8250 network management functions, including image download, configuration upload, statistics, telnet, UI, SNMP, trap, and MIBs.
  
  
• OAM features—LMI and Enhanced LMI (ANNEX A, ANNEX D, Strata LMI).
  
  
• Hot standby with 1:1 redundancy (see sections for individual FRSM card types).
  
  
• Resource partitioning at the card level or port level.
  
  
• Bit error rate test (BERT) functions for all card types except the HSSI card types. For a description of BERT on the MGX-FRSM-2T3E3, see the "Bit Error Rate Testing on an Unchannelized T3 or E3 FRSM" section. Running a BERT session on an MGX-FRSM-2CT3 or an eight-port FRSM requires a set of MGX-SRM-3T3s in the system. For a description of BERT on these cards, see the "Bit Error Rate Testing Through an MGX-SRM-3T3" section.
  
  
• User-selectable weighted fair queuing or fixed-rate queuing. The user can select either fixed-rate queuing to provide highest egress port speed while reducing quality of service or weighted fair queuing to provide maximum quality of service but slower egress port speed. This feature applies to the FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2 cards.
  
  
• Subrate support is provided for the MGX-FRSM-2T3E3 card. This feature applies to the MGX-FRSM-2T3E3 card only when used with Digital Link equipment.
  
  

---

Note   Subrate capability is not supported on Kentrox equipment.

---

• Zero CIR Service for FRSM-VHS, FRSM-8T1 and FRSM-8E1 cards.
  
  
• The features of the FRSM service modules are listed in Table 6-2.
  Table 6-2: FRSM Card Features

  Model	Features
  MGX-FRSM-2CT3	Up to 4000 user-connections Two T3 lines Up to 256 logical ports Logical port speed from DS0 56 Kbps through DS1 1.536 Mbps Support for five class of service (CoS) queues (high priority, rt-VBR, nrt-VBR, ABR, UBR) Supports Hot Standby with less than 1 second switchover using 1:1 redundancy through Y-cable redundancy (no Service Resource Module required) OAM Continuity Traffic Generation Test for use on defective PVCs
  MGX-FRSM-2T3E3	Up to 2000 user-connections Two T3 or E3 lines coinciding with two logical ports ADC Kentrox and Digital Link methods for supporting fractional T3 or E3 ports Maximum possible number of DLCIs per port by using the Q.922 two-octet header format Support for five CoS queues (high priority, rt-VBR, nrt-VBR, ABR, UBR) Supports Hot Standby with less than 1 second switchover using 1:1 redundancy through Y-cable redundancy (no Service Resource Module required) Fractional T3 speeds available through either the Digital Link or ADC Kentrox method Supports running lines at subrates when used with Digital Link equipment OAM Continuity Traffic Generation Test for use on defective PVCs
  MGX-FRSM-HS2	Up to 2000 user-connections Maximum two logical ports Two HSSI lines with configurable line speeds in multiples of 56 Kbps or 64 Kbps Selectable DTE or DCE mode for each port In DCE mode, per port clock speeds of nxT1 and nxE1 up to 52 Mbps Various DTE/DCE loopback operations Maximum possible number of DLCIs per port by using the Q.922 two-octet header format Supports Hot Standby with less that 1 second switchover using 1:1 redundancy through a Y-cable
  MGX-FRSM-HS1/B Features	Up to 200 data connections In addition to data connections, support for LMI according to ITU-T Q.333 Annex A and ANSI T1.617 Annex D OAM messaging Total card throughput of 16 Mbps Choice of the operating card as either X.21 or V.35 Maximum of 8 Mbps per line Choice of DTE or DCE mode for each line Maximum frame size of 4510 bytes One-to-one mapping between a logical port and a physical line Support for metallic (internal) loopback (ITU-T type 1) V.35-specific alarms (in addition to standard alarms such as LOS, and so on) Inactive DCD and CTS signals in DTE mode (red alarm) Inactive RTS signal in DCE mode (red alarm) Selected line type (for example, through the cnfln command on the CLI) and the attached cable are incompatible (red alarm) Disconnected cable, such as a disconnect at the far end (creating LOS, a red alarm) No cable attached (a red alarm) Support for ANSI/EIA/TIA-613-1993 and ANSI/EIA/TIA-612-1993
  Eight-Port FRSM	Eight-Port FRSM Fractional FRSMs support a single 56 Kbps or multiple 64 Kbps user-ports (FR-UNI, FR-NNI, FUNI, and Frame forwarding) per T1 or E1 line. Channelized FRSMs (AX-FRSM-8T1-C and AX-FRSM-8E1-C) support multiple 56 Kbps or Nx64 Kbps user-ports per line up to the physical line bandwidth limit. Bulk distribution for T1 only through the MGX-SRM-3T3. See the "Service Resource Module" section. Redundancy support: the MGX-SRM-3T3 can provide 1:N redundancy for T1 or E1 operation if the FRSM uses an SMB-8E1 back card. Supports OAM Loopback non intrusive test. Supports zero CIR service. Standard ABR (TM 4.0 compliant). Class of service (CoS) mapping.

  
  
  

Configuring Frame Relay Service

This section first describes how to configure the FRSM card, lines, and ports, then describes how to add connections. The descriptions are for the CLI execution of the tasks.

Note   FRSM card, lines, and ports can also be configured using the CiscoView application. Refer to the CiscoView documentation for the directions.

Note   The easiest way to add connections is by using the Cisco WAN Manager application. For full details on how to set up a connection through the Cisco WAN Manager GUI, refer to the Cisco WAN Manager Operations.

This section contains the following information:

• Configuring the FRSM Cards, Lines, and Ports
  
  
• Adding a Frame Relay Connection
  
  
• Establishing the BPX 8600-to-BPX 8600 Series Segment
  
  
• Test Commands for FRSM Cards
  
  
• Support for Alarm Reporting
  
  
• Bit Error Rate Testing on an Unchannelized T3 or E3 FRSM
  
  

Configuring the FRSM Cards, Lines, and Ports

This section describes how to configure card-level parameters—including Y-cable redundancy, where applicable, as well as physical lines and logical ports on the FRSM-series cards.

Step 1   If necessary, modify the resource partitioning for the whole card by entering the cnfcdrscprtn command. You can view resource partitioning by entering the dspcdrscprtn command.

cnfcdrscprtn <number_PAR_conns | number_PNNI_conns | number_TAG_conns>

For example, you could reserve 300 connections for each controller on the FRSM with

cnfcdrscprtn 300 300 300

Step 2   If the physical line is not yet active, enter the addln command to activate it. The only argument addln takes is the line number.

Step 3   If necessary, modify a line on the MGX-FRSM-2CT3, MGX-FRSM-HS2, MGX-FRSM-HS1/B, AX-FRSM-8T1, or AX-FRSM-8E1 by entering the cnfln command.

To change the line parameters on an MGX-FRSM-2CT3 or MGX-FRSM-2T3E3, enter cnfds3ln. Note that both cnfln and cnfds3ln apply to the MGX-FRSM-2CT3 but apply to different features. Refer to the Cisco MGX 8800 Series Command Reference for the syntax of the line modification commands on all cards except the MGX-FRSM-HS1/B.

The syntax for cnfln on the MGX-FRSM-HS1/B is:

cnfln <line_num> <line_type> <line_rate>

The possible errors for the cnfln command are

• One or more parameters are invalid.
  
  
• Line does not exist (has not been added).
  
  
• Loopback or BERT is on.
  
  
• Active port already exists on this line.
  
  

Step 4   If the logical port does not exist or is not the appropriate type (Frame Relay, FUNI, or frame forwarding), enter the addport command to create the appropriate type of port. If the logical port already exists and needs no modification (cnfport), you can add connections by performing the tasks in the "Adding a Frame Relay Connection" section. The parameters for addport depend on the type of FRSM.

For MGX-FRSM-2T3E3 or MGX-FRSM-HS2

addport <port_num> <line_num> <port_type>

For an MGX-FRSM-2CT3

addport <port_num> <line_num> <ds0_speed> <begin_slot> <num_slot> <port_type>

For MGX-FRSM-HS1/B

cnfbctype is the command to change a 12-in-1 back card type between support for x.21 and v.35.

addport <port_num> <port_type>

For AX-FRSM-8T1 and AX-FRSM-8E1:

addport <port_num> <line_num> <ds0_speed> <begin_slot> <num_slot> <port_type>

Step 5   Modify as needed the signaling on a port by entering cnfport.

cnfport <port_num> <lmi_sig> <asyn> <elmi> <T391> <T392> <N391> <N392> <N393>

Step 6   Configure resources for the port as needed by entering cnfportrscprtn. To see the partitioning, enter dspportrscprtn. The description has a high- and low-bandwidth version:

cnfportrscprtn <port_num> <controller-name> <conn ID range> <percent bandwidth> [number of conns]

---

Note   The following step applies to Y-cable redundancy for the MGX-FRSM-2T3E3. For 1:N redundancy on the eight-port FRSMs, see the "Redundancy Support by the MGX-SRM-3T3/C" section.

---

Step 7   Optionally, configure Y-cable redundancy if you have connected the lines of adjacent MGX-FRSM-2T3E3 cards through a Y-cable. The applicable commands are addred, dspred, and delred. These commands run on the PXM1 rather than the service module, change to the PXM1 CLI to enter them:

addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Enter the display commands dspcd, dspln, and so on to check the configuration and status.

Adding a Frame Relay Connection

The user should add a Frame Relay connection according to the following steps for adding a standard connection or a management connection in the form of either a DAX con or a three-segment connection. See the "Rules for Adding Connections" section.

Step 1   Add a connection by entering addcon. If the application requires the NSAP form for the endpoint, enter addchan as described in the command reference.

The system automatically assigns the next available channel number, so the addcon command does not require it. However, some related commands require a channel number. To see the channel number after you add a connection, enter dspcons.

On the FRSM-VHS cards (2CT3, 2T3E3, or HS2):

addcon <port> <DLCI> <cir> <chan_type> <egress_service_type> [CAC] <controller_type> <mastership> [connID] <controllerID>