-
Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.2
-
PDF Copy, Cisco ATM and Frame Relay Services (MPSM-T3E3-155 /16T1E1) Config. and Command Reference, Release 5.2
-
About This Guide
-
Introduction
-
Preparing Cards and Lines for Communication
-
Provisioning ATM Services
-
Provisioning Frame Relay Services
-
Provisioning Multilink PPP Services
-
MPSM Card Management
-
MPSM Command Reference (addapsln through cnfimaparms)
-
MPSM Command Reference (cnfln through dspilmis)
-
MPSM Command Reference (dspimagrp through whoami)
-
Table Of Contents
Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication
Quickstart Provisioning Procedures
Preparing Cards and Lines for Configuration Quickstart
Moving MPSM Feature Licenses Quickstart
Channelizing DS3 (T3) Lines Configuration Quickstart
Channelizing Sonet Lines Configuration Quickstart
Channelizing SDH Lines Configuration Quickstart
General MPSM Provisioning Procedures
Selecting and Viewing Service Class Templates
Establishing Redundancy Between Two Lines with APS
Channelizing MPSM-T3E3-155 SONET, SDH, and DS3 (T3) Lines
Setting the Service Context on MPSM-T3E3-155 and MPSM-16-T1E1 Cards
Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication
This chapter describes how to prepare MPSM-T3E3-155 and MPSM-16-T1E1 cards and lines for communications with other switches and customer premises equipment (CPE) by using the command-line interface (CLI).
These topics describe how to prepare MPSM-T3E3-155 and MPSM-16-T1E1 cards and lines for communication:
•
Quickstart Provisioning Procedures
•
Note
Preparing for Provisioning
Before you begin configuring lines and ports on MPSM-T3E3-155 and MPSM-16-T1E1 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.
The MPSM-T3E3-155 card supports 1:1 card redundancy, and the MPSM-16-T1E1 card supports both 1:1 and 1:N card redundancy. The MPSM-T3E3-155 card supports both intercard and intracard APS.
The MPSM-T3E3-155 and MPSM-16-T1E1 service modules also require the management of feature licenses. The required feature licenses are described in "MPSM Feature Licenses".
For instructions on initializing cards, configuring card and line redundancy, and managing MPSM feature licenses on the PXM processor card, refer to the:
•
•
•
MPSM Feature Licenses
The MPSM-T3E3-155 and MPSM-16-T1E1 cards require feature licenses to enable the optional MPSM features listed in Table 2-1.
You must have the required license installed in the PXM license pool if you want to use any of the features described. To install and manage licenses on the PXM card, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2
For instructions on displaying, moving, and allocating feature licenses, and managing feature license alarms on the MPSM-T3E3-155 and MPSM-16-T1E1 cards, see "Managing Feature Licenses" in Chapter 6, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."
Quickstart Provisioning Procedures
These quickstart procedures contain abbreviated procedures for preparing MPSM-T3E3-155 and MPSM-16-T1E1 cards and lines for communication:
•
•
•
•
•
These procedures are provided as an overview and as a quick reference for those who already have configured Cisco MGX switches.
Preparing Cards and Lines for Configuration Quickstart
This procedure describes how to prepare MPSM-T3E3-155 and MPSM-16-T1E1 cards for configuration:
Step 1
username
<password>
Start a configuration session with the active PXM card.
Note
Step 2
setrev
Related commands:
dspcds
From the active PXM card, initialize MPSM-T3E3-155 and MPSM-16-T1E1 cards by setting the firmware version level for each card.
Note
For instructions on initializing cards, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
Step 3
addred <options>
From the active PXM card, define which cards are operating as redundant cards.
Note
For instructions on adding card redundancy, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
Step 4
cc <options>
Change to an active MPSM-T3E3-155 or MPSM-16-T1E1 card from which you will select a card SCT.
Step 5
cnfcdsct <sctid>
Related commands:
dspcd
Apply ATM or Frame Relay 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" section, which appears later in this chapter.
Step 6
upln <bay.line>
Related commands:
dsplns
dspln -type <bay.line>
Bring up and configure lines. This step establishes physical layer connectivity between two switches.
See the "Setting Up Lines" section, which appears later in this chapter.
Step 7
cnfln <options>
Related commands:
dsplns
dspln <bay.line>
Configure lines.
To configure T1 lines, see the " Configuring DS1 (T1) Lines" section, which appears later in this chapter
To configure E1 lines, see the " Configuring E1 Lines" section, which appears later in this chapter
To configure T3 lines, see the " Configuring DS3 (T3) Lines" section, which appears later in this chapter.
To configure E3 lines, see the " Configuring E3 Lines" section, which appears later in this chapter.
To configure SONET/SDH lines, see the " Configuring SONET/SDH Lines" section, which appears later in this chapter.
Step 8
addapsln <workingIndex> <protectIndex> <archmode>
If you are using APS redundancy on the current card, configure a redundant relationship between two redundant lines.
Note
See the "Establishing Redundancy Between Two Lines with APS" section, which appears later in this chapter.
i
Moving MPSM Feature Licenses Quickstart
To move MPSM feature licenses from the MPSM-T3E3-155 and MPSM-16-T1E1 cards into the PXM license pool, perform the following steps:
Step 1
username
<password>
Start a configuration session.
Step 2
dspliccd
View the feature licenses that have been installed on the MPSM-T3E3-155 or MPSM-16-T1E1 card.
See the "Displaying Feature Licenses" section in Chapter 6, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."
Step 3
movelic
Move the MPSM feature licenses programmed on the MPSM-T3E3-155 or MPSM-16-T1E1 card to the switch license pool on the PXM processor card.
See the "Moving MPSM Feature Licenses" section in Chapter 6, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."
Step 4
dsplics
Related commands:
cnflic <options>
dspliccds
dspliccd <slot>
dsplicalmsNote
View the MPSM feature licenses installed in the PXM license pool.
See the "Displaying Feature Licenses" section in Chapter 6, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."
Note
Note
Channelizing DS3 (T3) Lines Configuration Quickstart
Note
This procedure describes how to create channelized DS3 paths on the MPSM-T3E3-155 card:
Step 1
username
<password>
Start a configuration session with the active PXM card.
Note
Step 2
cc <options>
Change to an active MPSM-T3E3-155 card on which you will configure a path.
Step 3
upln
Bring up a line (bay.line).
See the "Setting Up Lines" section, which appears later in this chapter.
Step 4
cnfln <bay.line> -lt <LineType> -chan 2
Related commands:
dsplns
dspln -type <bay.line>
From the active card, configure the DS3 line with a valid line type for channelization, and enable channelization on the line.
See the "Configuring DS3 (T3) Lines" section, which appears later in this chapter.
Step 5
uppath [-pathfilter] <pathid>
Bring up the DS1 sub-paths that were created in Step 4.
See the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter.
Step 6
cnfpath <options>
Related commands:
dsppath
dsppathsConfigure the DS1 sub-paths.
See the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter.
i
Channelizing Sonet Lines Configuration Quickstart
Note
This procedure describes how to create channelized SONET paths on the MPSM-T3E3-155 card:
Step 1
username
<password>
Start a configuration session with the active PXM card.
Note
Step 2
cc <options>
Change to an active MPSM-T3E3-155 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 "Setting Up Lines" section, which appears later in this chapter.
Step 4
cnfpath -sts <pathid> -width <width spec>
Related commands:
dsppath
dsppathsFrom the active MPSM-T3E3-155 card, configure the SONET/SDH path width.
See the " Channelizing a SONET Line" section, which appears later in this chapter.
Step 5
uppath -sts <pathid>
Related commands:
dsppath
dsppathsBring up the SONET/SDH path.
See the " Bringing Up and Configuring SONET Paths" section, which appears later in this chapter.
Step 6
cnfpath -sts <pathid> -payload <sts_au_payload_type>
Related commands:
dsppath
dsppathsConfigure the payload type for the STS path you are channelizing.
See the " Bringing Up and Configuring SONET Paths" section, which appears later in this chapter.
Step 7
uppath [-pathfilter] <pathid>
Bring up the sub-paths that were created in Step 6.
To bring up DS3 paths, see the " Bringing Up and Configuring a DS3 (T3) Path" section, which appears later in this chapter
To bring up E3 paths, see the " Bringing Up and Configuring E3 Paths" section, which appears later in this chapter
To bring up DS1 paths, see the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter
Step 8
cnfpath <options>
Related commands:
dsppath
dsppathsConfigure the sub-paths.
To configure DS3 paths, see the " Bringing Up and Configuring a DS3 (T3) Path" section, which appears later in this chapter
To configure E3 paths, see the " Bringing Up and Configuring E3 Paths" section, which appears later in this chapter
To configure DS1 paths, see the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter
To configure TUG-3s, see the " Bringing Up and Configuring TUG-3s" section, which appears later in this chapter.
i
Channelizing SDH Lines Configuration Quickstart
Note
This procedure describes how to create channelized SDH paths on the MPSM-T3E3-155 card:
Step 1
username
<password>
Start a configuration session with the active PXM card.
Note
Step 2
cc <options>
Change to an active MPSM-T3E3-155 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 SDH path has a width of 3.
See the "Setting 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 " Configuring SONET/SDH Lines" section, which appears later in this chapter.
Step 5
cnfpath -sts <pathid> -width <width spec>
Related commands:
dsppath
dsppathsFrom the active MPSM-T3E3-155 card, configure the SDH path width.
See the " Channelizing an SDH Line" section, which appears later in this chapter.
Step 6
uppath -sts <pathid>
Related commands:
dsppath
dsppathsBring up the SDH path.
See the " Bringing Up and Configuring SDH Paths" section, which appears later in this chapter.
Step 7
cnfpath -sts <pathid> -payload <sts_au_payload_type>
Related commands:
dsppath
dsppathsConfigure the payload type for the STS path you are channelizing.
See the " Bringing Up and Configuring SDH Paths" section, which appears later in this chapter.
Step 8
uppath [-pathfilter] <pathid>
Bring up the sub-paths that were created in Step 7.
To bring up DS3 paths, see the " Bringing Up and Configuring a DS3 (T3) Path" section, which appears later in this chapter
To bring up E3 paths, see the " Bringing Up and Configuring E3 Paths" section, which appears later in this chapter
To bring up DS1 paths, see the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter.
Step 9
cnfpath <options>
Related commands:
dsppath
dsppathsConfigure the sub-paths.
To configure DS3 paths, see the " Bringing Up and Configuring a DS3 (T3) Path" section, which appears later in this chapter
To configure E3 paths, see the " Bringing Up and Configuring E3 Paths" section, which appears later in this chapter
To configure DS1 paths, see the " Bringing Up and Configuring DS1(T1) and E1 Paths" section, which appears later in this chapter
To configure TUG-3s, see the " Bringing Up and Configuring TUG-3s" section, which appears later in this chapter.
i
General MPSM Provisioning Procedures
These topics and procedures describe preparing MPSM-T3E3-155 and MPSM-16-T1E1 cards for communication:
•
•
•
•
Selecting and Viewing Service Class Templates
These topics and procedures describe selecting and viewing Service Class Templates on the MPSM-T3E3-155 and MPSM-16-T1E1 cards:
•
•
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 and 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:
•
•
•
•
•
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 configuring SCTs and SCT parameters, refer to the Cisco WAN Manager User's Guide, Release 15.1.
For information on downloading, registering, and managing SCTs on the PXM card, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2
MPSM Service Class Templates
SCT files are applicable to the MPSM-T3E3-155 and MPSM-16-T1E1 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
Table 2-2 lists the SCTs supplied by Cisco for the MPSM-T3E3-155 and MPSM-16-T1E1 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
Table 2-2 Cisco Provided SCTs for the MPSM-T3E3-155 and MPSM-16-T1E1
MPSM-T3E3-155
MPSM155_SCT.CARD.1.V1
Card
1
N/A
This is the only card SCT for this card.
MPSM155_SCT.PORT.1.V1
Port
1
On
Use for UNI ports greater than 4 T1 in bandwidth.
MPSM155_SCT.PORT.2.V1
2
Off
Use for NNI ports greater than 4 T1 in bandwidth.
MPSM155_SCT.PORT.3.V1
3
On
Use for UNI ports less than or equal to 4 T1 in bandwidth.
MPSM155_SCT.PORT.4.V1
4
Off
Use for NNI ports less than or equal to 4 T1 in bandwidth.
MPSM-16-T1E1
MPSM16T1E1_SCT.CARD.1.V1
Card
1
N/A
This is the only card SCT for this card.
MPSM16T1E1_SCT.PORT.3.V1
Port
3
On
Use for UNI ports less than or equal to 4 T1 in bandwidth. For UNI ports greater than 4 T1 in bandwidth, create a new custom SCT.
MPSM16T1E1_SCT.PORT.4.V1
Port
4
Off
Use for NNI ports less than or equal to 4 T1 in bandwidth. For NNI ports greater than 4 T1 in bandwidth, create a new custom SCT.
1 Cisco recommends using SCTs with policing enabled for UNI ports and using SCTs with policing disabled for NNI ports.
Note
Selecting a Card SCT
A card SCT defines the queue parameters for the destination slot based cell queues towards the backplane. The same card SCT may be used for multiple cards of the same card type.
When an MPSM-T3E3-155 or MPSM-16-T1E1 card is powered up for the first time, the default card SCT file is used. The default SCT file is 0.
Note
Selecting a Port SCT
A port SCT defines queue parameters that apply to egress queues on a port. You can use the same port SCT for multiple ports. Port SCTs can be changed with connections provisioned on the port. However, the port needs to be administratively down to effect this change. Hence this is service affecting.
Note
Setting Up Lines
The first step in configuring MPSM-T3E3-155 and MPSM-16-T1E1 lines is to bring up and configure the physical lines that are connected to the switch. These topics describe how to do the following tasks:
•
Bringing Up Lines
Installing an MPSM-T3E3-155 card can add from 1 to 3 lines to your switch. Installing an MPSM-16-T1E1 card can add from 1 to 16 lines. 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 port status light for the line flashes green, and all line alarms are cleared. The flashing green light means the line is unprovisioned.
When you bring up a line, the switch starts monitoring the line. The 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.
Note
Note
Tip
To bring up a line on the switch, use the following procedure.
Step 1
Step 2
M8850_NY.7.PXM.a > cc <slotnumber>Replace <slotnumber> with the number of the slot in which the card is installed. Valid slot numbers are as follows:
•
•
Verify your card selection by viewing the switch prompt, which should list the slot number and the card type.
Step 3
M8850_NY.13.MPSM155[ATM].a > upln <bay.line>Replace <bay> with 1, and replace <line> with the number that corresponds to the back card port to which the line is connected, as shown in the following example:
M8850_NY.13.MPSM155[ATM].a > upln 1.1
Note
Step 4
M8850_NY.13.MPSM155[ATM].a > dsplnsMedium MediumSonet Line Line Line Frame Line Line Valid Alarm APS Channe-Line State Type Lpbk Scramble Coding Type Intvls State Enabled lized------------- ----- ------------ ------ -------- ------ -------- ------ -------- ------- -------1.1 Up sonetSts3c NoLoop Enable NRZ ShortSMF 2 Clear Disable No1.2 Down sonetSts3c NoLoop Enable NRZ Other 0 Clear Disable NoThe line state column shows whether each line is up or down. The line state is 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 or Frame Relay connectivity is established later when interfaces or ports are configured on the line.
Configuring DS1 (T1) Lines
All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 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.
The following procedure describes how to configure T1 lines.
Step 1
Step 2
M8850_NY.13.MPSM16[FR].a > dsplnsRemember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines".
Step 3
M8850_NY.13.MPSM16[FR].a > dspln 1.1For more information, see "Verifying Line Configuration", which appears later in this chapter.
Step 4
mpsm_node1.9.MPSM16T1E1[ATM] cnfln <bay.line> -lt<Line Type> -len<LineLength> -clk <clockSource> -lc <Line Coding>
Table 2-3 lists the parameter descriptions for configuring T1 lines.
Step 5
Configuring E1 Lines
All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 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.
The following procedure describes how to configure E1 lines.
Step 1
Step 2
M8850_NY.13.MPSM16[FR].a > dsplnsRemember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines".
Step 3
M8850_NY.13.MPSM16[FR].a > dspln 1.1For more information, see "Verifying Line Configuration", which appears later in this chapter.
Step 4
mpsm_node1.9.MPSM16T1E1[ATM] cnfln <bay.line> -lt<Line Type> -clk <clockSource> -lc <Line Coding>
Table 2-4 lists the parameter descriptions for configuring E1 lines.
Step 5
Configuring DS3 (T3) Lines
All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 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.
The following procedure describes how to configure T3 lines.
Step 1
Step 2
M8850_NY.13.MPSM16[FR].a > dsplnsRemember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines".
Step 3
M8850_NY.13.MPSM16[FR].a > dspln 1.1For more information, see "Verifying Line Configuration", which appears later in this chapter.
Step 4
M8850_NY.13.MPSM16[FR].a > cnfln <bay.line> -lt <LineType> -len <Length> -oof <OOFCriteria> -cb <AIScBitsCheck> -rfeac <RcvFEACValidation> -sc <sendCode> -clk <clockSource> -chan <channelization>Table 2-5 lists the parameter descriptions for configuring T3 lines.
Step 5
Configuring E3 Lines
All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 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.
The following procedure describes how to configure E3 lines.
Step 1
Step 2
Step 3
M8850_NY.13.MPSM155[ATM].a > dsplnRemember that you cannot configure a line until you have brought it up as described earlier in the " Bringing Up Lines" section.
Step 4
M8850_NY.13.MPSM155[ATM].a > cnfln <bay.line> -lt <lineType> -clk <clockSource> -txtrace <TraceString>Table 2-6 lists the parameter descriptions for configuring E3 lines.
Step 5
Configuring SONET/SDH Lines
All line types are brought up with a default configuration. When configuring trunks between two Cisco MGX 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.
The following procedure describes how to configure SONET/SDH lines.
Step 1
Step 2
M8850_NY.13.MPSM155[ATM].a > dsplnsMedium MediumSonet Line Line Line Frame Line Line Valid Alarm APS Channe-Line State Type Lpbk Scramble Coding Type Intvls State Enabled lized------------- ----- ------------ ------ -------- ------ -------- ------ -------- ------- -------1.1 Up sonetSts3c NoLoop Enable NRZ ShortSMF 2 Clear Disable No1.2 Down sonetSts3c NoLoop Enable NRZ Other 0 Clear Disable NoRemember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines".
Step 3
M8850_NY.13.MPSM155[ATM].a > dspln 1.1Line Number : 1.1Admin Status : Up Alarm Status : ClearLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable Number of ATM ports : 0Xmt Clock source : localTiming Number of ATM partitions : 0Line Type : sonetSts3c Number of ATM SPVC : 0Medium Type(SONET/SDH) : SONET Number of ATM SPVP : 0Medium Time Elapsed : 823 Number of ATM SVC : 0Medium Valid Intervals : 2 Number of ATM Sig VC : 0Medium Line Type : ShortSMF Number of FR ports : 0Channelized : No Number of FR Connections : 0Num of STS-Paths/AUs : 1 Number of IMA Links : 0Provisioned Paths/AUs : 0For more information, see the "Verifying Line Configuration" section later in this chapter.
Step 4
M8850_NY.13.MPSM155[ATM].a > cnfln <bay.line> -slt <LineType> -clk <clockSource>Table 2-7 lists the parameter descriptions for configuring SONET/SDH lines.
Step 5
Verifying Line Configuration
To display the configuration of a line, use the following procedure.
Step 1
Step 2
M8850_NY.13.MPSM155[ATM].a > dsplnsStep 3
M8850_NY.13.MPSM155[ATM].a > dspln <bay.line>Replace bay with 1, and line with a number in the range from 1-3 on the MPSM-T3E3-155 or from 1-16 on the MPSM-16-T1E1.
Note
In the following example, the line configuration of a SONET line appears as follows:
M8850_NY.13.MPSM155[ATM].a > dspln 1.2Line Number : 1.2Admin Status : Down Alarm Status : ClearLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable Number of ATM ports : 0Xmt Clock source : localTiming Number of ATM partitions : 0Line Type : sonetSts3c Number of ATM SPVC : 0Medium Type(SONET/SDH) : SONET Number of ATM SPVP : 0Medium Time Elapsed : 0 Number of ATM SVC : 0Medium Valid Intervals : 0 Number of ATM Sig VC : 0Medium Line Type : Other Number of FR ports : 0Channelized : No Number of FR Connections : 0Num of STS-Paths/AUs : 0 Number of IMA Links : 0Provisioned Paths/AUs : 0M8850_NY.13.MPSM155[ATM].a >Establishing Redundancy Between Two Lines with APS
The Cisco MGX switch supports two types of line redundancy:
•
•
The MPSM-T3E3-155 card supports APS when using the SFP-2-155 or SMB-2-155-EL back cards. APS is not supported on the MPSM-16-T1E1 card.
These topics describe how to add redundancy for these types of APS lines:
•
•
Adding Intracard APS Lines on the Same Card
To establish redundancy between two lines on the same card, use the following procedure.
Step 1
Step 2
Step 3
M8850_NY.13.MPSM155[ATM].a > addapsln <workingIndex> <protectIndex> <archmode>Replace <workingIndex> with the location of the working line using the format "slot.bay.line." For example, to specify the line on card 2, line 2, enter 2.1.2.
Note
