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>

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

addcon <port> <DLCI> <cir> <chan_type> [CAC] <controller_type> <mastership> <remoteConnID> <serv_type>

For MGX-FRSM-HS1/B:

addcon <port_number> <DLCI> <CIR> <chan_type> <CAC> <Controller_type> <mastership> <connID>

Step 2   Modify a connection as needed by executing cnfcon. See the command line Help or the command reference for the parameters for individual card types.

Step 3   If necessary, modify the CLP and congestion indicator fields by using cnfchanmap. Use dspchanmap to check this configuration for a connection.

cnfchanmap <chan_num> <chanType> <FECN/EFCI> <DE to CLP> <CLP to DE>

Step 4   To check statistics for a connection, enter dspchstats as needed.

Step 5   Enter cnfchanstdabr to configure the parameters for standard ABR (TM 4.0), if they are not properly configured:

cnfchanstdabr <Port.DLCI/CHAN_NUM> <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.
  
  
• Standard ABR does not support Explicit Rate (ER) marking of RM cells.
  
  
• cnfconabrrates is used to modify the rates:
  Usage: cnfconabrrates <Port.Vpi.Vci/Chan_Num> <mcr> <pcr> <icr>
  
  
• cnfconabrparams is used to modify the parameters.
  Usage: cnfconabrparams <Port.Vpi.Vci/Chan_num> <ABRType> <rif> <rdf> <nrm> <trm> <tbe> <rtt> <adtf>
  
  

Step 6   Enter cnfchanfst to configure the parameters for ForeSight ABR, if necessary.

cnfchanfst <Port.DLCI/CHAN_NUM> <ForeSight enable> <mir> <pir> <uir>

Establishing the BPX 8600-to-BPX 8600 Series Segment

For a three-segment connection, establish a BPX 8600-to-BPX 8600 series (middle) segment. This type of connection is used to establish feeder connections across a BPX network. To establish such a connection, execute the addcon command at one of the BPX 8600 series nodes, as follows.

• For slot and port number—Specify the slot and port of the BXM connected to the MGX 8250 node.
  
  
• For VPI and VCI values—Specify the VPI and VCI at the endpoint on the PXM1 card.
  
  
• For nodename—Specify the name of the BPX 8600 series switch at the far end of the connection.
  
  
• For remote channel—Specify the slot and port number of the BXM port attached to the MGX 8850 node at the far end. Specify the VPI as the slot number of the remote MGX 8850 FRSM connected to the BPX 8600 series switch, and specify the VCI as the LCN of the Frame Relay connection at the remote MGX 8850 node.
  
  
• For connection type—Specify ATFST if the ForeSight feature is operating; if ForeSight is not operating, specify ATFR.
  
  

Specify the other addcon command bandwidth parameters, such as MCR, PCR, %Util, and so on.

• Minimum cell rate (MCR) is only used with the ForeSight feature (ATFST connections).
  
  
• MCR and peak cell rated (PCR) should be specified according to the following formulae:
  
  
• • MCR=CIR *3/800 cells per second.
    
    
  • PCR=AR * 3/800 cells per second but less than or equal to 6000.
    AR=Frame Relay port speed in bps. For example,
    
    

The above MCR and PCR formulas are predicated on a relatively small frame size of 100 octets. Smaller frame sizes can result in worst-case scenarios, as shown in the following table:

The %Util parameter should be set to the same value as that used for the Frame Relay segments of the connection.

Test Commands for FRSM Cards

To check the state of cards, lines, ports, queues, and connections, enter the display commands (dsp...) and addchanloop. The following commands are available for testing the FRSM cards (refer to the Cisco MGX 8800 Series Command Reference for descriptions):

• addlnloop, cnflnloop, and dellnloop are line-level, diagnostic commands that require the service level user privilege.
  
  
• addchanloop and delchanloop are standard user commands for looping on a channel.
  
  
• tstcon checks the integrity of a connection.
  
  
• tstdelay measures the round-trip delay on a connection.
  
  
• cnftrafficgen enables/disables traffic-generation tests on a per LCN basis. Enter the dsptrafficgen command to display the traffic-generation test results.
  
  

Support for Alarm Reporting

The FRSM cards support card and line-level alarm reporting. Use the CiscoView application or the CLI to view current alarms. The CLI commands are dspalmcnt, dspalm, and dspalms. These commands require a switch, either "-x21 or "-hs1" whichever is valid, to identify the interface type. Refer to the Cisco MGX 8800 Series Command Reference for syntax and alarm descriptions.

Bit Error Rate Testing on an Unchannelized T3 or E3 FRSM

The MGX 8250 shelf can perform a bit error rate test (BERT) on one active line at a time on the MGX-FRSM-2T3E3. This type of testing disrupts service because it requires the tested path to be in loopback mode. You can configure a BERT session and perform related tasks through the CiscoView application or the CLI.

