Cisco Wide Area Application Services Upgrade Guide

Published: November 18, 2010

Software Versions 4.2 and 4.3

This document describes how to upgrade Cisco Wide Area Application Services (WAAS) from software release 4.0 or 4.1 to 4.2.x or 4.3.x. This document also describes how to migrate an existing WAAS 4.0.x legacy Common Internet File System (CIFS) infrastructure to the CIFS application accelerator introduced in WAAS 4.1.

Information About Upgrading to Version 4.2 or 4.3

WAAS Versions and Upgrade Path

Upgrading to release 4.2.x or 4.3.x is supported from certain older releases only. If you have a WAAS device that is running a release from which upgrading directly to release 4.2.x or 4.3.x is not supported, first upgrade the device to the next highest supported intermediate release, and then upgrade to the desired 4.2.x or 4.3.x release.

Table 1-1 shows the upgrade path for upgrading a WAAS device to release 4.2.x or 4.3.x.

Note To upgrade the WAAS network to WAAS 4.2.x or 4.3.x, the Central Manager must be at an equal or later software version than the other WAE devices in the network.

Note If you are upgrading from version 4.0.x, and you are using legacy mode WAFS, you must also migrate all devices from legacy mode WAFS to the transparent CIFS accelerator, because legacy mode WAFS is not supported in version 4.2 and later. For information on CIFS migration, see the "Migrating from CIFS Legacy Mode to CIFS Accelerator Mode" section.

Deprecated Features

With the introduction of release 4.2, the following features have been deprecated and are no longer supported:

•Legacy mode WAFS—This mode still operates but is not supported and will be removed in a future version. If you enable legacy mode WAFS, an alarm is raised on the Central Manager and you are alerted in all Central Manager GUI pages and the CLI if you configure any legacy WAFS settings. Legacy WAFS users should migrate to the transparent CIFS accelerator.

•Legacy mode print services—This mode still operates but is not supported and will be removed in a future version. If you enable legacy print services, an alarm is raised on the Central Manager and you are alerted in all Central Manager GUI pages and the CLI if you configure any legacy print services settings. Legacy print services users should migrate to the Windows Print accelerator.

•WAE-511 and WAE-611 platforms—These WAE models are no longer supported.

Additionally, in release 4.1, the following features were deprecated and are no longer supported:

•WAFS File Blocking—The file-blocking option allows an administrator to define one or more file-blocking directives that prevent users from opening, creating, or copying files that match a defined filename pattern.

Cisco RAID Controller Firmware Upgrade and Validation

Before upgrading the software, you must upgrade the WAE firmware to avoid possible firmware related issues on WAE-674, WAE-7341, and WAE-7371 devices. We recommend using Firmware version L4_15418 or later.

The symptoms of firmware issues are as follows:

•Syslog output contains several instances of the following message:

WAAS-SYS-3-900000: sd 0:0:0:0: rejecting I/O to offline device."

•A sysreport and running-config cannot be generated and copied to /local/local1.

Both of the above symptoms are an indication of the file system becoming read only during traffic flow.

•An increasing number of pending connections appear in the output of the show statistics tfo command, indicating that new connections cannot be optimized. You can use this command to proactively check the functionality of the system.

To determine the RAID controller firmware version on a device, run the show disks tech-support EXEC command. Look for the Firmware line, where the version number is shown at the end in parentheses, as follows:

Firmware : 5.2-0 (15418)

The version number must be 15418 or higher.

Instructions for applying and validating the firmware update are posted on cisco.com together with the firmware and are named L4_15418_FIRMWARE.pdf.

WAAS Software Upgrade Guidelines

Observe the following guidelines before you upgrade the software:

•Make sure the IOS version on the router/switch has been scrubbed for WCCP issues for your specific platform. This needs to be done only on routers/switches participating in transparent redirection and is not applicable to PBR or inline deployments. If this was not done and there is a current active WAAS network, disable WCCP in the routers/switches in the data center and all branches before the software upgrade to 4.2.x or 4.3.x.

