Table of Contents

Configuring Cards
Configuration Tasks for Cards

Configuring Card Parameters

Viewing Card Configuration and Status
Viewing Summary Information for Cards
Viewing MSM Configuration and Status
Choosing the NSC Interface Mode
Configuring the NSC Interface Mode
Setting the ATM Queue Profile
Resetting a Card

Understanding Redundancy

Understanding Physical and Logical Slot Numbers
Using 1:N NSC Redundancy
Using 1:1 BSC Redundancy

Configuring BSC or NSC Redundancy

Viewing BSC and NSC Redundancy
Adding NSC Redundancy
Adding BSC Redundancy
Deleting Redundancy
Invoking a Switchback

Saving and Restoring Card Configurations

Backing Up Configurations
Uploading Configurations
Downloading Configurations
Restoring Configurations

Upgrading Software Images

Downloading Software Images
Upgrading Card Software

Card Management

This chapter explains how to configure cards and lines for service delivery.

Configuring Cards

Card parameters control the operational characteristics of the card as a whole. The MGX 8260 Media Gateway supports the following cards:

• SCC (System Controller Card)

  The SCC provides overall system control and database management for the shelf. In addition, the card provides optional broadband interfaces to the WAN backbone network, such as Fast Ethernet or SONET. SCCs are always in slots 9 or 10. When SCCs are installed in both slots, they operate as a redundant pair.

• NSC (Narrowband Service Card)

  The NSC adapts different media types and switches signals between carrier networks and services. The NSC supports a range of service and applications for both voice and data calls. NSCs are always in slots 1-8 and 11-16.

• BSC (Broadband Service Card)

  The BSC adapts different media types and switches signals between carrier networks and services. The BSC supports a range of service and applications for both voice and data calls, including DS3 circuits. BSCs are always in slots 11-16.

• DMC (Distribution Matrix Card)

  The MGX 8260 Media Gateway supports full multiplexing/demultiplexing and TDM-based switching at DS3 rates through the DMC. The DMC receives DS3 signals and distributes the services across NSC modules for processing. DMCs are always in slots 7 or 8.

Configuration Tasks for Cards

See the following sections for card configuration tasks.

• Configuring Card Parameters

• Configuring BSC or NSC Redundancy

Configuring Card Parameters

This sections describes how to view and set card-level parameters.

Viewing Card Configuration and Status

To list information for a single card, enter the lscd command, specifying the card location by a slot number in the MGX 8260 chassis. Slots are numbered from 1 through 16, starting at the left.

The system displays the card information.

=======================================================================
                      Physical Card Entry (lscd)
=======================================================================
Physical Card Number          :         11
Logical Card Number           :         11
Front Card Type               :         bsc
Back Card Type                :         dmcBsc6T3
Daughter Card 1 Type          :         bim4T3E3
Daughter Card 2 Type          :         *
Card State                    :         active
Card Service                  :         0
Hardware Revision             :         1
Firmware Revision             :         BSC_B_r01.01.b1
Software Revision             :         BSC_r01.01.b1
Front Card Serial #           :         bsc-093
Back Card Serial #            :         t3e3-141
Fab Version                   :
Failure Reason                :         failResonNone
Reset Reason                  :         watchDogReset
Mismatch Reason               :         noMismatch
Integrated line alarm state   :         Clear
Line performance alarm state  :         Clear
EMM temperature alarm state   :         Clear
EMM voltage alarm state       :         Clear
SW error alarm state          :         Clear
Component failure alarm state :         Clear
ATM Queue Profile #           :         1
RAM Backup                    :         disabled
Interface Mode                :         bkcd
 

