Cisco LocalDirector 400 Series

Introduction

This document describes a basic HTTP redirection without specifying Direct IP (DIP) addresses or real IP addresses. The configuration takes a call on the Virtual IP (VIP) address and redirects it to a URL address that has been configured without an availability check. This redirection technique is not limited to sites that have a real or DIP address.

Before You Begin

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites

There are no specific prerequisites for this document.

Components Used

The information in this document is based on the software and hardware versions below.

• Cisco LocalDirector 416 Switch

• Cisco LocalDirector Software Release 4.2.1

• Netscape 4.7

• Microsoft Internet Explorer 5.5

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.

Configure

In this section, you are presented with the information to configure the features described in this document.

Note: To find additional information on the commands used in this document, use the Cisco LocalDirector Command Reference.

Network Diagram

This document uses the network setup shown in the diagram below.

Configurations

The bold text indicates the required configuration for LocalDirector "HTTP redirection on a stick," or "one-armed HTTP redirection."

36-37-ld430-p-s# show conf
: Saved
: LocalDirector 416 Version 4.2.1
syslog output 20.7
no syslog console
enable password dfeaf10390e560aea745ccba53e044 encrypted0pt;
hostname 36-37-ld430-p-s
no shutdown ethernet 0
no shutdown ethernet 1
shutdown ethernet 2
interface ethernet 0 auto
interface ethernet 1 auto
interface ethernet 2 auto
mtu 0 1500
mtu 1 1500
mtu 2 1500
multiring all
no secure
no secure
no secure
ping-allow  
ping-allow  1
ping-allow  2
p address 172.18.124.215 255.255.255.0
route 0.0.0.0 0.0.0.0 172.18.124.1 1
arp timeout 30
no rip passive
rip version 1   
failover ip address 0.0.0.0
no failover
failover hellotime 30
password dfeaf10390e560aea745ccba53e044ed encrypted
telnet 172.18.124.0 255.255.255.0
snmp-server enable traps
snmp-server community public
no snmp-server contact 
no snmp-server location
virtual 172.18.124.216:80:0:tcp is
url test2 http://www.cisco.com 302
bind 172.18.124.216:80:0:tcp test2
36-37-ld430-p-s#

Verify

This section provides information that you can use to confirm your configuration is working properly.

Commands and Sample Output

show statistics

The show statistics command shows statuses for machines.

In this example, the http address http://172.18.124.216 was redirected to http://www.cisco.com with IE 5.5.

36-37-ld430-p-s# show statistics

Real Machine(s)           Bytes     Packets     Connections

Virtual Machine(s)        Bytes     Packets     Connections
172.18.124.216:80:0:tcp   1804        14             1

36-37-ld430-p-s# show statistics

Real Machine(s)           Bytes     Packets     Connections

Virtual Machine(s)        Bytes     Packets     Connections
172.18.124.216:80:0:tcp   1804         14            1

In this example, the http address 172.18.124.216 with Netscape Communicator 4.7 on the same client was redirected to http://www.cisco.com.

36-37-ld430-p-s# show statistics

Real Machine(s)           Bytes     Packets     Connections

Virtual Machine(s)        Bytes     Packets     Connections
172.18.124.216:80:0:tcp   3266         26            2

bind

To associate a virtual server with one or more real servers, issue the bind command. Issue the no bind command to release an association between a real server and virtual server.

bind virtual_id real_id [real_id...]


no bind virtual_id real_id [real_id...]

url

To define a URL and create a short identifier to replace a long URL string, issue the url command.

url url_id url_short_identifier [http-code]


no url url_id url_short_identifier [http-code]

virtual

To create a virtual server to accept connections from the network, or to specify a content rule to be associated with this virtual server, issue the virtual command. Issue the no virtual command to remove the virtual server from Cisco LocalDirector.

virtual virtual_ip | virtual_name [:[virtual_port]:
         [bind-id]:[protocol]:[rule_name]] [service-state] 

no virtual virtual_ip | virtual_name [:[virtual_port]:
         [bind-id]:[protocol]:[rule_name]] [service-state]

Troubleshoot

The following commands can be used to troubleshoot:

• show virtual—This command indicates the service state of virtual servers in addition to other information.

• show bind—This command is to confirm binding of URLs to each real server.

Related Information

• HTTP Redirection Overview
• Cisco LocalDirector Documentation
• Content Network Delivery Products
• Technical Support - Cisco LocalDirector 400 Series Content Switches ( registered customers only)