Cisco Wide Area Application Services Configuration Guide (Software Version 6.2.3)

Determining the Current Software Version

To view the current software version running on a particular device, choose Devices > All Devices. The All Devices window displays the software version for each listed device.

You can also click Devices > device-name or the Edit icon next to the name of a device in the Devices window. The Device Dashboard window appears, listing the software version for that device.

Note The software version is not upgraded until a software upgrade is successfully completed. If a software upgrade is in progress, the version number displayed is the base version, not the upgraded version number.

Alternatively, in the device context, choose Monitor > CLI Commands > Show Commands. Choose version and click Submit. A secondary window is displayed with the CLI output for the show version command.

Obtaining the Latest Software Version from Cisco.com

To obtain the latest WAAS software version from Cisco.com, follow these steps:

Step 1 Launch your web browser and access the cisco.com website:

http://www.cisco.com/cisco/software/navigator.html

Step 2 Navigate to the Application Networking Services > Wide Area Application Services > Cisco Wide Area Application Services (WAAS) Software download area.

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

Step 4 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 WAAS Central Manager GUI.

Specifying the Location of the Software File in the WAAS Central Manager GUI

To upgrade your WAAS software, you must first specify the location of the WAAS software file in the WAAS Central Manager GUI and configure the software file settings.

There are two types of WAAS software files:

• Universal—Includes Central Manager, Application Accelerator, and AppNav Controller functionality. You can use this type of software file to upgrade a device operating in any mode.
• Accelerator only—Includes Application Accelerator and AppNav Controller functionality only. You can use this type of software file to upgrade only an Application Accelerator or AppNav Controller device. If you want to change an Application Accelerator or AppNav Controller to a Central Manager, you must install the Universal software file, reload the device, change the device mode to central-manager, and then reload the device again. Additionally, kdump analysis functionality is not included in the Accelerator only image.

To configure the software file settings form, follow these steps:

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

Step 2 Click the Create New Software File icon in the taskbar.

The Creating New Software File window appears. (See Figure 14-1.)

Figure 14-1 Creating New Software File Window

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

a. Choose a protocol (http or ftp) from the Software File URL drop-down list.

b. 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 / versions.

