Technical Implementation Guide
Cisco® Wide Area Application Services (WAAS) Version 4.0 is a major release that contains functions that exist in Cisco Wide Area File Services (WAFS) Software Version 3.0. Cisco WAAS Version 4 and WAFS Version 3 are not interoperable. This white paper describes the process for a smooth migration from a WAFS network into a WAAS network. The procedure preserves all Cisco WAFS device configuration and transforms it into a Cisco WAAS configuration.
MIGRATION REQUIREMENTS
• Supported hardware platforms-The following platforms are supported with Cisco WAAS Version 4: Cisco FE 511 File Engine, Cisco 511 Content Engine, and Cisco WAE-511, WAE-512, WAE- 611, WAE-612, and WAE-7326 Wide Area Application Engines. In Cisco WAFS deployments that use other hardware, you must refresh the hardware with a compliant model. Migration directly from Cisco WAFS Version 2.5.X to Cisco WAAS Version 4.0 is not supported, and router-integrated network modules are not supported in the first release of Cisco WAAS Version 4.0.
• Supported software platforms-You can complete the migration to Cisco WAAS Version 4.0 only from WAEs that are running Cisco WAFS Version 3.0.1 or newer. Previous versions of Cisco WAFS Software are not supported for this migration.
• Feature changes-Please note the following feature changes before beginning the migration:
– Cisco WAFS replication directives-Configured Cisco WAFS replication directives are not retained during the migration, because the replication function is not supported in Cisco WAAS Version 4.0.
– Common Internet File System (CIFS) coherency settings-Configured CIFS coherency settings are not maintained, because they are no longer necessary in Cisco WAAS Version 4.0, which provides an adaptive coherency model that requires no user configuration.
– Redundant Array of Independent Disks 0 (RAID-0) and "just a bunch of disks" (JBOD) disk configurations-All WAEs with two or more disk drives configured with RAID-0 or JBOD are automatically converted during the upgrade to RAID-1. If necessary, the WAE automatically evicts cached content using a Least Recently Used (LRU) algorithm to support the change in usable disk capacity.
– Network File System (NFS) acceleration-NFS configurations will be removed as the NFS protocol acceleration components are not included in WAAS v4.0.
• Supported configurations-The migration to Cisco WAAS Version 4.0 requires that all WAEs that are planned to perform WAN optimization capabilities must be deployed on routable subnets that are different from the subnets to which clients and servers are connected. Any connectivity directives in the original Cisco WAFS Central Manager that map explicitly to a Cisco WAFS Core WAE are automatically modified to map to a newly created Cisco WAFS Core Cluster that includes the Cisco WAFS Core WAE.
• Additional devices-In some cases, additional WAE devices need to be deployed to support an upgrade from Cisco WAFS to Cisco WAAS. These cases include:
– Deployments of Cisco WAFS where the central manager is deployed on a Cisco WAE also acting as a Cisco WAFS Core-An additional WAE is required to act as a central manager in the Cisco WAAS network, because this service must be run on a separate appliance.
– Deployments of Cisco WAFS in which you want to take advantage of a phased migration-An additional Cisco WAE may be necessary to act as an interim Cisco WAFS Core WAE in the Cisco WAAS network.
– Deployments of Cisco WAFS that use higher fan-out ratios than those supported by Cisco WAAS-Because Cisco WAAS provides additional WAN optimization technologies that require additional CPU, memory, and disk requirements, you should ensure that an adequate number of (and appropriately sized) Cisco WAEs are deployed in the remote branch offices as well as in the data center.
• Caveats-Please consider the following caveats when migrating from Cisco WAFS to Cisco WAAS:
– Upgrades from Cisco WAFS to Cisco WAAS require that the Cisco WAFS topology be fully configured. If file servers are not configured, directives are considered invalid and the upgrade will not work.
– Application policies need to be configured after the migration. You can easily apply the default application policy against a device group within Cisco WAAS Central Manager after an upgrade.
FULL MIGRATION HIGH-LEVEL PROCEDURE
• Preparation of your network for a full migration to Cisco WAAS-This process includes performing a configuration backup of each Cisco WAFS device using Device Manager GUI and command-line interface (CLI), as well as preparing the Cisco WAAS Version 4.0 Central Manager. In a full migration scenario with an existing standalone Cisco WAFS Central Manager, you can simply upgrade this WAE. If the existing WAFS central manager is cohosted on a Cisco WAFS Core WAE, you should back up the central manager database from the Cisco WAFS Core WAE and restore it to a new WAE acting as a standalone WAAS central manager.
• Distribution and installation of software-Distribute the Cisco WAAS Version 4.0 Software image to all the WAEs in the topology using the WAFS central manager GUI or device CLI, and reboot the WAEs to perform the upgrade.
• Activation of WAEs within Cisco WAAS Central Manager-Activate all WAEs from the Cisco WAAS Central Manager to make them available for central management.
• Verification of migration and functions
FULL MIGRATION PROCEDURE
Preparing Your Network
1. Perform a backup of each WAE from the device manager GUI of each WAE. You should perform this step on all WAEs in the deployment, including the central manager WAE. To perform a backup of each WAE from the device manager GUI, open Internet Explorer and browse to each WAE and navigate to:
File Engine > Control > Backup
From this page, click the Download button, as shown in Figure 1.
Figure 1. Backing Up WAEs
Distribution and Installation of Software
1. Connect to the central manager WAE CLI and use the copy command to copy the Cisco WAAS Version 4 binary file into the central manager software image repository.
The syntax of the WAE CLI copy command to copy a software binary file into the central manager software repository follows:
Because the Cisco WAFS Central Manager can hold up to five software images, the (slot#) parameter should be 1-5. For example:
Note: The message "MD5 not defined, skipping validation" is expected, and you can ignore it.
To verify that the file was successfully copied into the central manager repository, use the command:
2. When the Cisco WAAS Version 4 binary file is uploaded to the central manager, distribute the file to all the WAEs in the WAFS topology. Do this in the central manager by going to:
Software Versions > Upgrade
Click the Cisco WAAS Version 4 binary file (notice that the line becomes highlighted) and then click Status, as shown in Figure 2.
Figure 2. Software Version Status Window
Figure 3. Distributing Software to All WAEs
Figure 4. Distribution Status Window
3. When the software has been successfully distributed to all the WAEs, ensure that the WAAS software file is selected and click Install to move the WAAS software image into the software installation folder on each of the WAEs (Figure 5).
Figure 5. Installing WAAS Software Image
Figure 6. Operation Status Window
Note: The software image must be successfully installed on all WAE devices before it can be installed on the central manager.
4. When the install is completed, click Activate. This action causes each of the affected WAEs to reboot and install the WAAS software (Figure 7).
Figure 7. Activating Installation
Note: When upgrading from WAFS to WAAS, the disk capacity assigned to the WAFS file cache is shrunk to provide disk capacity for the DRE database. The WAFS cache in Cisco WAAS Version 4 on an edge WAE is given the lesser of 300 GB or one-half of the available storage capacity.
5. When all WAEs have successfully activated the new version of software, be sure to repeat the install and activate processes to install the WAAS software on the central manager WAE as well. When the software is distributed, you should manually reload the WAE through the CLI and configure the appropriate device mode.
When the WAEs are reachable again and all have installed the WAAS software, proceed to the next task.
Activation of WAEs
1. First, disable central management services on the WAAS central manager WAE through the CLI:
2. Then copy the file generated from the backup operation performed against the WAE acting as the WAFS central manager to the WAE acting as the WAAS central manager and restore the database:
When the file is successfully transferred to the new WAAS central manager, restore the database. Respond "yes" when the WAAS central manager prompts you to confirm that you wish to restore the database. Restoring the WAFS central manager database into the WAAS central manager automatically marks all WAEs as "replaceable".
Note: Importing the WAFS central manager database into a WAAS central manager overwrites any existing WAFS configurations in the WAAS central manager that are conflicting. Existing WAFS configurations that are not conflicting are not modified.
3. When the WAFS central manager database is imported into the WAAS central manager, enable central management services and save the WAE configuration:
4. Connect to each WAE using the CLI and supply a central manager IP address. Then perform node recovery on each WAE to reconnect to the central manager:
5. After recovering the device identity on each WAE, enable the central management service on each WAE and save the WAE configuration:
6. When all WAEs have successfully completed node recovery, central management services are enabled, and configurations are saved, open the WAAS central manager interface using the URL:
Navigate to Devices > Devices and note that each of the WAEs is marked as Inactive, as shown in Figure 8. Click the Activate All icon to activate all devices.
Figure 8. Activating Devices
Figure 9. Device Activation Window
Note: Device activation may take up to 10 minutes, because this process is performed during the periodic exchange of configuration data between the central manager and each WAE. You can monitor the status of each WAE through the Devices homepage.
7. Each of the WAEs should change from Inactive to Pending while activation is taking place. When activation has finished, each of the WAEs appear as Online, as shown in Figure 10.
Figure 10. Device Status
Verification of Migration and Functions
• Services > File > File Servers-Verify that file servers configured for optimization were imported, WAFS core clusters were properly assigned, dynamic share configuration was retained, and optionally configure file servers for read-only disconnected mode.
• Services > File > Connectivity-Verify that connectivity-directive parameters were migrated, including file server settings, assigned WAFS edge devices and groups, and WAN usage parameters.
• Services > File > File Blocking-Verify that any configured file-blocking directives were imported correctly.
• Services > File > Preposition-Verify that any previously configured preposition directives were migrated properly.
• Devices > Device Groups-Verify that WAFS core cluster configurations and membership were retained through the migration.
PHASED MIGRATION HIGH-LEVEL OVERVIEW
• Preparation of your network for a phased migration to Cisco WAAS-Preparation includes performing a configuration backup of each WAFS device using the Cisco Device Manager GUI and CLI, as well as preparing the Cisco WAAS Version 4.0 Central Manager by importing the existing Cisco WAFS Central Manager database. In a phased migration scenario, a separate WAE is necessary to act as a WAAS central manager, and the existing WAFS central manager database is restored onto the WAAS central manager. The WAFS central manager WAE is the last to be migrated. In addition, in single WAFS core WAE scenarios that require phased migration, yet another WAE is required to act as a WAFS core WAE in the WAAS topology. You should configure these extra WAEs and confirm that they are online before beginning the migration.
• Assessment of WAE migration order and timeline-Cisco recommends that you migrate groups of WAEs that are interconnected (edge and core pairs and WAEs within the same device groups or same locations) together, and create a schedule that outlines which WAEs will be migrated and when. If you do not perform an accurate assessment and interconnected groups of WAEs are not migrated together, service will be interrupted for the WAE pairs that are unable to reach one another or are running incompatible versions of software. Cisco WAFS Version 3 and Cisco WAAS Version 4 are not compatible, nor are they interoperable.
• Distribution and installation of software-Distribute the Cisco WAAS Version 4.0 Software image to WAEs based on migration order and timeline using the CLI, and reboot the WAEs to perform the upgrade. Note that Cisco WAFS Version 3 Central Manager does not provide facilities for selective software installation, so you must use the CLI of each WAE.
• Activation of WAEs within Cisco WAAS Central Manager-Activate all WAEs from the WAAS central manager to make them available for central management. You should do this as WAEs are upgraded from Cisco WAFS Version 3 to Cisco WAAS Version 4.
PHASED MIGRATION PROCEDURE
Preparing Your Network
1. Perform a backup of each WAE from its device GUI. You should perform this step on all WAEs in the deployment, including the central manager WAE. To perform a backup of each WAE from the device GUI, open Internet Explorer and browse to each WAE and navigate to:
File Engine > Control > Backup
From this page, click the Download button, as shown in Figure 11.
Figure 11. Backing Up WAE Configuration
2. Then copy the file generated from the backup operation performed against the WAE acting as the WAFS central manager to the WAE acting as the WAAS central manager and restore the database. This process requires that the WAFS central manager backup file be placed on a server that is accessible through HTTP or FTP:
When the file is successfully transferred to the new WAAS central manager, first disable central management services and then restore the database. Respond "yes" when the WAAS central manager prompts you to confirm that you wish to restore the database. Restoring the WAFS central manager database into the WAAS central manager automatically marks all WAEs as "replaceable".
Note: Importing the WAFS central manager database into a WAAS central manager overwrites any existing WAFS configurations in the WAAS central manager that are conflicting. Existing WAFS configurations that are not conflicting are not modified.
3. When the WAFS central manager database is imported into the WAAS central manager, enable central management services and save the WAE configuration:
4. Connect to the central manager and verify that all the settings have been successfully integrated into the WAAS central manager using the URL:
• Services > File > File Servers-Verify that file servers configured for optimization were imported, WAFS core clusters were properly assigned, dynamic share configuration was retained, and then optionally configure file servers for read-only disconnected mode
• Services > File > Connectivity-Verify that connectivity-directive parameters were migrated, including file server settings, assigned WAFS edge devices and groups, and WAN usage parameters.
• Services > File > File Blocking-Verify that any configured file-blocking directives were imported correctly.
• Services > File > Preposition-Verify that any previously configured preposition directives were migrated properly.
• Devices > Device Groups-Verify that WAFS core cluster configurations and membership were retained through the migration.
Assessment of WAE Migration Order and Timeline
Note: You should perform the steps in the next two sections, "Distribution and Installation of Software" and "Activation of WAEs", once for each of the identified migration groups until all WAEs are successfully migrated from WAFS to WAAS.
Distribution and Installation of Software
1. Download the WAAS binary file to each WAE that is being migrated in this migration group using the copy command from the CLI. You can do this using either HTTP or FTP. When using FTP, you will be prompted for user credentials. Note that one pound (#) sign is printed for every 1 MB downloaded. This operation may take a while over a WAN.
2. When the software is downloaded to each of the WAEs in the migration group, be sure to reload the WAEs to install the upgraded software:
The reload and installation process may take up to 15 minutes.
Note: When upgrading from WAFS to WAAS, the disk capacity assigned to the WAFS file cache is shrunk to provide disk capacity for the DRE database. The WAFS cache in Cisco WAAS Version 4 on an edge WAE is given the lesser of 300 GB or one-half of the available storage capacity.
Activation of WAEs
1. Connect to each WAE using the CLI and supply a central manager IP address. Then perform node recovery on each WAE to reconnect to the central manager:
2. After recovering the device identity on each WAE, enable the central management service on each WAE and save the WAE configuration:
3. When all WAEs have successfully completed node recovery, central management services are enabled, and configurations are saved, open the WAAS central manager interface and navigate to:
Devices > Devices
Notice that each of the WAEs from the migration group is shown as Inactive (Figure 12). Click the Activate All icon to activate all WAEs from the migration group. Any devices that have already been migrated should appear Online and any devices that have not yet been migrated should appear Offline.
Figure 12. Device Status
Figure 13. Device Activation Window
Note: Device activation may take up to 10 minutes, because this process is performed during the periodic exchange of configuration data between the central manager and each WAE. You can monitor the status of each WAE through the Devices homepage.
Figure 14. System Status
SUMMARY