Displayed Information	Description
Physical Card Number	The physical slot number of the card
Logical Card Number	The logical slot number of the card
Front Card Type	The front card type: dmc—Distribution Matrix Card. scc—Switch Control Card. bsc—Broadband Service Card. nsc—Narrowband Service Card.
Back Card Type	The back card type: scc-4fe—Switch Control Card with four Fast Ethernet (100 Mbps) ports scc4OC3—Switch Control Card with four OC-3 ports scc4OC3MM—Switch Control Card with four mulit-mode OC-3 ports bsc12T3—Broadband Service Card with 12 DS3 ports dmcBsc6t3—Distribution Matrix Card or BSC with six DS3 ports nsc-16t1e1—Narrowband Service Card with sixteen T1 ports rnd16-t1e1—Redundancy backcard for NSC blank—No back card
Daughter Card1 Type	The type of daughter card installed on the NSC or SCC card: NSC types: msmDSPV—Multiservice module DSP voice SCC type: bim4FE—Broadband Interface Module with four Fast Ethernet ports bim4OC3ATM—Broadband Interface Module with 4 OC-3 ATM ports
Daughter Card 2 Type	The type of secondary daughter card installed. See Dgtr Crd1 types.
Card State	The status of the card: empty in-boot active standby mismatch failed unknown
Card Service	A bitmap of the services offered by the card. When set, the card offers the service: bit 0: ATM bit 1: Frame Relay (reserved for future use) bit 2: Voice bit 3: IP Emulation (reserved for future use) For more information, see the "Understanding Bitmaps" section.
Hardware Revision	The hardware revision of the card.
Firmware Revision	The firmware revision of the card.
Software Revision	The software revision of the card.
Front Card Serial #	The serial number of the front card.
Back Card Serial #	The serial number of the back card.
Fab Version	The fab version of the card.
Failure Reason	The reason of the last card failure, as follows: hwMSMFailed—One or both MSMs failed hwSarFailed—Sar failed hwPCIAErrInt—PCI-A error interrupt hwASXFailed—ASX failed hwALBMFailed—ALM or ABM switch port failed hwCubitFailed—Cubit failed hwBusCycleTmOut—Bus cycle timeout hwHardDrvFailed—Hard drive failed hwMgmtEthFailed—Management Ethernet failed hwDMCFailed—DMC failed hwSerlPtFailed—Serial port failed swStrvBkgdTask—Background task starvation swKeyTaskFailed—Critical task failed swFailReason—Software failed hwFailReason—Hardware failed heartBeatLost—Lost the heartbeat imageDownLoadFailed—Image download failed failedToMoveToActive—Transition to active state failed failedToInitApps—Application initialization failed configDownLoadFail—Configuration download failed remoteCardFailed—Remote card reported a failure
Reset Reason	The reason for the mismatch for the card, as follows: noMismatch configMismatchHw—configuration file and hardware do not match fcAndBcMismatch—the front and back card do not match daughterCardBcMismatch—the daughter card and back card do not match peerHardWareMismatch—the two SCC cards do not match dmcMismatch—DMC configuration mismatch with the hardware noBackCard—No back card noDaughterCard—None or invalid daughter cards
Mismatch Reason	The reason the card was last reset, as follows: shellReset hardReboot softRebootNoImage softReboot chipError eventLogReset taskError softwareUpgrade gracefulSwitchover dmcRemovedSwitchover sccBcRemovedSwitchover appsInitFailed plfmTimerExpired ideReformat, unknownResetReason
Integrated line alarm state	The state of the integrated line alarm for the card: No Alarm Minor Alarm Major Alarm
Line performance alarm state	The state of the line performance alarm for the card: No Alarm Minor Alarm Major Alarm
EMM temperature alarm state	The state of the EMM temperature alarm for the card: No Alarm Minor Alarm Major Alarm
EMM voltage alarm state	The state of the EMM voltage alarm for the card: No Alarm Minor Alarm Major Alarm
SW error alarm state	The state of the software error alarm for the card: No Alarm Minor Alarm Major Alarm
Component failure alarm state	The state of the component alarm for the card: No Alarm Minor Alarm Major Alarm
ATM Queue Profile	The queue profile for ATM traffic on the SCC. Valid profiles: 1 to 10.
RAM Backup	The status of RAM backup facility: enabled disabled
Interface Mode	The interface mode: bkcd —Use the back card signals bkpln—Use back plane signals npbkcd—No back card mode For more information, see the "Choosing the NSC Interface Mode" section.

