Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2
Preparing AXSM Lines for Communication
Downloads: This chapterpdf (PDF - 483.0KB) The complete bookPDF (PDF - 5.73MB) | Feedback

Preparing AXSM Lines for Communication

Table Of Contents

Preparing AXSM Lines for Communication

Preparing for Provisioning

Quickstart Provisioning Procedures

Preparing Cards and Lines for Configuration Quickstart

Channelizing SONET Lines Configuration Quickstart

Channelizing SDH Lines Configuration Quickstart

General AXSM Provisioning Procedures

Selecting and Viewing Service Class Templates

Overview of Service Class Templates

AXSM Service Class Templates

Setting Up Lines

Bringing Up Lines

Configuring Lines

Verifying Line Configuration

Establishing Redundancy between Two Lines with APS

Adding Intracard APS Lines

Adding Intercard APS Lines

Channelizing SONET, SDH, and DS3 (T3) Lines into Paths

Overview of Channelization on an AXSM-XG Card

Channelizing a Line

Channelization in SDH Networks Versus SONET Networks

Channelizing a SONET Line

Bringing Up and Configuring SONET Paths

Channelizing an SDH Line

Bringing Up and Configuring SDH Paths


Preparing AXSM Lines for Communication


This chapter describes how to prepare AXSM cards and lines for communications to other switches using the command-line interface (CLI). It includes the following sections:

Preparing for Provisioning

Quickstart Provisioning Procedures

General AXSM Provisioning Procedures


Note AXSM cards, lines, and ports can be configured using the Cisco WAN Manager application. For full details on how to set up a connection through the Cisco WAN Manager, refer to the Cisco WAN Manager User's Guide, Release 15.1.



Note You can get information about most CLI commands by entering the command without parameters. Ordinarily, experienced users can configure AXSM card connections using just the quickstart procedures and the online help facilities. For a detailed description of the commands used in this chapter, refer to Chapter 5, "AXSM Command Reference."


Preparing for Provisioning

Before you begin provisioning line and ports on AXSM service modules, you need to initialize the cards you plan to provision. Then you should develop and implement a plan for the card and line redundancy options available for each service module. This plan determines how service modules and their back cards must be installed in the chassis, and how lines must connect to the cards before software configuration starts.

Without a plan developed for these services, a configuration change for any of these services has the potential to interrupt service and can require substantial configuration teardown. Table 2-1 defines the AXSM card redundancy and line redundancy support features, per available AXSM card models.

Table 2-1 Card Redundancy and Line Redundancy Features per AXSM Card 

Card Type
Card Redundancy Options
Line Redundancy Supported

AXSM-1-2488
AXSM-1-2488/B
AXSM-1-9953-XG

Standalone

None

1:1

Intercard APS

AXSM-2-622-E

Standalone

None

1:1

Intercard and intracard APS

AXSM-4-622
AXSM-4-622/B
AXSM-4-2488-XG

Standalone

Intracard APS

1:1

Intercard and intracard APS

AXSM-8-155-E
AXSM-8-622-XG

Standalone

Intracard APS

1:1, 1+1

Intercard and intracard APS

AXSM-16-155
AXSM-16-155/B
AXSM-16-155-XG

Standalone

Intracard APS

1:1

Intercard and intracard APS

AXSM-16-T3E3
AXSM-16-T3E3/B
AXSM-16-T3E3-E
AXSM-32-T1E1-E

Standalone

None

1:1


For instructions on initializing cards and configuring card and line redundancy, refer to the following guides:

Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2

Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.2

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.2.00


Note The procedures in this guide do not apply to Cisco MGX 8850 (PXM1E), Cisco MGX 8830, or Cisco MGX 8830/B switches because these switches do not support AXSM cards. On these switches, ATM communication is supported on the PXM1E, AUSM, and MPSM cards.



Note For the purposes of this guide, the term "AXSM" refers to all types of AXSM cards. In this document, the term AXSM/A distinguishes the first release of AXSM from AXSM/B, AXSME, and AXSM-XG cards.


Quickstart Provisioning Procedures

This section includes quickstart procedures for preparing AXSM cards and lines for communications, as follows:

Preparing Cards and Lines for Configuration Quickstart

Channelizing SONET Lines Configuration Quickstart

Channelizing SDH Lines Configuration Quickstart

Preparing Cards and Lines for Configuration Quickstart

The following quickstart procedure provides a summary of the tasks required to prepare AXSM lines for configuration as ATM trunks and lines. This procedure is provided as an overview and as a quick reference for those who already have configured Cisco MGX switches.

 
Command
Purpose

Step 1 

username

<password>

Start a configuration session with the active PXM card.

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

Step 2 

addred <options>

From the active PXM card, define which cards are operating as redundant cards. See Table 2-1 for more details on redundancy options supported.

For instructions on adding card redundancy, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Step 3 

cc <options>

Change to an active AXSM card from which you will select a card SCT.

Step 4 

cnfcdsct <sctid>

Related commands:

dspcd

Apply ATM communications parameters from a preconfigured Service Class Template (SCT) file to all communications between the card you are configuring and the other cards in the switch.

See the "Selecting and Viewing Service Class Templates".

Step 5 

upln <bay.line>

Related commands:

dsplns

dspln -type <bay.line>

Bring up lines. This step establishes physical layer connectivity between two switches.

See the "Bringing Up Lines" section.

Step 6 

cnfln <options>

Related commands:

dsplns

dspln -type <bay.line>

Configure lines. See the "Configuring Lines" section.

Step 7 

