CSS Getting Started Guide (Software Version 5.00) - Configuring the CSS [Cisco CSS 11000 Series Content Services Switches]

Table Of Contents

Configuring the CSS

Service, Owner, and Content Rule Overview

Using the Configuration Script

Configuring Layer 3 Load Balancing

Configuring Layer 5 Load Balancing

Configuring Proxy Cache

Configuring Transparent Cache

Where to Go Next

Configuring the CSS

This chapter provides information on service, owner, and content rules, and how to configure the CSS through configuration scripts. This chapter contains the following sections:

•Service, Owner, and Content Rule Overview

•Using the Configuration Script

Service, Owner, and Content Rule Overview

The CSS enables you to configure services, owners, and content rules to direct requests for content to a specific destination service (for example, a server or a port on a server). By configuring services, owners, and content rules, you optimize and control how the CSS handles each request for specific content.

•A service is a destination location where a piece of content resides physically (a local or remote server and port). You add services to content rules. Adding a service to a content rule includes it in the resource pool that the CSS uses for load balancing requests for content. A service may belong to multiple content rules.

•An owner is generally the person or company who contracts the web hosting service to host their web content and allocate bandwidth as required.

•A content rule is a hierarchical rule set containing individual rules that describe which content (for example, .html files) is accessible by visitors to the web site, how the content is mirrored, on which server the content resides, and how the CSS should process requests for the content. Each rule set must have an owner.

Note For detailed information on creating and configuring services, owners, and content rules, refer to the Content Services Switch Basic Configuration Guide.

When a request for content is made, the CSS:

1. Uses the owner content rule to translate the owner's Virtual IP address (VIP) or domain name using Network Address Translation (NAT) to the corresponding service IP address and port.

2. Checks for available services that match the content request.

3. Uses content rules to choose which service can best process the request for content.

4. Applies all content rules to service the request for content (for example, load balancing method, redirects, failover, stickiness).

The CSS uses content rules to determine:

•Where the content physically resides, whether local or remote

•Where to direct the request for content (which service or services)

•Which load balancing method to use

The type of rule also implies the network layer at which the rule functions.

•A Layer 3 content rule implies a destination IP address of the host or network.

•A Layer 4 content rule implies a combination of destination IP address, protocol, and port.

•A Layer 5 content rule implies a combination of destination IP address, protocol, port, and Universal Resource Locator (URL) that may or may not contain an HTTP cookie or a domain name.

Note A Layer 5 rule supports the HTTP CONNECT, GET, HEAD, POST, PUSH, and PUT methods.

Content rules are hierarchical. That is, if a request for content matches more than one rule, the characteristics of the most specific rule apply to the flow. The hierarchy for content rules is shown below. The CSS uses this order of precedence to process requests for the content, with 1 being the highest match and 8 being the lowest match.

1. Domain name, IP address, protocol, port, URL

2. IP address, protocol, port, URL

3. IP address, protocol, port

4. IP address, protocol

5. IP address

6. Domain name, protocol, port, URL

7. Protocol, port, URL

8. Protocol, port

Using the Configuration Script

The CSS initiates the configuration script automatically when you log in and it does not detect an existing startup-config file.

Note If you want to configure the CSS manually, refer to the Content Services Switch Basic Configuration Guide.

You need to enter the following information as the configuration script completes:

•IP address and subnet mask for circuit VLAN1 (all interfaces are assigned to VLAN1 by default)

•IP address for the default gateway

•IP addresses for the servers

•Virtual IP address (VIP) for the content rule

The configuration script allows you to create services, owners, and content rules based on your entries and then enables you to:

•Configure Layer 3 load balancing

•Configure Layer 5 load balancing

•Configure Proxy cache

•Configure Transparent cache

•Exit from the script and save the information you entered to the running-config

To accept the script default values, press the Enter key at the prompts. To quit the script, enter "q" at any prompt.

