Preparing Cell Bus Service Modules for Communication

Table Of Contents

Preparing Cell Bus Service Modules for Communication

Configuration Quickstart

Managing Firmware Version Levels for CBSM Cards

Locating Cards that Need the Firmware Version Set

Initializing CBSM Cards

Verifying Card Firmware Version Levels

Establishing Redundancy Between CBSM Cards

Preparing Cell Bus Service Modules for Communication

Cell bus service modules (CBSMs) use the cell bus within the switch for customer traffic between cards. In contrast, serial bus service modules use the serial bus to carry customer traffic. In this release, all service modules except AXSM, FRSM-12-T3E3, and RPM are CBSMs. The supported CBSMs are:

•AUSM8T1/B and AUSM8E1/B

•CESM-8E1 and CESM-8T1/B

•FRSM-2CT3 and FRSM-2T3E3

•FRSM-8E1, FRSM-8E1-C, FRSM-8T1, and FRSM-8T1-C

•FRSM-HS2/B

•VISM-PR-8E1 and VISM-PR-8T1

This chapter provides a quickstart procedure for configuring CBSMs, and it provides additional information in the following related procedures:

• Managing Firmware Version Levels for CBSM Cards

• Establishing Redundancy Between CBSM Cards

Configuration Quickstart

The quickstart procedure in this section provides a summary of the tasks required to prepare CBSM cards for operation in a Cisco MGX switch. This procedure is a quick reference for those who already have configured CBSMs.

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 CBSM cards by setting the firmware version level for each card. Run the setrev command from the PXM.

See the " Managing Firmware Version Levels for CBSM Cards" section later in this chapter.

Step 3

addred <options>

Related commands:

dspred

Define which cards are operating as redundant cards.

See the " Establishing Redundancy Between CBSM Cards" section later in this chapter.

Managing Firmware Version Levels for CBSM Cards

The CBSMs within the switch run two types of firmware: boot firmware and runtime firmware. The boot firmware provides the startup information the card needs. The boot firmware is installed on the card at the factory. The runtime firmware controls the operation of the card after startup. The runtime firmware file is stored on the PXM hard disk.

After the CBSMs are installed, 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

•Locate the cards that need to have the firmware version level set

•Set the firmware version levels for cards in the switch

•Verify the firmware version levels being used by cards

Locating Cards that Need the Firmware Version Set

When a CBSM is installed and the firmware version needs to be set, the System Status LED on the front of the card blinks red. The dspcds command shows that the card status is Failed. Other events can cause a failed status, but if the CBSM 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 1 Establish a CLI management session at any access level.

Step 2 To display a list of all the cards in the switch, enter the dspcds command.

mgx8830b.1.PXM.a > dspcds
The following example shows the display for this command. The card state for the card in slot 4 is listed as Failed/Active. This is how a card appears when the runtime firmware version is not selected.

mgx8830b.1.PXM.a > dspcds

mgx8830b System Rev: 03.00 Apr. 25, 2002 23:20:16 GMT
Chassis Serial No: SCA053000KM Chassis Rev: A0 GMT Offset: 0
Node Alarm: MAJOR
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----

01 Active/Active PXM1E-4-155 MAJOR 02 PRIMARY SLOT
02 Standby/Active PXM1E-4-155 NONE 01 SECONDARY SLOT
03 Active/Empty RPM NONE NA NO REDUNDANCY
04 Failed/Active FRSM_2CT3 MINOR 05 PRIMARY SLOT
05 Standby/Active FRSM_2CT3 NONE 04 SECONDARY SLOT
06 Active/Active CESM_8T1 NONE NA NO REDUNDANCY
07 Active/Active SRM_3T3 NONE 14 PRIMARY SLOT
11 Active/Active FRSM_8T1 NONE NA NO REDUNDANCY
12 Empty --- --- --- ---
13 Standby/Active FRSM_8T1 NONE NA NO REDUNDANCY
14 Standby/Active SRM_3T3 NONE 07 SECONDARY SLOT

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 CBSM Cards."

