The document discusses using Cisco WCCP or PBR routing policies to insert ADs using Adzilla. It provides background on WCCP, details Adzilla's solution of deploying Cisco WAE content engines and establishing a relationship with routers using WCCP. It then shows sample WCCP and PBR configurations for routers, and notes known issues around using PBR for failover versus WCCP allowing multiple caches.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online from Scribd
The document discusses using Cisco WCCP or PBR routing policies to insert ADs using Adzilla. It provides background on WCCP, details Adzilla's solution of deploying Cisco WAE content engines and establishing a relationship with routers using WCCP. It then shows sample WCCP and PBR configurations for routers, and notes known issues around using PBR for failover versus WCCP allowing multiple caches.
The document discusses using Cisco WCCP or PBR routing policies to insert ADs using Adzilla. It provides background on WCCP, details Adzilla's solution of deploying Cisco WAE content engines and establishing a relationship with routers using WCCP. It then shows sample WCCP and PBR configurations for routers, and notes known issues around using PBR for failover versus WCCP allowing multiple caches.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online from Scribd
The document discusses using Cisco WCCP or PBR routing policies to insert ADs using Adzilla. It provides background on WCCP, details Adzilla's solution of deploying Cisco WAE content engines and establishing a relationship with routers using WCCP. It then shows sample WCCP and PBR configurations for routers, and notes known issues around using PBR for failover versus WCCP allowing multiple caches.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online from Scribd
A brief introduction WCCP Background • When a user (client) requests a page from a web server (located in the Internet, in this case), the router sends the request to a Cisco Cache Engine (Cache 1, or Cache 2 based on the Adzilla diagram). If the cache engine has a copy of the requested page in storage, the engine sends the user that page. Otherwise, the engine gets the requested page and the objects on that page from the web server, stores a copy of the page and its objects (caches them), and forwards the page and objects to the user. Adzilla Solution • Will deploy multiple Cisco WAE-612 content engines. • Will allow the Router using the wccp protocol to establish a relationship directly with the WAE-612s (Cisco content caches). • The Content forwarding and requesting service will reside directly on the NDR. Sample Config (All Traffic) Using WCCP • lslky002hb7# configure terminal • lslky002hb7(config)# ip wccp enable • lslky002hb7(config)# interface (insert uplinks from CMTS or ICE here) • lslky002hb7(config-if)# ip web-cache redirect • lslky002hb7(config-if)# end • You will need to do step 3 -6 for each unterface that uplinks from a cmts or aggregation switch Sample Config (Restricted Traffic) Using WCCP • lslky002hb7 # configure terminal • lslky002hb7(config)# access-list 100 deny ip any host 74.128.1.1 • lslky002hb7(config)# access-list 100 permit ip any any • lslky002hb7(config)# ip wccp enable • lslky002hb7(config)# ip wccp redirect-list 100 • lslky002hb7(config)# interface (insert uplinks from CMTS or ICE here) • lslky002hb7(config-if)# ip web-cache redirect • lslky002hb7(config-if)# end Sample Config using PBR • Ip access-list extended permit ip http-redirect – Permit ip any any eq 80 (specifies all traffic with a destination of port 80)
• route-map http-redirect permit 10
• match ip address http-redirect • set ip default next-hop X.X.X.X (address of adzilla)
• route-map http-redirect permit 20
• set default interface null0
• Interface (apply to all CMTS uplinks)
– ip policy route-map http-redirect Known Issues • In the absence of a Layer-4 switch (eg. Foundry, Alteon) Adzilla transparency is probably best achieved using Cisco's Web Cache Coordination Protocol (WCCP). Policy Based Routing (PBR) can be used but suffers from one significant limitation: failover. If you choose to use PBR and your Adzilla cache dies or needs to be rebooted then all your web surfing stops. Further, WCCP allows multiple caches to participate (for further fault tolerance) while PBR only allows one. WCCP does place a load on your router in excess of normal HTTP traffic. Hence, ensure that your router has adequate RAM and CPU horsepower. • This is based on what I know about the Adzilla solution as of 12/13/2007