You may also initiate the configuration script manually by entering the script play setup command.

To clear an existing running-config, use the clear running-config command from SuperUser mode. To clear an existing startup-config, use the clear startup-config command from SuperUser mode.

The following pages show you the entire configuration script including:

•Bold text to indicate where you enter information

•Explanations to help you use the script
##############################################
#Setup Script for the Content Services Switch#
##############################################
 
Checking for Existing Config...
No startup-config was found, continue with the setup script [y/n]? y
Note: Pressing "q" after any prompt quits setup. Pressing <CR> after 
any [y/n] defaults to "y".
Warning: All circuit VLAN IP addresses must be on a different subnet 
than the Ethernet Mgt port IP address. The existing Ethernet Mgt port 
IP address is: 10.0.4.251
Add an IP address to VLAN1: [default = 192.168.10.1] 192.168.3.6
Add an IP subnet mask to VLAN1: [default = 255.255.255.0]
Warning: The default gateway IP address must be on the same subnet as 
VLAN1. VLAN1 IP address is: 192.168.3.6
Add IP address for default gateway: [default = 192.168.3.2] 
192.168.3.3
Pinging the default gateway: 100% Success.
Which feature do you want to configure?
[1] Layer3 load balancing 
[2] Layer5 load balancing 
[3] Proxy cache 
[4] Transparent cache 
[5] Exit script
If you select option 5 to exit the script, the CSS saves the information you entered to the running-config and then displays the running-config.

Configuring Layer 3 Load Balancing

A Layer 3 load balancing configuration enables the CSS to use a Virtual IP address (VIP) to load balance Web traffic to Web servers based on IP addresses.

When you select Layer 3 load balancing, the script automatically:

•Creates an owner (L3_Owner)

•Creates a Layer 3 content rule (L3_Rule) and defines ArrowPoint Content Awareness (ACA) as the load balance method

•Activates the services

•Activates the content rule

•Saves the running-config to the startup-config

The script enables you to configure:

•Service name (default name is Server1)

•Service IP address

•VIP for the content rule

To configure Layer 3 load balancing, enter 1.
Which feature do you want to configure?
[1] Layer3 load balancing
[2] Layer5 load balancing
[3] Proxy cache
[4] Transparent cache
Enter the number for the feature you want to configure: 1
To accept the script default values, press the Enter key at the prompts.
Creating Layer3 load balancing
Enter service name: [default = Server1]
Enter service IP address: [default = 192.168.10.3] 192.168.3.58
Create another service? [y/n]? y
Enter service name: [default = Server2]
Enter service IP address: [default = 192.168.10.3] 192.168.3.59
Create another service? [y/n]? n
Enter Virtual IP address for L3_Rule: [default = 192.168.10.4] 
192.168.3.6
After the configuration is completed, the script automatically:

•Displays the running-config

•Saves the running-config to the startup-config
Showing the Running Config
!Generated MAR 6 17:53:49
!**************** GLOBAL *****************
ip route 0.0.0.0 0.0.0.0 192.168.3.3
!**************** CIRCUIT ****************
circuit VLAN1
ip address 192.168.3.6 255.255.255.0
!**************** SERVICE ****************
service Server1
	ip address 192.168.3.58
	active
service Server2
	ip address 192.168.3.59
	active
!**************** OWNER ******************
owner L3_Owner
	content L3_Rule
	add service Server1
	add service Server2
	vip address 192.168.3.6
	balance aca
	active
##########################################
##    Setup Completed Successfully!!!   ##
##########################################
For detailed configuration information, refer to the Content 
Services Switch Basic Configuration Guide.
Configuring Layer 5 Load Balancing

A Layer 5 load balancing configuration enables the CSS to use a VIP address to load balance Web traffic to Web servers based on URLs.

When you select Layer5 load balancing, the script automatically:

•Creates an owner (L5_Owner)

•Creates a Layer 3 content rule (L3_Rule)