•Perform the migration of CIFS legacy mode to CIFS accelerator mode in a separate change window from the WAAS software version upgrade.

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. And if you are downgrading a 4.2.1 WAE, its WCCP source IP mask will not be changed. By not changing the mask during 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.

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.

Upgrade Methods

The following three methods can be used to perform the WAAS upgrade and transfer the new software image onto the WAE devices in the WAAS network:

Beginning with version 4.2.1, two different WAAS software images are available, as follows:

•Universal—Includes Central Manager and Application Accelerator functionality. You can use this type of software file to upgrade either a Central Manager or an Application Accelerator device but this software file is significantly larger, so for Application Accelerator devices we recommend using the Accelerator only image.

•Accelerator only—Includes Application Accelerator functionality only. You can use this type of software file to upgrade only an Application Accelerator device.

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

Additionally, beginning with version 4.2.3, 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.

Upgrade Sequence

To upgrade a WAAS network to WAAS 4.2.x or 4.3.x, the software version installed on the Central Manager (CM) must be equal to or later than the version installed on the other WAE network devices. For this reason, you must upgrade the Central Managers before you upgrade the rest of the WAE devices.

The CMs are updated with the new WAAS software version 4.2.x or 4.3.x. The Secondary CM was upgraded first followed by the Primary CM.

Upgrading the Branch WAAS Software

This section describes how to upgrade each WAAS branch WAE to version 4.2.x or 4.3.x.

Note After an upgrade from software version 4.0.x to 4.2.x or 4.3.x, all branch WAE devices continue to run with legacy mode CIFS until they are converted to CIFS accelerator mode. This does not apply if you are upgrading from version 4.1.x and already using the CIFS accelerator mode.

Preparing to Upgrade the Branch WAE

We recommend that you check the health of the WAE devices before upgrading the branch WAE devices.

Procedure

Step 1 Access the CM GUI.

https://cm_ip_address:8443

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

Step 3 Address any alarm conditions that may exist.

Upgrading the Branch WAE Software

This procedure shows how to upgrade the branch WAE software.

Procedure

Step 1 Open a console or telnet session to the branch WAE.

Step 2 Copy the software image to the WAE.

copy ftp install ftpserver / waas-image.bin

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 3 Reload the WAE.

reload

Step 4 Verify that the image installed correctly.

show version

Step 5 Verify that the correct licenses are installed.

show license

If an Enterprise license has been purchased and not enabled, go to Steps 6 and 7. Otherwise, go to Step 8.

Step 6 (Optional) Clear the Transport license.

clear license Transport

Step 7 (Optional) Add the Enterprise license.

license add Enterprise

Step 8 Save the configuration.

copy running-config startup-config

Step 9 From the WAAS CM GUI, choose My WAN > Devices > branchWAE and verify that the WAE is online and has a green device status.

Step 10 (Optional) If you are using CIFS legacy mode, from the WAAS CM GUI, verify that CIFS legacy mode is still enabled as follows:

a. Choose My WAN > Devices > branchWAE > Configure > Legacy Services > WAFS Edge Configuration and make sure that the Enable Edge Services check box is still checked. If you were also running core services in the branch, confirm that it is also enabled.

a. Assuming that WCCP is used for the traffic interception method, verify the WCCP is functioning properly.

show run | include wccp

b. (Optional) Confirm that a port 4050 tunnel exists and flows are being optimized (only if using CIFS legacy mode).

show statistics connections

c. Confirm that the Enterprise license is enabled.

show license

If the Enterprise license is not enabled, proceed with Steps d through f.

d. Clear the Transport license.

clear license Transport

e. Add the Enterprise license.

license add Enterprise

f. Save the changed configuration.

copy running-config startup-config

Checkpoint

All the branch WAE devices within the active WAAS network are upgraded to release 4.2.x or 4.3.x. If any branch WAEs were running in CIFS legacy mode, they are still running in that mode.

Upgrading the Data Center WAAS Software