addapsln <workingIndex> <protectIndex> <archmode>

Configure a redundant relationship between two AXSM lines.

See the "Establishing Redundancy between Two Lines with APS" section.

Step 8 

For an AXSM-XG only:

cnfpath

uppath

Related commands:

dsppath

dsppaths

Add and configure a channelized path. See the appropriate following section, as applicable to the type of lines you are configuring:.

"Channelizing SONET Lines Configuration Quickstart" section.

"Channelizing SDH Lines Configuration Quickstart" section.

Channelizing SONET Lines Configuration Quickstart


Note Channelizing is not supported on non-XG AXSM Cards. This section only applies to AXSM-XG cards


This procedure describes how to create channelized SONET paths on an AXSM-XG card:

 
Command
Purpose

Step 1 

username

<password>

Start a configuration session with the active PXM card.

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

Step 2 

cc <options>

Change to an active AXSM-XG card on which you will configure a path.

Step 3 

upln

Bring up a line (bay.line). When you bring up a line, the corresponding SONET path has a width of 3.

See the "Bringing Up Lines" section.

Step 4 

cnfpath -sts <pathid> -width <width spec>

Related commands:

dsppath
dsppaths

From the active AXSM-XG card, configure the SONET path width. See the "Configuring Lines" section.

Step 5 

uppath -sts <pathid>

Related commands:

dsppath
dsppaths

Bring up the SONET path. See the "Bringing Up and Configuring SONET Paths" section.

Step 6 

cnfpath -sts <pathid> -payload <sts_au_payload_type>

Related commands:

dsppath
dsppaths

Configure the payload type for the STS path you are channelizing. See the "Bringing Up and Configuring SONET Paths" section.

Step 7 

uppath [-pathfilter] <pathid>

Bring up the sub-paths that were created in Step 6. See the "Bringing Up and Configuring SONET Paths" section. .

Step 8 

cnfpath <options>

Related commands:

dsppath
dsppaths

Configure the sub-paths.. See the "Bringing Up and Configuring SONET Paths" section.

i

Channelizing SDH Lines Configuration Quickstart


Note Channelizing is not supported on non-XG AXSM Cards. This section only applies to AXSM-XG cards


This procedure describes how to create channelized SDH lines on an AXSM-XG card:

 
Command
Purpose

Step 1 

username

<password>

Start a configuration session with the active PXM card.

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

Step 2 

cc <options>

Change to an active AXSM-XG card on which you will configure a path.

Step 3 

upln

Bring up a line. When you bring up a line, the corresponding SDH path has a width of 3.

See the "Bringing Up Lines" section, which appears later in this chapter.

Step 4 

cnfln -<bay.line> -slt 2
-clk
<clockSource>

Configure the line you brought up in Step 3 to be an SDH line. See the "Channelizing an SDH Line" section.

Step 5 

cnfpath -sts <pathid> -width <width spec>

Related commands:

dsppath
dsppaths

From the active AXSM card, configure the SDH path width. See the "Bringing Up and Configuring SDH Paths" section.

Step 6 

uppath -sts <pathid>

Related commands:

dsppath
dsppaths

Bring up the SDH path. See the "Bringing Up and Configuring SDH Paths" section.

Step 7 

cnfpath -sts <pathid> -payload <sts_au_payload_type>

Related commands:

dsppath
dsppaths

Configure the payload type for the STS path you are channelizing. See the "Bringing Up and Configuring SDH Paths" section.

Step 8 

uppath [-pathfilter] <pathid>

Bring up the sub-paths that were created in Step 7.See the "Bringing Up and Configuring SDH Paths" section.

Step 9 

cnfpath <options>

Related commands:

dsppath
dsppaths

Configure the sub-paths. See the "Bringing Up and Configuring SDH Paths" section..

i

General AXSM Provisioning Procedures

The following sections describe general provisioning procedures for AXSM cards:

Selecting and Viewing Service Class Templates

Setting Up Lines

Establishing Redundancy between Two Lines with APS

Channelizing SONET, SDH, and DS3 (T3) Lines into Paths

Selecting and Viewing Service Class Templates

The sections describe SCTs, and how to use them to configure AXSM cards:

Overview of Service Class Templates

AXSM Service Class Templates

See additional sections of working with SCTs in "Managing Card SCTs" section on page 4-4 and "Managing Port SCTs" section on page 4-9.

Overview of Service Class Templates

A Service Class Template (SCT) is a file that contains default configuration data for switch connections and for configuring the hardware to support connections. When you configure a connection, or when an SVC is established, the switch analyzes the connection setup request data, any local configuration data, and the SCTs that apply to the port and to the card.

For example, if an SPVC configuration does not include required data for the requested class of service (COS), default values from the SCT files are used. If an SVC request or SPVC configuration specifies configuration values that are different from the SCT values, the specified values override the default SCT values.

There are two types of SCTs:

Card SCTs

Port SCTs

Card SCTs define configuration parameters for the hardware that transfers data between the a service module and the switch back plane. You can assign one card SCT to each service module. Port SCTs define configuration parameters for the hardware that transfers data between a service module and a communication line to another switch or CPE. Port SCTs are assigned when a port is configured, and you can use different port SCTs on the same card, provided that the port SCT you select is designed for that card type.

Some SCT parameters control the service module hardware, and others are used as default values for connection parameters. A complete discussion of the SCT parameters is beyond the scope of this book.

SCT parameters are used to do the following:

Connection policing.

Connection admission control (CAC).

Provide default connection parameters.

Provide connection threshold parameters.

