Table Of Contents
Release Notes for Cisco ACNS Software, Release 5.5.5
Software Component Versions Supported in ACNS Software
New and Changed Commands in the ACNS 5.5.5 Software
SmartFilter Version 4.1 Integration
About the Temporary User Override Feature
Design Limitation for ACNS Object Transfers
Open Caveats—ACNS 5.5.5 Software
Resolved Caveats—ACNS 5.5.5 Software
2007 Daylight Savings Time Compliance
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco ACNS Software, Release 5.5.5
December 29, 2006
ACNS Release 5.5.5 b4
Revised: March 20, 2008
Note
The most current Cisco documentation for released products is available on Cisco.com.
Contents
This release note contains information about the Cisco Application and Content Networking System (ACNS) 5.5.5 software. This release note contains the following topics:
•
•
Introduction
The ACNS software combines the technologies of demand-pull caching and pre-positioning for accelerated delivery of web applications, objects, files, and streaming media; the ACNS software runs on Cisco Content Engines, Content Distribution Manager, and Content Router hardware platforms, as well as Cisco Wide Area Application Engine appliances.
This release note is intended for administrators who will be configuring, monitoring, and managing devices that are running the ACNS 5.5.5 software. This release note describes the new product features, the supported hardware, and the open and resolved caveats regarding the ACNS 5.5.5 software release.
System Requirements
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
Software Component Versions Supported in ACNS Software
Table 2 describes which integrated SmartFilter and Websense versions are supported in the ACNS software releases.
Table 2 Component Versions Supported in ACNS Software Releases
ACNS 5.2.1
Version 4.0.1
Version 5.2
ACNS 5.3.x
Version 4.0.1
Version 5.2
ACNS 5.4.1
Version 4.0.1
Version 5.5.21
ACNS 5.4.3
Version 4.1.1
Version 5.5.2
ACNS 5.5.1
Version 4.0.1
Version 5.5.2
ACNS 5.5.5
Version 4.1.1
Version 5.5.2
1 The integrated Websense Enterprise software Version 5.5 in the ACNS 5.4 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.
Note
New and Changed Information
This section describes the following new and changed features in the ACNS 5.5.5 software release:
•
•
Websense 6.2 Support
The ACNS 5.5.5 release supports URL filtering using an external Websense server with Websense Version 6.2. To configure your Content Engines for Websense URL filtering in a centrally managed deployment, see the "Using a Websense Enterprise Sever" section. To configure your Content Engines for Websense URL filtering in a locally managed deployment, see the "Configuring Standalone Content Engines for Websense URL Filtering" section.
Note
For more detailed information about configuring the Websense software, go to the following website: http://www.websense.com.
WCCP Layer 2 Return Support
The ACNS 5.5.5 software introduces a new option (l2-return) for the wccp global configuration command that provides Layer 2 packet return support. The Layer 2 return option allows you to override the default Layer 3 GRE return path; packets are returned from the Content Engine to the WCCP-enabled router at Layer 2 instead.
A Content Engine can reject and return packets in the following typical situations:
•
•
•
Note
The packet return method can be configured independently of the packet forwarding method. For example, you can configure the following methods for packet forwarding and packet return:
•
•
The Layer 2 return option is available for all WCCP services listed in the wccp command. Some sample configurations are as follows:
WAE(config)# wccp reverse-proxy router-list-num 1 l2-returnWAE(config)# wccp rtsp router-list-num 1 l2-returnWAE(config)# wccp wmt router-list-num 1 hash-source-port l2-redirect l2-returnWAE(config)# wccp ftp-native router-list-num 1 l2-redirect l2-returnWAE(config)# wccp https-cache router-list-num 1 l2-redirect l2-returnWAE(config)# wccp service-number 91 router-list-num 1 port-list-num 1 application cache l2-redirect l2-returnTo configure the Layer 2 packet return option from the Content Distribution Manager GUI, follow these steps:
Step 1
Step 2
•
•
Step 3
Step 4
Step 5
Figure 1 Enabling Packet Return by Layer 2 Rewrite
Step 6
Step 7
New and Changed Commands in the ACNS 5.5.5 Software
This section describes the new and changed commands in the ACNS 5.5.5 software release. Changes are described for both the command line interface and the Content Distribution Manager GUI.
Table 3 lists the commands and options that have been added in this release.
Table 4 lists the commands and options that have changed in this release.
SmartFilter Version 4.1 Integration
The plug-in for SmartFilter software Version 4.1 has been integrated with the ACNS 5.5.5 software. This version of SmartFilter has the following features:
•
The ACNS caching process listens on port 9015 for blocked pages and forwards the packets to port 9014 where SmartFilter listens.
•
•
Note
About the Temporary User Override Feature
In the ACNS 5.5.5 software release, the temporary user override is a new feature that is available with the SmartFilter software version 4.1. This feature allows the SmartFilter plugin to override the filtering mechanism that is being applied to the user group to which users have been added in the authentication server (in Step 3). You must configure this new feature through the SmartFilter Administrator Console (version 4.1.1).
To use the temporary user override feature, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Design Limitation for ACNS Object Transfers
By design, ACNS software does not handle the transfer of objects larger than 2 GB. When an object transfer reaches the 2-GB limit, the Content Engine closes the connection to both the client and the server.
Caveats
This section lists and describes the new, open, and resolved Severity 1, 2, and 3 caveats in the ACNS 5.5.5 software. Caveats describe unexpected behavior in the ACNS 5.5.5 software. Severity 1 caveats are the most serious; Severity 2 caveats are less serious. Severity 3 caveats are moderate caveats.
This section contains information about the open and closed caveats:
•
•
Open Caveats—ACNS 5.5.5 Software
This section lists caveats that have not been resolved in the ACNS 5.5.5 software release. The open caveats are grouped into the following categories:
Windows Media Open Caveats
•
Symptom: In a Content Router environment, you cannot choose RTSPU (UDP) or RTPST (TCP) when you request rtspu:// or rtspt:// from Windows Media Players. In addition, when you request an RTSPU stream, an RTSPT stream is returned instead. Also, when you specify the wmt disallowed-client-protocols rtspu global configuration command, it does not prevent clients from being served for a request rtspu://crfqdn/file.asf and returns an RTSP stream instead of an error.
Condition: This problem can occur if you use a Content Router for RTSP redirection.
Workaround: The restricted protocol cannot be played; however, as a partial solution, another protocol is chosen instead of returning an error message. We are working to provide a complete solution to this issue.
•
Symptom: When a WMT stream is pre-positioned, the audio works but the playback of embedded slides in the pre-positioned WMT stream are not displayed.
Condition: This problem occurs if you use Microsoft presenter to create a WMT stream that has embedded slides. When this content is pre-positioned, WMT opens and the audio works but the slides never appear.
Workaround: When you are using Microsoft producer to publish the content, choose publish to My Computer. When you choose the Choose publish settings for different audiences option, do not check the Enable rich-media Streaming option. When the content is pre-positioned, all content that is created in publishing should be pre-positioned.
•
Symptom: Camiant server request validation fails for live content when the URL is requested again.
Condition: This problem occurs when the .asx URL is requested again without the browser cache being cleared.
Workaround: Clear the browser cache after every request.
•
Symptom: The RTSP request fails.
Condition: This problem occurs when the publishing point on a Windows Media server is a URL to source content published on a Content Engine, and the Windows Media server is requesting the content using an RTSPU URL (rtspu://).
Workaround: For the above configuration, Microsoft recommends using RTSPT as the protocol for the URL to the remote source (rtspt://).
•
Symptom: The IXIA Windows Media load tool client does not interoperate with ACNS 5.5.x WMT using RTSP.
Condition: IXIA Windows Media load tool clients are not compatible with the ACNS 5.5.x software because the ACNS 5.5.x software does not start sending RTP packets until after it receives the RTSP SET_PARAMETER logconnectstats. The problem does not occur with Windows Media Players because Windows Media Players send the connectstats.
Workaround: Use IXLoad version 3.10 software to allow IXLoad media clients to generate WMT traffic to RealMedia servers. You must configure each IXLoad WMT client manually to set the appropriate parameters.
For example, use the SET_PARAMETER command that was introduced in IXLoad 3.10 to add the set parameter into the client IXLoad stream, and use Option1 as the argument. The IXLoad client will connect to an RTSP Windows Media server and request the content through a Content Engine.
Contact your IXIA support specialist for further IXIA IXLoad support information.
•
Symptom: The RTSPU disallowed counter, in the output of the show statistics wmt error command, does not get incremented when RTSPU is disallowed on the Content Engine. However, the RTSPU request will be blocked.
Condition: This problem occurs with some versions of Windows Media Players 9 and 10.
Workaround: This problem affects statistics only; it does not affect functionality. We are working to resolve this problem.
•
Symptom: The live splitting statistics in the output of the show statistics wmt savings command do not get incremented for broadcast-alias requests.
Condition: This problem occurs only when the broadcast alias is configured with a video on demand (VoD) or a proxy source.
Workaround: There is no known workaround at this time. We are working to resolve this problem.
•
Symptom: Windows Media Player displays "Attempting to reconnect" when playing server-side playlists that contain multi-bit-rate (MBR) streams using RTSP.
Condition: When playing a server-side playlist using RTSP, the Windows Media Player requests an MBR stream switch because of insufficient bandwidth and then later requests the next entry in the server-side-playlist.
Workaround: Start the play again.
•
Symptom: More outgoing bandwidth is consumed than expected.
Condition: This problem occurs when Fast Cache (FC) is enabled on the client and on the Content Engine. Because FC is supported only for cache-hit cases, the outgoing bandwidth should be calculated with consideration for FC for cache-hit cases only. (Outgoing bandwidth is calculated with consideration for FC because data is sent at a higher rate when FC is enabled on the client and on the Content Engine.) However, this problem occurs because the outgoing bandwidth is being calculated with consideration for FC even for cache-miss cases.
Workaround: There is no known workaround. The bandwidth allocation is reset as soon as playback ends for that stream.
•
Symptom: A PacketVideo player cannot play back a Helix Mobile Producer-encoded media file.
Condition: This problem occurs when the files are pre-positioned. This problem does not occur if the QuickTime player (Version 6.0.5 or Version 7.0.2) is used to play back the files.
Workaround: Use a QuickTime player instead of a PacketVideo player.
•
Symptom: Outgoing bytes are not getting incremented in a timely fashion.
Condition: Outgoing byte statistics are incremented in the CLI only when control events (such as pauses or stops) occur on active streams. This condition occurs during VoD, proxy, or live playback for Windows Media streams.
Workaround: Click any control event, such as pause, and then view the bytes being incremented by using the show statistics wmt bytes outgoing EXEC command.
•
Symptom: The remote HTTP source counter increments for the multicast-in source.
Condition: When a multicast-in source is used for a broadcast alias in the Content Engine, then the By Source of Content field in the show statistics wmt requests command output shows the remote HTTP counter incrementing instead of the multicast counter. This condition is seen in the ACNS 5.5.x software.
Workaround: There is no known workaround. This problem does not impact the performance of this product. We are working to resolve this problem in a future release.
•
Symptom: Even when a multicast station is removed from the Content Engine, the Current field of the Number of Concurrent Active Multicast Sessions section in the show statistics wmt multicast command output shows a value. The field is not cleared even after you enter the clear statistics wmt command. This problem does not affect the core functionality.
Condition: This condition can occur when a multicast station is stopped and removed from the Content Engine.
Workaround: There is no known workaround at this time. We are working to resolve this problem.
•
Symptom: The incoming bandwidth does not restrict the multicast source.
Condition: This condition occurs when an RTSP source is directed to the multicast station.
Workaround: An HTTP source can be used for the multicast station.
•
Symptom: The outgoing bytes keep incrementing.
Condition: When a multicast station is started and stopped quickly 10 times or more, the Outgoing Bytes field of the show statistics wmt multicast command keeps incrementing even though multicasting is stopped. Also, the Aggregate Multicast-out Bandwidth field is not cleared until the WMT program is restarted.
Workaround: Avoid rapid multiple starts and stops during a WMT multicast program.
•
Symptom: The Windows Media Player stays in the buffering state.
Condition: A stream encoded with video only is played using RTSPU (that is, either the URL is rtspu:// or the URL is rtsp://), and the player advanced statistics indicate that the protocol in use is RTSP (UDP).
Workaround: Use the RTSPT protocol as the protocol for the URL (rtspt://).
•
Symptom: The Windows Media Player stays in the buffering state and then disconnects.
Condition: In a very high-latency network (>100 ms), when playback is over RTSP (UDP) for a multi-bit-rate stream, retransmission requests can lag behind and cause this problem.
Workaround: Request the file stream again. Reduce the latency in your network. Use rtspt:// in the URL.
•
Symptom: The Content Engine sends a 500 error message to one of the clients during a live split of a managed live unicast program.
Condition: This error occurs when the source for the program is an SSPL.
Workaround: The user on the client that receives a 500 error message should request the program again.
•
Symptom: The incoming bandwidth usage statistics for broadcast server-side-playlists continue to increment.
Condition: This problem is seen when there are more than 100 requests for a server-side-playlist that switches streams every 1 minute. This condition is not seen for a lower number of requests.
Workaround: There is no known workaround at this time. We are working to resolve this problem.
•
Symptom: The player goes into the buffering state and hangs.
Condition: This problem occurs during a multicast-in-multicast-out play forever program after the end of the first loop.
Workaround: Use the encoder source content instead of the VoD content.
•
Symptom: The Windows Media Player attempts to reconnect when it reaches an end of stream (EOS) of the broadcast alias.
Condition: This condition occurs only when a multicast stream is used as the source for the broadcast alias in the Content Engine.
Workaround: Use unicast instead of multicast as the source for your broadcast alias. We are working to resolve this problem.
•
Symptom: The Content Engine appears to be in a hung state and does not respond to ping, Telnet, or to requests.
Condition: This condition occurs when a Content Engine receives 200 live-splitting requests for a combination of fast-switching server-side playlists that have streams switching every 1 minute and that have their multi-bit-rate encoder source encoded with 8 different bit rates.
Workaround: Stop incoming requests from clients. If the software does not recover, reload the Content Engine.
•
Symptom: The wmt_be process generates a core file during the server_parse phase.
Condition: This problem occurs during VoD stress testing for pass-through content when you use the Windows Media load simulator.
Workaround: There is no known workaround. If this problem occurs, save the core files and the WMT error logs to assist TAC in further debugging the problem.
•
Symptom: The wmt_be process generates a core file.
Condition: This problem occurs during stress testing of a managed live unicast out-only program with a live SSPL source.
Workaround: There is no known workaround. If this problem occurs, save the core files and the WMT error logs to assist TAC in further debugging the problem.
•
Symptom: The wmt_be process hangs in the read phase, and outgoing bandwidth is not fully released.
Condition: This problem occurs during proxy VoD stress testing after two to three hours of testing.
Workaround: Use the clear wmt incoming (outgoing) command to clear the session.
•
Symptom: The wmt_be sessions are not exiting properly, and outgoing bandwidth is not released.
Condition: This problem occurs during proxy VoD stress testing when you use the Windows Media load simulator.
Workaround: Use the clear wmt incoming (outgoing) command to clear the session.
Other Open Caveats
•
Symptom: Content cannot be acquired using strong authentication from secure origin servers that use certificates from nonstandard certificate authorities (CAs). If strong authentication was chosen for content acquisitions from such a site, the acquirer error statistics will contain a 401 (Unauthorized) error code, and the acquirer error log contains the following error message:
Strong Cert Authentication rejects certificate due to error: ssl error codeCondition: This problem occurs if the origin server uses a certificate that is not known as a standard certificate to the ACNS software acquirer. For content acquisition from secure sites over HTTPS using strong authentication, only sites with certificates from standard certificate authorities are supported.
Note
Workaround: Use one of these workarounds:
–
–
•
Symptom: When a Content Engine model CE-565 is attached to a Storage Array SA-7 device, if too large a cache file system (cfs) partition is configured, and a combined streaming and caching workload is used, then a lower HTTP performance is observed.
Condition: This problem occurs when the CE-565 has Windows Media Technologies (WMT) enabled, a combined streaming and caching workload is used, and the Content Engine is attached to an SA-7 device.
Note
Workaround: Allocate less space to the cfs if a Storage Array is attached to the Content Engine.
•
Symptom: The Content Distribution Manager only checks if coverage zone files refer to invalid Content Engines after there is a fresh import. When there is a configuration change that can cause already imported coverage zone files to refer to invalid Content Engines, the Content Distribution Manager does not check or display the correct error message until the next fresh import.
Condition: This problem occurs if there is a coverage zone configuration change that causes already-imported coverage zone files to refer to invalid Content Engines.
Workaround: Whenever the hostname of a Content Engine is changed or the Content Engine is removed from the network, the current information about the device has to be updated in the corresponding coverage zone file or files.
•
Symptom: The Content Engine stops spoofing the client IP address and uses its own IP address to fetch content from the origin server.
Condition: The http l4-switch spoof-client-ip enable global configuration command turns on IP spoofing on a Content Engine that is functioning as a caching engine. When a rule action use-server global configuration command is used, the Content Engine stops spoofing the client IP address and instead uses its own IP address to fetch the content.
Workaround: Remove the rule configurations.
•
Symptom: The network management system (NMS) host does not know where SNMP traps are coming from.
Condition: This problem occurs if there are two interfaces and you configure interface redundancy using both interfaces. You must use a dummy address for the physical addresses. You then configure a real address that floats between the two interfaces. If you then configure SNMP traps, the traps are being sourced from the dummy address and not the routable address. Therefore, the NMS host does not know where the trap is coming from.
Workaround: Configure the Content Engine to generate SNMP version 2c type trap messages. Because the SNMP version 2c trap message does not contain the IP address of the SNMP agent, the NMS software will use the source IP address of the UDP message to identify the address of the SNMP agent.
•
Symptom: Microsoft NT LAN Manager (NTLM) authentication fails and the pop-up window is displayed again.
Condition: This problem occurs if NTLM authentication is being used and the specified domain name is longer than 50 characters.
Workaround: For NTLM authentication, use a domain controller (DC) that has a domain name shorter than 35 characters.
•
Symptom: Microsoft NT LAN Manager (NTLM) authentication occurs even though you disabled it on the Content Engine.
Condition: This problem occurs very rarely. In very rare situations, even though you entered the no ntlm server enable global configuration command to disable NTLM proxy authentication on the Content Engine, NTLM proxy authentication is still not turned off. In such cases, NTLM authentication can still occur, although the output of the show running EXEC command shows that the NTLM server is not enabled on the Content Engine.
Workaround: Enter the no ntlm server enable global configuration command again on the Content Engine.
•
Symptom: The ICAP service is enabled on the Content Engine, but the Content Engine is unable to retrieve the content.
Condition: This problem can occur if the Content Engine is running the ACNS 5.x software, and you configure two or more ICAP services to subscribe to the same vectoring point (the response modification [RESPMOD] vectoring point).
Workaround: Currently, we do not have a workaround for this problem. This problem has not been seen in any of our customer sites; the scenario was assumed by our testing team in an attempt to support this scenario in future releases based on the need.
•
Symptom: An HTTP 1.0 request that is received by the Content Engine from a client web browser is sent as an HTTP 1.1 request by the Content Engine to the origin server.
Condition: This problem occurs only when the ICAP service is enabled on the Content Engine.
Workaround: Currently, we do not have a workaround for this problem. This problem has not been seen in any of our customer sites; the scenario was assumed by our testing team in an attempt to support this scenario in future releases based on the need.
•
Symptom: Even though you entered a write memory command, after an immediate reload, a prompt appears that the configuration has been changed.
Condition: This problem occurs if the following conditions are met:
–
–
–
–
Workaround: Note that ACNS functionality is not affected if this problem occurs. However, if a prompt appears stating that the configuration has been changed, enter yes to save the configuration.
•
Symptom: The proxy autoconfiguration file is missing from the Content Engine after you switch from group settings to device settings, and then switch back to group settings.
Condition: This problem can occur in the following condition:
a.
b.
c.
The autoconfiguration file is not found but the proxy autoconfiguration feature is shown as enabled.
Workaround: Return to the device window in the Content Distribution Manager GUI, delete the values from the proxy autoconfiguration fields in the device window, and then select device group from the drop-down menu.
•
Symptom: When using the quick start tool in the Content Distribution Manager GUI, if you repeatedly click the Add-Router to List button before the window completely loads in your browser, the following message appears in your browser:
The system had trouble processing your last request.This situation can occur under the following circumstances:
–
–
–
Condition: This problem occurs only when there is a slow connection between the Content Distribution Manager and your browser and you perform any of the unsupported actions described above.
Workaround: Return to the Content Distribution Manager GUI and wait until the window is completely loaded in your browser before you click the Add-Router to List button.
•
Symptom: RealPlayer crashes when the streams are switched from the first stream to the second stream.
Condition: This problem can occur if you have set the reconnect as automatic for broadcast redundancy.
Workaround: Set the reconnect as manual instead as automatic.
•
Symptom: The Internet Explorer client retrieves a partial (incomplete) customized error page and displays it along with some partial HTML code.
Condition: This problem occurs if a customized error page is configured on the Content Engine and an Internet Explorer client requests a nonexistent HTTPS URL, which causes the customized error page to be returned.
Workaround: There is no known workaround. This problem does not occur with non-IE client browsers.
•
Symptom: NTLM authentication for a valid user may take a longer period than usual (approximately two minutes) if the client sends the request when the Content Engine has been idle for a long period of time.
Condition: This problem can occur in the following condition:
a.
b.
c.
GET http://somehostname/Zone-UVWXYZ/config.cfg HTTP/1.0\r\nRequest Method: GETAccept: */*\r\nUser-Agent: Tioga\r\nHost: somehostname\r\nPragma: no-cache\r\nwhere somehostname is a hostname.
The user will be authenticated after waiting approximately two minutes. After reporting a failure to the browser, the Content Engine uses the same credential and retrieves the group information for that user from its HTTP authentication cache.
Workaround: On the Content Engine, configure a rule to either reject requests from the user agent named Tioga, or configure the no-auth rule to bypass authentication for this user agent.
•
Symptom: The table of contents and the index of the ACNS Content Distribution Manager online help are not functioning. When you open the online help window, the left pane, which contains the table of contents and index, appears blank.
Condition: This problem is caused by the Windows Security Update MS05-001. This security patch prevents the creation of an instance of the HTML Help ActiveX control that is served in HTML content from outside the Local Machine zone.
Workaround: Because the ACNS Content Distribution Manager is part of your internal network, you may modify the Windows registry to allow execution of ActiveX controls that are served from within the intranet zone. For more information on modifying the registry to workaround this issue, refer to Microsoft Knowledge Base article 892675, which is available at this URL: http://support.microsoft.com/kb/892675.
•
Symptom: When you are trying to install the ACNS software on a Content Engine, DMA errors are displayed.
Condition: This problem only occurs under the following condition:
a.
b.
Installer Main Menu:1. Configure Network2. Manufacture flash3. Install flash cookie4. Install flash image from network5. Install flash image from cdrom6. Install flash image from disk7. Wipe out disks and install .bin image8. Exit (and reboot)Choice [0]: 7Workaround: The DMA errors are displayed four to five times in sequence and then the normal operation of the Content Engine continues without any user intervention.
•
Symptom: The firewall shows that there is an excessive amount of traffic coming from the Content Engine over TCP port 8999.
Condition: This problem can occur if the Content Engine is on the outside of the firewall (connected to the internet gateway router). The Content Engine is constantly attempting to reset the connections to the inside with a source port of TCP 8999 going to the NAT address of the clients.
Because the port translation timer has expired on the Content Engine, the Content Engine uses port 8999 to return the message to the client. Because there is no NAT address configured on the firewall with the TCP port 8999, these messages/requests fail at the firewall.
Workaround: Configure the following global configuration CLI commands on the Content Engine:
ContentEngine(config)# http tcp-keepalive enableContentEngine(config)# tcp keepalive-timeout 60ContentEngine(config)# tcp keepalive-probe-interval 60•
Symptom: The system crashes and there are kernel core dumps.
Condition: This problem occurs very rarely.
Workaround: No workaround is required because the Content Engine will reboot and the system will work normally after the reboot.
•
Symptom: There is not an option in the Websense GUI for configuring the Winix NTLM Settings (Windows NT Directory/Active Directory [Mixed Mode]).
Condition: The problem can occur in the following situation:
–
–
Workaround: Reinstall the user service component of Websense on the Content Engine. For example, enter the following two global configuration commands:
ContentEngine(config)# no websense-server service user activateContentEngine(config)# websense-server service user activate•
Symptom: The Content Engine is returning a 200 OK response when it should be returning a 304 message.
Condition: This problem can occur when the content has been pre-positioned on the Content Engine.
Workaround: Although we do not have a workaround, we are working to fix this issue.
•
Symptom: During ICAP REQMOD precache processing, a significant amount of server errors occur.
Condition: The server errors are being generated because the existing connections are closed when the internal connection to the Content Engine receives an error.
Workaround: No workaround is required because even though the clients whose requests are going through the Content Engine will experience one failure to load a page, their attempt to reload a page will succeed.
•
Symptom: The Windows Media Player reports an error when the user attempts to play a URL that requires authorization by the Camiant ICAP server.
Condition: This problem occurs in the following situation. A request fail authorization with the ICAP server occurs, and the Camiant ICAP server has its alternate URL configured as a content-routed FQDN (for example, http://<cr-fqdn>/filename.asf).
Workaround: The Windows Media Player will not report an error and will successfully play the alternate URL that is configured on the Camiant ICAP server if you configure the alternate URL in one of the following formats:
–
–
•
Symptom: After you remove the no-auth rule on the Content Engine, the Content Engine continues to apply the rule even if you enter the no rule enable command and then remove all of the pattern lists.
Condition: This problem occurs if the no auth rule has been configured and then you remove it from the Content Engine.
Workaround: Reload the Content Engine.
•
Symptom: The Windows version of the PacketVideo player does not display video output. The player indicates that buffering is occurring but no video or audio is rendered.
Condition: This problem occurs if the client is a PacketVideo player (a Windows simulator) and the source is a PacketVideo server. (The actual mobile phone-based PacketVideo client plays video/audio properly for the same program.)
Workaround: Use the QuickTime player or a VLC client to view the content from a Microsoft Windows computer.
•
Symptom: At the Content Engine, the client is refused access to the RealProxy client. The Content Engine is also logging the following types of error messages:
Sep 2 11:50:30 prx03 wccp: %CE-WCCP-3-500001: RTSP Proxy may be down, keepalives halted!Sep 2 11:50:30 prx03 rtspd: %CE-WCCP-3-500057: wccp_liveness_update(): Could not send alivemessage (tries 1). SuccessSep 2 11:50:38 prx03 MCM: Plugin MC_REAL_ERRORPLUGIN: 72: Error retrieving URL `broadcast/.../reflector:35134' (Invalid path)Sep 2 11:50:39 prx03 MCM: Plugin MC_REAL_ERRORPLUGIN: 74: Error retrieving URL`broadcast/.../reflector:35137' (Invalid path)Condition: This problem can occur if RealProxy is enabled on a Content Engine that is running the ACNS 5.x software.
Workaround: Reload the Content Engine.
•
Symptom: ACNS pre-positioned downloads are slower than downloads from the origin server. For example, if you download a pre-positioned file from a Content Engine, the maximum download speed is 3.5 Mbps. If you download the same file directly from the origin server, the maximum download speed is 10 Mbps.
Condition: This problem can occur in the following situation. A Content Engine model CE-7305 is running the ACNS 5.3.5 software or a later release and the pre-positioned file is downloaded over a Gigabit Ethernet interface with an HTTP bit rate set to 0 (unrestricted).
Workaround: There is no known workaround. You must upgrade to a version of ACNS 5.4.x software in which this issue has not been seen.
•
Symptom: The DNS pin of a host does not take effect on the Content Engine until you reload the DNS caching service on the Content Engine.
Condition: This problem occurs when the DNS pin configuration has been changed but the DNS queries do not reflect the configuration changes.
Workaround: Disable and enable the DNS cache on the Content Engine.
•
Symptom: The Content Engine does not reflect a change in the IP address of the HTTPS server host.
Condition: This problem occurs when you have changed the IP address for the HTTPS server host FQDN in the DNS server after the HTTPS server host FQDN has been configured to resolve to an IP address on the Content Engine.
Workaround: Enter the https server server_name host FQDN global configuration command on the Content Engine after you have modified the IP address that corresponds to the HTTPS server host FQDN on the DNS server.
•
Symptom: Before sending a request to the Internet Content Adaptation Protocol (ICAP) server, the Internet Content Adaptation Protocol (ICAP) client contacts the DNS.
Condition: This problem occurs when the ICAP feature has been enabled.
Workaround: Although we do not have a workaround, we are working to fix this issue.
•
Symptom: The Content Engine may skip audio and video streams in MPEG2 files.
Condition: This problem occurs in the Content Engine running ACNS versions later than 5.1.9.5.
Workaround: Downgrade to the ACNS 5.1.9.5 software.
•
Symptom: The Content Engine is unable to use a Common Internet File System (CIFS) sharename called global and responds with this error message:
Network name cannot be foundCondition: This problem occurs when you try to map a drive to the pre-positioned content for a manifest file or a simple pre-positioned file with a Common Internet File System (CIFS) sharename called global.
Workaround: Use any other Common Internet File System (CIFS) sharename except global.
•
Symptom: The show stat dns-cache CLI command does not reflect the statistics of the DNS caching.
Condition: This problem occurs when the request is routed through WCCP and the dns-cache statistics command is not updated. The statistics are updated when the Content Engine is used as a proxy.
Workaround: Although there is no known workaround, we are working on a solution to update the statistics in WCCP mode.
•
Symptom: RTSP requests to the Content Router return an RTSP 404 error message. The media file fails to play in the player, and the player displays an error message.
Condition: This problem occurs when the Content Router has more than 100 Content Engines registered in the ACNS network.
Workaround: No workaround is possible with the single Content Router. You must add an additional Content Router to balance the load.
•
Symptom: The Content Engine cache process restarts continuously and creates core dumps.
Condition: This problem occurs when you have ACNS 5.5.5 software on a Content Engine with an external storage array and a CFS partition size that is greater than 440 GB. This defect is not seen on Content Engines running ACNS software prior to the 5.5.5 release. Neither is this defect seen on Content Engines running ACNS 5.5.5 software that are using the internal disk drives because the maximum CFS partition size for internal disks is 384 GB.
Workaround: Reduce the CFS partition size to less than 440 GB.
•
Symptom: Packets for existing connections are not returned to the router, but are dropped. The field, "Packets dropped due to bad buckets" is incremented in the output of the show wccp gre command.
Condition: This problem occurs when you have multiple Content Engines in the farm with a redirection policy mask assigned, a mask value of 0xfd, and a static bypass list configured. The incoming requests are matching the configured bypass list.
Workaround: Configure a different mask value.
Resolved Caveats—ACNS 5.5.5 Software
This section lists the caveats that have been resolved in the ACNS 5.5.5 software release. The resolved caveats are grouped into the following categories:
•
•
•
•
•
•
•
•
•
•
Guest
