Table Of Contents
Release Note for Cisco Wide Area Application Services Software Version 4.3.5x
October 29, 2012
Note The most current Cisco documentation for released products is available on Cisco.com.
This release note applies to the following software versions for the Cisco Wide Area Application Services (WAAS) software:
For information on WAAS features and commands, see the WAAS documentation located at http://www.cisco.com/en/US/products/ps6870/tsd_products_support_series_home.html.
Note The WAAS Central Manager must be the highest version of all devices in your WAAS network. Upgrade the Central Manager first before any other devices.
This release note contains the following sections:
Upgrading From WAFS to WAAS
Although WAFS to WAAS migration is supported, a rollback from WAAS to WAFS is not supported. For information regarding a WAFS-to-WAAS migration, contact your Cisco Sales Engineer.
If you are upgrading from WAFS 3.0.7 or later to WAAS, you must upgrade to a released WAAS version; you cannot upgrade to a prerelease version of WAAS software.
If you are upgrading from the WAFS 3.0.7-special5 build or from a later WAFS release to WAAS, you must upgrade to a minimum of WAAS 4.0.5 or later; however, to ensure that you obtain all of the latest fixes and features, we recommend that you upgrade to the most current version of WAAS.
Note the following points when upgrading from WAFS to WAAS:
•When you upgrade from WAFS to WAAS, you may lose up to half of the WAFS cache space because the upgrade process uses the WAFS cache eviction process to reclaim the space needed for the DRE cache; the oldest content is removed first.
•The hardware that supports WAFS 3.0 also supports WAAS, with the exception of the NM-CE.
•You need a dedicated WAE to function as the Central Manager in WAAS.
•You must place the WAEs in a separate subnet from the clients, or you must use the GRE return feature.
•After migrating from WAFS to WAAS, reenter the file server credentials from the WAAS Central Manager GUI.
Upgrading and Interoperability
This section contains the following topics:
Central Managers running version 4.3.5x can manage WAEs running software versions of 4.0.19 and later. However, it is recommended that all WAEs in a given WCCP service group be running the same version.
Note The default value for the WCCP source IP mask changed in version 4.2.1 to 0xF00. If you are upgrading a WAE that previously used the default WCCP source IP mask of 0x1741, its WCCP mask is not changed. Note that 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 IOS router first. To remove the global WCCP configuration, use the following no ip wccp global configuration commands:Router(config)# no ip wccp 61Router(config)# no ip wccp 62
Step 2 Perform the WAAS software upgrade on all WAEs using the WAAS Central Manager GUI.
Step 3 Verify that all WAEs have been upgraded in the Devices pane of the WAAS Central Manager GUI. Choose My WAN > Manage 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.
If you have upgraded any WAEs from a version earlier than 4.2.1, and the WAEs were using the default mask value, the mask value is not changed by the upgrade.
Step 5 Re-enable WCCP redirection on the IOS routers. To enable WCCP redirection, use the ip wccp global configuration commands:Router(config)# ip wccp 61Router(config)# ip wccp 62
Note When a Central Manager running version 4.1.5c or later is managing a WAE running a previous version (4.1.5b or earlier), you must use the Central Manager to create, modify, delete, and schedule preposition tasks.
This requirement is necessary because of preexisting behavior in WAE software versions 4.1.5b or earlier that causes schedule information, from a preposition task created on the WAE, to be discarded by the 4.1.5c or later Central Manager. Since the Central Manager cannot create a preposition task successfully without schedule information, the preposition task is automatically removed from the WAE.
In this case, although the Central Manager GUI indicates that the preposition schedule is NOW and the WAE has been assigned to the task, this information is misleading.
To recover from this scenario, for preposition tasks that were created on WAE software versions 4.1.5b or earlier to be successful with a Central Manager running version 4.1.5c or later, follow these steps:
Step 1 Modify the schedule as required using the Central Manager GUI, even if you want the preposition schedule as NOW, and click Submit.
Step 2 Wait two data feed poll cycles for the configuration to synchronize between the Central manager and the WAE (default data feed poll cycle is 300 seconds).
The preposition task is then created on the WAE and the Central Manager, and the WAE is assigned to the preposition task with the required schedule changes.
In addition to GUI changes, any preposition changes made using the CLI on a WAE running previous version 4.1.5b or earlier are also discarded by the 4.1.5c or later Central Manager.
Therefore, you must also use the Central Manager to perform the following preposition CLI tasks:
•Create, modify, or delete schedule
•Modify or delete root-share
Upgrading from a Prerelease Version to Version 4.3.5x
To upgrade from WAAS prerelease software to version 4.3.5x, you must perform the following tasks to ensure a successful upgrade:
•Restore the factory default settings by using the restore factory-default command.
•Perform a fresh install from the rescue CD.
Upgrading from a Release Version to Version 4.3.5x
This section contains the following topics:
For additional upgrade information and detailed procedures, refer to the Cisco Wide Area Application Services Upgrade Guide.
Requirements and Guidelines
When you upgrade to version 4.3.5x, observe the following requirements, guidelines, and considerations:
•Upgrading to version 4.3.5x is supported only from versions 4.0.19, 4.0.27, 4.1.1d, 4.1.3, 4.1.3b, 4.1.5c, 4.1.5f, 4.1.7a, 4.1.7b, 4.2.1, 4.2.3, 4.2.3b, 4.2.3c, 4.3.1, 4.3.3, and 4.3.5. If you want to upgrade a WAAS device running a different version, first upgrade to the next supported version in the list, and then upgrade to the current 4.3.5x version.
•To take advantage of new features and bug fixes, we recommend that you upgrade your entire deployment to the latest version.
•If you operate a network with devices that have different software versions, the WAAS Central Manager must be the highest version.
•Upgrade the WAAS Central Manager devices first, and then upgrade the WAE devices. If you have a standby WAAS Central Manager, upgrade it first, before upgrading the primary WAAS Central Manager. After upgrading, restart any active browser connections to the WAAS Central Manager.
•Before upgrading a WAAS Central Manager to version 4.3.5x, make a database backup by using the cms database backup EXEC command. This command creates a backup file in /local1/. In case of any problem during the upgrade, you can restore the database backup that you made before upgrading by using the cms database restore backup-file EXEC command, where backup-file is the one created by the backup command.
•If you upgrade a WAAS Central Manager to 4.3.5x using the Jobs > Software Update page from a 4.0.x WAAS Central Manager, enter 18.104.22.168.1 in the Software Version field.
•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 WAFS was enabled on the device before the upgrade, then the Enterprise license should be enabled. Configure any additional licenses (Video and Virtual-Blade) 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.
•After upgrading application accelerator WAEs, verify that the proper application accelerators, policies, and classifiers are configured. For more information on configuring accelerators, policies, and classifiers, see the "Configuring Application Acceleration" chapter in the Cisco Wide Area Application Services Configuration Guide.
•WAAS versions 4.1.3 and later supports SSL application definition, which is enabled for monitoring by default. However, if you are upgrading from version 4.1.1 or earlier to version 4.3.5x and already have 20 applications enabled for monitoring, the new SSL application will have monitoring disabled because a maximum of 20 monitored applications are allowed. In order to enable monitoring of the SSL application, you must disable monitoring of a different application and then enable monitoring of the SSL application. You can enable and disable monitoring by using the Enable Statistics check box in the Modifying Application page of the WAAS Central Manager (Configure > Acceleration > Applications > Application Name).
If the SSL Bandwidth Optimization chart has no data, monitoring may be disabled for the SSL application definition. Check that monitoring is enabled for the SSL application.
•If you are upgrading a WAAS Central Manager from version 4.0.19 or later and have the secure store enabled, you will need to reopen the secure store after the device reloads (and after any reload). From the WAAS Central Manager GUI, choose Admin > Secure Store or use the cms secure-store open EXEC command. For more information on using the secure store, see the "Configuring Secure Store Settings" section in the Cisco Wide Area Application Services Configuration Guide.
•When upgrading a WAE from version 4.0.19 to version 4.3.5x, where the default policy configuration was applied from the CLI, after the upgrade, you may see two classifiers for NFS traffic in the WAAS Central Manager and on the WAE device: NFS and NFS-non-wafs. These classifiers have no effect on NFS traffic acceleration, which continues to operate as configured.
•If you are upgrading from version 4.0.x to version 4.1.x or later, the way a wildcard mask is interpreted has changed. Wildcard masks can be specified for a traffic classifier match condition or an ACL rule. In version 4.0.x, a wildcard mask of 255.255.255.255 would (incorrectly) match no IP addresses, but in version 4.1.x and later, this wildcard mask matches any IP address, as expected.
•The device group and role naming conventions changed in version 4.1.3. Device group and role names cannot contain characters other than letters, numbers, period, hyphen, underscore, and space. (In version 4.0.x, other characters were allowed.) If you upgrade from version 4.0.x to version 4.3.5x, disallowed characters in device group and role names are retained, but if you try to modify the name, you must follow the new naming conventions.
•The standby interface configuration changed in version 4.1.3. If multiple standby groups are configured before upgrading from version 4.1.1 or earlier, only the group with the lowest priority and a valid member interface will remain after the upgrade, and it will become standby interface 1. If the errors option was configured, it will be removed.
•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 4.3.5x, you must reenter all passwords in the primary Central Manager GUI. The passwords that need to be reentered include user passwords, CIFS file server passwords, and WAFS core passwords. If you do not reenter the passwords, after upgrading to version 4.3.5x, the Central Manager fails to send configuration updates to WAEs and the standby Central Manager until after the passwords are reentered.
•If you have a version 4.1.1x Central Manager where secure store has been initialized but not opened (such as after a reload) and the Central Manager has sent configuration updates containing user account, CIFS core password, preposition, or dynamic share changes to WAEs before the secure store was opened, then before upgrading the Central Manager to version 4.3.5x, you must reenter all passwords in the primary Central Manager GUI. The passwords that need to be reentered include user passwords, CIFS file server passwords, and WAFS core passwords. If you do not reenter the passwords, after upgrading to version 4.3.5x, the Central Manager fails to send configuration updates to WAEs and the standby Central Manager until after the passwords are reentered.
•If you have a version 4.1.1x or earlier Central Manager, are using external/remote users that have the admin role, and have edited one or more of these users on the Central Manager, you might encounter caveat CSCsz24694, which causes the Central Manager not to send updates to WAEs after upgrading to version 4.1.5x. To work around this caveat, from the Central Manager, manually edit the external users (without changing anything) after the upgrade. If you have a large number of external users defined, contact Cisco TAC for a script to run before or after the upgrade.
•The default value for the WCCP source IP mask changed in version 4.2.1 to 0xF00. If you are upgrading a WAE that previously used the default WCCP source IP mask of 0x1741, its WCCP mask is not changed. Note that all WAEs in a WCCP service group must have the same mask. For the recommended upgrade procedure for WAEs in a service group, see the "WCCP Interoperability" section.
•The SNMP username and remote entity ID constraints changed in version 4.2.1. SNMP usernames are limited to 32 characters. (In version 4.1x and earlier, 64 characters were allowed.) SNMP remote entity IDs must be between 10-32 hexadecimal characters. (In version 4.1x and earlier, 1-64 characters were allowed.) If you upgrade from version 4.1x or earlier to version 4.3.5x, invalid settings in these fields are deleted.
•Central Manager support for configuring the Initial Slow Start Threshold TCP/IP setting was removed in version 4.2.1. If your Central Manager is managing devices earlier than version 4.2.1, you may see repeated device configuration change updates for the Initial Slow Start Threshold configuration parameter coming from these devices when this parameter is assigned a non-default value in the devices. To avoid these repeated updates, use the no tcp init-ss-threshold global configuration command to set the default value on the devices, which is the recommended value for most networks.
•If you are upgrading a Central Manager from version 4.1.1x to version 4.3.5x, before you upgrade, save all scheduled default reports that exist in version 4.1.1x to avoid failed scheduled reports. To save a default report that you want to schedule, display the report and click the Save button. This requirement does not apply if you are upgrading from 4.1.3 or later because default reports are automatically saved.
•If you are upgrading a Central Manager from version 4.2.3x or earlier to version 4.3.5x, and you have any scheduled reports that are configured for more than 100 recurrences, after the upgrade only 100 recurrences are retained.
•After upgrading a Central Manager from version 4.1.x to version 4.3.5x, any scheduled reports that contain the following charts are removed from the Manage Reports and Scheduled Reports lists: Managed Devices Information, CPU Utilization, and any CIFS charts. You can reschedule the CPU Usage report for a device if you want. The Managed Devices and CIFS charts are not applicable as part of a scheduled report.
•After upgrading a Central Manager from version 4.1.1x to version 4.3.5x, any scheduled reports that are pending (not yet completed) are removed. To continue generating these reports, reschedule them.
•If you use the setup utility for basic configuration after upgrading to 4.3.5x, wccp router list 7 is used. Since the setup utility is designed for use on new installations, any existing configuration for wccp router list 7 will be replaced with the new configuration.
•If you have disk encryption enabled and are upgrading to version 4.3.5x NPE from version 4.2.1 or earlier, disk encryption configuration as well as disk cached data are lost. There is no impact when upgrading to standard version 4.3.5x (non-NPE).
•Beginning with version 4.3.1, the print admin role is no longer assigned to all admin user accounts by default. However, if you are upgrading from an earlier version, the print admin role is not automatically removed from all admin user accounts. To manually remove the print admin role from an account, edit the admin user from the Admin > AAA > Users page, uncheck the Print Admin check box, and click Submit.
•After upgrading a Central Manager from a version prior to 4.3.1, the AllDevicesGroup device group is renamed to the AllWAASGroup. Additionally, an AllWAASExpressGroup is created for all WAAS Express devices.
Ensuring a Successful RAID Pair Rebuild
RAID pairs will 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 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 from Version 4.3.5x to a Previous Version
Note the following guidelines and considerations for downgrading:
•Downgrade is supported only to versions 4.3.5, 4.3.3, 4.3.1, 4.2.3c, 4.2.3b, 4.2.3, 4.2.1, 4.1.7b, 4.1.7a, 4.1.5f, 4.1.5c, 4.1.3b, 4.1.3, 4.1.1d, 4.0.27, or 4.0.19.
•On a vWAAS device you cannot downgrade to a version earlier than 4.3.1.
•When downgrading WAAS devices, first downgrade application accelerator WAEs, then the standby WAAS Central Manager (if you have one), and lastly the primary WAAS Central Manager.
•If you have a standby WAAS Central Manager, it must be registered to the primary WAAS Central Manager before the downgrade.
•When downgrading from a WAAS NPE version to a version earlier than 4.2.3, the show version last command does not display NPE in the version output.
•If two Cisco WAE Inline Network Adapters are installed in a WAE, you must remove one of the adapters before you downgrade the WAE to a version earlier than 4.2.1. Two Cisco WAE Inline Network Adapters are not supported in WAAS versions earlier than version 4.2.1.
•If downgrading to version 4.2.1, you must first change the password for WCCP, SNMP user, RADIUS, TACACS, or transaction log modules before the downgrade if any of the special characters !@#$%\ were used in the password for the module. Otherwise, the related CLI commands for those modules will fail.
•Due to stricter security implemented in version 4.2.1 and later, when downgrading to a version earlier than 4.2.1, any configuration settings that contain passwords or security keys are discarded and will have to be reconfigured. Affected CLI commands include the following: ntp, radius-server, snmp-server user, tacacs, transaction-logs, and wccp tcp-promiscuous router-list-num. After the downgrade, discarded configurations are listed in the file /local1/discarded_cli.
Additionally, the following Central Manager settings are affected:
–All SNMP users are deleted.
–The RADIUS encryption key is deleted.
–The TACACS security word is deleted.
–The Email notification server password is deleted.
–The transaction log and video acceleration transaction log export server configurations are deleted.
–The WCCP password is set to null.
–The username and password (if defined) associated with all software image files is set to anonymous/anonymous.
•Locked-out user accounts will be reset upon a downgrade.
•All preposition directives configured in CIFS accelerator mode must be removed before downgrading to a version earlier than 4.1.1. You also must configure legacy mode file services by enabling a core server and configuring a WAFS core cluster, enabling an edge server, and registering file servers with the Central Manager.
•All dynamic shares configured in CIFS accelerator mode must be switched to legacy mode before downgrading to a version earlier than 4.1.1, if you want to keep the dynamic shares. To switch a dynamic share to legacy mode, follow these steps:
1. Edit the dynamic share in the Configure > File > Dynamic Shares window and choose a file server in the drop-down list. (File servers must be previously registered in the Configure > File > File Servers window.)
2. Click Submit.
•If extended object cache is enabled, all CIFS cache data, DRE cache data, and virtual blade data is lost when downgrading to a version earlier than 4.2.1.
•Any new reports and charts that were introduced prior to version 4.3.5x are removed from managed reports and scheduled reports when downgrading to an earlier version in which they are not supported.
•The default value for the WCCP source IP mask changed in version 4.2.1 to 0xF00. If you are downgrading a 4.3.5x WAE that uses the default WCCP source IP mask, its WCCP mask is not changed on downgrade to a version earlier than 4.2.1. Note that all WAEs in a WCCP service group must have the same mask.
•If you use the setup utility for basic configuration after downgrading to a version earlier than 4.2.3x, WCCP router list 8 is used. Since the setup utility is designed for use on new installations, any existing configuration for WCCP router list 8 will be replaced with the new configuration.
•After downgrading a Central Manager to a version earlier than 4.3.1, the AllWAASGroup device group is renamed to the AllDevicesGroup. Additionally, the AllWAASExpressGroup is removed.
•After downgrading a Central Manager to a version earlier than 4.3.1, all registered WAAS Express devices are deleted from the Central Manager. If the Central Manager is later upgraded to 4.3.1, WAAS Express devices must be registered again.
To downgrade the WAAS Central Manager (not required for WAE devices), follow these steps:
Step 1 If you are downgrading to version 4.1.1x or earlier and the secure store is enabled in the Central Manager, disable it using the cms secure-store clear global configuration command. (This step is not needed if you are downgrading to version 4.1.3 or later.)(config)# cms secure-store clear
Step 2 (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.CentralManager# cms database backup
Step 3 Install the downgrade WAAS software image by using the copy ftp install EXEC command.
Step 4 Reload the device.
Downgrading the database may trigger full updates for registered devices. In the Central Manager GUI, ensure that all previously operational devices come online.
Cisco WAE and WAVE Appliance Boot Process
To monitor the boot process on Cisco WAE and WAVE appliances, connect to the serial console port on the appliance as directed in the Hardware Installation Guide.
Cisco WAE and WAVE appliances have video connectors that should not be used in a normal operation. The video output is for troubleshooting purposes only during BIOS boot and stops displaying output as soon as the serial port becomes active.
Cisco WAE-674, WAE-7341, and WAE-7371 RAID Controller Firmware Upgrade
Under rare circumstances, the RAID controller firmware used in the WAE-674, WAE-7341, and WAE-7371 appliances can cause the disk storage subsystem to go offline and the affected devices to stop optimizing connections. The symptoms 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.
The solution is to upgrade to the 5.2-0 (15427) RAID Controller Firmware, which can be found on cisco.com at the Wide Area Application Service (WAAS) Firmware download page (registered customers only). The firmware binary image is named L4_15427_FIRMWARE.bin.
Instructions on how to apply the firmware update are posted on cisco.com together with the firmware and are in the file named L4_15427_FIRMWARE.zip.
Cisco WAE-612 Hard Disk Drive Replacement Notification
This notice applies to the WAE-612 and all WAAS versions previous to 4.0.19 that support the hot-swap replacement of drives while the appliance is running.
A problem may occur while replacing the drives while the unit is running. Occasionally after a drive hot-swap procedure, the WAE-612 may stop operating and require a reboot.
To avoid this problem, upgrade your WAAS software to version 4.0.19 or later.
This notice does not apply to the WAE-674, WAE-7341, or WAE-7371.
This section includes operating considerations that apply to software versions 4.3.5x:
This section discusses operating considerations when operating a WAAS network that mixes version 4.3.5x devices with devices running earlier software versions.
•WAAS version 4.3.5x does not support running in a mixed version WAAS network where any WAAS device is running a software version lower than 4.0.19. If you have any WAAS devices running version 4.0.17 or earlier, you must first upgrade them to version 4.0.19 (or a later version), before you install version 4.3.5x. You should first upgrade any WAEs to version 4.0.19 (or a later version) and then upgrade any WAAS Central Managers to version 4.0.19 (or a later version).
•In a mixed version WAAS network with version 4.3.5x, the WAAS Central Manager must be running the highest version of the WAAS software.
•When a WAAS Central Manager is upgraded to version 4.3.5x and it is managing a 4.0.x device with legacy mode WAFS enabled that is not upgraded, the device may appear to have both legacy mode WAFS and the transparent CIFS accelerator enabled, because the Central Manager enables it by default. Disable the transparent CIFS accelerator if you want to continue to use legacy mode for WAFS on the 4.0.x device.
Central Manager Report Scheduling
In the WAAS Central Manager, we recommend running system wide reports in device groups of 250 devices or less, or scheduling these reports at different time intervals, so multiple system wide reports are not running simultaneously.
WAAS Express Policy Changes
Making policy changes to large numbers of WAAS Express devices from the Central Manager may take longer than making policy changes to WAAS devices.
Virtual Blade Configuration From File
If you copy the device configuration to the running-config from a file (for example, with the copy startup-config running-config command), configuration changes from the file are applied to the device without confirmation. If a virtual blade disk configuration exists in the configuration file and it is different from the actual device configuration, the device virtual blade disk configuration is removed and replaced with the disk configuration from the file. You will lose all data on the virtual blade disks.
Device Group Default Settings
When you create a device group in WAAS version 4.3.5x, 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 group. Do not enable the auto-register global configuration command when the interface is configured as part of a port-channel or standby group.
WAFS Support of FAT32 File Servers
The WAFS feature does not support file servers that use the FAT32 file system. You can use the policy engine rules to exclude from CIFS optimization 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
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 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 log in page. To avoid this prompt, remove the installed personal certificates or use a different browser.
Software Version 4.3.5a Resolved and Open Caveats
The following sections contain the resolved and open caveats for Software version 4.3.5a:
Software Version 4.3.5a Resolved Caveats
The following caveats were resolved in software Version 4.3.5a.
Caveat ID Number Description
Apache HTTPd vulnerability (CVE-2011-3192)
wafs_edge service is killed after upgrading to 4.3.5
Deadlock in CIFS AO Causes Clients to Experience Slowness
Software Version 4.3.5a Open Caveats
The open caveats for software version 4.3.5a are the same as those for software version 4.3.5. For details, see the ""Software Version 4.3.5 Open Caveats" section".
Software Version 4.3.5 Resolved Caveats and Open Caveats
The following sections contain the resolved caveats and open caveats in software version 4.3.5:
Software Version 4.3.5 Resolved Caveats
The following caveats were resolved in software version 4.3.5.
Software Version 4.3.5 Open Caveats
The following open caveats apply to software version 4.3.5.
The additional open caveats for software version 4.3.5 are the same as those for software version 4.3.3. For details, see the Release Note for Cisco Wide Area Application Services (Software Version 4.3.3).
WAAS Documentation Set
In addition to this document, the WAAS documentation set includes the following publications:
•Cisco Wide Area Application Services Online Help
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "WAAS Documentation Set" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2011-2012 Cisco Systems, Inc. All rights reserved.