Release Note for Cisco Wide Area Application Services (Software Version 6.2.3x)

Cisco Software Version 6.2.3x New and Changed Features

This section contains the following topics:

• WAAS Version 6.2.3e New and Changed Features
• WAAS Version 6.2.3d New and Changed Features
• WAAS Version 6.2.3b New and Changed Features

WAAS Version 6.2.3e New and Changed Features

• Unique alarm identifier support—WAAS Central manager now identifies every device alarm instance with an unique identifier. This allows for better tracking raised and cleared alarms and link notifications with GUI outputs.

WAAS Version 6.2.3d New and Changed Features

• Alarm Email Notification- With release 6.2.3d, the WAAS software supports an email notification mechanism, that is triggered whenever the WAAS Central Manager receives an alarm notification for a raised or cleared alarm. To configure the alarm email notification feature:

– From the WAAS Central Manager menu go to Devices > Configure > Monitoring > Email Notification to configure the email server settings.

– From the WAAS Central Manager go to Home > Admin > Alarm Email Notification > Configure to configure the email notification settings.

You can enable the email notification for Raised and Cleared alarms, depending on the severity level. After you have configured this, you are notified of all alarms for the devices that are registered with the WAAS Central Manager.

• Easy detection and resolution of configuration conflicts between WAAS Central Manager and WAAS Devices.

To identify the configuration conflict pages, from the WAAS Central Manager navigate to Home > Admin > Force Device Group > View Pages to see the impacted Device Name, Device Group Name and Page Name. You can click on the page link to navigate to the corresponding page to correct the configuration conflict.

WAAS Version 6.2.3b New and Changed Features

• Configuring ICA over Socket Secure (SOCKS) Server—For WAAS Version 6.2.3b and later, WAAS software supports optimizing ICA traffic redirected over SOCKS proxy servers. For details on how to configure ICA over SOCKS for WAAS, see Configuring ICA over Socket Secure (SOCKS) Server.
• SMART-SSL, an encryption service that enables L7 application network services (such as FTP, HTTP, DNS) to optimize traffic on SSL/TLS encrypted applications. SMART-SSL enables content caching for SSL/TLS applications (HTTP object cache for HTTPS traffic) in single-sided deployment.
  
  For how to configure and use this feature, see “Configuring SMART-SSL” in the “Configuring Application Acceleration” chapter of the Cisco Wide Area Application Services Configuration Guide.
• Cisco WAAS Version 6.2.3 with Akamai Connect Version 1.4.2
• vWAAS new and changed features:

– vWAAS in KVM on CentOS

For a list of CLI commands added to or changed for WAAS Version 6.2.3x, see Cisco WAAS Software Version 6.2.3 Command Changes.

Cisco Software Version 6.2.3x Filenames

This section describes the Cisco WAAS Software Version 6.2.3x software image files for use on Cisco WAAS appliances and modules and contains the following topics:

• Standard Image Files
• No Payload Encryption Image Files
• For a list of vWAAS image files, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.

Standard Image Files

Cisco WAAS Software Version 6.2.3x includes the following standard primary software image files for use on Cisco WAAS appliances and modules:

• waas-universal-6.2.3. x -k9.bin—Universal software image that includes Central Manager and Application Accelerator functionality. You can use this type of software file to upgrade a device operating in any device mode.
• waas-accelerator-6.2.3. x -k9.bin—Application Accelerator software image that includes Application Accelerator functionality only. You can use this type of software file to upgrade only an Application Accelerator device. This software image file is significantly smaller than the Universal image. Kdump analysis functionality is not included in the Accelerator-only image.

The following additional files are also included:

• waas-rescue-cdrom-6.2.3. x -k9.iso—Cisco WAAS software recovery CD image.
• waas-sre-installer-6.2.3.x-k9.zip—Image for SRE installer.

Note From software version 6.2.3d, separate software images for the SRE installer are not supported. If you want to upgrade your existing SRE deployments, you need to use the standard software image file WAAS-6.2.3.x-k9.bin.

For EOS announcement of select Cisco Services-Ready Engine Modules, please refer to the EOS document on cisco,com.

• waas-x86_64-6.2.3. x -k9.sysimg—Flash memory recovery image for 64-bit platforms (WAVE-294/594/694/7541/7571/8541).
• waas-6.2.3. x -k9.sysimg—Flash memory recovery image for 32-bit platforms (all other devices).
• waas-kdump-6.2.3. x -k9.bin—Kdump analysis component that you can install and use with the Application Accelerator software image. The Kdump analysis component is intended for troubleshooting specific issues and should be installed following the instructions provided by Cisco TAC.
• waas-alarm-error-books-6.2.3. x.zip—Contains the alarm and error message documentation.

No Payload Encryption Image Files

Cisco WAAS Software Version 6.2.3x includes No Payload Encryption (NPE) primary software image files that have the disk encryption feature disabled. These images are suitable for use in countries where disk encryption is not permitted. NPE primary software image files include the following:

• waas-universal-6.2.3. x -npe-k9.bin—Universal NPE software image that includes Central Manager and Application Accelerator functionality. You can use this type of software file to upgrade a device operating in any device mode.
• waas-accelerator-6.2.3. x -npe-k9.bin—Application Accelerator NPE software image that includes Application Accelerator functionality only. You can use this type of software file to upgrade only an Application Accelerator device. This software image file is significantly smaller than the Universal image. Kdump analysis functionality is not included in the Accelerator-only image.
• waas-sre-installer-6.2.3. x -npe-k9.zip—SM-SRE install.zip file that includes all the NPE files necessary to install Cisco WAAS on the SM-SRE module.

The following additional files are also included:

• waas-rescue-cdrom-6.2.3. x -npe-k9.iso—Cisco WAAS NPE software recovery CD image.
• waas-x86_64-6.2.3. x -npe-k9.sysimg—Flash memory NPE recovery image for 64-bit platforms (WAVE-294/594/694/7541/7571/8541).
• waas-6.2.3. x -npe-k9.sysimg—Flash memory NPE recovery image for 32-bit platforms (all other devices).
• waas-alarm-error-books-6.2.3. x -npe.zip—Contains the NPE alarm and error message documentation.

Cisco WAAS Appliance System Firmware Update

On Cisco Wide Area Application Engine (WAE) and Cisco Wide Area Application Virtualization Engine (WAVE) appliances, we recommend that you update the following three types of system firmware to the latest version to best support new Cisco WAAS features.

This section contains the following topics:

• BIOS Update

BIOS on the WAVE-294/594/694/7541/7571/8541 models. The latest BIOS is required for AppNav operation.

• BMC Firmware Update

BMC firmware on the WAVE-294/594/694/7541/7571/8541 models. The latest BMC (Baseboard Management Controller) firmware is required for Intelligent Platform Management Interface (IPMI) over LAN feature.

• RAID Controller Firmware Update

RAID controller firmware on the WAVE-7541/7571/8541. The latest RAID (Redundant Array of Independent Disks) controller firmware is recommended to avoid some rarely-encountered RAID controller issues.

BIOS Update

The latest BIOS is required for AppNav operation with a Cisco AppNav Controller Interface Module in WAVE-594/694/7541/7571/8541 models. WAVE-294 models may also need a BIOS update.

Note AppNav IOM is not supported in WAAS Software version 6.1.x and later.

WAVE-594/694/7541/7571/8541 appliances shipped from the factory with Cisco WAAS Version 5.0.1 or later have the correct BIOS installed. WAVE-294 appliances shipped from the factory with Cisco WAAS Version 5.1.1 or later have the correct BIOS installed.

If you install a Cisco AppNav Controller Interface Module in a device that requires a BIOS update, the bios_support_seiom major alarm is raised, “I/O module may not get the best I/O performance with the installed version of the system BIOS firmware.”

To determine if a device has the correct BIOS version, use the show hardware command. The last three characters of the Version value, for example, “20a,” show the BIOS version installed on the device.

For the specific BIOS version required for WAVE-594/694 models, WAVE-7541/7571/8541 models, and WAVE-294 models or if a BIOS firmware update is needed, you can download it from cisco.com at the Cisco Wide Area Application Service (WAAS) Firmware download page ( registered customers only). The firmware binary image for WAVE-294/594/694/7541/7571/8541 appliances is named waas6-bios-installer-20a-19a-13a-k9.bin.

You can use the following command to update the BIOS from the image file that is available through FTP on your network:

copy ftp install ip-address remotefiledir waas6-bmc-installer-49a-49a-27a-k9.bin

Use the appropriate BIOS installer file for your appliance model.

