Guest

Cisco Application and Content Networking System (ACNS) Software

Release Notes for Cisco ACNS Software, Release 5.1.5

 Feedback

Table Of Contents

Release Notes for Cisco ACNS Software, Release 5.1.5

Contents

Introduction

System Requirements

Hardware Supported

New or Changed Information

New Manifest File Attribute

Filtering Support for HTTPS Requests with SmartFilter

Manually Downloading the SmartFilter Control List

Fetching the Preload File over HTTPS

Important Notes

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

Caveats

Open Caveats - ACNS Software, Release 5.1.5

Open ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

Other Open ACNS Software, Release 5.1.5 Caveats

Resolved Caveats - ACNS Software, Release 5.1.5

Resolved ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

Other Resolved ACNS Software, Release 5.1.5 Caveats

Documentation Updates

TACACS+ Enable Password Attribute

Pre-Positioned Content

Configuration Requirements for Managed Live Events

cdn-url Attribute Description

Multicast Sender Interoperability

FTP Caching Support

FTP-over-HTTP Caching Support

Native FTP Caching Support

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

pace Command

pre-load Command

NTLM Preload Support

show statistics icap Command

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

Related Documentation

Product Documentation Set

Hardware Documentation

Software Documentation

Online Help

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco ACNS Software, Release 5.1.5


August 4, 2005

ACNS Build 5.1.5b2


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.5. These release notes describe the following topics:

Introduction

System Requirements

New or Changed Information

Important Notes

Caveats

Documentation Updates

Related Documentation

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

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 The ACNS software 5.1.5 release is a maintenance release.


These release notes are intended for administrators who will be configuring, monitoring, and managing devices that are running ACNS 5.1.5 software. These release notes describe the open and resolved caveats regarding ACNS software, Release 5.1.5.

System Requirements

This section describes the hardware supported by ACNS software, Release 5.1.5.

Hardware Supported

ACNS software, Release 5.1.5 supports the same hardware platforms that were supported in the ACNS 5.1 and 5.1.3 releases. The following hardware platforms are supported:

NM-CE-BP-SCSI

CE-565-K9

NM-CE-BP-80G

CE-565A-72GB-K9

NM-CE-BP-40G

CE-565A-144GB-K9

CDM-4630

CE-590

CDM-4650

CE-590-DC

CE-507

CE-7320

CE-507AV

CE-7305-K9

CE-510-K9

CE-7305A-K9

CE-510A-80GB-K9

CE-7325-K9

CE-510A-160GB-K9

CE-7325A-K9

CE-560

CR-4430

CE-560AV

 

New or Changed Information

This section describes new or changed information for the ACNS 5.1.5 release. It covers the following topics:

New Manifest File Attribute

Filtering Support for HTTPS Requests with SmartFilter

Manually Downloading the SmartFilter Control List

Fetching the Preload File over HTTPS


Note For information about changes to the ACNS software 5.1 documentation set, see the "Documentation Updates" section.


New Manifest File Attribute

In ACNS software, Release 5.1.5 there is a new manifest file attribute, ignoreOriginPort. The ignoreOriginPort attribute controls content playback and allows the use of nonstandard ports to play back pre-positioned content. In previous releases of ACNS software, playback of pre-positioned content using nonstandard ports was not supported (see the "Pre-Positioned Content" section).

The ignoreOriginPort attribute is supported under the following tags:

<options> tag

<item> tag

<crawler> tag

<item-group> tag

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.xml

then the content can be played back as:

<http//www.foo.comXXXX/abcd.xml>http//www.foo.comXXXX/abcd.xml

where 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.

Filtering Support for HTTPS Requests with SmartFilter

In ACNS 5.1.5 software, HTTPS WCCP intercepted requests can be filtered with SmartFilter.

Manually Downloading the SmartFilter Control List

The intent of the SmartFilter Control List is not to categorize every available URL on the Internet. Instead, it focuses on categorizing those Internet sites that are considered unproductive or inappropriate for typical business or educational environments. The 30 predefined SmartFilter Control List categories encompass a wide variety of material. Some categories are focused on reducing legal liability of a company. These 30 categories are set to "Deny" in the default SmartFilter software policy. Some categories contain such sites as MP3 sites (sites that content that consumes excessive bandwidth). The remainder of these 30 categories are considered unproductive or inappropriate for business or educational environments.

SmartFilter software also provides ten user-defined categories that allow you to further tailor access by defining and filtering sites that are not included in the SmartFilter Control List. Additionally, you can exempt any site that you would like specific groups or individuals to access quickly and easily.

Secure Computing uses automated tools to search the Internet continuously for new sites and pages that meet the content criteria for the 30 predefined Control List categories. Candidate sites are presented to Secure Computing Control List technicians for personal review. As a rule, sites are not added to the SmartFilter Control List without first being viewed and approved by Secure Computing Control List technicians.


Note Secure Computing Corporation cannot guarantee that it has identified every potential site in a given category. Because identifying a particular site as belonging to a particular category involves judgment and opinion, the SmartFilter Control List that is provided may not include sites that a particular organization may wish to control.


You can use the SmartFilter Administration Console to define a SmartFilter Control List download schedule. The Download Setup window tracks the download site, your username, and your password. If you do not download an updated SmartFilter Control List at least monthly, the SmartFilter software considers the Control List "expired," and invokes the action that you specified in the SmartFilter License window.

If the SmartFilter Control List (sfcontrol file) was not properly downloaded from the Secure Computing FTP site and you used FTP to transfer this sfcontrol file from one Content Engine to another, this can cause the cache process to restart.

To stop SmartFilter from restarting the cache process, complete the following tasks, which include manually downloading the SmartFilter control list to the Content Engine:

1. Disable the SmartFilter feature on the Content Engine.

For example, enter the no url-filter http smartfilter enable global configuration command to disable this feature through the Content Engine CLI.

2. Remove the sfcontrol file from the Content Engine. The file is at /local1/smartfilter/sfcontrol.

3. Reenable the SmartFilter feature on the Content  Engine.

For example, enter the url-filter http smartfilter enable global configuration command to disable this feature through the Content Engine CLI.

4. From the SmartFilter Administration Console, perform a manual download of the SmartFilter Control List from the Secure Computing FTP site to the Content Engine.

a. In the upper left panel of the SmartFilter Administration Console, choose the plug-in that corresponds to the Content Engine that is experiencing the problem.

b. In the lower left panel of the SmartFilter Administration Console, double-click the Control List folder to open it.

c. From the Control List folder, choose Download Setup. The Download Setup window appears.

d. In the Download Setup window, verify that the download settings are properly set for a manual download.

e. If you change anything in the Download Setup window, click OK to apply the change to the selected Content Engine.

f. In the Download Setup window, click the Download Now button.


Note For more information about configuring the SmartFilter software, go to the following website: http://www.securecomputing.com.


Fetching the Preload File over HTTPS

When configuring a preload file in the Content Engine CLI, the pre-load global configuration command only had the HTTP or FTP option in ACNS 5.1.x software earlier than Release 5.1.5. There was no mechanism in place to fetch the preload file securely. In ACNS software, Release 5.1.5 the ability to fetch the preload file over HTTPS was added.

Important Notes

This section emphasizes important information regarding ACNS 5.1.x software.

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

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. After you downgrade to ACNS 5.0 software, use the CLI (disk config EXEC command) or the GUI to assign the mediafs disk space.

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. Reboot the Content Engine for the disk configuration changes to take effect.

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. Disable the local (internal) Websense server on the Content Engine.

2. Deactivate the Websense services on the Content Engine.

3. Install the ACNS 5.1 software or ACNS 5.0 software downgrade image on the Content Engine.

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 When the multicast fixed-carousel option is used, the on-demand-only option of the distribution multicast command is not available. The system displays an error message when the on-demand-only option of the distribution multicast resend command is issued in conjunction with the multicast fixed-carousel enable command.


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.5. Caveats describe unexpected behavior in ACNS 5.1.5 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.5

This section lists caveats that have not been resolved in ACNS software, Release 5.1.5. The open caveats are grouped into two categories:

Open ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

Other Open ACNS Software, Release 5.1.5 Caveats


Note For information about open caveats for the IP/TV 5.1.5 software that are not related to ACNS and IP/TV software integration, refer to the Release Notes for Cisco IP/TV, Release 5.1.5.


Open ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

This section lists and describes caveats that are open in ACNS software, Release 5.1.5 and IP/TV software, Release 5.1.5, and are related to ACNS-IP/TV software integration.

CSCec52492

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.

CSCec58408

Symptom: Content Engines in an ACNS network delete the acquired on-demand content when IP/TV Broadcast Server, which is configured to serve the program, does not have the media file available in its IP/TV media root directory.

Condition: This occurs when the associated media file is not available in the IP/TV Server media root directory. This can occur in any of the following cases:

The file has been deleted.

The file has been renamed.

The file has been moved to another location.

The IP/TV media root directory path has been changed.

Workaround: Make sure that a media file, which is associated with an on-demand program that is exported to an ACNS network, is not removed or renamed after the program has been created.

CSCec65255

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.

CSCin70882

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.5 Caveats

This section lists and describes caveats that are open in ACNS software, Release 5.1.5 and are not related to ACNS-IP/TV software integration.

CSCdy82311

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 code

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.


Note 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.


Workaround: Use one of these workarounds:

Use weak authentication.

On the secure server, use a certificate that was generated by one of the standard certificate authorities. 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.1.x software release or later, refer to the certificate list in the Cisco ACNS Software Upgrade and Maintenance Guide, Release 5.x.

CSCea51815

Symptom: The Content Engine model CE-565 shows lower HTTP performance when it is attached to a Storage Array SA-7 device.

Condition: This problem occurs when the CE-565 has Windows Media Technologies (WMT) enabled and is attached to an SA-7 device.


Note The Storage Array device is used for the cache file system (cfs).


Workaround: Allocate less space to the cfs if a Storage Array is attached to the Content Engine.

CSCeb33333

Condition 1: The ACNS network is set up for multicast distribution with Content Engines subscribed to multicast-enabled channels. Multicast sender and receiver Content Engines are running mixed versions of ACNS software. All Content Engines have been successfully enabled for multicasting. The Content Distribution Manager is running ACNS 5.1.x software.

Symptom:

Only senders running ACNS 5.1.x software support failover to a backup sender. Only receivers running ACNS 5.1.x software can send negative acknowledgements (NACKs).

If both the primary sender and the backup sender are actively sending the same file, the receiver Content Engine locks out one of the two and receives one copy of the file from the first sender.


Note Cases 1 through 6 assume that you are using a Content Distribution Manager that is running ACNS 5.1.x software.


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.

The backup sender considers the primary sender inactive and becomes active after the configured failover period.

The primary sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings.

The receiver tries to send a NACK to the primary sender, but receives NACK failures and begins sending NACKs to the backup sender. The backup sender responds to the NACK.

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.

Failover works between the primary and backup senders, but neither the primary sender nor the backup sender ever receives a NACK response from the receiver.

The primary sender sends out the first carousel pass for content without the need for a NACK, so the receiver might be able to obtain content if it joins the group promptly. If it does not, the receiver is not able to obtain content.

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.

The backup sender considers the primary sender inactive and becomes active after the configured failover grace period. The backup sender continues to wait for a NACK response from the receiver before sending the multicast, but the receiver is unable to send a NACK.

The primary sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings.

The receiver should be able to obtain content from the primary sender.

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 also occur if a backup sender using ACNS 5.1.x software is downgraded to an earlier software version through the Content Engine CLI.

Case 4: Both the primary sender and the backup sender are using an ACNS software release earlier than ACNS Release 5.1.x. The receiver is running ACNS 5.1 software.

The receiver alternates attempts to send NACKs between the primary sender and the backup sender but is unsuccessful.

