Is this good plan? Please let me know. I would like to have minimum downtime. Also while i replace CM during maintenance window, will this affect production traffic between all WAE s? Go to Solution. But be aware that the changes you have made to the CM. View solution in original post. CM is being used for : pushing opt. Also be aware of potential spanning tree configs setup, which might block the port for some seconds.
My plan is to unplug existing CM completely from network and plug CM to same ports in the network. It has same IP address since it was restored exactly as CM. Please let me know if this will work or not. I don't think you can do that - the devices are different models, thus the generated certificate is different.
The network stuff could be specific ip-addresses, redirection etc , and is as such never defines in device groups, but either using CLI or on the indivudual Device in CM I prefer the CLi method ,. I would be grateful. If the recovery request matches the device record, then the WAAS Central Manager updates the existing record and sends the requesting device a registration response.
The replaceable state is cleared so that no other device can assume the same identity. When the WAAS device receives its recovered registration information, it writes it to file, initializes its database tables, and starts. I've never tried this - as I always run with the same global policy and just push that down to the device. Buy or Renew. Step 8 Verify the CMS status in the running configuration. Use this procedure to restore the primary CM database.
Look for the timestamp from the output and compare it with the current time. Step 9 Verify the CMS status in the running configuration. Step 2 From the branch WAE, enter the following commands:. Use this procedure to install a previous version of software on a branch WAE if you encounter a problem during the upgrade.
Step 1 Determine the previously installed version. Install the previous version software image. Step 4 Verify that the software image installed correctly. This section lists the commands that you can use for WCCP validity testing. Enter the commands three to four times in succession to determine if counters are incrementing. For possible Cisco IOS issues, capture the following debug output to either the console or a Telnet session:.
This section describes the methods that you can use for SMB validity testing, which includes manual procedures and automation tools. Use the following guidelines when performing SMB validity testing and performing a rollback:.
Use this procedure to prepare the shared server and client for SMB validity testing. Step 1 On the server, create a share directory that contains several subfolders and files. Step 2 Verify the following items on the shared server:. Use this procedure to manually perform a SMB performance test. Step 1 Verify operation by opening some Microsoft Office documents from the shared server. Step 2 Modify the files by adding some text and saving.
Step 3 Open the files again to inspect response time and data integrity. Record the time it took to open them and get to the place where your changes were made. The test should show significant improvement in the time to open and time to save operations. The same behavior should also be observed with the modified file.
Figure 1 shows some of the SMB charts. To display detailed information about any SMB connection, enter the show statistics connection optimized smb detail command. To display overall SMB accelerator statistics, enter the show statistics accelerator smb detail command as follows:. The RSS feeds are a free service. Upgrade Restrictions and Prerequisites The following list includes prerequisites and restrictions that you need to know about before upgrading your software: You must upgrade the Central Manager software to version 6.
You must do this action only on routers and switches that participate in transparent redirection and is not applicable to policy-based routing PBR or inline deployments. If you do not do this action and there is a current active WAAS network, disable WCCP in the routers and switches in the data center and all branches before the software upgrade to 6.
The following device platform is no longer supported on WAAS version 5. WAAS version 5. The following device platforms are no longer supported on WAAS version 5. If you are using NTLM Windows domain authentication or are using a nonstandard port other than port 88 for Kerberos authentication, you must change these configurations and ensure that your domain controller is configured for Kerebos authentication before proceeding with an upgrade to WAAS version 5.
Capacity Planning Capacity planning is an ongoing process as branches and applications are added. Install the software image directly using the Software Recovery CD or USB method to perform a clean install not an upgrade , which deletes the previous WAAS software image, deletes any cache and so forth. Procedure Step 1 Telnet to the primary CM. Disable WCCP. Validity Testing and Rollbacks This section describes specific actions that are related to backing up your software, restoring your software from a backup, registering upgrades, and testing different aspects of your network affected by the upgrade.
Procedure Step 1 From the primary CM, create a backup of the database. Restoring the Central Manager Databases This section describes how to restore the databases on the primary and standby CMs using their database backup files see the Backing Up the Central Manager Database. Guidelines and Restrictions Use the following guidelines when restoring the CM databases: Ensure that the CM is using the same software version as when the database backup file was created.
Restore the standby CM first and then restore the primary CM. If you are restoring a backup from a CM where the secure store was in user-provided passphrase mode when the backup was made, you may be asked to provide the secure store password during the restore process.
Step 2 From the branch WAE, enter the following commands: cms deregister force. Procedure Step 1 Determine the previously installed version. Guidelines and Restrictions Use the following guidelines when performing SMB validity testing and performing a rollback: Choose a single file or a variety of files for the test.
You must use the same file or files for all the tests base, cold, hot. Use an existing share or create a directory structure on the file server. Verify that the share has permissions set for domain users. We recommend that you test or create a share that has multiple nested directories at least 2 to 3 levels deep that contain files of various types such as PowerPoint, Excel or Word and sizes.
Procedure Step 1 On the server, create a share directory that contains several subfolders and files. Step 2 Verify the following items on the shared server: Adequate permissions for domain users used in the testing. 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.
Disable WCCP. Verify that WCCP is disabled. Step 4 Upgrade the data center WAE software as follows:. Open a console or Telnet session to the data center WAE.
Copy the software image to the WAE. You can use either the Universal or Accelerator only images. Reload the WAE. Verify that the image installed correctly. Confirm that WCCP is disabled. Telnet to each core router or switch. Enable WCCP. Step 7 Verify WAE device functionality as follows:. Confirm that redirecting intercepting router IDs are seen.
Confirm that all WAE devices in the cluster are seen. Confirm that the packet count to the WAE is increasing and no loops are detected. Confirm that flows are being optimized. All WAE devices in the data center are upgraded to version 5. After you upgrade your WAAS software to version 5. These accelerators perform similar optimizations using different techniques. This section assumes that you have already upgraded your devices to Version 5.
Step 3 Decide on your migration options by reviewing the information in these topics:. Step 4 Follow the migration steps in the section for the option you have selected. Step 5 If you had dynamic shares on a device that you migrated to the SMB application accelerator, you need to recreate those shares, as described in the "Migrating Dynamic Shares" section. Version 5. The CIFS and SMB application accelerators mostly support the same features, although they use different techniques to perform their optimizations.
Table 3 shows the main features supported by each accelerator for file sharing. Enabling one automatically disables the other on the device. They can coexist in the same WAAS network but only on separate devices that are not peers. Note that the SMB application accelerator provides options for fine-tuning the optimizations you want it to perform. When you upgrade to version 5. If you are migrating some or all of your file share traffic to the SMB application accelerator, be aware of these considerations:.
Before starting any migration, make sure that the current CIFS traffic load can be supported without the CIFS object cache for the time required to perform the migration. The all at once option is the simplest way to migrate. All you need to do is update all devices to version 5.
After you are done, the file share traffic is optimized by the SMB application accelerator. Step 1 Upgrade the data center and remote devices to Version 5. Step 3 Verify that all the WAE devices are online green. Step 4 Address any existing alarm conditions before proceeding.
Step 7 Verify proper WAE functionality as follows:. Verify that only the SMB accelerator is enabled. Confirm that other flows are optimized. You know that a connection is being optimized when you see the letter C in the Accel column for that connection in the output of the show statistics connection command.
With the phased-in mixed deployment migration, you separate your devices into two groups. You can either add additional data center devices or separate the devices in the data center; we strongly recommend that you perform a sizing estimate before you migrate any branch nodes.
You can use WAAS Central Manager reports to help determine sizing metrics such as traffic volume, connections, and pass-through traffic. Initially, when the WAE servers are assigned for each accelerator, the traffic load is increased on the device that handles the existing CIFS traffic. As soon as branches are updated to use the SMB accelerator, that traffic load drops, and the load on the designated SMB accelerator s begins to increase. This section describes the steps required to migrate some of your branches to SMB acceleration with AppNav.
This approach creates a WNG for the branch nodes you want to migrate to SMB acceleration, and uses branch affinity to distribute traffic from those branches to SMB accelerator nodes in the data center.
Unmigrated nodes are left unchanged. Step 1 Identify the number of connections you want to migrate and how to fit those connections into your WAAS network, as described in the "Planning Your Migration" section. Step 5 Verify that traffic is being optimized, as described in the "Verifying That Both Accelerators are Working" section. Before migrating some of your branch nodes to the SMB accelerator, plan your migration by performing a sizing estimate and deciding if you have enough capacity to support a phased migration.
Step 1 Identify the number of branch devices that you want to migrate to the SMB accelerator. Step 2 Determine how many file sharing connections those branches are handling. Step 3 Decide whether your data center capacity supports accelerating those connections with SMB on existing devices, or if you need additional capacity. If you determine that you need additional capacity, contact your Cisco representative.
Step 1 Select the group of target branches that you want to migrate to SMB acceleration. Step 2 Verify that the correct accelerator is enabled for each group of nodes in your network. Step 3 Verify that the connections are being optimized. Step 3 Decide whether your data center capacity supports accelerating those connections with SMB on existing devices or if you need additional capacity.
Step 4 Plan to perform the migration during a maintenance window; existing traffic will be processed with less acceleration during the migration process. Use this procedure to set up the recommended services 51 and 52 on a router by configuring the data center router to separate the traffic flow for the CIFS and SMB accelerators.
Step 1 Create an access list to identify the branch subnets that you want to redirect to the SMB accelerator:.
Step 2 Create the WCCP service groups and use the access list that you just created for the redirect list. When you then add branch subnets to the access list, those subnets are redirected to the SMB accelerator. The new service groups do not yet intercept traffic, because none of the branch subnets are listed in the access list.
0コメント