The MGX 8250 bus structure supports one BERT session per upper or lower bay of the card cage, so the shelf can run a maximum of two sessions at once. When you specify the target slot through the CiscoView application or the acqdsx3bert command on the CLI, the system determines if a BERT configuration already exists in the bay that has the specified slot. If no BERT configuration exists in the bay, the display presents a menu for the BERT parameters.

The CLI commands (whose functions correspond to CiscoView selections) are

• acqdsx3bert to determine if other BERT sessions exist in the bay
  
  
• cnfdsx3bert to specify a pattern for the BERT test
  
  
• startdsx3bert to start a BERT test (after resetting BERT counters)
  
  
• moddsx3bert to inject multi-rate errors into the BERT bit stream
  
  
• dspdsx3bert to display the parameters and results of the current test
  
  
• deldsx3bert to end the current test (and retain the values in the BERT counters)
  
  

Refer to the Cisco MGX 8250 Wide Area Edge Switch Command Reference for command details.

Note   When a BERT session begins, all the connections on the line go into alarm and return to normal when you end the test. Consequently, the test may result in a large number of traps and other types of traffic (such as AIS).

Circuit Emulation Service Module for T3 and E3

The main function of the Circuit Emulation Service Module (CESM) is to provide a constant bit rate (CBR) service. The CESM converts data streams into CBR AAL1 cells according to the CES-IS specifications of the ATM Forum for unstructured transport across an ATM network. Unstructured transport means the CESM does not interpret or modify framing bits, so a high-speed CESM creates a single data pipe The most common application is legacy support for digitized voice from a PBX or video from a codec. Using circuit emulation, a company can expand its data communication network without specific voice or video cards to meet its voice or teleconferencing requirements.

The higher speed CESM uses a T3 or E3 line. The card set consists of an MGX-CESM-T3 or MGX-CESM-E3 front card and either a BNC-2T3 or BNC-2E3 back card. In this CESM application, only one line on the two-port back card is operational. Furthermore, it supports one logical port and one logical connection (as a data pipe) on the line and runs at the full T3 or E3 rate. Although the typical connection setup is the three-segment connection across an ATM network, the CESM can support a DAX connection. Up to 26 CESM card sets can operate in an MGX 8250 shelf.

Features

The MGX-CESM-T3 or MGX-CESM-E3 support the following features:

• Unstructured data transfer: T3 CESM 44.736 Mbps (1189980 cells per second) for T3, or 34.368 Mbps (91405 cells per second) for E3
  
  
• Synchronous timing by either a local clock sourced on the PXM1 or loop timing (transmit clock derived from receive clock on the line)
  
  
• 1:1 redundancy is through a Y-cable
  
  
• Programmable egress buffer size (in the form of cell delay variation)
  
  
• Programmable cell delay variation tolerance (CDVT)
  
  
• Per VC queuing for the transmit and receive directions
  
  
• An idle code suppression option
  
  
• Bit count integrity when a lost AAL1 cell condition arises
  
  
• Alarm state definitions per G.704
  
  
• Trunk conditioning by way of framed AIS for T3 and unframed, alternating 1s and 0s for E3
  
  
• On-board bit error rate testing (BERT)
  
  

Cell Delay Treatment

You can configure a tolerable variation in the cell arrival time (CDVT) for the receive buffer. After an underrun, the receiver places the contents of the first cell to arrive in a receive buffer then plays it out at least one CDVT value later. The maximum cell delay and CDVT (or jitter) are

• For T3
  
  
• • Cell delay of 4 msec
    
    
  • CDVT of 1.5 msec in increments of 125 microseconds
    
    
• For E3
  
  
• • Cell delay of 2.9 msec
    
    
  • CDVT of 2 msec in increments of 125 microseconds
    
    

Error and Alarm Response

When it detects a loss of signal (LOS) alarm, the CESM notifies the connected CPE in the upstream direction after an integration period. The CESM continues to emit cells at the nominal rate but sets the ATM cell payload with an appropriate data pattern as specified by the ATM Forum CES V2.0 specification. Also, an OAM cell with RDI code goes to the far end to indicate out-of-service. The differences between the types are shown in Table 6-4.

Configuring Service on a T3 or E3 CESM

This section first describes the steps for configuring the card, line, and port-level parameters for an MGX-CESM-T3 and MGX-CESM-E3. It then describes how to add a connection. See the "Tasks and Rules to Configure Cards and Services" section for background information on these types of tasks. Use either the CLI or the CiscoView application to set up the card and line parameters. Use either the CLI or the Cisco WAN Manager application to add connections. The fundamental tasks and applicable CLI commands appear in the following list. For a complete list of CLI commands that apply to the CESM cards, enter the Help command on the CLI of the card or refer to the tables at the front of the Cisco MGX 8000 Series Command Reference.

