Cisco 500 Series Content Engines

Content Engine Frequently Asked Questions

Document ID: 15039

Updated: Jan 31, 2006



This document provides answers to Frequently Asked Questions (FAQ) about the Cisco Content Engine.

Q. Do I need to use WCCP to use the Cisco Content Engine?

A. No, you can use the Content Engine in transparent Web Cache Communication Protocol (WCCP) or proxy mode.

Q. How do I keep Content Engine from placing a site in the cache?

A. Use a Web Cache Communication Protocol (WCCP) redirect-list to send users directly to the site.

Q. What Cisco IOS software versions support both WCCPv1 and WCCPv2?

A. Cisco IOS ® Software Release 12.05T and later.

Q. Can WCCPv2 support ports other than 80?

A. Yes, Web Cache Communication Protocol Version 2 (WCCPv2) can support other ports, however, the caching device must negotiate the port with the WCCP router.

Q. How do I upgrade the software version on the CE 5xx series?

A. Refer to the Upgrading and Downgrading Procedures section of the Cisco ACNS Software Maintenance and Troubleshooting Guide for respective codes. Refer to Cisco Application and Content Networking Solution Software Technical Documentation for all release code documentation.

Q. Can you explain why Content Engine is slow to connect to a Web server, cannot connect to a Web server, or cannot transfer files?

A. When receiving a connection, a server generally attempts to map a fully qualified domain name to an IP address to determine the source domain of a connection. If the Content Engine does not have a Domain Name System Pointer (DNS PTR) record reachable by the receiving server, the connection could be delayed or not permitted. The delay occurs if the server's DNS server times out while requesting the PTR record. If the PTR record does not exist or is not received, the server may refuse access to the Content Engine. To prevent this, configure a DNS PTR record for the IP address or Network Address Translation (NAT) address of the Content Engine.

Q. How do I configure the Content Engine as a proxy server?

A. Configure all clients' Web browsers to go to the Content Engine. Configure the Content Engine with the following command to allow incoming or outgoing requests on a specific port number:

http | proxy {incoming ports | outgoing {host {{hostname | ipaddress} ports [prima]

Note:  No Web Cache Communication Protocol (WCCP) redirection is required.

Related Information

Updated: Jan 31, 2006
Document ID: 15039