•Creates a Layer 5 content rule (L5_Rule) and defines:

–Protocol tcp

–Port 80

–URL "/*"

–Load balance method as ACA

•Activates the services

•Activates the content rule

•Saves the running-config to the startup-config

The script enables you to configure:

•Service name (default name is Server1)

•VIP for the content rule

To configure Layer 5 load balancing, enter 2.
Which feature do you want to configure?
[1] Layer3 load balancing
[2] Layer5 load balancing
[3] Proxy cache
[4] Transparent cache
Enter the number for the feature you want to configure: 2
To accept the script default values, press the Enter key at the prompts.
Creating Layer5 load balancing
Enter service name: [default= Server1] 
Enter service IP address: [default = 192.168.10.3] 192.168.3.58
Create another service? [y/n]? n
Enter Virtual IP address for L5_Rule: [default = 192.168.10.4] 
192.168.3.8
After the configuration is completed, the script automatically:

•Displays the running-config

•Saves the running-config to the startup-config
Showing the Running Config
!Generated MAR 6 17:53:49 
!**************** GLOBAL *****************
ip route 0.0.0.0 0.0.0.0 192.168.3.3
!**************** CIRCUIT ****************
circuit VLAN1
ip address 192.168.3.6 255.255.255.0
!**************** SERVICE ****************
service Server1
	ip address 192.168.3.58
	active
!**************** OWNER ******************
owner L5_Owner
content L3_Rule
	add service Server1
	vip address 192.168.3.8
	balance aca
	active
content L5_Rule
	add service Server1
	vip address 192.168.3.8
	protocol tcp
	port 80
	url "/*"
	balance aca
	active
##########################################
##    Setup Completed Successfully!!!   ##
##########################################
For detailed configuration information, refer to the Content 
Services Switch Basic Configuration Guide.
Configuring Proxy Cache

A proxy cache configuration enables the CSS to use a Virtual IP address (VIP) to load balance Web traffic to proxy cache servers based on domain name.

When you select Proxy Cache, the script automatically:

•Creates an owner (Proxy_Owner)

•Creates a content rule (Proxy_Rule) and defines:

–Service type as proxy-cache

–Protocol tcp

–Port 8080

–URL "/*"

–Load balance method as domain

–Application type HTTP

•Activates the services

•Activates the content rule

The script enables you to configure:

•Service name (default name is Proxy_Cache1)

•VIP for the content rule

To configure a proxy cache configuration, enter 3.
Which feature do you want to configure?
[1] Layer3 load balancing
[2] Layer5 load balancing
[3] Proxy cache
[4] Transparent cache
Enter the number for the feature you want to configure: 3
To accept the script default values, press the Enter key at the prompts.
Creating Proxy Cache Configuration
Enter service name: [default=Proxy_Cache1]
Enter service IP address: [default = 192.168.10.3] 192.168.3.60
Create another service? [y/n]? n
Enter Virtual IP address for Proxy_Rule: [default = 192.168.10.4] 
192.168.3.9
After the configuration is completed, the script automatically:

•Displays the running-config

•Saves the running-config to the startup-config
Showing the Running Config
!Generated MAR 6 17:53:49
!**************** GLOBAL *****************
ip route 0.0.0.0 0.0.0.0 192.168.3.3
!**************** CIRCUIT ****************
circuit VLAN1
ip address 192.168.3.6 255.255.255.0
!**************** SERVICE ****************
service Proxy_Cache1
	ip address 192.168.3.60
	type proxy-cache
	port 8080
	protocol tcp
	active
!**************** OWNER ******************
owner Proxy_Owner
content Proxy_Rule
	add service Proxy_Cache1
	vip address 192.168.3.9
	port 8080
	protocol tcp
	url "/*"
	balance domain
	application http
	active
##########################################
##    Setup Completed Successfully!!!   ##
##########################################
For detailed configuration information, refer to the Content 
Services Switch Basic Configuration Guide.
Configuring Transparent Cache