Viewing Summary Information for Cards

To list summary information for all cards, enter the lscds command.

The system displays information for all cards:

=====================================================================
                     Physical Card Entries (lscds)
=====================================================================
PhyCd LogCd  FC     BC      Dgtr Cd1  Dgtr Cd2  Card State   SW Rev
===== ===== ==== ========= ========== ========  ========== ==========
   1     1  nsc  nmc16T1E1    msmDSPV  msmDSPV  active    NSC_r01.01.b1
   2     2  nsc  nmc16T1E1    msmDSPV  msmDSPV  active    NSC_r01.01.b1
   3     3  nsc  nmc16T1E1    msmDSPV  msmDSPV  active    NSC_r01.01.b1
   4     4  nsc  rnd16T1E1    msmDSPV  msmDSPV  standby   NSC_r01.01.b1
   5     5  nsc  nmc16T1E1    msmDSPV  msmDSPV  active    NSC_r01.01.b1
   6     6  nsc  nmc16T1E1    msmDSPV  msmDSPV  active    NSC_r01.01.b1
   7     7    *          *          *        *  empty     Unknown
   8     8    *          *          *        *  empty     Unknown
   9     9  scc     scc4FE     bim4FE        *  standby   SCC_r01.01.b1
  10     9  scc     scc4FE     bim4FE        *  active    SCC_r01.01.b1
  11    11  bsc  dmcBsc6T3   bim4T3E3        *  active    BSC_r01.01.b1
  12    12  bsc  dmcBsc6T3   bim4T3E3        *  active    BSC_r01.01.b1
  13    13  bsc  dmcBsc6T3   bim4T3E3        *  active    BSC_r01.01.b1
  14    14  bsc  dmcBsc6T3   bim4T3E3        *  active    BSC_r01.01.b1
  15    15  bsc  dmcBsc6T3   bim4T3E3        *  active    BSC_r01.01.b1
  16    16    *          *          *        *  empty     Unknown 
 

Displayed Information	Description
PhyCd	The physical slot number of the card
LogCd	The logical slot number of the card
FC	The front card type
BC	The back card type
Dgtr Cd1	The type of daughter card installed on the NSC or SCC card
Dgtr Cd2	The type of secondary daughter card installed on the NSC card
Card State	The status of the card
SW Rev	The software release and version that is running on the card. The first letters identify the card type and the numbers identify the major release, minor release, and version.

Viewing MSM Configuration and Status

To view DSP information, enter the lsdsps command.

The system lists current DSP information:

======================================================================
                MultiService Module (DSP) Entries (lsdsps)
======================================================================
  Slot Number      DSP MSM Number    DSP Number           DSP Status
===============  ================== ================  ================
         2                  1                1               active
         2                  1                2               active
         2                  1                3               active
         2                  1                4               active
         2                  1                5               active
         2                  1                6               active
         2                  1                7               active
         2                  1                8               active
 

Displayed Information	Description
Slot Number	The slot number of the multi-service module
DSP MSM Number	The multi-service module number
DSP Number	The DSP number on the multi-service module
DSP Status	The status of the DSP

To view MSM information, enter the lsmsms command.

The system lists current MSM information:

====================================================================
                MultiService Module (MSM) Entries (lsmsms)
====================================================================
  Slot Number        MSM Number       MSM Type         MSM Status
===============  ================ ===============   ================
         2                  1          msmDSPV            active
         2                  2          msmDSPV            active
         6                  1          msmDSPV            active
         6                  2          msmDSPV            active
 