Set up class of service buffer (COSB) parameters and threshold values.

SCTs simplify configuration by providing default values that will work for most connections. This reduces the number of parameters that need to be defined when setting up connections. Without SCTs, you need to perform a lot of detailed manual configuration on each and every port on the switch. This is time consuming and error prone.

Typically, traffic profiles are defined by a handful of traffic engineering experts who understand the service level agreements and expected traffic pattern on the ports. These experts define the SCTs for each port in the system. Once the SCT is applied on the port, you do not need to (re)configure the switch. The parameters in the SCTs define generic thresholds and priorities of queues that can be understood without having to go through the programming details of Queuing engines, such as QE1210.

When configuring a service module card SCT, your goal should be to select the card SCT that will support the majority of planned connections on that card. When configuring a service module port SCT, your goal should be to select the port SCT that supports the majority of planned connections on that port.

Each service module contains default SCT parameters that you can use for communications. Cisco also supplies additional SCTs that you can use to better support communications. If none of the Cisco supplied SCTs meet your needs, you can use Cisco WAN Manager (CWM) to create your own custom SCTs. You can not create or modify SCT files using the CLI.

For more information on:

Managing card and port SCTs on AXSM cards through the command line, refer to "Managing Card SCTs" section on page 4-4 or "Managing Port SCTs" section on page 4-9.

Configuring SCTs and SCT parameters, refer to the Cisco WAN Manager User's Guide, Release 15.1.

Downloading, registering, and managing SCTs on the PXM card, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2

AXSM Service Class Templates

SCT files are applicable to the AXSM cards. Each SCT is classified by card or service module type, by whether it is a card or port SCT, and as either policing or non-policing. Although card SCTs may contain policing parameters, these parameters are ignored.

Typically, policing SCTs are used on UNI ports at the edge of the ATM network and control traffic entering the network. Non-policing SCTs are typically on trunk ports that interconnect switches within the network.


Note If traffic is properly controlled at the edges of an ATM network, there should be no need for policing within the network.


Table 2-2 lists the SCTs supplied by Cisco for AXSM cards. For the very latest information on Cisco SCTs, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.2.00


Note For information on managing card and port SCTs on AXSM cards, refer to "Managing Card SCTs" section on page 4-4 or "Managing Port SCTs" section on page 4-9.


Table 2-2 Cisco Provided SCTs for AXSM Cards 

Card Type
SCT Type
SCT ID
PNNI
MPLS
Notes
Policing 1

AXSM

Card2

23

N/A

There is no operational difference between AXSM card SCTs 2 and 3. Cisco recommends using AXSM card SCT 4 or 5.

33

N/A

4

N/A

N/A

There is no operational difference between AXSM card SCTs 4 and 5.

5

N/A

N/A

Port

23

On

Cisco recommends using AXSM port SCT 4 or 5.

33

Off

4

On

Off

PNNI policing on.

5

Off

Off

PNNI policing off.

AXSM-E

Card2

4

N/A

N/A

All three AXSM-E card SCTs are identical.

5

N/A

N/A

52

N/A

N/A

Port

4

On

Off

Use for UNI ports on interfaces faster than T1 or E1. There is no difference between port SCTs 4 and 5.

5

On

Off

6

Off

Off

Use for NNI ports on interfaces faster than T1 or E1.

52

On

Off

Use on AXSM-32-T1-E1-E UNI ports.

53

Off

Off

Use on AXSM-32-T1-E1-E NNI ports.

54

On

Off

Optimized for UNI IMA groups that use 4 T1/E1 lines or less.4

55

Off

Off

Optimized for NNI IMA groups that use 4 T1/E1 lines or less.4

AXSM-XG

Card2

1

N/A

N/A

Optimized for an OC-192 backplane rate. Recommended for use in MGX 8950 switches.

2

N/A

N/A

Optimized for an OC-48 backplane rate. Recommended for use in MGX 8850 switches.

Port

100

Off

Off

Optimized for OC-192 interface path rates.

101

Off

On

110

On

Off

111

On

On

200

Off

Off

Optimized for OC-48 interface path rates.

201

Off

On

210

On

Off

211

On

On

300

Off

Off

Optimized for OC-12 interface path rates.

301

Off

On

310

On

Off

311

On

On

400

Off

Off

Optimized for OC-3 interface path rates.

401

Off

On

410

On

Off

411

On

On

500

Off

Off

Optimized for DS-3 interface path rates.

501

Off

On

510

On

Off

511

On

On

1 Cisco recommends using SCTs with policing enabled for UNI ports and using SCTs with policing disabled for NNI ports.

2 Although policing card SCTs are provided for some service modules, the policing parameters are not used. All card SCTs are non-policing.

3 SCTs 2 and 3 were created when MGX switches supported PNNI only and were distributed with Release 2.0. These SCTs are provided for backward compatibility. Cisco recommends the use of SCTs that support PNNI and MPLS for all new installations and upgrades.

4 For IMA groups with 5-8 links, construct an SCT that uses 1/2 of the value of thresholds defined in SCTs 54 and 55. For IMA groups with 9-16 links, construct an SCT that uses 1/4 of the value of thresholds defined in SCTs 54 and 55.


Setting Up Lines

The first step in configuring AXSM lines is to bring up and configure the physical lines that are connected to the switch. The following section describe these tasks:

Bringing Up Lines

Configuring Lines

Verifying Line Configuration

Bringing Up Lines

Installing an AXSM card can add from 1 to 32 lines to your switch. You must bring up a line before you can configure the line or provision services on the line.