The complete update process can take several minutes and the device may appear unresponsive but do not interrupt the process or power cycle the device. After the update is complete, you must reload the device.

After the device reboots, you can verify the firmware version by using the show hardware command.

BMC Firmware Update

IPMI over LAN requires that you install a specific BMC firmware version on the device. The minimum supported BMC firmware versions are as follows:

• WAVE-294/594/694—49a
• WAVE-7541/7571/8541—27a

Cisco WAAS appliances shipped from the factory with Cisco WAAS Version 4.4.5 or later have the correct firmware installed. If you are updating a device that was shipped with an earlier version of Cisco WAAS software, you must update the BMC firmware, unless it was updated previously.

To determine if you are running the correct firmware version, use the show bmc info command. The following example displays the latest BMC firmware version installed on the device (49a here):

If a BMC firmware update is needed, you can download it from cisco.com at the Cisco Wide Area Application Service (WAAS) Firmware download page ( registered customers only). For example, if the firmware binary image is named waas-bmc-installer-49a-49a-27a-k9.bin, you can use the following command to update the firmware from the image file that is available through FTP on your network:

copy ftp install ip-address remotefiledir waas6-bmc-installer-49a-49a-27a-k9.bin

The update process automatically checks the health status of the BMC firmware. If the system detects that the BMC firmware is corrupted, BMC is recovered during the BMC firmware update procedure. The complete update process can take several minutes. If the device appears unresponsive, do not interrupt the process or power cycle the device. After the update is complete, you must reload the device.

After the device reboots, you can verify the firmware version by using the show bmc info command.

BMC recovery and BMC firmware update restores the factory defaults on the BMC and all the current IPMI over LAN configurations are erased.

If the BMC firmware gets corrupted, a critical alarm is raised.

RAID Controller Firmware Update

We recommend that you upgrade to the latest RAID-5 controller firmware for your hardware platform, which can be found on cisco.com at the Cisco Wide Area Application Service (WAAS) Firmware download page ( registered customers only). The firmware differs depending on your hardware platform:

• WAVE-7541/7571/8541—Update to the 12.12.0 (0060) RAID Controller Firmware (or later version).

The firmware binary image is named waas6-raid-fw-installer-12.12.0-0060-k9.bin. Instructions on how to apply the firmware update are posted on cisco.com together with the firmware in the file named M2_0060_FIRMWARE.pdf, which you can see when you hover the mouse over the firmware file.

Configuring ICA over Socket Secure (SOCKS) Server

This section contains the following topics:

• About ICA over SOCKS Optimization
• Limitations of ICA over SOCKS Optimization
• Configuration Procedure for Optimizing ICA over SOCKS

About ICA over SOCKS Optimization

In a typical deployment where NetScaler is deployed as a SOCKS proxy, the connections from the client go to the SOCKS server instead of the XenApp server.

Since the ICA optimizer accepts and intercepts only ICA and CGP packets, the packets with SOCKS headers are not recognized and the connection is handed off. The ICA traffic does not get optimized in such scenarios.

For WAAS Version 6.2.3b and later, the WAAS software supports optimizing ICA traffic redirected over SOCKS proxy servers.

Limitations of ICA over SOCKS Optimization

ICA over SOCKS optimization has the following limitations:

• The NetScaler gateway does not support non-default ports configured with Multi-Port Policy on XenApp for Multi-Stream ICA (MSI).
• The NetScaler gateway does not support SOCKS with ICA over SSL.

Additionally, the NetScaler gateway does not support SOCKS v4. so the current functionality supports only SOCKS v5.

Configuration Procedure for Optimizing ICA over SOCKS

To support optimizing ICA over SOCKS, perform the following steps:

Step 1 Make the necessary changes in the NetScaler Gateway to enable the SOCKS proxy (Cache redirection server) and also make the equivalent/required changes on the StoreFront server along with updates to the default.ica file. Refer to Citrix NetScaler documentation for more information.

Step 2 From the WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name). Next choose Configure > Acceleration > Optimization Class-Map.

Step 3 Edit the class-map named Citrix and add the required port number using the Add Match Condition option.
The port number added in the class-map should be the same as the one configured for the SOCKS proxy, on the NetScaler gateway. Note that in case the SOCKS proxy port is running on ICA or CGP ports i.e. 1494 or 2498, then the existing configuration need not be modified.

Step 4 Select the branch device and make the necessary changes for the port number.

Alternately use the class-map type match-any citrix global configuration command to make these changes.

Hardware, Client, and Web Browser Support

This section contains the following topics:

• Platforms Supported by WAAS
• Browsers Supported by WAAS

Platforms Supported by WAAS

The Cisco WAAS software operates on these hardware platforms:

• WAVE-294, 594, 694, 7541, 7571, 8541
• SM-SRE-700/710, 900/910
• ISR-WAAS-200, 750, 1300, 2500
• vWAAS-150, 200, 750, 1300, 2500, 6000, 12000, 50000 on ESXi. For information on minimum ESXi version supported for each vWAAS model, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
• vWAAS-150, vWAAS-200, 750, 1300, 2500, 6000, 12000, 50000 on Microsoft Hyper-V. For information on the version of Windows supported for each vWAAS model on Microsoft Hyper-V, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
• For WAAS Version 6.2.1 and later, vWAAS is supported on RHEL KVM. For WAAS Version 6.2.3x and later, vWAAS is supported on KVM on CentOS and Microsoft Azure.
  
  For more information on vWAAS for RHEL KVM, KVM on CentOS, and vWAAS on Microsoft Azure, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
• Additionally, Cisco 880 Series, 890 Series, and ISR G2 routers running Cisco WAAS Express are supported on the branch side (Cisco WAAS Version 5.0.x or later is required on the data center side).

You must deploy the Cisco WAAS Central Manager on a dedicated device.

Browsers Supported by WAAS

The Cisco WAAS Central Manager GUI requires Internet Explorer Version 11, Windows Version 7 or later, Firefox Version 4 or later, Chrome Version 10 or later, or Safari version 5.x (only on Apple OS X) and the Adobe Flash Player browser plug-in.

Note For best results for Windows-based systems with WAAS, we recommend using FireFox as your browser.

• For WAAS version 5.4.1 and later, you are no longer prompted to install the Google Frame plug-in when you access the Central Manager GUI using Internet Explorer. However, if Google Frame plug-in has already been installed earlier, IE will continue using it.
• When using Internet Explorer, ensure that the Tools > Internet Options > Advanced tab > Do not save encrypted pages to disk check box (under Security) is checked. If this box is unchecked, some charts will not display.

Note A known issue in Chrome Version 44.0 may prevent some WAAS Central Manager pages—including Device Listing, Reports, Software Update pages—from loading properly. In all other Chrome versions, earlier and later than Chrome Version 44.0, all WAAS Central Manager pages work as expected.

Cisco WAAS Version Interoperability

Consider the following guidelines when operating a Cisco WAAS network that mixes Software Version 6.2.3x devices with devices running earlier software versions:

• Cisco WAAS CM interoperability:
  
  In a mixed version Cisco WAAS network, the Central Manager must be running the highest version of the Cisco WAAS software, and associated Cisco WAAS devices must be running Version 5.1.x or later.
• Cisco WAAS system interoperability:
  
  Cisco WAAS Version 6.2.3x is not supported running in a mixed version Cisco WAAS network in which any Cisco WAAS device is running a software version earlier than Version 5.1.x. Directly upgrading a device from a version earlier than Version 5.5.3 to 6.2.3x is not supported.

Cisco WAAS and vWAAS Interoperability

Table 1 shows the default number of CPUs, memory capacity, disk storage and supported ISR platforms for ISR models. Table 2 shows the default number of CPUs, memory capacity and disk storage for vWAAS models.

Table 1 ISR Models: CPUs, Memory, Disk Storage and Supported ISR Platforms

Note For vWAAS with WAAS Version 6.2.3c or later, for ISR-4321 with profile ISR-WAAS-200, the ISR-WAAS RAM is increased from 3 GB to 4 GB. For this increase in ISR-WAAS RAM to be implemented, you must complete a new OVA deployment of WAAS version 6.2.3c or later. The increase in ISR-WAAS RAM is not automatically implemented with an upgrade to WAAS Version 6.2.3c or later.

Table 2 vWAAS Models: CPUs, Memory and Disk Storage

Consider the following guidelines when using Cisco vWAAS with WAAS:

Note For vWAAS for WAAS Version 6.2.x with Cisco Enterprise NFVIS, the vWAAS must run as an unmanaged VM.