Displayed Information	Description
Slot Number	The slot number of the multi-service module
MSM Number	The multi-service module number
MSM Type	The type of multi-service module
MSM Status	The multi-service module status

Choosing the NSC Interface Mode

The interface mode controls the signal source for the T1 interface of an NSC card. There are three modes (see Figure 3-1)

• Back card

• Back plane

• No back card

All sixteen T1 lines operate in the same mode. The system ignores this setting for cards other than the NSC.

NSC-BC -> NSC-FC -> Bus -> SCC-FC -> SCC-BC
where BC = Back Card and FC = Front Card
 

DMC-BC -> DMC-FC -> Bus -> NSC-FC -> Bus -> SCC-FC -> SCC-BC
where BC = Back Card and FC = Front Card
 

NSC-FC -> Bus -> SCC-FC -> SCC-BC
where BC = Back Card and FC = Front Card
 

Configuring the NSC Interface Mode

You can only change the interface mode on an NSC while it's in one of the following states:

• Active

• InBoot

• Mismatch

• Failed

To set the NSC interface mode, enter the chcdif command, specifying the card number and NSC interface mode. Valid NSC interface mode settings are:

1: back card (default)

2: back plane

3. no back card

Note   Configuring the back card mode with out a back card installed results in a card mismatch.

The system sets the specified interface mode on the target NSC card. The following example sets the interface mode of card 13 to back plane:

chcdif 13 2
 

The card resets and reboots into backplane mode.

Setting the ATM Queue Profile

The ATM queue profile defines the queue behavior for the SCC card. You can only change the ATM Queue profile on the active SCC.

To set the ATM queue profile, enter the chqprf command, specifying the slot number of the SCC card, either 9 or 10, and the queue profile, a number from 1 to 10. Profile 1 is the default.

The system sets the specified queue profile on the target SCC card.

Resetting a Card

The resetcd command restarts a card and restores its stored configuration. The following table shows response of the reset command for different card types and operating states:

Table 3-1: Response of Reset Command by Card and State

State	SCC slots 9/10	DMC slots 7/8	NSC slots 1-8, 11-16 and BSC slots 11-16
active	OK	Service not available on DMC	OK
standby			OK
empty	Card does not exist.		Card does not exist
inBoot	OK		OK
mismatch			OK
failed			OK
unknown	Card does not exist	N/A	N/A

Warning Resetting a card interrupts service. Perform this operation during light traffic periods or in a pre-arranged maintenance window.

To reset a card, enter the resetcd command, specifying the card to reset.

The following example resets card 13:

resetcd 13

Understanding Redundancy

The MGX 8260 Media Gateway supports both redundant and non-redundant operation for all cards. The SCC and DMC don't require user setup for redundant operation. To configure redundancy for the NSC or BSC, you define protection pairs. The Cisco MGX 8260 uses 1:N protection for NSCs and 1:1 protection for BSCs. With protection, the system switches to a protection card if an active card fails.

Understanding Physical and Logical Slot Numbers

Cards configured for redundancy may have logical numbers that are different than physical slot numbers. The physical slot number always represents the physical location of the card in the chassis. The logical slot number is an abstract concept that helps the system keep track of primary and secondary cards.

With 1:1 redundancy, the primary and secondary cards both have the same logical slot number. As such, the system treats them as a single entity for configuration operations. With 1:N redundancy, the secondary card uses logical slot number 0. During switchover, the secondary card assumes the logical number of the card it protects.

Using 1:N NSC Redundancy

A single secondary card can support multiple primary cards. In this configuration, a failure of any of the primary cards causes a switchover to the designated secondary. After a switchover, the other NSCs are unprotected until you fix the problem and restore the primary card to the active state.

For example, a 1:2 redundancy configuration with slot 3 covering slot 1 and slot 5 actually has two redundancy pairs (see Figure 3-2).