Before a line is brought up, or after it is brought down, the switch does not monitor the line. The AXSM port status light for the line is unlit, and all line alarms are cleared.

When you bring up a line, the switch starts monitoring the line. The AXSM port status light is green when physical layer communications are established with a remote switch. If physical layer communications problems are detected, the port status light turns red, and alarms are reported. The port status light turns yellow when physical layer communications problems are detected on the remote switch.


Note APS protection lines for intracard redundancy should be left down. APS automatically brings up each line at the appropriate time. For general information on APS line redundancy, refer to Chapter 2 of the the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2. For information on configuring APS lines, see the "Establishing Redundancy between Two Lines with APS" section.



Tip To minimize the number of alarms and failed port status lamps (which display red), keep lines down until they are ready for operation.


To bring up a line on the switch, use the following procedure.


Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Select the card on which you want to bring up a line with the cc command.

M8950_DC.5.AXSM.a > cc <slotnumber>

Step 3 Enter the upln command:

M8950_DC.5.AXSM.a > upln <bay.line>

Replace <bay> with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Replace <line> with the number that corresponds to the line you want to configure.

Table 2-3 lists the valid bay numbers and line numbers for each AXSM card. Figure 2-1 illustrates the bay and line numbers used on the Cisco MGX 8850(PXM45), MGX 8950, and MGX 8880 switches.

Table 2-3 AXSM Card Types 

Front Card
Valid Line Numbers
Valid Bay Numbers

AXSM-1-2488
AXSM-1-2488/B
AXSM-1-9953-XG

1

1

AXSM-2-622-E

1

1, 2

AXSM-4-622
AXSM-4-622/B

1 to 2

1, 2

AXSM-4-2488-XG

4

1

AXSM-8-155-E
AXSM-8-622-XG

1 to 4

1, 2

AXSM-16-T3E3
AXSM-16-T3E3/B
AXSM-16-T3E3-E
AXSM-16-155
AXSM-16-155/B
AXSM-16-155-XG

1 to 8

1, 2

AXSM-32-T1E1-E

1 to 16

1, 2


Step 4 Enter the dsplns command. The line state column shows whether each line is up or down as shown in the following example:

M8950_DC.5.AXSM.a > dsplns

Medium Medium

Sonet Line Line Line Frame Line Line Alarm APS

Line State Type Lpbk Scramble Coding Type State Enabled

----------- ----- ------------ ------ -------- ------ -------- -------- -------

1.1 Up sonetSts48c NoLoop Enable Other Other Clear Disable


The line state—Up or Down—represents the administrative intent for the line. For example, a line is reported as Down until an administrator brings up the line. Once the administrator brings up the line, the line state remains Up until the administrator brings the line down with the dnln command.

The alarm state indicates whether the line is communicating with a remote switch. When the alarm state is reported as Clear, the physical devices at each end of the line have established physical layer communications. ATM connectivity is established later when interfaces or ports are configured on the line.


Figure 2-1 Bay and Line Numbers

Configuring Lines

All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 8850 (PXM45), MGX 8950, or MGX 8880 switches, you may be able to accept the defaults for each switch and thus minimize configuration time. When configuring a line to another type of device, ensure that both devices are using the same configuration parameters on the shared line.

At the physical communications level, you can configure the following line options :

Line type

Line clock source

The following procedure describes how to configure SONET lines.


Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 If you do not know the line number you want to configure, enter the dsplns command to display a list of the lines.

8850_NY.1.AXSM.a > dsplns 


Note Remember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines."


Step 3 To display the configuration for a line, enter the dspln command. For example:

M8950_DC.16.AXSMXG.a > dspln 1.1       
  Line Number            : 1.1
  Admin Status           : Up                Alarm Status        : Clear
  Loopback               : NoLoop            APS enabled         : Disable
  Frame Scrambling       : Enable            Channelized         : Yes
  Xmt Clock source       : loopTiming        Num of STS-Paths/AUs: 4
  Line Type              : Sts48c            Provisioned Paths/AUs: 1
  Medium Type(SONET/SDH) : SONET             Number of ports     : 0
  Medium Time Elapsed    : 276               Number of partitions: 0
  Medium Valid Intervals : 96                Number of SPVC      : 0
  Medium Line Type       : SSMF              Number of SPVP      : 0
  Number of SVC          : 0          

M8950_DC.16.AXSMXG.a > 

For more information, see the "Verifying Line Configuration" section later in this chapter.

Step 4 To configure a SONET line, enter the following command:

cnfln -sonet <bay.line> -slt <LineType> -clk <clockSource>

Table 2-4 lists the parameter descriptions for configuring AXSM lines. Be sure to use only the parameters listed for SONET lines.

Table 2-4 Parameters for cnfln Command 

Parameter
Description

-sonet

Enter the keyword (-sonet) followed by the bay.line number. Ranges:

bay: 1-2

line: 1-8

-slt

Enter the keyword (-slt) followed by the LineType identifier. Identifiers:

1 = SONET

2 = SDH

-clk

Enter the keyword (-clk) followed by the clockSource identifier. Identifiers:

1 = loopTiming

2 = localTiming

-description

The circuitIdentifier is a text string with up to 64 characters that uniquely identifies the line.


Step 5 To verify your configuration changes, enter the dspln command.


Verifying Line Configuration

Use the following procedure to display the configuration of a line.


Step 1 Establish a CLI management session at any user access level.

Step 2 If you do not know the line number you want to view, display a list of the lines by entering the following command:

M8950_DC.16.AXSMXG.a > dsplns 

Step 3 To display the configuration of a single line, enter the following command:

dspln <bay.line>

Table 2-5 describes the dspln command parameters. The line configuration appears as follows:

M8950_DC.16.AXSMXG.a > dspln 1.1
  Line Number            : 1.1
  Admin Status           : Up                Alarm Status        : Clear
  Loopback               : NoLoop            APS enabled         : Disable
  Frame Scrambling       : Enable            Channelized         : Yes
  Xmt Clock source       : loopTiming        Num of STS-Paths/AUs: 4
  Line Type              : Sts48c            Provisioned Paths/AUs: 1
  Medium Type(SONET/SDH) : SONET             Number of ports     : 0
  Medium Time Elapsed    : 21                Number of partitions: 0
  Medium Valid Intervals : 96                Number of SPVC      : 0
  Medium Line Type       : SSMF              Number of SPVP      : 0
  Number of SVC          : 0          

M8950_DC.16.AXSMXG.a > 


Table 2-5 dspln Command Parameters

Parameter
Description

type

The parameter specifies the type of line that is connected to the switch. Replace <type> with -sonet, -ds3, -e3, or -e1.

bay

Replace <bay> with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay.

line

Replace <line> with the number that corresponds to the line you want to view. Table 2-3 lists the valid line numbers for each AXSM card.


Establishing Redundancy between Two Lines with APS

The Cisco MGX switch supports two types of line redundancy:

Intracard redundancy, where the working and protection lines are connected to the same card.

Intercard redundancy, where the working line is connected to the primary card, and the protection line is connected to the secondary card.

The AXSM card support, whether intracard or intercard, is called out in Table 2-1.

Intracard and intercard APS line redundancy is discussed in greater detail in the "Managing Redundant APS Lines" section of the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

The sections that follow briefly describe how to configure these intracard and intercard APS lines.

Adding Intracard APS Lines

Adding Intercard APS Lines

Adding Intracard APS Lines

Use the following procedure to establish redundancy between two lines on the same card.


Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 If you have not done so already, bring up the working line as described in the "Bringing Up Lines" section, which appears earlier in this chapter.

Step 3 Enter the addapsln command as follows:

addapsln <workingIndex> <protectIndex> <archmode>

Replace <workingIndex> with the location of the working line using the format slot.bay.line. Replace <protectIndex> with the location of the protection line, using the same format used for the working line.


Note For intracard redundancy, the working index and protection index must specify ports on the same card, so the slot and bay number for the working and protection index will always match.


Replace <archmode> with the option number that selects the automatic protection switching (APS) architecture mode you want to use. Table 2-6 shows the option numbers and the architecture modes they select.

Table 2-6 APS Line Architecture Modes 

Option
Description

1

Selects the following APS protocol signaling standards (transmission on both working and protection lines):

1+1 Bellcore GR-253 APS

ITU-T G783 Annex A

2

Selects 1:1 Bellcore GR-253 APS protocol signaling (transmission on either the working line or the protection line) for intracard APS.

3

Selects 1+1 ITU-T G.783 AnnexB APS protocol signaling (transmission on both working and protection lines).

4

Selects 1+1 Y-cable signaling without K1 and K2.

Note This option is not supported.

5

Selects 1+1 straight cable signaling without K1 and K2.

Note This option is not supported.


In the following example, 1+1 APS redundancy is assigned to two lines on the same card:

M8950_DC.5.AXSM.a > addapsln 9.2.1 9.2.2 1

Step 4 To display a list of all the APS lines on an AXSM card, enter the dspapslns command on the active AXSM card.

Step 5 To display information on a specific APS line, enter the dspapsln <slot.bay.line> command on the active AXSM card.

Refer to the "Managing Redundant APS Lines" section in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 for more details


Adding Intercard APS Lines

Use the following procedure to establish redundancy between two lines between different cards.


Note For intercard APS to operate properly, an APS connector must be installed between redundant AXSM/A, AXSM/B, AXSM-E, and AXSM-16-155-XG cards. APS functionality is built directly into the AXSM-4-2488CH-XG, AXSM-1-9953-XG, and AXSM-8-622-XG cards. For more information in the APS connector and how to install it, refer to the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.2.



Note The APS connector that fits into an MGX 8850 (PXM45) switch is different from the APS connector that fits into an MGX 8950 switch. Refer to the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.2 to ensure that you have the correct APS connector installed.



Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 If you have not done so already, add card redundancy as described in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Step 3 If you have not done so already, bring up the working line as described in "Bringing Up Lines."

Step 4 Enter the dspapsbkplane command on both the standby and active cards to verify that the APS connector is installed properly.


Note This command can show different values for each of the two cards, which indicates that the APS connector is seated properly on one card, but not on the other.


Step 5 Enter the addapsln command as follows:

addapsln <workingIndex> <protectIndex> <archmode>

Replace <workingIndex> with the location of the working line using the format slot.bay.line. Replace <protectIndex> with the location of the protection line, using the same format.


Note For intercard redundancy, the working index and protection index must specify the same line numbers on different cards. Also, the working line index must identify a line on the primary card.


Replace <archmode> with an option number that defines the type of line redundancy you want to use. Table 2-6 shows the option numbers and the types of redundancy they select.

In the following example, 1+1 APS redundancy is assigned to lines on two different cards:

pop20one.1.AXSM.a > addapsln 1.1.2 2.1.2 1

Step 6 To display a list of all the APS lines on an AXSM card, enter the dspapslns command.

