This chapter describes how to configure the lines on a Service Redundancy Module (SRM), enable bulk distribution between SRM cards and T1/E1 service modules, and establish APS redundancy on SRME cards.
This chapter provides a quickstart procedure for configuring SRM cards and lines, and describes the following procedures:
preparing SRM lines for physical connectivity
establishing redundancy with APS
establishing redundancy for service modules
enabling bulk distribution to T1/E1 service modules
Note All SRM configuration is done from the PXM1E card.
Configuration Quickstart
The quickstart procedure in this section summarizes SRM line configuration. This procedure is a quick reference for those who already have configured Cisco MGX 8850 and Cisco MGX 8830 switches.
Command
Purpose
Step 1
username
<password>
Start a configuration session.
Note To perform all the procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Step 2
upln <bay.line>
Related commands:
dsplns
dspln -type <bay.line>
At the active PXM1E prompt, bring up and activate the line or lines on the SRM card. This step establishes physical layer connectivity between two switches.
You do not need to download any firmware to the SRM cards because they are controlled by the PXM1E cards. The PXM1E and SRM cards together are considered core cards. When a switchover occurs on the PXM1E cards, the SRM cards will also switch.
Setting Up Lines
The first step in configuring SRM lines is to define the physical lines that are connected to the switch. The following sections describe how to do the following procedures:
Bring up lines
Configure lines
Verify the configuration of lines
Bringing Up Lines
Before a line is brought up, or after it is brought down, the switch does not monitor the line. The SRM 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 SRM line status light is green when physical layer communication is established with a switch or CPE. If physical layer communications problems are detected, the port status light turns red, and alarms are reported.
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 SRM, use the following procedure.
Step 1 Establish a configuration session on the PXM1E card using a user name with GROUP1 privileges or higher.
Step 2 Enter the upln command at the switch prompt.
mgx8830b.1.PXM.a > upln <X.line>
Replace <X> with the logical slot number of the SRM. On a Cisco MGX 8850, replace <X> with15 or 16 if the line is connected to a back card in the upper bay, or replace it with 31or 32 if the line is connected to a back card in the lower bay. On a Cisco MGX 8830, replace <X> with7 if the line is connected to a back card in the upper bay, or replace it with 14 if the line is connected to a back card in the lower bay. Replace <line> with the number that corresponds to the back card port to which the line is connected.
Step 3 Enter the dsplns <logical slot>command to verify that the appropriate line is up.
Replace <logical slot> with the slot number of the SRM to which you are adding a line.
The Line State column shows whether a line is up or down as shown in the following example:
mgx8830b.1.PXM.a > dsplns
Medium Medium VT
Sonet Line Line Line Frame Line VT Maping APS
Line State Type Lpbk Scramble Type Type Type Enabled
31.1 Up sonetSts3 NoLo Enable ShortS vt15/vc11 asynch Disable
The line state, which is either Up or Down, represents the administrative intent for the line. For example, a line is reported as Down until you bring it up. Once you bring up the line, the line state remains Up until you bring it down with the dnln command.
The alarm state indicates whether the line is communicating with another device. When the alarm state is Clear, the devices at each end of the line have established physical layer communications. ATM connectivity is later established when logical interfaces are configured on the line.
Configuring SONET Lines
All line types are brought up with a default configuration. When configuring a connection between two Cisco MGX 8850 or Cisco MGX 8830 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 options for SONET lines:
Line type
Line clock source
The following procedure describes how to configure SONET lines on an SRM card.
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.
mgx8830b.1.PXM.a > dsplns <logical slot>
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:
mgx8830b.1.PXM.a > dspln -sonet 7.2
Line Number : 7.2
Admin Status : Up Alarm Status : Critical
Loopback : NoLoop APS enabled : Disable
Frame Scrambling : Enable Number of ports : 1
Xmt Clock source : localTiming Number of partitions: 1
Table 4-1 lists the parameter descriptions for configuring SONET lines. To verify your configuration changes, enter the dspln command.
Table 4-1 Parameters for cnfln Command
Parameter
Description
slot.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 back card port to which the line is connected.
-slt
Sonet line type. Replace < LineType> with 1, to specify this line as a sonet line.
Note Replacing < LineType> with 2 specifies the line as an SDH line.
-clk
The -clk option selects the source timing for transmitting messages over the line. Replace <clockSource> with 1 to use the clock signal received over this line from a remote node, or specify 2 to use the local timing defined for the local switch. For information on defining the clock source for the local switch, see the "Managing Network Clock Sources" section in "Switch Operating Procedures."
-lpb
Enables one of two loopback types or disables an active loopback, as follows:
1: No loopback
2: Local loopback
3: Remote loopback
A loopback circulates OAM cells between the card and the CPE in a local loopback or between he card and the network in a remote loopback. The loopback continues until you halt it by again running the cnfln command with the parameter sequence -lpb 1.
Default: no loopback
-sfs
Enables/disables the frame scramble. Replace <FrameScramble> with 1 to disable frame scramble, or 2 to enable frame scramble.
-rdiv
Specifies the number of RDI V bits. Replace <RDI-V Type> with either a "1" for 1 bit or a "3" for 3 bits.
-rdip
Specifies the number of RDI P bits. Replace <RDI-V Type> with either a "1" for 1 bit or a "3" for 3 bits.
-tt
The TributaryType selects a tributary type based on whether the line is SONET or SDH. Replace <TributaryType> with either a "1" for Vt15/Vc11, or a "2" for Vt2/Vc12.
Note For SONET, type "1." For SDH, type "2." This choice results in the standard for virtual tributary (VT) and virtual container (VC).
Note In the current release, only VT1.5 and VC 11 for T1 applications are supported.
-tm
The tributary mapping type is either asynchronous or byte-synchronous. Type a "1" or "2."
1: Asynchronous
2: Byte-synchronous
Default: asynchronous
Note In the current release, tributary mapping applies to only T1 tributaries.
-tf
The tributary framing type is either superframe or extended superframe. This option applies only if the tributary mapping is byte-synchronous (-tm 2). Replace <TributaryFramingType> with "2" to specify Superframe, or "3" to specify extended superframe.
-st
The signaling transport mode applies only if you have selected byte-synchronous tributary mapping (-tm 2). Replace <SignallingTranportMode> with either a "2" to specify transfer mode, or a "3" to specify clear mode.
With transfer mode, the framing bit is transferred to the VT header.
With clear mode, the signaling bit is transferred to the VT header.
-tg
The tributary grouping type applies to SDH. Replace <TributaryGroupingType> with a "2" to specify AU3, or a "3" to specify AU4.
Verifying Line Configuration
To display the configuration of a line, use the following procedure.
Step 1 Establish a CLI management session with the active PXM1E 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:
mgx8830b.1.PXM.a > dsplns
Step 3 To display the configuration of a single line, enter the following command:
mgx8830b.1.PXM.a > dspln <-type> <bay.line>
Table 4-2 describes the command parameters. The line configuration appears as follows:
mgx8830b.1.PXM.a > dspln -sonet 7.1
Line Number : 2.1
Admin Status : Up Alarm Status : Clear
Loopback : NoLoop APS enabled : Disable
Frame Scrambling : Enable Number of ports : 1
Xmt Clock source : localTiming Number of partitions: 1
Line Type : sonetSts12c Number of SPVC : 0
Medium Type(SONET/SDH) : SONET Number of SVC : 4
Medium Time Elapsed : 248198
Medium Valid Intervals : 96
Medium Line Type : ShortSMF
Table 4-2 dspln Command Parameters
Parameter
Description
-type
The parameter specifies the type of line that is connected to the switch. Replace <-type> with -sonet or-ds3. The -ds3 option works for DS3 and E3 lines.
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 back card port to which the line is connected.
Establishing Redundancy Between Two Lines with APS
The SRME supports intercard redundancy, where the wor.king line is connected to the primary card, and the protection line is connected to the secondary card.
Note The SRM3T3-C does not support APS redundancy.
To establish redundancy between two lines on different cards, use the following procedure.
Note For intercard APS to operate properly, an APS connector must be installed between the two cards. For
more information in the APS connector and how to install it, refer to either the
Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E).
Step 1 Establish a configuration session with the active PXM1E using a user name with GROUP1_GP privileges or higher.
Note All SRM configuration is done from the active PXM1E card.
Step 2 Ensure that you have two SRME cards installed and acting as redundant cards.
Step 3 If you have not done so already, bring up the working and protection lines as described in the "Bringing Up Lines" section earlier in this chapter.
Step 4 Verify that an APS connector is installed between the cards that host the working and protection lines by entering the dspapsbkplane command.
Replace <workingIndex> with the location of the working line using the format slot.bay.line. For example, to specify line 1on the card in slot 15 (which is in the upper bay), enter 15.1.2.
Replace <protectIndex> with the location of the protection line, using the same format used for the working line.
Note For intercard redundancy, the working index and protection index must specify ports 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 4-3 shows the option numbers and the types of redundancy they select.
Table 4-3 APS Line Architecture Modes
Option
Description
1
Selects 1+1 signaling (transmission on both working and protection lines) for intracard APS.
Note This option is not supported in this release.
2
Selects 1:1 signaling (transmission on both working and protection lines) for intracard APS.
Note This option is not supported in this release.
3
Selects G.783, Annex B 1+1 signaling.
Note This option is not supported in this release.
4
Selects Y-cable 1+1 signaling without k1 and k2.
5
Selects straight cable 1+1 signaling.
The following example shows assigns 1+1 APS redundancy to lines on different cards:
mgx8850b.1.PXM.a > addapsln 7.1.1 14.1.1 1
Step 6 Enter the cnfapsln command to configure the APS line, as follows:
Table 4-4 shows the option numbers and the types of redundancy they select.
Table 4-4 cnfapsln Command Parameters
Option
Description
-w
Replace <workingline> with the location of the working line using the format slot.bay.line. For example, to specify the line on card 7, bay 1, line 2, enter 7.1.2.
Note In the MGX 8850 chassis, the slot is 15 or 31 for the SRME. In the MGX 8830 chassis, the slot is 7 for the SRME.
Example: -w 15.1.2
-sf
Replace <SignalFaultBER> with one of the following numbers to indicate the Signal Fault Bit Error Rate (BER), in negative powers of ten:
3 = 10-3
4 = 10-4
5 = 10-5
Example: -sf 3
-sd
Replace <SignalDegradeBER> with one of the following numbers to indicate the Signal Degrade Bit Error Rate (BER), in negative powers of ten:
5 = 10-5
6 = 10-6
7 = 10-7
8 = 10-8
9 = 10-9
Example: -sd 5
-wtr
Replace <Wait To Restore> with the number of minutes to wait after the working line has become functional again, before switching back to the working line from the protection line. The range is 5-12.
Example: -wtr 5
-dr
Replace <direction> with the direction of the transmitting or receiving path. Enter "1" to set the signal to unidirectional, or enter "2" to set the path to bidirectional
Bidirectional means that both the receiving and transmitting paths are switched. Unidirectional means that only the affected path, receiving or transmitting, is switched.
Example: -dr 2
-rv
Enables/disables revertive behavior. Replace <revertive> with the number "1" to disable revertive behavior, or "2" to enable revertive behavior.
Example: -rv 1
-proto
Replace <protocol> with the number "1" to specify the Bellcore protocol, "2" to specify the ITU protocol.
Step 7 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 the APS
connector is seated properly on one card, but not on the other.
Step 8 To display the a list of all the APS lines on an SRM card, enter the dspapslns command.
Enabling Bulk Distribution Between the SRM and Service Modules
Once you have brought up the line or lines on your SRM card and established redundancy, you can link the SRM to the appropriate service module or modules and enable bulk distribution.
Linking SRM Cards to T1 Service Modules for Bulk Distribution
Linking the SRM to a destination card causes the shelf to take CPE traffic through the SRM 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 SRM, the back card on the service module becomes inoperative, so you must link all other T1 ports on that service module to the SRM-3T3 or to the SRM-E if you want them to operate.
Note The SRM3T3-C supports bulk distribution to T1 only. The SRME supports bulk distribution to T1 and
E1.
To link a T1 port on an NBSM to an SRM and enable bulk distribution, use the following procedure:
Step 1 Enter the addlink command on the active PXM1E.
mgx8830b.1.PXM.a > addlink <T3 line number> <T1 slot> <NumberOfLinks> <TargetSlotLineNum>
Replace <T3 line number> with the SRM card's T3 line number. Replace T1 slot with the
In the following example, the user links an SRM-E card in slot 31 to an NBSM in slot 30.
mgx8830b.1.PXM.a > addlink 31.1.1 1 30.1
Step 2 Enter the dsplink command to verify your configuration.
Step 3 Enter dsplink to verify that the link has been brought up.
Where To Go Next
Once you have linked the SRM to the service modules and established redundancy, you are ready to start provisioning connections. To provision connections on a particular service module, you need to refer to the appropriate software configuration guide (see Table 4-5).
Table 4-5 Service Module Software Configuration Guides
Service Module
Document Title
CESM
Cisco CESM Software Configuration Guide and Command Reference
AUSM
Cisco AUSM Software Configuration Guide and Command Reference
FRSM
Cisco FRSM Software Configuration Guide and Command Reference
