Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5
Preparing Service Modules for Communication
Download this chapter
Preparing Service Modules for CommunicationPreparing Service Modules for Communication
Download the complete book
PDF Copy of the MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5PDF Copy of the MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5 (PDF - 7 MB)
give_us_feedback

Table Of Contents

Preparing Service Modules for Communication

Configuration Quickstart

Managing Firmware Version Levels for Service Modules

Locating Cards that Need the Firmware Version Set

Initializing Service Modules

Verifying Card Firmware Version Levels

Selecting MPSM Interfaces and Services

Establishing Redundancy Between Two Service Modules

Selecting a Card SCT

Selecting a Port SCT


Preparing Service Modules for Communication

This chapter describes how to prepare service modules for operation in an MGX switch. All MGX switch cards except PXM, SRM, XM-60, and RPM are service modules. Service modules add ATM, circuit emulation and Frame Relay services to a switch. Table 1-2 in "Preparing for Configuration," lists service module services and the service modules that provide them. This table also lists the interfaces supported on the service modules.

Tip For information on which slots support each type of service module, see Table 2-9 in Chapter 2, "Configuring General Switch Features." For information on the redundancy options for each service module, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5.

The procedures in this chapter help you complete the initial configuration required for each service module. After the initial configuration is complete, the card is ready for provisioning. Provisioning is described in the configuration and command reference guide for each service module. Table 1-1 in "Preparing for Configuration," lists the service module configuration and command reference guides.

The following sections provide a quickstart procedure for configuring service modules and describe the following procedures:

•Managing Firmware Version Levels for Service Modules

•Establishing Redundancy Between Two Service Modules

•Selecting a Card SCT

•Selecting a Port SCT

Note The Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5, describes the physical planning requirements for installing redundant service modules with standalone or redundant lines. If these requirements are not met, the planned service module configuration will not work properly.

Note For the purposes of this document, 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.

Configuration Quickstart

The quickstart procedure in this section provides a summary of the tasks required to prepare service modules for operation in an MGX switch. 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.

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 service modules by setting the firmware version level for each one.

See the "Managing Firmware Version Levels for Service Modules" section, which appears later in this chapter.

Step 3 

cnfcdmode <slot> <interfaceType> <service>

Related commands:

dspcd

dspcds

If you are configuring an MPSM card, select the back card interface type (T1, E1, T3 or E3). If you are configuring a MPSM-8-T1E1, you must also select the service (ATM, Frame Relay, or circuit emulation) this card will support.

Note This step is required only for MPSM cards.

See the "Selecting MPSM Interfaces and Services" section later in this chapter.

Step 4 

movelic <options>

If you are configuring an MPSM card and that card has feature licenses installed on it, use the movelic command to transfer the licenses to the license pool for the switch.

Note This step is required only for MPSM cards. See "MPSM Licensing"

Step 5 

addred <options>

Define which service modules are operating as redundant cards.

See the "Establishing Redundancy Between Two Service Modules" section, which appears later in this chapter.

Step 6 

cnfcdsct <sctid>

Related commands:

dspcd

This optional step applies only to AXSM, FRSM12, and MPSM-T3E3-155 cards and applies communications parameters from a preconfigured Service Class Template (SCT) file to all communications between the service module you are configuring and the other service modules in the switch.

See the "Selecting a Card SCT" section, which appears later in this chapter.

Managing Firmware Version Levels for Service Modules

The service modules 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 board 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 service modules 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

•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 service module 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 display these symptoms, but if the service module 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. 

8850_NY.7.PXM.a > dspcds

The following example shows the display for this command. The card state for the card in slot 3 is listed as Failed/Active. This is how a card appears when the runtime firmware version has not been selected. 

M8850_LA.7.PXM.a > dspcds

M8850_LA                         System Rev: 02.01   Sep. 27, 2001 20:33:09 PST

Chassis Serial No:   SAA03230375 Chassis Rev: B0     GMT Offset: -8

                                                     Node Alarm: NONE

Card  Front/Back          Card           Alarm      Redundant   Redundancy     

Slot  Card State          Type           Status     Slot        Type   

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


01    Active/Active       AXSM_4OC12     NONE       NA          NO REDUNDANCY

02    Empty               ---            ---        ---         ---    

03    Failed/Active       AXSM_16T3E3    NONE       NA          NO REDUNDANCY

04    Empty               ---            ---        ---         ---    

