cc/td/doc/product/access/sc/rel7/soln/voip13
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Upgrading Cisco Media Gateway Software

Determining Your Cisco IOS Version

Determining Memory Requirements

Upgrading the Cisco AS5300 Universal Access Server

Blocking Voice Gateway Circuits

Loading a Cisco IOS Upgrade on the Cisco AS5300

Upgrading Cisco VCWare

Upgrading the Cisco AS5350 or Cisco AS5400 Universal Gateway

Upgrading the Cisco AS5800 Universal Access Server

Backing Up Your AS5800 Configuration

Installing New IOS Software on the Cisco AS5800

Software Upgrade Verification

Upgrading the Cisco AS5850 Universal Gateway

Upgrading from a High-Availability Image

Upgrading from a Nonhigh-Availability Image


Upgrading Cisco Media Gateway Software

This chapter describes procedures for upgrading software on Cisco network access servers (NAS). It contains the following sections:

• Determining Your Cisco IOS Version

• Determining Memory Requirements

• Upgrading the Cisco AS5300 Universal Access Server

• Upgrading the Cisco AS5350 or Cisco AS5400 Universal Gateway

• Upgrading the Cisco AS5800 Universal Access Server

For detailed information about obtaining and managing Cisco IOS images, refer to Appendix B, "Managing Cisco Media Gateway Software."

Determining Your Cisco IOS Version

To determine the version of Cisco IOS software running on your NAS, log in to the Cisco AS5X00 and enter the show version EXEC command:

AS5300> show version
Cisco Internetwork Operating System Software
IOS (tm) 12.1 Software c5300-i-mz, Version 12.1(2), RELEASE SOFTWARE

Determining Memory Requirements

The amount of memory required by a Cisco IOS image depends on the platform and the SS7 Interconnect Solution that the platform supports. To determine the latest memory requirements, refer to the following online documents:

• Release Notes for Cisco SS7 Interconnect for Access Servers Release 2.2(B)

• Release Notes for Cisco SS7 Interconnect for Voice Gateways Release 1.3

Upgrading the Cisco AS5300 Universal Access Server

The Cisco AS5300 Universal Access Server will not allow the Flash to be overwritten during normal operation. You need to configure your router to boot up from boot Flash (or ROM) so you can copy the upgraded version of Cisco IOS Software into the regular system Flash.

Blocking Voice Gateway Circuits

Cisco AS5300s that use H.225 Resource Availability Indicator (RAI) to load-share VoIP traffic with other voice gateways require special preparation before you can place them out of service. You must block the appropriate circuits on the Cisco SC2200 and wait for in-progress calls to disconnect on the affected Cisco AS5300. Doing so will cause the NAS to send a "resource unavailable" message to the local H.323 gatekeeper, which will then route calls only to the remaining Cisco AS5300s.

Note This procedure is required only for the Cisco SS7 Interconnect for Voice Gateways Solution in environments where H.225 RAI is used to share egress traffic among multiple Cisco AS5300s.

Complete the following steps before placing the Cisco AS5300 out of service:

Step 1 On the Cisco SC2200, block the circuits that terminate on the NAS.

SC2200 mml> blk-cic:point code:CIC=circuit identification code,RNG=CIC+range

Note For more information on MML commands, refer to MML Command Reference at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/sw_ref/elmmlref.htm 

Step 2 When all in-progress calls have disconnected, disable the loopback interface on the NAS. H.323-id and gatekeeper information is contained in the loopback interface, and disabling this interface will cause the NAS to unregister with the local gatekeeper.

AS5300(config)# interface loopback 0
AS5300(config)# shutdown

Step 3 Save the configuration of the NAS. This command will prevent the NAS from re-registering with the gatekeeper until Redundant Link Manager (RLM) and all ISDN channels have initialized. The NAS is now ready to be shut down.

AS5300# write memory

Loading a Cisco IOS Upgrade on the Cisco AS5300

Complete the following steps to upgrade the Cisco IOS Software on a Cisco AS5300:

Step 1 Back up the boot Flash memory.

AS5300# copy bootflash tftp

Step 2 Back up the Flash memory.

AS5300# copy flash tftp

Step 3 Back up your configuration. Be sure to use a distinct name for the startup configuration for each of your Cisco AS5300s.

AS5300# copy startup-config tftp