If the primary card in slot one fails, the system switches to the secondary NSC, and the secondary NSC assumes the logical slot number of the card that failed (see Figure 3-3).

Using 1:1 BSC Redundancy

You configure BSC protection using a pair of cards configured for 1:1 redundancy. After you configure a redundant pair of BSCs, both cards reboot and return to operation with the same logical slot number. The card LED displays green for the active card and yellow for the standby card.

For example, you can configure cards 15 and 16 for redundancy (see Figure 3-4).

A failure of the active card causes a switchover to the backup card. During the switchover, the active and standby roles are reversed (see Figure 3-5). The card that failed reboots, and the Card LED changes to either yellow or red, depending on the type of problem. After a switchover, the other BSC is unprotected until you fix the problem and restore the primary card to the active state.

After repair of the failure, you restore normal operation by invoking a switchback. The system does not automatically restore the protection pair to its original state. For more information, see Invoking a Switchback.

Configuring BSC or NSC Redundancy

This section describes the process for configuring redundancy for BSC and NSC cards.

Viewing BSC and NSC Redundancy

To view all redundancy pairs, enter the lsreds command.

The system displays all redundancy pairs:

=======================================================================
                     Card Redundancy Table  (lsreds)
=======================================================================
  Primary Slot   Secondary Slot
=============== ================
  1              3
  5              3
 

Displayed Information	Description
Primary Slot	The physical slot for the primary card of the redundancy pair
Secondary Slot	The physical slot for the secondary card of the redundancy pair

Adding NSC Redundancy

There are two possible NSC redundancy scenarios: with and without DMC.

• NSC redundancy without DMC

  This scenario requires a redundant back card in the secondary slot. The back card protects the primary slots in the event of a primary card failure.

• NSC redundancy with DMC

  This scenario does not require, and cannot have, a redundant back card.

Both scenarios require assignment of primary and secondary slot numbers in pairs. The MGX 8260 chassis only supports one secondary slot.

Configuring NSC Redundancy without DMC

To configure NSC redundancy without DMC, follow these steps:

Step 2   Verify that each primary, active NSC is in the back card mode and is in the active state. List the operational status of all cards using the lscds command.

Step 3   Add a redundancy pair using the addreds command, specifying the slots of the primary and secondary slots.

The primary slot is active during normal operation. The secondary slot is in standby during normal operation and protects the primary slot in the event of a primary failure.

The following example creates a redundancy pair with slot 1 as primary and slot 3 as secondary:

addreds 1 3
 

Step 4   Repeat the previous step to assign additional primary slots to the designated secondary slot. Each MGX 8260 chassis can have only one secondary slot.

Configuring NSC Redundancy with DMC

To configure NSC redundancy with DMC, follow these steps:

lscds
 

Step 2   Verify that the redundant NSC does not have a redundancy back card installed. See "Viewing Summary Information for Cards" section.

Step 3   Verify that each primary NSC does not have a back card installed.

Step 4   Add a redundancy pair using the addreds command.

Step 5   Repeat the previous step to assign additional primary slots to the designated secondary slot. Each MGX 8260 chassis can have only one secondary slot for NSC cards.

Adding BSC Redundancy

In order to successfully configure a redundant pair, the following conditions must be true:

• The hardware configuration of the two BSCs must be identical

• The firmware version of the two BSCs must be identical

• The redundant BSC must not have any lines configured

Warning Adding BSC redundancy interrupts service. Perform this operation during light traffic periods or in a pre-arranged maintenance window.

To configure BSC redundancy, follow these steps:

Step 2   Add a redundant "Y" cable between all ports on the two cards.

Step 3   From a management session, add a redundancy pair using the addreds command.

Both cards reboot and return to operation with the same logical slot number.

Deleting Redundancy

To delete a redundancy pair, enter the delreds command specifying the primary and secondary slots. The following example deletes the redundancy pair where slot 1 is primary and slot 3 is secondary:

delreds 1 3
 

