Setup and Management for the CacheRaQ

Confidential, Page 2 Cache Installation Outline – Setup & Wizard – Cache Configurations –ICP

LCD Panel setup LCD panel configuration: –Enter the CacheRaQ's IP address, Netmask, and Gateway address –For IP address and netmask: Use the Select button to select either "Setup Net1" or "Setup Net2", depending on which Ethernet interface you want to use. –After configuring Net1 and/or Net2, choose "Setup Gateway" and enter Gateway IP address –Choose Finished when done Proceed to web based setup

Setup Wizard - Step 1 of 4 Connect to the CacheRaQ Enter host, domain and DNS server

Setup Wizard - Step 2 of 4 Cache Settings –Select Transparent or Traditional Proxy mode –Refresh frequency Document refresh frequency : Enter 1-10, depending on how paranoid you are about getting fresh content (1 = very paranoid, 10 = not paranoid; 5 = default)

Setup Wizard - Step 3 of 4 Enter Administrative settings

Setup Wizard - Step 4 of 4 Enter Date, Time & Zone

Cache Administrative Site

Traditional Proxy Mode Essential feature –browsers are configured to make explicit requests from the proxy server Implication –No changes are required to the existing network structure. The CacheQube is simply put out on the network. It is just another host

Traditional Proxy Caching Advantages – Familiar mode of operation – Non HTTP traffic does not go through the web cache server – Router / Firewall address does not need to be changed Disadvantages – Client browsers need to be reconfigured Clients Internet 100Mbps Content Server Proxy Web Cache

Transparent Mode Essential feature: No browser configuration required –Network is arranged so that all client traffic is routed through the CacheRaQ, which then automatically caches HTTP traffic. Implication –Network must be arranged to route client traffic through CacheRaQ. This requires knowledge of TCP/IP networking.

Transparent Mode Web caching server is installed ‘inline’ Advantages – No client browser modifications – Usage monitoring can be enforced Disadvantages – Router / firewall address may have to be changed – All network traffic goes through web caching server Content Server Clients Internet 100Mbps Transparent Web Cache

Web Caching - Clustering You have some number of CacheRaQ –One will be the Cluster Master –The rest will be Cluster Slaves Configure the Cluster Master in the desired mode ( traditional proxy mode or transparent mode ). Configure the Cluster Slaves to be in traditional proxy mode. Note: For best performance, the cluster slaves should use the Network2 interface to communicate with the cluster master.

Clustering InstaCache Clustering allows scalable web caching performance Advantages – Very cost effective technique for web server scaling – Transparent operation - no client browser modifications Clients Internet Cluster Master Cluster Slaves

Web Caching - Clustering Adding Clusters

High Speed Clustering Advantages – Highly scalable – Non HTTP traffic does not go through web cache – Cache not a single point of failure – Automatic failover Disadvantage – Additional cost of level- 4 switch (~$8,000) In conjunction with Layer 4 Switching Clients Internet Example using Alteon Switch

Web Caching - ICP Internet Caching Protocol (ICP) –ICP is used to exchange hints about the existence of URLs in neighbor caches. –Caches exchange ICP queries and replies to gather information for use in selecting the most appropriate location from which to retrieve an object.

Web Caching - ICP

Inter-Cache Protocol Advantages –Allows hierarchical peering between cache servers –Reduces latency –Saves bandwidth for upstream peers ICP Example Clients Internet CustomerCacheRaQ WAN Web server ISP’s CacheRaQ (ICP Parent) WAN LAN

Internet CacheRaQ Sibling CacheRaQ 3. If sibling doesn’t have page, CacheRaQ will contact web site directly 1. Cache miss occurs. CacheRaQ then contacts sibling for web site and misses 2. CacheRaQ then contacts sibling Note: sibling does not contact web site Example Sibling Operation

Example Parent Operation Internet CacheRaQ Parent CacheRaQ 2. Parent then contacts web site directly and caches page(s) 1. Cache miss occurs. CacheRaQ then contacts sibling for web site and misses 3. Parent then serves page(s) back to local CacheRaQ