Table Of Contents
Release Notes for Cisco ACNS Software, Release 5.1.9
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
Scheduling Live Events for Multiple Content Engines
Multicast Sender Nonretroactive Scheduling Rule
Open Caveats - ACNS Software, Release 5.1.9
Open ACNS-IP/TV Software Integration Caveats, Release 5.1.9
Other Open ACNS Software, Release 5.1.9 Caveats
Resolved Caveats - ACNS Software, Release 5.1.9
TACACS+ Enable Password Attribute
Configuration Requirements for Managed Live Events
Multicast Sender Interoperability
Restrictions Regarding Native FTP Caching in ACNS 5.1 and 5.1.x Software
FTP Caching Support in the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1
FTP Caching Support in the Cisco ACNS Software Command Reference, Release 5.1 Publication
Group-Type Patterns in Rule Pattern Lists
SmartFilter Software and the rule action no-auth Command Rule Interaction
Bandwidth Configuration for Interfaces and Content Services
Default Port of the Content Engine GUI
Playing Nonhinted IP/TV On-Demand Programs over an ACNS Network
Restriction on IP/TV Program Manager Configuration
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco ACNS Software, Release 5.1.9
August 4, 2005
ACNS Build 5.1.9b5
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
These release notes contain information about the Cisco Application and Content Networking System (ACNS) software, Release 5.1.9. These release notes describe the following topics:
•
•
•
Introduction
ACNS software combines the technologies of demand-pull caching and pre-positioning for accelerated delivery of web applications, objects, files, and streaming media; ACNS software runs on Cisco Content Engines, Content Distribution Manager, and Content Router hardware platforms.
Note
These release notes are intended for administrators who will be configuring, monitoring, and managing devices that are running ACNS 5.1.9 software. These release notes describe the open and resolved caveats regarding ACNS software, Release 5.1.9.
System Requirements
This section describes the hardware supported by ACNS software, Release 5.1.9.
Hardware Supported
ACNS software, Release 5.1.9 supports the same hardware platforms that were supported in the ACNS 5.1, 5.1.3, 5.1.5, and 5.1.7 releases. The following hardware platforms are supported:
Important Notes
This section emphasizes important information regarding ACNS 5.1.x software.
•
•
•
•
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.
3.
Scheduling Live Events for Multiple Content Engines
When you schedule a program for a live event, we strongly recommend that you use Greenwich Mean Time (GMT) instead of the local time of the Content Engine that is delivering the program. If you are transmitting the live event across multiple Content Engines that span different time zones, and you schedule local time on each Content Engine instead of GMT, the live transmission is likely to fail.
Multicast Sender Nonretroactive Scheduling Rule
In ACNS 5.1 software, a primary multicast sender automatically schedules the first carousel pass, which sends multicast content to receiver Content Engines. However, ACNS software enforces a nonretroactive scheduling rule, which states that a multicast sender cannot send any files that arrived 10 minutes before it became a multicast sender. Thus, in ACNS software, Release 5.1, when a Content Engine becomes the active primary sender, it does not automatically schedule the first carousel pass to include content that is over 10 minutes old. If you want the old content sent, you must use the distribution multicast resend EXEC command without the on-demand-only option specified. (The on-demand-only option triggers a resend only when a negative acknowledgement [NACK] is issued. In this instance, you want to trigger the resend without a NACK from the receiver.)
After the first multicast carousel pass is complete (whether you manually triggered the resend using the distribution multicast resend command or whether the primary sender completed the pass automatically), the primary sender then determines whether the next carousel pass for content will follow a fixed schedule or whether it will be triggered by NACKs from receiver Content Engines.
In ACNS 5.1 software, you can configure the primary sender to disregard NACKs from receiver Content Engines and send content based on a fixed schedule of carousel passes. To enable this behavior, use the multicast fixed-carousel enable global configuration command. In contrast, a backup multicast sender cannot be enabled for fixed carousel passes; on backup senders, carousel passes must always be triggered by NACKs from receiver Content Engines.
Note
The multicast fixed-carousel enable command is only available for the ACNS 5.1 software primary multicast sender. The default is no fixed carousel; the first carousel pass is automatic and future carousel passes are ondemand only, that is, they are triggered by NACKs.
Caveats
This section lists and describes the open and resolved caveats in ACNS software, Release 5.1.9. Caveats describe unexpected behavior in ACNS 5.1.9 software. 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.1.9
This section lists caveats that have not been resolved in ACNS software, Release 5.1.9. The open caveats are grouped into two categories:
•
•
Open ACNS-IP/TV Software Integration Caveats, Release 5.1.9
This section lists and describes caveats that are open in ACNS software, Release 5.1.9, and are related to ACNS-IP/TV software integration.
•
Symptom: Requests for on-demand programs from clients in an ACNS network are sent to IP/TV Program Manager. IP/TV Program Manager treats these requests as standalone IP/TV on-demand program requests and directs them to the IP/TV Broadcast Server that can serve the request. This causes bandwidth issues and affects the functioning of IP/TV Server.
Condition: This problem occurs when IP/TV has been integrated in an ACNS network. It occurs when requests for on-demand programs that are exported to the ACNS network reach IP/TV Program Manager instead of being routed to the Content Engine that has the programs. This problem is related to routing failure or a routing error.
Workaround: Configure routing correctly in ACNS networks so that on-demand requests are directed to the nearest Content Engine that is capable of serving the program. Alternatively, you can change the proximity settings in IP/TV Program Manager so that it does not redirect the on-demand program requests to IP/TV Broadcast Servers. However, the second approach can also affect the serving of standalone on-demand programs.
•
Symptom: The audio stream sounds discontinuous when you listen to a rebroadcast or video on demand (VOD) of a recorded MP4 file.
Condition: The symptom occurs with IP/TV-generated MP4 files that are streamed from a Cisco Streaming Engine. The problem only occurs with MP4 files that contain an MP3 audio track sampled at 8000 Hz. Streaming the file directly from IP/TV Server does not result in this problem.
Workaround: Use a sampling frequency of 11025 Hz or 22050 Hz while creating a live program with MP3 audio if the recorded file is to be deployed in an ACNS network. Alternatively, use the AAC codec instead of MP3.
•
Symptom: When you are upgrading IP/TV Version 3.5 to Version 5.1, the functionality of the IP/TV Archive Server is replaced by Content Engines in the ACNS network. The Content Engines need to have the content present on a broadcast server but broadcast servers often have limited disk space.
Condition: This problem is only applicable if you are planning to upgrade from IP/TV Version 3.5 to Version 5.1 software, which will require that you use broadcast servers that have limited disk space.
Workaround: Import this data into your ACNS network by moving the media to a web server (origin server), and then creating a manifest file and an associated channel.
•
Symptom: For ACNS-based IP/TV scheduled programs that use live-split-only content delivery mode, IP/TV Program Manager allocates multicast addresses to individual streams that are never used along the content delivery path.
Condition: The problem is observed with live-split-only programs.
Workaround: There is no known workaround.
Other Open ACNS Software, Release 5.1.9 Caveats
This section lists and describes caveats that are open in ACNS software, Release 5.1.9 and are not related to ACNS-IP/TV software integration.
•
Symptom: Content cannot be acquired using strong authentication from secure origin servers that use certificates from nonstandard certificate authorities (CAs). If strong authentication was chosen for content acquisitions from such a site, the acquirer error statistics will contain a 401 (Unauthorized) error code, and the acquirer error log contains the following error message:
Strong Cert Authentication rejects certificate due to error: ssl error codeCondition: This problem occurs if the origin server uses a certificate that is not known as a standard certificate to the ACNS software acquirer. For content acquisition from secure sites over HTTPS using strong authentication, only sites with certificates from standard certificate authorities are supported.
Note
Workaround: Use one of these workarounds:
–
–
•
Symptom: When a Content Engine model CE-565 is attached to a Storage Array SA-7 device, if too large a cache file system (cfs) partition is configured, and a combined streaming and caching workload is used, then a lower HTTP performance is observed.
Condition: This problem occurs when the CE-565 has Windows Media Technologies (WMT) enabled; a combined streaming and caching workload is used, and the Content Engine is attached to an SA-7 device.
Note
Workaround: Allocate less space to the cfs if a Storage Array is attached to the Content Engine.
•
Symptom: Windows Media Technologies (WMT) is enabled with no media file system (mediafs) after you downgrade from ACNS 5.1b300 software to ACNS 5.0.7b8 software.
Condition: This occurs if you upgrade from ACNS 5.0.7b8 to ACNS 5.1bx software, configure the disk, and then downgrade to ACNS 5.0.7b4 software.
Workaround: Reconfigure the disk with a mediafs partition and reload the software.
•
Symptom: Using FTP inside the .meta file to have the Content Engine obtain the .bin file for a Content Distribution Manager GUI-initiated upgrade is unsuccessful if the user's home directory differs from the FTP root.
Condition: Either you receive an error in the Content Distribution Manager GUI when you are creating the definition for the upgrade (when the .bin file does not exist in the user's home directory), or the Content Engine displays an error message on the upgrade (when the .bin file does not exist in the FTP root directory).
Workaround: Copy the .bin file to both the FTP root and the user's home directory, or use a user whose home directory is the FTP root.
•
Symptom: The following error is reported when the ceApiServlet is called:
type Exception reportmessagedescription The server encountered an internal error () that prevented it fromfulfilling this request.exceptionjava.lang.NullPointerExceptionCondition: This problem occurs if the Content Engine does not have an explicit management IP address configured.
Workaround: Configure a management IP address for the Content Engine's Activation page.
•
Symptom: If you edit a file-based scheduled program and the Quality of Service (QoS) feature is configured, the revised program retains the QoS configuration even if you disable the QoS feature.
Condition: This problem occurs only with file-based scheduled programs; it does not occur with live programs.
Workaround: The only known workaround is re-creation. To remove the QoS configuration, delete the program and then re-create the program without configuring the QoS feature.
•
Symptom: The API program is created with multicast settings, with no multicast address ports specified within the program file. The program address pool is configured including the pool TTL.
Condition: This problem occurs if the program multicast TTL is set to 255 instead of the address pool TTL value.
Workaround: Set the required TTL value within the program file.
•
Symptom: A constant stream of bandwidth error messages (one about every 2 seconds) is reported in the syslog. As the following sample messages indicate, these messages are not very useful.
Feb 11 13:24:26 webcache01 bandwd: %CE-BANDWD-3-115002: BANDWD: Trying again in two secondsFeb 11 13:24:28 webcache01 bandwd: %CE-BANDWD-3-115003: BANDWD: verification registration failed, err=30Condition: None.
Workaround: There is no known workaround.
•
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 user-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: There is no known workaround.
•
Symptom: The network management system (NMS) host does not know where SNMP traps are coming from.
Condition: This problem occurs if there are two interfaces and you configure interface redundancy using both interfaces. You must use a dummy address for the physical addresses. You then configure a real address that floats between the two interfaces. If you then configure SNMP traps, the traps are being sourced from the dummy address and not the routable address. Therefore, the NMS host does not know where the trap is coming from.
Workaround: There is no known workaround.
•
Symptom: You experience problems when trying to add rules that have the pipe character (|).
Condition: You cannot add rules that contain the pipe character (|).
Workaround: Add multiple rules for the OR functionality.
•
Symptom: The cache process restarts when the ICAP feature is enabled.
Condition: The problem occurs if the ICAP functionality is in an unstable state.
Workaround: Reboot the Content Engine to restart the ICAP daemon and bring it back to its normal state.
•
Symptom: Syslog messages contain the following text:
uns-server: %CE-CDNFS-0-480000: uns_read_meta: WOW! url mismatch: wanted '<URL>', swaw '^C'Condition: This problem occurs because of an apparent file system corruption; the cdnfs metadata files have the wrong content (the content is internally consistent but in the wrong file). This happens infrequently. For example, in this case, cdnfs content was being updated and a crash occurred because of a kernel panic (which occurs infrequently).
Workaround: Although there is no known workaround to stop the syslog messages shown above, lookups for the target URL (listed in the syslog message) may succeed if the ACNS software has created a new cdnfs entry for the target URL.
A way to test this is to use the cdnfs lookup url EXEC command and see if the URL is found. If the URL is not found, a way to force it to be replicated is to modify the file on the origin server (for example, by using the touch command on a UNIX-based origin server).
Alternatively, you can enter the acquisition-distribution database-cleanup start command on the affected Content Engine; this queries the cdnfs for all the objects that are supposed to be on the Content Engine. Missing objects should be detected and replicated.
•
Symptom: Proxy requests to the Content Engine proceed to allow mode (if allow mode is enabled) or are blocked (if allow mode is disabled) when the Websense URL filtering mechanism is configured to use the local Websense server.
Because the connections from the Content Engine to the Websense server time out, all requests go to allow mode until all 40 connections are exhausted. (This makes it appear as if the Websense server is not responding.) After all 40 connections are attempted, the Content Engine successfully connects to the Websense server and works properly thereafter.
Conditions: This problem can occur under the following conditions:
•
•
•
•
Workaround: Reconfigure Websense URL filtering on the Content Engine so that the Content Engine will attempt to establish new connections to the Websense server.
•
Symptom: The Java monitor in the Content Engine GUI does not show statistics of all of the Content Engines that are using the same WCCP-enabled router. The Content Engine GUI only shows statistics for the Content Engine from which you accessed the Content Engine GUI.
Condition: This occurs when the Content Engine is running ACNS 5.1.7 software.
Workaround: There is no known workaround.
•
Symptom: The Content Engine may not set the Don't Fragment (DF) bit in the IP header even though the path MTU discovery is enabled by default.
Condition: This problem can occur if the Content Engine is reloaded and the ip path-mtu-discovery enable global configuration command is not specified.
Workaround: Specify the ip path-mtu-discovery enable global configuration command on the Content Engine even though this is the default configuration.
•
Symptom: The show statistics distribution mcast-data-send detail EXEC command shows that the multicast sender is not making any progress even though several files are ready to be sent.
Condition: This problem occurs if multicast is enabled on a multicast sender and the Content Engine clock has been changed.
Workaround: Restart the multicast sender by specifying the no multicast enable and multicast enable global configuration commands.
•
Symptom: When you click links from the table of contents or the index of the ACNS Content Distribution Manager online help, the links open in the same pane, that is, the left pane, which contains the table of contents and the index, instead of opening in the right pane, which contains the help topics.
Condition: This problem occurs after you install Microsoft security update MS05-026. This security patch disables cross-frame navigation features that are based on HTML Help ActiveX control (HHCTRL).
Workaround: To reenable cross-frame navigation features that are based on HHCTRL, modify your Windows registry as explained in Microsoft Knowledge Base article 896905, which is available at this URL:
http://support.microsoft.com/kb/896905/
•
Symptom: Websense Manager cannot connect to the local Websense server (the Websense server runs 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 Websense Manager to connect to the local Websense server (Version 5.0.1) that is running on the Content Engine.
Workaround: There is no known workaround.
•
Symptom: The Websense policy server and user server generate core files.
Condition: This problem occurs when the Websense server is running on ACNS 5.1.x software with a version of the Websense Manager that is earlier than Version 5.0.1 build 20030722. This problem does not exist when the Websense server is running on ACNS 5.0.3 software.
Workaround: Download Websense Manager Version 5.0.1 build 20030722.
•
Symptom: If there is a WCCP transparent proxy between the ACNS network root Content Engine and the content origin server, and the proxy requires NTLM authentication, then the ACNS network acquirer may fail to acquire content in the following scenario:
1.
2.
3.
Condition: This occurs with ACNS 5.1.x software.
Workaround: Restart the acquirer through the acquisition-distribution stop and acquisition-distribution start commands.
•
Symptom: In ACNS 4.2 software, rules are configured only for HTTP and not for streaming protocols. If a Content Engine that is configured with rules and is running ACNS 4.2 software is upgraded to ACNS 5.1.x software, then these rules are configured with the protocol type "all."
Condition: This occurs when the software is upgraded to ACNS software Release 5.1.x from ACNS software Release 4.2.
Workaround: If you do not want the rule to be applied for some of the rule actions, you can change the rule configuration as required.
•
Symptom: An FTP client application stops receiving data for a data transfer operation such as a directory listing (ls) or file transfer (GET). The same symptom can occur for FTP-over-HTTP data transfers from the FTP server to the Content Engine.
Condition: For FTP client applications, the Content Engine must be using the FTP proxy through WCCP redirection, configured for following the FTP client's mode for establishing a data connection. The FTP client application must have also been set to use active mode to the FTP server.
ContentEngine(config)# wccp ftp router-list-num numberContentEngine(config)# wccp version 2ContentEngine(config)# ftp proxy active-mode enableFor FTP-over-HTTP data transfers, the Content Engine must be configured for an FTP incoming proxy and configured to use active mode to the FTP server. The client browser must be configured to use the Content Engine FTP proxy for FTP URLs.
ContentEngine(config)# ftp proxy incoming portContentEngine(config)# ftp proxy active-mode enableThe symptoms can occur with the configurations described above and when the FTP server starts sending data packets that are received out of order by the Content Engine before the Content Engine sends the TCP connection establishment SYN-ACK packet to the FTP server.
Workaround: Remove the Content Engine active mode configuration by issuing the following configuration command:
ContentEngine(config)# no ftp proxy active-mode enableWhen this symptom occurs on an FTP client application, press Ctrl-C simultaneously to stop the partial data transfer operation.
When this symptom occurs on a browser configured for FTP-over-HTTP, click the STOP button to stop the partial data transfer operation.
•
Symptom: In ACNS 5.0 software, only "AND" is allowed between group of patterns with the same pattern list number. When you downgrade from ACNS 5.1 software to ACNS 5.0 software, the ORing of patterns configuration is not supported and is converted to ANDing of patterns. For example:
–
rule action block pattern-list 3 protocol httprule pattern-list 3 url-regex senrule pattern-list 3 domain ciscoIn ACNS 5.1 software, the default behavior is ORing of patterns.
–
rule action block pattern-list 3 protocol httprule pattern-list 3 url-regex senrule pattern-list 3 domain ciscoIn ACNS 5.0 software, the only behavior is ANDing of patterns.
Condition: The problem occurs when the configuration on the Content Engine has many pattern lists that are configured (ORed together) in ACNS 5.1 software and the Content Engine is downgraded to ACNS 5.0 software. Then only the first pattern-list configuration is used.
Workaround: There is no known workaround.
•
Symptom: After a Content Engine is downgraded from ACNS 5.1 software to ACNS 4.2 software, some patterns in the pattern list are lost. For example:
–
rule action block pattern-list 3 protocol httprule pattern-list 3 url-regex senrule pattern-list 3 domain cisco–
rule block url-regex senCondition: This problem occurs when the configuration on the Content Engine has many pattern lists that are configured (ORed together) in ACNS 5.1 software, and the Content Engine is downgraded to ACNS 4.2 software. Then only the first pattern-list configuration is used. All other pattern lists are lost.
Workaround: There is no known workaround.
•
Symptom: The cache process crashes while passing traffic for both the standard and the dynamic HTTPS service.
Condition: This problem can occur when heavy HTTPS traffic is passing through the Content Engine. Using standard and dynamic WCCP services and having the debug function enabled when HTTPS traffic is heavy may contribute to this problem.
Workaround: There is no known workaround. However, the cache process will restart and work normally after such a crash.
•
Symptom: When a rule with the redirect action is configured with a URL of 0 and with a matching pattern (no replacing pattern), the cache process crashes if the request matches the pattern.
Condition: This occurs when you configure a numeric value of 0 for the redirected URL (for example, if www.yahoo.com is redirected to 0). If you want the Content Engine to redirect URL x to URL y, then you can configure the rule redirect action. While doing so, you must configure URL x and URL y.
Workaround: There is no known workaround.
•
Symptom: When MPEG-2 is specified as the preferred format in a channel, programs cannot be created in that channel.
Condition: This problem occurs only if MPEG-2 is the preferred format.
Workaround: When MPEG-2 is chosen as the preferred format for a channel-based program, the default bandwidth is set to 1150 (the default for non-MPEG-2 programs). The default bandwidth for MPEG-2-based programs should be 2000 for MPEG-2 half duplex, and 3000 for MPEG-2 full duplex. Manually set the bandwidth while creating the program as follows:
–
–
•
Symptom: If Quality of Service (QoS) for MP2T audio-only programs is set, QoS parameters are not included in the Session Description Protocol (SDP) information for the program. Consequently, the MP2T stream is streamed without the intended QoS characteristics.
Condition: The problem is observed with MP2T audio-only programs and when the audio QoS option is specified.
Workaround: There is no known workaround.
•
Symptom: The manifest validator fails to fetch the XML file if the source is authenticated.
Condition: This problem occurs only if the file is located at an authenticated location.
Workaround: Put a copy of the manifest file in a non authenticated location to use the manifest validator.
Resolved Caveats - ACNS Software, Release 5.1.9
This section lists caveats that have been resolved in ACNS software, Release 5.1.9.
•
When you use Windows XP, and Windows Media Player Version 9.0.0.3008 is installed, embedded Microsoft media files (for example, .asf files) cannot be retrieved with HTTP from a Content Engine that has the media files pre-positioned on it.
•
When the Content Engine is performing live splitting for a variable bit rate file, a core file can be generated for the mms_server and the Windows Media player is unable to play the broadcast alias.
•
When content is being acquired, the ACNS software checks the Expires field in the HTTP header against the local Content Engine clock. If the time in the Expires field in the HTTP header is earlier than the present time, the acquirer honors the time in the Expires field in the case of a crawl but not for a single item.
This problem can occur if the local Content Engine clock is not accurate or the server and the Content Engine clock are not synchronized. In this case, checking the "Expires" field from the server response against the local Content Engine clock can give an incorrect result. For HTML crawl jobs, if the page is expired, an error is reported and the page is discarded. If it is an HTML file, the ACNS software performs a a crawl link to the expired HTML page.
•
With ACNS 5.x software prior to Release 5.1.9, you receive a message indicating the RAM disk is full, when certain applications overuse the RAM disk. The following syslog message appears:
Jan 15 00:30:00 %CE-SYSUTIL-3-800002 RAM disk usage is growing.•
When the NTLM nested group search feature is enabled, the Content Engine can generate heavy traffic to the domain controllers, and the access list that allows or denies a user's primary group is inoperable. This only occurs if there are more than 1000 groups in the Active Directory (AD).
•
The output of the show cdp neighbors EXEC command does not show neighboring Content Engines. This problem can occur on the CE-7305 and CE-7325 that are running ACNS software (Version 5.1.7 or earlier) and that have the network interfaces configured in non-autosense mode.
•
A Content Engine deregistration may fail if the Content Engine is the last remaining Content Engine in a device group and there are more than five channels assigned to the device group at the moment that the Content Engine is deregistered.
•
The Websense server cannot be enabled or disabled if you enter the cms enable global configuration command and then attempt to enable or disable the Websense server before the cache process is completely operational.
•
After a Content Distribution Manager is upgraded from ACNS Release 5.0 software to Release 5.1 software, the specified syslog setting is copied from the device group to the Content Engine that belongs to the device group. However, syslog settings on the Content Engine are not changed. This problem occurs if any logging priority value is set to "warning."
•
Certain encoded WMT files cannot be served to Windows Media Player Version 6.4 or Version 7.0 through a Content Engine using the MMST protocol. (The MMSU protocol works properly, and Windows Media Player Version 9 also works properly.) This problem can occur if the following conditions exist:
–
–
•
The Centralized Management System service logs the following message in the service_logs/cms_cdm_start_log:
Tue May 04 20:45:09 UTC 2004 [E] Thread-14: java.net.SocketException: Too many open files: java.net.SocketException: Too many open filesat java.net.PlainSocketImpl.socketAccept(Native Method)at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)at java.net.ServerSocket.implAccept(ServerSocket.java:439)at java.net.ServerSocket.accept(ServerSocket.java:410)This message may occur under the following conditions:
1.
2.
•
The status of the Content Engine, Content Router, and standby Content Distribution Manager frequently switches between online and offline after you change the system.datafeed.pollRate from a small value to a large value.
•
If the content that exists in the pre-positioned file system (cdnfs) does not correspond with the channels assigned to the Content Engine, you can issue the cdnfs cleanup EXEC command to delete such content. However, although the content in the folders is deleted, the folders themselves are not deleted (If you issue the cdnfs browse EXEC command, the command output indicates that the empty folders are not deleted). This problem occurs prior to ACNS 5.1.8-b3, all empty folders were not deleted. Prior to ACNS 5.1.9-b3, folders with files that were created in order to have a cdnfs entry for the folder itself were not deleted.
•
When you add new files to an existing multicast-only channel and the new files have the same priority as the older files, it can take a long time to distribute the new files to the multicast receivers. Some of the Content Engines in the multicast cloud lose multicast connectivity but continue to send negative acknowledgements (NACKs) to the sender for the missing files.
•
Detail replication status for all crawled content items may display additional items, such as directories. This problem can occur under the following conditions:
–
–
–
•
The Content Router uses the default coverage zone instead of using the coverage zone file that it was configured to use.
•
The cms deregister and cms database delete EXEC commands fail and send an error message indicating that the database files were not deleted.
•
The Content Engine shows a high CPU usage and reports a bad disk drive. The sysmon process is using a high percentage of the CPU.
•
The ACNS acquirer generates a core file when the Content Distribution Manager is not enabled and the database server is restarted.
•
The show statistics distribution errors channel EXEC command shows some receiving errors, but the show distribution channels channel EXEC command shows that all the files in the channel are completed.
•
A core file is generated because the fxd plug-in failed to make a remote procedure call (RPC).
•
When you are using Windows Media Player 9.0 Versions 2980, 2991, and 3128 to stream WMT files, the stream may stop after 3000 to 6000 packets are played.
•
The syslog.txt files shows disk errors, and the disk becomes unresponsive. Messages such as the following are shown in the system log:
disk_check_io(/dev/sdc): read (Input/output error)disk_check_io(/dev/sdc): bad diskSCSI I/O error: POSSIBLE BAD DISK -- device 0x820, sector 0disk02 is bad. Check cable or replace it.On any Content Engine with an MPT driver, the drive under normal operation may encounter a parity error, which is automatically corrected by the drive hardware. The drive reports this fact to the software, which erroneously treats this as a hard error and passes it up to the application.
•
The following types of errors occur if you attempt to add a disk to an array and a cache file system (cfs) partition is already configured on the disk drive, and you reissue the disk add EXEC command:
ContentEngine# disk add disk21 cfs remainingFailed to remove partitions on /dev/sdvFailed to add disk disk21•
The Content Distribution Manager GUI, the Content Engine remote procedure calls (RPCs) to the Content Distribution Manager, and the application programming interface (APIs) to the Content Distribution Manager all seem unresponsive. The Content Distribution Manager has encountered a deadlock that makes the Centralized Management System unresponsive.
•
The WMT player cannot play back a Windows Media file that has an index and markers and is not pre-positioned on the Content Engine. For pre-positioned files that have an index and markers, the Windows Media Player cannot jump to the marked location.
•
When you upgrade without saving the configuration, the Websense configuration is not saved.
•
The root Content Engine performs a crawl, but does not acquire some of the Windows Media files that are referenced within the playlist files. This occurs when a playlist file, which lists the Windows media files, has a .wmx extension rather than a .wax, .wvx, or .asx extension.
•
The acquirer can generate a core file when updating the channel's fully qualified domain name (FQDN).
•
A crawl with a start-url of http://host-name/ or http://host-name/folder/ only crawls for a few pages then stops. For the HTTP and HTTPS protocols, if the start-url ends with a forward slash ("/"), the ACNS acquirer treats it as a directory index crawl. It treats the return HTML from the web server as a file list from a folder, not as the default index.html page.
For directory index crawling, the ACNS acquirer only parses HTML files from the folder URL (the URL ending with a forward slash) and does not parse any other HTML files or links in the directory.
•
After the connection from the Content Engine to the origin server times out during a POST request, it is possible that an additional connection is opened without interaction from the original client. This results in an identical request to be sent to the server, which can cause the server to process duplicate requests.
•
If you configure some URL filter settings (for example, Websense filtering) through a device group but do not configure the general URL filter setting (for example, the custom message directory), localized central management copies the URL filter settings from the device group window to the device window in the Content Distribution Manager GUI.
•
The unicast published URL for a live channel does not work if the OS-FQDN of the live channel's website was updated. This problem occurs with WMT live programs that use a unicast URL.
•
If the primary Content Distribution Manager fails, the standby Content Distribution Manager takes over as primary and the GUI is enabled and operational. However, the Content Engines do not report their disk errors to the standby (now primary) Content Distribution Manager.
•
In the WMT transaction logs, the sc-bytes and s-pkts-sent are logged as zero (0) for fast forwards and rewinds when the video-on-demand (VOD) content is accessed from the Content Engine.
•
In ACNS 5.1.7 and 5.1.5 software, the LDAP policy redirect feature does not work after a reload. The ldap server policy-redirect global configuration command appears in the startup configuration before the reload, but does not appear in the startup or running configuration after a reload.
•
A Content Engine that is installed as an edge device may lose the WCCP router that it was configured to use. If you enable WCCP debugging on the Content Engine, the debugging results indicate that the Content Engine is not sending assignments because all of the WCCP-enabled routers are not recognizing this Content Engine. If you issue the show wccp routers and show wccp EXEC commands on the Content Engine, the command output may be inconsistent.
•
The Content Engine appears to freeze and has no console or network response when it performs WMT live streaming.
•
The Content Distribution Manager GUI fails to respond, and the browser reports HTTPS timeout errors. This occurs when messaging resources that are used to communicate with remote devices become blocked because resources are not being properly returned to the resource pool.
•
An FTP crawl does not work if the FTP server's response to a LIST -a FTP command does not conform to one of the following formats:
UNIX Format:
10-18-01 12:09PM 3437071 JoeDoeInterview_150k.wmv10-18-01 12:09PM 380086 JoeDoeInterview_16k.wmaDOS Format:
drwxrwxrwx 1 owner group 0 May 30 2003 AD-SSL-rwxrwxrwx 1 owner group 79 Mar 13 2003 hello.txt•
If you configure two ICAP vector points (REQMOD and RESPMOD) to the same external ICAP server, occasionally the ICAP server returns incorrect data to the Content Engine. This can cause the ICAP service to restart on the Content Engine.
•
The cache process hangs and stops responding to traffic when you use a custom error page and the page uses Squid variables.
•
An SNMP query to the cdpCacheVTPMgmtDomain variable in the Cisco Discovery Protocol (CDP) MIB can fill up the RAM disk on the Content Engine. This occurs when a CDP-enabled Content Engine is running ACNS software (Release 5.1.7 or earlier), and receives CDP packets from a neighboring device that does not have the VTPMgmtDomain configured.
•
When you create a Cisco Streaming Engine live program through the application programming interface (APIs), the multicast addresses are associated with the different tracks. If the published multicast contains leading or trailing spaces, the multicast addresses are saved but not associated with the live program. The live program receives multicast addresses selected from the program address pool. If no program address pool is defined, the program creation will fail. The multicast addresses specified in the program file are not deleted from the system and therefore cannot be reused.
•
The icap_daemon generates a core file if weight is configured for any ICAP server but the load-balancing scheme is configured either as client-ip-hash or server-ip-hash.
•
When unconfiguring an ICAP service through the no icap service service-id global configuration command, you may be dropped from the configuration shell back to the EXEC shell. A core dump file may be found in the core_dir directory.
•
If the FTP server sends a multi-line response after it has successfully authenticated the user, the ACNS acquirer may have a problem handling the multi-line FTP response. This can result in the ACNS acquirer not being able to retrieve the content from the FTP server.
•
The icap_daemon can periodically generate a core file if the maximum number of ICAP servers (which is 5) is configured for a single ICAP service. If the icap_daemon generates a core file, the ICAP service is stopped by the Node Manager.
•
A multi-level WMT broadcast request may fail under the following conditions. There is a Content Engine chain, and the broadcast alias configuration has an MMS source and HTTP is being used to serve the content.
Documentation Updates
This section describes documentation updates.
•
•
•
•
•
•
•
•
•
•
TACACS+ Enable Password Attribute
This documentation update applies to the following three ACNS Release 5.1 software guides:
•
•
•
The ACNS software CLI EXEC mode is used for setting, viewing, and testing system operations. It is divided into two access levels, user and privileged. To access privileged-level EXEC mode, enter the enable EXEC command at the user access level prompt and specify a privileged EXEC password (superuser or admin-equivalent password) when prompted for a password.
In TACACS+ there is an "enable password" feature that allows an administrator to define a different enable password for each user. If an ACNS user logs in to the Content Engine with a normal user account (privilege level of 0) instead of an admin or admin-equivalent user account (privilege level of 15), the user must enter the admin password in order to access privileged-level EXEC mode.
ContentEngine> enablePassword:
This caveat applies even if these ACNS users are using TACACS+ for login authentication.
Pre-Positioned Content
This documentation update applies to the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.
In ACNS 5.1.x software earlier than Release 5.1.5, pre-positioned content is served only on ports that are standard for the protocol. If the incoming URL contains a port number other than the standard port for that protocol (for example, HTTP uses port 80, RTSP uses port 554, and WMT uses port 1755), then the Content Engine does not attempt to serve the content from the pre-positioned file system (cdnfs). Instead, the Content Engine tries to serve the content from the cache file system (cfs) or tries to fetch the content from the origin server, depending on the existing configuration of the Content Engine.
In ACNS software, Release 5.1.5, the ignoreOriginPort attribute was added to support the playback of pre-positioned content using nonstandard ports. The ignoreOriginPort attribute controls content playback and allows the use of nonstandard ports to play back pre-positioned content. In releases of ACNS software prior to Release 5.1.5, playback of pre-positioned content using nonstandard ports was not supported.
The ignoreOriginPort attribute is supported under the following tags in the manifest file:
•
•
•
•
The ignoreOriginPort attribute is optional. Valid values for the ignoreOriginPort attribute are true or false. The default is false. In the following example, the ignoreOriginPort attribute is specified in the <item> tag and is set to true.
<item scr="<http//10.77.155.211/abc.html>http//10.77.155.211/abc.html" ignoreOriginPort="true" />If an item is acquired with the attribute set to true (ignoreOriginPort=true), then the content is played back even if the incoming URL that was used to request the content contains a nonstandard port. For example, if content is acquired as:
<http//www.foo.com/abcd.xml>http//www.foo.com/abcd.xmlthen the content can be played back as:
<http//www.foo.comXXXX/abcd.xml>http//www.foo.comXXXX/abcd.xmlwhere XXXX is the port number.
For more information about using a manifest file to acquire and distribute content in an ACNS 5.1 network, refer to Chapter 7, "Creating Manifest Files," in the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.
Configuration Requirements for Managed Live Events
This documentation update applies to the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.
If you have channels for live programs configured in your ACNS 5.1 network, make sure that there are no external proxy servers physically located between your ACNS 5.1 receiver Content Engines and your ACNS 5.1 root Content Engine that require proxy authentication. Also, make sure that proxy authentication is not enabled on any receiver Content Engines that might be in the logical, hierarchical path between the root Content Engine and the receiver Content Engine that is going to serve the live stream to the requesting clients. If a live stream encounters any device that requires proxy authentication, the stream will be dropped before it reaches its destination.
If your network is set up with intermediary devices that require proxy authentication, you can work around the problem by configuring rules to bypass authentication on these devices.
For example, to enable the formation of a unicast splitting tree and, in turn, enable live broadcasting from all receiver Content Engines, you can specify the following rule on all of the parent Content Engines in the channel:
ContentEngine(config)# rule pattern-list 1 downstream-CE-ipaddressContentEngine(config)# rule no-auth pattern-list 1cdn-url Attribute Description
This documentation update applies to the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.
With ACNS software, you can use cdn-url as an optional attribute of distributed content. This option only works when the media is pre-positioned on the Content Engine and the origin server does not have to be contacted for any reason to fulfill the request. You cannot use the cdn-url attribute if the origin server needs to be contacted to fulfill the request, for example, in such situations as the following:
•
•
•
Note
On page 7-44, replace the bulleted item under the "Item" section with the following.
•
The cdn-url attribute is optional and is used when content needs to be acquired from one URL (the content acquisition URL) and published using another URL (the publishing URL). The cdn-url attribute is the relative ACNS network URL that end users use to access this content. If no cdn-url attribute is specified, then the src attribute is used as the relative ACNS network URL.
In the following sample manifest file, the content item being acquired contains the file path /RemAdmin/InternalReview/firstpage.htm. By specifying a new file path (RemAdmin/Production/firstpage.htm) using the cdn-url attribute, the publishing URL disguises the fact that the content originated from an internal review.
<CdnManifest><server name="ultra-server"><host name="http://ultra-server" /></server><item src="RemAdmin/InternalReview/firstpage.htm" cdn-url="RemAdmin/Production/firstpage.htm" /></CdnManifest>In the preceding example, src is the content acquisition URL and cdn-url is the publishing URL.
Note
If the content is live or requires playback authentication, the origin server from which the content is acquired must be contacted. Therefore, two URLs must exist for the same content item, and the URL specified in the cdn-url attribute must exist on the origin server at all times.
For example, if the content item "RemAdmin/Production/firstpage.htm" requires playback authentication, this content must exist on the "ultra-server" origin server. Otherwise, pre-positioned content playback will fail.
In general, you should not use the cdn-url, cdnPrefix, or srcPrefix attributes if playback authentication is required or if the content is live.
If you use FTP to acquire content and the content type is not specified in the manifest file and the cdn-url attribute is used to alter your publishing URL, the cdn-url attribute must have the correct file path extension (for example, .jpg). Otherwise, the incorrect content type will be generated and you cannot play the content.
The following example correctly shows the publishing URL with the same file path extension (.jpg) as that of the origin server URL.
<item src="ftp://ftp-server.abc.com/pictures/pic.jpg" cdn-url="pic.jpg" />The following example is incorrectly written, because it does not specify the file path extension (.jpg) in the cdn-url attribute.
<item src="ftp://ftp-server.abc.com/pictures/pic.jpg" cdn-url="pic" />Multicast Sender Interoperability
This documentation update applies to the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1. The following is additional information regarding multicast sender interoperability.
•
Symptom:
–
–
Note
Case 1: The primary sender is using an ACNS software release earlier than ACNS 5.1.x. The backup sender is using ACNS 5.1.x software, as is the receiver.
–
–
–
Case 2: Both the primary sender and the backup sender are using ACNS 5.1.x software. The receiver is using an ACNS software release earlier than ACNS Release 5.1.x.
–
–
Case 3: Both the primary sender and the receiver are using an ACNS software release earlier than ACNS Release 5.1.x. The backup sender is using ACNS 5.1 software.
–
–
–
Condition 2: Although you may have received a warning message from the Content Distribution Manager, you can still configure a Content Engine as a backup sender if the Content Engine is registered with a Content Distribution Manager running ACNS 5.1.x software and the Content Engine is running ACNS software earlier than ACNS Release 5.1.x. Cases 4 through 6 discuss the backup sender operating under these conditions.
Symptom: The Content Distribution Manager does not send related configuration information and configuration changes to the Content Engine running the earlier software version. This results in the the Content Engine not being able to identify itself as the multicast backup sender. This scenario might als
Guest
