Filter
Top Products
C-32
Cisco MGX 8220 Installation and Configuration
Release 5.0, Part Number 78-6430-03 Rev. D0, November 2003
Appendix C Firmware Upgrade and Downgrade Procedures
Graceful Upgrade and Downgrade Procedures
Step 5 For all SMs, set the start and end addresses in Flash memory where the boot code file will be written.
a. Enter the flashStartAddr and flashEndAddr commands to start the Flash memory file at
0xbfc00000 and end it at 0xbfc40000
shelf.1.<slot>.<type><a|s>flashStartAddr = 0xbfc00000
shelf.1.<slot>.<type>.<a|s>flashEndAddr = 0xbfc40000
b. Enter the tftp put <SM_BT_file> AXIS_SM_1_$slot.FW command.
c. Enter the chkflash command. This command calculates and compares the Flash checksum to verify
whether the boot code is correct.
d. Enter the version command. This command displays the version of the boot code currently stored
in Flash memory. This step downloads new firmware into the ASC.
Step 6 For all SMs, set the start and end addresses in Flash memory where the firmware file will be written.
a. Enter the flashStartAddr and flashEndAddr commands to start the Flash memory file at
0xbfc40000 and end it at 0xbfd00000
shelf.1.<slot>.<type><a|s>flashStartAddr = 0xbfc40000
shelf.1.<slot>.<type>.<a|s>flashEndAddr = 0xbfd00000
b. Enter the tftp put <SM_FW_file> AXIS_SM_1_$slot.FW command.
c. Enter the chkflash command. This command calculates and compares the Flash checksum to verify
whether the boot code is correct.
d. Enter the resetcd <standby_ASC> command. This command resets the standby card.
e. Enter the resetcd <active_ASC> command. This command resets the active card.
Step 7 For all stand-alone SMs
a. Enter the resetcd <stand-alone> command. This command resets the stand-alone card.
b. Enter the dspadrxlat command to ensure that the number of connection is correct.
Step 8 For all primary SMs in all redundancy groups
a. Enter the resetcd command <primary_SM>
b. Enter the resetcd command <secondary_SM>
Step 9 For all SMs, enter the dsptotals command.
This step is to examine the number of lines, ports, and channels after the upgrade or downgrade. The
values can be compared to those before the download and, therefore, it can be established that the
configuration has remained the same. Restore the ASC and SM configurations if necessary.
Procedure 20—Graceful Upgrade, 2-Core Card Set
Procedure 20 is used for 1.3.x to 3.y.
Step 1 Check compatibility.
With any downgrade technique, there is always the issue of compatibility. Any release can be
downgraded to any other release, but in many instances configuration information will be lost.
Hardware incompatibilities can prevent some downgrades. For example, Release 2 and Release 3
service modules require two Flash chips. Release 4 SMs will be shipped with a single Flash chip. A