Note If any CBSM card displays the Active/Active card state, you do not have to set the runtime firmware version for that card.

Initializing CBSM Cards

Before a CBSM card can operate, it must be initialized in a switch slot. The initialization process defines the runtime software version that will run on the CBSM and identifies the slot in which the card operates. To initialize a CBSM, use the following procedure.

Note The line count for all cards in the switch must not exceed the maximum number of lines supported by the current PXM controller card. The PXM45/A supports 192 UNI/NNI lines. The PXM45/B and PXM45/C support up to 4,000 UNI/NNI interfaces. The PXM1E card supports a maximum of 4,000 UNI/NNI interfaces per switch. Keep this information in mind as you add CBSMs to your switch.

Step 1 If you have not already done so, determine the software version number for the card by referring to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 4.0.00.

Tip If you have trouble locating the runtime firmware version level, use the filenames on the PXM hard disk. To see how to derive a version number from a file name, see the " Determining the Software Version Number from Filenames" section in Chapter 13, "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.

mgx8830b.1.PXM.a > setrev <slot> <version>

Note Each card should be initialized only once with the setrev command. The only other time you should enter the setrev command is to initialize cards after the configuration has been cleared with the clrallcnf, clrcnf, or clrsmcnf commands.

Replace <slot> with the card slot number and replace <version> with the software version number. For example:

mgx8830b.1.PXM.a > setrev 4 3.0(0)

After you enter the setrev command, the System status LED blinks red until the firmware load is complete, 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.

Verifying Card Firmware Version Levels

When you are having problems with your switch, or when you have taken delivery of a new switch but delayed installation, 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 see the firmware version numbers in use on your switch, use the following procedure.

Step 1 To display the software revision status of all the cards in a switch, enter the dsprevs command as shown in the following example:

PXM1E_SJ.8.PXM.a > dsprevs
PXM1E_SJ System Rev: 04.09 Jul. 10, 2003 17:21:51 GMT
MGX8850 Node Alarm: CRITICAL
Phy. Log. Inserted Cur Sw Boot FW
Slot Slot Card Revision Revision
---- ---- -------- -------- --------

01 01 AUSMB_8T1 21.0(2.37)A 1.0(2.0)
02 02 AUSMB_8E1 21.0(2.37)A 1.0(2.0)
03 03 --- --- ---
04 04 CESM_8T1 21.0(2.37)A 1.0(2.0)
05 05 CESM_8E1 21.0(2.37)A ---
06 06 --- --- 1.0(2.0)
07 07 PXM1E-T3E3-155 4.9(4.1)P1 4.9(4.1)P1
08 07 PXM1E-T3E3-155 4.9(4.1)P1 4.9(4.1)P1
09 09 RPM_PR --- ---
10 10 --- --- ---
11 11 FRSM_HS2/B 21.0(2.37)A 1.0(6.0)
12 12 FRSM_8T1 21.0(2.37)A 1.0(2.0)
13 13 FRSM_2CT3 21.0(2.37)A 1.0(1.0)
14 14 --- --- ---
15 15 --- --- ---
16 15 --- --- ---

Type <CR> to continue, Q<CR> to stop:

Step 2 To see the software revision levels for a single card, enter the version command as follows:

PXM1E_SJ.1.1.AUSMB8.a > version

***** Cisco Systems Inc. AXIS AUSM-8T1/E1 Card *****
Firmware Version = 021.000.002.037-A
Backup Boot version = AU8_BT_1.0.02
AUSM8p Xilinx file = ausm8pXilinx.h
VxWorks (for CISCO) version 5.1.1-R3000.
Kernel: WIND version 2.4.
Made on Fri Jun 6 03:17:38 PDT 2003.
Boot line:

Step 3 Another way to see the software revision levels for a single card is to enter the dspcd command as follows:

PXM1E_SJ.8.PXM.a > dspcd 4
PXM1E_SJ System Rev: 04.09 Jul. 10, 2003 17:25:56 GMT
MGX8850 Node Alarm: CRITICAL
Slot Number: 4 Redundant Slot: NONE

Front Card Back Card
---------- ---------
Inserted Card: CESM_8T1 RJ48_8T1
Reserved Card: CESM_8T1 UnReserved
State: Active Active
Serial Number: 123456 691681
Prim SW Rev: 21.0(2.37)A ---
Sec SW Rev: 21.0(2.37)A ---
Cur SW Rev: 21.0(2.37)A ---
Boot FW Rev: 1.0(2.0) ---
800-level Rev: 00 00
800-level Part#: 000-00000-00 000-00000-00
CLEI Code: N.A N.A
Reset Reason: On Reset from PXM
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:

Type <CR> to continue, Q<CR> to stop:

Step 4 Using the dsprevs and dspcd commands, complete the hardware and software configuration worksheets for your switch and service module type. These worksheets appear in "Hardware Survey and Software Configuration Worksheets."

Step 5 Compare the versions you noted in the worksheets with the latest versions listed in the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 4.0.00.

Step 6 If the switch requires software updates, upgrade the software using the instructions in Appendix A, "Downloading and Installing Software Upgrades."

Establishing Redundancy Between CBSM Cards

Each CBSM supports either 1:1 or 1:N redundancy as listed in Table 2-1. If you are not familiar with these redundancy options, see "Planning for Card Redundancy, Line Redundancy, and Bulk Distribution." To establish redundancy between CBSM cards of the same type, use the following procedure.

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

Step 2 Enter the dspcds command to verify that both CBSM cards are in the Active state.

Step 3 Enter the addred command as follows:

pop20one.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Replace <redPrimarySlotNum> with the slot number of the card that will be the primary card, and replace <redSecondarySlotNum> with the slot number of the secondary card. Replace <redType> with the number 1 to select 1:1 card redundancy (also called Y-cable redundancy), or enter 2 to select 1:N redundancy.

Step 4 To verify that the redundancy relationship is established, enter the dspred command as shown in the following example:

PXM1E_SJ.8.PXM.a > dspred
PXM1E_SJ System Rev: 04.09 Jul. 10, 2003 17:33:00 GMT
MGX8850 Node Alarm: CRITICAL
Logical Primary Secondary Card Redundancy
Slot Slot Card Slot Red Type Type
State State
----- ----- ----------- ---- ------------ ------------ ----------
7 7 Standby 8 Active PXM1E-T3E3-155 1:1
15 15 Empty 16 Empty SRME_OC3 1:1
17 17 Active 19 Standby FRSM-8T1 1:n
18 18 Active 19 Standby FRSM-8T1 1:n
20 20 Active 22 Standby FRSM-8E1 1:n
21 21 Active 22 Standby FRSM-8E1 1:n
28 28 Active 29 Standby VISM-PR-8T1 1:n
31 31 Standby 32 Active SRME_OC3 1:1

The secondary state for the card in the secondary slot changes to Standby only when the secondary card is ready to take over as active card. After you enter the addred command, the switch resets the secondary card. When you first view the redundancy status, the state may be Empty Resvd or Init. The secondary card may require one or two minutes to transition to standby.

Note The dspcds command also shows the redundancy relationship between cards.

For information on managing redundant cards, refer to the " Managing Redundant Cards" section in Chapter 13, "Switch Operating Procedures."

	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 CBSM cards by setting the firmware version level for each card. Run the setrev command from the PXM. See the " Managing Firmware Version Levels for CBSM Cards" section later in this chapter.
Step 3	addred <options> Related commands: dspred	Define which cards are operating as redundant cards. See the " Establishing Redundancy Between CBSM Cards" section later in this chapter.