This section describes how to prepare for and upgrade the data center WAAS Software. The data center WAE devices will be upgraded to 4.2.x or 4.3.x but may continue running CIFS legacy mode if you are upgrading from version 4.0.x. The conversion to CIFS accelerator mode is done in a later step depending on the chosen upgrade path. For information about the options to upgrade to the CIFS Accelerator, see the "Migrating from CIFS Legacy Mode to CIFS Accelerator Mode" section.

Preparing to Upgrade Data Center WAAS Software

This procedure shows how to prepare for upgrading the data center WAE devices.

Procedure

Step 1 Access the primary Central Manager GUI.

https://cm_ip_address:8443

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

Step 3 Address any alarm conditions that may exist.

Upgrading the Data Center WAE

This procedure shows how to upgrade the data center WAE software.

Note For a graceful termination of existing TCP flows optimized by WAAS, we recommend that you disable WCCP on the WAE first, as described in Step 1 of this procedure. Then wait until the graceful timer counts down, during which period no new connections are redirected to the WAE and the existing connections are allowed to gracefully terminate. Upon completion of the countdown timer, all existing connections are terminated.

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.

Procedure

Step 1 Disable WCCP on the WAE as follows to allow a graceful termination of existing TCP flows that are optimized by WAAS:

Step 2 (Optional) Disable WCCP on the intercepting router/switch. This step is recommended only if the IOS version on the router/switch has not been scrubbed for WCCP issues for your specific platform.

config t

no ip wccp 61

no ip wccp 62

exit

Step 3 (Optional) Verify that WCCP is disabled. This step is needed only if you disabled WCCP in Step 2.

show ip wccp

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.

copy ftp install ftpserver / waas-image.bin

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.

c. Reload the WAE.

reload

d. Verify that the image installed correctly.

show version

e. Confirm that WCCP is disabled.

show wccp status

f. Save the changed configuration.

copy running-config startup-config

Step 5 From the WAAS CM GUI, choose My WAN > Devices > dataCenterWAE and verify that the WAE is online and has a green device status.

Step 6 (Optional) If you are using CIFS legacy mode, from the WAAS CM GUI, verify that CIFS legacy mode is still enabled as follows:

a. Choose My WAN > Devices > dataCenterWAE > Configure > Legacy Services > WAFS Core Configuration and make sure that the Enable Core Server check box is still checked. If you were also running the edge service in the data center, confirm that it is also enabled.

d. Confirm that tunnels on port 4050 exist and that flows are being optimized (only if using CIFS legacy mode).

show statistics connections

e. Confirm that the packet count to the WAE is increasing and no loops are detected.

show wccp gre

f. Verify that the buckets assigned for Service Group 61 match those of Service Group 62 and are assigned to the WAE.

show wccp flows tcp-promiscuous detail

g. Confirm that other flows are being optimized.

show statistics connections

Checkpoint

All WAE devices in the data center are upgraded to release 4.2.x or 4.3.x and have WCCP enabled. If any data center WAEs were running in CIFS legacy mode, they are still running in that mode and CIFS traffic is optimized according to the defined connectivity directives.

Migrating from CIFS Legacy Mode to CIFS Accelerator Mode

This section describes how to migrate from CIFS legacy mode to CIFS accelerator mode. If you are upgrading from software version 4.1.x to 4.2.x or 4.3.x, you may have previously migrated to CIFS accelerator mode. If this is the case, you can skip this section.

Note If you are upgrading from version 4.0.x, and you are using legacy mode WAFS, you must also migrate all devices from legacy mode WAFS to the transparent CIFS accelerator as soon as possible, because legacy mode WAFS is not supported in version 4.2 and later, though it still operates. For information on CIFS migration, see the "Migrating from CIFS Legacy Mode to CIFS Accelerator Mode" section.

Note The CIFS cache is not lost during migration from CIFS legacy mode to CIFS accelerator mode. Disk allocation for CIFS in releases 4.2 and 4.3 also remains similar to its allocation in 4.0 and 4.1.

