Cisco LocalDirector 400 Series

Introduction

This document explains how to configure a Hypertext Transfer Protocol (HTTP) probe on the Cisco LocalDirector. LocalDirector validates the HTTP services on the respective server farms.

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:

• LocalDirector 416 in a lab environment with cleared configurations

• LocalDirector Software Release 4.2.1

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.

Network Diagram

This document uses this network setup:

Conventions

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

How to Configure an HTTP Probe on LocalDirector

Use these steps to configure the LocalDirector:

1. Configure a Virtual IP (VIP) address:

   virtual 172.18.124.208:80:0:tcp is
   
   

2. Configure a real server IP address:

   real 172.18.124.193:80:0:tcp is
   real 172.18.124.206:80:0:tcp is
   real 172.18.124.207:80:0:tcp is
   

3. Bind the VIPs to the real server IP addresses using the bind command:

   bind 172.18.124.208:80:0:tcp 172.18.124.193:80:0:tcp
   bind 172.18.124.208:80:0:tcp 172.18.124.206:80:0:tcp
   bind 172.18.124.208:80:0:tcp 172.18.124.207:80:0:tcp
   

4. Configure a probe to a VIP or a real server IP address with a 10 second interval:

   probe virtual 172.18.124.208:80:0:tcp http 3
   probe real 172.18.124.193:80:0:tcp http 3
   
   

5. Configure the HTTP probe for non-default settings:

   probehttp real 172.18.124.193:80:0:tcp
   probehttp virtual 172.18.124.208:80:0:tcp file /index.htm
   
   

6. Configure the probe configuration to display the threshold for HTTP:

   probeconfig http 3
   
   

Verify

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

Certain show commands are supported by the Output Interpreter Tool, (registered customers only) which allows you to view an analysis of show command output.

• show version—Displays the software version that runs on the LocalDirector.

• show running-config—Displays the configuration that runs on the LocalDirector.

• show probehttp—Displays the non-default output of the command.

• show probe—Displays the probes and their probing intervals.

• show real—Displays a list of the real servers, their states, number of connections, and load-balancing algorithms.

• show probeconfig—Displays the status of the probe configuration (if enabled) and the respective threshold.

• show virtual—Displays a list of virtual servers, their states, number of connections, and load-balancing algorithms.

show version Command

LDIR-416# show version
LocalDirector 416 Version 4.2.1

show running-config Command

LDIR-416# show running-config
: Saved
: LocalDirector 416 Version 4.2.1
syslog output 23.7
no syslog console
enable password dfeaf10390e560aea745ccba53e044 encrypted
hostname LDIR-416
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  0
no secure  1
no secure  2
ping-allow 0
ping-allow 1
ping-allow 2
ip address 172.18.124.210 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
telnet 64.0.0.0 255.0.0.0
snmp-server enable traps
snmp-server community public
no snmp-server contact
no snmp-server location

!--- This is the VIP configuration.

virtual 172.18.124.208:80:0:tcp is
virtual 172.18.124.208:0:0:tcp is

!--- This is the real server configuration.

real 172.18.124.193:80:0:tcp is
real 172.18.124.206:80:0:tcp is
real 172.18.124.207:80:0:tcp is

!--- Bind the VIP configuration to the Real configuration.

bind 172.18.124.208:80:0:tcp 172.18.124.193:80:0:tcp
bind 172.18.124.208:80:0:tcp 172.18.124.206:80:0:tcp
bind 172.18.124.208:80:0:tcp 172.18.124.207:80:0:tcp

!--- Probe to a VIP configuration.

probe virtual 172.18.124.208:80:0:tcp http 3

!--- Probe to a real server configuration.

probe real 172.18.124.193:80:0:tcp http 3

!--- The HTTP probe is configured for non-default settings.

probehttp virtual 172.18.124.208:80:0:tcp file /index.htm
probehttp real 172.18.124.193:80:0:tcp

!--- Probe configuration to display the threshold for HTTP.

probeconfig http 3
LDIR-416#

show probehttp Command

LDIR-416# show probehttp
                                                                Return
                  Machine                       Port  Request   Code   Filename
            172.18.124.193:80:0:tcp (real)       80    HEAD     200      /
            172.18.124.208:80:0:tcp (virtual)    80    HEAD     200      /index.htm

show probe Command

LDIR-416# show probe
          Probes for Reals ----
                  Machine                     Type     Interval
            172.18.124.193:80:0:tcp           http        3


          Probes for Virtuals ----
                  Machine                     Type     Interval
            172.18.124.208:80:0:tcp           http        3

show real Command

LDIR-416# show real
          Real Machines:

                                                             No Answer TCP Reset DataIn
                            Machine  Connect   State  Thresh Reassigns Reassigns  Conns
            172.18.124.193:80:0:tcp       0      IS       8         0         0      0
            172.18.124.206:80:0:tcp       0      IS       8         0         0      0
            172.18.124.207:80:0:tcp       0      IS       8         0         0      0

show probeconfig Command

LDIR-416# show probeconfig
Type    Threshold
dns    disabled
http   3

Troubleshoot

This section provides information you can use to troubleshoot your configuration.

Troubleshooting Commands

Certain show commands are supported by the Output Interpreter Tool (registered customers only) , which allows you to view an analysis of show command output.

Note: Before you use debug commands, refer to Important Information on Debug Commands.

• syslog output 20.7—Displays the status of any configuration updates and logging information at the debugging level.

• syslog console—Displays the status of any configuration updates and logging information at the debugging level.

LDIR-416# <187> May 23 15:03:45 LD-ERR Real machine '172.18.124.193:80:0:tcp': 
edited from Failed (External) to Testing - HTTP probes.
LDIR-416# <187> May 23 15:04:15 LD-ERR Real machine '172.18.124.193:80:0:tcp': 
edited from Testing to In Service - HTTP probes.
LDIR-416# <187> May 23 14:59:55 LD-ERR Real machine '172.18.124.193:80:0:tcp': 
edited from In service to Failed (External) -- Probe.
LDIR-416# <187> May 23 14:52:45 LD-ERR Real machine '172.18.124.193:80:0:tcp': 
edited from In service to Failed (External) -- Probe.

Note: You can also issue the show real command to troubleshoot the configuration.

Related Information

• LocalDirector 400 Series End-of-Life and End-of-Sale Notices
• LocalDirector 400 Series Product Bulletins
• Configuring Cisco LocalDirector 4.2.1
• Cisco LocalDirector
• Technical Support - Cisco Systems