Specifications

3-25
Cisco MGX 8260 Command Line Interface Guide
Release 1.2, Part Number 78-10987-01 Rev. B0, January, 2002
Chapter 3 Card Management
Upgrading Software Images
Warning Upgrading nonredundant cards interrupts service. Perform nonredundant upgrades
during light traffic periods or during a prearranged maintenance window.
If your MGX 8260 includes BSCs, perform the following steps to upgrade BSC Flash and software
images:
Step 1 Upgrade the boot Flash software on each BSC using the following command. Issue the command for
each BSC, replacing the <physicalSlotNumber> with the appropriate number for your configuration.
updatefls <physicalSlotNumber> IMAGE/BSC/bsc_r01.02.05.fls
Step 2 Ensure that the standby BSC is in the standby state.
Step 3 Upgrade the BSC software image using the following command. Issue the command for the first
primary BSC in your system, replacing the <logicalSlotNumber> with the appropriate number for your
configuration.
upgd <logicalSlotNumber> bsc_r01.02.05.fw
Answer Y to the “Are you sure?” warning message.
In redundant configurations, the upgd command resets the secondary BSC matched with the primary
BSC you specified in <logicalSlotNumber>. The secondary is now running the new release of boot
Flash and the software images.
Step 4 Ensure that the standby BSC has finished booting and is in the standby state.
Step 5 You can now commit or cancel the upgrade.
a. For redundant BSCs, if you wish to cancel the upgrade, enter the upgdcancel command. This
command can be used only if you have not entered the upgdcmit command. You cannot cancel an
upgrade for nonredundant cards.
Note Before you cancel an upgrade with the upgdcancel command, you need to to reset the
previous software on the flash card using the updatefls command.
b. To commit the new software, use the following command. Issue the command for the first primary
BSC in your system, replacing the <logicalSlotNumber> with the appropriate number for your
configuration.
upgdcmit <logicalSlotNumber>
If you have redundant BSCs installed, the upgdcmit command switches over the two BSCs. The
BSC that was secondary (with its newly upgraded database and software image) becomes the
primary BSC, and the previously primary BSC becomes the secondary BSC.
Warning You must execute either the upgdcmit command in Step 5b. or the upgdcancel command in
Step 5a. If you do not execute one of these commands, database corruption occurs.
Step 6 Ensure that the previously primary BSC has finished booting and is in the standby state.
Step 7 On redundant systems, force a switchback to the original primary BSC using the swcd command:
swcd <standbySlotNumber>
Where <standbySlotNumber> is the number of the original secondary BSC (the BSC that is currently
in active state).