The two methods for migrating from CIFS legacy mode to CIFS accelerator mode are as follows:

•Disruptive Migration—Enables the CIFS accelerator at the time of upgrade. CIFS legacy mode must first be disabled, at which time the CIFS accelerator can be enabled. This method is disruptive and affects CIFS optimized traffic between the WAE devices on the branch and data center sides until all the sites have the CIFS accelerator enabled. It can be applied to any existing WAAS 4.0.x deployment. This method requires little preplanning, but end users do experience short WAAS and WAAS files service outages; however, it has the advantage of a relatively quick and straightforward execution.

•Graceful Migration—Allows CIFS legacy mode to continue functioning while migrating to the CIFS accelerator. This method is non-disruptive and allows migration without impacting traffic between the WAE devices on the branch or data center sides as the sites are migrated to the CIFS accelerator. This method requires preplanning and systematic execution over a significant period of time, but it has the advantage of nonstop operation of WAAS and WAAS file services.

Note CIFS legacy mode is deprecated and not supported in version 4.2 and later. If you are upgrading directly from version 4.0.x to 4.2 or 4.3, we recommend using the disruptive migration method instead.

Note Auto-discovery differs between the CIFS legacy and CIFS accelerator modes. Legacy mode uses CIFS auto-discovery, which is based on selection of the "best" Core device from the configured Cores for each Edge, whereas CIFS accelerator mode uses standard WAAS auto-discovery, which is based on routing and interception. You must verify that the network and the interception are configured properly and an existing stable CIFS environment exists before the migration. The differences between the auto-discovery mechanisms may lead to different Core selections in the accelerator and legacy modes.

Performing a Disruptive Migration

This procedure shows how to perform a disruptive migration from CIFS legacy mode to CIFS accelerator mode. It is the simplest and easiest method to perform and is recommended if you choose not to use the graceful migration procedure. During the migration, CIFS connections are optimized with TFO/DRE but they are not CIFS accelerated until the WAE devices have been upgraded to release 4.2.x or 4.3.x with CIFS accelerator enabled. Existing legacy CIFS connections are closed during the upgrade and the migration. Additionally, it requires several reboots on each WAE device.

Note You can also disable the edge service through device groups depending upon the individual network configurations. By default, all WAE devices should be members of the AllDevicesGroup, which can be used to remove edge services.

Note Check marks should now be beside TFO, DRE, Persistent Compression, and CIFS Accelerator. The following Accelerator check boxes should be unchecked (unless the appropriate licenses have been installed): Video, MAPI, NFS, HTTP, SSL, and EPM.

Note You can also enable the CIFS accelerator through device groups depending upon the individual network configurations. By default, all WAE devices should be members of the AllDevicesGroup, which can be used to enable CIFS accelerator.

e. Reload each affected WAE.

reload

Note You can initiate a reload though the CM either individually or through the Device Groups to which the WAE devices belong. If the WAE devices are divided into Device Groups, by default, all the devices are members of the AllDevicesGroup, which you can use to reload all the group devices.

Step 5 Verify proper WAE functionality as follows:

a. Confirm that the redirecting intercepting router IDs are seen.

show wccp routers

b. Confirm that all WAE devices in the cluster are seen.

show wccp wide-area-engine

c. Confirm that the packet count to the WAE is increasing and no loops are detected.

show wccp gre

d. Verify that the buckets assigned for Service Group 61 match those of Service Group 62 and are assigned to the WAE.

show wccp flows tcp-promiscuous detail

e. Verify that only the CIFS accelerator is enabled.

show accelerators

f. Confirm that other flows are optimized and you see "C" for CIFS optimizations applied (seen only if CIFS traffic is present).

show stat connections

Performing a Graceful Migration

This section describes how to perform a graceful migration from CIFS legacy mode to CIFS accelerator mode. It requires multiple data center WAE devices where half the devices can handle the full traffic load. This migration method might require adding new WAE devices in the data center.