The primary sender periodically sends multicast files as configured in the carousel and multicast-out bandwidth settings.

Case 5: The primary sender and the receiver are using ACNS 5.1 software. The backup sender is using an ACNS software release earlier than ACNS Release 5.1.x.

The primary sender considers the backup sender inactive after the configured failover grace period.

The receiver can successfully send NACKs only to the primary sender. If the primary sender fails, the receiver sends the NACKs to the backup sender, and when it receives a NACK failure as expected, the receiver retries the primary sender. The receiver alternates sending NACKs between the senders until the primary sender becomes active again.

Case 6: The primary sender is using ACNS 5.1.x software. Both the backup sender and the receiver are using an ACNS software release earlier than ACNS Release 5.1.x.

The primary sender considers the backup sender inactive and becomes active after the configured failover grace period. The primary sender sends the first carousel pass of content without needing to receive a NACK. The primary sender then waits for the receiver's NACK to trigger further carousel passes if more than one carousel pass is configured.

The receiver never sends a NACK to the primary sender or the backup sender.

Condition 3: The Content Distribution Manager is using an ACNS software release earlier than ACNS Release 5.1.x. In software releases earlier than ACNS Release 5.1.x, only one sender is configurable for each multicast cloud.

Case 7: The sender is using ACNS 5.1.x software. The receiver is using a software release earlier than ACNS Release 5.1.x.

The sender behaves like a primary sender running ACNS 5.1.x software. That is, it sends the first round of content without requiring a NACK to trigger the carousel pass. However, the sender is unable to continue making carousel passes because the receiver is unable to send NACKs.

Case 8: Both the sender and the receiver are using ACNS 5.1.x software.

The sender is able to perform carousel passes and the receiver is able to send NACKs for missing content; however, there is no support for a backup sender or for configuring the NACK interval multiplier.

Case 9: The sender is using an ACNS software release earlier than ACNS Release 5.1.x. The receiver is using ACNS 5.1.x software.

The sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings so that the receiver can obtain content.

The receiver tries to send NACKs to the sender but continually fails and retries.

Workaround for Cases 1 through 9: Upgrade both senders and receivers to ACNS 5.1.x software. Upgrade the sender first, and then upgrade the receivers.

Workarounds for Case 7 only:

Use the distribution multicast resend EXEC command on the sender Content Engine to trigger a multicast carousel pass manually.

Upgrade both senders and receivers to ACNS 5.1.x software. Upgrade the sender first, and then upgrade the receivers.

CSCeb83282

Symptom: When IP address changes are made on a WCCP-enabled Content Engine, existing connections break, and new connections are not accepted for 30 seconds.

Condition: This problem occurs when you change IP addresses on a Content Engine that has WCCP enabled.

Workaround: Disable WCCP on the Content Engine before changing IP addresses on the Content Engine.

CSCeb85057

Symptom: The Content Engine displays the following error message:

KERNEL: assertion (atomic_read(&sk->wmem_alloc) == 0) failed

Condition: The Content Engine displays this error message during normal operation.

Workaround: Ignore the error message.

CSCec09045

Symptom: Users do not receive the requested page, or the requested page loads very slowly.

Condition: This problem occurs when the origin server sends back a response with "Connection: close," but does not close the connection. The Content Engine waits for the server to close the connection, until the Content Engine times out. Subsequent requests are affected and are not processed until the previous request is completed, thus causing the delay.

Workaround: Configure the Content Engine with a static bypass entry for the server.

CSCec31134

Symptom: The HTTP proxy cache hit response time increases dramatically over time.

Condition: The Content Engine is overloaded (200 requests per disk spindle is the maximum for the CE-7305 and CE-7325).

Workaround: Reduce the load.

CSCec36290

Symptom: When you use Windows XP with Windows Media Player Version 9.0.0.3008 installed, embedded Microsoft media files (for example, .asf files) cannot be retrieved over HTTP from a Content Engine that has the media files pre-positioned.

Condition: When the Content Engine has media files pre-positioned, and the Content Engine is not configured for either WMT or HTTP proxy services, media files must be retrieved over HTTP from a pre-positioned store on the Content Engine.

Workaround: Choose one of these workarounds:

Use Windows 2000 or a different version of Windows Media Player.

Enable WMT on the Content Engine.

CSCec40403

Symptom: The CE-7325 does not respond to a console or Telnet session.

Condition: This situation can occur if the CE-7325 is experiencing a heavy WMT proxy load (approximately 3000 concurrent sessions of 300-kbps media requests) and the majority of the requests are cache misses. Even after the heavy load no longer exists, the CE-7325 does not respond to a console or Telnet session for another few minutes.

Workaround: Reboot the device.

CSCec46643

Symptom: The CLI shell (in EXEC or configuration mode) exits unexpectedly in ACNS software.

Condition: This is very rare. When it occurs, there is a core.XXXX file in the /local1/core_dir directory, where XXXX is a number.

Workaround: Log in to the CLI shell again.

CSCec52221

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.

CSCec54225

Symptom: You cannot configure the Content Engine TACACS+ client to authenticate administrative users if the TACACS+ encryption key is not defined.

Condition: This problem is reported for a TACACS+ server configuration in conjunction with a Rivest, Sharmir, Adelman (RSA) token server. The problem occurs when the TACACS+ encryption key is not defined and the TACACS+ authentication server configuration involves an RSA server. There are no problems if the encryption key is configured. There are no authentication problems if the encryption key is not defined and the RSA token server is not involved in the configuration.

Workaround: Configure the TACACS+ encryption key for secure authentication.

CSCec57998

Symptom: Rarely, core dumps from the login program may occur.

Condition: This problem appears to occur only very rarely when you try to use Telnet to access the Content Engine.

Workaround: There is no known workaround.

CSCec70872

Symptom: The Content Engines fill up the / file system, and components then start to fail.

Condition: This problem may be related to SmartFilter configurations.

Workaround: There is no known workaroud.

CSCec74208

Symptom: In rare circumstances the bypass counters may be incorrect.

Condition: This problem is likely to be seen under the following conditions:

WCCP Layer 2 (L2) redirect is being used, and the WCCP router ID is different from the IP address that is assigned to the router interface from which the packets are redirected to the Content Engine (the WCCP router ID is the numerically lowest IP address configured on the router).

Layer 4 (L4) switched connections are being bypassed.

Workaround: If the first condition is true, change the IP address assignments on the router so that the IP address assigned to the router interface from which packets are redirected to the Content Engine becomes the WCCP router ID. If the second condition is true, there is no known workaround.

CSCec75537

Symptom: The MPEG-4 Microsoft codec has a pixilation problem. Irrespective of the resolution and bit rate, pixilation is seen.

Condition: This problem occurs when the MPEG-4 Microsoft codec and the Video for Windows codec are used at higher resolutions.

Workaround: Use the MPEG-4 ISO codec instead of the MPEG-4 Microsoft codec.

CSCec78596

Symptom: The Content Engine WMT server sends WMT streaming packets at a faster rate than it should.

The problem occurs only if the stream file is generated by the Windows Media Player Version 9 encoder. The higher the bit rate, the more serious the problem. For a 1500-kbps stream, the Content Engine sends it at 1600 kbps; for a 2100-kbps stream, the Content Engine sends it at 3100 kbps.

Condition: This problem causes both Windows Media Player Version 8 and Windows Media Player Version 9 to exhaust the receive buffer and to start dropping packets, which will cause inferior audio and video quality. Windows Media Player Version 7 experiences the same problem when using MMSU. However, Windows Media Player Version 7 operates better when using MMST or HTTP instead because it stops receiving packets instead of dropping them, which triggers the TCP flow control on the Content Engine side to pause sending.

Workaround: Use either of the following workarounds:

Use the Windows Media Player Version 7 encoder instead of the Windows Media Player Version 9 encoder to generate high-bit-rate streaming files.

Use the Windows Media Player Version 7 to play back the high-bit-rate stream through MMST and HTTP.

CSCec78725

Symptom: Pre-positioned content is proxied to the origin server.

Condition: When content is acquired, the manifest file has an item AuthFlag=True. For content to be authenticated, the request is proxied to the origin server.

Workaround: Do not set the AuthFlag to true. If you need to authenticate content, then there is no known workaround for users of ACNS 5.1.x software.

CSCec82061

Symptom: The Content Engine pauses indefinitely in all processing tasks. The kdb (kernel debugger) prompt appears.

Condition: This problem occurs when Windows Media Technologies (WMT) live splitting is used with WMT video-on-demand (VOD) on a Content Engine.

Workaround: Use the no wmt fast-live-split enable global configuration command to disable the high-performance live splitting feature on the Content Engine. This should bypass some kernel work. However, this workaround is not recommended if the highest WMT live-split performance is required from this Content Engine.

CSCec83776

Symptom: The Centralized Management System (CMS) becomes unresponsive on a Content Distribution Manager or reports a timeout error.

Condition: This problem occurs if the CMS locks up on the Content Distribution Manager because of massive device registration and activation within a short time.

Workaround: Restart the CMS on the Content Distribution Manager.

CSCec87047

Symptom: The DNS cache setting on the Content Engine does not affect the DNS behavior of the HTTP proxy.

Condition: This occurs if both the DNS cache and an HTTP proxy are being used.

Workaround: There is no known workaround.

CSCed11183

Symptom: Websense filtering stops working if you configure Websense to use custom filters. For example, the LDAP user attribute is changed from uid to employeenumber in the Websense advanced directory settings. This allows users to use their employee number for authentication; however, LDAP expression filtering will stop working.

Condition: This problem occurs when custom filtering is used. This problem does not occur if the Websense default LDAP expression filter is used.

Workaround: There is no known workaround.

CSCed13700

Symptom: When you attempt to edit the list of locations through the Content Distribution Manager GUI, a processing error for the request occurs.

Condition: This problem can occur when there are a large number of locations and you try to edit the list of locations before the entire list is populated in the Content Distribution Manager GUI.

Workaround: Wait until the list of locations is fully populated in the Content Distribution Manager window before you make any changes to the list.

CSCed19288

Symptom: TV-out playback fails with media files that are larger than 2 GB.

Condition: This problem can occur when the Content Engine with TV-out capabilities attempts to play back media files that are larger than 2 GB.

Workaround: There is no known workaround.

CSCed28289

Symptom: Non-HTTP requests are blocked by the Content Engine.

Condition: This problem can occur if the client sends a non-HTTP request to the Content Engine.

Workaround: There is no known workaround.

CSCed33530

Symptom: The Content Engine's error log file under /local1/errorlog/errlog-cache* contains many of the following error messages

Thu Dec 18 14:41:59 2003: 257: dir(0x91c5440) val 5937736 link list length 13

where the link list length is greater than 5.


Note The string /local1/errorlog/errlog-cache* refers to the filenames with this pattern. These files are the error logs of the cache process.


Condition: This problem occurs when there are duplicate cache disk file system object entries for the same object. When a record is inserted into the hash table, there can be slower performance for a long list of duplicates because the entire list is searched.

Workaround: There is no known workaround.

CSCed34718

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.

CSCed35186

Symptom: An SNMP request that is sent to a physical interface address is returned to the SNMP manager with the IP address of the virtual (standby) group.

Condition: This occurs when you are running ACNS software with a standby IP group and the default gateway is on the subnet that belongs to the virtual IP address, without a closer matching "ip route" statement. Because no other route is configured, the network layer of the Content Engine uses the default gateway and the virtual IP address.

Workaround: Use the ip route dest_addrs net_addrs gateway_addrs global configuration command to add a more specific IP route to the Content Engine. Configure this more specific IP route so that the returned request uses the intended physical interface and the intended Content Engine IP address instead of the default gateway and the virtual IP address.

CSCed38772