• Optionally configure Y-cable redundancy at the card level (addred command).
  
  
• Optionally modify resource partitioning at the card level (cnfcdrscprtn command)
  
  
• Activate a physical line (addln on the CLI) and optionally configure the line (cnfln command) for line coding, line length, and clock source
  
  
• Activate the functioning of the logical port on a physical line (addport command)
  
  
• Optionally modify resource partitioning at the port level (cnfportrscprtn command)
  
  
• Add the connections by entering addcon command (or addchan command if NSAP addressing is necessary)
  
  
• Configure the connection for CDVT, cell loss integration period, and egress buffer size by entering cnfcon command (or cnfchan command if NSAP addressing is necessary)
  
  

Configuring the Card, Lines, and Ports

This section describes how to configure parameters for the card, line, and port through the CLI. If you use the CiscoView application, refer to the CiscoView documentation. The steps are:

Step 1   Enter addln <line number>

where line number is 1. You can modify line characteristics with cnfln.

Step 2   Optionally enter cnfln to modify line characteristics:

cnfln <line_num> <line_code> <line_len> <clk_src>

Step 3   Enter dspln or dsplns to check the line. For dspln, the valid line number is 1.

Step 4   Enter addport to create a logical port

addport <port_num> <line_num>

Step 5   Enter cnfportrscprtn to configure resources at the port level as needed

cnfportrscprtn <port_num> <controller_name>

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

addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Adding and Modifying Connections

Use either the Cisco WAN Manager application or the CLI to add or modify connections. If you use the Cisco WAN Manager application, refer to the Cisco WAN Manager Operations Guide.

This section describes how to add a connection to a PXM1 in a stand-alone shelf according to the rules for a standard connection or a management connection in the form of either a three-segment connection or a DAX con. See the "Rules for Adding Connections" section. The preferred command is addcon. If the application requires NSAP addressing, use addchan to add the connection and cnfchan if you need to modify it. Refer to the command reference for the syntax.

To add a connection perform the following steps.

Step 1   Add a connection by entering addcon. (Alternatively, you can enter addchan if your application requires the NSAP format of end-point specification.) Enter addcon at both ends of the connection—unless the remote end-point is on port 34 of a PXM1 (see the note at the end of this step).

The syntax for addcon is

addcon <port_num> [mastership [remoteConnId] ]

---

Note   For the channel number, the system always returns the number 32 for the high-speed CESM. If you enter dspchan, use channel number 32 to see details about the channel (or dspchans—and no arguments—to see high-level details about the channel). In contrast, the dspcon command takes the port number 1 to identify the connection even though it shows the same information as dspchan.

---

Step 2   Optionally, you can enter cnfcon to modify the connection.

cnfcon <port_num> <CDVT> <CellLossIntegPeriod> <bufsize>

Step 3   Optionally, you can enter cnfswparms on a BPX 8600 series switch to configure connection parameters for the network segment of a three-segment connection. For a stand-alone application, use whatever means are supported by the backbone switches.

cnfswparms <chan_num> <mastership> <vpcflag> <conn_service_type> (=cos) <route_priority> <max_cost> <restrict_trunk_type> <pcr> <mcr> <pct_util>

Bit Error Rate Testing on a T3 or E3 CESM

An active MGX-CESM-T3 or MGX-CESM-E3 can perform a bit error rate test (BERT). Each of these cards contains its own BERT controller, so BERT sessions can run on any number of these cards in the system. However, only one user at a time can run BERT on a card. BERT disrupts service because it requires the tested path to be in loopback mode.

The CLI commands (whose functions correspond to CiscoView selections) appear in the following list. The correct order of task execution is crucial for obtaining valid results. With the exception of dspdsx3bert, you must enter the commands in the order they appear in the following list. You can enter dspdsx3bert before, during, or after a session. Because the order command sequence is crucial, read the command descriptions whether you use the CiscoView application or the CLI.

Refer to the Cisco MGX 8000 Series Command Reference for command details.

Note   When a BERT session begins, all the connections on the line go into alarm and return to normal when you end the test. Consequently, the test may result in a large number of traps and other types of traffic (such as AIS).

Eight-Port Circuit Emulation Service Modules

The main function of the Circuit Emulation Service Module (CESM) is to provide a constant bit rate (CBR) circuit emulation service by converting data streams into CBR AAL1 cells for transport across an ATM network. The CESM supports the CES-IS specifications of the ATM Forum.

The 8-port CESM lets you configure individual physical ports for structured or unstructured data transfer. The card sets consist of an AX-CESM-8T1 or AX-CESM-8E1 front card and one of the following back cards:

• RJ48-8T1
  
  
• R-RJ48-8T1 for supporting 1:N redundancy through the optional MGX-SRM-3T3/C
  
  
• RJ48-8E1
  
  
• R-RJ48-8E1 for supporting 1:N redundancy through the optional MGX-SRM-3T3/C
  
  
• SMB-8E1
  
  

Structured Data Transfer

If you configure an individual port for structured data transfer, the 8-port CESM supports:

• Synchronous timing.
  
  
• Superframe or Extended Superframe for T1.
  
  
• Nx64 Kbps, fractional DS1/E1 service (contiguous time slots only). You can map an
  Nx64 Kbps channel to any VC.
  
  