Note CIFS legacy mode is deprecated and not supported in version 4.2 and later. If you are upgrading directly from version 4.0.x to 4.2 or 4.3, we recommend using the disruptive migration method instead. (See the "Performing a Disruptive Migration" section.)

•Do not register the new devices with the Central Manager at this time.

Procedure

Step 1 Install the device, burn-in, and specify the basic configuration as follows:

a. Cable, apply power, and burn in for 48 hours.

b. Open a console into the WAE.

c. Configure all network related settings.

d. Test network connectivity.

e. Ping the default gateway.

f. Ping the Primary CM IP address.

g. Ping the Secondary CM IP address (if present).

Step 2 Upgrade the WAAS software as follows:

a. Copy the software image to the device.

copy ftp install ftpserver / waas-image.bin

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.

b. Reload the device.

reload

c. Verify that the software is installed correctly by checking the version number of the installed software.

show version

d. Confirm that WCCP is disabled.

config

no wccp version 2

exit

e. Configure other settings as needed.

f. Save changes to the configuration.

copy running-config startup-config

Checkpoint

At this point, you should have the new WAE installed with updated firmware and the desired WAAS software release 4.2.x or 4.3.x installed with network connectivity. WCCP is not yet configured and this device is not yet registered with the CM.

Enabling/Disabling WCCP on WAE Devices in a Cluster

This section describes the recommended practice of enabling or disabling WCCP on WAE devices in a cluster.

When enabling WCCP on WAE devices in a cluster, first enable WCCP on the WAEs in the cluster, followed by enabling WCCP on the intercepting routers/switches, provided that you have validated the IOS version with a bug scrub for WCCP related issues for your specific platform.

To disable WCCP, we recommend that you disable WCCP on the intercepting routers/switches first and wait for a graceful shut down to allow existing TCP connections to expire before disabling WCCP on the WAE devices. If a scrub of IOS has been performed, you can proceed with upgrading the WAE devices without disabling WCCP.

The following ACL template is recommended while running WCCP (IOS version and hardware platform permitting). The template must be altered to suit your environment.

•Although WCCP has been removed from the WAE devices at the data center with CIFS legacy mode configured, CIFS continues to work. The connection between the Edge WAE devices and the Core WAE devices in CIFS legacy mode is established through a point-to-point connection that does not involve WCCP. This point-to-point connection is set up during the configuration of connectivity directives.

Step 5 On the branch WAE devices, check and verify that the CIFS legacy mode is operating and verify that a port 4050 tunnel exists to the Core WAE that is still running CIFS legacy mode.

show statistic connection

Checkpoint

At this point in the process, you now have two sets of WAE devices in the data center:

•One set is running CIFS legacy mode with WCCP disabled but is still functioning as a Core WAE cluster for CIFS legacy mode.

•The second set has WCCP and the CIFS accelerator enabled and is optimizing all other applications.

CIFS is optimized one way only on connections initiated at the branches to the data center. These connections rely on the configured CIFS connectivity directives. Because WCCP is enabled on the branches only and not at the data center, at the branch site, TCP traffic is redirected to the WAE where the CIFS port 4050 point-to-point tunnel is used to optimize CIFS traffic depending upon the configured connectivity directives.

For connections initiated at the data center, because WCCP is enabled only on the WAE devices running CIFS accelerator mode, CIFS is not optimized unless the paired site is also running the CIFS accelerator.

This procedure shows how to migrate branch WAE devices from CIFS legacy mode to CIFS accelerator mode. Using the Central Manager, you migrate selected sites to the CIFS accelerator by removing the checkmark from the WAFS Edge Configuration page (and also, if configured, from the WAFS Core Configuration page) on the individual branch WAE devices. Then the CIFS accelerator is enabled.

The migration of sites continues until all the branch sites have been successfully migrated to the CIFS accelerator and no branch sites or devices exist with CIFS legacy mode enabled.

Note You can also disable features through device groups depending on how your WAAS network is designed. The ability to disable device features either individually or as a group allows you to migrate certain sites to CIFS accelerator while other sites continue to optimize CIFS using the legacy mode.