• For vWAAS with WAAS Version 6.2.3x, ISR-4321 with profile ISR-WAAS-200, ISR-WAAS RAM is increased from 3 GB to 4 GB. For this increase in ISR-WAAS RAM to be implemented, you must complete a new OVA deployment of WAAS version 6.2.3x; the increase in ISR-WAAS RAM is not automatically implemented with an upgrade to WAAS 6.2.3x.
• When selecting the format in the vSphere Client for the virtual machine’s disks for vWAAS with VMware vSphere ESXi, you must choose the Thick Provision Eager Zeroed disk format for vWAAS deployment; this is the format recommended with vWAAS deployment for a clean installation.
• vWAAS and DRE partitions:

– When you deploy vWAAS using OVAs older than the 6.2.3d version, DRE's ackq and plz partitions are not created as expected for vWAAS-6000, 12000, and 50000 models (they are created of lesser size and no alarms will be displayed to indicate the mismatch in partition sizes). Because of this, the connection flow for vWAAS will not be optimized by DRE after a certain period. To ensure DRE optimization for vWAAS, after deployment you must use the disk delete-data-partitions command to re-create these partitions for vWAAS.

Note If the vWAAS device is downgraded in the following scenarios:

—from vWAAS for WAAS Version 6.4.1a to WAAS Version 6.2.3x, or
—from vWAAS for WAAS Version 6.x to 5.x

the WAAS alarm filesystem_size_mismatch is displayed; it indicates that the partition was not created as expected. To clear the alarm, use the disk delete-data-partitions command to re-create the DRE partitions.

– If you deploy vWAAS with WAAS version 6.2.3d or later, an issue will not be seen. Here, partitions will be created as expected.

Note The disk delete-data-partitions command will re-create the partition and leads to cache loss.

For more information on the disk delete-data-partitions command, see the Cisco Wide Area Application Services Command Reference. For more information on DRE compression, see the Cisco Wide Area Application Services Configuration Guide.

• For vWAAS in Azure, the supported traffic interception method is PBR (Police-Based Routing); vWAAS in Azure does not support WCCP or AppNav interception methods.

Caution Multiple deployments of vWAAS on the same Hyper-V host in parallel may cause unexpected results, due to availability of free space when creating VHDs. We recommend that you do not deploy multiple vWAAS on Hyper-V in parallel, unless you have verified that you have enough free disk space required for the respective vWAAS models.

---

• For vWAAS with WAAS Version 6.1.x and later, the vWAAS and vCM devices require both virtual (network) interfaces to be present, but both need not be active. If only one virtual interface is active, the vWAAS and vCM devices will not be operational after power up. For more information, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
• To ensure reliable throughput with the following configuration—vWAAS on Windows Server 2012 R2 Hyper-V in Cisco UCS-E Series 160S-M3—we recommend that you do the following:

– Upgrade to the latest UCS-E firmware (Version 3.1.2), available on the Cisco Download Software Page for UCS E-Series Software, UCS E160S M3 Software.

– Verify that you have installed the critical Windows Server updates, available on the Microsoft Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update Rollup page. You can also obtain the standalone update package through the Microsoft Download Center by searching for KB2887595.

Note When upgrading vWAAS, do not upgrade more than five vWAAS nodes at the same time on a single UCS box. Upgrading more than five vWAAS nodes at the same time may cause the vWAAS devices to go offline and diskless mode.

• If the virtual host was created using an OVA file of vWAAS for WAAS Version 5.0 or earlier, and you have upgraded vWAAS within WAAS, you must verify that the SCSI Controller Type is set to VMware Paravirtual. Otherwise, vWAAS will boot with no disk available and will fail to load the specified configuration.

If needed, change the SCSI controller type to VMware Paravirtual by following these steps:

a. Power down the vWAAS.

b. From the VMware vCenter, navigate to vSphere Client > Edit Settings > Hardware.

c. Choose SCSI controller 0.

d. From the Change Type drop-down list, verify that the SCSI Controller Type is set to VMware Paravirtual. If this is not the case, choose VMware Paravirtual.

e. Click OK.

f. Power up the vWAAS, with WAAS Version 6.1.x or later.

For more information on setting the SCSI Controller Type and on the vWAAS VM installation procedure, see st of vWAAS image files, see the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.

Note For a vCM-100 model used with the RHEL KVM or KVM on CentOS hypervisor, with the default memory size of 2 GB:

When you upgrade to WAAS Version 6.2.3x from an earlier version, or downgrade from WAAS Version 6.2.3x to an earlier version, and use either the restore factory-default command or the restore factory-default preserve basic-config command, the vCM-100 may not come up due to GUID Partition Table (GPT) boot order errors.

CAUTION: The restore factory-default command erases user-specified configuration information stored in the flash image, including the starting configuration of the device, and also removes data from the disk, user-defined partitions, and the entire Central Manager database.

To resolve this situation, follow these steps:

1. Power down the vWAAS using the virsh destroy vmname command or the virt manager.

2. Power up the vWAAS using the virsh start vmname command or the virt manager.

This upgrade/downgrade scenario does not occur for vCM-100 models whose memory size is upgraded to 4 GB.

Cisco WAAS, ISR-WAAS and IOS-XE Interoperability

Table 3 shows Cisco WAAS, ISR-WAAS and IOS-XE Interoperability.

Table 3 Cisco WAAS, ISR-WAAS and IOS-XE Interoperability

Operating Guidelines for Cisco WAAS, ISR-WAAS and IOS-XE Interoperability

• ISR4321-B/K9 is not supported for ISR-WAAS installation.
• Activating ISR-WAAS after formatting the Cisco 4000 Series ISR-router bootflash:

After you format the Cisco 4000 Series ISR-router bootflash, you must reload the router to ensure a successful activation of ISR-WAAS. If you do not reload the ISR router after formatting the bootflash, you will be unable to activate ISR-WAAS. For more information on formatting the Cisco 4000 Series ISR router bootflash, see the Configuration Guide for Integrated AppNav/AppNav-XE and ISR-WAAS on Cisco 4000 Series ISRs.

• For ISR-4321 with IOS-XE, used with WAAS Version 6.2.3x:

You must complete a new OVA deployment of WAAS version 6.2.3x for this configuration to work successfully. This configuration will not automatically work after an upgrade to WAAS Version 6.2.3x from WAAS Version 5.x or 6.x.

• Using the intrusion detection and prevention system Snort with ISR-WAAS and ISR-4000 Series, with a hard disk less than or equal to 200 GB:

To ensure a successful WAAS installation of ISR-WAAS and Snort on an ISR router, you must install ISR-WAAS before you install Snort. If you do not follow this installation order, ISR-WAAS will not install and a disk error will be displayed.

• VRF restriction for VirtualPortGroup31 on ISR-WAAS:

When you configure ISR-WAAS with EZConfig—VirtualPortGroup31, the WAAS service/router interface, is automatically created, and you can then add or modify specific parameters for it.

Note Do not add Virtual Routing and Forwarding (VRF) to VirtualPortGroup31. VRF will cause VirtualPortGroup31 to lose its IP address and will disable AppNav. To re-establish these, you must uninstall and reinstall ISR-WAAS without VRF.

For more information on VirtualPortGroup31, see the Configuration Guide for Integrated AppNav/AppNav-XE and ISR-WAAS on Cisco 4000 Series ISRs.

Cisco AppNav and AppNav-XE Interoperability

Consider the following guidelines when deploying the Cisco AppNav solution, for AppNav and AppNav-XE.

• All Cisco WAAS nodes in an AppNav deployment must be running Cisco WAAS version 5.0 or later.
• Cisco WAAS Express devices cannot operate as Cisco WAAS nodes in an AppNav deployment.
• All AppNav devices in a single cluster must be of the same exact type. This includes IOS-XE devices, down to memory and ESP configuration.

– All Cisco ASRs (Aggregation Services Routers) in an AppNav Controller Group need to be the same model, with the same ESP (Embedded Services Processor) rate (in Gbps). For example, in an AppNav Controller Group, you cannot have one ASR-1006 40-Gbps ESP and one ASR-1006 100-Gbps ESP.

– The same principle is true for using the ISR (Integrated Services Router) 4000 series. You cannot have an ISR-4451 and an ISR-4321 in the same AppNav-XE cluster.

• If you are connecting an AppNav Controller (ANC) to a Catalyst 6500 series switch and you have configured the ANC to use the Web Cache Communication Protocol (WCCP) with the L2 redirect method, do not deploy the ANC on the same subnet as the client computers. This configuration can cause packet loss due to a limitation of the Catalyst 6500 series switch.

