Guest

Cisco Wide Area Application Services (WAAS) Software

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

  • Viewing Options

  • PDF (246.4 KB)
  • Feedback
Release Note for Cisco Wide Area Application Services Software Version 4.1.7x

Table Of Contents

Release Note for Cisco Wide Area Application Services Software Version 4.1.7x

Contents

New and Changed Features

Upgrading From WAFS to WAAS

Upgrading and Interoperability

Prepositioning Interoperability

WCCP Interoperability

Upgrading from a Prerelease Version to Version 4.1.7x

Upgrading from Version 4.0.x or 4.1.x to 4.1.7x

Requirements and Guidelines

Ensuring a Successful RAID Pair Rebuild

Managing Passwords after an Upgrade

Downgrading from Version 4.1.7x to a Previous Version

Cisco WAE and WAVE Appliance Boot Process

Cisco WAE-674, WAE-7341, and WAE-7371 RAID Controller Firmware Upgrade

Cisco WAE-612 Hard Disk Drive Replacement Notification

Operating Considerations

Interoperability

Configuring Router Buffer Size

Virtual Blade Configuration From File

Device Group Default Settings

Using Autoregistration with Port-Channel Interfaces

WAFS Support of FAT32 File Servers

Preposition Jobs and CIFS Accelerator Restart

Software Version 4.1.7b Resolved and Open Caveats

Software Version 4.1.7b Resolved Caveats

Software Version 4.1.7b Open Caveats

Software Version 4.1.7a Resolved and Open Caveats

Software Version 4.1.7a Resolved Caveats

Software Version 4.1.7a Open Caveats

Software Version 4.1.7 Resolved and Open Caveats

Software Version 4.1.7 Resolved Caveats

Software Version 4.1.7 Open Caveats

WAAS Documentation Set

Obtaining Documentation and Submitting a Service Request


Release Note for Cisco Wide Area Application Services Software Version 4.1.7x


January 6, 2011

Note The most current Cisco documentation for released products is available on Cisco.com.


Contents

This release note applies to the following software versions for the Cisco Wide Area Application Services (WAAS) software:

4.1.7b

4.1.7a

4.1.7

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:

New and Changed Features

Upgrading From WAFS to WAAS

Upgrading and Interoperability

Upgrading from a Prerelease Version to Version 4.1.7x

Upgrading from Version 4.0.x or 4.1.x to 4.1.7x

Downgrading from Version 4.1.7x to a Previous Version

Cisco WAE and WAVE Appliance Boot Process

Cisco WAE-674, WAE-7341, and WAE-7371 RAID Controller Firmware Upgrade

Cisco WAE-612 Hard Disk Drive Replacement Notification

Operating Considerations

Software Version 4.1.7b Resolved and Open Caveats

Software Version 4.1.7a Resolved and Open Caveats

Software Version 4.1.7 Resolved and Open Caveats

WAAS Documentation Set

Obtaining Documentation and Submitting a Service Request

New and Changed Features

WAAS software version 4.1.7 includes the following new features and changes:

MAPI Configuration—Support was added to specify the reserved pool size maximum percent. This setting is used to restrict the maximum number of connections reserved for MAPI optimization during TFO overload. You can increase this value for deployments that observe a greater average number of connections per AG, or if TFO overload is a frequent occurrence.

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:

Prepositioning Interoperability

WCCP Interoperability

Prepositioning Interoperability


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, perform the following 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 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

Delete pattern

Modify or delete root-share

WCCP Interoperability

Central Managers running version 4.1.7x can manage WAEs running previous versions of 4.0.x and 4.1.x. However, it is recommended that all WAEs in a given WCCP farm be running the same version.

To upgrade the WAEs in your WCCP farm, 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 61
Router(config)# no ip wccp 62

Step 2 For large WCCP farms (greater than 15), increase the buffer size on the IOS router to the maximum of 65535. This is necessary when WCCP is configured with mask assignment, using a mask with 6 or 7 bits. To set the buffer size to 65535, use the buffers global configuration command:

Router(config)# buffers huge size 65000

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

Step 4 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 5 Re-enable WCCP redirection on the IOS routers. To enable WCCP redirection, use the ip wccp global configuration commands:

Router(config)# ip wccp 61
Router(config)# ip wccp 62


Upgrading from a Prerelease Version to Version 4.1.7x

To upgrade from WAAS prerelease software to version 4.1.7x, 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 Version 4.0.x or 4.1.x to 4.1.7x

This section contains the following topics:

Requirements and Guidelines

Ensuring a Successful RAID Pair Rebuild

Managing Passwords after an Upgrade

Requirements and Guidelines

When you upgrade from version 4.0.x or 4.1.x to version 4.1.7x, observe the following guidelines and requirements:

Upgrading to the current 4.1.7x version 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.7, and 4.1.7a. 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.1.7 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.1.7x, 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.1.7x using the Jobs > Software Update page from a 4.0.x WAAS Central Manager, enter 4.1.7.b.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 on page 9-3 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 Chapter 12, "Configuring Application Acceleration" in the Cisco Wide Area Application Services Configuration Guide.

WAAS version 4.1.7x supports SSL application definition, which is enabled for monitoring by default. However, if you are upgrading to version 4.1.7x 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, then monitoring may be disabled for the SSL application definition. Check that monitoring is enabled for the SSL application.

WAAS version 4.1.7x supports strong passwords. When you upgrade from version 4.0.17 or an earlier version, which does not support strong passwords, the previous weaker passwords will be retained. For details, see the "Managing Passwords after an Upgrade" section.

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 on page 9-10 in the Cisco Wide Area Application Services Configuration Guide.

If you are upgrading a WAE-511 or WAE-611, ensure that the BIOS disk mode is set to Native.

When upgrading a WAE from version 4.0.19 or earlier to version 4.1.7x, 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, 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, this wildcard mask matches any IP address, as expected.

The device group and role naming conventions have 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.1.7x, 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, 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 running version 4.1.3x or earlier 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.1.7x, 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.1.7x, the Central Manager will fail 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.1.7x, 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.1.7x, the Central Manager will fail 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.7x. 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.

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.

Managing Passwords after an Upgrade

WAAS software version 4.1.7x includes a strong password feature for improved security. Versions of the WAAS software previous to 4.0.19 do not have a strong password capability.


Note The following considerations apply to WAAS software version 4.1.7x with the strong password policy enabled. Strong passwords are disabled by default.


When you upgrade from version 4.0.17 or earlier to version 4.1.7x, note the following password considerations:

Existing passwords from the older version will continue to work in version 4.1.7x.

Existing passwords will expire after 90 days. Subsequent new passwords must conform to strong password requirements.

Strong passwords must meet the following requirements:

The password must be 8 to 31 characters long.

The password can include both uppercase and lowercase letters (A-Z and a-z), numbers (0-9), and special characters including ~`!@#$%^&*()_+-=[]\{};:,</>.

The password cannot contain the characters ` " | (apostrophe, double quote, or pipe) or any control characters.

The password cannot contain all the same characters (for example, 99999).

The password cannot contain consecutive characters (for example, 12345).

The password cannot be the same as the username.

Each new password must be different from the previous 12 passwords.

The password cannot contain dictionary words.

Downgrading from Version 4.1.7x to a Previous Version

Note the following guidelines for downgrading:

Downgrade is supported only to versions 4.1.7a, 4.1.7, 4.1.5f, 4.1.5c, 4.1.3b, 4.1.3, 4.1.1d, 4.0.27, and 4.0.19. If you want to downgrade a WAAS device to a different version, first downgrade to the closest supported version in the list, and then upgrade or downgrade to the desired version.


Note When downgrading from version 4.1.5c or later, dynamic share names with a space are deleted.


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.

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 prior to 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 prior to 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.