• CAS robbed bit for T1 (ABCD for ESF and SF frames) and CAS for E1 (channel 16).
  
  
• CCS channel as a transparent data channel.
  
  
• Choice of partial-fill payload sizes.
  
  
• Idle detection and suppression for 64 Kbps CAS connections.
  
  
• Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
  
  
• BERT functionality with loopback 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.
  
  

Unstructured Data Transfer

If you configure an individual port for unstructured data transfer, the 8-port CESM supports:

• Synchronous or asynchronous timing at T1 (1.544 Mbps) or E1 (2.048 Mbps) rates. For asynchronous timing, you can select its basis as either SRTS and adaptive clock recovery.
  
  
• The special port type framingOnVcDisconnect. This port type prevents a remote-end CPE from going to LOF by placing a line in remote loopback mode when the CESM determines that a connection deletion or suspension occurred at the network-side ATM interface.
  
  
• Ability to detect and display a yellow alarm for the ESF framing on a T1 line.
  
  
• Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
  
  
• Bit error rate test (BERT) functionality with loopback pattern generation and verification on individual lines. For a description of BERT functions, see the "Bit Error Rate Testing Through an MGX-SRM-3T3" section.
  
  

Cell Delay Treatment

For each connection, you can configure a tolerable cell delay variation time (CDVT) according to the expected reliability of the route. The CDVT applies to the receive buffer. After an underrun, the receiver places the contents of the first cell to arrive in a receive buffer then plays it out at least one CDVT value later. For each VC, the maximum cell delay and CDVT (or jitter) are

• For T1
  
  
• • Cell delay of 48 msec
    
    
  • CDVT of 24 msec in increments of 125 microseconds
    
    
• For E1
  
  
• • Cell delay of 64 msec
    
    
  • CDVT of 32 msec in increments of 125 microseconds
    
    

Redundancy Support for the Eight-Port CESM

The AX-CESM-8T1 and AX-CESM-8E1 can have 1:N redundancy support but with some variations between the T1 and E1 modes of operation. The type of redundancy and the type of back card are interdependent. See the "Service Resource Module" section for more details. Some general observations are:

• With an RJ48-8T1, an MGX-SRM-3T3 can provide 1:N redundancy through the distribution bus or the redundancy bus.
  
  
• With an RJ48-8E1, an MGX-SRM-3T3 can provide 1:N redundancy through the redundancy bus.
  
  

Back card requirements for the MGX-SRM-3T3 and service modules vary, as follows:

• If you are using the MGX-SRM-3T3 for bulk distribution of T1 channels, the CESMs do not use back cards, but each MGX-SRM-3T3/C must have an MGX-BNC-3T3-M back card. (Bulk distribution is not available for E1 operation.)
  
  
• If the MGX-SRM-3T3/C supports T1 or E1 1:N redundancy through the redundancy bus (no bulk distribution), the MGX-SRM-3T3/C does not require a back card, but the N CESM primary cards must have one redundant version of the back card.
  
  

Error and Alarm Response

When it detects a loss of signal (LOS) alarm, the CESM notifies the connected CPE in the upstream direction after an integration period. The CESM continues to emit cells but sets the ATM cell payload with an appropriate data pattern as specified by the ATM Forum CES V2.0 specification. Also, an OAM cell with RDI code goes to the far end to indicate out of service. See (Table 6-5).

Configuring Service on an Eight-Port CESM

This section describes the steps for setting up a CESM and adding connections. The maximum number of connections is 248 on the MGX-CESM/B-8E1 and 192 on the MGX-CESM/B-T1. Use either the CLI or the Cisco WAN Manager application to set up a CESM and add connections. The following list shows the fundamental tasks and applicable CLI commands:

• Optionally configure redundancy at the card level (addred and possibly addlink on the PXM1)
  
  
• Optionally modify resource partitions at the card level (cnfcdrscprtn)
  
  
• Activate a physical line (addln) and optionally configure the line (cnfln)
  
  
• Create logical ports for structured data transport on a physical line (addport)
  
  
• Optionally modify resource partitions at the port level (cnfportrscprtn)
  
  
• Add connections by entering addcon (or addchan if NSAP addressing is necessary)
  
  

For CESM-related commands, see the list of service module commands at the beginning of the Cisco MGX 8000 Series Command Reference. Also, each command description in the command reference lists related commands. For example, it shows display commands that relate to addition commands.

Configuring the Card, Lines, and Ports

This section describes how to configure parameters for the card, lines, and ports through the CLI. If you use the CiscoView application, refer to the CiscoView documentation. On the CLI, the command sequence is:

Step 1   Add the line by entering the addln <line number> command.

where line number is in the range 1-8. You can modify line characteristics with cnfln.

Step 2   Optionally execute cnfln to modify line characteristics from the defaults. (Use dspln or dsplns to check). The syntax for cnfln is:

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

