Filter
Top Products
C-8
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
Standard Upgrade and Downgrade Procedures
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
Oxbfc40000 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 resetsys command. This command resets all cards on the shelf.
e. Enter the dspadrxlat command to ensure that the number of connections is correct.
Step 7 For all primary and stand-alone SMs, enter the dsptotals command.
Use this step 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.
Procedure 4—Standard Downgrade, 2-Core Card Set
Procedure 4 is used for 1.2.y to 2.x, 2.3.y to 2.x, and 3.3.y to 3.x.
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
Release 4 shelf containing BNM-E1 cards or service resource module 3T3 cards cannot be downgraded
to Release 2 or Release 3. Check the compatibility matrix to determine if a particular downgrade is
supported and how it could affect configuration loss.
Step 2 Enter the dspadrcxat command. Note the value of the ConnNumOfValidEntries parameter.
This value indicates the number of the connection. This command is run again at the end of the
procedure to ensure that the number of connections has not changed.
Step 3 For all stand-alone and primary SMs
a. Enter the dsptotals command.
The configuration of the shelf should not be changed during the downgrade process. Use this step
to examine the number of lines, ports, and channels before the upgrade or downgrade. A similar
step can be made to examine the same configuration parameters after the upgrade or downgrade
and, therefore, it can be established that the configuration has remained the same.
b. Enter the tftp put <ASC_BT_file> AXIS_ASC_BACKUP.FW command. This step downloads the
new boot code into the ASC.
c. Enter the chkflash command. This command calculates and compares the Flash checksum to verify
whether the boot code is correct.