Cisco Wide Area Application Services Upgrade Guide (Software Version 6.x)
Available Languages
Table of Contents
Cisco Wide Area Application Services Upgrade Guide
Information About Upgrading to Version 6.1.x, 6.2.x, or 6.4.x
Upgrade Restrictions and Prerequisites
Information About Upgrade Methods
Selecting a WAAS Upgrade Software Image
Creating a Backup of the Primary Central Manager
Upgrading the Standby Central Manager
Upgrading the Primary Central Manager
Upgrading the Branch WAAS Software
Upgrading the Data Center WAAS Software
Validity Testing and Rollbacks
Backing Up the Central Manager Database
Restoring the Central Manager Databases
Restoring the Standby Central Manager Database
Restoring the Primary Central Manager Database
Registering an Upgraded WAE with the Central Manager
Performing a WAE Software Downgrade
Performing WCCP Validity Testing
Performing SMB Validity Testing and Performing a Rollback
Preparing the Shared Server and Client for SMB Validity Testing
Performing a Manual SMB Performance Test with WAAS
Evaluating the Manual Test Results
Obtain Documentation and Submit a Service Request
Cisco Wide Area Application Services Upgrade Guide
Software Versions 6.1.x, 6.2.x, or 6.4.x
This document describes how to upgrade Cisco Wide Area Application Services (WAAS) to software version 6.1.x, 6.2.x, or 6.4.x.
Note The procedures in this note contain CLI command examples. For more information about the commands used in the procedures, see the Cisco Wide Area Application Services Command Reference.
Information About Upgrading to Version 6.1.x, 6.2.x, or 6.4.x
This section provides general information about upgrading your WAAS software to version 6.1.x, 6.2.x, or 6.4.x and contains these topics:
Upgrade Paths
Upgrading to version 6.1.x, 6.2.x, or 6.4.x is supported from certain older versions only. If you have a WAAS device that is running a version from which upgrading directly to version 6.1.x, 6.2.x, or 6.4.x is not supported, first upgrade the device to the next highest supported intermediate version and then upgrade to the desired 6.1.x, 6.2.x, or 6.4.x version.
WAAS Versions and Upgrade Paths specifies which WAAS software versions can be directly upgraded to version 6.1.x, 6.2.x, or 6.4.x and which versions require an intermediate upgrade.
1. Upgrade to version 4.3.x through 5.4.x
1. Upgrade to version 4.3.x through 5.4.x
Upgrade Restrictions and Prerequisites
The following list includes prerequisites and restrictions that you need to know about before upgrading your software:
- You must upgrade the Central Manager software to version 6.1.x, 6.2.x, or 6.4.x prior to upgrading other Wide Area Application Engine (WAE) devices in your network.
- Make sure the Cisco IOS release on the router or switch has been scrubbed for WCCP issues for your specific platform. You must do this action only on routers and switches that participate in transparent redirection and is not applicable to policy-based routing (PBR) or inline deployments. If you do not do this action and there is a current active WAAS network, disable WCCP in the routers and switches in the data center and all branches before the software upgrade to 6.1.x, 6.2.x, or 6.4.x.
- You may need to update firmware or BIOS on some or all of your devices; see the Release Note for Cisco Wide Area Application Services for the latest information on firmware requirements and updates.
- The following device platform is no longer supported on WAAS version 5.1 or later: NME-502. WAAS version 5.1 or later does not operate or install on this device.
- The following device platforms are no longer supported on WAAS version 5.0 or later: NME-302, NME-522, WAE-512, and WAE-612 platforms. WAAS version 5.0 or later does not operate or install on these devices. Additionally, the NME-502 platform is not supported in WAAS version 5.1.
- If you are using NTLM Windows domain authentication or are using a nonstandard port (other than port 88) for Kerberos authentication, you must change these configurations and ensure that your domain controller is configured for Kerebos authentication before proceeding with an upgrade to WAAS version 5.1 or later, which does not support NTLM or nonstandard ports. For more details on the procedure, see the WAAS Release Note for Cisco Wide Area Application Services .
Note If you upgrade from MCPDEV to Cisco IOS XE Denali 16.3 or later image, you need to reinstall the ISR-WAAS.
Note If you are using WCCP, the default value for the WCCP source IP mask changed in version 4.2.1 and later to 0xF00. However, if you are upgrading a WAE that used the previous default WCCP source IP mask of 0x1741 (or any custom mask), its WCCP mask will not be changed. If you are downgrading a WAE to a version earlier than 4.2.1, its WCCP source IP mask will not be changed. By not changing the mask during an upgrade or downgrade, the WAE avoids unexpected mask changes and WCCP farm disruptions. All WAEs in a WCCP farm must have the same mask or they will not participate in the farm.
For important upgrade details, including to which software version you want to upgrade, see the WAAS Release Note for Cisco Wide Area Application Services .
Capacity Planning
Capacity planning is an ongoing process as branches and applications are added. Check the WAE devices to make sure that they are providing adequate caching and optimization and that connection limits are not exceeded.
If you determine that you need more processing capacity, contact your Cisco representative.
Upgrading Your WAAS Software
This section contains the following topics:
- Information About Upgrade Methods
- Upgrading Your Firmware
- Selecting a WAAS Upgrade Software Image
- Upgrading Sequence
- Creating a Backup of the Primary Central Manager
- Upgrading the Standby Central Manager
- Upgrading the Primary Central Manager
- Upgrading the Branch WAAS Software
- Upgrading the Data Center WAAS Software
Information About Upgrade Methods
You can use one of the following methods to perform the WAAS upgrade and transfer the new software image onto the WAE devices in the WAAS network:
- Use the Central Manager Software Update feature to distribute the WAAS software image to WAAS devices.
- Install the software image directly using the Software Recovery CD or USB method to perform a clean install (not an upgrade), which deletes the previous WAAS software image, deletes any cache and so forth.
- Use FTP or TFTP directly on the WAE through the command-line interface (CLI).
The remainder of this document assumes that you are using FTP or TFTP and the CLI to upgrade your software.
If you are using one of the other methods, see the “Maintaining Your WAAS System” chapter of the Cisco Wide Area Application Services Configuration Guide .
Upgrading Your Firmware
On WAE and WAVE appliances, before proceeding with your software upgrade, we recommend that you update the following three types of system firmware to the latest versions to best support new WAAS features:
- BIOS on the WAVE-594/694/7541/7571/8541 models—The latest BIOS is required for the AppNav operation in WAAS version 5.0 and later.
- BMC firmware on the WAVE-294/594/694/7541/7571/8541 models—The latest BMC firmware is required for the Intelligent Platform Management Interface (IPMI) over LAN feature in WAAS version 5.0 and later.
- RAID controller firmware on the WAE-674/7341/7371 and WAVE-7541/7571/8541—The latest RAID controller firmware is recommended to avoid some rarely encountered RAID controller issues.
See the Release Note for Cisco Wide Area Application Services for the latest information on firmware requirements and updates.
Selecting a WAAS Upgrade Software Image
Two different WAAS software images are available. One provides only accelerator and AppNav Controller (ANC) functionality, while the other provides all (universal) functionality, as shown in Table 2 .
Additionally, a separate set of No Payload Encryption (NPE) images are provided that have the disk encryption feature disabled. These images are suitable for use in countries where disk encryption is not permitted. Be sure to use the standard or NPE software images as required. You can recognize the NPE images by the “-npe” designation in the image filenames.
Upgrading Sequence
Use this procedure to upgrade your WAAS network to version 6.1.x, 6.2.x, or 6.4.x.
Step 1 Create a backup of the Central Manager database and save it to an external hard drive, as described in the Creating a Backup of the Primary Central Manager.
Step 2 Upgrade the Secondary Central Manager, if present, as described in the Upgrading the Standby Central Manager.
Step 3 Upgrade the primary Central Manager, as described in the Upgrading the Primary Central Manager.
Note You must upgrade your Central Manager(s) before you upgrade the rest of the WAE devices in your WAAS network.
Step 4 Upgrade the other WAE network devices, as described in the Upgrading the Branch WAAS Software and the Upgrading the Data Center WAAS Software.
Note The CIFS application is removed from WAAS Version 6.0 and later. For information about CIFS to SMB migration, please see earlier versions of the Cisco Wide Area Application Services Upgrade Guide.
Creating a Backup of the Primary Central Manager
Use this procedure to back up the primary Central Manager (CM) database and copy the backup file to an FTP server.
Step 1 Telnet to the primary CM.
Step 2 Create the database backup.
Step 3 Copy the backup file to a remote FTP server.
Step 4 Verify that the backup file copied correctly by checking the file for correct size and timestamp.
Upgrading the Standby Central Manager
Use this procedure to upgrade the WAAS software on the standby CM.
Step 1 Telnet to the standby CM IP address.
Step 2 Copy the new software image to the standby CM.
This example assumes that the file is in the root directory of the FTP server. Provide the correct path if needed.
Step 4 Verify that the new image loaded correctly.
Step 5 Ping the primary CM and branch WAE devices to confirm connectivity.
Step 6 Wait at least 5 minutes and then confirm the database last synchronization time to ensure that the database has been synchronized.
Step 7 From the primary CM, confirm that the status indicator for the standby CM is online and green.
Upgrading the Primary Central Manager
Use this procedure to upgrade the WAAS software on the primary CM.
Upgrade the standby CM before you upgrade the primary CM, as described in the “Upgrading the Standby Central Manager” section.
Step 1 Telnet to the primary CM IP address.
Step 2 Copy the new software image to the primary CM.
This example assumes that the file is in the root directory of the FTP server. Provide the correct path if needed.
Step 4 Verify that the new image loaded correctly.
Step 5 Ping the standby CM and branch WAE devices to confirm connectivity.
Step 6 Confirm that the CMS services are running.
Step 7 Verify that all the WAE devices are online and in the AllWAASGroup.
a. Choose Devices > All Devices and verify that all the WAE devices are online and have a green device status.
b. Choose Device Groups > AllWAASGroup > Assign Devices and verify that all WAEs are listed with a green check mark.
The CMs are updated with the new WAAS software version 6.1.x, 6.2.x, or 6.4.x. The standby CM was upgraded first followed by the primary CM.
Upgrading the Branch WAAS Software
Use this procedure to upgrade each WAAS branch WAE to version 6.1.x, 6.2.x, or 6.4.x.
- Make sure that you have already upgraded the secondary and primary CM(s)
- Use FTP to copy the WAAS software image to a local server or push the software image to your WAE devices through the CM, as described in the “Maintaining Your WAAS System” chapter of the Cisco Wide Area Application Services Configuration Guide .
Step 2 Verify that all the WAE devices are online (green).
Step 3 Address any alarm conditions that may exist.
Step 4 Open a console or Telnet session to the branch WAE.
Step 5 Copy the software image to the WAE.
This example assumes that the file is in the root directory of the FTP server. Provide the correct path if needed. You can use either the Universal or Accelerator-only images.
Step 7 Verify that the image installed correctly.
Step 8 Verify that the correct licenses are installed.
If an Enterprise license has been purchased and not enabled, go to Steps 9 and 10. Otherwise, go to Step 11.
Step 9 (Optional) Clear the Transport license.
Step 10 (Optional) Add the Enterprise license.
Step 11 Save the configuration.
Step 12 From the WAAS CM GUI, choose Devices > branchWAE and verify that the WAE is online and has a green device status.
Step 13 Verify the WAE device functionality as follows:
a. Assuming that WCCP is used for the traffic interception method, verify the WCCP is functioning properly.
b. (Optional) Confirm that flows are being optimized.
c. Confirm that the Enterprise license is enabled.
If the Enterprise license is not enabled, proceed with Steps d through f.
d. Clear the Transport license.
e. Add the Enterprise license.
f. Save the changed configuration.
All the branch WAE devices within the active WAAS network are upgraded to version 6.1.x, 6.2.x, or 6.4.x.
Upgrading the Data Center WAAS Software
Use this procedure to prepare for and upgrade the data center WAAS Software to version 6.1.x, 6.2.x, or 6.4.x.
Step 2 Verify that all the WAE devices are online (green).
Step 3 Address any alarm conditions that may exist.
Step 4 Follow the procedure in the Upgrading Each Data Center WAE, for each data center device.
Note This procedure removes the WAE from the interception path while the upgrade is done and applies to deployments that use WCCP for redirection in the data center. If you are not using WCCP interception in the data center, you should use another method to remove the WAE from the interception path. For an inline deployment, use the interface InlineGroup slot/group shutdown global configuration command to bypass the traffic on the active inline groups. In a serial inline cluster, shut down the interfaces on the intermediate WAE first, then on the optimizing WAE in the cluster. For a deployment using Cisco ACE for interception, gracefully shut down the ACE real server by using the no inservice command in either real server host or real server redirect configuration mode.
Upgrading Each Data Center WAE
Use this procedure to upgrade the data center WAE software.
Step 1 Disable WCCP on the WAE as follows to allow a graceful termination of existing TCP flows that are optimized by WAAS:
b. Wait until the countdown expires or press Ctrl-C to skip waiting for a graceful WCCP shutdown.
c. Verify that WCCP is disabled.
d. Save the changed configuration.
Step 2 (Optional) Disable WCCP on the intercepting router or switch. This step is recommended only if the Cisco IOS release on the router or switch has not been scrubbed for WCCP issues for your specific platform.
Step 3 (Optional) Verify that WCCP is disabled. This step is needed only if you disabled WCCP in Step 2.
Step 4 Upgrade the data center WAE software as follows:
a. Open a console or Telnet session to the data center WAE.
b. Copy the software image to the WAE.
This example assumes that the file is in the root directory of the FTP server. Provide the correct path if needed. You can use either the Universal or Accelerator only images.
d. Verify that the image installed correctly.
e. Confirm that WCCP is disabled.
f. Save the changed configuration.
Step 5 From the WAAS CM GUI, choose Devices > dataCenterWAE and verify that the WAE is online and has a green device status.
Step 6 (Optional) Enable WCCP on all intercepting routers or switches in the router list as follows:
a. Telnet to each core router or switch.
See the Enabling WCCP on WAE Devices in a Cluster for an example ACL template.
This step is needed only if you disabled WCCP in Step 2.
Step 7 Verify WAE device functionality as follows:
If you are using wccp single service, use these commands instead:
b. Confirm that redirecting intercepting router IDs are seen.
c. Confirm that all WAE devices in the cluster are seen.
d. Confirm that the packet count to the WAE is increasing and no loops are detected.
e. Verify that the buckets assigned for Service Group 61 match those of Service Group 62 and are assigned to the WAE.
f. Confirm that flows are being optimized.
All WAE devices in the data center are upgraded to version 6.1.x, 6.2.x, or 6.4.x and have WCCP enabled.
Enabling WCCP on WAE Devices in a Cluster
Use this procedure to enable WCCP on WAE devices in a cluster.
Step 1 Validate your Cisco IOS release with a bug scrub for WCCP-related issues for your specific platform.
Step 2 Enable WCCP on the WAEs in the cluster
Step 3 Enable WCCP on the intercepting routers or switches; you can use or modify the following router ACL template for running WCCP in your network.
Validity Testing and Rollbacks
This section describes specific actions that are related to backing up your software, restoring your software from a backup, registering upgrades, and testing different aspects of your network affected by the upgrade.
- Backing Up the Central Manager Database
- Restoring the Central Manager Databases
- Registering an Upgraded WAE with the Central Manager
- Performing a WAE Software Downgrade
- Performing WCCP Validity Testing
- Performing SMB Validity Testing and Performing a Rollback
Backing Up the Central Manager Database
Use this procedure to back up the databases of the primary and standby CMs.
Step 1 From the primary CM, create a backup of the database.
Step 2 Copy the primary CM backup file to a remote location.
Step 3 From the standby CM, create a backup of the database.
Step 4 Copy the standby CM backup file to a remote location.
Restoring the Central Manager Databases
This section describes how to restore the databases on the primary and standby CMs using their database backup files (see the Backing Up the Central Manager Database).
Use the following guidelines when restoring the CM databases:
- Ensure that the CM is using the same software version as when the database backup file was created.
- Restore the standby CM first and then restore the primary CM.
- If you are restoring a backup from a CM where the secure store was in user-provided passphrase mode when the backup was made, you may be asked to provide the secure store password during the restore process. For more information on the secure store, see the “Configuring Other System Settings” chapter of the Cisco Wide Area Application Services Configuration Guide.
Restoring the Standby Central Manager Database
Use this procedure to restore the standby CM database.
Step 1 From the standby CM, disable the Centralized Management System (CMS) service.
Step 2 Delete the existing CMS database.
Step 3 Initialize the CMS database.
Step 4 Restore the CMS database contents from the backup file.
Step 5 Enable the CMS service.
Step 6 Verify that the CMS services are running and that the database has synchronized.
Wait at least 5 minutes and then confirm that the database last synchronization time is current. If the time is not current, wait another 5 minutes.
Step 7 Check the current date and time on the standby CM.
Step 8 Verify the CMS status in the running configuration.
Restoring the Primary Central Manager Database
Use this procedure to restore the primary CM database.
Restore the standby CM database before you restore the primary CM database (see the Restoring the Standby Central Manager Database).
Step 1 From the primary CM, disable the CMS service.
Note Stopping the CMS service disables the CM GUI. All users logged in to this GUI are logged out when the CMS service is disabled.
Step 2 Delete the existing CMS database.
Step 3 Initialize the CMS database.
Step 4 Restore the CMS database contents from the backup file.
Step 5 Enable the CMS service.
Step 6 Verify that the CMS services are running.
Step 7 Check the current date and time on the standby CM.
Step 8 Confirm that you see “Ready to accept incoming RPC requests” in the log file (errorlog/cms_log.current), which indicates that the WAE is ready to establish connections with the Central Manager.
Look for the timestamp from the output and compare it with the current time.
Step 9 Verify the CMS status in the running configuration.
Step 10 Access the CM GUI from a browser.
Registering an Upgraded WAE with the Central Manager
If you cannot set a WAE in the Central Manager after upgrading the device, you must register the upgraded WAE, as shown in the following procedure.
Step 1 From the CM, delete the branch WAE.
Step 2 From the branch WAE, enter the following commands:
Step 3 From the CM, choose Devices > branchWAE > Activation to activate the branch WAE.
Performing a WAE Software Downgrade
Use this procedure to install a previous version of software on a branch WAE if you encounter a problem during the upgrade.
Step 1 Determine the previously installed version.
Step 2 Install the previous WAAS software version as follows:
b. Install the previous version software image.
Step 4 Verify that the software image installed correctly.
If you want to downgrade your entire WAAS network software to a previous version, see the Release Note for Cisco Wide Area Application Services .
Performing WCCP Validity Testing
This section lists the commands that you can use for WCCP validity testing.
Enter the commands three to four times in succession to determine if counters are incrementing.
– show wccp flows tcp-promiscuous detail
– show ip wccp service service
– show ip wccp service internal (available in most recent releases only)
– show ip wccp interface detail (available in most recent releases only)
– show mls netflow table detail
– show mls netflow ip sw-installed count
– show mls netflow ip sw-installed detail
– show fm interface interface_name
– show tcam interface interface name acl { in | out } ip
– show tcam interface interface name acl { in | out } ip detail
For possible Cisco IOS issues, capture the following debug output to either the console or a Telnet session:
Performing SMB Validity Testing and Performing a Rollback
This section describes the methods that you can use for SMB validity testing, which includes manual procedures and automation tools.
Use the following guidelines when performing SMB validity testing and performing a rollback:
- Choose a single file or a variety of files for the test. You must use the same file or files for all the tests (base, cold, hot).
- Use an existing share or create a directory structure on the file server. Verify that the share has permissions set for domain users. We recommend that you test or create a share that has multiple nested directories (at least 2 to 3 levels deep) that contain files of various types (such as PowerPoint, Excel or Word) and sizes.
Preparing the Shared Server and Client for SMB Validity Testing
Use this procedure to prepare the shared server and client for SMB validity testing.
Step 1 On the server, create a share directory that contains several subfolders and files.
Step 2 Verify the following items on the shared server:
- Adequate permissions for domain users used in the testing.
- Domain users can access the share before testing WAAS.
- SMB signing (digital signature) is disabled on the server.
Step 3 Verify the following items on the client:
- PC clients are part of the tested domain environment.
- A domain user exists for each PC client.
- Tested shares do not rely on local user and groups but rather have permissions for domain users and groups.
- Microsoft Office (Word, Excel, PowerPoint) is installed.
Performing a Manual SMB Performance Test with WAAS
Use this procedure to manually perform a SMB performance test.
Step 1 Verify operation by opening some Microsoft Office documents from the shared server.
Record the filename, size, and open time.
Step 2 Modify the files by adding some text and saving.
Record the time it takes to save.
Step 3 Open the files again to inspect response time and data integrity.
Record the time it took to open them and get to the place where your changes were made.
Step 4 Evaluate the results of the testing (see the Evaluating the Manual Test Results).
Evaluating the Manual Test Results
This section describes the expected results of the manual SMB performance test (see the Performing a Manual SMB Performance Test with WAAS).
The test should show significant improvement in the time to open and time to save operations. The same behavior should also be observed with the modified file.
The Central Manager provides real-time statistics and a summary report for SMB connections ( Devices > branchWAE > Monitor > Acceleration > SMB Acceleration Report ).
Figure 1 shows some of the SMB charts.
Figure 1 SMB Acceleration Report
From the CLI, the following information appears:
To display detailed information about any SMB connection, enter the show statistics connection optimized smb detail command.
To display overall SMB accelerator statistics, enter the show statistics accelerator smb detail command as follows:
Additional Resources
For additional information on the Cisco WAAS software, see the following documentation:
- Release Note for Cisco Wide Area Application Services
- Cisco Wide Area Application Services Quick Configuration Guide
- Cisco Wide Area Application Services Configuration Guide
- Cisco Wide Area Application Services Command Reference
- Cisco Wide Area Application Services API Reference
- Cisco Wide Area Application Services Monitoring Guide
- Cisco Wide Area Application Services vWAAS Installation and Configuration Guide
- Cisco WAAS Installation and Configuration Guide for Windows on a Virtual Blade
- Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later
- Cisco WAAS on Service Modules for Cisco Access Routers
- Cisco SRE Service Module Configuration and Installation Guide
- Configuring Cisco WAAS Network Modules for Cisco Access Routers
- WAAS Enhanced Network Modules
- Regulatory Compliance and Safety Information for the Cisco Wide Area Virtualization Engines
- Cisco Wide Area Virtualization Engine 294 Hardware Installation Guide
- Cisco Wide Area Virtualization Engine 594 and 694 Hardware Installation Guide
- Cisco Wide Area Virtualization Engine 7541, 7571, and 8541 Hardware Installation Guide
- Cisco Wide Area Virtualization Engine 274 and 474 Hardware Installation Guide
- Cisco Wide Area Virtualization Engine 574 Hardware Installation Guide
- Regulatory Compliance and Safety Information for the Cisco Content Networking Product Series
- Cisco Wide Area Application Engine 7341, 7371, and 674 Hardware Installation Guide
- Installing the Cisco WAE Inline Network Adapter
Obtain Documentation and Submit a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation .
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed . The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Additional Resources” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)