Step 3   Create a logical port with addport if the application requires N x 64Kbps channels:

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

Step 4  

Step 5   Configure resources at the port level as needed by executing cnfportrscprtn:

cnfportrscprtn <port_num> <controller_name>

Configuring Bulk Distribution and Redundancy

You can configure either bulk distribution alone, redundancy alone, or both of these features according to the restrictions in the "Redundancy Support for the Eight-Port CESM" section. On the CLI of the PXM1, execute addlink for bulk distribution (T1 only) before you enter addred for redundancy. To configure bulk distribution enter addlink to create the links:

addlink <T3 line number> <T1 line number> <Target Slot number> <Slot line number>

Execute addred:

addred <redPrimarySlotNum> <redSecondarySlotNum> <RedType>

Adding and Modifying Connections

Use either the Cisco WAN Manager application or the CLI to add or modify connections. If you use the WAN Manager application, refer to the Cisco WAN Manager Operations Guide.

This section describes how to add a connection to a PXM1 in a stand-alone shelf according to the rules for a standard connection or a management connection in the form of either a three-segment connection or a DAX con. See the "Rules for Adding Connections" section. The preferred command is addcon. If the application requires NSAP addressing, enter addchan to add the connection and cnfchan if you need to modify it. Refer to the command reference for the syntax. Perform the following steps to add a connection

Step 1   Add a connection through the preferred command addcon. (Alternatively, you can use addchan if your application requires the NSAP format of end-point specification.)

Enter the addcon command at both ends of the connection—unless the remote end-point is on port 34 of a PXM1 (see the note at the end of this step). The maximum number of connections for the AX-CESM-8T1 is 248 and 192 for the AX-CESM-8E1. Note that because you can add only one connection per port, addcon does not request a connection number.

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.

The syntax for addcon is:

addcon <port_num> <sig_type> <partial_fill> <cond_data> <cond_signalling> [controller_type] [mastership] [remoteConnId]

Step 2   Optionally, you can use cnfcon to modify an individual connection. This command requires a channel number. If you add a connection by using addcon, you do not need to specify a channel number because the system automatically uses the next available number. To obtain the channel number for cnfcon, execute dspcons.

cnfcon <port_num> <CDVT> <CLIP> <bufsize> <cbrclkmode> <IdleSuppEnable> <ForceSuppression>

Step 3   Optionally, you can configure connection parameters for the network segment of a three-segment connection:

cnfswparms <chan_num> <mastership> <vpcflag> <conn_service_type> (=cos)
<route_priority> <max_cost> <restrict_trunk_type> <pcr> <mcr> <pct_util>

Service Resource Module

This section describes how to use the features of the T3 version of the Service Resource Module (MGX-SRM-3T3/C). This multipurpose card can provide:

• Demultiplexing of T3 service called bulk distribution.
  
  
• 1:N redundancy support for service modules with T1 or E1 lines.
  
  
• Bit error rate testing (BERT) for T3, E3, T1, E1, fractional T1, or subrate operation with loopback 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.
  
  

An MGX-SRM-3T3/C installation requires at least one card set in the upper bay of the card cage and one card set in the lower bay. Each set services one half of the backplane. The PXM1 in slot 7 controls the SRMs in slots 15 and 31. The PXM1 in slot 8 controls the redundant SRMs in slots 16 and 32. If the shelf has SRMs with redundant PXM1s, the SRMs must occupy all the reserved slots for this feature—15, 16, 31, and 32.

Configuring Card and Line Parameters

You can configure card- and line-level parameters for an SRM through the CiscoView application or the CLI on the PXM1 (not the SRM itself). For descriptions of the commands, refer to the Cisco MGX 8250 Wide Area Edge Switch Command Reference. The CLI commands that apply to the SRM are:

• addln
  
  
• delln
  
  
• cnfln
  
  
• dspln
  
  
• dsplns
  
  
• addlmiloop
  
  
• dellmiloop
  
  
• cnfsrmclksrc
  
  
• dspsrmclksrc
  
  
• dspalm
  
  
• dspalms
  
  
• dspalmcnt
  
  
• clralmcnt
  
  
• clralm
  
  
• dspalmcnt
  
  
• addlink
  
  
• dsplink
  
  
• dellink
  
  
• addred
  
  
• dspred
  
  
• delred
  
  

Bulk Distribution for T1 Service

The MGX-SRM-3T3/C supports a demultiplexing function called bulk distribution. With bulk distribution, the MGX-SRM-3T3/C converts traffic from its T3 lines to T1 channels and sends the data streams across the distribution bus to the appropriate service modules. The benefit of this feature is that the number of T1 cables and back cards is greatly reduced. Applicable service modules are the MGX-AUSM/B-8T1, AX-FRSM-8T1, and AX-CESM-8T1.

At its MGX-BNC-3T3-M back card, the MGX-SRM-3T3/C connects to an external multiplexer. The multiplexer connects to the T1 lines from user-equipment and places the data streams on T3 lines to the MGX-SRM-3T3/C. Each T3 line can contain 28 T1 channels. An individual MGX-SRM-3T3/C can support 10 card slots, so the maximum number of T1 channels it can process is 80.

