WCCP技术.pptVIP

Web Cache Communication Protocol(WCCP) Introduction Objective - Provide a conceptual understanding on what WCCP is, the factors that have gone into it’s development, and thoughts on what we (Cisco) can use for tomorrow. This is not in-depth technical WCCP Web Cache Communication Protocol (WCCP) Content Routing Technology first introduced in 1997 Provides mechanism to redirect traffic flows [originally caches] in real-time Has in-built load-balancing mechanism, scaling, fault tolerance, and service-assurance (failsafe) mechanisms First - what exactly is the name? WCCP’s many names: Web Cache Coordination Protocol Web Cache Control Protocol Web Cache Communication Protocol is the name was finally reached via internal consensus. (yes we need to change the names on the Internet-Drafts) Second - WCCP is not just Web WCCPv2 works with any TCP/UDP port. The name suggest “web,” but the key value is it’s use for redirection of other applications. Web Cache Communication Protocol (WCCP) WCCPv1/WCCPv2 implemented by several vendors: Inktomi, NetApps, CacheFlow, Novell, Infolibra - orginal licensees Squid has a version with WCCPv1 w/ WCCPv2 coming (when Lincoln has time) Transparent Redirection of a Flow in the POP Factors that went into the design of WCCP Design Objectives for the ISP Transparent Redirection of a IP flow based on source, destination, and/or port number. Transparent Integration - no rebuilding the POP to add this service. Failed open - if the service fails, it should not effect the core IP service nor any other services. Design Objectives for the ISP Not to effect the primary packet flow of the POP - if not redirected - then is CEF/dCEF Switched! Design Objectives for the ISP Work with the multi-level L2/L3 redundancy of the ISP POP. Equal paths in the IGP + CEF leads packet asymmetry. Design Objectives for the ISP Provide the ISP with Flexibility on the point of redirection. Design Objectives for the Service Group Linear Scalability with the Cache - m