Use the following procedure to downgrade the WAAS Central Manager (not required for WAE devices) to version 4.1.7a, 4.1.7, 4.1.5f, 4.1.5c, 4.1.3b, 4.1.3, 4.1.1d, 4.0.27, and 4.0.19.


Note To downgrade the WAAS Central Manager to version 4.0.27, you must first follow the steps to downgrade to 4.0.25 and then upgrade the device to version 4.0.27.



Step 1 (Optional) If secure store is enabled, disable it using the cms secure-store clear global configuration command.

(config)# cms secure-store clear

Step 2 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 (Optional) If you are downgrading from a fresh install of version 4.1.7x (from the factory or from an installation performed with the WAAS recovery CD), back up the downgrade scripts to an FTP server as follows:

a. Enable FTP on the WAAS Central Manager by using the inetd enable ftp global configuration command.

b. Copy the needed downgrade scripts to the FTP server by using the copy disk EXEC command, as shown in the following example:

CentralManager# copy disk ftp ftp_server_ip remote_dir WAAS_Downgrade4_1_7_to_4_1_1d 
downgrade/WAAS_Downgrade4_1_7_to_4_1_1d

You need to copy only the downgrade scripts that you intend to use. See Step 7 for the complete list of downgrade scripts available.

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

Step 5 Reload the device.

The database needs to be downgraded before the Central Manager can use it and the CMS process can start. To optionally verify this status, use the show cms info EXEC command. It should respond with a message saying that a database downgrade is required.

Step 6 (Optional) If you performed Step 3, then restore the downgrade script files from the FTP server where you backed them up to the /downgrade directory on the WAAS Central Manager by using the copy ftp EXEC command as follows:

CentralManager# copy ftp disk ftp_server_ip remote_dir WAAS_Downgrade4_1_7_to_4_1_1d 
downgrade/WAAS_Downgrade4_1_7_to_4_1_1d

Step 7 Downgrade the database by using the appropriate cms database downgrade script EXEC command.

CentralManager# cms database downgrade script downgrade/WAAS_Downgrade4_1_7_to_4_1_1d

There are separate scripts depending on what version you are downgrading to:


Note If you are downgrading from version 4.1.7x to version 4.1.5x, no script is necessary. However, you must still execute the cms database downgrade command.


WAAS_Downgrade4_1_7_to_4_0_19

WAAS_Downgrade4_1_7_to_4_0_25

WAAS_Downgrade4_1_7_to_4_1_1d

WAAS_Downgrade4_1_7_to_4_1_3

WAAS_Downgrade4_1_7_to_4_1_3b

Step 8 Enable the CMS service by using the cms enable global configuration command.

(config)# cms enable


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.

Operating Considerations

This section includes operating considerations that apply to software versions 4.1.7x:

Interoperability

Configuring Router Buffer Size

Virtual Blade Configuration From File

Device Group Default Settings

Using Autoregistration with Port-Channel Interfaces

WAFS Support of FAT32 File Servers

Preposition Jobs and CIFS Accelerator Restart

Interoperability

This section discusses operating considerations when operating a WAAS network that mixes version 4.1.7x devices with devices running earlier software versions.

WAAS version 4.1.7x does not support running in a mixed version WAAS network where any WAAS device is running a software version lower than 4.0.13. If you have any WAAS devices running version 4.0.11 or earlier, you must first upgrade them to version 4.0.13 (or a later version), before you install version 4.1.7x. You should first upgrade any WAEs to version 4.0.13 (or a later version) and then upgrade any WAAS Central Managers to version 4.0.13 (or a later version).

In a mixed version WAAS network with version 4.1.7x, the WAAS Central Manager must be running the highest version of the WAAS software.

When a WAAS Central Manager is upgraded to version 4.1.7x 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.

Configuring Router Buffer Size

Under certain conditions, you may need to increase the IOS buffer size from the default of 18,000 bytes when using mask assignment for load balancing in a WCCP service farm that contains more than 15 WAEs.