The redundant card continues to protect other primary cards with which it is paired.

Invoking a Switchback

The switchover from primary to secondary cards is automatic when a primary card fails. Switching back is a manual task. The following table shows the response of the switchback command as a function of card type and operational state:

Table 3-2: Response for the Switch Card Command by Card and State

State	SCC slots 9/10	DMC slots 7/8	NSC slots 1-8, 11-16 and BSC slots 11-16
active	OK	Service not available on DMC	Switchback from secondary to primary only.
standby	Illegal slot number for this state.
empty	Card does not exist.
inBoot	Illegal slot number for this state.
mismatch
failed
unknown		N/A	N/A

To force a switchback, enter the swcd command specifying the physical number of the primary card in a protection pair.

Note   To force a switchover, rather than a switch back, reset the primary card using resetcd.

Saving and Restoring Card Configurations

You can save or restore system configuration from a tftp server on the management network. To use tftp, you must conform to the Cisco file-naming convention and supply a six-character security key. The security system disables tftp file transfers if the key is missing or does not match. The following procedures explain how to save and restore card configurations.

Backing Up Configurations

You can back up the current MGX 8260 configuration with the dbbkup command. This command captures the configuration information for all cards and saves it to a file on the SCC hard drive. The system assigns a name for this file and reports it to the user.

To save a card configuration, follow these steps:

Step 2   At the command prompt, type dbbkup.

The system reports the result of the operation and the name of the backup file.

Step 3   Record the file name for future reference. By default, the backup file name matches the software version name with a .cfg extension. For example, the backup file for software release R01.02.03 is SCC_R01.02.03.CFG

Uploading Configurations

The MGX 8260 stores configuration information for all cards in the chassis in the SCC hard drive. You can upload this configuration information to an external server for safekeeping. Before performing this procedure, check your records to determine the name of the backup file you want to upload.

To upload a configuration file, follow these steps:

Step 2   Initiate a tftp session with the target MGX 8260 Media Gateway using the tftp command.

tftp <IP Address>
 

Specify the IP address of the MGX 8260 management port in standard IP dot notation.

Note   tftp is an operating system command executed by the management workstation.

Step 3   Set the transfer mode to binary:

mode binary
 

Step 4   Start the file transfer using the tftp get command.

get <FileName>.<SecurityKey>

Parameter	Description
FileName	The name of the configuration file. This name indicates the card type, major release, minor release, and version, followed by the .cfg extension. For example, SCC_R01.02.03.CFG is the database for software release 1.2.3.
SecurityKey	The six-character alphanumeric security key for the target MGX8260

Step 5   Confirm the file transfer by checking the distribution directory.

Downloading Configurations

The MGX 8260 stores configuration files on the SCC hard drive, so you generally don't need to download a configuration file. However, if you prefer to save configuration files on an external server, you can download the file to the MGX 8260 before invoking dbrstr. Before performing this procedure, check your records to determine the name of the backup file you want to download.

To restore a card configuration, follow these steps:

Step 2   Initiate a tftp session with the target MGX 8260 Media Gateway using the tftp command.

tftp <IP Address>
 

Specify the IP address of the MGX 8260 management port in standard IP dot notation.

Note   tftp is an operating system command executed by the management workstation.

Step 3   Set the transfer mode to binary using the tftp mode command.

mode binary
 

Step 4   Start the file transfer using the tftp put command.

put <srcImageFileName> <destImageFileName>.<Security Key>

Parameter	Description
srcImageFileName	The path and file name of the source file stored on your server
destImageFileName	The name of the configuration file. This name indicates the card type, major release, minor release, and version, followed by the .cfg extension. For example, SCC_R01.02.03.CFG is the database for software release 1.2.3.
SecurityKey	The six-character alphanumeric security key for the target MGX8260

Step 5   Confirm the file transfer.

Restoring Configurations

