|
|
This chapter describes how to prepare AXSM cards and lines for configuration as ATM trunks and lines. "Provisioning," describes how to configure the AXSM lines as ATM trunks and lines.
The quickstart procedure in this section provides a summary of the tasks required to prepare AXSM cards and lines for configuration as ATM trunks and lines. This procedure is provided as an overview and as a quick reference for those who have already configured the MGX 8850 switch.
| 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 | setrev <slot> <version> Related commands: dspcds | Initialize AXSM cards by setting the firmware version level for each AXSM card. See "Managing Firmware Version Levels for AXSM Cards," which appears later in this chapter. |
Step 3 | dspcds dspcd cc <slotnumber> | Verify the hardware configuration. See "Verifying the Hardware Configuration," which appears later in this chapter. |
Step 4 | addred <options> | Define which AXSM cards are operating as redundant cards. See "Establishing Redundancy Between Two AXSM Cards," which appears later in this chapter. |
Step 5 | cnfcdsct <sctid> Related commands: dspcdsct | This step applies ATM communications parameters in a preconfigured Service Class Template (SCT) file to all communications between the card you are configuring and the other AXSM cards in the switch. Cisco policing SCT ID is 2, and non-policing SCT ID is 3. See "Selecting and Viewing Service Class Templates," 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 connectivity between two switches. See "Setting Up Lines," which appears later in this chapter. |
Step 7 | cnfln <options> Related commands: dsplns dspln -type <bay.line> | Configure lines. See "Configuring Lines," which appears later in this chapter. |
Step 8 | addapsln <workingIndex> <protectIndex> <archmode> | This optional step configures a redundant relationship between two AXSM lines. See "Establishing Redundancy Between Two Lines with APS," which appears later in this chapter. |
The AXSM cards within the switch run two types of firmware: boot firmware and runtime firmware. The boot firmware provides the basic information the card needs to start up and is installed on the board at the factory. The runtime firmware controls the operation of the card after startup, and the runtime firmware file is stored on the PXM45 hard disk back card.
After the AXSM cards are installed in the switch, you must specify the correct runtime firmware version for each card before the switch can begin using the card. The following sections explain how to
When an AXSM card is installed and the firmware version needs to be set, the System Status LED on the front of the card blinks red and the dspcds command shows that the card status is Failed. Other events can display these symptoms, but if the AXSM card is new, the problem is probably that the firmware version number has not been set. To locate the cards that need to have the firmware version set, use the following procedure.
Step 2 To display a list of all the cards in the switch, enter the dspcds command:
mgx8850a.7.PXM.a > dspcds
Example 3-1 shows the display for this command. The card state for the card in slot 9 is listed as Failed/Active. This is how a card appears when the runtime firmware version has not been selected.
pop20one.7.PXM.a > dspcds
pop20one System Rev: 02.00 Sep. 02, 2000 06:35:02 GMT
Backplane Serial No: SAA03211181 Bp HW Rev: B0 GMT Offset: 1
Node Alarm: MAJOR
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Empty --- --- --- ---
02 Empty --- --- --- ---
03 Empty --- --- --- ---
04 Empty --- --- --- ---
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Active/Active PXM45 NONE 08 PRIMARY SLOT
08 Empty Resvd/Emp --- NONE 07 SECONDARY SLOT
09 Failed/Active AXSM_4OC12 NONE NA NO REDUNDANCY
10 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
11 Empty --- --- --- ---
12 Empty --- --- --- ---
13 Empty --- --- --- ---
14 Empty --- --- --- ---
Note the slot number, card type, and redundancy type for each card that needs to have the firmware version set. You will need this information to activate these cards as described in the next section, "Initializing AXSM Cards."
 |
Note If any AXSM card displays the Active/Active card state, you do not have to set the runtime firmware version for that card. |
Before an AXSM card can operate, it must be initialized in a switch slot. The initialization process defines the AXSM runtime software version that will run on the card and identifies the slot in which the card operates. To initialize an AXSM card, use the following procedure.
 |