05    Active/Active       AXSME_2OC12    NONE       NA          NO REDUNDANCY

06    Active/Active       AXSM_16OC3_B   NONE       NA          NO REDUNDANCY

07    Active/Active       PXM45          NONE       08          PRIMARY SLOT

08    Standby/Active      PXM45          NONE       07          SECONDARY SLOT

09    Active/Active       RPM_PR         NONE       NA          NO REDUNDANCY

10    Empty               ---            ---        ---         ---    

11    Empty               ---            ---        ---         ---    

12    Empty Reserved               ---            ---        ---         ---    

13    Empty Reserved               ---            ---        ---         ---    

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 Service Modules."

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

Initializing Service Modules

Before a service module can operate, it must be initialized in a switch slot. The initialization process defines the runtime software version that will run on the card and identifies the slot in which the card operates. To initialize a service module, 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. The PXM45/A supports 192 UNI/NNI lines. The PXM45/B and PXM45/C support up to 4,000 UNI/NNI interfaces. Keep this information in mind as you add service modules to your switch.

Step 1 If you have not already done so, determine the software version number for the card by referring to the following release note documents:

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

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

Tip If you have trouble locating the runtime firmware version level, use the filenames on the PXM hard disk to determine the level. For more information, see the "Determining the Software Version Number from Filenames" section in Chapter 9, "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 enter 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.1(60)

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 appear as follows:

•All service modules except MPSM should display Active/Active.

•MPSM cards should display Standby/Empty.

To bring MPSM cards up to the Active/Active status, you must configure an interface type. For MPSM-8-T1E1 cards, you must also configure a service. For more information, see the "Selecting MPSM Interfaces and Services" section, which appears later in this chapter.

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 verify the firmware versions 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 follows: 

M8850_LA.7.PXM.a > dsprevs

M8850_LA                         System Rev: 02.01   Sep. 27, 2001 20:36:15 PST

MGX8850                                              Node Alarm: NONE

Physical  Logical   Inserted       Cur Sw              Boot FW             

Slot      Slot      Card           Revision            Revision            

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


01        01        AXSM_4OC12     2.1(60)             2.1(60)             

02        02        ---            ---                 ---                 

03        03        AXSM_16T3E3    2.1(60)             2.1(60)             

04        04        ---            ---                 ---                 

05        05        AXSME_2OC12    2.1(60)             2.1(60)             

06        06        AXSM_16OC3_B   2.1(60)             2.1(60)             

07        07        PXM45          2.1(60)             2.1(60)             

08        07        PXM45          2.1(60)             2.1(60)             

09        09        RPM_PR         ---                 ---                 

10        10        ---            ---                 ---                 

11        11        ---            ---                 ---                 

12        12        ---            ---                 ---                 

13        13        ---            ---                 ---                 

14        14        ---            ---                 ---

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

8850_NY.1.AXSM.a > dspversion


  Image Type   Shelf Type    Card Type         Version   Built On 

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

     Runtime          MGX         AXSM     2.1(0)        Feb 13 2001, 07:47:35 

        Boot          MGX         AXSM     2.1(0)        -

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

M8850_LA.7.PXM.a > dspcd 1

M8850_LA                         System Rev: 02.01   Sep. 27, 2001 20:38:48 PST

MGX8850                                              Node Alarm: NONE

Slot Number:   1    Redundant Slot: NONE 


                    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:      SAK0350007N         SAK0346003F         SBK0406001V 

Prim SW Rev:        2.1(60)             ---                 ---

Sec SW Rev:         2.1(60)             ---                 ---

Cur SW Rev:         2.1(60)             ---                 ---

Boot FW Rev:        2.1(60)             ---                 ---

800-level Rev:                                                   

800-level Part#:    800-05774-05        800-05383-01        800-05383-01

CLEI Code:          BAA1BADAAA          0000000000          BAI9ADTAAA 

Reset Reason:       On Power up

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 worksheet in Table E-6.

Step 5 Compare the versions you noted in Table E-6 with the latest versions listed in the release note documents:

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

•Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

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

Selecting MPSM Interfaces and Services

After you initialize an MPSM card, the status changes from Failed/Empty to Standby/Empty. MPSM cards are designed to support multiple interface types (T1, E1, T3, and E3) and multiple services (ATM, Frame Relay, and circuit emulation). To bring an MPSM-8-T1E1 card to the Active/Active state, you must specify the interface type and service to be used. To bring an MPSM-T3E3-155 card to the Active/Active state, you must specify only the interface type because this card can simultaneously support ATM and Frame Relay services on different ports. To configure MPSM interfaces and services, use the cnfcdmode command as described in the following procedure.

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