You can restore the MGX 8260 to a previous configuration using the dbrstr command. This command retrieves a configuration file from the SCC hard disk and restores all cards accordingly. Before performing this procedure, check your records to determine the name of the backup file you want to restore.

Warning This is a service-affecting action. Perform this task when the equipment is down or during a pre-arranged maintenance window.

To restore MGX 8260 configurations, follow these steps.

Step 2   At the command prompt, type database restore command and the configuration file name. Omit the .cfg extension from the file name.

For example:

dbrstr scc_r01.02.03
 

Step 3   Restart the target card using the resetcd command.

Upgrading Software Images

When upgrading the MGX 8260 Media Gateway you download the new software and then upgrade the cards. A software upgrade consists of a set of files, one for each type of card in your chassis. Plan to upgrade every card in the chassis to the same software version level. For redundant systems, you can upgrade software without interrupting service.

Downloading Software Images

You can download e software image for any card from a tftp server on the management network. When downloading files, you must conform to the Cisco file-naming convention, and supply a security key. The security system disables tftp file transfers if the key is missing or does not match. The MGX 8260 can store up to 10 software images per card type.

To download a new software image, follow these steps:

Step 2   Initiate a tftp session with the target MGX 8260 Media Gateway using the tftp command.

tftp <IP Address>
 

Specify the IP address of the MGX 8260 management port in standard IP dot notation.

Note   tftp is an operating system command executed by the management workstation.

Step 3   Set the transfer mode to binary:

mode binary
 

Step 4   Transfer the new software image to the chassis using the put command.

put <srcImageFileName> <destImageFileName>.<key>

Parameter	Description
srcImageFileName	The path and file name of the source file stored on your server
destImageFileName	The name of the software image. This name indicates the card type, major release, minor release, and version, followed by the .img extension. For example, SCC_R01.02.03.IMG indicates SCC software release 1.2.3. The release and version information (R01.02.03) must be 9 characters in length.
key	The 6-character tftp security key

Step 5   Confirm the file transfer.

Upgrading Card Software

The upgrade process for redundant cards is graceful and doesn't interrupt service. When you invoke the process, the system upgrades and restarts the standby card only. You then have the option to commit or cancel the upgrade. When you commit the software, the system switches to the standby card and then upgrades the other card. This upgrade does not interrupt traffic.

Warning Upgrading non-redundant cards interrupts service. Perform non-redundant upgrades during light traffic periods or during a pre-arranged maintenance window.

Before performing either type of backup, make sure you have a current backup of the configuration database. You back up the database using the dbbkup command from the command line interface.

To upgrade the software image:

Step 2   Log in as the SuperUser or a user with level 1 privileges

Step 3   Initiate the upgrade procedure using the upgd command, specifying the logical slot of the card to upgrade and the file name of the software image. The system upgrades and reboots the standby card.

upgd <logicalSlotNumber> <destImageFileName>
 

Parameter	Description
logicalSlotNumber	The logical number of the card to upgrade. Values: SCC: 9 BSC: 11-16 NSC: 1-8 and 11-16
destImageFileName	The name of the software image. This name indicates the card type, major release, minor release, and version, followed by the .fw extension. For example, SCC_R01.02.03.FW indicates SCC software release 1.2.3. The release and version information (R01.02.03) must be 9 characters in length. This name is the same as the downloaded file name except for the extension.

Step 4   Verify the software versions on the active and standby cards using the lslgcd command.

Step 5   For redundant cards, type the upgdcmit command, specifying the logical slot number of the card. The system switches to the standby card and upgrades the other one. If you don't want to use the new software, use the upgdcancel command, specifying the logical slot number of the card.

Step 6   For redundant BSC or NSC upgrades, force a switchback. This is important because the standby card doesn't protect the active card. For more information on switchover, see Invoking a Switchback.

Note   You can't cancel an upgrade for non-redundant cards.

Posted: Mon Oct 2 22:56:42 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.