Step 7 To display information on a specific APS line, enter the dspapsln <slot.bay.line> command on the active AXSM card.

For information on managing redundant APS lines, refer to Chapter 13, "Switch Operating Procedures," in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.


Channelizing SONET, SDH, and DS3 (T3) Lines into Paths

This section describes the basic channelization procedure for channelizing SONET, SDH, or DS3 paths on AXSM-XG cards that support channelization. It includes the following sections:

Overview of Channelization on an AXSM-XG Card

Overview of Channelization on an AXSM-XG Card

AXSM-XG cards support clear channel services and channelized lines. If a line is not channelized, it is said to be a clear channel line, and the full bandwidth of that line is dedicated to a single channel or path. When a line is channelized, it is logically divided into smaller bandwidth channels called paths. The following table summarizes channelization capabilities by card:

Table 2-7 Line Channelization

Line Type
SONET Channelization

OC-192/STM-64

None supported

OC-48/STM-16

STS-12, STS-3, DS3

OC-12/STM-4

STS-3 and DS3

OC-3/STM-1

None supported


A SONET synchronous transport signal (STS) is an electrical signal that gets combined with other electrical signals before being transported over an optical line. An STS-3 path has the same bandwidth as an OC-3 line, but it is not labeled with the OC rating if it is merely a path within a higher bandwidth line. For example, you can configure up to 16 STS-3 width paths in an OC-48 line. A synchronous transport module (STM) signal is the SDH equivalent of the SONET STS.

When a line is brought up initially, there is one path with. On a SONET line, a path width of 3 indicates that the line contains one clear channel STS-3 path. On an SDH line, a path width of 3 indicates that the line contains one clear channel STM-1/AU-4.

Channelizing a Line

The channelization feature allows you to create a simple or complex combination of paths for each line on your AXSM-XG back card. The simplest approach assigns the same bandwidth to each path. A more complex approach creates different path widths within the same SONET/SDH/T3 line. Depending on the type of line being channelized and the channelization scheme used, different types of paths are created.


Note The CLI shows SONET naming conventions in place of their equivalent SDH terms. For example, the display for SDH AU paths shows "STS", the display for VC/TU paths shows "VT".


Because paths support both ATM and DS3 payloads, you need to specify which payload type will travel over each path, and you may want to configure additional options for DS3 paths. Table 2-8 shows the channel payloads that are supported by each interface type.

Table 2-8 Channlized Interface Mapping 

Path/Interface Type
Possible Channel Payloads

STS-1

DS3

ATM


You can assign ATM service to any level path down to DS3. The ATM service is carried on an STS-3 down to nxDS3 (IMA), where n is the number of configured DS3s. See the "Adding ATM Ports" section on page 3-27 to configure ATM service to a DS3 line.

Keep the following in mind when configuring paths on a channelized line:

You can not configure channelization on a line that is already carrying active paths. Before you can configure a previously channelized line, you must bring down all previously configured paths on that line with the dnpath command.

You can not configure a channelized line to be in clear channel mode if it is carrying active paths. Before you can configure a channelized line to be clear channel, you must bring down all previously configured paths on that line with the dnpath command.

The sum of the bandwidths on the provisioned physical interfaces can not exceed the total bandwidth of the physical line (OC3 or DS3).

A single STS-1 or AU-3 can carry one E3 or one DS3 (T3).

All tributaries within an AU-3 (or TUG-3 within AU-4) must be the same size: either VC-11/TU-11 or VC-12/TU-12.

A single TUG-3 in an AU-4 can carry 21E1s, 28 T1s, one E3, or one T3.

A single AU-4 can carry 84 T1s, 63 E1s, 3 T3s, or 3 E3s.

You can not map channelized DS3 lines or paths into VC3/TU-3s, TUG-3s, or AU-4s.

A single STS-1 will carry one E3 or one T3.

After a line is channelized, all the paths are initially down. To use a channel:

Enter the uppath command to bring up the paths you want to configure.

Then enter the cnfpath command to configure them. The cnfpath command parameters are different, depending on the type of path you are configuring. Take care to only use the parameters that are valid for the path type you are configuring.

Table 2-9 describes the possible cnfpath command parameters for all path types.

Table 2-9 cnfpath Command Parameters 

Parameter
Description

path type

Keyword that specifies the type of path you are configuring. Possible path types are:

-sts: sts/au path

-ds3: ds3 path

path_num

Identifies the path you want to configure.


Note If you do not know the path_num, enter the dsppaths command to see a list of all path numbers on the current card.


width_spec

Specifies the width of the path. Possible values are:

1 = sts1_stm0

3 = sts3c_stm1

12 = sts12c_stm4

48 = sts48c_stm16

192 = sts192c_stm64

sts_au_payload_type

Specifies the payload type. Possible values are:

atm

ds3


Note If you select ds3, you must set the width to sts1_stm0. DS3 automatically carries ATM.


trace-string

For SONET/SDH and E3 paths, this option allows you to transmit and display trail trace bytes. You can test the line by transmitting a group of numbers using cnfln -txtrace and then displaying the result using the dshpln command to see if the numbers are the same. Enter the keyword (-txtrace) followed by the TraceString. Possible values are:

On SDH, the TraceString is a number that can be a maximum of 15 bytes.

ON SONET lines, the TraceString is a number that can be a maximum of 62 bytes.

AIScBitsCheck

For DS3 paths, this option specifies whether to ignore or check the AIS C-bit.

1-Chk C-bit

2-Ignore C-bit

plcp_spec

For DS3 paths, enables or disable PLCP.