Note Although an IOS router can have a dot (“.”) in the hostname, this special character is not allowed in a WAAS device hostname. If you try to import an AppNav-XE device that has a dot in the hostname, the import will fail and the following error message is displayed: Registration failed for the device devicename ConstraintException; Invalid AppNav-XE name: X.X since name includes invalid character ‘.’.

Cisco WAAS, ASR/CSR, and IOS-XE Interoperability

Table 4 shows Cisco WAAS, ASR/CSR and IOS-XE Interoperability.

Table 4 Cisco WAAS, ASR/CSR, and IOS-XE Interoperability

Cisco WAAS Express Interoperability

Consider the following guideline when using Cisco WAAS Express devices in your Cisco WAAS network:

Note When Cisco WAAS Express is used on the Cisco Integrated Services Router Generation 2 (ISR G2) with the Cisco VPN Internal Service Module (VPN-ISM) or with Group Encrypted Transport (GETVPN) enabled, the WAAS Express does not optimize FTP data.

To ensure that FTP data is optimized when WAAS Express is used with the Cisco ISR G2, use the ISR G2's IOS crypto map software.

• For a Cisco WAAS device running WAAS Version 6.x and a Cisco WAAS Express peer device running Cisco IOS Release 15.6(3)M, 15.6(2)T1 or later, TLS1 is supported, but SSL3 is removed. Before upgrading WAAS Express to one of these IOS releases, configure TLS1 in the WAAS Express Device Group > Peering Service page, and then upgrade the WAAS Express device to the specified IOS release.
• When using a Cisco WAAS device running version 5.x and a Cisco WAAS Express peer device running Cisco IOS Release 15.2(2)T or earlier, connections originating from the Cisco WAAS device and sent to the Cisco WAAS Express peer are passed through instead of being optimized. We recommend upgrading to Cisco WAAS Express in Cisco IOS Release 15.2(3)T or later to take advantage of the latest enhancements.

Note If you are upgrading the WAAS Express devices to IOS 15.3(3)M image, as part of the AppX/K9 (Application Experience) license support in WAAS Express IOS 15.3(3)M images, you need to upgrade the WAAS Central Manager to WAAS v5.3.1 or later, or else the devices will go offline.

Note As listed in “Software Version 5.1.1 Open Caveats,” CSCug16298, “WAAS-X to WAAS 5.1.1 connections will be reset when using HTTP acceleration.” We recommend that you do not use HTTP Application Optimizer (AO) between Cisco WAAS and Cisco WAAS Express unless you are running Cisco IOS Release 15.3(1)T or later.

Table 5 lists the Cisco WAAS, WAAS Express and IOS Interoperability

Table 5 Cisco WAAS, WAAS Express and IOS Interoperability

Note 39xxE series routers do not support WAAS Express.

Traffic Interception Interoperability

This section contains the following topics:

• General Traffic Interception Interoperability
• WCCP Interoperability

General Traffic Interception Interoperability

Cisco WAAS uses the following traffic interception methods: Web Cache Communications Protocol (WCCP), WCCP Version 2, AppNav, Inline, Policy-Based Routing (PBR) and ITD (advanced version of PBR). For WAAS Version 5.5.1 and earlier, WAAS supports WCCP, AppNav, and vPATH.

Consider the following guidelines when configuring traffic interception for Cisco WAAS.

• ISR-WAAS devices support only the AppNav Controller interception method. For more information on AppNav, see Cisco AppNav and AppNav-XE Interoperability.
• For vWAAS in Azure, the supported traffic interception method is PBR (Police-Based Routing); vWAAS in Azure does not support WCCP or AppNav interception methods.
• Pass-through traffic does not benefit from optimization. For example, SSH port 22 has minimal traffic volume, so would not benefit by optimizing TCP flows.
• If you use Microsoft System Center Configuration Manager with Preboot Execution Environment (SCCM/PXE), we recommend the following configurations for the ports that carry SCCM/PXE traffic: port 80, port 443, and port 445:

– port 80—Communicates with the distribution point. Configure for pass-through traffic.

– port 443—Communicates with the distribution point. Configure for pass-through traffic.

– port 445—Used for software package distribution data transfer. Configure for traffic optimization.

Without these configurations you may see the error message “PXE error code 80070056.”

For more information on traffic interception methods, see the “Configuring Traffic Interception” chapter of the Cisco Wide Area Application Services Configuration Guide.

WCCP Interoperability

Central Managers running Version 6.2.3x can manage WAEs running software Versions 5.x and later. However, we recommend that all WAEs in a given WCCP service group be running the same version.

Note All WAEs in a WCCP service group must have the same mask.

To upgrade the WAEs in your WCCP service group, follow these steps:

Step 1 You must disable WCCP redirection on the Cisco IOS router first. To remove the global WCCP configuration, use the following no ip wccp global configuration commands:

Step 2 Perform the Cisco WAAS software upgrade on all WAEs using the Cisco WAAS Central Manager GUI.

Step 3 Verify that all WAEs have been upgraded in the Devices pane of the Central Manager GUI. Choose Devices to view the software version of each WAE.

Step 4 If mask assignment is used for WCCP, ensure that all WAEs in the service group are using the same WCCP mask value.

Step 5 Reenable WCCP redirection on the Cisco IOS routers. To enable WCCP redirection, use the ip wccp global configuration commands:

NTLM Interoperability

Cisco WAAS Version 5.1 and later do not support Windows domain login authentication using the NTLM protocol. Therefore, upgrading from a Cisco WAAS Version earlier than Version 5.1 with the device configured with Windows domain login authentication using the NTLM protocol is blocked. You must change the Windows domain authentication configuration to use the Kerberos protocol before proceeding with the upgrade.

Follow these steps to change from NTLM to Kerberos Windows domain login authentication:

Step 1 Unconfigure Windows domain login authentication. You can do this from the Central manager in the Configure > Security > AAA > Authentication Methods window.

Step 2 Change the Windows domain configuration setting to use the Kerberos protocol. You can do this from Central manager in the Configure > Security > Windows Domain > Domain Settings window. For more information, see “Configuring Windows Domain Server Authentication Settings” in the “Configuring Administrative Login Authentication, Authorization, and Accounting” chapter of the Cisco Wide Area Application Services Configuration Guide.

Step 3 Perform the Windows domain join again from the Central manager in the Configure > Security > Windows Domain > Domain Settings window.

Step 4 Configure Windows domain login authentication from the Central manager in the Configure > Security > AAA > Authentication Methods window.

Step 5 Upgrade your device.

Note If you are upgrading the Central Manager itself from the GUI and the Windows domain login authentication on the Central Manager is configured to use the NTLM protocol, the upgrade fails with the following error logged in the device log:
Error code107: The software update failed due to unknown reason. Please contact Cisco TAC.

To view the device log for the Central Manager, choose the Central Manager device and then choose Admin > Logs > Device Logs. If you see this error, follow the steps above to change the Central Manager device Windows domain login authentication from NTLM to Kerberos.

If you upgrade the Central Manager itself from the CLI and the upgrade fails due to NTLM being configured, you will get an appropriate error message. Once the Central Manager is upgraded to Version 5.1, it can detect and display the reason for any upgrade failures for other devices.

Note Cisco WAAS Version 5.1 and later do not support the Kerberos protocol running with a nonstandard port (other than port 88). Upgrading from a Cisco WAAS Version earlier than 5.1 with the device configured with the Kerberos protocol on a nonstandard port is blocked. You must change the Kerberos server on your network to listen on port 88 and change the Kerberos configuration on the device to use port 88. You can do this from the Central manager in the Configure > Security > Windows Domain > Domain Settings window.

If you are trying to upgrade your device from the CLI and the upgrade fails due to NTLM configuration, then the kerberos_validation.sh script is installed on your device. This script can be used to verify that your network supports the Kerberos protocol before changing from NTLM to Kerberos. This script is not available if you are using the Central Manager to upgrade the device.

To run the script, follow these steps:

Step 1 (Optional) Run the Kerberos validation script command with the -help option to display the usage:

CM# script execute kerberos validation.sh -help

Step 2 Run the Kerberos validation script to verify that your network supports the Kerberos protocol before migrating from NTLM to Kerberos:

Step 3 Change the device Windows domain login authentication from NTLM to Kerberos and upgrade your device, as described in the first procedure in this section.

Citrix ICA Interoperability

Citrix ICA versions 7.x (XenApp and XenDesktop) contain changes affecting the optimization efficiency of WAAS compared to that achieved with Citrix ICA versions 6.x. To maximize the effectiveness of WAAS, the Citrix administrator should configure the following:

• Adaptive Display: Disabled
• Legacy Graphic Mode: Enabled

WAAS Application Accelerators Interoperability with Third-Party Load Balancers

A load balancer is used to balance network and application traffic across a set of servers, The resulting evenly-distributed traffic improves the response rate of network traffic, increases the availability of applications, and minimizes the risk of a single server becoming overloaded.

Table 6 shows the interoperability between WAAS application accelerators and the F5 load balancer. For more information about WAAS load balancing, see the “Configuring Traffic Interception” chapter of the Cisco Wide Area Application Services Configuration Guide and also see the Server Load-Balancing Guide vA5(1.0), Cisco ACE Application Control Engine.

Note WAAS does not currently support Citrix NetScaler load balancer.

Table 6 WAAS Application Accelerators Interoperability with Load Balancers

Cipher Support for SSL Acceleration

No new cipher support is available for SSL Acceleration (Legacy SSL Acceleration) other than those listed in “Configuring SSL Management Services” of the Cisco Wide Area Application Services Configuration Guide. For additional ciphers supported, please see the supported cipher list for SMART-SSL Acceleration.

Upgrade Paths and Considerations for Version 6.2.3x

This section contains the following topics:

• Upgrade Paths for WAAS Version 6.2.3x
• Upgrading from Cisco WAAS Version 5.x and Later to Version 6.2.3x
• Upgrading from Cisco WAAS Version 4.2.x to Version 6.2.3x

Upgrade Paths for WAAS Version 6.2.3x

Upgrading to WAAS Version 6.2.3x is supported from WAAS Version 4.2.x and later. Table 7 shows the upgrade path for each of these versions.

Table 7 Upgrade Paths to WAAS Version 6.2.3x

Note When you upgrade from WAAS Software Version 5.5.x to 6.2.3b, the expired SSL certificates do not get removed automatically and show up in the alarms.

Upgrading from Cisco WAAS Version 5.x and Later to Version 6.2.3x

This section contains the following topics:

• WAAS Version 5.1 and Later: NTLM
• WAAS Version 5.2 and Later: Usernames
• WAAS Version 5.3 and Later: Name and Description Fields
• WAAS Version 6.2.3x: vWAAS
• WAAS Version 6.2.3x: vCM-100 with RHEL KVM or KVM on CentOS

WAAS Version 5.1 and Later: NTLM

Cisco WAAS Version 5.1 and later do not support NTLM Windows domain authentication or use of a nonstandard port (other than port 88) for Kerberos authentication.

• Upgrading from a Cisco WAAS Version earlier than 5.1 is blocked if either of these configurations are detected. You must change these configurations and ensure that your domain controller is configured for Kerberos authentication before proceeding with the upgrade.
• A script is provided to verify that your network supports Kerberos protocol before migrating from NTLM. For more information, see NTLM Interoperability. If no application is using the unsupported configurations on the device, then remove the unsupported configurations to upgrade.

WAAS Version 5.2 and Later: Usernames

Cisco WAAS Version 5.2 and later restrict the characters used in usernames to letters, numbers, period, hyphen, underscore, and @ sign, and a username must start with a letter or number.

Any username not meeting these guidelines is prevented from logging in. Prior to upgrading the Central Manager to Version 5.2 or later, we recommend that you change any such usernames to valid usernames to allow login.

For local users—Change usernames in the Central Manager Admin > AAA > Users page.

For remotely authenticated users—Change usernames on the remote authentication server.

Note Prior to upgrading the Central Manager to Version 5.2 or later, we strongly encourage you to change any usernames that use restricted characters; however if you must maintain existing usernames unchanged, please contact Cisco TAC.

WAAS Version 5.3 and Later: Name and Description Fields

Cisco WAAS Version 5.3 and later restricts the use of characters in the name and description field to alphanumeric characters, periods (.), hyphens (-), underscores (), and blank spaces when you create custom reports. When you upgrade from Cisco WAAS Version 4.x and you have custom reports that have special characters in the name or description field, Cisco WAAS automatically removes the special characters from the report name and description, and logs the modification in the Centralized Management System (CMS) logs.

WAAS Version 6.2.3x: vWAAS

When upgrading vWAAS, do not upgrade more than five vWAAS nodes at the same time on a single UCS box. Upgrading more than five vWAAS nodes at the same time may cause the vWAAS devices to go offline and diskless mode.

WAAS Version 6.2.3x: vCM-100 with RHEL KVM or KVM on CentOS

If you upgrade to WAAS Version 6.2.3x, or downgrade from WAAS Version 6.2.3x to an earlier version, and use a vCM-100 model with the following parameters, the vCM-100 may not come up due to GUID Partition Table (GPT) boot order errors.

• vCM-100 has default memory size of 2 GB
• vCM-100 uses the RHEL KVM or KVM on CentOS hypervisor
• You use either the restore factory-default command or the restore factory-default preserve basic-config command

Note The restore factory-default command erases user-specified configuration information stored in the flash image, including the starting configuration of the device, and also removes data from the disk, user-defined partitions, and the entire Central Manager database.

To resolve this situation, follow these steps:

1. Power down the vWAAS using the virsh destroy vmname command or the virt manager.

2. Power up the vWAAS using the virsh start vmname command or the virt manager.

This upgrade/downgrade scenario does not occur for vCM-100 models whose memory size is upgraded to 4 GB.

Upgrading from Cisco WAAS Version 4.2.x to Version 6.2.3x

When you upgrade from Cisco WAAS Version 4.x, you must reconfigure the custom EPM policy for a device or device group. You must first restore the default policy setting by selecting the Restore default Optimization Policies link for the device group in the Modifying Device Group window and then reconfigure your custom policy rules for the device. For more information on upgrade paths, see Table 7.

Workflow: Upgrading from a Release Version to Version 6.2.3x

To upgrade from a Release Version to Version 6.2.3x, complete the tasks listed in Table 8.

Table 8 Workflow: Upgrading from a Release Version to Version 6.2.3x

Upgrade Part 1: Create a Backup of the Primary WAAS CM Database

This section contains the following topics:

• Prerequisite for Primary WAAS CM Database Backup
• Creating a Primary WAAS CM Database Backup

Prerequisite for Primary WAAS CM Database Backup

Note the following different CMS database backup scenarios, depending on the size of /sw and /swstore:

• If you are upgrading your vCM, vWAAS, ISR-WAAS, or SRE device from an earlier WAAS version to WAAS Version 6.2.3x, and the /sw and /swstore partition size is less than 2GB, you must back up the CMS database before creating a backup of the primary WAAS CM database, following the instructions described in the Caution note.
• For devices using WAAS Version 5.x, the /sw and /swstore partition size is 1GB, so you must back up the CMS database, you must back up the CMS database before creating a backup of the primary WAAS CM database, following the instructions described in the Caution note.
• For devices using WAAS Version 6.x, the /sw and /swstore partition size is 2GB, so you do not need to create a backup of the CMS database before creating a backup of the primary WAAS CM database.

Caution If you are upgrading your WAAS device from an earlier WAAS version to WAAS Version 6.2.3x, and the /sw and /swstore partition size is less than 2 GB, it is crucial that you create a backup of the WAAS CM database and save it to an external file (FTP/SFTP) before you upgrade to WAAS Version 6.2.3x.

The upgrade process on this type of configuration will automatically clear system and data partition, which will erase the WAAS CM database.

After upgrade is complete, restore the saved WAAS CM database to your system.

---

Creating a Primary WAAS CM Database Backup

Before upgrading to WAAS Version 6.2.3x, follow these steps to create a backup of the WAAS CM database:

Step 1 Use Telnet or SSH to access the primary WAAS CM IP address.

Step 2 Create the database backup, using the cms database backup command:

waas-cm# cms database backup

Step 3 The cms database backup command displays the following information:

creating backup file with label ‘backup’

backup file local1/filename filedate.dump is ready. use ‘copy’ command to move the backup file to a remote host.

Step 4 Copy the backup database file to a remote location, using the copy disk command:

waas-cm# copy disk ftp hostname ip-address remotefiledir remotefilename localfilename

Step 5 Verify that the backup file was copied correctly by verifying file size and time stamp.

Upgrade Part 2: Upgrade the Standby WAAS CM

Follow these steps to upgrade the standby WAAS CM, if present in your WAAS system.

Step 1 Use Telnet or SSH to access the standby WAAS CM IP address:

Step 2 Copy the new software image to the standby WAAS CM with the WAAS CLI copy ftp command.