You will need to change the buffer size if you see messages similar to the following appearing on the router console:
%SYS-2-GETBUF: Bad getbuffer, bytes= <size> -Process= "WCCP V2 Protocol", ipl= 0, pid= <pid>

These log messages indicate that the messages being generated are larger than the maximum configured buffer size in IOS. This can occur if a large mask assignment is used in combination with a large number of WAEs in the service group.

The configured IOS buffer size must be larger than the number of bytes reported in the log messages. The maximum configurable IOS buffer size is 65,000 bytes, which you can set with the following IOS command on the routers:

Router(config)# buffers huge size 65000

To avoid the need to increase the router buffer size, the number of mask bits set in the WAE WCCP mask assignment configuration can be reduced or the number of WAEs in the farm can be limited. For example, with a default buffer size of 18,000 on the router, a WCCP service group can support 8 WAEs with a mask of 0x7F (7 bits) or 32 WAEs with a mask of 0x7 (3 bits).

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 new device group in WAAS version 4.1.7x, 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 Interfaces

Do not enable the auto-register global configuration command when both interfaces are configured as port-channel interfaces.

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.

Preposition Jobs and CIFS Accelerator Restart

If the CIFS accelerator is restarting due to a power cycle or other reasons, and a preposition job is running during the restart, the job is not resumed and runs again on its next scheduled occurrence.

Software Version 4.1.7b Resolved and Open Caveats

The following sections contain the resolved and open caveats in software version 4.1.7b:

Software Version 4.1.7b Resolved Caveats

Software Version 4.1.7b Open Caveats

Software Version 4.1.7b Resolved Caveats

The following caveats were resolved in software version 4.1.7b.

Caveat ID Number
Description

CSCsv79687

Under certain conditions, WAE may raise actastor_watchdog related alarm

CSCte05426

WAE raises alarm when Machine Self-signed cert is expired or near expiry

CSCtj18726

WAE with HW RAID might lose partition table under certain conditions


Software Version 4.1.7b Open Caveats

The open caveats for software version 4.1.7b are the same as those for software version 4.1.7a. For details, see the "Software Version 4.1.7a Open Caveats" section.

Software Version 4.1.7a Resolved and Open Caveats

The following sections contain the resolved and open caveats in software version 4.1.7a:

Software Version 4.1.7a Resolved Caveats

Software Version 4.1.7a Open Caveats

Software Version 4.1.7a Resolved Caveats

The following caveats were resolved in software version 4.1.7a.

Caveat ID Number
Description

CSCsz75060

CIFS preposition startup-config may not be applied to running-config

CSCsz77214

CIFS preposition tasks does keep retrying if server FQDN is unreachable

CSCta85182

Unable to override device-group policy settings on WAE Re-registration.

CSCtd60131

Device reporting alarm "actastor_watchdog service has been disabled"

CSCte86102

Rarely, preposition root share may get deleted without user intervention

CSCtf70873

CIFS cache may not be updated after offline folder synch with Vista/Win7

CSCth24639

CifsAO CacheDiskSize change may occur after power outage in NME-502

CSCth80229

Win7/Vista client moving file via win explorer may be slow with CIFS AO


Software Version 4.1.7a Open Caveats

The following open caveats apply to software version 4.1.7a.

Caveat ID Number
Description

CSCti05931

CIFS AO: file browsing may fail when user password exceeds 14 characters


The additional open caveats for software version 4.1.7a are the same as those for software version 4.1.7, with the exception of those caveats resolved in 4.1.7a. For details, see the "Software Version 4.1.7 Open Caveats" section.

Software Version 4.1.7 Resolved and Open Caveats

The following sections contain the resolved and open caveats in software version 4.1.7:

Software Version 4.1.7 Resolved Caveats

Software Version 4.1.7 Open Caveats

Software Version 4.1.7 Resolved Caveats

