График работы: с нежели заказ оформлен до 16. Магазином, в случае Санкт-Петербург - на 10 до 20. Режим работы: понедельник-суббота, с 10 до 10 до 20 самовывоза: 180 рублей - выходной день другие условия доставки. От метро на нежели заказ оформлен. График работы: с Санкт-Петербург - на 2-ой день опосля.
The ACNS 5. However, in the ACNS 5. To avoid this problem when downgrading from the ACNS 5. Step 1 Disable the local internal Websense server on the Content Engine. Step 2 Deactivate the Websense services on the Content Engine. If you have configured the media file system mediafs with the ACNS 5. The cdnfs is used for pre-positioned content in the ACNS network.
This situation occurs because of a design change that was implemented in the ACNS 5. Because the ACNS 5. To work around this problem, follow these steps:. After you downgrade to the ACNS 5. Reboot the Content Engine for the disk configuration changes to take effect. When you upgrade or downgrade the Content Engine to a different release of the ACNS software, if there is a difference in the SmartFilter plug-in version, the SmartFilter database and configuration files are deleted and default configurations are loaded.
This change occurs because the configuration details might be changed with each new version of SmartFilter software. After each upgrade or downgrade of the SmartFilter plug-in, a fresh database has to be downloaded from the SmartFilter Administration Console to the Content Engine.
Note ACNS software release 5. Content adaptation includes virus scanning, content translation, content filtering, content insertion, and other ways of improving the value of content to end users. The two modes are as follows:.
The ICAP server can modify these requests depending on the services requested. The ICAP server only acts on requested objects after they return from the origin server. The following is a complete list of the ICAP vendors that have been certified to interoperate with the Content Engine:. For ACNS 5. Files that exceed this size limit are not supported for ICAP processing. Table 1 lists the caching, filtering, and authentication methods supported by Content Engines that are running the ACNS 5.
This section lists caveats that are open in the ACNS 5. 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 Unauthorized error code, and the acquirer error log contains the following error message:. Condition: This problem occurs if the origin server uses a certificate that is not known as a standard certificate to the ACNS software acquirer.
For content acquisition from secure sites over HTTPS using strong authentication, only sites with certificates from standard certificate authorities are supported. With strong authentication, if any errors occur during certificate verification by the ACNS acquirer, then content from that site will not be acquired. With weak authentication, certain errors for example, a certificate has expired, certificate is not yet valid, and a subject issuer mismatch has occurred are allowed during certificate verification.
ACNS network administrators should refer to the following information to determine which CA certificate to install on their origin servers. Note that the certificate list differs based on the version of the ACNS software. For the ACNS 5.
Symptom: When a Content Engine model CE 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. Workaround: Reconfigure the disk with a mediafs partition and reload the software. Symptom: The Content Distribution Manager only checks if coverage zone files refer to invalid Content Engines after there is a fresh import. When there is a configuration change that can cause already imported coverage zone files to refer to invalid Content Engines, the Content Distribution Manager does not check or display the correct error message until the next fresh import.
Condition: This problem occurs if there is a coverage zone configuration change that causes already-imported coverage zone files to refer to invalid Content Engines. Condition: The http l4-switch spoof-client-ip enable global configuration command turns on IP spoofing on a Content Engine that is functioning as a caching engine. When a rule action use-server global configuration command is used, the Content Engine stops spoofing the client IP address and instead uses its own IP address to fetch the content.
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. You pre-position a file for example, file.
Symptom: A WMT live stream in a managed live event environment is accessible for a period longer than the scheduled duration. Condition: This problem occurs only with WMT live programs that have unicast access enabled. In this situation, streams can be accessible for up to 24 hours after the last playtime of the event if "Auto Delete" is set to true or can be accessible indefinitely if "Auto Delete" is set to false.
Workaround: Control the live-stream source through the schedule for the event. Typically, this process involves starting and stopping the WMT encoder. Symptom: The content replication status can show an incorrect manifest item count. Condition: This problem can occur if too many channels share the same content for example, if over channels share the same 30 files in each channel.
Even though all channels should show the 30 files that were acquired and distributed, it takes an extended period days before the correct manifest item count is displayed. If you are using the quick crawl tool in the Channel Content window, some of the files also report error messages.
Condition: This problem occurs if NTLM authentication is being used and the specified domain name is longer than 50 characters. Consequently, routing loops can develop within the system. Condition: This problem can occur if the ACNS network configuration is very large for example, with configured Content Engines and the sysfs partition is 2 GB or less.
Condition: This problem occurs very rarely. In very rare situations, even though you entered the no ntlm server enable global configuration command to disable NTLM proxy authentication on the Content Engine, NTLM proxy authentication is still not turned off. Workaround: Enter the no ntlm server enable global configuration command again on the Content Engine. Workaround: There is no known workaround. Mask assignment was only designed for Catalyst series switches and is not supported by Cisco routers.
Condition: This problem occurs if the stream scheduler retrieves stale SDP information from its forwarder because the program has been edited and the encoding changed for a program. This situation occurs if the Content Distribution Manager notification at the edge Content Engine triggers the stream scheduler before the same occurs at the root Content Engine.
Consequently, the edge Content Engine obtains the SDP content from its forwarder, which is valid content at that moment. The Content Engine becomes unresponsive, and it takes a long time for commands to be executed. This situation causes the Content Engine to go into an overload state and not recover easily. Condition: This problem occurs only when RealPlayer Version 10 is used. The player exhibits the same behavior whether or not there is a Content Engine between the client and the origin server.
The URL will be played at least once in the player. Symptom: Even though you entered a write memory command, after an immediate reload, a prompt appears that the configuration has been changed. However, if a prompt appears stating that the configuration has been changed, enter yes to save the configuration.
Condition: This problem occurs only when you use special characters "? Workaround: To publish a live event, use URLs that do not contain special characters. Symptom: The Content Engine reboots suddenly when you are performing database maintenance. Condition: The problem can occur because of a platform issue in the power supply of the device. Symptom: The proxy autoconfiguration file is missing from the Content Engine after you switch from group settings to device settings, and then switch back to group settings.
You revert the Content Engine back to the device group settings you click the Force device group settings button in the device group window or you select the device group from the drop-down menu in the device window.
The autoconfiguration file is not found but the proxy autoconfiguration feature is shown as enabled. Workaround: Return to the device window in the Content Distribution Manager GUI, delete the values from the proxy autoconfiguration fields in the device window, and then select device group from the drop-down menu. Symptom: When using the quick start tool in the Content Distribution Manager GUI, if you repeatedly click the Add-Router to List button before the window completely loads in your browser, the following message appears in your browser:.
Condition: This problem occurs only when there is a slow connection between the Content Distribution Manager and your browser and you perform any of the unsupported actions described above. The command output shows the total unicast requests field as 2 but shows the other types of requests for example, the number of served streaming requests as only 1.
Workaround: Wait until the stream ends before you enter the show statistics wmt requests EXEC command. Condition: This problem can occur when the Websense server is enabled on the Content Engine. Workaround: No user intervention is required. If this problem occurs, the Websense server functionality is not affected. After generating a core file, the Websense server will be automatically restarted and the functionality is restored. Symptom: If you modify a Content Engine GUI page and reload the page without first clicking the Update button, the new unsaved values are displayed on the page instead of the old saved values.
Condition: This problem only occurs if you are using the latest versions of the Netscape browser Version 7. The redisplayed Content Engine GUI page will display the old saved values instead of the new unsaved values. Symptom: RealPlayer crashes when the streams are switched from the first stream to the second stream. Condition: This problem can occur if you have set the reconnect as automatic for broadcast redundancy.
Workaround: If you are not expecting a very high load on the Content Engine, you can turn off kernel optimization by entering the no wmt accelerate live-split enable global configuration command. Symptom: The Internet Explorer client retrieves a partial incomplete customized error page and displays it along with some partial HTML code. Symptom: NTLM authentication for a valid user may take a longer period than usual approximately two minutes if the client sends the request when the Content Engine has been idle for a long period of time.
The request is sent after the Content Engine has been idle for a long period of time. The client machine has some malfunctioning program for example, spyware or a virus and is sending HTTP requests to the Content Engine along with the first request from the browser. The user agent is named Tioga, and the request is as follows:. The user will be authenticated after waiting approximately two minutes. After reporting a failure to the browser, the Content Engine uses the same credential and retrieves the group information for that user from its HTTP authentication cache.
Workaround: On the Content Engine, configure a rule to either reject requests from the user agent named Tioga, or configure the no-auth rule to bypass authentication for this user agent. Symptom: Even though you have the transaction log sanitize feature enabled on the Content Engine, the RealProxy or RealServer access logs still display the client IP address even though it should be hidden. Even though you have entered the transaction-logs sanitize global configuration command, the RealProxy or RealServer access logs still display the client IP address even though it should be hidden.
When you open the online help window, the left pane, which contains the table of contents and index, appears blank. Workaround: Because the ACNS Content Distribution Manager is part of your internal network, you may modify the Windows registry to allow execution of ActiveX controls that are served from within the intranet zone. When the WMT player is being proxied to the Content Engine, the player stops and starts buffering several times when it is playing a media file.
WMT is disabled on the Content Engine. The media file is located on the Windows Media Series 9. Workaround: Enter the http ignore-resp-len-conn-hdr-check global configuration command, which is a hidden CLI command, on the Content Engine. You select Option 7 from the Installer main menu as follows:. Workaround: The DMA errors are displayed four to five times in sequence and then the normal operation of the Content Engine continues without any user intervention.
Symptom: The Windows Media player is not able to stream content for more than one hour in the case of a cache hit. Condition: This problem can occur when the Limit Player Timeout Inactivity value in the origin Windows Media server is set to the default value of seconds. Symptom: The acquirer experiences a problem with a samba crawl. The acquirer is recrawling the same crawl job. A channel contains a samba crawl from a Network Appliance file server, which contains such media files as.
Symptom: The Websense Manager cannot connect to the local internal Websense server that is running on the Content Engine, and clients receive the following error: "Failed to connect, the server is not yet fully started. Condition: This problem can occur if a standby IP address is used on both the primary and secondary interfaces, which prevents the Websense Manager from connecting to the Content Engine.
Symptom: The firewall shows that there is an excessive amount of traffic coming from the Content Engine over TCP port Condition: This problem can occur if the Content Engine is on the outside of the firewall connected to the internet gateway router. The Content Engine is constantly attempting to reset the connections to the inside with a source port of TCP going to the NAT address of the clients.
Because the port translation timer has expired on the Content Engine, the Content Engine uses port to return the message to the client. Condition: This problem can occur if there are more than 14 unique 2-Mbps streams with two clients per stream 28 connections. Workaround: No workaround is required because the Content Engine will reboot and the system will work normally after the reboot. 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 that is running on the Content Engine. Symptom: An FTP client application stops receiving data for a data transfer operation such as a directory listing ls or file transfer GET. Workaround: Remove the Content Engine active mode configuration by entering the following global configuration command:.
When this symptom occurs on an FTP client application, press Ctrl-C simultaneously to stop the partial data transfer operation. Symptom: The Content Engine sends the redirect assign message before it receives the "I see you" message from the router. Condition: Because the Content Engine sends the redirect assign message before it receives the "I See You" message, the redirect assign message will always have a bad rcv-id. This problem occurs because the rcv-id is incremented as part of the router processing the "Here I am" message.
Consequently, the value in the redirect assign message will be behind by 1. Workaround: No workaround is required because although the redirect assign message will have a bad rcv-id it will be behind by 1 , the redirect assign message is resent by the Content Engine and is accepted by the router without affecting the WCCP service. The local Network Agent is one of the services of the local Websense server and runs on the Content Engine. Workaround: Reinstall the user service component of Websense on the Content Engine.
For example, enter the following two global configuration commands:. Symptom: The Content Engine is returning a OK response when it should be returning a message. Condition: This problem can occur when the content has been pre-positioned on the Content Engine. Symptom: When a WMT stream is pre-positioned, the audio works but the playback of embedded slides in the pre-positioned WMT stream are not displayed. Condition: This problem occurs if Microsoft presenter was used to create a WMT stream that has embedded slides.
When this content is pre-positioned, WMT opens and the audio works but the slides never appear. Workaround: When you are using Microsoft producer to publish the content, select publish to My Computer and when you select the Choose publish settings for different audiences option do not check the Enable rich-media Streaming option. When the content is pre-positioned, all content that is created in publishing should be pre-positioned.
Symptom: The browser displays an error message that the requested URL could not be retrieved. Condition: The server errors are being generated because the existing connections are closed when the internal connection to the Content Engine receives an error.
Workaround: No workaround is required because even though the clients whose requests are going through the Content Engine will experience one failure to load a page, their attempt to reload a page will succeed. Condition: This problem occurs when the files are pre-positioned. This problem does not occur if the QuickTime player Version 6. Symptom: A disk is marked as "bad" when a disk error threshold is reached after a transient disk failure.
Workaround: After the disk is marked "bad," you can enter the disk mark diskname good EXEC command on the Content Engine to mark the disk as "good. Condition: This problem occurs in the following situation. There are certain clients that are known to append this data to a request. Symptom: A Content Engine can hang or go into kernel debug mode if the kernel debug feature is enabled on the Content Engine.
Symptom: After you remove the no-auth rule on the Content Engine, the Content Engine continues to apply the rule even if you enter the no rule enable command and then remove all of the pattern lists. Condition: This problem occurs if the no auth rule has been configured and then you remove it from the Content Engine. Workaround: No workaround is required because the cache process automatically restarts on the Content Engine.
Symptom: The configured rules for a device group are randomized when they are applied to the Content Engine that joins the device group. Condition: This problem occurs because the Content Distribution Manager GUI sorts the configured device group rules by the name of the rule. When you use the Content Distribution Manager GUI to configure rules for a device group, you cannot specify the precedence of a configured rule.
Symptom: The Windows version of the PacketVideo player does not display video output. The player indicates that buffering is occurring but no video or audio is rendered. Condition: This problem occurs if the client is a PacketVideo player a Windows simulator and the source is a PacketVideo server. Symptom: The Content Router does not redirect requests to Content Engines in less specific network routes when all Content Engines in the more specific network routes have reached their load threshold.
Workaround: The coverage zone file should be reconfigured in such a way that all Content Engines serving the less specific network route should be configured for the more specific network route with a higher metric value, as shown in the following example:. In this example, ce3 initially configured for the If the Content Router receives a request from network Similarly, if the Content Router receives a request from network Symptom: Usernames are not being used by the Websense Network Agent for user-based policy filtering.
The Content Engine is also logging the following types of error messages:. Symptom: ACNS pre-positioned downloads are slower than downloads from the origin server. For example, if you download a pre-positioned file from a Content Engine, the maximum download speed is 3. If you download the same file directly from the origin server, the maximum download speed is 10 Mbps.
Condition: This problem can occur in the following situation. This section lists the caveats that have been resolved in the ACNS 5. The resolved caveats are grouped into the following categories:. A live channel may fail to be played from the clients. The replication fails as indicated by the output from the show programs EXEC command. This problem can occur in the following condition:. You are running the ACNS 5.
You use uppercase letters when specifying the program name. Because uppercase letters are sometimes rejected, you need to avoid using uppercase letters when specifying the program name in the Content Distribution Manager GUI. This problem was fixed in the ACNS 5. The root Content Engine cannot acquire content. The ACNS acquirer repeatedly attempts to acquire files that have been removed from the origin server.
This problem only occurs when a schedule is used within the manifest file. For the same content, pre-positioned files are being served slower than if the content is served from the Content Engine's web cache as a result of a cache hit. The multicast receiver is unable to receive any files that are sent from the multicast sender.
This problem can occur if the multicast sender and the multicast receiver both have two network interfaces, and multicast traffic is sent and received through the second network interface. A coverage zone file import fails and the following warning appears in the system log syslog :. The problem can occur if the download of the coverage zone file takes more than 60 seconds because of the size of the coverage zone file and the network bandwidth.
If MMS acquisition is used, the asfduration process generates a core file during the acquisition of Windows media files. Multicast distribution cause files to be retransmitted to Content Engines that have already replicated the files. The multicast distribution balance of the priority-based queue versus the ime-based queue is not in line with the configured multicast distribution priority weight. This problem can occur when files, which are larger than 1GB, have been transmitted or are in the queue.
The multicast distribution priority weight balance may be skewed from day to day. This problem can occur because the scheduler is tracking the statistics for one day only. If there are large files being transferred over a low bandwidth, the scheduling could be skewed for the day. New files cannot be pre-positioned and older files cannot be deleted because UNS fills up. This problem occurs because the file system has filled up to the point that UNS cannot even rewrite the required journal files.
Under the ext2 file system, cdnfs corruption causes a UNS directory to be assigned a regular filename, which takes up disk space that is not cleaned up by a cdnf clean up. All pre-positioned content is lost throughout the content distribution network. This problem occurs in the following situation. The root Content Engine fails and the temporary root takes over.
However, the temporary root either cannot access the manifest file or cannot access the origin server or both. Consequently, the temporary root deletes all of the content it previously had pre-positioned from the root Content Engine. Eventually all of the other Content Engines also delete all of their content.
The DNS service can crash or stop responding when it receives a certain type of maliciously coded DNS request from a client. The connection to the ICAP server is not terminated for up to 1. This problem occurs regardless of the keepalive timer setting. If you remove unconfigure the primary IP address of the ICAP server on the Content Engine, and then configure the backup IP address and attempt to add configure the primary IP address back, an error message is displayed:.
The origin server times out before the data transfer to the ICAP server and processing is completed. If you try to enter a value for the maximum group cached authenticated entries settings that is out of range for the specified hardware platform, the Content Distribution Manager GUI does not display a warning message that Content Engine's local settings will override the device group setting for the maximum HTTP authenticated caching setting if the specified setting exceeded the platform limit for a particular Content Engine that was assigned to that device group.
In the ACNS 5. The LocationApiServlet fails with a constraint exception when the name is not set. The DeviceGroup TimeZone Settings with summertime set are overridden by each device in the device group. This problem can occur if the CMS agent that is running on the Content Engine fails to properly parse the time zone configuration on the device and reports the time zone as having been changed from that of the Content Distribution Manager configuration.
This situation causes the values to be overridden. This problem only occurs for the default time zone of UTC. If you are running the ACNS 5. Clients receive a "Page cannot be displayed" error message when they access a site that requires NTLM authentication. This problem can occur with chunked-encoded responses and responses without a content length header.
If you perform a software download from the Content Distribution Manager GUI and the download file is larger than 1 MByte, the GUI displays an incorrect status message about the software download "Download failed" while it is performing the software update. In the Channels Content window, "presedence" was changed to "precedence.
Because of insufficient error handling, the CMS service reconnects to the data server if the requested information for example, the WMT license is not found in the data server. The data server is the service that maintains the current device configuration.
The following Cache application software documents are available:. The following documents are available:. To order printed copies, see the "Obtaining Documentation" section of this publication. The following sections provide sources for obtaining documentation from Cisco Systems. Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. Registered Cisco. Nonregistered Cisco. If you are reading Cisco product documentation on Cisco.
Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:. Cisco provides Cisco. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center TAC Web Site.
You can self-register on Cisco. To access Cisco. The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Network functionality is noticeably impaired, but most business operations continue. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable. The site provides around-the-clock access to online tools, knowledge bases, and software. All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site.
If you have a valid service contract but do not have a login ID or password, go to the following URL to register:. The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations.
In addition, please have available your service agreement number and your product serial number. This document is to be used in conjunction with the documents listed in the "Related Documentation" section. 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. Note The most current Cisco documentation for released products is available on Cisco. The online documents may contain updates and modifications made after the hardcopy documents were printed.
A known defect exists that will prevent you from restoring the content from tape backup. See caveat CSCdv in the "Caveats" section for more information. Note The Installation Wizard shows you only devices that are connected to the same local segment as the Windows PC that is running the Installation Wizard program. Note After you click Finish in the Installation Wizard, a status box appears with configuration information.
Ultimately, you see the device status as "online"; however, if the device is a new Content Engine or Content Router, it must first be approved within the Content Distribution Manager GUI before the device status will change to online. Before the device status shows as online, however, it may actually show as "failed.
While it is rebooting, the Installation Wizard loses communication with it, and the device status shows as failed. However, if you wait for the device to finish booting, the status in the Installation Wizard should change to online. If this occurs, activate a console session and power cycle the device to boot up successfully. Note After mass upgrades from Cache 2. Otherwise, the system may become nonoperational. Note To upgrade Cache 3. In some cases, not all content will be preserved. The downgrade process automatically detects potential loss of content and warns the user.
In this case, the user must agree to these terms before proceeding. Do not perform the downgrade with a console cable connected to the device if a Telnet session is not active. Downgrading from ACNS 4. Note If the software cannot be downgraded without losing Enterprise CDN content, the CLI command will fail and prompt the user to agree to a partial or entire loss of content.
Cumulative keepalive traffic is not segmented and will be visible on the network. A maximum of entries can be added to the playlist at a time. CSCdt Proxy configuration settings cannot be disabled by going into the device editor GUI, checking the corresponding radio button, and clicking Save Changes.
CSCdt Importing a large number of files more than in multiple folders using drag and drop and FTP clients can cause some of the files not to be imported. CSCdu Unnecessary console error messages appear on the console: eth0: command unit failed to mark command as complete at eth0: command unit failed to mark command as complete at CSCdu If a proxy server is set up for the CDN Enterprise Content Distribution Manager and the device is then rebooted for these changes to take effect, an attempt is made to obtain content from the Internet by importing media through HTTP.
The Content Distribution Manager goes to the Internet to fetch the list of files when the user clicks Get List of Files not via the proxy server. However, the content is fetched through the proxy server. This may also occur if clients are behind high-latency connections.
CSCdv The Cache software crashes with a message to the console. This occurs when there is a cache hit but the requested server IP address does not match the IP address of the object source. The Content Engine at this stage is unusable. CSCdw A Content Engine under heavy utilization that is, one experiencing a large number of concurrent connections may run low on RAM and cause network problems.
CSCdw On Windows 95 and Windows 98 clients using NTLM request authentication, the user is not able to authenticate against the primary domain controller PDC without being prompted for a username, password, and domain. Workaround: The device must be rebooted for these changes to take effect.
Condition: This occurs with Netscape 4. Workaround: There is no known workaround. When you try to enter a leap day as the system date, the Content Distribution Manager displays a confirmation box with the wrong date. CSCdt Symptom: After the backup and restore process, the icon for some files disappears. On both the Media Editor page and the Preview page, there is an icon next to the media file that may no longer appear. For MPEG files, it is usually the first frame of the video.
Workaround: The play command works when the TV time, the local time of the TV-out device system time plus the time zone , falls within a defined start and stop time. There are two workarounds: 1. Remove all playlist times. Define a new playlist time that reflects the current TV time. If the user clicks the Upgrade button before the upgrade files are replicated to the Content Engines, the upgrade will not occur.
Users must make sure that all upgrade files have been successfully replicated to each selected Content Engine before they click the Upgrade button. Workaround: The following steps should ensure that software upgrade is successful: 1.
Go to the Import Progress page and wait for the import to be percent complete. Wait 20 minutes. Go to the Software Upgrade page, choose the appropriate Content Engines, and then click the Upgrade button. Wait for 20 minutes for the upgrade to be completed and then go to the Software Upgrade page to verify the software version number for each selected device.
In other words, before clicking the Upgrade button, make sure that the package files are replicated to the Content Engines. CSCdt Symptom: A lag occurs between the time that the Digital Fountain server stops serving a file and the time the channel replication status is updated on the Channel Console page of the user interface.
The user may think that replication is finished for a channel because of what is shown on the replication status bar on the user interface, but because of the lag, the Digital Fountain server may still be serving files from that channel.
Condition: This occurs on systems running the E-CDN application on channels that have been enabled for multicast. Workaround: To ensure that the Digital Fountain server has stopped serving files before importing new ones into the channel, the user should check whether the Digital Fountain server is still serving the files. Further information on how to check this can be obtained from the Digital Fountain documentation.
Condition: This occurs only on systems with multicast replication using a Digital Fountain server. Workaround: Replicate the file again to successfully reach Content Engine B. Condition: This occurs only if the user has overloaded the Digital Fountain server by importing more files at a rate higher than what can be sustained by the Digital Fountain server, and at the same time, by setting the timeout value to be very high.
For more information, refer to the E-CDN documentation for the limit on the number of files that can be multicast and also the Digital Fountain server documentation regarding limitations on the number of files. Workaround: The user should be careful about the number of files imported into the multicast channels and also the rate that has been set for the channel. For example, if the user has a Digital Fountain server with a rate limit of 12 Mbps, importing 13 files into a channel whose rate is 1 Mbps per file will overload the server.
Also, users should set the timeout such that if Content Engines do not receive the file through multicast, they can obtain it through unicast. CSCdt Symptom: A change in the multicast timeout on the Content Distribution Manager is ignored if the change is made after the Digital Fountain client on the Content Engine has already begun downloading the content. Workaround: Reimport the files after changing the timeout, and wait for 15 to 20 minutes to have the new timeout take effect.
CSCdt Symptom: If the user has fewer than 22 layers on the Multicast Server page, then the Digital Fountain server will use a single multicast group address to distribute the content. Workaround: Because of the limitation of the Digital Fountain server, the user must enter 22 or more layers on the Multicast Server page in order for multiple multicast addresses to be used by the Digital Fountain server for multicasting content.
CSCdt Symptom: When a Content Engine that is enabled for TV-out is unsubscribed from a channel, the content from that channel still appears in the playlist. As a result, on the TV controller GUI, the content that belonged to the channel that the Content Engine is now unsubscribed from still appears, and the monikers are displayed, instead of the names. Workaround: If the mode is changed to Play, unsubscribed content is automatically removed from the playlist.
Otherwise, choose the unsubscribed content in the playlist and click the Remove button. A Digital Fountain server that appears as online when you use Internet Explorer 5. Workaround: Netscape Navigator 4. The user should use a supported browser version. CSCdu Symptom: FIN packets, which are harmless to the operation of Content Engine as well as to the network in general, are present on the customer network. Workaround: To prevent these harmless packets from propagating to the customer network, configure the router attached to the Content Engine interface using the ip-access-list feature or similar feature to drop packets coming from the Content Engine on source port Workaround: Delete a small number fewer than content items from the channel at a time until all desired channel items have been removed.
Once the channel is empty, then remove or delete the channel. CSCdu Symptom: Deleting a channel with a large number of items takes a very long time. CSCdu Symptom: Changing the time zone does not reboot the system. Changing the clock from the Identification page causes two reboots. Showlog operates in different time zones than the system clock. The system page is not refreshed, forcing the user to close and reopen the GUI to see the changes.
The video monitor flickers for awhile as it attempts to play the next file and then hangs. In this case, the system will automatically restart, but this could take up to 60 minutes. Otherwise, stopping and restarting the E-CDN application can be done by either disabling and then enabling the E-CDN application or by rebooting the system. This problem can be avoided by clicking NEXT at a slower pace, pausing for a second or two between the clicks.
CSCdu Symptom: If a user enables multicast on one channel and replicates the files successfully, and then creates another channel and enables multicast while the replication is occurring, the Content Distribution Manager reboots. The Digital Fountain server now serves all the files, including files from the first channel, when it should only be serving the files from the second channel.
CSCdu Symptom: Multicast replication through a Digital Fountain server may continue replicating for up to 30 minutes after the last Content Engine has received the entire file. This is normal behavior in the current product design. Condition: The Content Engine replication status is only reported back every 10 minutes and the Content Distribution Manager only checks for the reported replication status from the Content Engines every The Digital Fountain control process in the Content Distribution Manager only checks file replication status every 12 minutes.
None of these timers are tunable, nor are they synchronized. So if the timers are not correlated, you potentially see the multicast continue for up to 30 minutes after the last Content Engine has received the complete file.
The Content Engines will only subscribe to the multicast channel and the routers will only route those multicast packets while the Content Engines are receiving content. Once each Content Engine has the content, it is unsubscribed from the multicast channel and its router will stop routing the multicast traffic. When all Content Engines are unsubscribed, the router in front of the Digital Fountain server will also stop routing multicast traffic.
Therefore, even though the Digital Fountain server is still sending multicast traffic, that traffic does not pass the router. This symptom also occurs with a Content Engine that has lost its network connection, and has many children attached to its hierarchy.
The contents stay on the Content Engine even after it comes on line again. Workaround: Bring the Content Engine back on line, add the channel back into the Content Distribution Manager, and then delete the channel from the Content Distribution Manager. This should remove the channel and its contents from the Content Engine.
Condition: The Content Distribution Manager is very busy or has a very large number of content items, or there are communication problems on your network. Workaround: Assess network status and resolve any network problems, reduce the number of content items on the Content Distribution Manager, or wait for the Content Distribution Manager to finish the current operation: importing content, deleting content, replicating content, and the like.
While certain operations are occurring, such as requesting the Device Console page, requesting the Import Progress page, requesting the Subscriber page, requesting the Media Editor page, importing content, or deleting content, the processing done by the Content Distribution Manager may prevent the Content Distribution Manager from handling client requests in a timely manner.
Workaround: Use a Content Router a Content Router , for example to service client HTTP requests to reduce the number of content items on the Content Distribution Manager, or perform administration tasks during off hours. Condition: If the Content Distribution Manager has a large number of content items and a heavy operation is in process, such as deleting or importing files, the Content Distribution Manager may become so busy in its processing that the background health checks time out, and they will restart the internal Content Distribution Manager processes.
Workaround: The restarting is a normal safety measure. However, the operational load on the Content Distribution Manager is too heavy. Wait for this operation to finish, and make future operations smaller by importing fewer files at a time, for instance. Workaround: Perform the following steps: 1.
Condition: This could be due to conflicting filenames, an extremely busy Content Distribution Manager, or errors during the import process. If you import two files with conflicting names, only one will be imported. Workaround: First eliminate any conflicting filenames.
If you have no conflicting filenames, reduce the number of files that you import at one time. Do not start the next import until the previous one has completely finished. Workaround: Search by the device name or device IP address field on the Device Console page to list the new device. When a search for devices is done on the Content Distribution Manager using a substring, it can return duplicate results for the Content Engine and miss Content Engines that are meant to be listed.
Condition: This has occurred in large installed bases of Content Engines. CSCdv Symptom: Even with automatic hierarchy disabled, there will still be router requests sent by every Content Engine every 30 seconds for every channel on each of those Content Engines.
Condition: This condition is most noticeable in a Content Delivery Network with multiple channels and a large number of Content Engines. Workaround: Reduce the number of channels, disable the network hierarchy, or filter traffic between Content Engines that do not need to communicate. Repeated playback shows that the video freeze occurs at the same position. The hardware decoder interprets some sequences as an error and stops the decode.
Files exhibiting this behavior should be reencoded. CSCdv Symptom: In a network where Content Engines are behind a firewall in a private address space , the Content Distribution Manager is able to route a request behind the firewall, but a Content Router is not. When there is no firewall, no problem occurs. This causes an event record to be written and an exception. These excess event records are then replicated to the Content Distribution Manager, causing performance problems when left unchecked.
This symptom occurs with regard to changing the Alternate IP Port setting as well. The cache process fails and automatically restarts in approximately 1 to 2 minutes, so the service outage is temporary. This occurs only on a Content Engine The changes are lost and are replaced with old network settings stored in the library of the E-CDN. Workaround: In the first case, the network settings must be reconfigured while the E-CDN application is enabled.
CSCdv Symptom: Although a login prompt is visible, no login is possible when a user attempts to use Telnet to access a device during an upgrade. Workaround: After the upgrade is completed, the specified username and password can be used to log in. Using Telnet during an upgrade may make the upgrade appear to have failed because the Content Engine name on the login prompt is "none"; however, the upgrade is in progress and the device should be ready after 10 minutes.
This occurs only if the Content Engine, Content Router, or Content Distribution Manager console port is connected to a console server, a Cisco Series, for instance, and if there is no active session on the serial port of the console server to which the device is connected. Condition: The problem occurs because the console server, with no active session on the port in question, sends serial line flow control to the Content Engine, Content Router, or Content Distribution Manager to have it stop sending characters.
This effectively blocks the downgrade from continuing. Workaround: Remove the console cable and connect the serial cable to a PC running communications software. Alternatively, initiate a session on the console server and observe the output from the Content Engine, Content Router, or Content Distribution Manager. When a downgrade has already been initiated and the device has hung, configure the serial connection as above and reboot the device.
In most cases the downgrade will run to completion. CSCdv Symptom: The cache process may fail if healing mode is enabled. Condition: If healing mode is enabled on a Content Engine , the cache process may crash. The cache process automatically restarts but may crash and restart again.
This happens only on the Content Engine platform. Workaround: There is no known workaround at this time. We strongly recommend not enabling healing mode on the Content Engine Conditions: This problem happens only when heavy debug information is turned on, which should not be a normal situation when the cache is serving real traffic. Workaround: The system needs to be rebooted to bring the cache to a correct state.
Workaround: Delete a single message at a time. CSCdv Symptom: If no name server has been configured, the cache process exits while serving a request that requires name resolution. Condition: This problem occurs if no name servers have been configured. Workaround: Configure a name server using the ip nameserver CLI command in global configuration mode.
Condition: Under extremely high loads for long periods, WMT service will trigger some timing-related bugs that cause WMT service to stop accepting new requests. Workaround: This is not a common situation because the product targeted load is far less than the load causing this problem.
CSCdv Symptom: Rebooting with a communications server connected to the console brings a Content Engine into rescue mode. Condition: If the communications server is not configured correctly, it could send data to the console connection that causes the Content Engine to enter rescue mode. Workaround: Following is a known good console line configuration that prevents this problem: line 1 16 no exec exec-timeout 0 0 transport preferred none transport input telnet transport output none stopbits 1 CSCdv Symptom: The static bypass list does not support more than 32 entries.
Workaround: Disable URL filtering. Condition: This is seen when downgrading to Cache 3. Swapping was not turned off successfully by the downgrade script, which causes the partitioning and building of the swfs to be corrupted. Workaround: After Cache 3. The commands to manually install RealMedia code realmedia. Workaround: Use the disk config CLI command instead to incorporate additional disks or when the above condition has occurred. This workaround wipes out all existing E-CDN application content, but once this is done, the new storage capacity is used.
Workaround: Disable ICP server functionality. The HTTP proxy service will restart. CSCdw Symptom: If you use the Full button to perform a tape backup, after restoring, your system may become nonoperational. CSCdw Symptom: The cache process crashes when end-to-end NTLM authentication is triggered and the connection between the Content Engine and the browser is lost before the connection between the Content Engine and the web server is closed.
Workaround: None. The cache process will stop and restart automatically. The Cache software will restart if it crashes.
The Cisco Application and Content Networking System (ACNS) Software has been retired and is no longer supported. Cisco Application and Content Networking System (ACNS) Software. Introductory text about Cisco Application and Content Networking System (ACNS) Software. This release note contains information about the Cisco Application and Content Networking System (ACNS) software version