Launch your web browser and access the Cisco Software Download page:

Choose Application Networking Services > Wide Area Application Services > Cisco Wide Area Application Services (WAAS) Software download area.

Choose the Cisco WAAS software version that you want and download the appropriate software image.

Register the location of the software file in the WAAS Central Manager GUI, as described in Specifying the Location of the Software File in the Cisco WAAS Central Manager GUI.

From the Cisco WAAS Central Manager menu, choose Admin > Version Management > Software Update.

Click the Create New Software File icon in the taskbar.

The Creating New Software File window appears.

In the Software File URL field, specify the location of the new WAAS software file as follows:

1. From the Software File URL drop-down list, choose a protocol (HTTP or FTP).

2. Enter the URL for the .bin software file that you downloaded from Cisco.com. For example, a valid URL might look like the following:

   http://internal.mysite.com/waas/WAAS-xxxx-K9.bin

   http://2012:3:3:3::8/waas/WAAS-xxxx-K9.bin

   Here, WAAS- xxxx -K9.bin is the name of the software upgrade file. (The filename typically includes the version number.)

   Be sure that the URL identifies the correct type of software image for the devices you want to upgrade, either Universal or Accelerator only.

   If the Central Manager has been configured with an IPV6 address, it can be accessed using https://[CM ipv6 address]:8443/

   Software update configuration with IPv6 address will be filtered in the device /device group level usage pages for unsupported device models and versions.

(Optional) If your server requires user login authentication, enter your username in the Username field and enter your login password in the Password field. Enter the same password in the Confirm Password field.

To automatically reload a device when you upgrade the software, at the Advanced Settings pane, check the Auto Reload check box. If you do not check this check box, you should manually reload a device after you upgrade the software on it to complete the upgrade process.

(Optional) Enter comments in the Comments field.

Click Submit.

To reload a device from the CLI, run the reload EXEC command.

From the Cisco WAAS Central Manager menu, choose Devices > device-name.

Verify that the device is not already running the version to which you plan to upgrade.

Click Update.

To choose the software file URL from the Software Files list, click the radio button next to the corresponding filename.

To confirm you decision, click Submit and then click OK.

Clear your browser cache, close the browser, and restart the browser session to the WAAS Central Manager.

From the Cisco WAAS Central Manager menu, choose Device Groups > device-group-name.

Choose Admin > Versioning > Software Update.

To choose the software file URL from the Software File URL list, click the radio button next to the filename. If no images are available, create a software file, as described in Specifying the Location of the Software File in the Cisco WAAS Central Manager GUI.

Click Submit.

Add a hardware device as the new Cisco WAAS Central Manager and configure it as a Standby Cisco WAAS Central Manager. There may be multiple Standby Cisco WAAS Central Managers in the system. For more information, see Configuring the Cisco WAAS Central Manager Role.

Enable the new hardware device to be the primary Cisco WAAS Central Manager after it is available online and has finished synchronizing with other systems. For more information, see Converting a Standby Cisco WAAS Central Manager to a Primary Cisco WAAS Central Manager.

To remove the former Cisco WAAS Central Manager from the Cisco WAAS Central Manager database:

After the former Cisco WAAS Central Manager has been deregistered, perform the following tasks:

After the device has been reloaded, perform the following tasks:

From the Cisco WAAS Central Manager menu, choose Admin > Version Management > Software Update.

Click the Edit icon next to the software file that you want to delete.

Click the Trash icon in the taskbar.

Click OK.

To back up the CMS database to a file, on the Cisco WAAS Central Manager GUI, run the cms database backup global configuration command, as shown in the following example:

CM# cms database backup
Creating database backup file backup/cms-db-11-05-2010-15-22_4.3.1.0.1.dump
Backup file backup/cms-db-11-05-2010-15-22_4.3.1.0.1 is ready.
Please use 'copy' commands to move the backup file to a remote host.

Save the file to a remote server by using the copy disk ftp command. This command copies the file from a local disk to a remote FTP server.

Restore the CMS database as follows:

1. Disable the CMS service:

   CM# configure
   CM(config)# no cms enable
   CM(config)# exit

   Note	Stopping the CMS service disables the Cisco WAAS Central Manager GUI. All the users who are currently logged in to this GUI are automatically logged out after the CMS service is disabled.

2. To delete the existing CMS database, run the cms database delete EXEC command.

3. To initialize the CMS database, run the cms database create EXEC command.

4. Restore the CMS database contents from the backup file:

   CM# cms database restore backup/cms-db-7-22-2008-17-36_4.1.3.0.1.dump

   Note

   After the restore, any WAEs that were registered with the Cisco WAAS Central Manager during the time since the backup was created will be disconnected from the Cisco WAAS Central Manager because there is no information about them in the backup file. To bring these WAEs online, you must deregister and reregister them with the Cisco WAAS Central Manager. On each WAE that was disconnected, use the following commands:

   WAE# cms deregister force
   WAE# configure
   WAE(config)# cms enable

5. To enable the CMS service on the Cisco WAAS Central Manager, run the cms enable global configuration command.

(Optional) If you want to upgrade the Cisco WAAS Central Manager to a newer model, backing up the former Cisco WAAS Central Manager’s database and restoring it on the new device prevents it from being used as a WAE later. For more information, see Upgrading Cisco WAAS Central Manager to New Hardware and Converting an Existing Cisco WAAS Central Manager to a Cisco WAE.

Download the system image file (*.sysimg) to a host that is running an FTP server.

Establish a console connection to the Cisco WAAS device and open a terminal session.

To reboot the device, toggle the power on/off switch.

To boot the rescue image, enter r.

If you see the following output (from a device that was initially manufactured with Cisco WAAS Version 5.x), log in and run the copy install EXEC command to install the Cisco WAAS system software image (.bin file), as shown in the following example (user input is denoted by entries in bold typeface):

The device is running WAAS rescue image. WAAS functionality is unavailable
in a rescue image. If the rescue image was loaded by accident, please reload
the device. If the rescue image was loaded intentionally to reinstall WAAS software
please use the following command:
copy [ftp|http|usb] install ...
SW up-to-date
...
Cisco Wide Area Virtualization Engine Console
Username: admin
Password:
System Initialization Finished.
WAVE# copy ftp install 172.16.10.10 / waas-universal-5.1.1.12-k9.bin
...
Installing system image to flash... Creating backup of database content before database
upgrade.
The new software will run after you reload.
WAVE# reload
Proceed with reload?[confirm]yes
Shutting down all services, will timeout in 15 minutes.
reload in progress ..Restarting system.

If you see the following output (from a device that was initially manufactured with Cisco WAAS Version 4.x), log in and install the Cisco WAAS system image (.sysimg file), as shown in the following example (user input is denoted by entries in bold typeface):