Step 4 Change the configuration register from its current setting to 0x2101 so that the Cisco AS5300 boots from boot Flash memory. Be sure to enter the show version command and take note of the current configuration register settings.

AS5300# show version
AS5300# configure terminal
AS5300(config)# config-reg 0x2101
AS5300(config)# exit
AS5300#

Step 5 Reload the Cisco AS5300.

AS5300# reload

Step 6 Copy the Cisco IOS software to Flash memory.

AS5300(boot)# copy tftp flash

Step 7 Change the configuration register back to its original setting so that the Cisco AS5300 boots from Flash. In this example, the original setting was 0x2102.

AS5300(boot)# configure terminal
AS5300(config)# config-reg 0x2102
AS5300(config)# exit
AS5300(boot)#

Step 8 Reload the Cisco AS5300.

AS5300(boot)# reload

Note Do not save the configuration at this time.

Step 9 Confirm the software upgrade.

AS5300# show version

Note Complete Step 10 through Step 13 only if your network uses H.225 RAI to load-share VoIP traffic among multiple Cisco AS5300s.

Step 10 Verify that the Redundant Link Manager (RLM) is operational.

AS5300# show rlm group 1 status

Step 11 Verify that all ISDN channels on the NAS show "maintenance pending."

AS5300# show isdn service

Step 12 On the Cisco SC2200, unblock the circuits that terminate on the NAS.

SC2200 mml> unblk-cic:point code:CIC=circuit identification code,RNG=CIC+range

Step 13 Enable the loopback interface on the NAS. The NAS will re-register with the gatekeeper and begin processing calls.

AS5300(config)# interface loopback 0
AS5300(config)# no shut

Upgrading Cisco VCWare

Cisco VCware is a software image that runs only on voice cards used in the Cisco AS5300. Because Cisco VCWare is a separate image from Cisco IOS Software, it must be loaded and upgraded separately from Cisco IOS Software. For all other Cisco voice gateways using C54x series DSPs, the DSPware is embedded in the Cisco IOS Software image, so in those systems, Cisco VCware is not used. For instructions on upgrading Cisco VCWare, refer to Release Notes for Cisco VCWare on Cisco AS5300 Universal Access Servers at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/vcw_rn/index.htm

Upgrading the Cisco AS5350 or Cisco AS5400 Universal Gateway

Complete the following steps to upgrade the Cisco IOS software on a Cisco AS5350 or Cisco AS5400 universal access gateway:

Step 1 Display the contents of Flash memory:

Router# cd flash:
Router# dir
Directory of flash:/

1 -rw- 9950528 Jan 01 2000 00:48:59 c5350-js-mz.121-1.XD1.bin

32768000 bytes total (13041600 bytes free)

Step 2 Copy the new image from the remote TFTP server into Flash memory. Make sure that you specify your own TFTP server's IP address and Cisco IOS filename. If you encounter issues with upgrading the image, be sure that you can ping the TFTP server and that appropriate directory permissions are configured on the TFTP server. To see the bangs (!) during the download operation, enable line wrap in your terminal emulation software.

Note If you have available space for two images, leave both images in Flash memory. If necessary, you can easily revert back to the previous image. Enter the boot system flash newiosname.bin command to point to the new image filename. By default, the first image in Flash memory is loaded.

If you do not have available space, during the copy operation the system displays a message telling you to delete the current file and squeeze the flash to make room for the new image. Enter the delete flash:version command, followed by the squeeze flash command, to perform this delete-and-squeeze operation. Then proceed with the copy operation.

Router# copy tftp flash
Address or name of remote host [172.22.191.135]? 172.22.191.135
Source filename [c5350-js-mz.121-1.XD1.bin]? c5350-js-mz.121-3.T.bin
Destination filename [c5350-js-mz.121-3.T.bin]?
Accessing tftp://172.22.191.135/c5350-js-mz.121-3.T.bin...
Loading c5350-js-mz.121-3.T.bin from 172.22.191.135 (via FastEthernet0/0): !!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 9775616/19551232 bytes]

9775616 bytes copied in 66.424 secs (148115 bytes/sec)
Caution Occasionally TFTP errors occur. Make sure that the verifying checksum reports "OK." Do not reload the gateway if the checksum reports errors.

Step 3 Verify that the new image was downloaded. In this example, notice that the Cisco IOS Release 12.1(1)XD image is the first in Flash memory, so it is loaded during the boot sequence. To boot using the new image, you must either delete the unwanted image or use the boot system command to specify the alternate image to use during the boot sequence.