1-enable

2-disable


Channelization in SDH Networks Versus SONET Networks

SONET networks and SDH networks use different terminology to describe the same elements in a channelized line. Table 2-10 lists the SONET terms and their equivalent SDH terms.

Table 2-10 SONET Terminology versus SDH Terminology

SONET term
Equivalent SDH Term

STS-3

STM-1/AU-4

VT

Tributary Unit (TU) or Virtual Containers (VC).

VTG

TUG

VT 1.5

TU-11

VT 2.0

TU-12


SONET path and interface numbering is different from SDH path and interface numbering. Table 2-11 defines the interface and path numbering for SONET and T3 lines, and Table 2-12 defines the interface and path numbering for SDH lines.

Table 2-11 Interface Numbering in SONET Networks 

SONET Path Type
Path Number

STS paths

bay.line.sts

DS3(T3)/E3 paths

bay.line.ds3


Table 2-12 Interface Numbering in SDH Networks 

SDH Path Type
Path Number

AU paths

bay.line.AU

DS3(T3)/E3 paths

bay.line.ds3



Note The term "DS3" is used for both T3 and E3 lines.



Note The bay is always 1.



Tip Enter the dsppaths -all command to see the path identifies for all paths on the current card.


Channelizing a SONET Line

When a SONET line is in clear channel mode, it carries a single STS-3 path.

To channelize a SONET line into three STS-1 paths, perform the following steps.


Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 Enter the cc command to change to the card you want to configure.

Step 3 If you have not done so already, bring up the line to be configured as described in the "Bringing Up Lines" section, which appears earlier in this chapter.

Step 4 Enter the dsppaths -all command to see the path ID numbers for all STS-1 paths on the current card, and obtain the path ID for the path you want to channelize.

M8950_DC.16.AXSMXG.a > dsppaths -all

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts    Down   unequipped      48    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

Step 5 Enter the cnfpath -sts <path_id> -width 1 command to set the path width. Although this command has many options, you must channelize the line before you bring up and configure individual paths. The command form that channelizes the line is as follows:

cnfpath -sts <path_id> -width 1

Replace the path_id variable with the complete path number in the format bay.line.sts, as shown in Table 2-9.


Step 6 Enter the dsppaths -sts command to verify that the line has been channelized into three separate STS paths, as shown in the following example.

M8950_DC.16.AXSMXG.a > dsppaths -sts 

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts    Down   unequipped      12    Unknown        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down

M8950_DC.16.AXSMXG.a > 



Note The software supports only the path widths described in Table 2-9. When you create a path by dividing a larger path or combining smaller paths, the software may automatically create additional paths to assure that all the available bandwidth is assigned to one of the available path sizes.



Note To change the path width on a line that has already been configured to support a path width of 1, enter the dnpath -sts <path_id> command to bring down the path, and then enter the cnfpath -sts <path_id> -width 3. Note that all sub-paths must be in a down state before you can bring down a parent path.


Bringing Up and Configuring SONET Paths

After you split a SONET line into multiple paths, you are ready to bring up the individual paths. You must bring up the individual path or paths before you can assign a payload to that path and proceed with further channelization. Once you assign a payload to a path, the path is channelized into separate paths.

The following procedures describe how to bring up and configure the path when a single DS3 path is created and put in a DOWN state.

To bring up and configure a SONET path, perform the following steps.


Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 Enter the cc command to change to the AXSM-XG card you want to configure.

Step 3 If you have not done so already, channelize the line as described in the previous section, "Channelizing a SONET Line"

Step 4 Enter the dsppaths -sts command to see the path ID numbers for all STS-1 paths on the current card, and obtain the path ID for the path you want to channelize.

M8950_DC.16.AXSMXG.a > dsppaths -sts 

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts    Down   unequipped      12    Unknown        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down

M8950_DC.16.AXSMXG.a > 

Step 5 Bring up the path with the uppath -sts <path num> command, as shown in the following example.

M8950_DC.16.AXSMXG.a > uppath -sts 1.1.1 
M8950_DC.16.AXSMXG.a > dsppaths -all

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts      Up          atm      12   Critical        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

M8950_DC.16.AXSMXG.a >

Step 6 Enter the cnfpath -sts <path_id> -payload <sts_au_payload_type> command to set the payload type for the path. The possible payload types for the paths you can create are described in Table 2-9. Be sure to set the payload to a type that is appropriate to the path type you are channelizing.

The following example shows how to configure a path with a payload:

M8950_DC.16.AXSMXG.a > cnfpath -sts 1.1.1 -payload atm

M8950_DC.16.AXSMXG.a > dsppaths -all                  

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts      Up          atm      12   Critical        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

M8950_DC.16.AXSMXG.a > 

Step 7 To display the status of a path you have brought up, enter the dsppath command as follows:

M8950_DC.16.AXSMXG.a > dsppath 1.1.1
  Path Number            : 1.1.1             Path Type           : sts
  Payload                : atm               Width               : 12
  Admin Status           : Up                Alarm Status        : Critical
  Path Operational State : Down              
  Number of ports        : 0                 Number of partitions: 0
  Number of SPVC         : 0                 Number of SPVP      : 0
  Number of SVC          : 0          
  Xmt.Trace              : 

M8950_DC.16.AXSMXG.a > 

When the path is up, the Admin Status row displays Up. The Payload row displays the payload type (atm).

Step 8 Bring up and configure the paths you created in Step 5. Refer to the "Channelizing a Line" section for instructions on bringing up and configuring DS3 paths.