Linking the MGX-SRM-3T3/C to a destination card causes the shelf to take CPE traffic through the MGX-SRM-3T3/C rather than the T1 card's line module. Linkage is a card-level condition. If you link just one T1 channel on a service module to the MGX-SRM-3T3/C, the back card on the service module becomes inoperative, so you must link all other T1 ports on that service module to the MGX-SRM-3T3/C if you want them to operate. Linking T1 ports into a group does not form an N X T1 channel. Each T1 channel remains a distinct T1 channel. Furthermore, a group belongs to one slot, so it cannot include T1 channels belonging to another card.

For a description of how the MGX-SRM-3T3/C supports redundancy for linked channels, see the "Redundancy Support by the MGX-SRM-3T3/C" section.

Before configuring bulk distribution on an SRM, perform the following tasks:

To link T1 ports on a service module to a T3 line on an MGX-SRM-3T3/C:

• Enter addlink on the active PXM1. Related commands are dsplink and dellink.
  addlink <T3 line number> <T1 slot> <NumberOfT1s> <TargetSlotLineNum>
  
  

Redundancy Support by the MGX-SRM-3T3/C

The MGX-SRM-3T3/C can provide redundancy to service modules with T1 or E1 lines. For E1 or T1 modules, it can provide redundancy through the redundancy bus. For T1 modules only, it can provide redundancy through the distribution bus. The redundancy and distribution buses impose different requirements, but the common requirement is that all primary and secondary cards supported by a particular MGX-SRM-3T3/C must reside on the same level of the card cage as that SRM.

The need for back cards and the choice of bus for redundancy support depends on whether the MGX-SRM-3T3/C must provide bulk distribution:

• With bulk distribution, the T1 service modules do not use back cards. The MGX-SRM-3T3/C uses the distribution bus to support redundancy.
  
  
• Without bulk distribution, the supported service modules must have back cards. The redundant card set requires a special redundancy back card (R-RJ48-8T1 or R-RJ48-8E). The primary card sets use standard back cards (RJ48-8T1 or RJ48-8E1).
  
  

With redundancy provided by the SRM, no Y-cables are necessary because the MGX-SRM-3T3/C itself passes the traffic to the redundant front card if a failure necessitates switchover. Conversely, any card with 1:1 redundancy supported by Y-cabling does not require an SRM. For example, the FRSM-VHS cards have 1:1 redundancy through a Y-cable. The MGX-SRM-3T3/C redundancy feature is particularly important for cards that do not have Y-cable redundancy—the T1 and E1 service modules.

Configuring Redundancy Through the Redundancy Bus

For redundancy that utilizes the redundancy bus, the characteristics are

• Both the primary and the redundant front cards must have back cards. The secondary back card must be the version specifically designed to be redundant cards. Examples are the R-RJ48-8T1 and R-RJ48-8E1, where the first "R" means redundant.
  
  
• An MGX-SRM-3T3/C can redirect traffic for only one failed card at a time regardless of the number of redundant groups you have configured to rely on that MGX-SRM-3T3/C for redundancy.
  
  

Perform the following steps to configure redundancy through the redundancy bus.

Step 1   Execute addred on the active PXM1:

addred <redPrimarySlotNum> <redSecondarySlotNum> <RedType>

where:

Step 2   Check the redundancy status for all cards by entering the dspred command.

To remove redundancy, enter the delred command.

Configuring Redundancy Through the Distribution Bus

Redundancy by way of the distribution bus applies to T1 channels you linked for bulk distribution. For a redundancy configuration on the MGX-SRM-3T3/C that utilizes the distribution bus note the following items.

• No back cards are necessary.
  
  
• The MGX-SRM-3T3/C can support multiple switchovers for different 1: N redundancy groups.
  
  
• Slots 9, 10, 15, or 26 are not supported.
  
  

Before you specify redundancy with bulk distribution, linkage must exist between a T3 line on the MGX-SRM-3T3/C and a primary service module with the T1 lines. No linkage should exist on the secondary service module. To configure redundancy through the CLI:

Step 1   Execute addred on the active PXM1:

addred <redPrimarySlotNum> <redSecondarySlotNum> <RedType>

where:

Step 2   Check the redundancy status for all cards by entering the dspred command.

To remove redundancy, enter the delred command.

Bit Error Rate Testing Through an MGX-SRM-3T3

The MGX 8250 shelf can perform a bit error rate test (BERT) on an active line or port. This type of testing disrupts service because a BERT session requires the tested path to be in loopback mode. In addition, the pattern test replaces user-data in the path with the test pattern. The applicable line types and variations for a DS1 are

• T1 or E1 line
  
  
• Fractional portions of a T1 line that add up to a DS1
  
  
• Single 56 Kbps or 64 Kbps DS0
  
  
• DS0 bundle consisting of Nx64 Kbps DS0s
  
  