Symptom: The following error messages occur after you enter the write memory EXEC command:

CE# write memory
open cli lock tmp_uids: Permission denied
exec_copy: Copy adm_b_db to SS failed. status = (1,12).
Ignore if you didn't change RealServer config.

After these errors occur, the configuration for the system's nonadministrative users, who have a privilege level of 15, is lost after the reload.

Condition: This problem occurs if the following conditions exist:

A user who is configured and logged in with a privilege level of 0 enters privileged mode by issuing the enable EXEC command and then specifying the administrator password.

Other nonadministrative users are configured on the system with a privilege level of 15.

Workaround: Log in to the Content Engine as a user who is configured with a privilege level of 15 before you issue the write memory command.

CSCed44521

Symptom: The Content Engine is not able to use Microsoft Network Messenger when port 1863 is blocked and WCCP transparent redirection is enabled.

Condition: This problem occurs when the http persistent-connections server-only global configuration command is used.

Workaround: Disable the http persistent-connections server-only command.

CSCed48315

Symptom: Users must reenter their username and password information in the login popup window in order to be authenticated.

Condition: This problem occurs when the authentication realm is changed on the Content Engine and the users have been authenticated with the old realm and have checked the Save username and password check box in the popup window then the users must reenter their username and password information.

Workaround: There is no known workaround.

CSCed51672

Symptom: A Content Engine reports the following type of error messages:

Jan 15 16:41:08 webserver PAM adding faulty module: /lib/security/pam_unix.so
Jan 15 16:41:12 webserver PAM unable to dlopen(/lib/security/pam_unix.so)
Jan 15 16:41:12 webserver PAM [dlerror: libnsl.so.1: failed to map segment
from shared object:
Cannot allocate memory]

Condition: This problem can occur with Content Engines that are running ACNS 5.1.5 software.

Workaround: There is no known workaround.

CSCed54064

Symptom: A Content Engine that is running ACNS 5.1.x hangs after a few hours.

Condition: This problem can occur after the following command is entered on the Content Engine:

rule pattern-list 11 src-ip x.x.x.x 255.255.255.255

where x.x.x.x is a customer public address. All requests through that reverse proxy are denied or rejected.

Workaround: To restore service, remove the command.

CSCed55840