The following example shows the file in the root directory. Provide the correct path on your WAAS system, if different from the root directoy path.

wae# copy ftp install ftpserver / waas-image.bin

Step 3 Reload the standby WAAS CM, using the reload command

Step 4 Verify that the new image is loaded correctly, using the show version command.

Step 5 To confirm connectivity, ping the primary WAAS CM and branch WAE devices.

Step 6 Wait at least five minutes.

Step 7 To ensure that the database has been synchronized, confirm the database last synchronization time, using the show cms info command.

Step 8 From the primary WAAS CM, confirm that the status indicator for the standby WAAS CM is online and green.

Upgrade Part 3: Upgrade the Primary WAAS CM

Perform the following tasks before you upgrade the primary WAAS CM:

• Before upgrading the primary WAAS CM, create a backup copy of the primary WAAS CM database. For more information, see Upgrade Part 1: Create a Backup of the Primary WAAS CM Database.
• If your WAAS system has a standby WAAS CM, you must upgrade the standby WAAS CM before you upgrade the primary WAAS CM. For more information, see Upgrade Part 2: Upgrade the Standby WAAS CM.

Follow these steps to upgrade the primary WAAS CM.

Step 1 Use Telnet or SSH to access the primary WAAS CM IP address:

Step 2 Copy the new software image to the primary WAAS CM, either from the WAAS CM or the CLI.

From the WAAS CM:

a. In the Standby WAAS CM, navigate to Admin > Versioning > Software Update.

b. From the Software Files listing, select the new software version.

c. Click Submit.

From the CLI:

a. Use the copy ftp command.

The following example shows the file in the root directory. Provide the correct path on your WAAS system, if different from the root directoy path.

wae# copy ftp install ftpserver / waas-image.bin

Step 3 Copy the new Version 6.2.3x software image to the primary WAAS CM, using the copy ftp command:

wae# copy ftp install ftpserver / waas-image.bin

Note This example shows the file in the root directory. Provide the correct path on your WAAS system, if different from the root directory path.

Step 4 Reload the primary WAAS CM, using the reload command

Step 5 Verify that the new Version 6.2.3x image is loaded correctly, using the show version command.

Step 6 To confirm connectivity, ping the standby WAAS CM (if present in your WAAS system) and branch WAE devices.

Step 7 Confirm that the CMS services are running, using the show cms info command.

Step 8 Choose Devices > All Devices and verify that all WAE devices are online.

Step 9 Choose Device Groups > AllWAASGroups > Assign Devices and verify that each WAE device is listed with a green check mark.

Upgrade Part 4: Upgrade the Branch WAE Devices

Before you upgrade the branch WAE devices, verify that you have completed the following tasks:

• Created a backup copy of the primary WAAS CM database. For more information, see Upgrade Part 1: Create a Backup of the Primary WAAS CM Database.
• Upgraded the standby WAAS CM, if one is present on your WAAS system. For more information, see Upgrade Part 2: Upgrade the Standby WAAS CM.
• Upgraded the primary WAAS CM. For more information, see Upgrade Part 3: Upgrade the Primary WAAS CM.

Follow these steps to upgrade the branch WAE devices.

Step 1 Access the primary WAAS CM GUI:

https://cm-ip-address:8443

Step 2 Verify that all WAE devices are online (displaying green).

Step 3 Resolve any alarm conditions that may exist.

Step 4 Copy the new software image to the branch WAE, either from the WAAS CM or the CLI.

From the WAAS CM:

a. In the branch WAE, navigate to Admin > Versioning > Software Update.

b. From the Software Files listing, select the new software version.

c. Click Submit.

From the CLI:

a. Use the copy ftp command. You can use either Universal or Accelerator-only images.

The following example shows the file in the root directory. Provide the correct path on your WAAS system, if different from the root directoy path.

wae# copy ftp install ftpserver / waas-image.bin

Step 5 Reload the WAE using the reload command.

Step 6 Verify that the new Version 6.2.3x software image has installed correctly, using the show version command.

Step 7 Verify that the correct licenses are installed, using the show license command.

Step 8 If you have purchased an Enterprise license and have enabled it, proceed to Step 10.

If you have purchased an Enterprise license and have not yet enabled it, perform the following tasks:

a. Clear the Enterprise license, using the clear license transport command.

b. Add the Enterprise license, using the license add enterprise command.

Step 9 Save the changed configuration, using the copy running-config startup-config command.

Step 10 From the primary WAAS CM, choose Devices > branchWAE, to verify that the WAE device is online and has a green status.

Step 11 Verify the following WAE device functionalities:

a. If you are using WCCP for traffic interception, verify that WCCP is working properly, using the show running -config wccp command.

b. (Optional) Confirm that flows are being optimized, using the show statistics connection command.

c. Confirm that the Enterprise license is enabled, using the show license command.

If you have purchased the Enterprise license and it is enabled, proceed to Step 12.

If you have purchased an Enterprise license and have not yet enabled it, perform the following tasks:

1. Clear the Transport license, using the clear license transport command.

2. Add the Enterprise license, using the license add enterprise command.

3. Save the changed configuration, using the copy running-config startup-config command.

Step 12 The branch WAE devices within the active WAAS network are now upgraded to the current WAAS Version 6.2.3x.

Upgrade Part 5: Upgrade the Data Center WAAS Software

Follow these steps to upgrade the data center WAAS software.

Step 1 Access the primary WAAS CM GUI:

https://cm-ip-address:8443

Step 2 Verify that all WAE devices are online (displaying green).

Step 3 Resolve any alarm conditions that may exist.

Step 4 Upgrade each data center WAE (Upgrade Part 6: Upgrade Each Data Center WAE).

Note For deployments using WCCP as the traffic interception method, each data center WAE is automatically removed from the interception path. If your deployment does not use WCCP, use one of the following methods to remove each data center WAE from the interception path during the upgrade process:

For an inline deployment, use the interface InlineGroup slot/grpnumber shutdown global configuration command to bypass traffic on the active inline groups.

For a deployment using serial inline cluster, shut down the interfaces on the intermediate WAE in the cluster, then shut down the interfaces on the optimizing WAE in the cluster.

Upgrade Part 6: Upgrade Each Data Center WAE

Follow these steps to upgrade each data center WAE.

Step 1 Use the following sequence of commands to disable WCCP on the WAE and allow a graceful termination of existing TCP flows that are optimized by WAAS:

a. Disable WCCP with the no wccp tcp-promiscuous service-pair serviceID serviceID global configuration command.

b. Wait until the countdown expires, or use CTL-C to skip the countdown.

c. Verify that WCCP is disabled, using the show wccp status command.

d. Save the changed configuration, using the copy running-config startup-config command.

Step 2 (Optional) Disable WCCP on the intercepting router or switch, using the no ip wccp global configuration command.

Note We recommend this step 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, using the show ip wccp command, if you have used Step 2.

Step 4 Upgrade the data center WAE software:

Step 5 Copy the new software image to the data center WAE, either from the WAAS CM or the CLI.

From the WAAS CM:

a. In the data center WAE, navigate to Admin > Versioning > Software Update.

b. From the Software Files listing, select the new software version.

c. Click Submit.

From the CLI:

a. Use the copy ftp command. You can use either Universal or Accelerator-only images.

The following example shows the file in the root directory. Provide the correct path on your WAAS system, if different from the root directoy path.

wae# copy ftp install ftpserver / waas-image.bin

Step 6 Reload the WAE using the reload command.

Step 7 Verify that the new Version 6.2.3x software image has installed correctly, using the show version command.

Step 8 Verify that WCCP is disabled, using the show wccp status command.

Step 9 Save the changed configuration, using the copy running-config startup-config command.

Step 10 From the primary WAAS CM, choose Devices > branchWAE, to verify that the WAE device is online and has a green status.

Step 11 (Optional) Enable WCCP on all intercepting routers or switches in the list, if you have used Step 2.

a. Telnet to each core router or switch.

b. Enable WCCP, using the ip wccp 61 redirect-list acl-name command and the ip wccp 62 redirect-list acl-name command.

• WCCP Service ID 61—Source IP address. The WCCP Service ID (service group) is applied closest to the LAN interface.
• WCCP Service ID 62—Destination IP address. The WCCP Service ID (service group) is applied closest to the WAN interface.
• You can change the WCCP redirect list as needed by changing the redirect in/out statement.

Step 12 Verify the following WAE device functionalities:

a. Enable WCCP, using the wccp tcp-promiscuous service-pair serviceID serviceID global configuration command. If you are using WCCP single-service, use the wccp tcp-promiscuous serviceID global configuration command.