With a set of MGX-SRM-3T3/C cards in the system, you can initiate a BERT session on an MGX-FRSM-2CT3 or any eight-port service module. (In contrast, the MGX-FRSM-2T3E3, MGX-CESM-T3, and MGX-CESM-E3 do not use the MGX-SRM-3T3/C for BERT. See the sections for these service modules in this chapter for applicable BERT.)

The MGX 8250 bus structure supports one BERT session per upper or lower bay, so the shelf can run a maximum of two sessions at once. When you specify the target slot through the CiscoView application or the CLI, the system determines if a BERT configuration already exists in that bay. After the system determines that no BERT configuration exists in the applicable bay, the display presents a menu for the BERT parameters.

The CLI commands (whose functions correspond to CiscoView selections) are

• cnfbert to configure and start a test
  
  
• modbert to inject errors into the BERT bit stream
  
  
• dspbert to display the parameters and results of the current test
  
  
• delbert to end the current test
  
  

---

Note   When a BERT session begins, all connections on a line or port go into alarm and return to normal when the test ends. Consequently, the test may result in other types of traffic (such as AIS).

---

During configuration, the parameter display or menu items depend first on the card type and whether the test medium is a physical line or a logical port. Subsequent choices are test type, test patterns, loopback type, and so on. Refer to the Cisco MGX 8250 Wide Area Edge Switch Command Reference for details on cnfbert and the other BERT commands. The concatenation of menu to menu is extensive, so this section contains tables of menu selections based on the card types and the test type.

The test type can be pattern, loopback, or DDS seek. The choice of test type leads to further menu displays. Following the tables of menu choices, the remaining sections define the parameters in these menu choices.

• For AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3, see Table 6-6 pattern tests and Table 6-7 for loopback tests.
  
  
• For AX-FRSM-8E1 and AX-CESM-8E1, see Table 6-8 for pattern tests and Table 6-9 for loopback tests.
  
  
• For MGX-AUSM-8T1, see Table 6-10 for pattern tests and Table 6-11 for loopback tests.
  
  
• For MGX-AUSM-8E1, see Table 6-12 for pattern and Table 6-13 loopback tests.
  
  

Pattern Test Options

The pattern test options consist of the device to loop and the pattern. This section lists the device options and patterns that appear in the menus. See the preceding tables. The device to loop options identify the type of device that participates in the test.

• noLatch is a device that does not latch the data. It can be:
  
  
• • Nonlatching office channel unit (OCU) that consists of one device
    
    
  • Nonlatching OCU that consists of a chain of devices
    
    
  • Nonlatching channel service unit (CSU)
    
    
  • Nonlatching data service unit (DSU)
    
    
• Latch is a device that can latch the data. It can be:
  
  
• • Latching DS0-DP drop device
    
    
  • Latching DS0-DP line device
    
    
  • Latching office channel unit (OCU)
    
    
  • Latching channel service unit (CSU)
    
    
  • Latching data service unit (DSU)
    
    
  • Latching HL96 device
    
    
• in-band/ESF
  
  
• v54 is a polynomial loopback
  
  
• metallic is a local loopback within the service module and does not involve an external device.
  
  

The available patterns are

Loopback Test Options

The loopback tests do not monitor the integrity of the data but rather the integrity of the path. The type of loopback indicates the direction of test data transmission. The choices are

• far end means the service module transmits data to the CPE and receives the data back
  
  
• remote means the service module receives data from the CPE and loops back to the CPE
  
  
• metallic means the service module receives data from the network and loops it back to the network
  
  

Online Diagnostics Test

The Online Diagnostics are used to test components on the PXM1 and SRM modules of the MGX 8250 while the shelf is running. Connections, states, and tasks are not affected by the tests.

The diagnostic test is invoked from the active PXM1. If a standby PXM1 exists and is in standby state, it will also be tested. When the test is run, each component is checked and the results are presented on the screen. Results are also saved to a log file.

Automatic Switchover

The Online Diagnostic command (oldiags) includes an option to automatically switch operations from the active PXM1 to the standby PXM1 if a major problem is detected. This behavior is possible only when a standby PXM1 is installed and no errors are detected on the standby PXM1 during the test.

Alarms

If a failure is detected and an automatic switchover is not performed, a major alarm is set. This alarm is displayed in the card Major Alarm Bit Map field when the dspcd command is entered. The alarm message indicates the failed PXM1 by slot.

Note   Certain hardware failures prevent alarms from being set. If this occurs, the log files and screen display should be used to determine if a failure has occurred.

Log Files

Each time the diagnostics are run, the results are logged in a file on the PXM1 drive. If a standby PXM1 exists, a separate log file is written to that disk and must be viewed separately.

