These release notes are for use with Cisco Cache Engine User Guide, Version 2.0.0 publication and contain information that was not available for inclusion in that manual. These notes discuss the following topics:
The SCSI-LVD only port, located on the front of the Cache Engine, is reserved for future use and is not supported in Version 2.0.1. It is recommended that you do not plug anything into this port.
The Ethernet 1 port, located on the front of the Cache Engine, is reserved for future use and is not supported in Version 2.0.1
If an image intended for a Cache Engine Version 1.x is installed on a Cache Engine Version 2.0.1, you must repair and repartition the DOS file system of the Cache Engine. See the chapter "Maintaining the Cache Engine" in the Cisco Engine User Guide, Version 2.0.0 for instructions. [CSCdm21729]
If the Cache Engine is booted without either hard disk installed, you must power off the Cache Engine, reinsert the disks, and reboot the Cache Engine. If the console connection is lost following the initial boot up display, telnet directly to the Cache Engine and repair the dos file system. See the chapter "Maintaining the Cache Engine" in the Cisco Engine User Guide, Version 2.0.0 for instructions. [CSCdm27685]
When a Cache Engine Ethernet interface speed or duplex function is set using the halfduplex, fullduplex, or bandwidth commands, the corresponding Ethernet switch port autosense function should be turned off, and the duplex function and speed should be set manually. Conversely, if the Ethernet switch port autosense function is turned off, the Cache Engine Ethernet interface duplex function and speed has to be set manually to match the Ethernet switch port settings. The Cache Engine Ethernet interface autosense command will only erase manually set configurations. You must reboot the Cache Engine to start autosensing.
Cisco routers Ethernet interfaces do not negotiate duplex settings. If the Cache Engine is connected to a router directly with a crossover cable, the Cache Engine Ethernet interface has to be manually set to match the router's interface settings. [CSCdm41464]
When using the Cache Engine as a proxy server in conjunction with Internet Explorer, you must enable the Cache Engine to act as a proxy server only for HTTP-related traffic. Currently, setting a proxy server in Internet Explorer defaults to all protocols. To set this manually, go to the Advanced page associated with the proxy server configurations of your Internet Explorer browser. [CSCdm43044]
It is not possible to configure an IP default gateway if an IP address has not been configured on the Cache Engine. You must configure the IP address and subnet on the interface prior to configuring the IP default gateway. [CSCdk92729]
The Cache Engine supports the use of host names when using command-line interface (CLI) commands that require an external IP address entry. [CSCdm03221]
If the IP address of a Cache Engine is changed following the initial boot-up configuration, the Web Cache Communication Protocol (WCCP) communication with any routers is lost. The Cache Engine continues to use the initial IP address in its WCCP communication with the routers. You must reboot the Cache Engine after an IP address change to ensure proper WCCP communication. [CSCdm24895]
If you use the user interface WCCP Web-Cache page to enable the password or weight functionality with WCCP Version 2, these options cannot be disabled once a value or string has been added. These options can only be modified to a non-null value. To remove the use of a password or weight value with the Web-Cache service, you must use the CLI. Use the wccp web-cache command without the password and weight keywords to disable these services. To update the view on the user interface without reinstating the use of a password or weight, use the Refresh button on your browser rather than the Update button on the Web-Cache page. [CSCdm37307]
Currently, it is possible to configure an SNMP community string of up to 255 characters on the Cache Engine. However, if a string of more than 67 characters is used, an error occurs when an SNMP manager sends a request to the Cache Engine using this long community string. This causes the Cache Engine to reboot. [CSCdm45858]
When creating URL lists for use with the URL filtering feature on the Cache Engine, you must include a final carriage return after the last entry in the list. If no carriage return is entered after the final entry, the Cache Engine will not recognize that entry as a valid site for URL filtering. [CSCdm 21722]
If services other than TCP/IP services are enabled arbitrarily from the CLI with more than 24 characters, the Cache Engine reports an error and reboots. [CSCdm29527]
If an invalid server address is used when configuring NTP servers from the CLI, an NTP request to the server may cause the console connection to the Cache Engine to freeze. To unlock the console connection, you must telnet directly to the Cache Engine and delete the invalid server from the configuration. [CSCdm21303]
The TCP client-receive buffer setting is incorrect for windows larger than 64 K. If the TCP client receive buffer is set above 64 K, subsequent segments are constantly set at 32 K. [CSCdm40274]
The Cache Engine allows idle persistent connections to outlive the specified max-idle parameter set in the CLI or the user interface. [CSCdm39593]
When not using persistent connections, a browser is able to retrieve an entire object even if the Content-Length field of an object specified is less that the actual size of the object. The Cache Engine abides by the number of bytes indicated by the Content-Length field, thus interfering with the browser or server service of a misconfigured Content-Length field. [CSCdm44040]
When a client tries to send more than three requests at one time, the connection is closed by the Cache Engine, which may result in lost requests. [CSCdm39594]
In HTTP Version 1.1, persistent connections should be used by default; however, the Cache Engine only uses them if the server sends a keep-alive request in the object header. [CSCdm39595]
It is possible for a heavy traffic load to disable transaction logging. If this occurs, it may be necessary to reenable transaction logging manually. [CSCdm32593]
If the A (address) and PTR (IP map to host name) records (DNS forward and reverse entries) are not consistent, the remote host may send a connection request back to the Cache Engine, which ends connectivity to that site. [CSCdk91038]
When the network link to the Cache Engine is down (for example, a network cable is unplugged), a ping attempt (using the ping {hostname}command) will cycle until it times out after approximately two minutes. This attempt cannot be stopped using Ctrl-C. [CSCdm27092]
The maximum values for the HTTP performance statistics suddenly become large after the Cache Engine runs for a long period of time. The end time for the transaction is sooner than the start time resulting in a negative number for the length of the transaction, which results in a large maximum value. With these large values, the averages are also incorrect. [CSCdm44059]
When receiving POST requests without a Content-Length field, the Cache Engine does not pass the query itself (the body of the request) to the server. Servers usually read the POST body even if no Content-Length field is present. [CSCdm44058]
Objects with a Last-Modified date more recent than the Date (either the Date field in the header or the current date if there is no Date field) should not be cached. However, the Cache Engine caches them, and these objects then expire immediately. [CSCdm39583]
The Cache Engine management user interface provides a link to the transaction log files in the cache file system (cfs). These links are hard-coded to the cache IP. If the Cache Engine is placed behind a firewall, it is only possible to reach the logs from the user interface if you are working from the same subnet behind the firewall. [CSCdk83173]
The Cache Engine management user interface provides a hard-coded link to the Java Monitor applet. If the Cache Engine is placed behind a firewall, the Java Monitor will not work in the user interface unless you are working from the same subnet behind the firewall. [CSCdm24071]
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information,productdocumentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