Router# dir flash:
Directory of flash:/

1 -rw- 9950528 Jan 01 2000 00:48:59 c5350-js-mz.121-1.XD1.bin
2 -rw- 9775616 Jan 01 2000 00:59:10 c5350-js-mz.121-3.T.bin
32768000 bytes total (13041600 bytes free)

For more information on deleting the image, refer to the document Cisco IOS File System, available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113aa/113aa_2/allplats/ifs.htm

Note The Cisco AS5350 and Cisco AS5400, unlike the Cisco AS5200 and Cisco AS5300, use a Class A Flash File System.

Step 4 To specify the alternate image that is to be used during the boot sequence use the boot system flash newiosname.bin command to specify the location (device) and name of the image to be used:

Router(config)# boot system flash c5350-js-mz.121-3.T.bin
Router(config)# ^Z
Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]

To verify that this command is in effect, use the show running-configuration command. Save your running configuration before the reload so that the gateway loads the correct image.

Step 5 Reload the Cisco AS5350 or Cisco AS5400 to run the new image. If you erased the old Cisco IOS image, make sure that the boot system flash oldiosname.bin command is not enabled and pointing to the old image file name; otherwise, the gateway gets stuck trying to reload the old image over and over again.

Router# reload
Proceed with reload? [confirm]

System Bootstrap, Version 12.0(20000106:234457) [tombnyg-rommon_1_6 106],
SOFTWARE REV 1.6
Copyright (c) 1994-2000 by cisco Systems, Inc.
AS5400 platform with 131072 Kbytes of main memory


Self decompressing the image : #################################################
##################################################### [OK]
Self decompressing the image : #################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################### [OK]
Press RETURN to get started!

Note Most sections of the boot sequence have been omitted from the example.

Tips On system reload, if the console session freezes or displays unusual characters on the screen, you may have a console session mismatch between the Cisco IOS console line speed and the terminal server speed. This mismatch may occur because of the program settings of your console or your terminal server speed.

Upgrading the Cisco AS5800 Universal Access Server

Backing Up Your AS5800 Configuration

Cisco recommends backing up all existing IOS images and configurations from privileged exec mode.

Note Backup current IOS images (boot, router-shelf, dial-shelf), and configurations, to a TFTP server prior to upgrading. By default, files are copied to and from the Cisco TFTP root directory.

Step 1 Backup your existing startup configuration. Use a distinct file name for the startup configuration. This makes it easy to distinguish from other startup configurations previously saved on your TFTP Server.

AS5800# copy startup-config tftp
Address or name of remote host []? 171.71.219.167
Destination filename [startup-config]? AS5800-startup
!!
3449 bytes copied in 0.136 secs

Step 2 Backup your existing running configuration. Use a distinct file name for the running configuration. This makes it easy to distinguish from other running configurations previously saved on your TFTP Server.

AS5800# copy running-config tftp
Address or name of remote host []? 171.71.219.167
Destination filename [running-config]? AS5800-running-config
!!
3312 bytes copied in 0.140 secs

Step 3 Save your running-configuration to your startup configuration in NVRAM.

Router# copy running-configuration start-up configuration

Note Do not modify your running configuration during the IOS upgrade process.

Step 4 Determine the current boot image.

AS5800# sh bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AC05EDDF 37A6B8 22 3384888 Dec 31 1999 18:08:09 c7200-boot-mz.120-4.XE

Step 5 Backup the boot image (c7200-boot-mz.XXX) from bootflash to the TFTP server. Use the file name obtained in Step 4.

AS5800# copy bootflash: tftp
Source filename [c]? c7200-boot-mz.120-4.XE
Address or name of remote host []? 171.71.219.167
Destination filename [c7200-boot-mz.120-4.XE]?
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
3384888 bytes copied in 89.920 secs (38032 bytes/sec)

Step 6 Determine the router shelf's current flash image.

AS5800# sh flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AAD4004B 719C50 25 7314384 May 02 2000 13:55:04 c5800-p4-mz_120-4_XL1.bin

Step 7 Backup the current router shelf IOS image (C5800-p4-mz.XXX) stored in Flash memory. Use the file name obtained in Step 6.