A transparent cache configuration enables the CSS to redirect cacheable HTTP traffic to transparent cache servers based on IP address and port (80). The CSS directs non-cacheable HTTP traffic to the origin servers.

When you select Transparent Cache, the script automatically:

•Creates an owner (Transparent_Owner)

•Creates a content rule (Transparent_Rule) and defines:

–Service type as transparent-cache

–Protocol tcp

–Port 80

–Extension Qualifier List (EQL) named Cacheable that contains the file types displayed in the sample running-config file

–URL "/*" eql Cacheable

–Load balance method as domain

–Failover type as bypass

–Application type HTTP

•Activates the services

•Activates the content rule

The script enables you to:

•Configure a service name (Transparent_Cache1)

•Define whether to direct only cacheable content or all content to the cache servers

To configure a transparent cache configuration, enter 4.
Which feature do you want to configure?
[1] Layer3 load balancing
[2] Layer5 load balancing
[3] Proxy cache
[4] Transparent cache
Enter the number for the feature you want to configure: 4
To accept the script default values, press the Enter key at the prompts.
Creating Transparent Cache Configuration
Enter service name: [default = Transparent_Cache1]
Enter service IP address: [default = 0.0.0.0] 192.168.3.7
Create another service? [y/n]? n
Transparent caching can be configured to direct only cacheable content 
to the cache server. Non-cacheable content is sent directly to the 
origin server.
The alternative is to direct all traffic to the cache server 
regardless of whether the content is cacheable.
Should only cacheable content be directed to the cache server? [y/n]?
Enter:

•y to define URL "/*" as eql-cacheable in the content rule and allow the CSS to direct only cacheable content to the cache servers

•n to define URL "/*" in the content rule and allow the CSS to direct all content to the cache servers

After the configuration is completed, the script automatically:

•Displays the running-config

•Saves the running-config to the startup-config
Showing the Running Config
!Generated MAR 6 17:53:49
!**************** GLOBAL *****************
ip route 0.0.0.0 0.0.0.0 192.168.3.3
!**************** CIRCUIT ****************
circuit VLAN1
ip address 192.168.3.6 255.255.255.0
!**************** SERVICE ****************
service Transparent_Cache1
	ip address 192.168.3.7
	type transparent-cache
	port 80
	protocol tcp
	active
!****************** EQL ******************
eql Cacheable
	description "This EQL contains
		extensions of cacheable content"
	extension pdf "Acrobat"
	extension fdf "Acrobat Forms Document"
	extension au "Sound audio/basic"
	extension bmp "Bitmap Image"
	extension z "Compressed data
		application/x-compress"
	extension gif "GIF Image image/gif"
	extension html "Hypertext Markup
		Language text/html"
	extension htm
	extension js "Java script
		application/x-javascript"
	extension mocha
	extension jpeg "JPEG image image/jpeg"
	extension jpg
	extension jpe
	extension jfif
	extension pjpeg
	extension pjp
	extension mp2 "MPEG Audio audio/x-mpeg"
	extension mpa
	extension abs
	extension mpeg "MPEG Video video/mpeg"
	extension mpg
	extension mpe
	extension mpv
	extension vbs
	extension m1v
	extension pcx "PCX Image"
	extension txt "Plain text text/plain"
	extension text
	extension mov "QuickTime 	video/quicktime"
	extension tiff "TIFF Image image/tiff"
	extension tar "Unix Tape Archive
		application/x-tar"
	extension avi "Video for Windows
		video/x-msvideo"
	extension wav "Wave File audio/x-wav"
	extension gz "application/x-gzip"
	extension zip "ZIP file
		application/x-zip-compressed"
!***************** OWNER *****************
owner Transparent_Owner
content Transparent_Rule
	add service Transparent_Cache1
	port 80
	protocol tcp
	url "/*" eql Cacheable or url "/*"
	balance domain
	failover bypass
	application http
	active