Step 2 Enter the cnfcdmode command using the following format: 

M8850_SF.7.PXM.a > cnfcdmode <slot> <interfaceType> <service>

Table 4-1 defines the parameters for this command. After you enter the cnfcdmode command, the card resets and the status changes to Active/Active.

Table 4-1 cnfcdmode Command Parameters

Parameter
Description

slot

Enter the number for the slot in which the MPSM card is installed.

interfaceType

Enter a number from the following list that selects the interface type to be used with the MPSM:

•T1 Interface = 1

•E1 Interface = 2

•T3 Interface = 3

•E3 Interface = 4

service

Enter a number from the following list that selects the service the MPSM will support:

•Frame Relay Service = 1

•ATM Service = 2

•CES Service = 3

Note This parameter applies only to MPSM-8-T1E1 cards.


The following example shows how to configure an MPSM-8-T1E1 card to use a T1 interface and Frame Relay services: 

M8850_SF.7.PXM.a > cnfcdmode 28 1 1

You are about to configure MPSM in slot 28 to : 

Service Type : Frame Interface Type : T1

Unknown line module back card present 

cnfcdmode: Do you want to proceed (Yes/No)? y

After you set the interface type and service, the card resets. You can check the status with the dspcd <slot> command. You can verify that the cnfcdmode command has been run by looking at the Inserted Card row of the dspcd display. Before MPSM-8-T1E1 configuration, the Inserted Card row displays the generic name MPSM-8T1E1. After configuration, the generic name changes to a specific name such as MPSM-8T1-FRM. Table 4-2 lists the card names and what they mean when they appear in the dspcd and dspcds command displays. While the card is resetting, the status will be Empty Resvd. When the reset is complete and the card is ready for provisioning, the status changes to Active.

Table 4-2 MPSM-8-T1E1 Card Names in the dspcd and dspcds Command Displays

Card Name
Description

MPSM-8T1E1

No service configured on card.

MPSM-8E1-ATM

Configured for ATM services and E1 interfaces.

MPSM-8E1-CES

Configured for circuit emulation services and E1 interfaces.

MPSM-8E1-FRM

Configured for Frame Relay services and E1 interfaces.

MPSM-8T1-ATM

Configured for ATM services and T1 interfaces.

MPSM-8T1-CES

Configured for circuit emulation services and T1 interfaces.

MPSM-8T1-FRM

Configured for Frame Relay services and T1 interfaces.


Establishing Redundancy Between Two Service Modules

Guidelines for configuring redundancy between two service modules are provided in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5. To establish redundancy between two service modules, use the following procedure.

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

Step 2 If you have not done so already, set the firmware version for both cards, as described in the "Initializing Service Modules" section.

Step 3 Enter the dspcds command to verify that both service modules 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 service module that will be the primary card, and replace <redSecondarySlotNum> with the slot number of the secondary service module.

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. Each service module type supports only one redundancy type, and the redundancy types are defined in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5.

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.

Tip If the switch displays the message, ERR: Secondary cd is already reserved, then lines are already in use on the specified secondary card. Enter the dnln command to bring down these lines before re-entering the addred command.

Note When MPSM cards are installed on the switch, the addred command will fail if there are not enough licenses on the secondary card (1:N redundant configurations) or in the license pool to match the licenses already in use on the primary card. For example, if the primary card is configured to use the ABR rate control feature, and if the configuration of other primary cards has not already added a ABR rate control license to the secondary card, the secondary card will require an ABR rate control license from the license pool. If no license is available, the addred command fails.

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

pop20two.7.PXM.a > dspred

pop20two                         System Rev: 02.01   Feb. 06, 2001 11:24:53 PST

MGX8850                                              Node Alarm: NONE

Primary  Primary   Primary    Secondary  Secondary  Secondary    Redundancy  

SlotNum   Type      State      SlotNum     Type       State         Type  

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

  1      AXSM      Active        2        AXSM       Standby        1-1          

  7      PXM45     Active        8        PXM45      Standby        1-1          

  15     SRM-3T3   Empty Res     16       SRM-3T3    Empty Resvd    1-1         


  31     SRM-3T3   Empty Res     32       SRM-3T3    Empty Resvd    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 two cards.