AS5800# copy flash tftp
Source filename []? c5800-p4-mz_120-4_XL1.bin
Address or name of remote host []? 171.71.219.167
Destination filename [c5800-p4-mz_120-4_XL1.bin]?
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
7314384 bytes copied in 218.684 secs (33552 bytes/sec)

Step 8 On your TFTP Server, verify that files were copied (backed up).

Note By default, files are copied to and from the Cisco TFTP root directory.

Installing New IOS Software on the Cisco AS5800

An AS5800 Cisco IOS upgrade requires a compatible Cisco IOS image upgrade on both the Dial Shelf Controller (DSC) cards and Router Shelf (RS) components of the system. Two distinct upgrade procedures are necessary, one for each component.

Note Cisco recommends upgrading the dial-shelf controller(s) first, since all upgrades are performed through the router shelf. Once DSC(s) are upgraded, the router shelf will not be able to communicate with the DSC(s) until a compatible IOS image is installed on the RS.

Note Do not modify your running configuration during the IOS upgrade process.

Note Upgrade verifications are performed after all necessary upgrades are complete, and all system components are reloaded.

Upgrading the DSC Software

The following procedure outlines commands used to perform a Cisco 5814 Dial Shelf Controller (DSC) software upgrade from the Router Shelf.

Step 1 Login to the AS5800 Router Shelf and enter Enable (privileged exec) mode.

Step 2 Identify IOS images in the DSC bootflash.

AS5800# execute-on slot 12 sh bootflash:
DA-Slot12#
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image BC8CA85F 251C60 26 2169824 Nov 18 1999 22:12:15 dsc-c5800-mz.120-4.XL1.bin

Step 3 Delete the current IOS image(s) from bootflash.

AS5800# execute-on slot 12 del bootflash:dsc-c5800-mz.120-4.XL1.bin
DA-Slot12#
Delete filename [dsc-c5800-mz.120-4.XL1.bin]?
Delete bootflash:dsc-c5800-mz.120-4.XL1.bin? [confirm]
AS5800#

Step 4 Squeeze the DSC bootflash.

AS5800# execute-on slot 12 squeeze bootflash

DA-Slot12#
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete

Step 5 Identify IOS images in the DSC flash.

AS5800# execute-on slot 12 sh flash

DA-Slot12#
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image BC8CA85F 231C60 26 2169824 Sep 16 1999 18:10:32 dsc-c5800-mz.120-4.XL1.bin
2 .D image 8FDE1F61 45FEC8 18 2286056 Jan 25 2000 18:28:57 dsc-c5800-mz.Jan21

Step 6 Delete images or files no longer required.

AS5800# execute-on slot 12 delete flash:dsc-c5800-mz.120-4.XL1.bin
DA-Slot12#
Delete filename [dsc-c5800-mz.120-4.XL1.bin]?
Delete slot0:dsc-c5800-mz.120-4.XL1.bin? [confirm]
AS5800#

Step 7 Squeeze the DSC flash to remove deleted files.

AS5800# execute-on slot 12 squeeze flash:
DA-Slot12#
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Writing sector: 1
Squeeze of slot0 complete

Step 8 Download the new DSC image from your TFTP server to the DSC flash.

Note By default, files are copied to and from the Cisco TFTP root directory.