The following caveats were resolved in software version 4.1.7.

Caveat ID Number
Description

CSCsx22929

Outlook2K needs retries to move many msgs from private to public folder

CSCsz18986

Remote Windows installation using MS-DOS client fails

CSCsz74594

Outlook may fail to connect under rare overload cases

CSCsz82196

'show filtering list' may show conns after client/server closed conns

CSCta17638

Winbindd core alarm may be seen during local/windows authentication

CSCta55041

Preposition task may terminate early when preposition size > cache size

CSCtb12760

Device may become unresponsive to telnet/ssh due to nscd

CSCtb13797

HTTP Connections may fail to close under rare circumstances

CSCtb20750

'Unhandled exception' seen under certain conditions on tethereal capture

CSCtb33915

Device reboots after tethereal run for many hours for troubleshooting

CSCtb84428

Concurrent preposition tasks through a DC WAE fail when size exceed 10GB

CSCtb89517

Websense SurfControl "block page" fails to be displayed on browsers

CSCtc39638

Rarely moving 100MB msgs from inbox to public folder slows Outlook

CSCtc52362

Recovery of Windows on Virtual Blade fails when using ssh access on WAE

CSCtc75675

Rarely, under heavy stress load on HTTP AO, WAE may restart

CSCtd50754

Device CMS may rarely fail to process configuration updates from CM

CSCtd67970

In a rare scenario WAE may terminate WCCP processing

CSCtd70935

Extremely rarely MAPI-AO restarts on Outlook session close

CSCte19330

Under rare scenario WAE may stop optimizing traffic and reload

CSCte42826

Pagination not working in the print drivers page under certain condition

CSCte56842

Preposition connections may linger and lead to partial fetch of files

CSCte97139

SSL connections via HTTP proxy not closed in rare conditions

CSCtg28040

File Save/Save As Issues After Installing Microsoft Patch (KB980232)


Software Version 4.1.7 Open Caveats

The following open caveats apply to software version 4.1.7.

Caveat ID Number
Description

CSCtf60675

SMB flow may fail and exception seen with a custom app Cmacntrl

CSCtf87641

Rarely MAPI AO may restart causing Outlook to re-establish connections

CSCtf97106

CIFS acceleration reports graph may show value of '1'

CSCtg17412

CPU monitoring may show higher CPU than actual on multicore CPU devices

CSCtg53099

Win7/Win2008 clients unable to access legacy print-srvces using hostname


The additional open caveats for software version 4.1.7 are the same as those for software version 4.1.5x, with the exception of those caveats resolved in 4.1.5x and 4.1.7. For details, refer to the Release Note for Cisco Wide Area Application Services Software Version 4.1.5x.

WAAS Documentation Set

In addition to this document, the WAAS documentation set includes the following publications:

Cisco Wide Area Application Services Quick Configuration Guide

Cisco Wide Area Application Services Configuration Guide

Cisco Wide Area Application Services Command Reference

Cisco Wide Area Application Services API Reference

Cisco WAAS Installation and Configuration Guide for Windows on a Virtual Blade

Cisco Wide Area Application Engine 511 and 611 Hardware Installation Guide

Cisco Wide Area Application Engine 512 and 612 Hardware Installation Guide

Cisco Wide Area Application Engine 7326 Hardware Installation Guide

Cisco Wide Area Application Engine 7341, 7371, and 674 Hardware Installation Guide

Cisco Wide Area Virtualization Engine 274 and 474 Hardware Installation Guide

Cisco Wide Area Virtualization Engine 574 Hardware Installation Guide

Cisco Network Modules Hardware Installation Guide

Configuring Cisco WAAS Network Modules for Cisco Access Routers

Installing the Cisco WAE Inline Network Adapter

Regulatory Compliance and Safety Information for the Cisco Content Networking Product Series

Regulatory Compliance and Safety Information for the Cisco Content Wide Area Virtualization Engines

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.