Cachebox 310 For Large Network core - Enterprise Class Web Caching Server

Introduction of Cachebox 310 Cachebox 310 is basically designed for Huge network core i.e. for large network areas. It’s a perfect caching solution used for hundred of ISPs users worldwide. Cachebox is a High performance caching solution which is specially designed to manage modern Internet traffic with full security, reliability and problem solving technique. Cachebox 310 is a first web cache appliances which is using Solid State Drives (SSD) and delivers 3600 HTTP request per second in a 1 U format. It can support more than 20,000 user per appliance. CACHEBOX310 stores large file like internet video – include YouTube, Metacafe and many more…., It also caches the software updates for Operating system and Application that saves the vendor bandwidth up to 20 % - 40%. Cachebox is also compatible in heavy caching workload, You can cluster two or more Cachebox 310with WCCP or load balancer to increase its performance

Features & Bandwidth Save bandwidth, save money Fully featured caching software support for HTTP Video caching (YouTube, Metacafe, Vimeo, Dailymotion, 4shared, Veoh etc) Software update caching (MS Windows, Apple, Avast, Android, AVG Kaspersky etc) Pre-fetching and mirroring of content Browse safely and log activity Secure HTTPS and SSH management interface MS Active Directory integration via NTLM and Kerberos authentication RADIUS/LDAP authentication

Features & Bandwidth Easier to Manage Intuitive, secure web admin interface Setup and caching assistants On-box graphical reporting / scheduled reporting to monitor caching and network performance Automated on-box / off-box backups, alerting Multi-lingual interface Control and administer multiple users Validated and automated data entry Operating system runs from read-only industrial CompactFlash SNMP and Custom ACLs support Logging

Features & Bandwidth Flexible deployment Supports multiple transparent and explicit deployment modes Optional Fail-to-Wire resiliency Clustering, load balancing and hierarchies WCCP Support (v.2, GRE and Layer 2) IP spoofing Firewall with NAT forwarding for networking flexibility iKVM remote access technology

Specifications

Why Cachebox 310 Cachebox 310 is used for Large network core based organization. Cachebox 310 is compatible for saving bandwidth in large network of 20,000 people or more than that. Cachebox serves web pages to user from local web cache, so that less data fetches from the Internet. It has an ability to add more users without increasing capacity Cache saving helps you to grow your revenue too customers each spending an average $25 per month and you expect your hit rate to be 35%, your current monthly income is $37,500 and caching could help you make an additional $13, x $25 = $37,500 current income $37,500 x (35/100) = $13,125 additional monthly income That’s over $150,000 per year, dozens of times higher than the cost of an average CACHEBOX. For ISPs, in addition to bandwidth savings, you can typically provide a speed increase for customers of around 20-50%. An increase of this magnitude leads to increased customer satisfaction, reduced churn-rate, lower marketing costs and an opportunity to increase Average Revenue Per User (ARPU).

Delay upgrade to your bandwidth Cache upgrade your bandwidth as your traffic grows. It upgrade automatically so you keep on saving with a cache. For Example: you have a 100Mb connection with average peak load of 80% (80Mb) and growth of 60Mb per year. You would run out of bandwidth in 4 months: A cache saves up to 35 % would bring your current peak load down to 52Mb and your growth rate to 39Mb per year. This would keep you under your limit for 15months – an 11 month delay: If your current cost were Rs per month and after upgrade it would be Rs , your saving before upgrade would be: 60Mb / 12 = 5Mb monthly growth => 4 months to fill the spare 20Mb Year one: 52Mb + 39Mb = 91Mb Year two: 91Mb + 39Mb = 130Mb (capacity reached after 3 months) 11 (upgrade delay in months) x Rs.5000 (cost difference) = Rs cost saving

Delay upgrade to your bandwidth After you upgrade, caching continues working to save you bandwidth and delay future upgrades. You continue to save money month after month.

How to configure Zero Penalty Hit packet marking The idea behind ZPH is to allow classification of packets generated from the Squid cache engine towards clients. The classification is based on whether the content is being served from cache (a cache HIT), or is being retrieved from a remote server (a cache MISS). This feature can be used when QoS limits imposed by bandwidth management devices are to be circumvented. Configuration through the Custom Config feature can be done as follows: acl matched_traffic src /24 tcp_outgoing_tos 0x30 matched_traffic zph_mode tos zph_local 0x30 zph_parent 0

CACHEBOX Custom Config – ZPH All HTTP traffic with a HIT from the cache destined for clients on the ' /24' subnet will now be tagged with 0x30 which can be matched externally. Reference ToS/Hex/DSCP values: TOS hex binary DSCP hex binary Classid AFClass 40 0x x0a :111 AF x x0c :112 AF x x0e :113 AF x x :121 AF x x :122 AF x x :123 AF x x1a :131 AF x x1c :132 AF x x1e :133 AF x x :141 AF x x :142 AF x x :143 AF 43 How to configure Zero Penalty Hit packet marking

Lunkad Sky Station, Konark Nagar, Mhada Colony, Viman Nagar, Pune, Maharashtra ,India Tel : | Fax : |