This is the rescue image. The purpose of this software is to let
you download and install a new system image onto your system's
boot flash device. This software has been invoked either manually
(if you entered `***' to the bootloader prompt) or has been
invoked by the bootloader if it discovered that your system image
in flash had been corrupted.
To download an image, this software will request the following
information from you:
- which network interface to use
- IP address and netmask for the selected interface
- default gateway IP address
- server IP address
- which protocol to use to connect to server
- username/password (if applicable)
- path to system image on server
Please enter an interface from the following list:
0: GigabitEthernet 0/0
1: GigabitEthernet 0/1
enter choice: 0
Using interface GigabitEthernet 0/0
Please enter the local IP address to use for this interface:
[Enter IP Address]: 172.16.22.22
Please enter the netmask for this interface:
[Enter Netmask]: 255.255.255.224
Please enter the IP address for the default gateway:
[Enter Gateway IP Address]: 172.16.22.1
Please enter the IP address for the FTP server where you wish
to obtain the new system image:
[Enter Server IP Address]: 172.16.10.10
Please enter your username on the FTP server (or 'anonymous'):
[Enter Username on server (e.g. anonymous)]: anonymous
Please enter the password for username 'anonymous' on FTP server:
Please enter the directory containing the image file on the FTP server:
[Enter Directory on server (e.g. /)]: /
Please enter the file name of the system image file on the FTP server:
[Enter Filename on server (e.g. WAAS-x86_64-4.x.x-K9.sysimg)]:
waas-x86_64-5.1.1.12-k9.sysimg
Here is the configuration you have entered:
Current config:
IP Address: 172.16.22.22
Netmask: 255.255.255.224
Gateway Address: 172.16.22.1
Server Address: 172.16.10.10
Username: anonymous
Password:
Image directory: /
Image filename: waas-x86_64-5.1.1.12-k9.sysimg
Attempting download...
Downloaded 31899648 byte image file
A new system image has been downloaded.
You should write it to flash at this time.
Please enter 'yes' below to indicate that this is what you want to do:
[Enter confirmation ('yes' or 'no')]: yes
Ok, writing new image to flash
Finished writing image to flash.
Enter 'reboot' to reboot, or 'again' to download and install a new image:
[Enter reboot confirmation ('reboot' or 'again')]: reboot
Restarting system.
Booting system, please wait.........

Log in to the device with the username admin. To verify that you are running the correct version, run the show version EXEC command:

Username: admin
Password:
Console# show version
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2020 by Cisco Systems, Inc.
Cisco Wide Area Application Services (universal-k9) Software Release 6.4.3 (build b49 Jan 14 2020)
Version: oe294-5.1.1.12
Compiled 12:23:45 Jan 14 2020 by dsmith
Device Id: 50:3d:e5:9c:8f:a5
System was restarted on Tue Jan 14 16:35:50 2020.
System restart reason: called via cli.
The system has been up for 8 hours, 10 minutes, 19 seconds.

Establish a console connection to the device and open a terminal session.

Reboot the device.

Cisco WAAS boot:hit RETURN to set boot flags:0009

When prompted to enter bootflags, enter the value 0x8000.

Available boot flags (enter the sum of the desired flags):
0x4000 - bypass nvram config
0x8000 - disable login security
[CE boot - enter bootflags]:0x8000
You have entered boot flags = 0x8000
Boot with these flags? [yes]:yes
[Display output omitted]
Setting the configuration flags to 0x8000 lets you into the system, bypassing all
security. Setting the configuration flags field to 0x4000 lets you bypass the NVRAM
configuration.

When the device completes the boot sequence, you are prompted to enter the username to access the CLI. Enter the default administrator username (admin).

Cisco WAE Console
Username: admin

When you see the CLI prompt, set the password for the user using the username passwd command in global configuration mode:

WAE# configure
WAE(config)# username admin passwd

Save the configuration change:

WAE(config)# exit
WAE# write memory

(Optional) Reboot your device:

WAE# reload

Deactivate the device by completing the following steps:

1. From the Cisco WAAS Central Manager menu, choose Devices > device-name.

2. Choose device-name > Activation.

   The Device Activation window appears.

3. Uncheck the Activate check box, and then click Submit.

   The device is deactivated.

Power down the device and replace the failed hard drive.

Power on the device.

Use the CMS identity recovery procedure to recover the device CMS identity and associate this device with the existing device record on the Cisco WAAS Central Manager. For more information, see Recovering Cisco WAAS Device Registration Information.

To mark the failed device as Inactive and Replaceable by completing the following steps:

1. From the Cisco WAAS Central Manager menu, choose Devices > device-name.

2. Choose device-name > Activation.

3. Uncheck the Activate check box. The window refreshes, displaying a check box for marking the device as replaceable.

4. Check the Replaceable check box, and click Submit.

   Note	This check box appears in the Cisco WAAS Central Manager GUI only when the device is inactive.

If the failed device is configured as a nonoptimizing peer with another device, disable the peer settings on the other device.

1. From the Cisco WAAS Central Manager menu, choose Configure > Global > Peer Settings.

   The Peer Settings window for all the devices appears.

2. Click the Edit icon next to the nonoptimizing device identified in the message, which will appear in red because its peer is unknown.

   The Peer Settings window for that device appears.

3. Click the Remove Device Settings icon in the taskbar.

4. Click Submit.

Configure a system device recovery key as follows:

1. From the Cisco WAAS Central Manager menu, choose Configure > Global > System Properties.

2. Click the Edit icon next to the System.device.recovery.key property.

   The Modifying Config Property window appears.

3. Enter the password in the Value field, and click Submit.

   The default password is default.

Configure the basic network settings for the new device.

Open a Telnet session to the device CLI and enter the cms recover identity keyword EXEC command. Here, keyword is the device recovery key that you configured in the Cisco WAAS Central Manager GUI.

To enable the CMS service on the device, run the following commands:

WAE# config
WAE(config)# cms enable
WAE(config)# exit

Activate the device:

1. From the Cisco WAAS Central Manager menu, choose Devices > device-name.

2. Choose Device Name > Activation. The Cisco WAAS device status should be Online.

3. Check the Activate check box, and click Submit.

(Optional) Reconfigure the device peer settings, if the device was configured as a nonoptimizing peer with another device. For more information, see the chapter "Configuring Traffic Interception."

Save the device configuration settings by entering the copy running-config startup-config EXEC command.

Manually shut down the disk.

1. Enter global configuration mode and then enter the disk disk-name diskxx shutdown global configuration command:

   WAE# configure
   WAE(config)# disk disk-name diskxx shutdown

2. Wait for the disk to be completely shut down before you physically remove the disk from the WAE. When the RAID removal process is complete, Cisco WAAS generates a disk failure alarm and trap. In addition, a syslog error message is logged.

   Note	We recommend that you disable the disk error-handling reload option if it is enabled because it is not necessary to power down the system to remove a disk.

Insert a replacement disk into the slot in the WAE. The replacement disk must have a disk ID number that is different from the disk that it is replacing.

To re-enable the disk, run the no disk disk-name diskxx shutdown global configuration command.

Enter the disk disk-name diskxx replace command in EXEC mode from the Cisco WAAS CLI on the Cisco WAE.

Verify that the disk drive diskxx is in Defunct state by entering the show disks details command in EXEC mode. The RAID logical drive is in Critical state at this point.

Move the handle on the drive to the open position (perpendicular to the drive).

Pull the hot-swap drive assembly from the bay.

Wait for one minute and then insert the new drive into the same slot by aligning the replacement drive assembly with guide rails in the bay and sliding the drive assembly into the bay until it stops. Make sure that the drive is properly seated in the bay.

Close the drive handle.

Check the hard disk drive status LED to verify that the hard disk drive is operating correctly. If the amber hard disk drive status LED for a drive is lit continuously, that drive is faulty and must be replaced. If the green hard disk drive activity LED is flashing, it means the drive is being accessed.

Wait for 1 minute. To verify that the replaced disk drive is in the Rebuilding state, run the show disk details command in EXEC mode.

Wait until the rebuild operation is complete. To check if the rebuild operation is complete, run the show disk details command in EXEC mode. The physical drive state will be Online and the RAID logical drive state will be Okay after the rebuild operation is completed.

Reinstall the software on the device. For more information, see Upgrading the Cisco WAAS Central Manager

Add the license. For more information, see Managing Cisco WAAS Software Licenses in the chapter "Configuring Other System Settings."

Register the Cisco WAE to the Cisco WAAS Central Manager.

From the global configuration mode, run the disk logical shutdown command to disable the RAID-5 array.

To save the running configuration to NV-RAM, run the write command in EXEC mode.

To reload the system, run the reload command in EXEC mode.

To check the system configuration after the system is reloaded, run the show disks details command in EXEC mode. At this point, the disks are not mounted and the logical RAID drive should be in the Shutdown state.

To recreate the RAID-5 array, run the disk recreate-raid command in EXEC mode.

To disable the logical disk shutdown configuration: After successful execution of the disk recreate-raid command, enter global configuration mode and run the no disk logical shutdown command.

To save the configuration to NV-RAM, run the write command in EXEC mode.

To reload the system, run the reload command in EXEC mode.

To check the system configuration after the system is reloaded, run the show disks details command in EXEC mode.

Wait until the rebuild operation is complete. To check if the rebuild operation is complete, run the show disks details command in EXEC mode. The physical drive state will be Online and the RAID logical drive state will be Okay after the rebuild operation is completed.

After a multiple disk failure or RAID controller failure, and after the drives are replaced and the RAID disk is rebuilt, the logical disk may remain in the error state. To re-enable the disk, run the no disk logical shutdown force command, and then reload the WAE.

To deregister the Cisco WAE from the Cisco WAAS Central Manager, run the cms deregister force EXEC command.

To configure the device mode as central-manager, run the device mode central-manager global configuration command:

WAE# configure
WAE(config)# device mode central-manager

You must reload the device to apply the changes. For more information, see see Rebooting a Device.

To configure the Cisco WAAS Central Manager role as Standby, run the central-manager role standby command.

To configure the address of the Primary Cisco WAAS Central Manager, run the central-manager address cm-primary-address command:

To enable the CMS service, run the cms enable command.

To deregister the Cisco WAAS Central Manager, run the cms deregister EXEC command:

To configure the Cisco WAAS Central Manager role as Standby, run the central-manager role standby global configuration command.

To configure the address of the Primary Central Manager, run the central-manager address cm-primary-address global configuration command.

To enable the CMS service, run the cms enable global configuration command.

Ensure that your Cisco WAAS Central Manager devices are running the same version of Cisco WAAS software.

Synchronize the physical clocks on both devices so that both the Cisco WAAS Central Managers have the same Coordinated Universal Time (UTC) configured.

To ensure that the Standby is synchronized with the Primary, check the status of the following items:

1. Check the online status of your devices.

   The original Standby Cisco WAAS Central Manager and all currently active devices should be showing as online in the Cisco WAAS Central Manager GUI. This step ensures that all other devices know about both Cisco WAAS Central Managers.

2. Check the status of recent updates from the Primary WAAS Central Manager.

   To check the time of the last update, run the show cms info EXEC command. To be current, the value of the Time of last config-sync field should be between 1 and 5 minutes old. This time range verifies that the Standby Cisco WAAS Central Manager has fully replicated the Primary Cisco WAAS Central Manager configuration.

   If the update time is not current, determine whether or not there is a connectivity problem or if the Primary Cisco WAAS Central Manager is down. Fix the problem, if necessary, and wait until the configuration has replicated, as indicated by the time of the last update.

Switch roles in the following order:

1. Disable the original Primary Cisco WAAS Central Manager.

   WAE2(config)# no cms enable

2. Switch the original Standby Cisco WAAS Central Manager to primary mode:

   WAE2# configure
   WAE2(config)# central-manager role primary
   
   WAE1-CM3(config)# central-manager role standby
   Switching CM to standby will cause all configuration settings made on this CM to be
   lost.
   Please confirm you want to continue (yes|no) [no]?yes
   Restarting CMS services

3. Wait until the original Standby Cisco WAAS Central Manager is completely up and that you have verified that it is now working as the Primary Cisco WAAS Central Manager.

4. Switch the original primary Cisco WAAS Central Manager to standby mode:

   WAE1# configure
   WAE1(config)# central-manager role standby
   WAE1(config)# cms enable

Convert a Standby Cisco WAAS Central Manager to be the Primary Cisco WAAS Central Manager, as described in Converting a Standby Cisco WAAS Central Manager to a Primary Cisco WAAS Central Manager.

When the failed Cisco WAAS Central Manager becomes available again, configure it as a Standby Central Manager, as described in Converting a Primary Cisco WAAS Central Manager to a Standby Cisco WAAS Central Manager, beginning with Step 2. Skip Step 1 and do not use the cms deregister EXEC command.

Switch both the Cisco WAAS Central Manager roles, as described in Switching Both the Cisco WAAS Central Manager Roles.

From the Cisco WAAS Central Manager menu, choose Devices > device-name.

In the Device Info pane, click the Reload icon.

To confirm that you want to reboot the device, click OK.

To reboot a device from the CLI, run the reload EXEC command.

From the Cisco WAAS Central Manager menu, choose Device Groups > device-group-name.

In the taskbar, click the Reboot All Devices in Device Group icon.

To confirm that you want to reboot the device group, click OK.