Step 4 (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.

The Software Version and Image Type fields cannot be edited. They are filled in automatically after you submit the settings and the image is validated.

Step 5 In the Advanced Settings section, check the Auto Reload check box to automatically reload a device when you upgrade the software. 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.

Step 6 (Optional) Enter comments in the Comments field.

Step 7 Click Submit.

The software image file is validated and the Software Version and Image Type fields are filled in with the appropriate information extracted from the image file.

Caution If your browser is configured to save the username and password for the WAAS Central Manager GUI, the browser will autopopulate the Username and Password fields in the Creating New Software File window. You must clear these fields before you click Submit.

---

The software file that you want to use is now registered with the WAAS Central Manager. When you perform the software upgrade or downgrade, the URL that you just registered becomes one of the choices available in the Update Software window.

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

Note When you are viewing the list of registered software files, if the Image Type column shows Unknown for a software file, it indicates that the software file was added under a WAAS version previous to 4.2.1. These Unknown software files must be resubmitted if you want to use them. Click the Edit icon next to the file to open the Modifying Software File window, and then click the Submit button to resubmit the file.

Upgrading the WAAS Central Manager

When upgrading software in your WAAS network, begin with WAAS Central Manager before upgrading the WAE devices.

Primary and standby WAAS Central Manager devices must be running the same version of WAAS software. If they are not, the standby WAAS Central Manager detects this and will not process any configuration updates it receives from the primary WAAS Central Manager. If the primary WAAS Central Manager sees that the standby WAAS Central Manager has a different version level, it shows the standby WAAS Central Manager in red on the device listing page.

If you use the primary WAAS Central Manager to perform the software upgrade, you need to upgrade your standby WAAS Central Manager first, and then upgrade your primary WAAS Central Manager. We also recommend that you create a database backup for the primary WAAS Central Manager and copy the database backup file to a safe place before you upgrade the software.

Use this upgrade procedure for WAAS Central Manager devices. You can also use this upgrade procedure to upgrade WAAS devices one at a time (after the WAAS Central Manager).

To upgrade your software to another WAAS software release on a single device, follow these steps:

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

The Device Dashboard window appears.

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

Step 3 Click the Update link.

The Software Update window appears.

Step 4 Choose the software file URL from the Software Files list by clicking the radio button next to the corresponding filename.

The list displays only software files with an image type of Universal, because you are upgrading a Central Manager device. If no such images are available, you must create a software file, as described in Specifying the Location of the Software File in the WAAS Central Manager GUI.

Step 5 Click Submit, and then click OK to confirm your decision.

The Devices Listing window is displayed again. You can monitor the progress of your upgrade from this window.

Software upgrade status messages are displayed in the Software Version column. These intermediate messages are also written to the system log on the WAAS devices. See Table 14-2 for a description of upgrade status messages.

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

The WAAS Central Manager may reboot at the conclusion of the upgrade procedure (if Auto Reload is in the Creating New Software File window), causing you to temporarily lose contact with the device and the GUI.

Upgrading Multiple Devices Using Device Groups

Note This procedure is for WAE devices only. WAAS Central Manager devices cannot be upgraded using device groups.

To upgrade to a more recent WAAS software release on multiple devices, follow these steps:

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

Step 2 Choose Admin > Versioning > Software Update.

The Software Update for Device Group window appears.

Step 3 Choose the software file URL from the Software File URL list by clicking 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 WAAS Central Manager GUI.

If you are updating many devices and you want to use a smaller size software file to save network bandwidth, specify a software file with an image type of Accelerator only, which is smaller than a Universal image. If you later want to change an Accelerator-only device to a Central Manager, you must install the Universal software file, reload the device, change the device mode to central-manager, and then reload the device again.

Step 4 Click Submit.

To view the progress of an upgrade, go to the All Devices window (Devices > All Devices) and view the software upgrade status message in the Software Version column. These intermediate messages are also written to the system log on WAAS devices. See Table 14-2 for a description of the upgrade status messages.

Upgrading Central Manager to New Hardware and Converting an Existing Central Manager to a WAE

If you want to add a new piece of hardware as a primary Central Manager and want to use the existing Central Manager as a WAE, it is important to first add it to the system and then configure it.

Note Performing a database backup of the former Central Manager and restoring it on the new device prevents it from being used as a WAE later.

To upgrade to a new Central Manager and convert an existing Central Manager to a WAE, follow these steps:

Step 1 Add a hardware device as the new Central Manager and configure it as a standby Central Manager. There might be multiple standby Central Managers in the system. For more information, see Configuring the Central Manager Role.

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

Step 3 Disable CMS service and execute the cms deregister command at the former Central Manager CLI interface to remove it from the CM database. If there is no connectivity between the devices anymore, use the cms deregister force command and manually delete the former Central Manager in the new Central Manager GUI.

Step 4 Rename the former Central Manager, change the IP address, change its mode using the device mode command, and reload using the reload command:

Step 5 Rename the new primary Central Manager and change its IP address to fully replace the former one. Otherwise, you will need to update the configuration of your devices to point to the new address of the Central Manager. Contact a Cisco TAC member for scripts.

wae(config-if)# ip address ipaddress netmask.

Deleting a Software File

After you have successfully upgraded your WAAS devices, you can remove the software file from your WAAS system.

Note You may want to wait a few days before removing a software file in the event that you may have to downgrade your system for any reason.

To delete a software file, follow these steps:

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

Step 2 Click the Edit icon next to the software file that you want to delete. The Modifying Software File window appears.

Step 3 Click the Trash icon in the taskbar.

You are prompted to confirm your decision to delete the software file.

Step 4 Click OK.

The selected software file is removed from the WAAS network.

Backing Up and Restoring the WAAS Central Manager Database

The WAAS Central Manager device stores WAAS network-wide device configuration information in its Centralized Management System (CMS) database. You can manually back up the CMS database contents for greater system reliability.

The CMS database backup is in a proprietary format that contains an archive database dump, WAAS Central Manager registration information, and device information that the WAAS Central Manager uses to communicate with other WAAS devices. CMS database backup files are not interchangeable between primary and standby WAAS Central Manager devices. This means that you cannot use the backup file from a primary WAAS Central Manager to restore a standby WAAS Central Manager.

To back up the CMS database for the WAAS Central Manager, use the cms database backup EXEC command. For database backups, specify the location, password, and user ID of the remote server that you want to store the backup file in. If you want to back up only the configuration information, use the cms database backup config EXEC command.

Note If you have already performed a backup when the secure store was in user-passphrase mode and you restored it to a system where the secure store is in auto-passphrase mode, you must enter the user passphrase to proceed with the restore. After the restore, the system is in user-passphrase mode. If you already performed a backup when the secure store was in auto-passphrase mode and you restored it to a system where the secure store is in user-passphrase mode, you do not have to enter a password. After the restore, the system is in auto-passphrase mode.

To back up and restore the CMS database, follow these steps:

Step 1 On the WAAS Central Manager GUI, use the cms database backup command to back up the CMS database to a file, as shown in the following example:

Note The backup file is automatically given a name in the format cms-db-date-timestamp_version.dump, for example, cms-db-7-22-2010-17-36_4.3.1.0.1.dump. Note that the timestamp is in a 24-hour format (HH:MM) that does not show seconds. It is stored in /local1/backup.

Step 2 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.

Step 3 Restore the CMS database as follows:

a. Disable the CMS service:

Note Stopping the CMS service disables the 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.

b. Delete the existing CMS database:

c. Initialize the CMS database:

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

Note After the restore, any WAEs that were registered with the Central Manager during the time since the backup was created will be disconnected from the 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 Central Manager. On each WAE that was disconnected, use the following commands:
WAE# cms deregister force
WAE# configure
WAE(config)# cms enable

e. Enable the CMS service on the Central Manager:

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

Backing Up and Restoring a WAE Device

You should back up the database of each WAAS device on a regular basis in case a system failure occurs.

Note The backup and restore methods described in this section apply only to a WAE device that is not configured as a WAAS Central Manager. For information on backing up the WAAS Central Manager device, see Backing Up and Restoring the WAAS Central Manager Database.

You can use either of the following methods to back up and restore the database of an individual WAE device:WAE Device Manager.

• CLI—Use the copy running-config command to back up and restore a device’s configuration. This command saves the currently running configuration.

Additionally, you can restore a WAE to the default configuration that it was manufactured with at any time by removing the user data from the disk and Flash memory, and erasing all the existing files cached on the appliance. Basic configuration information, such as network settings, can be preserved. The appliance is accessible through Telnet and Secure Shell (SSH) after it reboots.

Note If software upgrades have been applied, the restoration process returns to the defaults of the currently installed version and not the factory defaults.

To restore a WAE to its factory defaults or the defaults of the current configuration from the CLI, use the restore factory-default [ preserve basic-config ] EXEC command.

For more information about the CLI commands, see the Cisco Wide Area Application Services Command Reference Guide.

Reinstalling the System Software

This section contains instructions for using the software recovery files to reinstall your system software if for some reason the software that is installed has failed. A software recovery CD-ROM ships with some WAE and WAVE hardware devices. Some WAVE devices use a USB flash drive for recovery.

Caution If you upgraded your software after you received your software recovery CD-ROM or image files, using the recovery software images may downgrade your system. Ensure that you are using the desired software recovery version.

---

The WAAS software consists of three basic components:

• Disk-based software
• Flash-based software
• Hardware platform cookie (stored in flash memory)

All of these components must be correctly installed for WAAS software to work properly.

The software is contained in two types of software images provided by Cisco Systems:

• A.bin image that contains disk and flash memory components (the Universal version of the WAAS software)
• A.sysimg image that contains a flash memory component only

An installation that contains only the WAAS flash memory-based software, without the corresponding disk-based software, boots and operates in a limited mode, allowing for further disk configuration before completing a full installation.

The.sysimg component is provided for recovery purposes and allows for repair of flash memory only without modifying the disk contents.

Note The system image that is used depends on your device. For all WAVE devices (64-bit platforms), use the 64-bit system image (with “x86_64” in its name). For all other devices, use the 32-bit system image named without this designator.

A Network Processing Engine (NPE) image that has the disk encryption feature disabled for use in countries where disk encryption is not permitted, is provided.

If you have a WAVE appliance that requires a USB flash drive for software recovery, your USB flash drive must contain both of the needed software images in the form of an ISO archive file that you copy to the flash drive. (See Preparing the USB Flash Drive).

These options are available from the software recovery installer menu:

• Option 1: Configure Network—If the.bin image you need to install is located on the network instead of the CD-ROM or USB flash drive (which may be the case when an older CD-ROM or USB image is used to install new software), then you must choose this option to configure the network before attempting to install the.bin image.

This option is performed automatically if you install a.sysimg file from the network.

• Option 2: Manufacture Flash—This option verifies the flash memory and, if invalid, automatically reformats it to contain a Cisco standard layout. If reformatting is required, a new cookie is installed automatically.

This option is performed automatically as part of a.bin or.sysimg installation.

• Option 3: Install Flash Cookie—This option generates a hardware-specific platform cookie and installs it in flash memory. Use this option only if there has been a change in the hardware components, such as replacing the motherboard, or if you moved a flash memory card between systems.

This option is performed automatically during the flash manufacturing process, if needed, as part of a.bin or.sysimg installation.

• Option 4: Install Flash Image from Network and Option 5: Install Flash Image from
  USB/CD-ROM —These options allow installation of only the flash memory.sysimg and do not modify disk contents. They can be used when a new chassis has been provided and populated with a customer’s old disks that need to be preserved.

These options automatically perform flash verification and hardware cookie installation, if required. When installing from the network, you are prompted to configure the network if you have not already done so.

• Option 6: Install Flash Image from Disk—This option is reserved for future expansion and is not available.
• Option 7: Re-create RAID device—This option applies only to WAVE-7541, WAVE-7571, and WAVE-8541 devices and re-creates the RAID array.
• Option 8: Wipe Out Disks and Install.bin Image—This option provides the preferred procedure for installing the WAAS software.

This option performs the following steps:

a. Checks that flash memory is formatted to Cisco specifications. If yes, the system continues to step b. If no, the system reformats the flash memory, which installs the Cisco file system, and generates and installs a platform-specific cookie for the hardware.

b. Erases data from all drives.

c. Re-manufactures the default Cisco file system layout on the disk.

d. Installs the flash memory component from the.bin image.

e. Installs the disk component from the.bin image.

• Option 9: Exit (reboot)—This option ejects the CD-ROM (if applicable) and reboots the device. If you are using a USB flash drive for software installation, remove it from the device before rebooting.

The following sections describe how to reinstall the WAAS system software:

• Preparing the USB Flash Drive—Read this section if you have a WAVE appliance that requires a USB flash drive instead of a CD to install the system software.
• Reinstalling the System Software—Describes how to reinstall the system software from a CD or USB flash drive.
• Ensuring that RAID Pairs Rebuild Successfully—Describes how to ensure that RAID disks rebuild successfully.

Preparing the USB Flash Drive

If you have a WAVE appliance that requires a USB flash drive for software recovery, you must prepare the USB flash drive with the appropriate files before you can start the software recovery process. You will need the following:

• Windows PC (Windows XP or 7) or Mac computer
• USB flash drive that is 1 GB or larger in size
• The following software recovery files:

– WAAS Rescue CD ISO image file, which is available in the WAAS Software Download area of Cisco.com. The filename is similar to waas-rescue-cdrom- x. x. x. x -k9.iso, where the x ’s denote the software version number. Alternatively, the ISO image file is available on the WAAS release DVD, or you can make an ISO image file from a WAAS recovery CD.

– The syslinux.cfg file, which is also available in the WAAS Software Download area of Cisco.com and on the WAAS release DVD.

– Unetbootin utility for Windows or MAC, which is available from the Unetbootin Sourceforge website.

To prepare the USB flash drive on a Windows or MAC computer, follow these steps:

Step 1 Transfer the software recovery files on to the computer, noting the directory in which they are stored.

Step 2 Insert the USB flash drive into a USB port on the computer.

Step 3 Open My Computer (Windows) or Disk Utility (MAC).

Step 4 Format the USB flash drive:

• For Windows, right click the Removable Disk (drive letter will vary with system) and select Format.

– In the formatting tool, from the File System drop-down list, select FAT32.

– In the Format Options sections, check the Quick Format check box, and then click Start.

– Click OK on the warning message.

– Close the formatting tool after the formatting is complete.

• For MAC, select the USB drive on the left side of window, and use the Erase tab to format for use with MS-DOS (FAT).

Step 5 Launch the Unetbootin utility.

Step 6 Select the Diskimage option and click the corresponding browse button (...) to select the waas-rescue-cdrom- x. x. x. x -k9.iso image file.

Step 7 Ensure that USB Drive is selected in the Type drop-down list and that the correct drive letter is selected for Drive.

Step 8 Click OK to install the bootable image in the USB flash drive. When the installation has completed, click Exit.

Step 9 Drag a copy of the syslinux.cfg file into the USB flash drive and click Yes to confirm the replacement. This file replaces the existing file on the USB flash drive with the one customized for your WAAS system.

Step 10 Remove the USB flash drive from the computer.

To continue reinstalling the system software from the prepared USB flash drive, follow the instructions in Reinstalling the System Software.

Reinstalling the System Software

To reinstall the system software on a WAE appliance using the software recovery CD-ROM or USB flash drive, follow these steps:

Step 1 Connect a serial console to the WAAS appliance and use the console for the following steps.

Step 2 Insert the software recovery CD-ROM in the CD drive of the WAE device or, if the device uses a USB flash drive for recovery, insert a bootable USB flash drive with the software recovery files into the USB port of the device (see Preparing the USB Flash Drive). WAVE-294/594/694/7541/7571/8541 devices do not have CD drives; they use a USB flash drive for software recovery.

Step 3 Reboot the WAE. During the boot process, the boot loader pauses for 30 seconds and you must choose the VGA console if you are using vWAAS. The prompt is displayed as follows:

Enter the vga command at the prompt to continue the boot process for the VGA console on vWAAS. After 30 seconds with no input, the boot process continues with the standard serial console for WAAS appliances.

After the WAE boots, you will see the following:

Note The option numbers in the installer main menu may vary, depending on the WAAS software release being installed.

Step 4 Choose Option 2, “Manufacture flash,” to prepare the flash memory.

This step prepares a cookie for the device and also retrieves the network configuration that was being used by the WAAS software. This network configuration is stored in the flash memory and is used to configure the network when the WAAS software boots up after installation.

Step 5 Choose Option 3, “Install flash cookie,” to install the flash cookie that you prepared in the previous step.

Step 6 Choose Option 5, “Install flash image from usb/cdrom,” to install the flash image from a CD-ROM or USB flash drive.

Step 7 (Optional) If you are working with a WAVE-7541, WAVE-7571, or WAVE-8541 device, choose option 7 to recreate the RAID array.

Step 8 Choose Option 8, “Wipe out disks and install.bin image,” to wipe the disks and install the binary image.

This step prepares the disks by erasing them. The WAAS software image is installed.

Step 9 If you are using a USB flash drive to install the software, remove it from the device.

Step 10 Choose Option 9, “Exit (reboot),” to reboot the WAE.

After the WAE reboots, it runs the newly installed WAAS software. The WAE has a minimal network configuration and is accessible via the terminal console for further configuration.

To reinstall the system software on an NME-WAE network module installed in a Cisco access router, follow these steps:

Step 1 Log in to the Cisco router in which the NME-WAE module is installed, and reload the NME-WAE module:

Step 2 Immediately open a session in the module:

Step 3 While the module is loading, you will see the following option during boot phase 3. Enter *** as instructed:

Step 4 The Rescue Image dialog is displayed. The following example shows how to interact with the Rescue Image dialog box (user input is denoted by entries in bold typeface):

Step 5 After the module reboots, install the.bin image from an HTTP server:

Step 6 Reload the module:

After the module reboots, it runs the newly installed WAAS software.

Ensuring that RAID Pairs Rebuild Successfully

Caution You must ensure that all the RAID pairs have completed rebuilding before you reboot your WAE device. If you reboot while the device is still rebuilding, you risk corrupting the file system.

---

RAID pairs will rebuild on the next reboot after you use the restore factory-default command, replace or add a hard disk drive, delete disk partitions, or reinstall WAAS from the booted recovery CD-ROM or USB flash drive.

To view the status of the drives and check if the RAID pairs are in “NORMAL OPERATION” or in “REBUILDING” status, use the show disk details EXEC command. When you see that RAID is rebuilding, you must let it complete that rebuild process. This rebuild process can take several hours.

If you do not wait for the RAID pairs to complete the rebuild process before you reboot the device, you may see the following symptoms indicating a problem:

• The device is offline in the Central Manager GUI.
• CMS cannot be loaded.
• Error message stating that the file system is read-only is displayed.

The syslog contains errors such as:

• Other unusual behaviors related to disk operations or the inability to perform them are visible.

If you encounter any of these symptoms, reboot the WAE device and wait until the RAID rebuild finishes normally.

Recovering the System Software

WAAS devices have a resident rescue system image that is invoked if the image in flash memory is corrupted. A corrupted system image can result from a power failure that occurs while a system image is being written to flash memory. The rescue image can help you download a system image to the main memory of the device and write it to flash memory.

Note The system image used depends on your device. For all WAVE and WAE devices (64-bit platforms), use the 64-bit system image (with “x86_64” in its name). For all other devices, use the 32-bit system image named without this designator.

An NPE image that has the disk encryption feature disabled for use in countries where disk encryption is not permitted is provided.

To install a new system image using the rescue image, follow these steps:

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

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

Step 3 Reboot the device by toggling the power on/off switch.

After a few seconds, the bootloader pauses and prompts you to enter 1 to boot WAAS, r to boot the rescue image, x to reboot, or 9 to escape to the loader prompt. You have 10 seconds to respond before the normal boot process continues.

Step 4 Enter r to boot the rescue image.

The Rescue Image dialog box is displayed and differs depending on whether your WAAS device was initially manufactured with Version 4.x or 5.x. Step 5 describes the rescue image on a device that was initially manufactured with Version 5.x. Step 6 describes the rescue image on a device that was initially manufactured with Version 4.x.

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

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

Step 7 Log in to the device with the username admin. Verify that you are running the correct version by entering the show version command:

Recovering a Lost Administrator Password

If an administrator password is forgotten, lost, or misconfigured, you will have to reset the password on the device.

Note You cannot restore a lost administrator password. You must reset the password, as described in this procedure.

To reset the password, follow these steps:

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

Step 2 Reboot the device.

While the device is rebooting, watch for the following prompt, and press Enter when you see it:

Step 3 When prompted to enter bootflags, enter the value: 0x8000:

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

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

This command invokes interactive password configuration. Follow the CLI prompts.

Step 6 Save the configuration change:

Step 7 (Optional) Reboot your device:

Rebooting is optional. However, we recommend that you reboot to ensure that the boot flags are reset, and to ensure that subsequent console administrator logins do not bypass the password check.

Note In the WAAS software, the bootflags are reset to 0x0 on every reboot.

Recovering from Missing Disk-Based Software

This section describes how to recover from the following types of disk drive issues:

• Your WAAS device contains a single disk drive that needs to be replaced due to a disk failure.
• Your WAAS device contains two disk drives and you intentionally deleted the disk partitions on both drives (diks00 and disk01).

Systems with two or more disk drives are normally protected automatically by RAID-1 on critical system partitions. Therefore, the procedures in this section do not have to be followed when replacing a disk drive in a multidrive system.

To recover from this condition, follow these steps:

Step 1 Deactivate the device by completing the following steps:

a. From the WAAS Central Manager menu, go to Devices > device-name.

b. Choose device-name > Activation. The Device Activation window appears.

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

The device is deactivated.

Step 2 Power down the device and replace the failed hard drive.

Step 3 Power on the device.

Install the WAAS software. For more information on initial configuration, see the Cisco Wide Area Application Services Quick Configuration Guide.

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

Recovering WAAS Device Registration Information

Device registration information is stored both on the device itself and on the WAAS Central Manager. If a device loses its registration identity or needs to be replaced because of a hardware failure, the WAAS network administrator can issue a CLI command to recover the lost information, or in the case of adding a new device, assume the identity of the failed device.

To recover lost registration information, or to replace a failed device with a new one having the same registration information, follow these steps:

Step 1 Mark the failed device as Inactive and Replaceable by completing the following steps:

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

b. Choose device-name > Activation.

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

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

Note This check box appears in the GUI only when the device is inactive.

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

A message is displayed if the failed device is a nonoptimizing peer, indicating that the device is a nonoptimizing peer. When a device is replaced, its device ID changes and therefore, the nonoptimizing peer configuration must be updated.

a. From the WAAS Central Manager menu, choose Configure > Global > Peer Settings. The Peer Settings window for all the devices appears.

b. 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.

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

d. Click Submit.

Step 3 Configure a system device recovery key as follows:

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

b. Click the Edit icon next to the System.device.recovery.key property. The Modifying Config Property window appears.

c. Enter the password in the Value field, and click Submit. The default password is default.

Step 4 Configure the basic network settings for the new device.

Step 5 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 WAAS Central Manager GUI.

When the WAAS Central Manager receives the recovery request from the WAAS device, it searches its database for the device record that meets the following criteria:

• The record is inactive and replaceable.
• The record has the same hostname or primary IP address, as given in the recovery request.

If the recovery request matches the device record, then the WAAS Central Manager updates the existing record and sends the requesting device a registration response. The replaceable state is cleared so that no other device can assume the same identity. When the WAAS device receives its recovered registration information, it writes it to file, initializes its database tables, and starts.

Step 6 Enter the following commands to enable the CMS service on the device:

Step 7 Activate the device:

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

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

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

Step 8 (Optional) Reconfigure the device peer settings, if the device was configured as a nonoptimizing peer with another device (see Information About Clustering Inline WAEs in Chapter 5, “Configuring Traffic Interception”).

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

Converting a WAE to a Standby Central Manager

This section describes how to convert a WAE that is operating as an application accelerator to a standby Central Manager.

There are two types of WAAS software files:

• Universal—Includes Central Manager, Application Accelerator, and AppNav Controller functionality.
• Accelerator only—Includes Application Accelerator and AppNav Controller functionality only. If you want to change an Application Accelerator or AppNav Controller to a Central Manager, you must use the Universal software file.

If the WAE is operating with an Accelerator only image, you cannot convert it to a Central Manager until after you update it with the Universal software file, reload the device, change the device mode to central-manager, and then reload the device again. For information on updating a WAE, see Upgrading the WAAS Software.

Use the show version EXEC command to check if the WAE is running an Accelerator only image. Also, the show running-config EXEC command displays the image type.

To convert a WAE with a Universal image to a standby Central Manager, follow these steps:

Step 1 Deregister the WAE from the Central Manager using the cms deregister force command:

This command cleans up any previous association to any other Central Manager.

Step 2 Configure the device mode as Central Manager using the device mode command:

Step 3 You must reload the device to apply the changes. For more information on reloading and rebooting a device, see Rebooting a Device or Device Group.

Step 4 Configure the Central Manager role as standby using the central-manager role standby command:

Step 5 Configure the address of the primary Central Manager using the central-manager address command:

Step 6 Enable the CMS service using the cms enable command:

Converting a Primary Central Manager to a Standby Central Manager

To convert a primary Central Manager to a standby Central Manager, follow these steps:

Step 1 Deregister the Central Manager using the cms deregister command:

This command cleans up any previous association to any other Central Manager.

Step 2 Configure the Central Manager role as standby using the central-manager role standby command:

Step 3 Configure the address of the primary Central Manager using the central-manager address command:

Step 4 Enable the CMS service using the cms enable command:

Converting a Standby Central Manager to a Primary Central Manager

If your primary WAAS Central Manager becomes inoperable, you can manually reconfigure one of your warm standby Central Managers to be the primary Central Manager. Configure the new role by using the global configuration central-manager role primary command as follows:

This command changes the role from standby to primary and restarts the management service to recognize the change.

If a previous failed primary Central Manager becomes available again, you can recover it to make it the primary Central Manager again. For details, see Central Manager Failover and Recovery.

If you switch a warm standby Central Manager to primary while your primary Central Manager is still online and active, both Central Managers detect each other, automatically shut themselves down, and disable management services. The Central Managers are switched to halted, which is automatically saved in flash memory.

To return halted WAAS Central Managers to an online status, decide which Central Manager should be the primary device and which should be the standby device. On the primary device, execute the following CLI commands:

On the standby device, execute the following CLI commands:

Switching Both the Central Manager Roles

Caution When you switch a WAAS Central Manager from primary to standby, the configuration on the Central Manager is erased. The Central Manager, after becoming a standby, will begin replicating its configuration information from the current primary Central Manager. If standby and primary units are not synchronized before switching roles, important configuration information can be lost.

---

Before you switch Central Manager roles, follow these steps:

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

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

Step 3 Ensure that the standby is synchronized with the primary by checking the status of the following items:

a. Check the online status of your devices.

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

b. Check the status of recent updates from the primary WAAS Central Manager.

Use the show cms info EXEC command and check the time of the last update. 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 WAAS Central Manager has fully replicated the primary WAAS Central Manager configuration.

If the update time is not current, determine whether or not there is a connectivity problem or if the primary 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.

Step 4 Switch roles in the following order:

a. Switch the original primary to standby mode:

b. Switch the original standby to primary mode:

The CMS service is restarted automatically after you configure a role change.

Central Manager Failover and Recovery

If your primary WAAS Central Manager (WAAS CM) becomes inoperable, you can reconfigure one of your standby Central Managers to be the primary Central Manager, and later, when the failed Central Manager becomes available, you can reconfigure it to be the primary again. Follow these steps:

Step 1 Convert a standby Central Manager to be the primary Central Manager, as described in Converting a Standby Central Manager to a Primary Central Manager.

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

Step 3 Switch both the Central Manager roles, as described in Switching Both the Central Manager Roles.

Note In some scenarios, when a Standby Central Manager (SCM) is registered newly with a WAAS Central Manager that is already managing more than 1000 WAEs, the devices may go off line. To avoid this, in case of large deployments, we recommend that you register the SCM to the Primary Central Manager (PCM) at the beginning of the deployment so that in case of an unexpected fail over the SCM takes up the PCM’s role.

Note When a backup operation is in progress on a SCM that is supporting a PCM managing more than 1000 WAEs, the SCM goes off line, if the backup operation takes more than 10 minutes. Additionally you will not be able to login to the PCM GUI when a backup operation is in progress.