AS5800# copy tftp:dsc-c5800-mz.120-7.T.bin dsc12-slot0
Address or name of remote host [171.71.219.167]?
Source filename [dsc-c5800-mz.120-7.T.bin ]?
Destination filename [dsc12-slot0]?
Accessing tftp://171.71.219.167/dsc-c5800-mz.120-7.T.bin ...
%Warning: File not a valid executable for this system
Abort Copy? [confirm]n
Loading dsc-c5800-mz.120-7.T.bin from 171.71.219.167 (via FastEthernet0/0/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The following Warning message appears.

%Warning: File not a valid executable for this system
Abort Copy? [confirm]

Note Do not abort the copy process. This message implies that the file being downloaded is not router shelf compatible, which is true. However, the router assumes the file being downloaded will be executed on the router shelf, when, in fact, the file is a dial shelf controller file, being downloaded to the dial shelf through the router, that will ultimately be executed on the dial shelf.

Step 9 Enter "n" to proceed with the download.

Step 10 Copy the new DSC image to the DSC bootflash:

AS5800# execute-on slot 12 copy slot0:dsc-c5800-mz.120-7.T.bin
bootflash:
DA-Slot12#
Destination filename [dsc-c5800-mz.120-7.T.bin ]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
2169824 bytes copied in 24.464 secs (90409 bytes/sec)

Step 11 Reload the DSC to load the new image.

Router# execute-on slot 12 reload

Step 12 Repeat this procedure if you have a second DSC card to ensure both cards are running the same software release. The only change to the commands will be the slot number ("13" instead of "12").

Note At this juncture, the DSC(s) and Router Shelf are not running the same IOS image, so you will not be able to communicate with the DSC through the Router Shelf.

Upgrading the Router Shelf Software

The following procedure outlines commands used to perform a Cisco 7206 router shelf (RS) software upgrade from the Router Shelf.

Note Unless you installed new port adapters in the router shelf, do not upgrade the boot image. See Upgrading the Router Shelf Boot Image.

Step 1 Identify IOS images in the RS flash.

AS5800# sh flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AAD4004B 719C50 25 7314384 May 02 2000 13:55:04 c5800-p4-mz_120-4_XL1.bin
9069488 bytes available (7314512 bytes used)

Step 2 Delete images or files no longer required.

AS5800# delete slot0:c5800-p4-mz_120-4_XL1.bin
Delete filename [c5800-p4-mz_120-4_XL1.bin]?
Delete slot0:c5800-p4-mz_120-4_XL1.bin? [confirm]

Step 3 Squeeze the flash to remove all deleted files.

AS5800# squeeze slot0:
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of slot0 complete

Step 4 Download the new image from a TFTP server to the RS flash.

Note By default, files are copied to and from the Cisco TFTP root directory.

AS5800# copy tftp:c5800-p4-mz.120-7.T.bin slot0:
Address or name of remote host [171.71.219.167]?
Source filename [c5800-p4-mz.120-7.T.bin ]?
Destination filename [c5800-p4-mz.120-7.T.bin ]?
Accessing tftp://171.71.219.167/c5800-p4-mz.120-7.T.bin ...
Loading c5800-p4-mz.120-7.T.bin from 171.71.219.167 (via FastEthernet0/0/0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Step 5 Upgrade the bootflash, if applicable. See "Upgrading the Router Shelf Boot Image".

Note Unless you are installing new port adapters in the router shelf, do not upgrade the boot image. See "Upgrading the Router Shelf Boot Image".

Step 6 Reload the router shelf to load the new image.

Router# reload

Upgrading the Router Shelf Boot Image

The following procedure outlines commands used to perform a Cisco 7206 router shelf (RS) boot image software upgrade from the router shelf.

Note Unless you installed new port adapters in the router shelf, do not upgrade the boot image.

Step 1 Identify the current bootflash image.

AS5800# sh bootflash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AC05EDDF 37A6B8 22 3384888 Dec 31 1999 18:08:09 c7200-boot-mz.120-4.XE

1 bytes available (3407872 bytes used)

Step 2 Delete the current boot image from bootflash.

AS5800# del bootflash:
Delete filename []? c7200-boot-mz.120-4.XE
Delete bootflash:c7200-boot-mz.120-4.XE? [confirm]

Step 3 Squeeze the bootflash to remove all deleted files.

AS5800# squeeze bootflash:
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]

Squeeze of bootflash complete

Step 4 Copy the boot image from the TFTP server (c7200-boot-mz.XXX) to bootflash.

AS5800# copy tftp bootflash:
Address or name of remote host []? 171.71.219.167
Source filename []? c7200-boot-mz.120-7.T.bin
Destination filename [c7200-boot-mz.120-7.T.bin]?
Accessing tftp://171.71.219.167/c7200-boot-mz.120-7.T.bin...
Loading c7200-boot-mz.120-7.T.bin from 171.71.219.167 (via FastEthernet0/0/0):!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 3384888/6769664 bytes]

3384888 bytes copied in 65.112 secs (52075 bytes/sec)

Software Upgrade Verification

Perform the following steps to verify the Router Shelf and DSC(s) are running new IOS images, and the Bootflash is running a new boot image.

Step 1 Check the Dial Shelf Controller(s) for a new IOS image.

AS5800# execute-on slot 12 show version

DA-Slot12>
Cisco Internetwork Operating System Software
IOS (tm) 5800 Software (C5800-DSC-M), Version 12.0(7)T
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 12-Aug-99 18:48 by ayeh
Image text-base: 0x600088F0, data-base: 0x60520000

