Table Of Contents
Release Note for Cisco ACNS Software, Release 5.4.5
Hardware Platforms Supported in ACNS Software
Software Component Versions Supported in ACNS Software
Multicast-In Sources in SSPLs Not Supported for Windows Media Streaming
No Downgrade Script to ACNS Releases Later than 5.3.3
RAM Requirements for ACNS 5.4 Software and Websense 5.5 Software
Websense Issues When Downgrading to the ACNS 5.0 Software or ACNS 5.1 Software
Media File System Issues When Downgrading to ACNS 5.0 Software
SmartFilter Issues When Upgrading or Downgrading to Another ACNS Software Release
Interoperability with ICAP Vendors
ICAP Maximum File Size Supported
Matrix of Supported Caching, Filtering, and Authentication Methods
Open Caveats in Software Version 5.4.5
Resolved Caveats in Software Version 5.4.5
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Note for Cisco ACNS Software, Release 5.4.5
October 30, 2007
Note
The most current Cisco documentation for released products is available at Cisco.com at http://www.cisco.com. The online documents may contain updates and modifications made after the hardcopy documents were printed.
Contents
This release note document contains information about the Cisco Application and Content Networking System (ACNS) 5.4.5 software. This release note describes 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.
This release note document is intended for administrators who will be configuring, monitoring, and managing devices that are running the ACNS 5.4.5 software. This document describes the new product features, the supported hardware, and the open and resolved caveats regarding the ACNS 5.4.5 software release.
Hardware Platforms Supported in ACNS Software
The ACNS software runs on Cisco Content Engine, Content Distribution Manager, Content Router, and Wide Area Application Engine (WAE) hardware platforms.
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.
Table 1 shows the hardware platforms and the minimum ACNS software release in which each is supported. An "X" indicates that the software supports the hardware models listed in that row.
Software Component Versions Supported in ACNS Software
Table 2 describes which 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
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), ACNS software requires a minimum of 1 GB of RAM.
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 might experience communication latency between Websense Enterprise Manager and other components. A significant increase in latency can lead to a communication failure.
New Command in ACNS 5.4.5
Table 3 describes the new command added in the ACNS 5.4.5 software release.
Operating Considerations
This section describes operating considerations for ACNS 5.4.x software. It includes the following sections:
•
•
•
•
•
•
•
•
•
Multicast-In Sources in SSPLs Not Supported for Windows Media Streaming
Multicast-in source objects in server-side playlists are not supported for Windows Media streaming. If you have such an unsupported configuration, the Windows Media stream will fail, and the problem will be identified in the syslog file, as shown in the following example:
Jul 9 21:30:09 new-stream-ce2-158-3 mms_server: %CE-WMT-2-512078: Multicast-in with SSPL source is not supportedNo Downgrade Script to ACNS Releases Later than 5.3.3
There is no downgrade script in the ACNS 5.4 code base to downgrade directly to ACNS 5.3.x releases that are later than ACNS 5.3.3. To downgrade from ACNS 5.4 software to ACNS 5.3.x software you must use the following guidelines:
•
•
•
RAM Requirements for ACNS 5.4 Software and Websense 5.5 Software
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.
Websense Issues When Downgrading to the ACNS 5.0 Software or ACNS 5.1 Software
If the local (internal) Websense server is enabled on the Content Engine and you downgrade from the ACNS 5.2.x software to either ACNS 5.0 software or ACNS 5.1 software, the WebsenseEnterprise directory is removed from the Content Engine and the local Websense server stops working. The ACNS 5.2.x software does not generate an error message indicating that the WebsenseEnterprise directory has been removed. However, in the ACNS 5.3.1 software and later releases, the following error message is displayed to notify you about this Websense downgrade issue:
WARNING:Websense does not support downgradeHence removing /local/local1/WebsenseEnterpriseWebsense will stop working after copy ftp installTo avoid this problem when downgrading from the ACNS 5.3.x or ACNS 5.2.x software to either ACNS 5.1.x software or ACNS 5.0.x software, follow these steps:
Step 1
Step 2
Step 3
Media File System Issues When Downgrading to ACNS 5.0 Software
If you have configured the media file system (mediafs) with the ACNS 5.1 software and later releases, and then downgrade to the ACNS 5.0 software, the mediafs disk space assignment is lost and reverts to the ACNS network file system (cdnfs) disk space. (The mediafs is used for on-demand content that is fetched through the two streaming protocols [RTSP and WMT]. The cdnfs is used for pre-positioned content in the ACNS network.)
This situation occurs because of a design change that was implemented in the ACNS 5.1 software. Because the ACNS 5.0 software is not compatible with this change, the disk space becomes assigned to cdnfs instead of mediafs. To work around this problem, follow these steps:
1.
Use the Content Distribution Manager GUI for Content Engines that are registered with a Content Distribution Manager. Use the Content Engine GUI for standalone Content Engines (Content Engines that are not registered with a Content Distribution Manager and are being managed through the Content Engine GUI or CLI).
2.
SmartFilter Issues When Upgrading or Downgrading to Another ACNS Software Release
When you upgrade or downgrade the Content Engine to a different release of the ACNS software, if there is a difference in the SmartFilter plug-in version, the SmartFilter database and configuration files are deleted and default configurations are loaded. This change occurs because the configuration details might be changed with each new version of SmartFilter software. After each upgrade or downgrade of the SmartFilter plug-in, a fresh database has to be downloaded from the SmartFilter Administration Console to the Content Engine. (For a description of which SmartFilter versions are supported in the ACNS software releases, see Table 2.)
Interoperability with ICAP Vendors
The Internet Content Adaptation Protocol (ICAP) is an open standards protocol for content adaptation, used typically at the network edge. Content adaptation includes virus scanning, content translation, content filtering, content insertion, and other methods of improving the value of content to end users. ICAP specifies how a Content Engine, acting as an HTTP proxy server, can communicate with an external device that is acting as an ICAP server to filter and adapt the requested content.
ICAP provides two content-processing modes for HTTP services. These modes define the transactions that can occur between a Content Engine acting as an ICAP client and an ICAP server. The two modes are as follows:
•
•
The following is a complete list of the ICAP vendors that have been certified to interoperate with the Content Engine:
•
•
ICAP Performance
With the respmod vectoring point, which is used by virus-scanning ICAP vendors, the performance of the Content Engine model CE-7305 will be 300 transactions per second.
With the reqmod-precache vectoring point, which is used by URL filtering ICAP vendors, the performance of the Content Engine model CE-7305 will drop 20 percent from the rated performance.
The performance of the Content Engine will be limited by the performance of the ICAP server.
ICAP Maximum File Size Supported
For ACNS 5.4.x software and later, the maximum file size that is supported in the ACNS software is 2 GB. Files that exceed this size limit are not supported for ICAP processing.
Matrix of Supported Caching, Filtering, and Authentication Methods
Table 4 lists the caching, filtering, and authentication methods supported by Content Engines that are running the ACNS 5.4.x software. An asterisk (*) indicates that a feature is supported for that particular protocol.
Open Caveats in Software Version 5.4.5
This section lists the open caveats in software version 5.4.5.
•
Symptom: Content cannot be acquired using strong authentication from secure origin servers that use certificates from nonstandard certificate authorities (CAs). If strong authentication is chosen for content acquisitions from such a site, the acquirer error statistics will contain a 401 (Unauthorized) error code, and the acquirer error log will display 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.
With strong authentication, if any errors occur during certificate verification by the ACNS acquirer, then content from that site will not be acquired. With weak authentication, certain errors are allowed during certificate verification (for example, a certificate has expired, certificate is not yet valid, and a subject issuer mismatch has occurred).
Workaround: Use one of the following 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 will result.
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.
Workaround: Allocate less space to the cfs if a Storage Array is attached to the Content Engine.
•
Symptom: After you downgrade from the ACNS 5.1b300 software to the ACNS 5.0.7b8 software, Windows Media Technologies (WMT) is enabled with no media file system (mediafs).
Condition: This problem occurs when you upgrade from the ACNS 5.0.7b8 to the ACNS 5.1bx software, configure the disk, and then downgrade to the ACNS 5.0.7b4 software.
Workaround: Reconfigure the disk with a mediafs partition and reload the software.
•
Symptom: The Content Distribution Manager only checks if coverage zone files refer to invalid Content Engines after there is a fresh import. When a configuration change causes 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 when a configuration change causes imported coverage zone files to refer to invalid Content Engines.
Workaround: None.
•
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 the location from which SNMP traps are originating.
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, and 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: Even though you entered the url-filter wmt bad-sites-deny global configuration command on the Content Engine, the Content Engine is not filtering requests for content that is pre-positioned in its wmt_vod directory.
Condition: This problem occurs in the following situation:
a.
b.
c.
Workaround: Configure the bad site list using mmst://127.0.0.1/wmt_vod/file.asf instead of mmst://Content Engine IP address/wmt_vod/file.asf.
•
Symptom: A WMT live stream in a managed live event environment is accessible for a period longer than the scheduled duration.
Condition: This problem occurs only when WMT live programs have unicast access enabled. In this situation, if "Auto Delete" is set to true, streams are accessible for a maximum of 24 hours after the last playtime of the event. If "Auto Delete" is set to false, streams are accessible indefinitely.
Workaround: Control the live-stream source through the schedule for the event. Typically, this process involves starting and stopping the WMT encoder.
•
Symptom: The content replication status may show an incorrect number of acquired files.
Condition: This problem may occur if too many channels share the same content (for example, if over 100 channels share the same 30 files in each channel). Even though all 100 channels should show the 30 files that were acquired and distributed, it takes an extended period (days) before the correct manifest item count is displayed.
Workaround: Reduce the number of channels that share the same contents.
•
Symptom: The CPU usage on the Content Engine hits a peak of 100 percent.
Condition: This problem may occur if the internal (local) Websense server is enabled on the NM-CE-BP models.
Workaround: None.
•
Symptom: When you specify foo as a folder URL in the manifest file, and there is a single item redirection from foo to foo/ by the web server, the ACNS acquirer fails to process such redirections and generates a 716 error message. If you are using the quick crawl tool in the Channel Content window, some of the files also report 716 error messages.
Condition: This problem occurs if you are using the quick crawl tool and there is a single item redirect from foo to foo/. However, if foo is a link from a crawl job, single item redirections from foo to foo/ are allowed.
Workaround: Specify foo/ in the manifest file, or specify a crawl job instead of using the quick crawl tool.
•
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 contains more than 50 characters.
Workaround: For NTLM authentication, use a domain controller (DC) that has a domain name with fewer than 35 characters.
•
Symptom: Channel routing causes loops for several Content Engines.
Condition: This problem may occur if there are Content Engines that are running the ACNS 5.1.x software or earlier, and these Content Engines are registered with a Content Distribution Manager that is running the ACNS 5.2.x software.
Workaround: Upgrade the Content Engines to the ACNS 5.2.x software. Currently, a Content Distribution Manager that is running the ACNS 5.2.x software does not propagate some configuration changes to Content Engines that are running an ACNS software release earlier than the ACNS 5.2.x software. Therefore, Content Engines that are running the ACNS 5.1.x software or earlier, may not recognize that the root Content Engine was changed from one Content Engine to another. Consequently, routing loops may develop within the system.
•
Symptom: The CMS service on the Content Distribution Manager cannot start and fails to create the CMS database backup file.
Condition: This problem occurs if the ACNS network configuration is very large (for example, with 2000 configured Content Engines) and the sysfs partition is 2 GB or less.
Workaround: Create a sysfs partition that is greater than 2 GB.
•
Symptom: Microsoft NT LAN Manager (NTLM) authentication occurs even though you disabled it on the Content Engine.
Condition: In rare situations, NTLM proxy authentication remains enabled when you enter the no ntlm server enable global configuration command, although the output of the show running EXEC command shows that the NTLM server is not enabled on the Content Engine.
Workaround: Reenter the no ntlm server enable global configuration command 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 occurs 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: None.
•
Symptom: A cleanup of the sysfs partition removes all pre-positioned RealMedia contents from the /local1/real_vod/ directory on the Content Engine.
Condition: This problem occurs if the sysfs partition is saturated because of the population of content in the real_vod directory.
Workaround: None.
•
Symptom: The WCCP cache farm (a cluster of Content Engines that are running WCCP) is formed using the assignment method even though you specified the mask-assignment assign-method- strict option when configuring the WCCP service.
Condition: This problem occurs if the WCCP cache farm is associated with Cisco routers instead of Cisco switches.
Workaround: None. Mask assignment was only designed for Catalyst 6500 series switches and is not supported by Cisco routers.
•
Symptom: The stream scheduler in the edge Content Engine retrieves stale Session Description Protocol (SDP) information from its forwarder and stores it in its local1/cse_live/ucast folder if the encoding is modified through IP/TV Program Manager. All further RTSP requests are served with this stale SDP content.
Condition: This problem occurs if the stream scheduler retrieves stale SDP information from its forwarder because the program has been edited and the encoding changed for a program. This situation occurs if the Content Distribution Manager notification at the edge Content Engine triggers the stream scheduler before the same occurs at the root Content Engine. Consequently, the edge Content Engine obtains the SDP content from its forwarder, which is valid content at that moment.
Workaround: Reload the Content Engine.
•
Symptom: The Content Engine becomes unresponsive, and commands take 16000 milliseconds or more to execute.
Condition: This problem occurs when the load that is running on the Content Engine is almost as high as the maximum permissible load for a Content Engine, and you then enable ICAP (especially with request modification [REQMOD] transactions). This situation causes the Content Engine to go into an overload state and not recover easily.
Workaround: The load on the Content Engine with ICAP enabled (for the response modification [respmod] transactions) should be kept to 50 percent of the load that it can handle without ICAP.
•
Symptom: A URL in the Synchronized Multimedia Integration Language (SMIL) file that has the "repeatCount" value set may not be requested the number of times specified by the "repeatCount" setting.
Condition: This problem occurs when RealPlayer Version 10 is used. The player exhibits the same behavior regardless of whether a Content Engine exists between the client and the origin server.
Workaround: Use RealOne player instead of RealPlayer Version 10, or request the SMIL file again. The URL will be played at least once in the player.
•
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 when the ICAP service is enabled on the Content Engine.
Workaround: None.
•
Symptom: The cache process on the Content Engine restarts.
Condition: This problem occurs if a large volume of HTTP, HTTPS, and FTP traffic is being directed to the Content Engine operating in transparent mode.
Workaround: None.
•
Symptom: When you enter the write memory command and immediately reload the Content Engine, a prompt appears showing that the configuration has been changed.
Condition: This problem occurs when you perform the following configuration sequence:
a.
b.
c.
d.
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: Unicast access to a live program does not work.
Condition: This problem occurs only when you use special characters ("?" and "#") in the unicast reference URL.
Workaround: To publish a live event, use URLs that do not contain special characters.
•
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 occurs when you perform the following configuration sequence:
a.
b.
c.
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.Condition: This problem occurs when there is a slow connection between the Content Distribution Manager and your browser, and any of the following unsupported actions take place:
–
–
–
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: HTTP VoD file statistics are not being updated correctly.
Condition: This problem occurs if you enter the show statistics wmt requests EXEC command while you are using the HTTP protocol to play a stream. The command output shows the total unicast requests field as 2 but shows the other types of requests (for example, the number of served streaming requests) as 1.
Workaround: Wait until the stream ends before you enter the show statistics wmt requests EXEC command.
•
Symptom: The Websense EIM server that is running on the Content Engine generates a core file.
Condition: This problem occurs when the Websense server is enabled on the Content Engine.
Workaround: No user intervention is required. The Websense server functionality is not affected. After generating a core file, the Websense server restarts automatically, and the functionality is restored.
•
Symptom: If you modify a Content Engine GUI page and reload the page without first clicking the Update button, the new (unsaved) values are displayed on the page instead of the old (saved) values.
Condition: This problem occurs if you are using the latest versions of the Netscape browser (Version 7.0 or later) to access the Content Engine GUI.
Workaround: Go to another Content Engine GUI page, and then return to the same Content Engine GUI page instead of reloading the page. The redisplayed Content Engine GUI page will display the old (saved) values instead of the new (unsaved) values.
•
Symptom: RealPlayer crashes when the streams are switched from the first stream to the second stream.
Condition: This problem occurs if you have set the reconnect as automatic for broadcast redundancy.
Workaround: Set the reconnect as manual instead of 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: None.
•
Symptom: After a client boots and sends the first request from the browser, the NTLM authentication prompt may take approximately two minutes to appear.
Condition: This problem occurs under the following conditions:
a.
b.
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: In a Content Router environment, users are not able to choose RTSPU (UDP) or RTPST(TCP) by requesting with rtspu:// or rtspt:// from their Windows Media players. Another symptom is that an RTSPT stream is returned when an RTSPU stream is requested. A third symptom is that even though you specified the wmt disallowed-client-protocols rtspu global configuration command, it is not preventing clients from being served for a request rtspu://crfqdn/file.asf, which will return an RTSP stream instead of an error.
Condition: This problem may occur if a Content Router is being used for RTSP redirection.
Workaround: None.
•
Symptom: Although you have the transaction log sanitize feature enabled on the Content Engine, the RealProxy or RealServer access logs display the client IP address when it should be hidden.
Condition: This problem is caused because the transaction-logs sanitize CLI command is not working properly for the RealProxy and RealServer.
Workaround: None.
•
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 containing 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 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 occurs under the following two conditions:
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 acquirer experiences a problem when accessing files from the Samba share.
Condition: This problem occurs when the following two conditions exist:
1.
2.
Workaround: The Network Appliance file server that is running a version older than 7.0 has problems with the Samba versions used in ACNS 5.3 and later. Upgrade the Network Appliance file server to version 7.0 or higher or downgrade ACNS to version 5.2.
•
Symptom: The Websense Manager cannot connect to the local (internal) Websense server that is running on the Content Engine, and clients receive the following error: "Failed to connect, the server is not yet fully started. please try again in a little while".
Condition: This problem occurs if a standby IP address is used on both the primary and secondary interfaces, which prevents the Websense Manager from connecting to the Content Engine.
Workaround: Disable the standby IP group and use a single IP address on the interface.
•
Symptom: The firewall shows that there is an excessive amount of traffic originating from the Content Engine over TCP port 8999.
Condition: This problem occurs when 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 client inside the firewall with a source port of TCP 8999 going to the NAT address of the client.
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 Websense Manager cannot connect to the Websense server that is running as a separate process on the Content Engine instead of running on a separate system.
Condition: This problem occurs if an external IP address is used from the Websense Manager to connect to the local Websense server that is running on the Content Engine.
Workaround: None.
•
Symptom: There is a local Network Agent core file on the Content Engine. The local Network Agent is one of the services of the local Websense server and runs on the Content Engine.
Condition: This problem occurs when the local Network Agent is enabled on the Content Engine.
Workaround: None.
•
Symptom: The Websense GUI does not contain an option for configuring the Winix NTLM Settings (Windows NT Directory/Active Directory [Mixed Mode]).
Condition: The problem may 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 occurs when the content has been pre-positioned on the Content Engine.
Workaround: None.
•
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 Microsoft presenter was used 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, select publish to My Computer and when you select 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: 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: 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: None.
•
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 when 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 when you enter the no rule enable command and 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: Reboot the Content Engine.
•
Symptom: Websense logging on the Content Engine does not show the usernames for LDAP/NTLM queries.
Condition: This problem occurs if the Content Engine is running the ACNS 5.3.x software release or a later software release.
Workaround: Downgrade the Content Engine to the ACNS 5.2.x software or an earlier software release.
•
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 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: The Content Router does not redirect requests to Content Engines in less specific network routes when all Content Engines in the more specific network routes have reached their load threshold.
Condition: This problem occurs when all of the following conditions exist:
–
–
<coverageZone><network>10.86.0.0/16</network> -----> More specific network route<CE>ce1</CE><metric>10</metric></coverageZone><coverageZone><network>10.77.0.0/16</network> -----> More specific network route<CE>ce2</CE><metric>10</metric></coverageZone><coverageZone><network>10.0.0.0/8</network> -----> Less specific network route<CE>ce3</CE><metric>10</metric></coverageZone>Content Engine ce3 is configured to serve the network 10.0.0.0/8 which is less specific to the network 10.86.0.0/16 served by Content Engine ce1 and 10.77.0.0/16 served by Content Engine ce2.
–
–
Workaround: The coverage zone file should be reconfigured in such a way that all Content Engines serving the less specific network route should be configured for the more specific network route with a higher metric value, as shown in the following example:
<coverageZone><network>10.86.0.0/16</network> -----> More specific network route with lower metric<CE>ce1</CE><metric>10</metric></coverageZone><coverageZone><network>10.77.0.0/16</network> -----> More specific network route with lower metric<CE>ce2</CE><metric>10</metric></coverageZone><coverageZone><network>10.86.0.0/16</network> -----> More specific network route with higher metric<CE>ce3</CE><metric>20</metric></coverageZone><coverageZone><network>10.77.0.0/16</network> -----> More specific network route with higher metric<CE>ce3</CE><metric>20</metric></coverageZone>In this example, Content Engine ce3 (initially configured for the 10.0.0.0/8 network route) is now configured for both the more specific network routes 10.86.0.0/16 and 10.77.0.0/16 with a metric value 20, which is higher than the metric value of 10 configured for Content Engine ce1 and Content Engine ce2.
If the Content Router receives a request from network 10.77.0.0/16, and if Content Engine ce2 has reached its load threshold, the Content Router will redirect the request to Content Engine ce3.
Similarly, if the Content Router receives a request from network 10.86.0.0/16, and if Content Engine ce1 has reached its load threshold, the Content Router will redirect the request to Content Engine ce3.
•
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 occurs 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 occurs when 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: None.
•
Symptom: The Content Engine closes the TCP connection gracefully at the client side, even when the connection is aborted on the server side.
Condition: This problem occurs when the Content Engine is acting as a proxy and the origin server is resetting (RST) the connection due to some failure condition.
Workaround: None. The Content Engine is designed to perform a graceful close on the client end, even if the server closes the connection abruptly by sending a reset.
•
Symptom: The Content Engine hangs and does not authenticate NLTM users or pass traffic. NTLM servers show as DEAD in the show statistics ntlm command output.
Condition: This problem occurs when the Content Engine is running NTLM or other authmod authentication.
Workaround: Restart the authmod process by using the service restart http_authmod command.
•
Symptom: Bypass servers (static or dynamic) are not accessible with WCCP enabled.
Condition: This problem occurs when you use WCCP with an L2 mask assignment on a WCCP router. When a bypass entry is added either dynamically or statically to the Content Engine, then the site is no longer accessible through a browser.
Workaround: None.
•
Symptom: The Content Distribution Manager reports the following error:
Cache service died kernel crash and or user core files detected.Condition: This error occurs after upgrading to ACNS 5.4.1 software.
Workaround: None.
•
Symptom: The dns pin cname global configuration command does not take effect on the Content Engine until after the DNS caching service is restarted.
Condition: This problem occurs when the DNS pin configuration has changed, but the DNS queries do not reflect that configuration change.
Workaround: Disable and then enable the DNS cache by using the dns disable command followed by the dns enable command.
•
Symptom: The ICAP client contacts the DNS server every time before sending the request to the ICAP server.
Condition: This condition occurs because the DNS lookup cannot be disabled.
Workaround: None.
•
Symptom: TVout programs exhibit audio skipping.
Condition: This problem occurs in ACNS builds above 5.1.9.5 and in ACNS 5.4.1, which exhibits video skipping, as well. This problem does not occur in ACNS build 5.1.9.5.
Workaround: Downgrade to ACNS 5.1.9.5 software, which does not exhibit this problem.
•
Symptom: The ACNS 5.3.5 or 5.4.1 software returns an error message when you use "global" as the CIFS sharename.
Condition: This problem occurs when you use either a manifest file or a simple pre-positioned file to map a drive to the pre-positioned content using "global" as the CIFS sharename.
Workaround: Use a sharename other than "global." If you use any name in the configuration other than "global," the drive is able to map successfully.
•
Symptom: DNS cache statistics are not updated. The output for the show statistics dns-cache command does not reflect the actual statistics of DNS caching; however, the DNS caching occurs without any issues.
Condition: This problem occurs when the request is routed using WCCP. When the Content Engine is used as proxy, the statistics are updated properly.
Workaround: None.
•
Symptom: Some show commands disappear from the CLI and stop functioning.
Condition: There is no known condition under which this problem occurs.
Workaround: Reload the Content Engine to restart the parser server.
•
Symptom: Core files are detected in the dispatcher.
Condition: This problem occurs when the Content Engine is running CSM.
Workaround: None. The Content Engine recovers on its own immediately.
•
Symptom: The Windows Media managed live program begins one hour later than scheduled or one hour earlier than scheduled.
Condition: This behavior occurs when a program is configured on March 11, 2007 between 1:00 and 7:00 a.m. or on November 4, 2007 between 2:00 and 6:00 a.m. only. This behavior also occurs for programs that are configured on the 2008 daylight savings transition dates and times.
Workaround: During these transition periods, adjust program schedules by one hour to compensate for the time change. For example, if you are configuring the program on March 11, at 6:00 a.m., set the start time in the GUI for one hour earlier. If you are configuring the program on November 4, at 6:00 a.m., set the start time in the GUI for one hour later.
Resolved Caveats in Software Version 5.4.5
This section lists the caveats that have been resolved in software version 5.4.5.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Guest