Channelizing an SDH Line

When an SDH line is in clear channel mode, it carries a single STS path. You can channelize the STS path into multiple separate STS paths.


Note STM/AU paths on SDH lines are equivalent to STS paths on SONET lines. The Release 5 CLI shows SONET naming conventions in the place of their equivalent SDH terms. Note that in the channelization CLI, the STM/AU paths are called "STS" paths.


To channelize an SDH line into four separate DS3 paths, perform the following procedure.


Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 Enter the cc command to change to the AXSM-XG card you want to configure.

Step 3 If you have not done so already, bring up the line to be configured as described in the "Bringing Up Lines" section, which appears earlier in this chapter. Once a line is brought up, a single STS path is created and put in a down state.

Step 4 Enter the dsppaths -all command to ensure that an STS path has been created, and to obtain the path_id for the path.

M8950_DC.16.AXSMXG.a > dsppaths -all

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts    Down   unequipped      48    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

If want to channelize the STS path into smaller paths, proceed to Step 5. If you want to channelize the STS path into clear channel DS3 paths, skip the rest of the steps in this section and follow the procedure in the "Bringing Up and Configuring SDH Paths" section.

Step 5 Enter the cnfpath -sts <path_id> -width 1 command to set the path width. Although this command has many options, you must channelize the line before you bring up and configure individual paths. The command form that channelizes the line is as follows:

M8950_DC.16.AXSMXG.a > cnfpath -sts 1.1.1 -width 12
Change in path width may cause traffic loss.
Do you want to proceed (Yes/No) ? y

M8950_DC.16.AXSMXG.a >

Replace the path_id variable with the complete path number in the format bay.line.sts, as shown in Table 2-9. The correct path number for unchannelized SDH line 1 on an MPSM-T3E3-155 card is 1.1.0.

The AXSM XG card supports two path widths, depending on the size of the AXSM XG initial path width:

1:STS1_STM0

3:STS3c_STM1

12:STS12c_STM4

48:STS48c_STM16

192:sts192c_stm64

Step 6 Enter the dsppaths -sts command to verify that the line has been channelized into three separate SDH paths, as shown in the following example.

M8950_DC.16.AXSMXG.a > dsppaths -sts 

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts    Down   unequipped      12    Unknown        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down

M8950_DC.16.AXSMXG.a > 



Note The software supports only the path widths described in Table 2-9. When you create a path by dividing a larger path or combining smaller paths, the software may automatically create additional paths to assure that all the available bandwidth is assigned to one of the available path sizes.



Note To change the path width on a line that has already been configured to support a path width of 1, enter the dnpath -sts <path_id> command to bring down the path, and then enter the cnfpath -sts <path_id> -width 3. Note that all sub-paths must be in a down state before you can bring down a parent path.


Bringing Up and Configuring SDH Paths

After you split an SDH line into multiple paths, you are ready to bring up the individual paths. You must bring up the individual path or paths before you can assign a payload to that path and proceed with further channelization. Once you assign a payload to a path, the path is channelized into separate paths

To bring up and configure a SDH path, perform the following steps.


Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.

Step 2 Enter the cc command to change to the AXSM-XG card you want to configure.

Step 3 If you have not done so already, channelize the line as described in the previous section, "Channelizing an SDH Line"

Step 4 Enter the dsppaths -sts command to see the path ID numbers for all STS-1/STM-0 paths on the current card, and obtain the path ID for the path you want to channelize.

Step 5 Bring up the path with the uppath -sts <path num> command as shown in the following example.

M8950_DC.16.AXSMXG.a > uppath -sts 1.1.1
M8950_DC.16.AXSMXG.a > dsppaths -all

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts      Up          atm      12   Critical        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

M8950_DC.16.AXSMXG.a >

Step 6 Enter the cnfpath -sts <path_id> -payload <sts_au_payload_type> command to set the payload type for the path. The possible payload types for the paths you can create are described in Table 2-9. Be sure to set the payload to a type that is appropriate to the path type you are channelizing.

The following example shows how to configure a path with a payload:

M8950_DC.16.AXSMXG.a > cnfpath -sts 1.1.1 -payload atm

M8950_DC.16.AXSMXG.a > dsppaths -all                  

              path     Admin     path       path      path      Oper 
   path       Type     Status    Payload    Width     Alarm     State
 ----------- -------  --------  ---------  --------  -------  ----------
       1.1.1     sts      Up          atm      12   Critical        Down
      1.1.13     sts    Down   unequipped      12    Unknown        Down
      1.1.25     sts    Down   unequipped      12    Unknown        Down
      1.1.37     sts    Down   unequipped      12    Unknown        Down
    Shelf Database table empty.Ds3PathsTable

M8950_DC.16.AXSMXG.a > 

Step 7 To display the status of a path you have brought up, enter the dsppath command as follows:

M8950_DC.16.AXSMXG.a > dsppath 1.1.1
  Path Number            : 1.1.1             Path Type           : sts
  Payload                : atm               Width               : 12
  Admin Status           : Up                Alarm Status        : Critical
  Path Operational State : Down              
  Number of ports        : 0                 Number of partitions: 0
  Number of SPVC         : 0                 Number of SPVP      : 0
  Number of SVC          : 0          
  Xmt.Trace              : 

M8950_DC.16.AXSMXG.a > 

When the path is up, the Admin Status row displays Up. The Payload row displays the payload type (atm).

Step 8 Bring up and configure the rest of the paths shown in Step 5. Refer to the "Channelizing a Line" section.