ROM: System Bootstrap, Version 11.3(1)AA, ROM: 5800 Software (C5800-DSC-M),Version 12.0(7)T

DA-Slot12 uptime is 41 minutes
System returned to ROM by reload
System image file is "slot0:dsc-c5800-mz.120-7.T.bin "

Router# execute-on slot 13 show version (IF APPLICABLE)

Step 2 Check the Router Shelf for a new IOS image.

AS5800# sh version
Cisco Internetwork Operating System Software
IOS (tm) 5800 Software (C5800-P4-M), Version 12.0(7)T, TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 12-Aug-99 13:16 by ayeh
Image text-base: 0x60008900, data-base: 0x611A6000

ROM: System Bootstrap, Version 12.0(19990210:195103) [12.7T 105], DEVELOPMENT SOFTWARE BOOTFLASH: 7200 Software (C7200-BOOT-M), Version 12.0(7)T

doc-rtr58-01 uptime is 9 minutes
System returned to ROM by reload at 16:04:24 CST Fri Jun 9 2000
System restarted at 16:05:39 CST Fri Jun 9 2000
System image file is "slot0:c5800-p4-mz.120-7.T.bin"

Step 3 Check the Bootflash for a new boot image.

AS5800#sh bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image AC05EDDF 37A6B8 22 3384888 Jun 12 200014:00:23 c7200-boot-mz.120-7.T.bin

22856 bytes available (3385016 bytes used)

Upgrading the Cisco AS5850 Universal Gateway

Verify that you are upgrading from a Cisco IOS release that supports high availability (Cisco IOS Release 12.2(2)XB or higher), then perform one of the following procedures:

• Upgrading from a High-Availability Image

• Upgrading from a Nonhigh-Availability Image

Note If, for some reason, you later wish to downgrade to a nonhigh-availability release, configure your system to classic-split mode, then reset each RSC.

Upgrading from a High-Availability Image

Tip•To minimize downtime, perform the following upgrade in handover-split mode. Just half the system is down at a time, for as little as one minute per RSC, compared to a total system downtime of over nine minutes in classic-split mode.

•Before any system handover, to gracefully disable associated modems and thus minimize dropped calls, enter the modem busyout or modem busyout-threshold (sometimes called autobusyout) command. After handover, to reenable the modems, enter the no form of the command.

Step 1 From RSC 1, do the following:

a. Disable RSC 1 modems by entering the modem busyout or modem busyout-threshold command.

b. Force handover of all RSC 1 slots to RSC 0 by entering the redundancy handover shelf-resources command. Wait for RSC 1 to reload automatically.

Step 2 From RSC 0, transfer back to RSC 1 the slots that should belong to it by entering the redundancy handover peer-resources command.

Step 3 From RSC 1, reenable the disabled modems by entering the no form of the modem-busyout command used above.

Step 4 From RSC 0, do the following:

a. Disable RSC 0 modems by entering the modem busyout or modem busyout-threshold command.

b. Force handover of all RSC 0 slots to RSC 1 by entering the redundancy handover shelf-resources command. Wait for RSC 0 to reload automatically.

Step 5 From RSC 1, transfer back to RSC 0 the slots that should belong to it by entering the redundancy handover peer-resources command.

Step 6 From RSC 0, reenable the disabled modems by entering the no form of the modem-busyout command used above.

Upgrading from a Nonhigh-Availability Image

Caution You must upgrade both RSCs at the same time. Operating with a mix of high-availability and nonhigh-availability images, even in classic-split mode, may result in erratic system behavior.

Tips Before any system handover, to gracefully disable associated modems and thus minimize dropped calls, enter the modem busyout or modem busyout-threshold (sometimes called autobusyout) command. After handover, to reenable the modems, enter the no form of the command.

Step 1 Disable all system modems by entering the modem busyout or modem busyout-threshold command.

Step 2 Do the following in rapid succession (do not wait for the first RSC to reboot before proceeding):

a. From RSC 0, reload by entering the reload command.

b. From RSC 1, reload by entering the reload command.

Wait for both reloads to complete.

Step 3 Reenable the modems as follows:

a. From RSC 0, reenable the disabled modems by entering the no form of the modem-busyout command used above.

b. From RSC 1, reenable the disabled modems by entering the no form of the modem-busyout command used above.

hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Feb 15 19:26:30 PST 2008
All contents are Copyright © 1992--2008 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.