• The log files on the active PXM1 also indicate if a failure occurred on the standby PXM1.
  
  
• Only the three most recent log files are retained. If three files exist and a new test is run, the oldest log file is overwritten by the new file.
  
  
• Log files are named onlinediag.MONTHDAY_hh:mm. The files are saved in C:DIAG.
  
  
• If a failure occurs, a message is also added to the shelf event log.
  
  

Commands to Operate the Online Diagnostics

The following commands are used to operate the Online Diagnostics:

oldiags <debug_level> <switch_enable>

This command runs the diagnostics on both the active PXM1 and the standby PXM1 (if available). Two options are available for this command. If the command is entered without specifying any options, the default values are automatically used. If options are used, they must be entered in the order shown:

• <debug_level> This option determines the amount of information to be displayed on the screen. This detail is shown on the screen only. Log files contain a standard set of information and are not affected by this option.
  
  
• • debug_level is a value between 0 and 3.
    
    
  • 0 (the default) displays the least amount of detail.
    
    
  • 3 displays the most detail.
    
    
• <switch_enable> enables or disables automatic switchover to the standby PXM1.
  
  
• • 0 (the default) disables automatic switchover.
    
    
  • 1 enables automatic switchover.
    
    

oldiags-help or oldiags help

These help commands display a description of the oldiags command and options.

oldclrlock

The oldclrlock command clears the lock of a previous oldiags process.

If an oldiags process is stopped while running (either from a keyboard command or unexpected process shutdown), the command will be locked and cannot be run again until the lock is cleared. The oldclrlock command clears this lock.

Note   Do not enter oldclrlock while another instance of oldiags is running on the shelf.

oldsplog <log_name>

The oldsplog command displays the log files that are automatically created each time a diagnostic test is performed. Log files are named onlinediag.MONTHDAY_hh:mm. The files are saved in C:DIAG.

If oldsplog is run without a variable, the most recent log file will be displayed by default.

The log_name variable is used to view an older file or a file that resides in a directory other than C:DIAG. If the file to be viewed is saved in C:DIAG, only the name of the file needs to be entered. A full path name can also be used if the file resides outside the default directory.

The oldsplog command can be run from either the active or standby PXM1. Log files are saved on each individual PXM1 and must be viewed separately.

oldclralm <slot_number>

The oldclralm command clears Online Diagnostic alarms.

The variable <slot_number> is used to specify which PXM1 slot is to be cleared. This variable is mandatory.

The oldclralm command can only be run from the active PXM1.

DS3 Loopback Test

This section contains instructions to test DS3 loopback functionality using CLI commands.

Loopback Tests

Loopback tests can be performed on both DS3 lines and DS1s in DS3 lines.

Configure Loopback on the Entire DS3 Line

Perform the following steps to verify that the loopback can be configured on the entire DS3 line.

Step 1   Select a node with PXM-T3 back card.

Step 2   Configure the line entering cnfln -felpbnum 30.

Step 3   Check that dsplog does not show any errors or alarms logged.

Step 4   Enter dspln to check that FarEndLoopbkLineNum has been configured to be ds3line.

Pass Criteria:

• No errors logged on the console or the log due to configuring loopback on PXM-T3.
  
  
• Configured loopback can be displayed entering dspln.
  
  

Configure Loopback on all DS1s in a DS3 Line

Perform the following steps to verify that the loopback can be configured on all the DS1s of the DS3 line:

Step 1   Select a node with PXM-T3 back card.

Step 2   Configure the line using cnfln -felpbnum 29.

Step 3   Check that dsplog does not show any errors or alarms logged.

Step 4   Enter dspln to check that FarEndLoopbkLineNum is configured to be ds1lineall.

Pass Criteria:

• No errors logged on the console or the log due to configuring loopback on all DS1 lines of PXM-T3.
  
  
• Configured loopback can be displayed using dspln.
  
  

Receive a Loopback Request

Perform the following steps to verify that DS3 interface can be put into loopback:

Step 1   Select a node with PXM-T3 back card.

Step 2   Make sure that the FEAC code validation criteria on the DS3 interface is not disabled entering dspln -ds3 <slot>.<port>.

Step 3   Configure the HP cerjac tester to send a pattern to the DS3 interface of the node.

Any pattern sent will cause the interface to put itself into loopback and the interface retransmits the same pattern back to the tester.

Step 4   From the tester, verify that the same pattern is received back on the tester thus validating the loopback on the DS3 interface.

Step 5   Check that dsplog does not show any errors or alarms logged.

Pass Criteria:

• The pattern sent by the tester is received back to the tester as is.
  
  
• No errors logged on the console or the log.
  
  

Configure Transmit FEAC code

This section describes how to configure a transmit FEAC code.

Configure Ds3 for Sending Looped or Normal Data

Perform the following steps to verify that DS3 can be configured to send looped or normal data:

Step 1   Select a node with PXM-T3 back card.

Step 2   Configure the line entering cnfln -felpbnum 30.

Step 3   Configure the transmit FEAC code to be 'dsx3SendNoCode' by entering CLI command, cnfln -ds3 <slot>.<port> -tfeac 1.