b. Verify that redirecting router IDs are seen, using the show wccp routers command.

c. Verify that all WAEs in the cluster are seen, using the show wccp clients command.

d. Verify that the packet count to the WAE is increasing and no loops are detected, using the show wccp statistics command.

e. Verify that the buckets assigned for Service Group 61 match those of Service Group 62, and are assigned to the WAE, using the show wccp flows tcp-promiscuous detail command.

f. Verify that flows are being optmized, using the show statistics connection command.

g. If you are using WCCP for traffic interception, verify that WCCP is working properly, using the show running -config wccp command.

Step 13 Each data center WAE within the active WAAS network is now upgraded to the current WAAS Version 6.2.3x.

Upgrade Part 7: WCCP and Migration Processes

For information on the sets of tasks to enable and reconfigure WCCP, and information on configuring accelerators, switches and routers for migration, see the Cisco Wide Area Application Services Upgrade Guide.

Upgrade Part 8: Post-Upgrade Tasks

Perform the following tasks after you have completed the upgrade to WAAS Version 6.2.3x:

• After upgrading a Central Manager, you must clear your browser cache, close the browser, and restart the browser before reconnecting to the Central Manager.
• After upgrading application accelerator WAEs, verify that the proper licenses are installed by using the show license EXEC command. The Transport license is enabled by default. If any of the application accelerators were enabled on the device before the upgrade, you should enable the Enterprise license. Configure any additional licenses as needed by using the license add EXEC command. For more information on licenses, see the “Managing Software Licenses” section in the Cisco Wide Area Application Services Configuration Guide . a;lkdsjhf;laksjf
• After upgrading application accelerator WAEs, verify that the proper application accelerators, policies, and class maps are configured. For more information on configuring accelerators, policies, and class maps, see the “Configuring Application Acceleration” chapter in the Cisco Wide Area Application Services Configuration Guide .
• If you use the setup utility for basic configuration after upgrading to 6.2.3x, WCCP router list 7 is used. Because the setup utility is designed for use on new installations, any existing configuration for WCCP router list 7 is replaced with the new configuration.
• If you have two Central Managers that have secure store enabled and you have switched primary and standby roles between the two Central Managers, before upgrading the Central Managers to Version 6.2.3x, you must reenter all passwords in the primary Central Manager GUI. The passwords that need to be reentered include user passwords. If you do not reenter the passwords, after upgrading to Version 6.2.3x, the Central Manager fails to send configuration updates to WAEs and the standby Central Manager until after the passwords are reentered.
• If you use the setup utility for basic configuration after upgrading to 6.2.3x, WCCP router list 7 is used. Because the setup utility is designed for use on new installations, any existing configuration for WCCP router list 7 is replaced with the new configuration.

Migrating a WAAS CM from an Unsupported to a Supported Platform

If you have a Cisco WAAS Central Manager that is running on a hardware platform that is unsupported in Version 6.1 and later (such as a WAE-274/474/574/674/7341/7371), you are not allowed to upgrade the device to Version 6.1 or later. You must migrate the WAAS CM to a supported platform by following the procedure in this section, which preserves all of the WAAS CM configuration and database information.

Caution Database backup is intended for recovery of the current WAAS CM only. Restoring to a different device will retain the device identity and will not allow you to re-use the current hardware in a different role. If you want to migrate the service to a new device, register the device as a standby WAAS CM first, and then change its role after database synchronization.

---

Follow these steps to migrate a primary WAAS CM from an unsupported platform to a platform that is supported for WAAS Version 6.2.3x:

Step 1 From the primary Central Manager CLI, create a database backup by using the cms database backup EXEC command. Move the backup file to a separate device by using the copy disk ftp command.

Step 2 Display and write down the IP address and netmask of the Central Manager.

Step 3 Shut down all the interfaces on the primary Central Manager.

Step 4 Replace the existing Central Manager device with a new hardware platform that can support Cisco WAAS Version 6.1. Ensure that the new Central Manager device is running the same software version as the old Central Manager.

Step 5 Configure the new Central Manager with the same IP address and netmask as the old Central Manager. You can do this in the setup utility or by using the interface global configuration command.

Step 6 Copy the backup file created in Step 1 from the FTP server to the new Central Manager.

Step 7 Restore the database backup on the new Central Manager by using the cms database restore command. Use option 1 to restore all CLI configurations.

Step 8 Enable the CMS service.

Step 9 Verify that the Central Manager GUI is accessible and all Cisco WAAS devices are shown in an online state in the Devices window.

Step 10 (Optional) If you have a standby Central Manager that is running on unsupported hardware and is registered to the primary Central Manager, deregister the standby Central Manager.

Step 11 Upgrade the primary Central Manager to Cisco WAAS Version 6.2.3x. You can use the Central Manager Software Update window or the copy ftp install command.

Step 12 Verify that the Central Manager GUI is accessible and all Cisco WAAS devices are shown in an online state in the Devices window.

Step 13 (Optional) Register a new standby Central Manager that is running Cisco WAAS Version 5.1.x or later.

Wait for the device to reload, change the Central Manager role to standby, and register the standby Central Manager to the primary Central Manager.

Migrating a Physical Appliance Being Used as a WAAS CM to a vCM

Follow these steps to migrate a physical appliance being used as a primary WAAS CM to a vCM:

Step 1 Introduce vCM as the Standby Central Manager by registering it to the Primary Central Manager.

Step 2 Configure both device and device-group settings through Primary CM and ensure that devices are getting updates. Wait for two to three data feed poll rate so that the Standby CM gets configuration sync from the Primary CM.

Step 3 Ensure that the Primary CM and Standby CM updates are working.

Step 4 Switch over CM roles so that vCM works as Primary CM. For more information, see the “Converting a Standby Central Manager to a Primary Central Manager” section of the Cisco Wide Area Application Services Configuration Guide.

Ensuring a Successful RAID Pair Rebuild

RAID pairs 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 Cisco WAAS from the booted recovery CD-ROM.

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

---

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 command in EXEC mode. When you see that RAID is rebuilding, you must let it complete that rebuild process. This rebuild process may 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 that could indicate a problem:

• The device is offline in the Central Manager GUI.
• CMS cannot be loaded.
• Error messages say that the file system is read-only.
• The syslog contains errors such as “Aborting journal on device md2,” “Journal commit I/O error,” “Journal has aborted,” or “ext3_readdir: bad entry in directory.”
• Other unusual behaviors occur that are related to disk operations or the inability to perform them.

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

Downgrading the WAAS System from Version 6.2.3x to a Previous Version

This section contains the following topics:

• Downgrade Path Considerations
• Downgrade Component and Data Considerations

Downgrade Path Considerations

• Downgrading from 6.2.3x is supported to 6.2.1x, 6.1.1a, 6.1.1, 5.5.7, 5.5.5a, 5.5.5 and 5.5.3. Downgrading directly from 6.x to a version earlier than 5.5.3 is not supported.
• On the Cisco 4451-X Integrated Services Router running ISR-WAAS, downgrading to a version earlier than 5.2.1 is not supported.
• On the UCS E-Series Server Module installed in a Cisco ISR G2 Router and running vWAAS, downgrading to a version earlier than 5.1.1 is not supported. On the UCS E-Series Server Module installed in the Cisco 4451-X Integrated Services Router and running vWAAS, downgrading to a version earlier than 5.2.1 is not supported. On other vWAAS devices you cannot downgrade to a version earlier than 4.3.1.
• On WAVE-294/594//8541 models with solid state drives (SSDs) you cannot downgrade to a version earlier than 5.2.1.
• On WAVE-694 model with solid state drives (SSDs), you cannot downgrade to a version earlier than 5.5.1.
• On vCM-500/vCM-1000, you cannot downgrade to a version earlier than 5.5.1.

Downgrade Component and Data Considerations

• Locked-out user accounts are reset upon a downgrade.
• Any reports and charts that are not supported in the downgrade version are removed from managed and scheduled reports when you downgrade to an earlier version. Any pending reports that were carried forward from an upgrade from a version earlier than 5.0 are maintained.
• When downgrading to a version earlier than 4.4.1, the DRE cache is cleared and the DRE caching mode for all application policies is changed to bidirectional (the only available mode prior to 4.4.1). Before downgrading a WAE, we recommend that you use the Central Manager GUI to change all policies that are using the new Unidirectional or Adaptive caching modes to the Bidirectional caching mode.
• Current BMC (Baseboard Management Controller) settings are erased and restored to factory default settings when you downgrade Cisco WAAS to a version earlier than 4.4.5.
• If you have configured disk cache for ISR-WAAS device, downgraded from 6.2.3x to 5.5.3, and then restore rollback to 6.1.1x, you must reload the disk cache configuration for the new configuration to take effect. If you do not perform a reload after the rollback to 6.2.3x, the new configuration will not take effect, and output from the show disks cache-details command will display the error message "Disk cache has been configured. Please reload for the new configuration to take effect."

