Document ID: 12645
Updated: Jan 30, 2006
Contents
Introduction
You can configure a redirect service to redirect client requests that match one Virtual IP Address (VIP) to another VIP, in the event that all of the services for the rule are down.
If you configure a service as type redirect, you can specify a domain string that you would like the Content Services Switch (CSS) to use when it sends the redirect to the client. You can append the remainder of the request to the new domain. You typically use this feature if you front-end your web farm with web-caches, and want clients to be redirected to the VIP that contains the origin servers in the event that all of the caches fail.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on these software and hardware versions:
-
CSS 11503
-
WebNS Version 7.50
Note: You can use this configuration on all versions of CSS 11000 and 11500 from WebNS 4.0 to date, unless specified in the release notes.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
HTTP Redirect using the Domain Command
Enter this information in the Services section for the redirect service:
!************************** SERVICE ************************** service Redirect type redirect ip address 1.1.1.1 domain 10.10.10.20 keepalive type none active service CacheEngine1 ip address 192.168.2.10 activeservice CacheEngine2 ip address 192.168.2.20 activeservice Webserver ip address 192.168.2.30 active
Note: You also need to configure a dummy non-existent IP address (for example, 1.1.1.1) and set the keepalive type to none in order to bring the Redirect service up.
Enter this information in the Owner section for the content rules:
!*************************** OWNER *************************** owner Content content Redirect protocol tcp add service Redirect !--- The Redirect service does not get used unless all !--- other services go down. port 80 url "/*" vip address 10.10.10.10 add service CacheEngine1 add service CacheEngine2 active content WebServer vip address 10.10.10.20 add service Webserver active
Note: You cannot use Redirect services with a Layer 4 rule (IP and port only ). You need to configure the url "/*" statement for the CSS to issue the redirect correctly.
Related Information
Open a Support Case
(Requires a Cisco Service Contract.)
Related Cisco Support Community Discussions
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.
