This document provides a sample configuration for configuring HTTP redirect on the Content Switching Module (CSM). Redirects can be used to send a client to a remote site when, for example, the main site is down for maintenance or any other reason.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
CSM version 3.x
Native IOS 12.1E
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.
This configuration can also be used with these hardware and software versions:
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
In this section, you are presented with the information to configure the features described in this document. This configuration allows the CSM of site A to redirect the client to site B when the server at site A is down.
Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) .
This document uses this network setup:
This document uses this configuration:
vlan 499 client
ip address 192.168.10.97 255.255.254.0
vlan 500 server
ip address 192.168.20.97 255.255.254.0
route 192.168.50.0 255.255.255.0 gateway 192.168.20.1
probe WEB_PING icmp
!--- This probe is used to track the availability of local servers.
!--- The ping interval has been reduced to two seconds to quickly detect a server down.
!--- This is the local serverfarm.
no nat client
!--- You may have many Web servers here; only one is used for this example.
!--- Specified the probe to be used as WEB_PING to detect when servers !--- are going down.
!--- This is the redirect configuration.
!--- NATing does not matter here because traffic is redirected.
no nat client
!--- Issue the redirect-vserver name !--- command to enter the relocation mode. !--- This replaces the configuration of the real servers.
webhost relocation 10.10.10.123/%p
!--- In this example, the traffic is redirected to IP address 10.10.10.123.
!--- The IP address is the remote site virtual IP address.
!--- You can also specify a DNS name, such as www.cisco.com. !--- The %p at the end tells the CSM to copy the directory path and the file from !--- the initial HTTP request of the client.
virtual 192.168.11.246 tcp www
serverfarm WEBFARM backup WEB_REDIRECT
!--- The redirect serverfarm is specified as a backup of the local Web farm. !--- When all servers are down in the local farm, traffic is redirected to the !--- remote site.
This section provides information you can use to confirm your configuration is working properly.
You can also verify if the configuration working properly by capturing a sniffer trace and verifying what the CSM returns to an HTTP request to the Web Vserver. It is also possible to determine if this is working by viewing the URL that displays on the browser after the connection has been completed.
There is currently no specific troubleshooting information available for this configuration.