Cisco Cisco Content Switching Module Manuale Tecnico

Introduction
 Prerequisites
      Requirements
      Components Used
      Conventions
 Configure
      Network Diagram
      Configurations
 Verify
      CSM debug and show Commands
      Content Engine show Commands
 Troubleshoot
 Related Information

This document describes how to configure a Content Switch Module (CSM) for transparent caching, with
Cisco Content Engines as caches. The transparent cache sits between the user and the server. The CSM is
introduced between the user and the cache. The CSM is intelligent because of its Layer 5 ability to
dynamically analyze content and determine if it is cacheable or not. These guidelines apply:

If cacheable, the CSM load balances the request to the cache service based on the configured
predictor.

• 

If not cacheable, the CSM sends it directly to the origin server. This avoids the performance hit that
occurs when the non−cacheable object goes to the cache, only to have its request redirected by the
cache to the origin server.

• 

There are several balancing methods available, which depend upon how you want to distribute data over the
caches (for example, whole URL, URL string, and so forth).

The CSM can be configured with a list of file extensions to send to the cache. This list is called an Extension
Qualifier List (EQL). Once you configure the 

slb−policy CACHE−POLICY

 under 

vserver

TRANSPARENT

, only requests with the file extensions that are listed in the 

map CACHEABLE url

 list are

sent the cache. If a file extensions is not listed in the 

map CACHEABLE url

 list, then the request will hit

slb−policy NONCACHE−POLICY

.

There are no specific requirements for this document.