These release notes are for use with Using the Cisco Cache Engine and contain information that was not available for inclusion in that manual. They discuss the following topics:
The following conditions may occur when using the 1.7.0 version of the Cache Engine system software.
Some sites report that web pages load with broken or incomplete images. Clear the cache using the FSReset and FSSync commands on the Cache Engine's command line interface (CLI) if you experience this problem. See Appendix A, "Console Command Reference" and the section "FSReset and FSSync" in Using Cisco Cache Engine, Version 1.7 document for a description of these commands. [CSCdk29292]
Some sites report that large file transfers are interrupted during very slow network conditions. Adjust the TCP settings (click Tuning and select the TCP option) from the web graphical user interface (GUI) if you experience this problem. See Chapter 3, "Managing the Cache Engine" and the section "Working with Tuning Options" in Using Cisco Cache Engine, Version 1.7 document for a description of the TCP tuning options. [CSCdk49101]
Some sites report that they have difficulty posting data to select web sites. Add a Web Cache Control Protocol (WCCP) access control list (ACL) on the router to bypass the Cache Engine if you encounter this problem. See Appendix C, "Web Cache Control Protocol" in Using Cisco Cache Engine, Version 1.7 document for a description of WCCP. [CSCdk49099]
Some sites report that they receive an incorrect personal customized home page at select web sites. If you encounter this problem, disable cookie caching (click Tuning and select the Freshness option) by selecting "No" on the Freshness web GUI page. See Chapter 3, "Managing the Cache Engine" and the subsection "Changing How Objects are Cached Using Freshness" under the section "Working with Tuning Options" in Using Cisco Cache Engine, Version 1.7 document to view the Freshness page options. [CSCdk83298]
The information collected by the Address Resolution Protocol (ARP) requests is overwritten by subsequent responses. This problem occurs when a routing entry is created using an invalid subnet mask. This entry causes the Cache Engine to "ARP" for the MAC addresses of hosts that are not connected directly to the network on which the Cache Engine resides.
However, the routers answer the ARP requests, acting as a proxy agent. In configurations where more than one router is attached to the network on which the Cache Engine resides, multiple proxy ARP replies may be received. This causes subsequent replies to overwrite the initial reply message. When this occurs, an error message is generated by the Cache Engine that includes the phrase "(tNetTask): arp info overwritten for." This problem will be corrected in future releases. For now, ignore the error messages generated in these scenarios. [CSCdj76551]
The Cache Engine fails to autodetect 10 MB/sec. full-duplex network connections. The connections register as half-duplex because the line-speed autosense detection on the network adapter card does not determine this setting correctly.
The workaround for this problem is to use the EthernetConfig command on the Cache Engine's command line interface to verify your ethernet link works properly. Connect your Cache Engine to its hub, switch or router, then use one of the commands below to ping your system:
EthernetConfig(100, "full")
EthernetConfig(100, "half")
EthernetConfig(10, "full")
EthernetConfig(10, "half")
You must also attach a console to the Cache Engine to initially configure the engine. This can be a normal VT100-style console, or a laptop or desktop computer that can attach to the engine's serial port. Once you have completed the basic configuration, you can manage the Cache Engine using a web browser from any machine. [CSCdK24099]
Using any unsupported VxWorks commands on the Cache Engine's command line may cause the Cache Engine to fail. Supported VxWorks commands are described in two locations:
1. Appendix B of the Using Cisco Cache Engine manual
Using unsupported VxWorks commands on the Cache Engine command line may cause unrecoverable damage to your Cache Engine. For example, if you use the diskInit command, you will loose access to all DOS partitions on your Cache Engine. Subsequent attempts to boot the Cache Engine will fail because the boot files have been deleted. The only workaround is to contact the TAC. [CSCdk11957]
If two Internet Cache Protocol (ICP) hosts are misconfigured as each other's Parent cache, an infinite loop results. [CSCdk17264]
If you issue the ping command when using the Recovery floppy diskette, the system defaults into an infinite loop. To stop the infinite loop, you must reboot the Cache Engine. To workaround this problem, use a count variable with the ping command. For example, the site, www.domain.com, will be pinged 3 times. [CSCdj92645]
> ping "www.domain.com", 3
If the following (example) sites are listed in a badurl.lst file, you cannot browse to these (example) locations separately:
However, you can browse to the http://www.gm.com/vehicles site, but you should not be allowed to browse there due to the http://www.gm.com/ entry in the badurl.lst file. Furthermore, rather than blocking a bogus gm.com URL starting with a letter after "v", such as http://www.gm.com/zzz, the Cache Engine looks for it and returns an object-not-found error.
Mixed results occur when you combine two different badurl.lst files: at times all of one file is blocked, and other times it is not blocked. If the badurl.lst file includes only http://www.gm.com/ and http://www.netking.com/, all subdirectories are blocked. [CSCdk23156]
After power-cycling a Cache Engine, a bad label error message may appear, and the box may fail to boot. This problem may last up to two or three power-cycles. If the problem persists, contact TAC. [CSCdj66667]
It is difficult to force the Cache Engine to be bypassed using the Microsoft Internet Explorer web browser version 4.0, because IE does not send pragma:no cache HTTP headers in transparent mode. The workaround is to use the Netscape Navigator web browser and press Shift and Reload. [CSCdk40032]
Transaction logging may generate very large log files if the Cache Engine services large amounts of traffic. Therefore, it is very important to set the interval for the archiving process accurately. Go to the Logging section and press the Transaction Logs link. The "Archive working log after __ seconds" field should contain the proper setting for your environment.
If Transaction logging encounters an error during logging, it generates an Event (viewable from the Events GUI page) and disables itself. The most common Transaction logging error results from lack of disk space on the DOS partition. If you encounter a logging error, we recommended that you save the working.log file by removing it from the LOGS directory using FTP or the GUI. Re-enabling logging will remove the last working.log file. Furthermore, if it is determined that the problem is due to lack of free space on the DOS partition, you should decrease the interval for archiving to prevent large log files from being created. [CSCdk43107]
The Cache Engine's Monitor section contains a Java applet that does not work with beta versions of Netscape Navigator. [CSCdk42188]
"Uptime" is not a reliable measure if the Time/Date is modified after you boot the Cache Engine. This is because the time is stamped during boot up and then compared with the current time to measure how long the Cache Engine has been up. The Monitor section contains a Java applet that may not function with some Beta versions of Netscape Navigator. [CSCdk10829]
Since the Cache Engine has 1,000,000 slots in its table, and it uses a hashing with CRC32 on the URL, distribution should be excellent. Instead, a collision occurs about 1/63,000 because the directory code uses a CRC32 hash for fast lookups. Although CRC32 is excellent at hashing dissimilar strings, it is less effective at hashing similar strings. Since many URLs are very similar, there are more hash collisions than one might expect. An improved hash algorithm will be used in future releases. [CSCdj80214]
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.