For information on managing redundant cards, see the "Managing Redundant Cards" section in Chapter 9, "Switch Operating Procedures."

Selecting a Card SCT

A Service Class Template (SCT) is a configuration file that defines the traffic characteristics of the various class of service queues in AXSM and FRSM12 service modules. The same card SCT may be used for multiple cards of the same card type.

Note An SCT must be registered before you can select it for a card or port. For instructions on registering SCTs, see "Registering SCT Files" in "Managing Service Class Templates."

To select an SCT for a card, use the following procedure.

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

Step 2 Enter the cc command to change to an active service module for which you will select an SCT. 

M8850_LA.8.PXM.a > cc 1


(session redirected)


M8850_LA.2.AXSM.a >

Note In a redundant pair, you must specify the SCT on the active card.

Step 3 All ports on the card must be down before you can configure the card SCT. To verify the status of the ports on the card, enter the dspports command. 

M8850_LA.2.AXSM.a > dspports

ifNum Line Admin Oper. Guaranteed Maximum   SCT Id ifType  VPI   minVPI maxVPI

           State State Rate       Rate     (D:dflt        (VNNI, (EVNNI,EVUNI)

                                            used)          VUNI)

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

    1  2.1    Up  Down    1412830   1412830   5       NNI      0      0      0

    2  2.2    Up  Down    1412830   1412830   5       NNI      0      0      0

    3  1.1    Up    Up    1412830   1412830   5       NNI      0      0      0

Enter the dnport command to bring down any ports that are in the Admin State "Up". 

M8850_LA.2.AXSM.a > dnport 2

dnport/dnallports can disrupt traffic on existing connections.

Use this command only to modify partition parameters or change SCT

Do you want to proceed (Yes/No) ? y

Step 4 Enter the cnfcdsct command. 

pop20two.1.AXSM.a > cnfcdsct <sctID>

Replace sctID with the number of the SCT that you want to assign to the card. Table 7-1 in "Managing Service Class Templates,"describes the SCTID options.

Note When a service module is powered up for the first time, the default card SCT file is used. You must run the cnfcdsct command in order to use another SCT file. The default SCT file s 0.

Step 5 To display the SCT assigned to a card, enter the following command: 

pop20two.1.AXSM.a > dspcd

The display card report displays a row labeled "Card SCT Id," which identifies the SCT assigned to the card. 

M8850_LA.1.AXSM.a > dspcd

                    Front Card          Upper Card          Lower Card

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


Card Type:          AXSM-4-622          SMFIR-2-622         SMFIR-2-622         

State:              Active              Present             Present             

Serial Number:      SAK0350007N         SAK0346003F         SBK043902FE         

Boot FW Rev:        3.0(0.171)P2        ---                 ---                 

SW Rev:             3.0(0.171)P2        ---                 ---                 

800-level Rev:      09                  13                  A1                  

Orderable Part#:    800-5774-5          800-5383-1          800-5383-1          

PCA Part#:          73-4504-2           73-4125-1           73-4125-1           

CLEI Code:          BAA1BADAAA          0000000000          BAI9ADTAAA          

Reset Reason:       Power ON Reset


Card Operating Mode: AXSM-A


SCT File Configured Version: 1


SCT File Operational Version: 1


Card SCT Id: 5



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

Step 6 Enter the upport <if> command to bring up any ports you brought down in Step 3. Replace <if> with the interface number of the downed port. 

M8850_LA.1.AXSM.a > upport 1

Step 7 Enter the dspports command to verify that all ports on the card are up. 

M8850_LA.1.AXSM.a > dspports

ifNum Line Admin Oper. Guaranteed Maximum   SCT Id ifType  VPI   minVPI maxVPI

           State State Rate       Rate     (D:dflt        (VNNI, (EVNNI,EVUNI)

                                            used)          VUNI)

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

    1  2.1    Up    Up    1412830   1412830   5       NNI      0      0      0

    2  2.2    Up    Up    1412830   1412830   5       NNI      0      0      0

    3  1.1    Up    Up    1412830   1412830   5       NNI      0      0      0

Selecting a Port SCT

A port SCT defines queue parameters that apply to egress queues on a port. Port SCTs are configured when provisioning ports. For more information on provisioning service module ports and configuring port SCTs, refer to the configuration and command reference guide for the service module. These guides are listed in Table 1-1 in "Preparing for Configuration."