Tips If you have trouble locating the runtime firmware version level, use the filenames on the PXM45 hard disk to determine the level. For more information, see "Determining the Firmware Version Number from Filenames," in "Switch Operating Procedures." |
Step 2 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 3 To set the firmware revision level for a card, enter the setrev command:
mgx8850a.7.PXM.a > setrev <slot> <version>
|
Note Each card should be initialized only once with the setrev command. The only other time you should use the setrev command is to initialize cards after the configuration has been cleared with the clrallcnf command. |
Replace slot with the card slot number and replace version with the software version number. For example:
mgx8850a.7.PXM.a > setrev 1 2.0(10)
After you enter the setrev command, the System status LED blinks red until the firmware load is complete, and then it changes to non-blinking green.
Step 4 To verify the activation of a card for which the status was previously listed as Failed/Empty, enter the dspcds command. The status should change to Active/Active.
When you are having problems with your switch, or when you've taken delivery of a new switch and delayed installation for a period of time, it is wise to verify the firmware versions installed on the switch. If newer versions of this firmware are available, installing the updated firmware can prevent switch problems.
To verify the firmware versions in use on your switch, use the following procedure.
Step 2 Compare the versions you noted in Table 3-1 with the latest versions listed in the Release Notes for the Cisco MGX 8850, Release 2.
Step 3 If the switch requires software updates, upgrade the software using the instructions in "Downloading and Installing Firmware Upgrades."
Before you can configure your switch, you need to collect information about the cards and software installed on the switch. You need to enter this information during the various configuration tasks. Table 3-1 shows the information you need and serves as a worksheet where you can enter this information.
| Card | Front Card Type | Upper Back Card | Lower Back Card | Primary Software Version | Boot Firmware Version | Redundant Slot | Redundancy Type |
|---|---|---|---|---|---|---|---|
1 |
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
3 |
|
|
|
|
|
|
|
4 |
|
|
|
|
|
|
|
5 |
|
|
|
|
|
|
|
6 |
|
|
|
|
|
|
|
7 |
|
|
|
|
|
|
|
8 |
|
|
|
|
|
|
|
9 |
|
|
|
|
|
|
|
10 |
|
|
|
|
|
|
|
11 |
|
|
|
|
|
|
|
12 |
|
|
|
|
|
|
|
13 |
|
|
|
|
|
|
|
14 |
|
|
|
|
|
|
|
The following procedure describes how to display the configuration information you need to enter in this table. It also describes how to verify that the correct upper and lower back cards are installed for each front card.
Step 2 To display a list of all the cards installed in the switch, enter the dspcds command after the switch prompt:
mgx8850a.7.PXM.a > dspcds
The switch displays a report similar to the following:
pop20one.7.PXM.a > dspcds
pop20one System Rev: 02.00 Sep. 02, 2000 04:48:06 GMT
Backplane Serial No: SAA03211181 Bp HW Rev: B0 GMT Offset: 1
Node Alarm: CRITICAL
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Empty --- --- --- ---
02 Empty --- --- --- ---
03 Empty --- --- --- ---
04 Empty --- --- --- ---
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Active/Active PXM45 NONE 08 PRIMARY SLOT
08 Empty Resvd/Emp --- NONE 07 SECONDARY SLOT
09 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
10 Active/Active AXSM_4OC12 NONE NA NO REDUNDANCY
11 Empty --- --- --- ---
12 Empty --- --- --- ---
13 Empty --- --- --- ---
14 Empty --- --- --- ---
Step 3 In the worksheet in Table 3-1, write down the following information for each card:
Step 4 For each slot in which a card is installed, complete the following tasks:
a. Enter the dspcd command as follows:
mgx8850a.7.PXM.a > dspcd slot
pop20two.7.PXM.a > dspcd 7
pop20two System Rev: 02.00 Sep. 02, 2000 19:06:00 PST
MGX8850 Node Alarm: CRITICAL
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK033600AN SAK0332009P SAK0403005Q
Prim SW Rev: 2.0(16)A1 --- ---
Sec SW Rev: 2.0(16)A1 --- ---
Cur SW Rev: 2.0(16)A1 --- ---
Boot FW Rev: 2.0(16)A1 --- ---
800-level Rev: 12 04 06
Orderable Part#: 800-05983-01 800-05787-01 800-05052-03
CLEI Code: 0000000000 H 0000000000
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
pop20two System Rev: 02.00 Sep. 02, 2000 19:06:00 PST
MGX8850 Node Alarm: CRITICAL
Crossbar Slot Status: Present
Alarm Causes
------------
NO ALARMS
|
Note The dspcd and dspcds commands are very similar, but they produce different reports. The dspcd command displays information about a specific card. The dspcds command displays summary information for all cards in the switch. |
pop20two.7.PXM.a > dspcd 1
pop20two System Rev: 02.00 Sep. 02, 2000 19:05:00 PST
MGX8850 Node Alarm: CRITICAL
Slot Number: 1 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK03500088 SBK0406002V SAK0346003F
Prim SW Rev: 2.0(16)A1 --- ---
Sec SW Rev: 2.0(16)A1 --- ---
Cur SW Rev: 2.0(16)A1 --- ---
Boot FW Rev: 2.0(16)A1 --- ---
800-level Rev:
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: 1234567890 BAI9ADTAAA 0000000000
Reset Reason: On Power up
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
pop20two System Rev: 02.00 Sep. 02, 2000 19:05:00 PST
MGX8850 Node Alarm: CRITICAL
Crossbar Slot Status: Present
Alarm Causes
------------
NO ALARMS
b. In the worksheet in Table 3-1, write down the following information for each card:
|
Tips Another way to display a detailed report on a card is to use the cc command to select the card and then use the dspcd command without a slot number. However, the preferred method is to use the dspcd command with a slot number because this method can display information on a card when card errors prevent access through the cc command. |
Step 5 After you have entered the required information for all cards in Table 3-1, use Table 3-2 to verify the following:
If any of the cards are installed incorrectly, refer to the Cisco MGX 8850 Hardware Installation Guide for instructions on installing the cards correctly.
|
Note The locations where the upper and lower back cards are installed are also called bays. Each slot has an upper and a lower bay for back cards. |
| Front Card Type | Description | Back Card Types | Valid Back Card Locations | Valid Slot Numbers |
|---|---|---|---|---|
PXM45 | Processor Switch Module | UI Stratum 3 | Upper | 7 and 8 |
PXM Hard Disk Drive | Lower | |||
AXSM-1-2488 | 1 port OC-48-STM-16 Note: no traffic shaping
| SMFSR-1-2488 | Upper | 1-6, 9-14 |
AXSM-16-155 | 16 port OC-3/ STM-1 | MMF-8-155-MT | Upper and lower | 1-6, 9-14 |
AXSM-4-622 | 4 port OC-12/STM-4 | SMFIR-2-622 | Upper and lower | 1-6, 9-14 |
AXSM-16-T3E3 | 16 port T3/E3 | SMB-8-T3 | Upper and lower | 1-6, 9-14 |
To establish redundancy between two AXSM cards, use the following procedure.
Step 2 If you have not done so already, set the firmware version for both cards as described earlier in "Initializing AXSM Cards."
Step 3 Use the dspcds command to verify that both AXSM cards are in the "Active" state.
Step 4 Enter the addred command as follows:
pop20one.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>
Replace redPrimarySlotNum with the slot number of the AXSM card that will be the primary card, and replace redSecondarySlotNum with the slot number of the secondary AXSM card. Replace redType with the number 1, which selects 1:1 Y cable redundancy. Although the online help lists other redundancy types, 1:1 Y cable redundancy is the only type supported in this release.
|
Note One of the two cards can be configured before redundancy is established. If this is the case, the configured card should be specified as the primary card. Redundancy cannot be established if the secondary card has active lines. If the secondary card has active lines, you must delete all ports and down all lines before it can be specified as a secondary card. |
|
Tips If the switch displays the message, ERR: Secondary cd is already reserved, then lines are already in use on the specified secondary card. Use the dnln command to bring down these lines before re-entering the addred command. |
After you enter the addred command, the switch resets the standby card, so it will be unavailable for a couple of minutes. When the reset is complete, a dspcds command will show the primary and secondary cards in the active and standby states, respectively, as shown in the following example.
pop20one.7.PXM.a > dspcds
pop20one System Rev: 02.00 Jul. 31, 2000 15:00:56 PST
Backplane Serial No: SAA03211181 Bp HW Rev: 00.00 GMT Offset: -8
Node Alarm: CRITICAL
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Empty --- --- --- ---
02 Empty --- --- --- ---
03 Empty --- --- --- ---
04 Empty --- --- --- ---
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Active/Active PXM45 NONE 08 PRIMARY SLOT
08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT
09 Standby/Active AXSM_4OC12 NONE 10 SECONDARY SLOT
10 Active/Active AXSM_4OC12 NONE 09 PRIMARY SLOT
11 Empty --- --- --- ---
12 Empty --- --- --- ---
13 Empty --- --- --- ---
14 Empty --- --- --- ---
In the example above, AXSM card 10 is the primary card and AXSM card 9 is the secondary card.
Step 5 To display the redundancy relationship between all cards in the switch, enter the dspred command.
For information on managing redundant cards, refer to "Managing Redundant Cards," in "Switch Operating Procedures."
A Service Class Template (SCT) is a collection of ATM configuration parameter settings that are stored in a single file and can be applied to multiple lines or ports. Instead of retyping configuration data for identical lines or trunks, you can specify an SCT to apply those settings to additional lines and trunks. SCT files include the following types of configuration data:
There are two types of SCTs: card SCTs and port SCTs. Card SCTs define parameters that apply to all communications traffic between an AXSM card and the other AXSM cards in the switch. Port SCTs define parameters that apply to communications traffic on a single line or port. You can apply the same SCT to multiple cards or ports. To enable ATM communications, you must assign a card SCT to every card and a port SCT to every port you use.
The SCT files are stored in the C:\SCT\AXSM directory. Card SCT files are named AXSM_SCT.CARD.n, where n is the SCT ID number. Similarly, port SCT files are named AXSM_SCT.PORT.n. Cisco provides default SCT files you can use. The SCT ID 2 file provides parameter settings for policed connections, and SCT ID 3 serves non-policed connections. To create additional SCT files or change the configuration of existing SCT files, you need to use Cisco WAN Manager (CWM). You cannot create or modify SCT files using the CLI.
|
Note After you create a SCT file with CWM, you must use FTP to transfer that file to the switch before you can use it. For guidelines on transferring files to the switch, see "Copying Firmware Files to the Switch" in "Downloading and Installing Firmware Upgrades." Be sure to copy SCT files to the C:\SCT\AXSM directory on the switch. |
The following sections describe how to select SCTs for cards and ports.
A card SCT defines ATM parameters that apply to communications between the card you are configuring and the other AXSM cards in the switch. You can use the same SCT for multiple cards. To select an SCT for a card, use the following procedure.
Step 2 Enter the following command:
pop20two.9.AXSM.a > cnfcdsct <sctID>
Replace sctID with the number of the SCT that you want to assign to the card. Valid SCT numbers are from 0 to 255; however, a valid SCT file must exist for the number you enter.
Step 3 To display the SCT assigned to a card, enter the following command:
pop20two.9.AXSM.a > dspcd
The display card report displays a row labeled "Card SCT Id," which identifies the SCT assigned to the card.
A port SCT defines ATM parameters that apply to communications through a single port. You can use the same port SCT for multiple ports. To select an SCT for a port, use the addport command as described in "Adding ATM Ports" in "Provisioning."
The first step in configuring AXSM lines is to define the physical lines that are connected to the switch. The following sections describe how to do the following:
Installing an AXSM card can add 1 to 16 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.
|
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, see "Planning for Card and Line Redundancy," in "Preparing for Configuration." For information on configuring APS lines, see "Establishing Redundancy Between Two Lines with APS," which appears later in this chapter. |
|
Tips To minimize the number 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 2 Select the card on which you want to bring up a line with the cc command:
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 3 Enter the upln command after the switch prompt:
mgx8850a.10.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 back card port to which the line is connected. Table 3-3 lists the valid bay numbers and line numbers for each AXSM card. Figure 3-1 illustrates the bay and line numbers used on the MGX 8850 switch.
| Front Card | Valid Line Numbers | Valid Bay Numbers |
|---|---|---|
AXSM-16-155 | 1-8 | 1, 2 |
AXSM-4-622 | 1-4 | 1, 2 |
AXSM-1-2488 | 1 | 1 |
AXSM-16-T3E3 | 1-8 | 1, 2 |
Step 4 Enter the following command:
mgx8850a.10.AXSM.a > dsplns
The line state column shows whether each line is up or down as shown in the following example:
pop20one.10.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 sonetSts12c NoLoop Enable Other ShortSMF Clear Disable
1.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable
2.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear Disable
2.2 Up sonetSts12c NoLoop Enable Other ShortSMF Clear 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 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 (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.
All line types are brought up with a default configuration. When configuring trunks between two MGX 8850 switches, you may be able to accept the defaults for each switch and 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:
The following procedure describes how to configure SONET, DS3, and E3 lines.
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:
mgx8850a.10.AXSM.a > dsplns
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 configure a SONET line, enter the following commands:
mgx8850a.10.AXSM.a > cnfln -sonet <bay.line> -slt <LineType> -sfs <FrameScramble> -clk <clockSource>
Table 3-4 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for SONET lines.
| Parameter | Line Types Supported | Description |
|---|---|---|
AIScBitsCheck | T3 | The -cb option defines C-bit checking. Set AIScBitsCheck to 1 to enable C-bit checking. Set it to 2 to ignore the C-bit. |
bay | T3 | 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. |
clockSource | T3 | 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 "Managing Network Clock Sources" in "Configuring General Switch Features." |
FrameScramble | SONET | The -sfs option enables or disables SONET frame scrambling. This setting must match the setting on the remote end of the line. Replace the FrameScramble variable with 1 to disable frame scrambling or 2 to enable frame scrambling. |
line | T3 | Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-3 lists the valid line numbers for each AXSM card. |
LineLength | T3 | The -len option specifies the length of a T3 line from the local node to a remote node in meters. Enter a value between 0 and 64000 meters. |
LineType | SONET | The -slt and -lt options specify the line type. For SONET lines, replace the LineType variable with 1 for SONET or 2 for SDH. For DS3 lines, replace the LineType variable with 1 for ds3cbitadm or 2 for ds3cbitplcp. |
OOFCriteria | T3 | |
RcvFEACValidation | T3 | Replace RcvFEACValidation with 1 to select 4 out of 5 and 2 to select 8 out of 10. |
Step 4 To configure a DS3 line, enter the following command:
mgx8850a.10.AXSM.a > cnfln -ds3 <bay.line> -lt <LineType> -len <LineLength> -oof <OOFCriteria> -cb <AIScBitsCheck> -rfeac <RcvFEACValidation> -clk <clockSource">
Table 3-4 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for DS3 lines.
Step 5 To configure an E3 line, enter the following command:
mgx8850a.10.AXSM.a > cnfln -ds3 <bay.line> -len <LineLength> -clk <clockSource">
Table 3-4 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for E3 lines.
After you configure a line, you can verify the configuration by following the procedure in the next section.
To display the configuration of a line, use the following procedure.
Step 2 If you don't know the line number you want to view, display a list of the lines by entering the following command:
mgx8850a.10.AXSM.a > dsplns
Step 3 To display the configuration of a single line, enter the following command:
mgx8850a.10.AXSM.a > dspln -type <bay.line>
The following table describes the command parameters.
type | The parameter specifies the type of line that is connected to the switch. Enter -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. Table 3-3 lists the valid line numbers for each AXSM card. |
The line configuration appears as follows:
pop2one.10.AXSM.a > dspln -sonet 2.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
The switch supports two types of line redundancy:
The following sections describe how to add redundancy for these types of APS lines.
To establish redundancy between two lines on the same card, use the following procedure.
Step 2 If you have not done so already, bring up the working line as described in "Bringing Up Lines," which appears earlier in this chapter.
Step 3 Enter the addapsln command as follows:
pop20one.7.PXM.a > addapsln <workingIndex> <protectIndex> <archmode>
Replace workingIndex with the with the location of the working line using the format "slot.bay.line." For example, to specify the line on card 9, bay 1, line 2, enter 9.1.2.
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 number will always match. |
Replace archmode with the option number that selects the APS architecture mode you want to use. Table 3-5 shows the option numbers and the architecture modes they select.
| Option | Description |
|---|---|
1 | Selects 1+1 signaling (transmission on both working and protect lines) for intracard APS. |
2 | Selects 1:1 signaling (transmission on either the working line or the protect line) for intracard APS. |
3 | Selects G.783, Annex B 1+1 signaling. This option is not supported in this release. |
The following example shows assigns 1+1 APS redundancy to two lines on the same card:
pop20one.9.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 dspapsln command.
For information on managing redundant APS lines, refer to "Managing Redundant APS Lines," in "Switch Operating Procedures."
To establish redundancy between two lines on different cards, use the following procedure.
Step 2 If you have not done so already, add card redundancy as described in "Establishing Redundancy Between Two AXSM Cards."
Step 3 If you have not done so already, bring up the working and protection lines as described in "Bringing Up Lines."
Step 4 Enter the addapsln command as follows:
pop20one.7.PXM.a > addapsln <workingIndex> <protectIndex> <archmode>
Replace workingIndex with the with the location of the working line using the format "slot.bay.line." For example, to specify the line on card 9, bay 1, line 2, enter 9.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 the 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 3-5 shows the option numbers and the types of redundancy they select.
The following example shows assigns 1+1 APS redundancy to lines on different cards:
pop20one.10.AXSM.a > addapsln 10.1.2 9.1.2 5
Step 5 To display the a list of all the APS lines on an AXSM card, enter the dspapsln command.
For information on managing redundant APS lines, refer to "Managing Redundant APS Lines," in "Switch Operating Procedures."
Posted: Thu Sep 14 18:50:31 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.