Downgrading the WAAS CM from Version 6.2.3x to a Previous Version

This section contains the following topics:

• WAAS CM Downgrade Path Considerations
• WAAS CM Downgrade Procedure Considerations
• Procedure for Downgrading the WAAS CM to a Previous Version

WAAS CM Downgrade Path Considerations

• Downgrading from 6.2.3x WAAS CM directly to a version earlier than Version 5.5.3 is blocked.
• If the 6.2.3x WAAS CM is downgraded to a version earlier than 5.2.1, it can no longer manage AppNav-XE clusters and devices and all related configuration records are removed.
• When downgrading a 6.2.3x WAAS CM to a version earlier than 4.4.1, and secure store is in auto-passphrase mode, the downgrade is blocked. You must switch to user-passphrase mode before you can downgrade to a software version that does not support auto-passphrase mode.

WAAS CM Downgrade Procedure Considerations

• As it applies to your WAAS CM and the current version of your WAAS system, perform the following tasks before a WAAS CM downgrade:

– If you have a standby Central Manager, it must be registered to the primary Central Manager before the downgrade.

– Prior to downgrading the WAAS CM to a version up to 5.2.1, you must remove Backup WNG from the AppNav-XE cluster and verify that the WAAS CM and AppNav-XE device are in sync.

– Before downgrading to a version earlier than 4.4.1, we recommend that you change the following WCCP parameters, if they have been changed from their default values:

——Change service IDs back to their default values of 61 and 62.

——Change the failure detection timeout back to the default value of 30 seconds.

Note Only these WCCP default values are supported in versions prior to 4.4.1; any other values are lost after the downgrade. If a WAE is registered to a Central Manager, it is configured with the default service IDs of 61 and 62 after it is downgraded and comes back online.

• Each of the following WAAS CM downgrade procedures requires a particular task sequence:

– If the WAAS CM is downgraded to a version up to 5.2.1 and if the AppNav-XE cluster has more than 32 WAAS nodes: prior to downgrade, we recommend that you reduce the number of WAAS nodes to a maximum of 32 WAAS nodes.

– When downgrading Cisco WAAS devices, first downgrade application accelerator WAEs, then the standby Central Manager (if you have one), and lastly the primary Central Manager.

• When downgrading an AppNav Controller device to a version earlier than 5.0.1, you must perform the following tasks:

1. Deregister the device from the WAAS CM.

2. Change the device mode to application-accelerator.

3. Downgrade the device.

4. Re-register the device (or, alternatively, you can reregister the device before downgrading).

If you do not deregister the device before downgrading, the device goes offline and the device mode is not set correctly. In that case, use the cms deregister force EXEC command to deregister the device and then reregister it by using the cms enable global configuration command.

Note All Cisco WAAS nodes in an AppNav deployment must be running Cisco WAAS version 5.0 or later.

Procedure for Downgrading the WAAS CM to a Previous Version

To downgrade the Cisco WAAS Central Manager (not required for WAE devices), follow these steps:

Step 1 (Optional) From the Central Manager CLI, create a database backup by using the cms database backup EXEC command. Move the backup file to a separate device by using the copy disk ftp command.

Step 2 Install the downgrade Cisco WAAS software image by using the copy ftp install EXEC command.

Note After downgrading a WAAS CM, you must clear your browser cache, close the browser, and restart the browser before reconnecting to the Central Manager.

Step 3 Reload the device.

Note Downgrading the database may trigger full updates for registered devices. In the WAAS CM GUI, ensure that all previously operational devices come online.

Device Group Default Settings

When you create a device group in WAAS Version 6.2.3x, the Configure > Acceleration > DSCP Marking page is automatically configured for the group, with the default DSCP marking value of copy.

• Using Autoregistration with Port-Channel and Standby Interfaces

Autoregistration is designed to operate on the first network interface and will not work if this interface is part of a port-channel or standby. Do not enable the auto-register global configuration command when the interface is configured as part of a port-channel or standby group.

CIFS Support of FAT32 File Servers

The CIFS accelerator does not support file servers that use the FAT32 file system. You can use the policy rules to exclude from acceleration any file servers that use the FAT32 file system.

Using the HTTP Accelerator with the Cisco ASR 1000 Series Router and WCCP

When using the Cisco ASR 1000 Series router and WCCP to redirect traffic to a WAE that is using WCCP GRE return as the egress method and the HTTP accelerator is enabled, there may be an issue with HTTP slowness due to the way the ASR router handles proxied HTTP connections (see CSCtj41045). To work around this issue, on the ASR router, create a web cache service in the same VRF as that of the 61/62 service by using the following command: ip wccp [vrf vrf-name ] web-cache

• Disabling WCCP from the Central Manager

If you use the Central Manager to disable WCCP on a Cisco WAAS device, the Central Manager immediately shuts down WCCP and closes any existing connections, ignoring the setting configured by the wccp shutdown max-wait global configuration command (however, it warns you). If you want to gracefully shut down WCCP connections, use the no enable WCCP configuration command on the Cisco WAAS device.

• Changing Device Mode To or From Central Manager Mode

If you change the device mode to or from Central Manager mode, the DRE cache is erased.

• TACACS+ Authentication and Default User Roles

If you are using TACACS+ authentication, we recommend that you do not assign any roles to the default user ID, which has no roles assigned by default. If you assign any roles to the default user, external users that are authenticated by TACACS+ and who do not have the waas_rbac_groups attribute defined in TACACS+ (meaning they are not assigned to any group) can gain access to all the roles that are assigned to the default user.

• Internet Explorer Certificate Request

If you use Internet Explorer to access the Central Manager GUI Version 4.3.1 or later and Internet Explorer has personal certificates installed, the browser prompts you to choose a certificate from the list of those installed in the personal certificate store. The certificate request occurs to support Cisco WAAS Express registration and is ignored by Internet Explorer if no personal certificates are installed. Click OK or Cancel in the certificate dialog to continue to the Central Manager login page. To avoid this prompt, remove the installed personal certificates or use a different browser.

• Default Settings with Mixed Versions

If a Central Manager is managing Cisco WAAS devices that have different versions, it is possible that a feature could have different default settings in those different versions. If you use the Central Manager to apply the default setting for a feature to mixed devices in a device group, the default for the Central Manager version is applied to all devices in the group.

Cisco WAAS Software Version 6.2.3e Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3e.

Cisco WAAS Software Version 6.2.3e Open Caveats

The following caveats are open in Software Version 6.2.3e. Note that there might be additional open caveats from previous releases that are applicable to this release, unless they are specifically listed as resolved.

Cisco WAAS Software Version 6.2.3d Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3d.

Cisco WAAS Software Version 6.2.3d Open Caveats

The following caveats are open in Software Version 6.2.3d. Note that there might be additional open caveats from previous releases that are applicable to this release, unless they are specifically listed as resolved.

Cisco WAAS Software Version 6.2.3c Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3c.

Cisco WAAS Software Version 6.2.3c Open Caveats

The following caveats are open in Software Version 6.2.3c. Note that there might be additional open caveats from previous releases that are applicable to this release, unless they are specifically listed as resolved.

Cisco WAAS Software Version 6.2.3b Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3b.

Cisco WAAS Software Version 6.2.3b Open Caveats

The following caveats are open in Software Version 6.2.3b. Note that there might be additional open caveats from previous releases that are applicable to this release, unless they are specifically listed as resolved.

Cisco WAAS Software Version 6.2.3a Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3a.

Cisco WAAS Software Version 6.2.3a Open Caveats

The following caveats are open in Software Version 6.2.3a. Note that there might be additional open caveats from previous releases that are applicable to this release, unless they are specifically listed as resolved.

Cisco WAAS Software Version 6.2.3 Resolved Caveats

The following caveats, impacting earlier software versions of WAAS, were resolved in Software Version 6.2.3.

Cisco WAAS Software Version 6.2.3 Open Caveats

The following caveats are open in Software Version 6.2.3.

Cisco WAAS Software Version 6.2.3 Command Changes

This section lists the new and modified commands in Cisco WAAS Software Version 6.2.3.

Table 9 lists the commands and options that have been added or changed in Cisco WAAS Software Version 6.2.3.

Using Previous Client Code