Table Of Contents
Release Notes for Cisco ACNS Software, Release 5.0.9
Accessing the SmartFilter Plug-In
Serving HTTP Requests From Windows Media Player 9.0
Media File System Issues When Downgrading to ACNS 5.0 Software
Websense Issues When Downgrading to ACNS 5.0 Software or ACNS 5.1 Software
Open Caveats - ACNS Software, Release 5.0.9
Resolved Caveats - ACNS Software, Release 5.0.9
SmartFilter and the No-Auth Rule Interaction
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ACNS Software, Release 5.0.9
December 31, 2003
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.
Documentation Survey
Is Cisco documentation helpful? Click here to give us your feedback.
Contents
These release notes contain information about ACNS software, Release 5.0.9. These release notes describe the following topics:
•
•
Introduction
These release notes describe supported hardware and open and resolved caveats regarding ACNS software, Release 5.0.9.
System Requirements
The following section lists the hardware platforms that can run ACNS software.
Hardware Supported
ACNS software, Release 5.0.9 supports the following hardware platforms:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Important Notes
This section emphasizes important information regarding ACNS 5.0.x software.
Accessing the SmartFilter Plug-In
ACNS software, Release 5.0.9 requires the SmartFilter Administration Console, Version 3.2.1 to access the SmartFilter plug-in.
Serving HTTP Requests From Windows Media Player 9.0
Content Engines running ACNS software, Release 5.0.9 may not serve HTTP content requests from Windows Media Player 9.0 correctly when the Content Engine has authentication enabled.
Media File System Issues When Downgrading to ACNS 5.0 Software
If you have configured the media file system (mediafs) with ACNS 5.1 software or later, and then downgrade to ACNS 5.0 software, the mediafs disk space assignment is lost and it reverts to 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 ACNS 5.1 software. Because 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 (that is, Content Engines that are not registered with a Content Distribution Manager and are being managed through the Content Engine GUI or CLI).
2.
Websense Issues When Downgrading to 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 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. Note that the ACNS 5.2.x software does not generate an error message indicating that the WebsenseEnterprise directory has been removed.
To avoid this problem when downgrading from ACNS 5.2.x software to ACNS software 5.1 or ACNS 5.0 software, follow these steps:
1.
2.
Install the ACNS 5.1 software or ACNS 5.0 software downgrade image on the Content Engine.
Caveats
This section lists and describes caveats that are open in ACNS software, Release 5.0.9. Caveats describe unexpected behavior in ACNS software, Release 5.0.9. Severity 1 caveats are the most serious; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats.
Open Caveats - ACNS Software, Release 5.0.9
•
Symptom: WCCP bypass does not function properly when bypassing large packets from the client. Therefore, the client never receives an acknowledgment from the server for the data sent.
Condition: This problem occurs when the Content Engine bypasses the connection and the server advertises a maximum segment size (MSS) of 1460 bytes.
Workaround: If the client's path is configured to discover the maximum transmission unit (MTU), users can configure a lower value of MTU on the router interface connected to the Content Engine. Thus, if a client sent a large packet, the router drops it and sends an Internet Control Message Protocol (ICMP) message with the reduced MTU value. Clients can then adjust to the lower value.
•
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 will contain 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 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:
–
–
-----BEGIN CERTIFICATE-----Issuer: C=US, O=VeriSign, Inc., OU=Class 1 Public PrimaryCertification AuthorityValidityNot Before: Jan 29 00:00:00 1996 GMTNot After : Jan 7 23:59:59 2020 GMTSubject: C=US, O=VeriSign, Inc., OU=Class 1 Public PrimaryCertification Authority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=US, O=VeriSign, Inc., OU=Class 2 Public PrimaryCertification AuthorityValidityNot Before: Jan 29 00:00:00 1996 GMTNot After : Jan 7 23:59:59 2004 GMTSubject: C=US, O=VeriSign, Inc., OU=Class 2 Public PrimaryCertification Authority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=US, O=VeriSign, Inc., OU=Class 3 Public PrimaryCertification AuthorityValidityNot Before: Jan 29 00:00:00 1996 GMTNot After : Jan 7 23:59:59 2004 GMTSubject: C=US, O=VeriSign, Inc., OU=Class 3 Public PrimaryCertification Authority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=US, O=RSA Data Security, Inc., OU=Secure ServerCertification AuthorityValidityNot Before: Nov 9 00:00:00 1994 GMTNot After : Jan 7 23:59:59 2010 GMTSubject: C=US, O=RSA Data Security, Inc., OU=Secure ServerCertification Authority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: O=VeriSign, Inc, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab.LTD., OU=For VeriSign authorized testing only. No assurances (C)VS1997ValidityNot Before: Mar 4 00:00:00 1997 GMTNot After : Mar 4 23:59:59 2025 GMTSubject: O=VeriSign, Inc, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab. LTD., OU=For VeriSign authorized testing only. No assurances (C)VS1997-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Queensland, O=CryptSoft Pty Ltd, CN=Test PCA (1024 bit)ValidityNot Before: Dec 2 21:38:51 1999 GMTNot After : Jul 10 21:38:51 2005 GMTSubject: C=AU, ST=Queensland, O=CryptSoft Pty Ltd, CN=Test CA (1024 bit)-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Some-State, O=Internet Widgits Pty Ltd, CN=PCAValidityNot Before: Jun 15 02:14:29 1997 GMTNot After : Jul 15 02:14:29 1997 GMTSubject: C=AU, ST=Some-State, O=Internet Widgits Pty Ltd, CN=CA-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Some-State, O=Internet Widgits Pty Ltd, CN=PCAValidityNot Before: Jun 14 22:54:45 1997 GMTNot After : Jul 14 22:54:45 1997 GMTSubject: C=AU, ST=Some-State, O=Internet Widgits Pty Ltd, CN=PCA-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=GB, O=UCL, OU=ICE-TEL Project, CN=TrustFactoryValidityNot Before: Apr 22 14:39:14 1997 GMTNot After : Apr 22 14:39:14 1998 GMTSubject: C=GB, O=UCL, OU=ICE-TEL Project, CN=TrustFactory-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: O=European ICE-TEL project, OU=V3-Certification AuthorityValidityNot Before: Apr 2 17:35:53 1997 GMTNot After : Apr 2 17:35:53 1998 GMTSubject: O=European ICE-TEL project, OU=V3-Certification Authority,L=Darmstadt-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: O=European ICE-TEL project, OU=V3-Certification AuthorityValidityNot Before: Apr 2 17:33:36 1997 GMTNot After : Apr 2 17:33:36 1998 GMTSubject: O=European ICE-TEL project, OU=V3-Certification Authority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: O=European ICE-TEL project, OU=V3-Certification Authority, L=DarmstadtValidityNot Before: Apr 2 17:35:59 1997 GMTNot After : Apr 2 17:35:59 1998 GMTSubject: O=European ICE-TEL project, OU=V3-Certification Authority,L=Darmstadt, CN=USER-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=Ca, L=Nepean, OU=No Liability Accepted, O=For Demo Purposes Only, CN=Entrust Demo Web CAValidityNot Before: Apr 26 13:35:01 1996 GMTNot After : Apr 26 13:35:01 2006 GMTSubject: C=Ca, L=Nepean, OU=No Liability Accepted, O=For Demo PurposesOnly, CN=Entrust Demo Web CA-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Queensland, O=CryptSoft Pty Ltd, CN=Test PCA (1024 bit)ValidityNot Before: Dec 2 21:35:48 1999 GMTNot After : Jul 11 21:35:48 2005 GMTSubject: C=AU, ST=Queensland, O=CryptSoft Pty Ltd, CN=Test PCA (1024 bit)-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=US, O=RSA Data Security, Inc., OU=Commercial CertificationAuthorityValidityNot Before: Nov 4 18:58:34 1994 GMTNot After : Nov 3 18:58:34 1999 GMTSubject: C=US, O=RSA Data Security, Inc., OU=Commercial CertificationAuthority-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=ZA, ST=Western Cape, L=Cape Town, O=Thawte Consulting cc,OU=CertificationServices Division, CN=Thawte Server CA/Email=server-certs@thawte.comValidityNot Before: Aug 1 00:00:00 1996 GMTNot After : Dec 31 23:59:59 2020 GMTSubject: C=ZA, ST=Western Cape, L=Cape Town, O=Thawte Consulting cc,OU=Certification Services Division, CN=Thawte Server CA/Email=server-certs@thawte.com-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=ZA, ST=Western Cape, L=Cape Town, O=Thawte Consulting cc,OU=CertificationServices Division, CN=Thawte Premium Server CA/Email=premium-server@thawte.comValidityNot Before: Aug 1 00:00:00 1996 GMTNot After : Dec 31 23:59:59 2020 GMTSubject: C=ZA, ST=Western Cape, L=Cape Town, O=Thawte Consulting cc,OU=Certification Services Division, CN=Thawte Premium Server CA/Email=premium-server@thawte.com-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Queensland, L=Brisbane, O=CryptSoft Pty Ltd,OU=development, CN=CryptSoft Dev CAValidityNot Before: Mar 22 13:34:04 1997 GMTNot After : Mar 22 13:34:04 1998 GMTSubject: C=AU, ST=Queensland, L=Brisbane, O=CryptSoft Pty Ltd, OU=development, CN=CryptSoft Dev CA-----END CERTIFICATE----------BEGIN CERTIFICATE-----Issuer: C=AU, ST=Queensland, L=Brisbane, O=CryptSoft Pty Ltd,OU=WORTHLESS CERTIFICATION AUTHORITIES, CN=ZERO VALUE CA - DEMONSTRATION PURPOSES ONLYValidityNot Before: Apr 3 13:22:54 1997 GMTNot After : Apr 3 13:22:54 1998 GMTSubject: C=AU, ST=Queensland, L=Brisbane, O=CryptSoft Pty Ltd,OU=WORTHLESS CERTIFICATION AUTHORITIES, CN=ZERO VALUE CA - DEMONSTRATION PURPOSES ONLY-----END CERTIFICATE-----•
Symptom: When ACNS network users use an external authentication server such as TACACS+, RADIUS, Windows NT LAN Manager (NTLM), or Lightweight Directory Access Protocol (LDAP) for authentication, authorization, and accounting of user accounts, the authentication server settings cannot be changed.
Condition: This occurs in ACNS software, Release 5.0 and later.
Workaround: Users need to remove the authentication server from service when they want to change the settings for any of the external authentication servers, such as TACACS+, RADIUS, NTLM, or LDAP. This can be done using the Local Authentication Settings window or the Authentication Scheme Settings window in the Content Distribution Manager GUI.
•
Symptom: When the user tries to add port 8443 for incoming HTTPS proxy requests on a Content Engine using the https proxy incoming 8443 command, the following message appears:
Port 8443 is reserved for application the Cdm_UI_httpCondition: This problem occurs when port 8443 is reserved for the HTTPS incoming proxy by the Content Distribution Manager GUI and port 8443 cannot be used on a Content Engine where no Content Distribution Manager GUI is running. However, on a Content Distribution Manager, it is appropriate to reserve port 8443, because this port is used as the Content Distribution Manager GUI port.
Workaround: Use a different port that is not reserved. You can check reserved ports using the commands show services port port-number for a specific port or show services summary commands for a collective summary of all used ports.
•
Symptom: For pre-positioned Windows Media content, if the content is defined in the manifest file to be WMT over HTTP play and if NTLM authentication is enabled from the Content Distribution Manager, the Content Engine fails to handle the authentication with the origin server properly. You are repeatedly prompted for a username and password even though you have already entered the proper username and password.
Condition: This occurs in ACNS software, Release 5.0 and later.
Workaround: Choose one of the following options to avoid this problem.
–
–
–
•
Symptom: The cache service unexpectedly restarts after running for 3 months.
Condition: The cache service automatically restarts when it runs for a relatively long time under production traffic.
Workaround: The cache service is automatically restarted by a node manager. Therefore, no special workaround action needs to be performed.
•
Symptom: A multicast receiver Content Engine obtains content through unicast before the multicast sender has delivered the content through multicast.
Condition: This problem occurs when the Content Engine has a parent forwarder, that is not the multicast sender, but which has already received the content. The Content Engine contacts the parent and downloads the content through unicast.
Workaround: Use one of the following workarounds:
–
–
•
Symptom: The CLI does not allow you to assign a device group and reports only the first Content Engine with insufficient space. You might have to try a few times to assign a device group.
Condition: You are using the CLI to assign a device group to a channel, and multiple Content Engines have insufficient space for the channel quota.
Workaround: Either verify which Content Engines have space before you use a CLI command, or make sure that device groups contain similar Content Engines and that Content Engines are assigned consistently to device groups.
•
Symptom: Users receive a DNS failure message when the cache process is unable to resolve the host names presented in the URL.
Condition: DNS failure occurs when users attempt to access a website. However, this symptom is transient and rare.
Workaround: Use the reload function of the browser, although the problem vanishes on its own after a short while.
•
Symptom: An error alert on the system log page indicates a failure to configure an IP address.
Condition: The Content Distribution Manager accepts invalid IP addresses that you enter as the NTLM server for authentication.
Workaround: Make sure that you enter a valid IP address.
•
Symptom: When the user tries to copy a file from the FTP server and install the software release file on the Content Engine, using the copy ftp install {hostname | ip-address} remotefiledir remotefilename command, the following error message appears:
ruby_upgrade: cannot create lock file 'ruby_upgrade.lck' : Permission deniedCondition: This error occurs when the user uses TACACS+ as the login authentication method for device management.
Workaround: There is no known workaround.
•
Symptom: When a user configures certain settings for RealProxy, RealServer, or WMT using CLI commands, the following message appears:
The evaluation has already expiredHowever, when the same settings are configured using the GUI, no error message is displayed, but an error is recorded in the System Message Log window on the Content Distribution Manager GUI.
Condition: This problem occurs when an evaluation license is used and the evaluation period has expired.
Workaround: Purchase and install a permanent license. Do not use the evaluation license anymore.
•
Symptom: If the server responds with a "100 Continue" message to a POST request from the user, the Content Engine stops parsing all requests on the connection, and subsequent requests are not handled properly.
Condition: This symptom occurs in ACNS software, Release 4.2.5 or earlier, and all 5.0.x releases.
Workaround: To partially address the problem with proxy connection, users can upgrade to ACNS software, Release 4.2.7 and later in which ACNS network closes the connection after serving the request. This results in slightly higher latency because of a break in the persistent connection. Known servers respond with the "100 Continue" message to the POST request method only.
•
Symptom: Login and configuration authentication servers can be enabled without your having to configure an IP address or host name. For example, even if no TACACS+ servers are configured, you can still enable login authentication using TACACS+. This can be verified by using the show authentication user and authentication login tacacs enable commands.
Condition: When the disable local login authentication command is used to disable local authentication, the CLI believes that TACACS+ authentication has already been enabled and allows users to disable local authentication for login. In this scenario, the user can never log in to the Content Engine, because there are no configured TACACS+ servers and local authentication is also disabled.
Workaround: There is no known workaround.
•
Symptom: Users cannot play live streaming content from a Windows Media Server that is trying to obtain a stream from a Content Engine broadcast station alias.
Condition: This problem occurs when a Microsoft Windows Media Server is configured to obtain a WMT live stream from the Content Engine. The user's media player receives a "corrupted data" error or "invalid state" error. This problem does not occur if the stream that has been obtained from the Content Engine is not a live stream. The Windows Media Server is failing to retrieve the stream from the Content Engine, which in turn is obtaining the stream from the origin server.
Workaround: There is no known workaround. If possible, users should use a Content Engine to obtain the stream from a Windows Media Server.
•
Symptom: The F1 key might not work with certain terminal settings to access the BIOS menu.
Condition: This symptom only occurs on either the CE-7305 or the CE-7325 only. With certain terminals, the F1 key might not work well because the terminal emulation program might use the F1 key for its own purposes, or send an incorrect F1 key sequence to the Content Engine. Without the F1 key, the user cannot press F1 to access the BIOS menu at system boot time.
Workaround: Tune the terminal emulation program settings, or connect a keyboard and monitor to the Content Engine to access the BIOS.
•
Symptom: When a user enables streaming (RTSP, WMT, and Cisco Streaming Engine) on the Content Engine Network Module from the Content Distribution Manager GUI, some of the streaming configuration settings are lost. These include WMT license key installed, RTSP server real-subscriber accept-license-agreement, rtsp server real-subscriber enable, rtsp proxy media-real enable, rtsp proxy media-real license-key installed, rtsp ip-address rtsp server, and cisco-streaming-engine enable.
Condition: This symptom occurs when the user performs a software upgrade or downgrade after applying the settings.
Workaround: The user must choose the RTSP and WMT settings from the Contents pane on the Content Distribution Manager GUI and resubmit the configurations.
•
Symptom: The Content Distribution Manager GUI shows that an upgrade on a Content Engine has failed when the upgrade has in fact been successful. However, the CLI on the Content Engine shows the correct upgrade information.
Condition: This symptom occurs because the upgrade meta file has the wrong software version. In other words, the version in the meta file does not match the version of the upgrade file.
Workaround: There is no known workaround.
•
Symptom: The Windows Media Player will continue to wait forever to play a media file if the source is a media file that is configured to play in a loop from the Windows Media Server, and if the Content Engine is configured for unicast-in multicast-out multicast delivery of streaming media.
Condition: This occurs only when the source is a Windows Media Server, the media file is configured to loop, and the Content Engine is configured for unicast-in multicast-out.
Workaround: Avoid using a loop file from the Windows Media Server. Users can pre-position the media file to the Content Engine and multicast the file from the local disk before configuring it to play in a loop.
•
Symptom: Content Engine model CE-565 shows lower HTTP performance when attached to and SA-7 Storage Array compared to a CE-565 not attached to an SA-7.
Condition: This problem occurs when the CE-565 has WMT enabled and is attached to an SA-7 Storage Array.
Note
Workaround: Allocate less disk space to the cfs if a Storage Array is attached to the Content Engine.
•
Symptom: When a user submits the WMT Multicast Stations page to the Content Distribution Manager using the Content Distribution Manager GUI, ACNS software displays an error message.
Condition: This problem occurs when there is a leading space entered in the Address field.
Workaround: Return to the WMT Multicast Stations page and resubmit it after entering the address without a leading space.
•
Symptom: Performing a software upgrade or downgrade using the Content Distribution Manager GUI shows the status as updateFailed in the device listing windows, such as the Content Engines window. This failure occurs when the software upgrade or downgrade encounters an error on the target device. Once a request for an upgrade or downgrade is received by the target device, attempts to upgrade or downgrade software occur only once.
Condition: This occurs in ACNS software, Release 5.0 and later.
Workaround: Avoid some of the following common error conditions:
–
–
–
–
If any of the above errors occur, clear that error and request another software upgrade or downgrade using the Content Distribution Manager GUI.
•
Symptom: After thousands of playlist position changes for a playlist that is scheduled to loop playback continuously or for an extended period, the TV-out service might run out of memory. Interruption in playback occurs and core files are generated.
Under some error conditions, such as loss or unavailability of media files on the cdnfs, a playlist might change its position rapidly, thereby exhibiting this behavior after several hours of continuously failed playback.
Condition: This occurs on the CE-507-AV, CE-560-AV, and CE-510 or CE-560 with optional AV decoder card installed, running ACNS software, Release 5.0 or later.
Workaround: Perform any of the following workarounds:
–
–
–
•
Symptom: The Content Engine does not accept the DHCP address and the Centralized Management System (CMS) is not enabled. The Content Distribution Manager therefore indicates that the device is inactive.
Condition: When autoregistration is disabled and reenabled on a Content Engine, the DHCP offer is not accepted because the Content Distribution Manager host name cannot be resolved. This occurs if there is an interface that does not have an IP address through which the Content Distribution Manager host name can be resolved.
Workaround: Do not disable and reenable autoregistration. If you reenable autoregistration, reboot the Content Engine to accept the DHCP offer, and to restart the CMS to register the Content Engine with the Content Distribution Manager.
•
Symptom: The acquirer check-time-for-old-content [channel-id channel_num | channel-name channel_name] EXEC command does not work. The following messages are displayed when the command is used with valid root Content Engine channel ID and names:
ContentEngine# acquirer check-time-for-old-content channel-id 291Unable to get the channel information record for channel= 291This CE is not the root CE for this channel = 291Failed to check the last modified time in DBContentEngine# acquirer check-time-for-old-content channel-name channeltestUnable to get the channel information record for channel= 291This CE is not the root CE for this channel = 291Failed to check the last modified time in DBWorkaround: Use the acquirer check-time-for-old-content EXEC command without the channel ID and channel name options. This command will display the incorrect last modified time for all channels of the root Content Engine.
•
Symptom: A socket write error occurs when a port channel on a nonexistent port channel is disabled using the no interface PortChannel global configuration command.
Condition: This error occurs on the Content Engine models CE-7325, CE-7305, CE-7320, and CE-510, because there is no port channel configuration on these Content Engines.
Workaround: Do not use the no interface PortChannel global configuration command for nonexistent port channels.
•
Symptom: When ACNS software is upgraded, the database upgrade fails because a database table is found to exist already. This appears as an upgrade error in the syslog.txt log file. The Centralized Management System (CMS) does not start on the device, and the device appears as offline in the device listing windows in the Content Distribution Manager GUI.
Condition: If a device is downgraded from ACNS software, Release 5.0.9 to ACNS software, Release 5.0.1, and subsequently deregistered from the Content Distribution Manager and reregistered with the Content Distribution Manager, the local database tables that were created as part of ACNS software, Release 5.0.9 remain in the database. The existence of these tables causes a later ACNS software upgrade to fail.
Workaround: This problem occurs only if the downgraded device is deregistered from the Content Distribution Manager. However, it is also possible to downgrade a device, keep it registered with the Content Distribution Manager, and later upgrade the device. In situations that require the downgraded device to be deregistered from the Content Distribution Manager, the database needs to be cleared of all tables before you reregister the device.
The sequence of CLI commands to deregister and reregister a device is as follows.
1.
2.
3.
The cms deregister command removes the registration information from the Content Distribution Manager and removes known database tables. The cms database delete command removes all tables, including any table that might have been created as part of another ACNS software release. The cms enable command registers the device with the Content Distribution Manager, creates the local database, and starts the CMS processes.
•
Symptom: Installing an upgraded version of ACNS software, Release 5.0.x deletes all content in the existing SmartFilter directory. Therefore, if SmartFilter software was previously installed for URL filtering, installation of a newer version of ACNS software, Release 5.0.x causes filtering to be disabled.
Condition: This symptom occurs if the user installs an upgraded version of ACNS software, Release 5.0.x on a Content Engine running SmartFilter software.
Workaround: SmartFilter, Version 3.1.2 is shipped with ACNS software, Release 5.0.x and contains SmartFilter software policy information stored on remote SmartFilter Administration Servers. Use the SmartFilter Administration Console to reapply the configuration settings on the Content Engine, and manually download the SmartFilter Control List. Once the Control List has been downloaded to the Content Engine, URL filtering will recommence.
•
Symptom: A multi-bit-rate (MBR) media file, after being preloaded, returns a partial cache hit after a proxy-style request.
Condition: This problem was observed with only one MBR media file.
Workaround: There is no known workaround. The media file will be fully cached after a proxy-style request is served.
•
Symptom: When the network experiences significant packet loss, the multicast sender may send a few bytes less than the actual file size. This causes multicast reception to fail on all receivers.
Condition: The network experiences significant multicast packet loss when a multicast session is about to end.
Workaround: In the /local1/multicast-expert-config/ directory, make the following changes in a pgmfx configuration file on the multicast sender:
–
–
On the Content Distribution Manager GUI, set the value of FEC to 16.
•
Symptom: Content Engine AV models are unable to play audio only files.
Condition: This occurs as the Content Engine is looking to synchronize audio and video tracks, but there is no video track.
Workaround: Record the audio-only files with blank video tracks.
•
Symptom: The show websense-server EXEC command shows the number of licensed users as zero.
Condition: The Websense Manager contacts the Websense server when a user enters the license key and expiry date, and tries to download the Websense database from the Websense website. If the Content Engine running the Websense server fails to download the Websense database because of network filtering errors, the show websense-server EXEC command shows the number of licensed users as zero.
Workaround: Configure a Content Engine that can download the Websense database as proxy in the Websense Manager.
•
Symptom: Unicast distribution is temporarily interrupted.
Condition: This occurs when there is no multicast sender configured at the beginning of distribution.
Workaround: There is no known workaround.
•
Symptom: Services do not start in ACNS software, and no message is displayed.
Condition: When a default gateway is not configured, services do not start.
Workaround: Configure a default gateway in the ACNS software GUI.
•
Symptom: All contents are deleted when a new root Content Engine is selected or the old root Content Engine goes offline and a temporary root Content Engine is elected, and if the channel is using a crawl job to acquire contents.
Condition: This problem occurs in ACNS software, Release 5.0.3.
Workaround: Clicking the Refetch button in the Channels window in the Content Distribution Manager GUI causes the new root Content Engine to acquire and distribute the content again.
•
Symptoms: An SNMP query to ccmHistoryEventTable on a Cisco Content Engine returns Management Information Base (MIB) instances with a fixed index. According to the definition of the CISCO-CONTENT-ENGINE-MIB, each new event stored in this table should be assigned a progressive unique index.
Condition: This problem occurs on Cisco Content Engines running ACNS software, Release 5.0.3 or earlier.
Workaround: There is no known workaround.
•
Symptom: When a Content Engine is configured for RADIUS authorization, the Content Engine sends two distinct Access-Requests to the authentication, authorization, and accounting (AAA) server. The second Access-Request is identical to the first, except for the RADIUS ID. This similarity causes problems with One-Time-Password (OTP) servers, which do not accept the second request (carrying an identical password as the first one), and send back an Access-Reject, causing the Content Engine to deny access to the user.
Condition: The problem is observed when users try to log on to the Content Engine using Telnet.
Workaround: There is no known workaround.
•
Symptom: When IP address changes are made on the Content Engine with WCCP enabled, existing connections break, and for 30 seconds new connections are not accepted.
Condition: This problem occurs when users change IP addresses on the Content Engine with WCCP enabled.
Workaround: Disable WCCP before changing IP addresses on the Content Engine.
•
Symptom: The Content Engine displays the following error message:
KERNEL: assertion (atomic_read(&sk->wmem_alloc) == 0) failedCondition: Content Engines display this error message during normal operation.
Workaround: Ignore the error message.
•
Symptom: Users do not receive the web pages they requested, or the web pages load very slowly.
Condition: This problem occurs when the Content Engine does not close an HTTP connection even after receiving a "connection:close" response from the origin server. The Content Engine keeps waiting for the server to close the connection until the connection times out, and the Content Engine does not process subsequent requests, causing delayed responses.
Workaround: Configure a static bypass entry for the origin server that causes the problem.
•
Symptom: The Content Engine GUI loads slowly and some images on the GUI do not load.
Condition: This problem occurs when TACACS+ is enabled as the primary authentication method for login and configuration access to the Content Engine.
Workaround: Use the local user ID with local authentication as the primary authentication method.
•
Symptom: The transaction log shows a cache miss for Range requests for pre-positioned content.
Condition: This problem occurs when a request for pre-positioned content contains HTTP Range request headers.
Workaround: There is no known workaround.
•
Symptom: Users employing a client computer running Windows XP with Windows Media Player 9.0.0.3008 cannot retrieve embedded Microsoft media files (for example, .asf files) over HTTP from a Content Engine that has the media files pre-positioned.
Condition: This problem occurs when all the following conditions exist:
–
–
–
Workaround: Take one of the following actions to avoid this problem:
–
–
–
•
Symptom: The Content Distribution Manager GUI forces users to specify an outgoing proxy when users check the Preserve 407 headers check box in the HTTP Connection Settings window.
Condition: This problem occurs when users try to check the Preserve 407 headers check box in the HTTP Connection Settings window in Content Distribution Manager GUI.
Workaround: Use the http proxy outgoing preserve-407 global configuration command from the CLI to make the required change.
Note
•
Symptom: The administrator cannot configure the TACACS+ client in Content Engine to authenticate administrative users.
Condition: This problem occurs if the TACACS+ encryption key is empty and the TACACS+ server configuration involves a Rivest, Shamir, and Adelman (RSA) token server.
Workaround: Configure the authorization portion of the user account in the TACACS+ server database.
•
Symptom: Users cannot access the Content Engine using the GUI or Telnet, because the root file system partition is full.
Condition: This problem occurs when users deploy rules from the SmartFilter Administration Console.
Workaround: There is no known workaround.
•
Symptom: Users experience long delays while using LDAP for authentication, and they see several prompts before successful authentication.
Condition: This problem occurs when users try to use LDAP for authentication.
Workaround: Try again, and the authentication will succeed.
•
Symptom: The Content Engine does not send SNMP traps when a disk is unreachable or pulled out of the device.
Condition: This problem occurs when SNMP is configured on the Content Engine, and the disk is not reachable or taken out of the device.
Workaround: There is no known workaround.
•
Symptom: Websense filtering stops working when Websense is configured to use custom filters.
Condition: This problem occurs when custom filtering is used in Websense.
Workaround: There is no known workaround.
•
Symptom: When users attempt to edit the list of locations using the Locations window in Content Distribution Manager GUI, an error is generated. The error message indicates that the user might have clicked the Back button or Refresh button in the browser window.
Condition: This problem occurs when there are a large number of locations, and users try to edit locations before the complete list is loaded.
Workaround: Wait for the complete list of locations to be loaded before making any changes.
•
Symptom: No CLI command is available in ACNS software, Release 5.0 and later releases to clear WCCP generic routing encapsulation (GRE) packet-related information. Although a CLI command (show wccp gre) is available to display the WCCP GRE counters, there is no CLI command currently available to clear them.
Condition: This symptom is observed regardless of whether WCCP is enabled or disabled on the Content Engine.
Workaround: There is no known workaround.
•
Symptom: Any changes in the Content Engine's DNS cache configuration do not take effect immediately.
Condition: This situation occurs when the dns listen and dns pin commands are used to configure an IP address and port number to listen for requests and map the IP addresses to their corresponding host names.
Workaround: Use the no dns enable and dns enable commands to disable and enable the Content Engine's DNS caching server, which causes the DNS caching server pick up the changed configurations.
•
Symptom: Under certain conditions, if the user configures one valid and one invalid FTP server for exporting transaction logs, the show statistics transaction-logs command displays the entry for the valid FTP server twice. As a result of the duplicate entry, the counters are not correspondingly incremented with the number of files that are exported through FTP.
Condition: This symptom is observed on Content Engines running ACNS software, Release 5.0.
Workaround: Use the clear statistics transaction-logs command can be used to clear the transaction log export statistics and the duplicate entry for the valid FTP server.
•
Symptom: The client does not receive a requested object if the Websense server is not reachable or if the Websense server timeout value is greater than the configured default timeout value.
Condition: This symptom is observed only under the following conditions:
–
–
–
–
Workaround: Configure a Websense server timeout value must be configured to be less than 60 seconds.
•
Symptom: The Software Update File Registration window in the Content Distribution Manager GUI displays the following error message for a valid meta file URL:
Transaction not completedsun.net.ftp.FtpProtoclException:portCondition: This occurs when the Content Distribution Manager host name contains numeric values. For example, if the software update file URL is 7305.cisco.com, Linux systems encounter problems when Java attempts to resolve the URL to an IP address. This is because only 7305 is considered instead of 7305.cisco.com. As a result, the URL is resolved to a strange IP address, 0.0.28.137 for 7305, causing the Content Distribution Manager GUI to display an error message even though the meta file URL might be valid. This problem also occurs if the update meta file is hosted on an FTP server.
Workaround: Perform one of the following workarounds:
–
–
•
Symptom: If the cdnfs browse EXEC command is used and the filename or the directory name of pre-positioned content contains a space, the command does not display the information contained in the file, nor does it browse through the cdnfs files and directories.
Condition: This occurs in Content Engines running ACNS software, Release 5.0.9.
Workaround: There is no known workaround.
•
Symptom: In the Bandwidth Setting for Device Groups window, when the user tries to navigate to any page (when there are more than 10 bandwidth records) using the pagination counter at the bottom of the page, an error message is displayed.
Workaround: Select All or a number higher than the default value (10) in the Rows field to display the record you want to edit on the first page.
•
Symptom: A pre-positioned content object is lost after you configure the disk and reload the Content Engine.
Condition: If the amount of cdnfs content present is close to the amount of disk space allocated to the cdnfs, then cdnfs content is removed to ensure that the cdnfs file system can be resized properly to hold the saved content. In ACNS software, Release 5.0.x, the content is moved out of the file system (if other file systems that can hold the content are detected), or deleted (if other file systems that can hold the content are not detected) when you perform a disk configuration, if 90 percent or more of the cdnfs file system is used.
Workaround: Perform one of the following tasks to avoid this problem:
–
–
–
Resolved Caveats - ACNS Software, Release 5.0.9
•
The Content Engine prompts the client for authentication when the no authentication rule is set for the website or protocol. This problem occurs when the Content Engine cannot resolve the host name.
•
The Content Engine stops responding and dumps the kernel register. All services are interrupted. This problem occurs on devices that have QLogic adapter installed, and when there is high load on the disk memory. This problem also occasionally occurs under normal circumstances.
•
The Content Engine stops responding while playing a WMT media stream, and users cannot access the Content Engine using a console or terminal. This problem occurs when the client performs a seek operation while playing the WMT media stream.
•
The Content Engine plays an incorrect WMT stream when the client performs a seek operation. This, sometimes causes the Content Engine to stop responding.
•
The Content Distribution Manager displays an incorrect IP address for a Content Engine in a DHCP-enabled network after the IP address of the Content Engine has been changed. The View Network Configurations for Content Engine window in the Content Distribution Manager displays the old IP address in the Primary IP field in Network Configuration, and new IP address in the Address field in Network Interfaces after a new IP address is assigned to the Content Engine.
•
The Content Engine 7325 generates core files when the following conditions are present:
–
–
•
The Websense server does not filter proxy requests intercepted by WCCP. This problem occurs on Content Engines running ACNS software, Release 5.0.3 or later, with the Websense Enterprise server running on the same Content Engine.
•
When the client tries to access some websites, the Content Engine returns a "Proxy Authentication Required" message (HTTP status code 407), and indicates that an unsupported HTTP method was used. This problem occurs under the following conditions:
–
–
•
The caching process restarts on Content Engines when proxy request authentication is turned on.
•
The caching process does not send SNMP traps if the community string used for sending traps is not the same as the community string specified for SNMP read or read-write access.
•
Interface failovers occur on the Content Engine as a result of transient network failures.
•
The caching process restarts when all the following conditions exist:
–
–
–
•
When there are a large number of Content Engines in the ACNS network, and if the user requests an update on the status of on-demand replication using the Content Distribution Manager GUI, the Centralized Management System (CMS) restarts on the Content Distribution Manager and the following messages are displayed in the syslog file:
va.lang.NullPointerException: java.lang.NullPointerException
at com.cisco.unicorn.util.Asserter.notNull(Asserter.java:29)
at com.cisco.unicorn.messaging.DistributionMessage.sendAsync(DistributionMessage.java:590)
•
When the load on the Content Distribution Manager is very high (typically when there are a large number of Content Engines in the ACNS network), the syslog file on the Content Distribution Manager displays the following warnings:
java.lang.NullPointerException: java.lang.NullPointerException
at com.cisco.unicorn.controller.ProxyInfoHelper.getConfigList(ProxyInfoHelper.java:31)
at com.cisco.unicorn.controller.AServant.getListEntryTripleUpdates(AServant.java:1763)
at com.cisco.unicorn.controller.ServantCe.calculateUpdates(ServantCe.java:352)
•
When the node manager process is restarted, multiple instances of several services are started on the Content Engine, CLI commands fail to execute, the default gateway configuration is lost from the running configuration, and the Content Engine generates core files.
•
The mms_server process, running on the Content Engine, crashes continuously while accessing some websites. This problem occurs when the Content Engine tries to access a file encoded using Windows Media Encoder 9.
•
The CPU usage of the Content Engine stays at 100 percent if the requested URL is longer than 8000 characters. This problem occurs when Websense is enabled in the Content Engine.
•
When SmartFilter is enabled, the Content Engine does not filter URLs longer than 2000 characters.
•
The Content Engine shows stopped MMS media streams as paused, a long time after the program has been stopped.
•
The caching process stops in the Content Engine when the port command to the FTP server fails in an FTP-over-HTTP request.
•
The MMS server on the Content Engine fails to serve HTTP requests originating from Windows Media Player Versions 6.0 and 9.0. This problem occurs when the Content Engine cannot perform a forward lookup of the DNS host name, because Windows Media Player Versions 6.0 and 9.0 do not send the host header with the request for content.
Note
•
In ACNS software, Release 5.0.1, the DNS process uses 50 to 60 percent of the CPU and the Content Engine stops responding.
•
The CMS restarts when the default IP domain name is set from the Content Distribution Manager GUI. This problem occurs when the Content Engine has a large running configuration.
•
In ACNS software, Release 5.0 and later, under some circumstances the caching process stops when an HTTP request containing range request is received.
•
Content requests that use MMS over HTTP cause the MMS server on the Content Engine to stop and to generate core files.
•
In Windows Media Player 9.x, the Fast Forward and Rewind buttons do not function properly for WMT video-on-demand content and pre-positioned content. This problem occurs when HTTP is used to deliver the content.
•
CLI commands, whether issued locally or from the Content Distribution Manager GUI, fail on the Content Router because of a full root file system partition.
•
The Content Router generates core files and restarts the Content Router processes. This problem occurs when the Content Router has a large and unstable running configuration.
•
The caching process on the Content Engine restarts when HTTPS is used to access a URL from Windows Media Player. This problem occurs on Content Engines running ACNS software, Release 5.0.x or later.
•
In Content Engines running ACNS software, Release 4.x or 5.0, an arithmetic violation occurs in the DNS process, causing the DNS process to restart. This problem occurs when the DNS client is unable to read from a socket.
•
The MMS server on the Content Engine generates core files if the user agent header does not contain the version number of Windows Media Player.
•
The WMT proxy generates core files when a client uses the Content Engine as a WMT proxy to request a streaming file that does not have any content.
•
The caching process generates core files and restarts on Content Engines when the SmartFilter plug-in is enabled and there is a high load on disk memory.
•
The Content Engine is unable to authenticate users when TACACS+ is used for request authentication. This problem occurs when the authentication process on the Content Engine does not release sockets after authentication is completed.
Documentation Updates
This section describes some documentation updates.
SmartFilter and the No-Auth Rule Interaction
The no-auth rule permits specific login and content requests to bypass authentication and authorization features such as LDAP, RADIUS, SSH, or TACACS+. For example, any requests from the source IP address (src-ip) of 172.16.53.88 are not authenticated.
ContentEngine(config)# rule enableContentEngine(config)# rule action no-auth pattern-list 1 protocol allContentEngine(config)# rule pattern-list 1 src-ip 172.16.53.88 255.255.255.255If ACNS software is configured for authentication and SmartFilter URL filtering, requests that are allowed to bypass authentication will also bypass the URL filter.
Related Documentation
Your product shipped with a minimal set of printed documentation. The printed documentation provides enough information for you to install and initially configure your product. Refer to the Documentation Guide for a complete documentation roadmap and URL documentation links for this product.
Product Documentation Set
In addition to these release notes, the product documentation set includes:
•
•
Hardware Documentation
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Software Documentation
•
•
•
•
•
•
•
•
•
•
•
•
Online Help
Content Distribution Manager GUI online help system
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0304R)
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Guest