Note Check marks should now be beside TFO, DRE, Persistent Compression, and CIFS Accelerator. The following Accelerator check boxes should be unchecked (unless the appropriate licenses have been installed): Video, MAPI, NFS, HTTP, SSL, and EPM.

Note You can also enable features through device groups depending on how your WAAS network is designed. The ability to enable device features either individually or as a group allows you to migrate certain sites to CIFS accelerator while other sites continue to optimize CIFS using the legacy mode.

e. Reload the device.

reload

Caution Reload is a disruptive process. Any existing connections through the WAE are terminated. When the WAE returns to an online state, new connections are optimized but existing connections established during the reload continue unoptimized until the connection is reestablished.

Step 5 Verify device functionality as follows:

a. Verify that only the CIFS accelerator is enabled.

show accelerators

b. Verify that the connections are being optimized.

show statistic connection

c. Confirm that the packet count to the WAE is increasing and no loops are detected.

show wccp gre

d. Confirm that redirecting intercepting router IDs are seen.

show wccp routers

e. Confirm that all the WAE devices in the cluster are seen.

show wccp wide-area-engine

f. Verify that the buckets assigned for Service Group 61 match those of Service Group 62 and are assigned to the WAE.

show wccp flows tcp-promiscuous detail

g. Confirm that the other flows are being optimized.

show statistic connections

Checkpoint

At this point, you should have all WAE devices running the CIFS accelerator except for half of the data center WAE devices.

Removing CIFS Legacy Configurations from Data Center WAE Devices

This procedure shows how to remove CIFS legacy configurations from data center WAE devices and enable both CIFS accelerator and WCCP so that the devices can rejoin as members of the CIFS accelerator farm.

Prerequisites

Confirm that you have migrated all the branch sites to the CIFS accelerator and that no branch device on the network is running CIFS legacy mode.

Note Check marks should now be beside TFO, DRE, Persistent Compression, and CIFS Accelerator. The following Accelerator check boxes should be unchecked (unless the appropriate licenses have been installed): Video, MAPI, NFS, HTTP, SSL, and EPM.

e. Reload the device.

reload

Step 5 Confirm that connections are being optimized.

show statistic connection

Checkpoint

All WAE devices are running the CIFS accelerator and none are running in CIFS legacy mode.

Additional Information—CM Downgrade and Database Rollback

This section describes how to create a backup of the CM database, which you must do both before and after an upgrade, and how to roll back to a previous version of the database should you encounter a problem during the upgrade.

This section describes the methods that you can use for CIFS validity testing, which includes manual procedures and automation tools.

Guidelines and Restrictions

Use the following guidelines when performing CIFS 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 testing or creating 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.

To display overall CIFS accelerator statistics, use the show statistics accelerator cifs detail command as follows:

WAE674# show statistics accelerator cifs detail

CIFS:

Global Statistics

-----------------

Time Accelerator was started: Sun May 17

06:11:00 2009

Time Statistics were Last Reset/Cleared: Sun May 17

06:11:00 2009

Total Handled Connections: 10565

Total Optimized Connections: 0

Total Connections Handed-off with Compression Policies Unchanged: 0

Total Dropped Connections: 0

Current Active Connections: 0

Current Pending Connections: 0

Maximum Active Connections: 5

Number of local reply generating requests: 13266

Number of remote reply generating requests: 13266

The Average time to generate a local reply (msec): 0

Average time to receive remote reply (ms): 1

. . .

Rolling Back from CIFS Accelerator Mode to CIFS Legacy Mode

This procedure shows how to roll back from CIFS accelerator mode to CIFS legacy mode if a failure occurs when upgrading to CIFS accelerator mode or CIFS is not optimized. CIFS accelerator mode can be rolled back to CIFS legacy mode by reenabling the CIFS Edge Services on the WAE devices and recreating the connectivity directive for the particular branch.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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. (1110R)

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.