Symptom: The client makes a request for some Windows Media content using a simplified hybrid routing (SHR)-style URL (http://FQDN/path/file.asf.asx) and receives a 404 error message.

Condition: This problem occurs when the client is using as its proxy a Content Engine that has the requested content pre-positioned on it. The client sends the SHR-style request directly through that Content Engine. That Content Engine knows it can serve the content itself, and returns an Active Stream Redirector (ASX) file for the Microsoft Media Server (MMS) stream. However, the Content Engine does not change the server portion of the URL, so the URL still points to the Content Router's fully qualified domain name (FQDN). The client therefore attempts to establish an MMS connection to the Content Router. The Content Router is not listening for MMS requests and immediately closes the connection. The client may eventually retry HTTP, which does go through the Content Engine but is then in a form that the Content Engine does not understand (that is, it includes "uns_uns/FQDN"). Consequently, the Content Engine returns a 404 error message to the client.

Workaround: For the Content Router FQDN, set up a bypass list entry in your PAC file or in the browser configuration so that any requests to the Content Router go directly to the Content Router and not through the proxy. If WCCP is used, you may need to set up static bypass for the Content Router on the Content Engine.

CSCed60909

Symptom: The Content Engine shows slower HTTP caching performance when it is attached to a Storage Array SA-14 device, and its syslog contains log messages such as the following:

%CE-SYS-5-900000: __alloc_pages: 0-order allocation failed
%CE-SYS-5-900000: Out of socket memory

Condition: This problem can occur on Content Engines (for example, the CE-7325) that have a large cache file system (cfs) because they are attached to a Storage Array SA-14 device.

This problem can also occur because of to resource exhaustion due to frequent requests from the virus protection software on the client desktops to www.microsoft.com:80. (This situation is visible in transaction logging.)

Workaround: If you are using WCCP, add static bypass entries for IP addresses that are associated with www.microsoft.com. If you are not using WCCP, there is no known workaround.

CSCed68360

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 seconds
Feb 11 13:24:28 webcache01 bandwd: %CE-BANDWD-3-115003: BANDWD:
verification registration failed, err=30 

Workaround: There is no known workaround.

CSCed68734

Symptom: DNS caching is enabled on the Content Engine, but DNS caching does not occur.

Condition: This problem occurs when the DNS caching service is enabled but does not start.

Workaround: In some cases, you can force the DNS caching service to be enabled and start by adding the following lines:

dns use-expired enable 
dns min-ttl 5 
dns max-ttl 86400 (this is the default value and will not show up in config)

CSCed69657

Symptom: An intermittent slow response occurs in a Content Engine that is functioning as an HTTP proxy server. Users experience timeouts of 5 to 10 seconds once or twice a day when accessing the Internet.

Condition: This problem can occur after you upgrade to ACNS 5.1.x software.

Workaround: There is no known workaround.

CSCed72235

Symptom: With ACNS software, you can specify 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.

Condition: 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:

Authenticated requests for pre-positioned content

Redirection to an origin server (for example, if the pre-positioning is incomplete)

Live streaming and splitting

Workaround: Do not use the cdn-url attribute in the affected situations.

CSCed74365

Symptom: A request for a large pre-positioned file over HTTP results in packets that appear to be fragmented.

Condition: This problem occurs if the IP fragmentation bit is not set but the packet seems to be fragmented (for example, adding the total packet size of the larger packet to the data portion of the second packet equals 1,514 total bytes).

Workaround: There is no known workaround.

CSCed74577

Symptom: When you enter the URL to a software upgrade meta file in the Content Distribution Manager software upgrade registration page, you receive an error message such as the following:

Transaction Not Completed
URL http://examplehost/test space/ACNS-5.1.3.15-K9.meta.txt is unreachable.

Condition: This problem occurs if you include a space when specifying the URL to a software upgrade meta file. Meta files to upgrade ACNS software do not accept spaces within URLs.

Workaround: Do not include any spaces when specifying the URL to a software upgrade meta file.

CSCed75352

Symptom: The cache application exits because of an intentional error checking in the code that fails, which causes a brief interruption in caching services while the application restarts. Output from the show tech-support EXEC command shows a crash trace with "eip=0x2599bd51" for ACNS build 5.1.3.b14 software as shown below:

Begin stack trace:
signal(6), bin size(1717100), version (5.1.3.b14),
built by (jsmith) at Feb  2 2004 18:27:42,
crash time(Thu Feb 19 14:47:19 2004)
Working Thread 1: Process 13116 stack
(esp=0xbffff2dc, ebp=0xbffff308, eip=0x2599bd51)

Condition: The Content Engine is configured with the following command to cache HTTP responses that contain the response header "Vary: User-Agent"

Content Engine (config)#	 http cache-vary-user-agent enable

Workaround: Remove the configuration for caching responses with the "Vary: User-Agent" response header by using the following global configuration command.

ContentEngine(config)# no http cache-vary-user-agent enable

CSCed77655

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 the 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.

CSCed84227

Symptom: The network management system (NMS) host does not know where the 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.

CSCed85036

Symptom: A Content Engine stops forwarding traffic (requesting pages from the origin server) after you change a rule on the Content Engine.

Condition: This problem can occur on Content Engines that are upgraded from ACNS 5.1.x software to another version of ACNS 5.1 software and have rules added or modified.

Workaround: To restore the functionality, reboot the Content Engine without saving the running configuration. Delete all newly added group-type AND patterns.

CSCed85146

Symptom: Although you configured the Content Engine to use nonpersistent connections (by issuing the rule no-persistent-connection global configuration command), the Content Engine ignores this rule and uses persistent connections to connect to clients and servers.

Condition: After you upgrade from ACNS 5.1 or 5.1.3 software to ACNS 5.1.5 software, the rule no-persistent-connection command fails; persistent connections are used.

Workaround: There is no known workaround.

CSCed89530

Symptom: The transaction log records the wrong server name.

Condition: This problem can occur when certain requests are redirected to different servers because of the defined rules.

Workaround: There is no known workaround.

CSCed88990

Symptom: Users receive a "400 Bad Request" error message from a website.

Condition: This problem can occur with POST requests because the Content Engine splits the HTTP header into two packets. The server then responds with a "400 Bad Request" error message.

Workaround: There is no known workaround.

CSCed89171

Symptom: A core file from the ICAP service is seen in the core directory.

Condition: This problem only occurs with some websites.

Workaround: There is no known workaround. The ICAP service is immediately restarted by the system.

CSCed91556

Symptom: Users experience problems when they access FTP servers that require a username and password.

Condition: When using FTP-over-HTTP to access an FTP server, users are not prompted under the following situations:

If users enter only a username in the URL (for example, ftp://user@host) and do not enter a password, they are not prompted to enter the password.

If users enter both a username and password in the URL (for example, ftp://user:pass@host), they are not prompted if they entered incorrect credentials.

Workaround: There is no known workaround.

CSCed94378

Symptom: DNS lookup is performed in transparent mode even if no object validation is required.

Condition: Even if no http object url-validation enable global configuration command is used, the statistics on the Content Engine indicate that DNS lookup has occurred and the traces on the VLAN caches indicate DNS requests, as shown in the following example.

ce7325# show statistics dns-cache
Max cache size: 10000
----- DNS Cache Statistics -----
Total DNS lookups: 2

Workaround: There is no known workaround.

CSCee11620

Symptom: Requests for pre-positioned content that are larger than 256 kilobytes return an error message indicating that the bandwidth has been exceeded. Similar error messages are reported in /local1/logs/apache/error_log.

Condition: This problem occurs with Content Engines that are running ACNS 5.1.3 software.

Workaround: Reboot the Content Engine.

CSCei62672

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/

CSCin54434

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 use an external IP address 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.

CSCin55484

Symptom: A pre-positioned content object is lost after you configure a disk and reload the Content Engine.

Condition: If the amount of cdnfs content approaches the amount of disk space allocated to the cdnfs, then cdnfs content is removed to ensure that the cdnfs file system can be resized properly to hold the saved content. In ACNS 5.0.x software, the content is moved out of the file system (if other file systems that can hold the content are detected) or is deleted (if other file systems that can hold the content are not detected) when a disk configuration is performed and 90 percent or more of the cdnfs file system is used.

Workaround: Choose one of the following workarounds:

Do not perform disk configuration.

Ensure that the amount of content present is less than 90 percent of the disk space allocated to the newly specified cdnfs file system.

Upgrade to ACNS 5.1.x software, which always preserves content when you perform a disk configuration, irrespective of the amount of disk space specified for the cdnfs.

CSCin58464

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.

CSCin59084

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. You specify the WCCP transparent proxy authentication information by using the acquirer proxy authentication transparent global configuration command. Content acquisition works correctly.

2. You remove the proxy authentication through the no acquirer proxy authentication transparent command. Content acquisition stops working, which is expected.

3. You restore proxy authentication using the basic-auth-disable option of the acquirer proxy authentication command. Content acquisition should work, but it does not. Content acquisition results in a 401 error message.

Condition: This occurs with ACNS 5.1.x software.

Workaround: Restart the acquirer through the acquisition-distribution stop and acquisition-distribution start commands.

CSCin59100

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 Release 5.1.x from ACNS 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.

CSCin59272

Symptoms: In HTTPS acquisition with directory indexing crawling, when the starting URL lacks a forward slash (/) at the end, the acquirer fails with a 700 error message.

Condition: In HTTPS acquisition with directory indexing crawling, when the starting URL lacks a forward slash at the end, the server returns a 302 Redirect message and redirects the request to the starting URL with a forward slash at the end. However, some servers may return some data in addition to the headers in the HEAD request. In such scenarios, the acquirer fails with a 700 error message.

Workaround: Add a forward slash to the starting URL in the manifest file.

CSCin59462

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 number
ContentEngine(config)# wccp version 2 
ContentEngine(config)# ftp proxy active-mode enable 

For 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 port
ContentEngine(config)# ftp proxy active-mode enable 

The 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 enable

When 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.

CSCin59581

Symptom: When you have numerous pattern lists configured (ORed together) and you downgrade from ACNS 5.1.x software to ACNS 5.0 software, then the first pattern list configuration is used. All other pattern lists are lost.

Condition: This problem occurs when you downgrade from ACNS 5.1.x software to ACNS 5.0 software and you have multiple pattern lists configured (ORed together). If you upgrade from ACNS 5.0 software to ACNS 5.1.x software, then the rules are converted properly. If you then downgrade to ACNS 5.0 software (without changing the rules; for example, not using ACNS 5.1.x software-specific syntax such as ORing) then there is no problem; all rules are converted properly.

Workaround: There is no known workaround.

CSCin59582

Symptom: When you have numerous pattern lists configured (ORed together) and you downgrade from ACNS 5.1.x software to ACNS 4.2 software, then the first pattern list configuration is used. All other pattern lists are lost.

Condition: This occurs when you downgrade from ACNS 5.1.x software to ACNS 4.2 software and you have multiple pattern lists configured (ORed together). If you upgrade from ACNS 4.2 software to ACNS 5.1.x software, then the rules are converted properly. If you then downgrade to ACNS 4.2 software (without changing the rules, for example, not using ACNS 5.1.x software-specific syntax such as ORing) then there is no problem; all rules are converted properly.

Workaround: There is no known workaround.

CSCin59781

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 WWPC services and having the debug function enabled when the 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.

CSCin59863

Symptom: You are unable to disable the local Websense server that is running on the Content Engine.

Condition: The no websense-server enable global configuration command does not generate an error, and the local Websense server still operates. The show websense-server EXEC command shows that all the Websense server ports are unconfigured in ACNS 4.0 software but the Websense server is still running. The show services ports and show services summary EXEC commands do not list the Websense server ports.

Workaround: Disabling the Websense server means turning off the URL filtering functionality (subject to allow mode configuration). In the case of not being able to disable the local Websense server, you can turn off the Websense client configuration. To turn off URL filtering for the local Websense server, disable the Websense URL filtering client in the Content Engine. Also if the local Websense server was used by some other Websense clients, disable Websense URL filtering on these clients. Alternatively, you can use the reload EXEC command on the Content Engine.

CSCin60029

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.

CSCin65344

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:

If the preferred format is MPEG-2 half duplex, set the bandwidth to 2000.

If the preferred format is MPEG-2 full duplex, set the bandwidth to 3000.

CSCin65511

Symptom: The DNS caching service restarts too frequently when the DNS listen all feature is configured.

Condition: This problem occurs when the following conditions are met.

The DNS caching service is enabled on the Content Engine.

The DNS listen all feature is configured on this Content Engine, as shown in the following example:

CE(config)# dns enable
CE(config)# dns listen all port 53 hostname 7325

The Content Engine has the port channel configured as its primary interface.

Workaround: On the Content Engine, enable DNS caching for only a particular IP name server (specify the IP address of the DNS name server that the Content Engine should use for domain name resolution) instead of using the DNS listen all feature (enabling DNS caching for all of the DNS servers that are included in the Content Engine's configured list of DNS servers).

CSCin65854

Symptom: If you set Quality of Service (QoS) for MP2T audio-only programs, 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.

CSCin71559

Symptom: The cache process restarts.

Condition: This problem can occur in the following situation. The certificate key of the origin server has been imported to the Content Engine. An HTTPS transaction is SSL-terminated at the Content Engine, rules are enabled, and the rule rewrite action is configured to match the destination IP address of the HTTPS server (as shown in the following example).

ContentEngine(config)# rule enable
ContentEngine(config)# rule action rewrite pattern-list 2 protocol https
ContentEngine(config)# rule action cache-non-cacheable ttl days 1
pattern-list 1 protocol https
ContentEngine(config)# rule pattern-list 1 dst-ip 10.77.157.170
255.255.255.255
ContentEngine(config)# rule pattern-list 2 url-regsub 10.77.157.170
10.77.155.164

Workaround: Remove the rewrite rules that affect the HTTPS request.

Resolved Caveats - ACNS Software, Release 5.1.5

This section lists caveats that have been resolved in ACNS software, Release 5.1.5. The resolved caveats are grouped into two categories:

Resolved ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

Other Resolved ACNS Software, Release 5.1.5 Caveats


Note For information about caveats that were resolved in IP/TV software, Release 5.1.5, and are not related to ACNS-IP/TV software integration, refer to the Release Notes for Cisco IP/TV, Release 5.1.5.


Resolved ACNS-IP/TV Software, Release 5.1.5 Integration Caveats

CSCed55135

When you create an IP/TV scheduled program to be distributed over an ACNS network, IP/TV Program Manager creates an XML file called a program file that contains information about the scheduled program. IP/TV Program Manager sends this file to the Content Distribution Manager in the ACNS network. Note that this program file is not visible to the user.

The Content Distribution Manager can receive updates from IP/TV Program Manager or directly from ACNS users who are using the CDM API. With ACNS 5.1.x software, if you use IP/TV Program Manager or the CDM API to update the schedule for a live program (a database update), the stream-scheduler process exits. The nodemanager process restarts the stream-scheduler process.

CSCed81171

If you use IP/TV Program Manager (Cluster Configuration window) to specify a name for an IP/TV Broadcast Server that is greater than 16 characters, the Cisco Streaming Engine is unable to multicast; however, the Cisco Streaming Engine is able to perform a unicast in this situation.

Other Resolved ACNS Software, Release 5.1.5 Caveats

CSCec68987

SSL certificates contain an embedded server host name. Client software checks to see that the embedded host name matches the host name used to contact the server, and warns the user if they do not match.

ACNS 5.1.5 software ensures that the SSL certificate and SSL key pair used for the Content Distribution Manager GUI (server) is always consistent with the configured Content Distribution Manager GUI host name, no matter when or how often the configured Content Distribution Manager host name changes.


Note In previous ACNS releases, the SSL certificate and SSL key pair used for the Content Distribution Manager GUI was generated during initial setup, and never updated. If the host name was set correctly prior to certificate generation, clients would not see a warning. However, if the Content Distribution Manager host name was changed after initial configuration, the administrator had no way to update the certificate with the correct host name. Consequently, after a host name was changed, all users logging in to the Content Distribution Manager GUI had to acknowledge a warning message when first connecting to the GUI. For API clients, code had to be written to bypass host name verification checks.


CSCec88324

Although SNMP is configured, traps are sent for a cold restart but not for disk failures.

CSCed10400

The cache process can hang after you enter a show statistics rule all EXEC command.

CSCed17318

A user sends an HTTP request to a browser in order to obtain a web page from an origin server; however, the user receives the web page from a different origin server. This problem can occur if the user's machine is running a web browser that has been infected with the Qhosts virus. The Qhosts virus modifies the DNS resolution mechanism on the user's machine so that the origin server host name resolves to an IP address other than the one associated with the origin server host name. This mismatch between the value of the "Host" header and the IP address of the destination origin server in the request that is redirected to the Content Engine causes this problem.

CSCed23995

The syslog contains messages such as the following:

uns-server: %CE-CDNFS-3-480000:
gen_userfilename: missing ECDNFS file for url <u>

where <u> is a URL.

For this problem to occur, all of the following conditions must exist:

The Content Engine contains cdnfs files that originated when the Content Engine ran ACNS 4.x software or E-CDN 3.x software. (The files would have been ecdnfs files then.)

The Content Engine contains multiple disk drives (possibly including a Storage Array).

Some but not all of those disk drives have been replaced.

The drives that were replaced contained some of ECDN-created files.

Some cdnfs space had been assigned to drives that were not replaced, and cdnfs entries existed on those drives.

CSCed29450

The node manager fails to clean up the start_log files if too many files already exist. If inodes of the /local1 partition are unavailable, then applications can encounter various errors. These errors occur because the applications are unable to write to the /local1 partition because there are no more unused inodes to assign to a new file.


Note An inode is a data structure for holding information about files in a UNIX file system. There is an inode for each file, and a file is uniquely identified by the file system on which it resides and its inode number on that system.


CSCed37238

HTTPS (native through WCCP) needs filtering support. In ACNS 5.1.5 software, HTTPS WCCP intercepted requests can be filtered with SmartFilter.

CSCed37266

When configuring a pre-load file in the Content Engine CLI, the pre-load global configuration command had only the HTTP or FTP option in ACNS 5.1.x software earlier than Release 5.1.5. There was no mechanism in place to fetch the pre-load file securely. In ACNS software, Release 5.1.5 the ability to fetch the preload file over HTTPS was added.

CSCed38486

The network interface records for Content Distribution Managers are never created. This means that the network interfaces cannot have IP access control lists (ACLs) associated with them, and in ACNS 5.1.x network interface properties are not manageable from the Content Distribution Manager.

CSCed41058

When you schedule a program to repeat broadcasting on certain days, you must set the interval between broadcasts accordingly. When a program is created through the Content Distribution Manager GUI, the interval setting is used by the software to rebroadcast the program every specified number of seconds per week (interval=604800 [number of seconds in a week]). However, when a program is created using the program API, the API ignores the interval settings, and the program is consequently not rebroadcast on specific days as intended. When you create a program using the program API, you must create separate schedules for each broadcast to overcome this problem.

CSCed43664

When login authentication is configured at a device group level, the authentication is not enabled at the Content Engine level unless you individually configure each Content Engine to use the device group properties.

CSCed43758

After the Content Engine is rebooted, Telnet is enabled; however, the ACNS CLI shows that Telnet is disabled.

CSCed48566

Because of an illegal argument exception, the standby Content Distribution Manager can not move an object to another transaction. This causes subsequent transactions to fail.

CSCed49619

Manufacturing scripts cause certain disk drive models to be reset.

CSCed51149

In ACNS software, Release 5.x, WMT transaction logs do not conform to the Windows Media Server 4.1 logging format. Consequently, some third-party applications that are based on Windows logging format may not work with the ACNS WMT transaction logs.

CSCed51292

In the case of Microsoft Media Server (MMS) requests, such Windows Media Player events as fast forward or pause are not logged in the ACNS 5.x WMT transaction logs.

CSCed57150

If users who are attempting to access the Content Distribution Manager GUI specify a one-time password for authentication with a RADIUS server, they are prompted multiple times for a new password.

CSCed58696

When WMT video-on-demand (VOD) rebroadcast programs are scheduled with the incorrect URL (for example, the URL has leading spaces), the unified name space (UNS) is unable to resolve the URL. After unsuccessfully trying to schedule such programs, the streaming scheduler exits with a signal 11 and signal 17 and is finally stopped. Because the stream scheduler is stopped, no further changes to schedules are handled.

CSCed60070

The snmpced process crashes when any of the following MIB object instances are queried by the snmpced process:

hrStorageIndex.0
hrStorageType.0
hrStorageDescr.0
hrSTorageAllocationUnits.0
hrStorageSize.0
hrStorageUsed.0
hrStorageAllocationFailures.0

CSCed61380

The Centralized Management System (CMS) must recognize and apply the appropriate downgrade processing for devices downgraded from ACNS 5.1.5 software.

CSCed62969

The Content Distribution Manager cms_cdm service restarts, and the Content Distribution Mange GUI is not available for a brief period.

CSCed63026

The SmartFilter agent (Sfagent) generates a core file in the /local1/core_dir directory on the Content Engine and restarts.

CSCed63770

HTTPS server authentication cannot be configured when a certificate authority (CA) is configured for the particular HTTPS server.

CSCed64178

After you use the CLI to run a multicast connectivity test, the multicast sender or receiver is restarted. This problem occurs if multicast is enabled on a device that is running ACNS software, Release 5.1.3 b13 or earlier.

CSCed65106

Pre-positioned HTTP content is not served. This problem can occur if IP spoofing is enabled.

CSCed65811

After you perform a reload, the configuration of the rules pattern group-type is not taken into account. In this situation, the default behavior of the rules pattern group-type (OR) is used even though AND is displayed as the rules pattern group-type in the running configuration.

CSCed67679

The root Content Engine is always chosen as the forwarder when Content Engines that are outside of the root location are choosing forwarders from the root location. Consequently, there is no load balancing among root Content Engines and other Content Engines within the root location.

CSCed69101

When you upgrade from ACNS 5.0.x software to ACNS 5.1.x software, the directory structure in which some symbolic links are kept is changed. This results in their dates being not synchronized, which in turn causes the symbolic links to be unserveable.

CSCed69674

The Content Engine that is functioning as a reverse proxy server generates a core file and reports the following types of errors:

Last login: Mon Feb  9 15:00:13 2004 from 10.2.62.81
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System Initializing. Please wait.....
System initialization takes longer than expected.
System may not be completely initialized

CSCed69983

When the cache process on the Content Engine restarts, a temporary interruption in caching services occurs for both proxy mode and WCCP transparent redirection. This problem occurs in the ACNS 5.1.1 and ACNS 5.1.3 software releases, but is not a problem in the ACNS 5.0.x releases.

CSCed70553

The root Content Engine reports an Exceed Disk Quota error message although the total file size in that channel is much less than the assigned disk quota.

CSCed73362

Because of a memory allocation failure, the cache process on the Content Engine restarts and generates a core file. The cache process is restarted automatically.

CSCed73944

When the Content Engine accesses the Content Distribution Manager (CDM) GUI, internal system errors are reported. CDM APIs are unavailable once the CDM enters this state. The Content Engine system logs indicate that the Content Engine that is being managed by the CDM experienced remote procedure call (RPC) errors when contacting the CDM.

CSCed74784

If the remote MMS source requires authentication, then a broadcast alias MMS request fails.

CSCed75374

The default route 0.0.0.0/0 (last resort) in a coverage zone file is not applied to the Content Engine selection of the dynamic proxy autoconfiguration (PAC) file.

CSCed76397

Some device group configurations are no longer configured on the device. In the Content Distribution Manager device-level configuration windows, there are no longer device group configurations shown for the device.

CSCed76787

Critical error such as the following appear in the system log:

foreign key referential integrity failure
RPC to replicator failed

If you enter the show distribution process EXEC command, the output indicates that the metadata receiver is not running. This problem occurs because any hard disk failures corrupt the database index file.

CSCed78074

If the User Datagram Protocol (UDP) push is from an Envivio encoder that produces MP4 format, the Cisco Streaming Engine fails to serve unicast live splits (RTP packets); the client's viewer also times out. However, the Cisco Streaming Engine can perform a multicast in this situation.

CSCed78685

The root Content Engine fails to acquire the crawling tasks, and error messages such as the following are reported in the system log:

Index pk_acqcrawltask

CSCed80673

A Windows Media Player POST request for pre-positioned content is not logged at the remote Windows media server.

CSCed81185

After you enter a shutdown command then a no shutdown command in interface configuration mode, the ip route command does not take effect even though the command still appears in the configuration.

CSCed84396

When a Content Engine is experiencing a heavy load, the ICAP process can generate a core file and not recover.

CSCed84752

When the acquirer process is terminated, it can be deadlocked.

CSCed87039

If ICAP is enabled and the traversed URLs return 0-byte chunk responses, you may receive a 502 Bad Gateway error message.

CSCed87474

Underscores are not allowed for custom HTTP request headers.

CSCed89031

The Content Router does not work correctly with EDNS PTR format queries.

CSCed89068

The MMS_SERVER process may restart periodically if the media file system (mediafs) partition is at 100 per cent on any of the disks that are being used for the mediafs.

CSCed89716

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). For more information on this topic, see the "New Manifest File Attribute" section in these release notes.

CSCed92163

Error messages in the system log indicate that the UNS server is being disabled because the UNS server is crashing frequently.

CSCed92366

The Internet Content Adaptation Protocol (ICAP) client receives a 502 error message when it is using ICAP in REQMOD-PRECACHE mode.

CSCed93158

The replication status shows "Pending" for receiver Content Engines for content that is encoded using Windows Media Version 9. The transaction log for the receiver repeatedly shows entries with an action string such as "rescheduled:reason=forwarder_conn_seem_closed" for the specified URL. Eventually, the receiver transaction log and the error log are full. This problem affects releases after ACNS software Release 5.1 but before Release 5.1.5.

CSCed93358

If the ICAP server modifies a file and the file is larger than 5 KB, the ICAP daemon corrupts the data in the file.

CSCed93479

The SNMP agent does not load the saved EVENT-MIB related settings from persistent storage. This is because the load_event_mib() is being called for ce_set_config_params().

CSCed94164

RealPlayer takes a long time to play back a file. In the RealProxy error log there is a message about collision.

CSCee00318

The stream scheduler terminates with a signal 15.

CSCee02712

In all rules specified with the group-type option, the OR rules are changed to AND rules if you move from one release of ACNS 5.1.x software to another ACNS 5.1 software release (for example, if you upgrade from ACNS Release 5.1.1b3 software to ACNS Release 5.1.3b18 software).

CSCee03670

A new vulnerability in the OpenSSL implementation for Secure Socket Layer (SSL) was announced on March 17, 2004.

An affected network device running an SSL server based on an affected OpenSSL implementation may be vulnerable to a Denial of Service (DoS) attack. Workarounds are available to mitigate the effects of this vulnerability on Cisco products in the workaround section of the advisory located at http://www.openssl.org/news/secadv_20040317.txt.

Cisco is providing fixed software, and recommends that customers upgrade to it when it is available.

ACNS software uses a patched OpenSSL 0.9.6j implementation (the patches have been the security updates from -k, -l, and will now include -m). Thus the #2 item in this advisory (Kerberos cipher suites) does not affect ACNS software because it only applies to OpenSSL 0.9.7.

CSCee05698

In the ACNS WMT transaction logs, whenever there is a rewind event, the Content Engine logs the c-rate entry as 65531 instead of -5.

CSCee07869

When the ACNS 5.1 managed live event redundant encoder feature is used, live splitting does not work if the encoder is a unicast broadcast station instead of a Microsoft Windows media encoder.

CSCee08750

The Content Engine does not autoregister with Content Distribution Manager when the IOS DHCP service is used.

CSCee10002

The meta receiver and the uni-receiver fail sometimes while replicating content and report bad forwarder to the channel routing module. As a result, the channel routing module stops using the Content Engine (forwarder) and periodically polls the bad forwarders. The output of the show distribution channels EXEC command indicates that the receiver device cannot find the meta-data forwarder, but can find the unicast data forwarder. This problem can occur when there is a heavy load on the Content Engine (forwarder).

CSCee10018

When the replication status of the receiver Content Engine is not synchronized with the replication status of the root Content Engine, a "Pending Update" state appears in the Content Distribution Manager GUI Monitoring > Replication > Replication Status > Device Replication Status window to explain the discrepancy.

In ACNS 5.1.5 software, when the receiver Content Engine is not synchronized with the root Content Engine, the Device Replication Status window displays a clearer message; it reports the state as "Pending Update From Root."

CSCee10243

When a device is booted and the Centralized Management System (CMS) services are disabled, if you issue the cms database create global configuration command, the command fails.

CSCee11852

After the full reload of meta-data, the delete log of the channel is always cleared. Consequently, the delete record of the channel is not replicated and expired contents are not removed. The receiver Content Engine sees more contents than the root Content Engine, and expired content is not removed from receiver Content Engine.

CSCin47514

The pre-load depth-level-default global configuration command needs to be enhanced to support 0 as a preload depth level.

CSCin59272

In HTTPS acquisition with directory indexing crawling, when the starting URL (start-url) does not contain a forward slash (/) at the end of the URL, the acquirer fails and reports a 700 error message.

CSCin69986

The WMT transaction logs on the Content Engine are erroneously logging Cache_miss instead of Live_Create under the following conditions: the Content Engine is operating in proxy redirection mode, and the client is using Windows Media Player Version player 6.4 to request live streaming content.

CSCin70401

If you use the Content Distribution Manager GUI to set the default coverage zone (the default coverage zone option in the Content Engine Definition window), the default coverage zone works inversely (it is disabled when you enable it, or is enabled when you disable it through the Content Distribution Manager GUI).

CSCin71314

The MMS_SERVER process generates a core file when issuing an HTTP request.

Documentation Updates

This section describes documentation updates.

TACACS+ Enable Password Attribute

Pre-Positioned Content

Configuration Requirements for Managed Live Events

cdn-url Attribute Description

Multicast Sender Interoperability

FTP Caching Support

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

pace Command

pre-load Command

NTLM Preload Support

show statistics icap Command

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

TACACS+ Enable Password Attribute

This documentation update applies to the following three ACNS Release 5.1 software guides:

Cisco ACNS Software Deployment and Configuration Guide, Release 5.1

Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1

Cisco ACNS Software Command Reference, Release 5.1

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> enable

Password:

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:

<options> tag

<item> tag

<crawler> tag

<item-group> tag

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.xml

then the content can be played back as:

<http//www.foo.comXXXX/abcd.xml>http//www.foo.comXXXX/abcd.xml

where 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-ipaddress
ContentEngine(config)# rule no-auth pattern-list 1

cdn-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:

Authenticated requests for pre-positioned content

Redirection to an origin server (for example, if the pre-positioning is incomplete)

Live streaming and splitting


Note Do not use the cdn-url attribute in the specified situations.


On page 7-44, replace the bulleted item under the "Item" section with the following.

cdn-url

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 The content item file path (RemAdmin/InternalReview/firstpage.htm) is controlled by the manifest file. The cdn-url attribute associates a file path with the content item in the manifest file. The manifest file allows the file path for the cdn-url attribute to be specified independently of the file path from which the content items are to be acquired from the origin server (src attribute), allowing the publishing URL to differ from the content acquisition URL. (Refer to the "Generate the Publishing URL" section on page 6-9 in the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.)


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.

Condition 1: The ACNS network is set up for multicast distribution with Content Engines subscribed to multicast-enabled channels. Multicast sender and receiver Content Engines are running mixed versions of ACNS software. All Content Engines have been successfully enabled for multicasting. The Content Distribution Manager is running ACNS 5.1.x software.

Symptom:

Only senders running ACNS 5.1.x software support failover to a backup sender. Only receivers running ACNS 5.1.x software can send negative acknowledgements (NACKs).

If both the primary sender and the backup sender are actively sending the same file, the receiver Content Engine locks out one of the two and receives one copy of the file from the first sender.


Note Cases 1 through 6 assume that you are using a Content Distribution Manager that is running ACNS 5.1.x software.


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.

The backup sender considers the primary sender inactive and becomes active after the configured failover period.

The primary sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings.

The receiver tries to send a NACK to the primary sender, but receives NACK failures and begins sending NACKs to the backup sender. The backup sender responds to the NACK.

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.

Failover works between the primary and backup senders, but neither the primary sender nor the backup sender ever receives a NACK response from the receiver.

The primary sender sends out the first carousel pass for content without the need for a NACK, so the receiver might be able to obtain content if it joins the group promptly. If it does not, the receiver is not able to obtain content.

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.

The backup sender considers the primary sender inactive and becomes active after the configured failover grace period. The backup sender continues to wait for a NACK response from the receiver before sending the multicast, but the receiver is unable to send a NACK.

The primary sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings.

The receiver should be able to obtain content from the primary sender.

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 also occur if a backup sender using ACNS 5.1.x software is downgraded to an earlier software version through the Content Engine CLI.

Case 4: Both the primary sender and the backup sender are using an ACNS software release earlier than ACNS Release 5.1.x. The receiver is running ACNS 5.1 software.

The receiver alternates attempts to send NACKs between the primary sender and the backup sender but is unsuccessful.

The primary sender periodically sends multicast files as configured in the carousel and multicast-out bandwidth settings.

Case 5: The primary sender and the receiver are using ACNS 5.1 software. The backup sender is using an ACNS software release earlier than ACNS Release 5.1.x.

The primary sender considers the backup sender inactive after the configured failover grace period.

The receiver can successfully send NACKs only to the primary sender. If the primary sender fails, the receiver sends the NACKs to the backup sender, and when it receives a NACK failure as expected, the receiver retries the primary sender. The receiver alternates sending NACKs between the senders until the primary sender becomes active again.

Case 6: The primary sender is using ACNS 5.1.x software. Both the backup sender and the receiver are using an ACNS software release earlier than ACNS Release 5.1.x.

The primary sender considers the backup sender inactive and becomes active after the configured failover grace period. The primary sender sends the first carousel pass of content without needing to receive a NACK. The primary sender then waits for the receiver's NACK to trigger further carousel passes if more than one carousel pass is configured.

The receiver never sends a NACK to the primary sender or the backup sender.

Condition 3: The Content Distribution Manager is using an ACNS software release earlier than ACNS Release 5.1.x. In software releases earlier than ACNS Release 5.1.x, only one sender is configurable for each multicast cloud.

Case 7: The sender is using ACNS 5.1.x software. The receiver is using a software release earlier than ACNS Release 5.1.x.

The sender behaves like a primary sender running ACNS 5.1.x software. That is, it sends the first round of content without requiring a NACK to trigger the carousel pass. However, the sender is unable to continue making carousel passes because the receiver is unable to send NACKs.

Case 8: Both the sender and the receiver are using ACNS 5.1.x software.

The sender is able to perform carousel passes and the receiver is able to send NACKs for missing content; however, there is no support for a backup sender or for configuring the NACK interval multiplier.

Case 9: The sender is using an ACNS software release earlier than ACNS Release 5.1.x. The receiver is using ACNS 5.1.x software.

The sender periodically sends multicast files as configured in the carousel pass and multicast-out bandwidth settings so that the receiver can obtain content.

The receiver tries to send NACKs to the sender but continually fails and retries.

Workaround for Cases 1 through 9: Upgrade both senders and receivers to ACNS 5.1.x software. Upgrade the sender first, and then upgrade the receivers.

Workarounds for Case 7 only:

Use the distribution multicast resend EXEC command on the sender Content Engine to trigger a multicast carousel pass manually.

Upgrade both senders and receivers to ACNS 5.1.x software. Upgrade the sender first, and then upgrade the receivers.

FTP Caching Support

This documentation update applies to the following three ACNS 5.1 software guides unless otherwise stated:

Cisco ACNS Software Deployment and Configuration Guide, Release 5.1

Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1

Cisco ACNS Software Command Reference, Release 5.1

A Content Engine that is running ACNS 5.1 software can be configured for FTP caching in either of the following two usage modes:

FTP-over-HTTP mode. The Content Engine (nontransparent proxy server) caches the contents of the specified FTP URLs that are sent to it directly by clients that are using the HTTP protocol. This allows users to use their browsers (HTTP protocol) to access files (to send and receive files) on remote FTP servers.

Native FTP mode. The Content Engine (transparent proxy server) caches the contents of the FTP requests that are sent from clients in the native FTP protocol.

In both of these usage modes, the Content Engine uses the FTP protocol to retrieve and locally cache the content of the FTP requests. These two usage modes differ in the protocol used by the client to issue the FTP request. In FTP-over-HTTP mode, clients use their browsers (the HTTP protocol) to issue FTP requests. In native FTP mode, clients use the native FTP protocol to issue FTP requests, as shown in the following example:

ContentEngine# ftp server.cisco.com


Note In ACNS 5.1 software, native FTP caching is only supported in transparent proxy mode; it is not supported in nontransparent proxy mode. In ACNS 5.1 software, transparent redirection of FTP requests is supported only by WCCP Version 2; transparent redirection through a Layer 4 switch is not supported.

Native FTP requests are logged in the HTTP transaction log on the Content Engine.


FTP-over-HTTP Caching Support

The ACNS 5.1 software supports proxying and caching of FTP URL client requests using proxy-mode HTTP requests when URLs specify the FTP protocol (for example, ftp://ftp.mycompany.com/ftpdir/ftp_file). For instance, the following is an example of an FTP-over-HTTP request that allows the end user to use a browser to access public files from an FTP server:

ftp://ftp.funet.fi/pub/cbm/crossplatform/converters/unix/

For these requests, the client uses HTTP as the transport protocol with the Content Engine, whereas the Content Engine uses FTP with the FTP server. When the Content Engine receives an FTP request from the web client, it first looks in its cache. If the object is not in its cache, it fetches the object from an upstream FTP proxy server (if one is configured), or directly from the origin FTP server.

The FTP proxy supports anonymous as well as authenticated FTP requests. Only base64 encoding is supported for authentication. The FTP proxy accepts all FTP URL schemes defined in RFC 1738. In the case of a URL in the form ftp://user@site/dir/file, the proxy sends back an authentication failure reply and the browser supplies a popup window for the user to enter login information.

The FTP proxy supports commonly used MIME types, attaches the corresponding header to the client, chooses the appropriate transfer type (binary or ASCII), and enables the browser to open the FTP file with the configured application. For unknown file types, the proxy uses binary transfer as the default and instructs the browser to save the downloaded file instead of opening it. The FTP proxy returns a formatted directory listing to the client if the FTP server replies with a known format directory listing. The formatted directory listing has full information about the file or directory and provides the ability for users to choose the download transfer type.

Native FTP Caching Support

On page 2-8 of the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1, and on page 2-120 ("Usage Guidelines") of the Cisco ACNS Software Command Reference, Release 5.1 publication, replace the information about native FTP caching with the following information.

The Content Engine operating as an FTP proxy supports passive and active mode for fetching files and directories. In native FTP caching mode, if the ftp proxy active-mode enable global configuration command is used, then the Content Engine uses the same mode with the FTP server for the data connection as the client used to reach the Content Engine, which can be either active or passive. If the ftp proxy active-mode enable command is not used, the Content Engine uses passive mode with the FTP server for the data connection.

As the following partial output of the show ftp command shows, if you have used the ftp proxy active-mode enable command, the Content Engine (the nontransparent proxy server that is functioning as a native FTP proxy server) adheres to the client's mode (active or passive):

The Content Engine (the native FTP proxy server) performs an active-mode data transfer to or from the FTP server if the FTP client issues an active-mode data transfer request.

The Content Engine performs a passive-mode data transfer to or from the FTP server if the FTP client issues a passive-mode data transfer request.

ContentEngine# show ftp

FTP Configuration
-----------------
WCCP FTP service status:                 ENABLED
Maximum size of a FTP cacheable object:  204800 KBytes
FTP data connection mode with Server:
Adhere to Client's mode (active or passive)

Note that the format of the URL that the Content Engine (nontransparent proxy server that is functioning as a native FTP proxy server) creates for a native FTP request depends on the FTP login name and the transfer mode (binary or ACSII file transfer mode).

If the FTP login name is an actual username instead of "anonymous," then the string "*user*:*password*@" is included in the URL before the host.

If the mode used to transfer the file is binary mode, then the string ";type=i" is included at the end of the URL. The following is an example of the URL format that the Content Engine creates for a specific user when binary mode is being used.

ftp://*user*:*password*@10.100.200.5/home/myhome/mybinfile.obj;type=i

The URL for an "anonymous" user login and an ACSII file transfer mode will not have any fields embedded in the URL, as shown in the following example:

ftp://10.100.200.5/home/myhome/mytextfile.txt

The following two examples demonstrate the use of native FTP with a Content Engine. In the first example, the user logs in with an actual username name ("huff") and is able to retrieve the requested file (test.c) from the FTP server. Note that in this case, the current directory for the user named "huff" is "/home/huff."

ContentEngine# ftp server.cisco.com
Connected to server.cisco.com.
220 server.cisco.com FTP server (Version wu-2.6.0(1)
Mon Feb 28 10:30:36 EST 2000) ready.
Name (server:huff): huff
331 Password required for myserver.
Password:
230 User huff logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> pwd
257 "/home/huff" is current directory.
ftp> get /tmp/test.c
200 PORT command successful.
150 Opening BINARY mode data connection for /tmp/test.c (645 bytes).
226 Transfer complete.
645 bytes received in 0.00077 seconds (8.2e+02 Kbytes/s)
ftp> quit
ContentEngine#

In the second example (shown below), the user logs in as an anonymous user and cannot retrieve the requested file (test.c) because the file is not located in the document root directory of the FTP server ("/"), which is the current directory for any anonymous user.

ContentEngine# ftp server.cisco.com
Connected to server.cisco.com.
220 server.cisco.com FTP server (Version wu-2.6.0(1)
Mon Feb 28 10:30:36 EST 2000) ready.
Name (server:huff): anonymous
331 Guest login ok, send your complete e-mail address as password.
Password: test@cisco.com
230 Guest login ok, access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> pwd
257 "/" is current directory.
ftp>
ftp> passive
Passive mode on
ftp> get
(remote-file) /tmp/test.c
(local-file) test.c
local: test.c remote: /tmp/test.c
227 Entering Passive Mode (172.31.255.255)
550 /tmp/test.c: No such file or directory.
ftp>
ContentEngine#

In ACNS 5.1 software, the wccp ftp router-list-number and wccp ftp mask global configuration commands were added to support native FTP caching on a Content Engine that is operating in transparent proxy mode.

The wccp ftp command is used to configure the WCCP interception of FTP protocol traffic from FTP clients to FTP servers.

ContentEngine(config)# wccp ftp ?
  mask             Specify mask used for CE assignment
  router-list-num  Router list number
ContentEngine(config)# wccp ftp mask ?
  dst-ip-mask      Specify sub-mask used in packet destination-IP address
  src-ip-mask      Specify sub-mask used in packet source-IP address
ContentEngine(config)# wccp ftp router-list-num ?
  <1-8>            Router List Number

The following example shows how to configure native FTP caching on a WCCP Version 2 router:

1. Turn on native FTP caching. The service group number for this service is 60.

Router(config)# ip wccp 60

2. Specify an interface on which the native FTP caching service will run.

Router(config)# interface type number

3. Configure the router to use the outbound interface for the FTP caching service.

Router(config-if)# ip wccp 60 redirect out

The associated show wccp services EXEC command was modified in ACNS software, Release 5.1 to show the configuration information associated with the FTP proxy.

ContentEngine# show wccp services 
Services configured on this Content Engine
        Web Cache
        Custom Web Cache
        FTP Cache
        RTSP

The show wccp modules EXEC command was modified in ACNS software, Release 5.1 to include an entry for the FTP caching service:

ContentEngine# show wccp modules

Modules registered with WCCP on this Content Engine

Module Socket Expire(sec) Name       Supported Services
-------------------------------------------------------
5      6      3          FTP Proxy   FTP Cache

1      7      3          RTSP Proxy  RTSP

0      8      3          HTTP Proxy  Web Cache
    Reverse Proxy
    Custom Web Cache
    WCCPv2 Service 90
    WCCPv2 Service 91
    WCCPv2 Service 92
    WCCPv2 Service 93
    WCCPv2 Service 94
    WCCPv2 Service 95
    WCCPv2 Service 96
    WCCPv2 Service 97

ContentEngine# show wccp masks ?
  custom-web-cache  Custom web caching service
  ftp               FTP Proxy caching service
  reverse-proxy     Reverse Proxy web caching service
  rtsp              Media caching service
  web-cache         Standard web caching service

For more information about these commands, refer to the Cisco ACNS Software Command Reference, Release 5.1.

Restrictions Regarding Native FTP Caching in ACNS 5.1 and 5.1.x Software

Restrictions regarding native FTP caching support in ACNS 5.1 and 5.1.x software are:

Maximum FTP object size of 200 megabytes

No support for bandwidth control for FTP client requests and FTP server pulls

No support for the Type of Service (ToS) bit for FTP client requests

No support for pre-positioned files in the cdnfs

No support for the Internet Content Adaptation Protocol (ICAP)

No support for nontransparent proxy

No support for proxy authentication

No support for the Internet Cache Protocol (ICP)

No support for healing mode

No support for Layer 4 switch FTP redirection

No support for FTP request proxy rules

No support for MIN-TTL and AGING-HEURISTIC-TTL cache control knob configurations

No support for any URL filtering schemes (good list, bad list, N2H2, Websense, and SmartFilter)

No support for caching files from a Macintosh FTP server

No support for "offline" operation for the FTP proxy server

FTP Caching Support in the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1

Updates to the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1 regarding FTP caching support are:

On page 2-7, in the "FTP and Caching" section, the information about configuring FTP incoming ports and the Rules Template only applies to FTP-over-HTTP caching. It does not apply to native FTP caching.

In the "FTP Proxy Configuration Examples" section on page 5-12, the examples of how to use the ftp proxy global configuration commands only apply to a Content Engine that is operating in FTP-over-HTTP mode. The ftp object max-size command applies to Content Engines that are operating in either FTP-over-HTTP mode or native FTP mode.

The "Configuring FTP Connection Settings Using the Content Engine GUI" section on page 10-2 applies only to FTP-over-HTTP caching for nontransparent proxy mode. The FTP inbound and outbound proxy configuration apply only to FTP URLs over HTTP (FTP-over-HTTP).

In the "Configuring FTP Connection Settings Using CLI Commands" section on page 10-3, the ftp proxy incoming and ftp proxy outgoing global configuration commands apply only to FTP-over-HTTP caching.

The ftp proxy active-mode global configuration command applies to FTP (native FTP) caching as well as to FTP-over-HTTP caching.

In FTP-over HTTP caching mode, if the ftp proxy active-mode global configuration command is used, the Content Engine first attempts to use active mode with the FTP server for the data connection. If the active mode fails, the Content Engine attempts to use passive mode for the data connection. If this command is not configured, the Content Engine first attempts to use passive mode with the FTP server for the data connection, and then automatically switches to active mode if passive mode is not supported by the FTP server.

In native FTP caching mode, if the ftp proxy active-mode command is used, then the Content Engine uses the same mode with the FTP server for the data connection as the client used to reach the Content Engine, which can be either active or passive. If this command is not configured, the Content Engine uses passive mode with the FTP server for the data connection.

In the "Setting FTP Cache Freshness" section on pages 10-4 through 10-7, the ftp object max-size global configuration command is the only mentioned command that applies to both native FTP caching and FTP-over-HTTP caching. All of the other mentioned commands (for example, the ftp age-multiplier command, the ftp max-ttl command, the ftp object command, the ftp proxy command, the ftp reval-each-request command, and the ftp min-ttl command) apply only to FTP-over-HTTP caching.

On page 10-7, replace the sample output of the show ftp EXEC command with the following sample output. The following example shows that the output of the show ftp command differentiates between the configuration that is applicable to FTP-over-HTTP client requests and the one that applies to FTP (native FTP) client requests:

ContentEngine# show ftp
FTP over HTTP Configuration
---------------------------

FTP heuristic age-multipliers: directory-listing 30% file 60%
Maximum time to live in days: directory-listing 3 file 7
Minimum time to live for all objects in minutes: 30
Incoming Proxy-Mode:
  Configured Proxy mode FTP connections on ports: 80 8080
Outgoing Proxy-Mode:
  Not using outgoing proxy mode.
Active mode of FTP transfer is enabled
Maximum size of a FTP cacheable object is 204800 KBytes
No object is revalidated on each request

FTP Configuration
-----------------

WCCP FTP service status:                 ENABLED
Maximum size of a FTP cacheable object:  204800 KBytes
FTP data connection mode with Server:    
Adhere to Client's mode (active or passive)

On page C-4, replace the WCCP Service Groups table with the following table that has the WCCP FTP caching service (service group number 60) added to it. You can configure a router that is running WCCP Version 2 to run any of the cache-related services listed in the following table. WCCP Version 1 routers support only the web cache service (service group 0).

Service Group Number
Description of Services

0

Web caching

53

DNS caching

60

FTP caching

80

RTSP

81

MMST

82

MMSU

90-97

User-configurable

98

Custom web caching

99

Reverse proxy web caching


On page C-9, add native FTP caching to the list of services that you can configure on a router that is running WCCP Version 2. The following is an example of how to configure native FTP caching on a router running WCCP Version 2.

1. Turn on native FTP caching. The service group number for this service is 60.

Router(config)# ip wccp 60

2. Specify an interface on which the native FTP caching service will run.

Router(config)# interface type number

3. Configure the router to use the outbound interface for the native FTP caching service.

Router(config-if)# ip wccp 60 redirect out

FTP Caching Support in the Cisco ACNS Software Command Reference, Release 5.1 Publication

Updates to the Cisco ACNS Software Command Reference, Release 5.1 publication regarding FTP caching support are:

On pages 2-118 through 2-119, replace the syntax description of the options for the ftp global configuration command with the following revised description that indicates whether an option applies to FTP-over-HTTP caching only (FTP-over-HTTP only), or both native FTP caching and FTP-over-HTTP caching (FTP and FTP-over-HTTP):

age-multiplier

FTP caching heuristic modifiers. (FTP-over-HTTP only)

max-ttl

Sets the maximum Time To Live for objects in the cache. (FTP-over-HTTP only)

min-ttl

Sets the minimum Time To Live for FTP objects in the cache.
(FTP-over-HTTP only)

object

Sets the configuration of FTP objects. (FTP and FTP-over-HTTP)

max-size

Sets the maximum size of a cacheable object. (FTP and FTP-over-HTTP)

proxy

Sets the proxy configuration parameters. (FTP and FTP-over-HTTP)

active-mode

Configures the FTP mode for establishing the data connection. (FTP and FTP-over-HTTP)

anonymous-pswd

Sets the anonymous password string (for example, wwwuser@cisco.com). (FTP-over-HTTP only)

incoming

Sets the incoming port for proxy-mode requests. (FTP-over-HTTP only)

outgoing

Sets the parameters to direct outgoing FTP requests to another proxy server. (FTP-over-HTTP only)

reval-each-request

Sets the scope of revalidation for every request. (FTP-over-HTTP only)


On page 2-120, note the following new usage guideline regarding the ftp proxy active-mode global configuration command.

The ftp proxy active-mode command applies to FTP (native FTP) caching as well as FTP-over-HTTP caching.

In FTP-over-HTTP caching mode, if the ftp proxy active-mode global configuration command is used, the Content Engine first attempts to use active mode with the FTP server for the data connection. If the active mode fails, the Content Engine attempts to use passive mode for the data connection. If this command is not used, the Content Engine first attempts to use passive mode with the FTP server for the data connection, and then automatically switches to active mode if passive mode is not supported by the FTP server.

In native FTP caching mode, if this command is used, then the Content Engine uses the same mode with the FTP server for the data connection as the client used to the Content Engine, which can be either active or passive. If this command is not used, the Content Engine uses passive mode with the FTP server for the data connection.

On page 2-121, the examples of how to use the ftp proxy global configuration commands apply only to a Content Engine that is operating in FTP-over-HTTP mode. The ftp object max-size global configuration command applies to Content Engines that are operating in either FTP-over-HTTP mode or native FTP mode.

On page 2-331, replace the sample output of the show ftp EXEC command with the following sample output. As the following example shows, the output of the show ftp command differentiates between the configuration that is applicable to FTP-over-HTTP client requests and that for FTP (native FTP) client requests:

ContentEngine# show ftp
FTP over HTTP Configuration
---------------------------

FTP heuristic age-multipliers: directory-listing 30% file 60%
Maximum time to live in days: directory-listing 3 file 7
Minimum time to live for all objects in minutes: 30
Incoming Proxy-Mode:
  Configured Proxy mode FTP connections on ports: 80 8080
Outgoing Proxy-Mode:
  Not using outgoing proxy mode.
Active mode of FTP transfer is enabled
Maximum size of a FTP cacheable object is 204800 KBytes
No object is revalidated on each request

FTP Configuration
-----------------

WCCP FTP service status:                 ENABLED
Maximum size of a FTP cacheable object:  204800 KBytes
FTP data connection mode with Server:
Adhere to Client's mode (active or passive)

On page 2-469, replace the sample output of the show wccp services EXEC command with the following:

ContentEngine# show wccp services 
Services configured on this Content Engine
        Web Cache
        Custom Web Cache
        FTP Cache
        RTSP

On page 2-469, replace the partial output from the show wccp routers EXEC command with the following:

ContentEngine# show wccp routers
Router Information for Service: FTP Cache
        Routers Configured and Seeing this Content Engine(1)
                Router Id        Sent To        Recv ID
                0.0.0.0         10.1.94.1       00000000
        Routers not Seeing this Content Engine
                10.1.94.1
        Routers Notified of but not Configured
                -NONE-
        Multicast Addresses Configured
                -NONE-

In ACNS 5.1 software, the debug ftp-proxy EXEC command was added. On page 2-88 of the Cisco ACNS Software Command Reference, Release 5.1 publication, add the following options to the debug command options table:

ftp-proxy

Debugs the native FTP functions (includes such functions as fetching and caching files from an FTP server, posting files to an FTP server, and performing directory listings on an FTP server).

all

Debugs all native FTP functions.

cache

Debugs the cache proxy that is used for native FTP caching (the cache proxy resides on the Content Engine that is operating in nontransparent proxy mode to support native FTP requests).

client

Debugs the native FTP client. In native FTP mode, clients use the native FTP protocol to issue FTP requests, as shown in the following example:

ContentEngine# ftp server.cisco.com

control-proxy

Debugs the control proxy that is used for native FTP caching (the control proxy resides on the Content Engine that is operating in nontransparent proxy mode to support native FTP requests).

parser

Debugs the parser that is used for native FTP caching.

proxy-comm

Debugs the proxy communications used for native FTP functions.

server

Debugs the native FTP server.



Note All the output of the debug ftp-proxy command is written to the file /local1/errorlog/ftp-ctlproxy-errorlog.current with the following exceptions. The output of the debug ftp-proxy cache command and portions of the debug ftp-proxy proxy-comm command output are written to the syslog at debug priority level.


On page 2-88 of the Cisco ACNS Software Command Reference, Release 5.1 publication, replace the description of the debug ftp EXEC command with the following:

ftp

Debugs the FTP functions for FTP-over-HTTP requests (includes fetching and caching files from an FTP server).

all

Debugs all FTP functions for FTP-over-HTTP requests.

cache

Debugs the FTP cache (the Content Engine that is operating in nontransparent proxy mode to cache the contents of the FTP-over-HTTP requests).

client

Debugs the FTP client (end users who are issuing the FTP-over-HTTP request from their browsers).

server

Debugs the FTP server (for FTP-over-HTTP requests).


Group-Type Patterns in Rule Pattern Lists

A group-type pattern is one of the types of rule patterns that you can add to a pattern list. The default operation for the group-type pattern is an OR operation.

In the "List of Rule Patterns" section on page 14-4 of the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1, replace the syntax description for the group-type pattern with the following description:

group-type

Specifies whether the pattern list is an AND or OR type. The default is OR.


In the "Patterns" section on page 2-281 of the Cisco ACNS Software Command Reference, Release 5.1 publication, replace the bulleted description for the group-type pattern with the following description:

Group-type—Specifies whether the pattern list is an AND or OR type. The default is OR.

SmartFilter Software and the rule action no-auth Command Rule Interaction

This documentation update applies to the following three ACNS 5.1 software guides:

Cisco ACNS Software Deployment and Configuration Guide, Release 5.1

Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1

Cisco ACNS Software Command Reference, Release 5.1

The rule action no-auth global configuration command permits specific login and content requests to bypass authentication and authorization features such as LDAP, RADIUS, SSH, or TACACS+. In the following example, any requests from the source IP address (src-ip) 172.16.53.88 are not authenticated.

ContentEngine(config)# rule enable
ContentEngine(config)# rule action no-auth pattern-list 1 protocol all
ContentEngine(config)# rule pattern-list 1 src-ip 172.16.53.88
255.255.255.255

If ACNS 5.1 software is configured for authentication and SmartFilter URL filtering, requests that are allowed to bypass authentication will also bypass the SmartFilter URL filter.

Bandwidth Configuration for Interfaces and Content Services

On page 3-19 of the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1, the tip states that Gigabit Ethernet interfaces run only at 1000 Mbps. This restriction only applies to a Content Engine CE-7320 model that has an optical Gigabit Ethernet interface; the speed of this interface cannot be changed.

For newer models of the Content Engine (for example, the CE-510, CE-565, CE-7305, and CE-7325) that have a Gigabit Ethernet interface over copper, this restriction does not apply; you can configure these Gigabit Ethernet interfaces to run at 10, 100, or 1000 Mbps. Note that on these newer Content Engine models, the 1000 Mbps setting implies autosense (for example, you cannot configure the Gigabit Ethernet interface to run at 1000 Mbps and half duplex). The ACNS 5.x software automatically enables autosense if the speed is set to 1000 Mbps.

pace Command

The pace global configuration command is no longer supported as a separate command in ACNS software, Release 5.1 and later. The functions of the pace command have been incorporated into the bitrate and bandwidth global configuration commands.

Updates to the Cisco ACNS Software Command Reference, Release 5.1 publication are as follows:

On page 2-6, ignore the description and cross-reference to the pace command in Table 2-1.

On page 2-39, replace the syntax description in the "bitrate" section with the following revised description:

http

Configures the maximum pacing bit rate in kilobits per second (kbps) for large files sent using the HTTP protocol.

default

Sets the default bit rate in kbps for large files.

bitrate

Bit rate in kbps (0-2000000).

wmt

Configures the bit rate in kbps for large files sent using the WMT protocol.

incoming

Sets the incoming bit rate settings.

bitrate

Incoming bit rate in kbps (0-2147483647).

outgoing

Sets the outgoing bit rate settings.

bitrate

Outgoing bit rate in kbps (0-2147483647).



Note The aggregate bandwidth used by all concurrent users is still limited by the default device bandwidth, or by the limit configured using the bandwidth command.


On page 2-223, ignore the entire "pace" command section.

pre-load Command

In the pre-load url-list-file path global configuration command, the value for path can be a URL as well as a local file path.

In the Cisco ACNS Software Command Reference, Release 5.1 publication, in the "pre-load" section on page 2-238, replace the syntax description for path with the following description:

path

Path of the file containing the URL list or a URL.


In ACNS 5.1.5 software, the pre-load depth-level-default command was enhanced to support 0 as a preload depth level. Setting the depth level default to 0 would be useful if you have specified URLs in preload.txt files and you do not want the Content Engine to try to preload other URLs.

In the Cisco ACNS Software Command Reference, Release 5.1 publication, in the "pre-load" section on page 2-236, replace the syntax description for path with the following description if you are using ACNS 5.1.5 or later software:

depth-
level-default

Configures the default depth level.

level_number

Depth level of URL download (0-20). The default is 3.


For ACNS 5.1 or 5.1.3 software, the valid values for the preload depth level default are still 1 to 20; 0 is not supported.

NTLM Preload Support

This documentation update applies to the following ACNS 5.1 software guides:

Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1

Cisco ACNS Software Command Reference, Release 5.1

In ACNS 5.1 software, support for preloading NTLM authenticated objects was added. This feature allows NTLM authenticated objects (authenticated objects that reside on the servers that authenticate NTLM only) to be preloaded on a Content Engine.

An entry in a URL list file has the following format:

URL [depth] [domain-name:host-name:host-domain-name]

hostname and host-domain-name can be null; however, domain name is required if NTLM credentials have been configured. (The separator is required.)

http//www.cisco.com 3 apac::

If NTLM-related information is not present in the preload URL list file entry, the authentication scheme falls back to basic authentication.

To preload authenticated content on the Content Engine, you must specify the username and password in the URL list file as follows:

http://username:password@www.authenticatedsite.com/depth_level


Note To enable the Content Engine to fetch specified objects and to store these preloaded objects in its local cache, you must use the http cache-authenticated ntlm global configuration command.


show statistics icap Command

This documentation update applies to the Cisco ACNS Software Command Reference, Release 5.1 publication.

In ACNS software, Release 5.1, the show statistics icap EXEC command was added. You can use this command to display ICAP related statistics for the Content Engine. This command has no arguments or keywords. There is no default behavior or values.

The following is an example of the output of the show statistics icap command.

ContentEngine# show statistics icap
ICAP-client statistics (http proxy)
---------------

Total requests for V1 via RPC:         0
Time per ICAP request (last 1k reqs):  0
ICAP daemon connection error:          0
Bad packets from ICAP daemon:          0
Error parsing HTTP req hdr from ICAP:  0
ICAP daemon internal error:            0

Total requests via outgoing proxy:     0
ICAP daemon overloaded:                0
Other errors:                          0

ICAP Daemon statistics
---------------

Total requests served:                 0
Total requests served:                 0
Average latency in milliseconds:       0.000000
ICAP Service statistics
-----------------------

  Service -- servforicap
   Service Errors:     0
   Service Bypasses:   0
    Server -- icap://1.2.3.4/servforicap
         Total Reqmods (0), Total Respmods (0)
         Modifications (Reqmod - 0), (Respmod - 0)
         No Modifications (Reqmod - 0), (Respmod - 0)
         Error Responses (Reqmod - 0), (Respmod - 0)
         Server Errors:             0
         Server Bypasses:           0
         Options Req Success:       0
         Options Req Failed:        8569
         Max Conn Available         0
         Used Connections:          0
         Total Bytes sent:          0
         Total Bytes received:      0
         Total BPS sent:            0.000000
         Total BPS received:        0.000000
         Server State:              DISCONNECTED
ContentEngine#

Default Port of the Content Engine GUI

On page 12-28 of the Cisco ACNS Caching and Streaming Configuration Guide, Release 5.1, replace the tip with the following:


Tip To access the Content Engine GUI, enter the Content Engine IP address and append the default port number 8003 as the URL address in your browser of choice. For example, enter https://CEIPaddress:8003 as the URL.


Playing Nonhinted IP/TV On-Demand Programs over an ACNS Network

This documentation update applies to the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.

The Cisco Streaming Engine supports only hinted files (MOV and hinted MP4 files) for streaming.


Note Hinted files contain hint tracks, which store packetization information that tells the streaming server how to package the media data. The streaming server uses the packetization information in the hint tracks to stream the media data to the network.


If you are creating a file-based IP/TV program for streaming over an ACNS network, make sure that you use only hinted files such as those with .mov or .mp4 extensions. However, you can pre-position on-demand programs based on nonhinted files such as .mpg files on Content Engines in an ACNS network. Pre-positioned on-demand programs based on nonhinted files are not listed in the IP/TV Viewer program listings or in the web-based program guide.

To watch IP/TV on-demand programs based on nonhinted files when IP/TV is integrated with an ACNS network, use the TV-out feature of the ACNS software. For more information on enabling the TV-out feature and creating playlists, refer to Chapter 11 of the Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.

Restriction on IP/TV Program Manager Configuration

This documentation update applies to the following ACNS 5.1 software guides:

Cisco ACNS Software Deployment and Configuration Guide, Release 5.1.

Cisco ACNS Software Program Manager for IP/TV User Guide, Release 5.1

If a program that you want to deliver over an ACNS network uses live multicast mode, you must use the same multicast IP address for the audio, video, and SlideCast streams.

This restriction on IP/TV Program Manager configuration does not apply if the Content Engine used for live splitting is running ACNS 5.1.5 or later software. However, this restriction still applies if the Content Engine is running ACNS 5.1.1 software, even if you are running IP/TV 5.1.5 or later software on IP/TV Program Manager.

Related Documentation

Your product shipped with a minimal set of printed documentation. The printed documentation provides enough information for you to install and initially configure your product.

Product Documentation Set

In addition to these release notes, the product documentation set includes:

Documentation Guide

Regulatory Compliance and Safety Information for the Cisco Content Networking Product Series

Refer to the Documentation Guide for a complete documentation roadmap and URL documentation links for this product.

Hardware Documentation

Cisco Content Engine 7305 and 7325 Hardware Installation Guide

Installing the Cisco Content Engine 7305 and 7325

Installing Field-Replaceable Units in the Cisco Content Engine 7305 and 7325

Cisco Content Engine 7320 Product Description Note

Cisco Content Engine 510 and 565 Hardware Installation Guide

Installing the Cisco Content Engine 510 and 565

Installing Field-Replaceable Units in the Cisco Content Engine 510 and 565

Cisco Storage Array Installation and Configuration Guide

Release Notes for Cisco Content Delivery Manager 4630

Cisco Content Distribution Manager 4650 Product Description Note

Cisco Content Distribution Manger 4630 Hardware Installation Guide

Cisco Content Router 4430 Hardware Installation Guide

Cisco Content Engine 500 Series Hardware Installation Guide

Release Notes for the Cisco Content Engine 500 Series

Cisco Content Networking Hardware Installation Guide for the Seven-Rack Unit Chassis

Software Documentation

Cisco ACNS Software Deployment and Configuration Guide, Release 5.1

Cisco ACNS Software Caching and Streaming Configuration Guide, Release 5.1

Cisco ACNS Software Command Reference, Release 5.1

Cisco ACNS Software Migration Guide, Release 5.1

Cisco ACNS Software API Guide, Release 5.1

Cisco ACNS Software Program Manager for IP/TV User Guide, Release 5.1

Release Notes for Cisco IP/TV, Release 5.1.5

Release Notes for Cisco ACNS Software, Release 5.1.5 (the release notes you are reading now)

Online Help

Content Distribution Manager GUI online help system for centrally managed ACNS networks

Content Engine GUI online help system for locally deployed Content Engines


Note The term "locally deployed Content Engine" refers to a Content Engine that was initially configured with the autoregistration feature turned off so that the Content Engine would not automatically register with the Content Distribution Manager. Because the Content Engine did not register with the Content Distribution Manager, it can be individually managed through the Content Engine CLI or GUI as a locally deployed device. The Content Engine GUI allows you to remotely configure, manage, and monitor locally deployed Content Engines through your browser.

The Content Distribution Manager GUI and the Content Engine GUI both have context-sensitive online help that can be accessed by clicking the HELP button.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Cisco Marketplace:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Cisco will continue to support documentation orders using the Ordering tool:

Registered Cisco.com users (Cisco direct customers) can order documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Instructions for ordering documentation using the Ordering tool are at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html