Table Of Contents
Release Notes for Cisco ACNS Software, Release 5.5.19
July 4, 2010
Note The most current Cisco documentation for released products is available on Cisco.com.
This release note contains information about the Cisco Application and Content Networking System (ACNS) software version 5.5.19.
Note If you are running ACNS version 5.5.13 we recommend that you upgrade to ACNS version 5.5.19 at your earliest convenience.
This release note contains the following topics:
Dual CPU Support in ACNS-VB
ACNS 5.5.19 supports ACNS-VB on a WAAS virtual blade having dual CPUs. To run ACNS-VB on a WAAS virtual blade supporting dual CPUs, install ACNS version 5.5.19. This release also supports ACNS-VB on a WAAS virtual blade having a single CPU.
ACNS releases 5.5.13 to 5.5.17 do not support ACNS-VB on a WAAS virtual blade host having dual CPUs.
Hardware Platforms Supported in the ACNS Software
Table 1 shows the hardware platforms supported in each ACNS software release. An "X" indicates that the software supports the hardware models listed in that row.
Note The ACNS 5.4.3 release is the required minimum software release for the WAE-512 and WAE-612 appliances. The ACNS 5.3.3 release is the required minimum software release for the WAE-511, WAE-611, and WAE-7326 appliances. The ACNS 5.5.13 release is the required minimum software release for ACNS-VB running on WAAS virtual blade.
Software Component Versions Supported in the ACNS Software
Table 2 describes the integrated SmartFilter and Websense versions that are supported in the ACNS software.
Table 2 Component Versions Supported in the ACNS Software
ACNS Software Release SmartFilter Version Supported Websense Version Supported
1 The integrated Websense Enterprise software Version 5.5 in the ACNS software requires a minimum of 512 MB of RAM. We recommend that you upgrade the RAM on your device to 512 MB or greater, or move your integrated Websense server to another device that has at least 512 MB of RAM. When additional Websense components are enabled (such as the Network Agent), the ACNS software requires a minimum of 1 GB of RAM.
The following software component restrictions apply to the NME-WAE-502:
•On-box SmartFilter is not supported on the NME-WAE-502 running ACNS version 5.5.7 and later.
Off-box SmartFilter is supported on the NME-WAE-502 running ACNS version 5.5.7 and later.
•On-box Websense is not supported on the NME-WAE-502 running ACNS version 5.5.7 and later.
Off-box Websense is not supported on the NME-WAE-502 running ACNS versions 5.5.7 and 5.5.9. Off-box Websense is supported in ACNS version 5.5.11 and later.
Performance is optimal when Websense Enterprise Manager, the Websense Policy Server, and all other Websense components are situated in the same LAN. If all components are not in the same LAN, you may experience communication latency between Websense Enterprise Manager and other components. A significant increase in latency may lead to a communication failure.
Software Version 5.5.19 Resolved and Open Caveats
The following sections list the resolved and open caveats in the ACNS 5.5.19 release.
Software Version 5.5.19 Resolved Caveats
This section lists the resolved caveats in the ACNS 5.5.19 release.
•CSCtg30080—Adding a server IP address in the device group bypass list is not allowed when it is already present in the bypass list of another device of the same device group. It is not possible to know the exact CE that contains this entry and it requires a time-consuming manual search to know the entry. This issue occurs when a new bypass entry is added to a device group and if any one of the CEs belonging to the same device group has the same entry in its bypass list.
Workaround: Remove the entry from the bypass list of the device before adding it in its device group.
•CSCtg50031—The Darwin server on ACNS aborts while parsing the SDP file during the process of serving the requests to the player. This occurs when the SDP information has "a=control:track" string instead of "a=control:trackID=" string.
Workaround: Edit the SDP file manually on CE and change the string.
•CSCtf08400— The user is unable to apply WCCP configurations immediately after making any changes in interface configurations like changing the interface mtu, disabling /enabling autosense, and so on. This occurs under normal conditions and when the WCCP service is enabled.
Workaround: Wait for approximately 10 seconds after the interface configuration changes are applied.
•CSCte39240—wmt_be aborts when the data object is null due to a corrupted ASF header. This occurs when WMT streaming is enabled.
•CSCtf24885— WCCP CLIs are getting lost. This occurs when the WCCP CLIs are applied repeatedly and periodically in a short time interval.
Workaround: Manually reconfigure the lost CLIs.
•CSCte91977—The CLI sh stat rule pattern-list all displays a truncated output. This occurs when the device is subjected to a high load.
•CSCtf30342—ACNS versions 5.5.17 and earlier use an outdated OpenSSH-portable package that is affected by CVE-2003-0190.
Software Version 5.5.19 Open Caveats
This section lists the open caveats in the ACNS 5.5.19 release.
CSCtf25331—Data transfer towards an HTTP client may get terminated by TCP RST. This occurs when client site persistent connections are disabled and when the client uses HTTP pipelining.
Workaround: Enable client side persistence or disable pipelining at the client.
•CSCtf69461—In a rare scenario, wmt_be gets aborted in the device.
•CSCtf71188— The CLI sh stat rule pattern-list all displays wrong rule hit count values in systems having multiple CPUs. This occurs when the device has more than two CPUs.
Note The issue with wrong stat values in dual CPU systems was resolved in CSCte91977.
•CSCtg27425—In a rare scenario, wmt_be gets aborted due to lack of memory. This occurs when wmt_be is trying to play a file.
•CSCtg65838—The video plays partially only. This occurs when ACNS with WMT streaming is enabled and HTTP is the allowed protocol.
Workaround: Disable HTTP for WMT.
•CSCth30982— Unable to install ACNS-VB when device disk Virtio is configured with the virtual blade.
Product Documentation Set
In addition to this release note, the following document types are included in the product documentation set. An online help system is included in the product software.
•Cisco Wide Area Application Engine 7341, 7371, and 674 Hardware Installation Guide
•Cisco Wide Area Application Engine 7326 Hardware Installation Guide
•Cisco Wide Area Application Engine 512 and 612 Hardware Installation Guide
•Cisco Wide Area Application Engine 511 and 611 Hardware Installation Guide
•Installing Hard Disk Drives in the Cisco Wide Area Application Engine 611
•Installing the Cisco WAE Inline Network Adapter
•Regulatory Compliance and Safety Information for the Cisco Content Networking Product Series
•Cisco WAAS Installation and Configuration Guide for ACNS on a Virtual Blade
•Cisco ACNS Software Upgrade and Maintenance Guide, Release 5.5.13
•Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.5.13
•Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.5.13
•Configuring Cisco Access Routers and the NME-WAE Network Module for ACNS Deployments
•Cisco ACNS Command Reference, Release 5.5.13
•Cisco ACNS Software API Guide, Release 5.5
The Content Distribution Manager GUI and the Content Engine GUI both have context-sensitive online help that can be accessed by clicking the HELP button. ACNS software includes the following online help systems:
•Content Distribution Manager GUI online help system for centrally managed ACNS networks
•Content Engine GUI online help system for locally deployed Content Engines
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2009-2010 Cisco Systems, Inc. All rights reserved.