##########################################
##    Setup Completed Successfully!!!   ##
##########################################
For detailed configuration information, refer to the Content 
Services Switch Basic Configuration Guide.
Where to Go Next

Refer to the Content Services Switch Basic Configuration Guide and the Content Services Switch Advanced Configuration Guide for detailed information on configuring the CSS.

	CSS Getting Started Guide (Software Version 5.00)
	Configuring the CSS
CSS Getting Started Guide (Software Version 5.00) Cisco Content Services Switch Getting Started Guide Index (Software Version 5.00) About This Guide Unpacking and Installing the CSS Cabling the CSS Booting the CSS Configuring the CSS Specifications Cable Pinouts Troubleshooting Log Messages Regulatory Information	Download this chapter Configuring the CSS Download the complete book Cisco Content Services Switch Getting Started Guide (Software Version 5.00), Book Length PDF (PDF - 2 MB) Table Of Contents Configuring the CSS Service, Owner, and Content Rule Overview Using the Configuration Script Configuring Layer 3 Load Balancing Configuring Layer 5 Load Balancing Configuring Proxy Cache Configuring Transparent Cache Where to Go Next Configuring the CSS This chapter provides information on service, owner, and content rules, and how to configure the CSS through configuration scripts. This chapter contains the following sections: •Service, Owner, and Content Rule Overview •Using the Configuration Script Service, Owner, and Content Rule Overview The CSS enables you to configure services, owners, and content rules to direct requests for content to a specific destination service (for example, a server or a port on a server). By configuring services, owners, and content rules, you optimize and control how the CSS handles each request for specific content. •A service is a destination location where a piece of content resides physically (a local or remote server and port). You add services to content rules. Adding a service to a content rule includes it in the resource pool that the CSS uses for load balancing requests for content. A service may belong to multiple content rules. •An owner is generally the person or company who contracts the web hosting service to host their web content and allocate bandwidth as required. •A content rule is a hierarchical rule set containing individual rules that describe which content (for example, .html files) is accessible by visitors to the web site, how the content is mirrored, on which server the content resides, and how the CSS should process requests for the content. Each rule set must have an owner. Note For detailed information on creating and configuring services, owners, and content rules, refer to the Content Services Switch Basic Configuration Guide. When a request for content is made, the CSS: 1. Uses the owner content rule to translate the owner's Virtual IP address (VIP) or domain name using Network Address Translation (NAT) to the corresponding service IP address and port. 2. Checks for available services that match the content request. 3. Uses content rules to choose which service can best process the request for content. 4. Applies all content rules to service the request for content (for example, load balancing method, redirects, failover, stickiness). The CSS uses content rules to determine: •Where the content physically resides, whether local or remote •Where to direct the request for content (which service or services) •Which load balancing method to use The type of rule also implies the network layer at which the rule functions. •A Layer 3 content rule implies a destination IP address of the host or network. •A Layer 4 content rule implies a combination of destination IP address, protocol, and port. •A Layer 5 content rule implies a combination of destination IP address, protocol, port, and Universal Resource Locator (URL) that may or may not contain an HTTP cookie or a domain name. Note A Layer 5 rule supports the HTTP CONNECT, GET, HEAD, POST, PUSH, and PUT methods. Content rules are hierarchical. That is, if a request for content matches more than one rule, the characteristics of the most specific rule apply to the flow. The hierarchy for content rules is shown below. The CSS uses this order of precedence to process requests for the content, with 1 being the highest match and 8 being the lowest match. 1. Domain name, IP address, protocol, port, URL 2. IP address, protocol, port, URL 3. IP address, protocol, port 4. IP address, protocol 5. IP address 6. Domain name, protocol, port, URL 7. Protocol, port, URL 8. Protocol, port Using the Configuration Script The CSS initiates the configuration script automatically when you log in and it does not detect an existing startup-config file. Note If you want to configure the CSS manually, refer to the Content Services Switch Basic Configuration Guide. You need to enter the following information as the configuration script completes: •IP address and subnet mask for circuit VLAN1 (all interfaces are assigned to VLAN1 by default) •IP address for the default gateway •IP addresses for the servers •Virtual IP address (VIP) for the content rule The configuration script allows you to create services, owners, and content rules based on your entries and then enables you to: •Configure Layer 3 load balancing •Configure Layer 5 load balancing •Configure Proxy cache •Configure Transparent cache •Exit from the script and save the information you entered to the running-config To accept the script default values, press the Enter key at the prompts. To quit the script, enter "q" at any prompt. You may also initiate the configuration script manually by entering the script play setup command. To clear an existing running-config, use the clear running-config command from SuperUser mode. To clear an existing startup-config, use the clear startup-config command from SuperUser mode. The following pages show you the entire configuration script including: •Bold text to indicate where you enter information •Explanations to help you use the script ############################################## #Setup Script for the Content Services Switch# ############################################## Checking for Existing Config... No startup-config was found, continue with the setup script [y/n]? y Note: Pressing "q" after any prompt quits setup. Pressing <CR> after any [y/n] defaults to "y". Warning: All circuit VLAN IP addresses must be on a different subnet than the Ethernet Mgt port IP address. The existing Ethernet Mgt port IP address is: 10.0.4.251 Add an IP address to VLAN1: [default = 192.168.10.1] 192.168.3.6 Add an IP subnet mask to VLAN1: [default = 255.255.255.0] Warning: The default gateway IP address must be on the same subnet as VLAN1. VLAN1 IP address is: 192.168.3.6 Add IP address for default gateway: [default = 192.168.3.2] 192.168.3.3 Pinging the default gateway: 100% Success. Which feature do you want to configure? [1] Layer3 load balancing [2] Layer5 load balancing [3] Proxy cache [4] Transparent cache [5] Exit script If you select option 5 to exit the script, the CSS saves the information you entered to the running-config and then displays the running-config. Configuring Layer 3 Load Balancing A Layer 3 load balancing configuration enables the CSS to use a Virtual IP address (VIP) to load balance Web traffic to Web servers based on IP addresses. When you select Layer 3 load balancing, the script automatically: •Creates an owner (L3_Owner) •Creates a Layer 3 content rule (L3_Rule) and defines ArrowPoint Content Awareness (ACA) as the load balance method •Activates the services •Activates the content rule •Saves the running-config to the startup-config The script enables you to configure: •Service name (default name is Server1) •Service IP address •VIP for the content rule To configure Layer 3 load balancing, enter 1. Which feature do you want to configure? [1] Layer3 load balancing [2] Layer5 load balancing [3] Proxy cache [4] Transparent cache Enter the number for the feature you want to configure: 1 To accept the script default values, press the Enter key at the prompts. Creating Layer3 load balancing Enter service name: [default = Server1] Enter service IP address: [default = 192.168.10.3] 192.168.3.58 Create another service? [y/n]? y Enter service name: [default = Server2] Enter service IP address: [default = 192.168.10.3] 192.168.3.59 Create another service? [y/n]? n Enter Virtual IP address for L3_Rule: [default = 192.168.10.4] 192.168.3.6 After the configuration is completed, the script automatically: •Displays the running-config •Saves the running-config to the startup-config Showing the Running Config !Generated MAR 6 17:53:49 !************** GLOBAL ************* ip route 0.0.0.0 0.0.0.0 192.168.3.3 !************ CIRCUIT ************ circuit VLAN1 ip address 192.168.3.6 255.255.255.0 !************ SERVICE ************ service Server1 ip address 192.168.3.58 active service Server2 ip address 192.168.3.59 active !************ OWNER **************** owner L3_Owner content L3_Rule add service Server1 add service Server2 vip address 192.168.3.6 balance aca active ########################################## ## Setup Completed Successfully!!! ## ########################################## For detailed configuration information, refer to the Content Services Switch Basic Configuration Guide. Configuring Layer 5 Load Balancing A Layer 5 load balancing configuration enables the CSS to use a VIP address to load balance Web traffic to Web servers based on URLs. When you select Layer5 load balancing, the script automatically: •Creates an owner (L5_Owner) •Creates a Layer 3 content rule (L3_Rule) •Creates a Layer 5 content rule (L5_Rule) and defines: –Protocol tcp –Port 80 –URL "/" –Load balance method as ACA •Activates the services •Activates the content rule •Saves the running-config to the startup-config The script enables you to configure: •Service name (default name is Server1) •VIP for the content rule To configure Layer 5 load balancing, enter 2. Which feature do you want to configure? [1] Layer3 load balancing [2] Layer5 load balancing [3] Proxy cache [4] Transparent cache Enter the number for the feature you want to configure: 2 To accept the script default values, press the Enter key at the prompts. Creating Layer5 load balancing Enter service name: [default= Server1] Enter service IP address: [default = 192.168.10.3] 192.168.3.58* Create another service? [y/n]? n Enter Virtual IP address for L5_Rule: [default = 192.168.10.4] 192.168.3.8 After the configuration is completed, the script automatically: •Displays the running-config •Saves the running-config to the startup-config Showing the Running Config !Generated MAR 6 17:53:49 !************** GLOBAL ************* ip route 0.0.0.0 0.0.0.0 192.168.3.3 !************ CIRCUIT ************ circuit VLAN1 ip address 192.168.3.6 255.255.255.0 !************ SERVICE ************ service Server1 ip address 192.168.3.58 active !************ OWNER **************** owner L5_Owner content L3_Rule add service Server1 vip address 192.168.3.8 balance aca active content L5_Rule add service Server1 vip address 192.168.3.8 protocol tcp port 80 url "/" balance aca active ########################################## ## Setup Completed Successfully!!! ## ########################################## For detailed configuration information, refer to the Content Services Switch Basic Configuration Guide. Configuring Proxy Cache A proxy cache configuration enables the CSS to use a Virtual IP address (VIP) to load balance Web traffic to proxy cache servers based on domain name. When you select Proxy Cache, the script automatically: •Creates an owner (Proxy_Owner) •Creates a content rule (Proxy_Rule) and defines: –Service type as proxy-cache –Protocol tcp –Port 8080 –URL "/" –Load balance method as domain –Application type HTTP •Activates the services •Activates the content rule The script enables you to configure: •Service name (default name is Proxy_Cache1) •VIP for the content rule To configure a proxy cache configuration, enter 3. Which feature do you want to configure? [1] Layer3 load balancing [2] Layer5 load balancing [3] Proxy cache [4] Transparent cache Enter the number for the feature you want to configure: 3 To accept the script default values, press the Enter key at the prompts. Creating Proxy Cache Configuration Enter service name: [default=Proxy_Cache1] Enter service IP address: [default = 192.168.10.3] 192.168.3.60 Create another service? [y/n]? n Enter Virtual IP address for Proxy_Rule: [default = 192.168.10.4] 192.168.3.9 After the configuration is completed, the script automatically: •Displays the running-config •Saves the running-config to the startup-config Showing the Running Config !Generated MAR 6 17:53:49 !************** GLOBAL ************* ip route 0.0.0.0 0.0.0.0 192.168.3.3 !************ CIRCUIT ************ circuit VLAN1 ip address 192.168.3.6 255.255.255.0 !************ SERVICE ************ service Proxy_Cache1 ip address 192.168.3.60 type proxy-cache port 8080 protocol tcp active !************ OWNER **************** owner Proxy_Owner content Proxy_Rule add service Proxy_Cache1 vip address 192.168.3.9 port 8080 protocol tcp url "/" balance domain application http active ########################################## ## Setup Completed Successfully!!! ## ########################################## For detailed configuration information, refer to the Content Services Switch Basic Configuration Guide. Configuring Transparent Cache A transparent cache configuration enables the CSS to redirect cacheable HTTP traffic to transparent cache servers based on IP address and port (80). The CSS directs non-cacheable HTTP traffic to the origin servers. When you select Transparent Cache, the script automatically: •Creates an owner (Transparent_Owner) •Creates a content rule (Transparent_Rule) and defines: –Service type as transparent-cache –Protocol tcp –Port 80 –Extension Qualifier List (EQL) named Cacheable* that contains the file types displayed in the sample running-config file –URL "/" eql Cacheable –Load balance method as domain –Failover type as bypass –Application type HTTP •Activates the services •Activates the content rule The script enables you to: •Configure a service name (Transparent_Cache1) •Define whether to direct only cacheable content or all content to the cache servers To configure a transparent cache configuration, enter 4. Which feature do you want to configure? [1] Layer3 load balancing [2] Layer5 load balancing [3] Proxy cache [4] Transparent cache Enter the number for the feature you want to configure: 4 To accept the script default values, press the Enter key at the prompts. Creating Transparent Cache Configuration Enter service name: [default = Transparent_Cache1] Enter service IP address: [default = 0.0.0.0] 192.168.3.7* Create another service? [y/n]? n Transparent caching can be configured to direct only cacheable content to the cache server. Non-cacheable content is sent directly to the origin server. The alternative is to direct all traffic to the cache server regardless of whether the content is cacheable. Should only cacheable content be directed to the cache server? [y/n]? Enter: •y to define URL "/" as eql-cacheable in the content rule and allow the CSS to direct only cacheable content to the cache servers •n to define URL "/" in the content rule and allow the CSS to direct all content to the cache servers After the configuration is completed, the script automatically: •Displays the running-config •Saves the running-config to the startup-config Showing the Running Config !Generated MAR 6 17:53:49 !************** GLOBAL ************* ip route 0.0.0.0 0.0.0.0 192.168.3.3 !************ CIRCUIT ************ circuit VLAN1 ip address 192.168.3.6 255.255.255.0 !************ SERVICE ************ service Transparent_Cache1 ip address 192.168.3.7 type transparent-cache port 80 protocol tcp active !************** EQL ************** eql Cacheable description "This EQL contains extensions of cacheable content" extension pdf "Acrobat" extension fdf "Acrobat Forms Document" extension au "Sound audio/basic" extension bmp "Bitmap Image" extension z "Compressed data application/x-compress" extension gif "GIF Image image/gif" extension html "Hypertext Markup Language text/html" extension htm extension js "Java script application/x-javascript" extension mocha extension jpeg "JPEG image image/jpeg" extension jpg extension jpe extension jfif extension pjpeg extension pjp extension mp2 "MPEG Audio audio/x-mpeg" extension mpa extension abs extension mpeg "MPEG Video video/mpeg" extension mpg extension mpe extension mpv extension vbs extension m1v extension pcx "PCX Image" extension txt "Plain text text/plain" extension text extension mov "QuickTime video/quicktime" extension tiff "TIFF Image image/tiff" extension tar "Unix Tape Archive application/x-tar" extension avi "Video for Windows video/x-msvideo" extension wav "Wave File audio/x-wav" extension gz "application/x-gzip" extension zip "ZIP file application/x-zip-compressed" !************* OWNER *************** owner Transparent_Owner content Transparent_Rule add service Transparent_Cache1 port 80 protocol tcp url "/" eql Cacheable or url "/" balance domain failover bypass application http active ########################################## ## Setup Completed Successfully!!! ## ########################################## For detailed configuration information, refer to the Content Services Switch Basic Configuration Guide. Where to Go Next Refer to the Content Services Switch Basic Configuration Guide and the Content Services Switch Advanced Configuration Guide for detailed information on configuring the CSS.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.