
Configuring Server Connections
c. On the Web Site tab, next to IP address, select the Advanced button.
d. Select the Add... button under the top list box.
e. Enter the IP address and the TCP port for the Layer 4 cluster, as configured on Equalizer.
Click OK.
f. Click OK twice to return to the Internet Information Service (IIS) Manager.
You should now be able to send client requests to the cluster IP and port, and get responses directly from the IIS
HTTP server running on Windows 2003. Remember that static routes on your servers may be necessary,
depending on your network configuration.
Adjusting ARP Behavior on Linux Servers
Some operating systems, such as Linux, will reply to ARP requests for the cluster IP address configured on the
loopback interface. On such systems, the ARP behavior needs to be adjusted so the system only replies to ARP
requests for IP addresses on non-loopback interfaces. The method used to do this varies between operating
systems. For example, to do this on a Linux box, you would adjust specific kernel parameter values as shown
below, by editing the file /etc/sysctl:
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.default.arp_ignore = 1
net.ipv4.conf.default.arp_announce = 2
net.ipv4.conf.eth0.arp_ignore = 1
net.ipv4.conf.eth0.arp_announce = 2
Configuring a Linux System running Apache for DSR
This is an example of how to configure a typical Linux system running Apache 2.0 for DSR:
1. Log into the Linux server as
root
, and enter the following command to configure a loopback interface:
# ifconfig lo:dsr inet cluster-ip netmask 255.255.255.255
Substitute the IP address of the DSR-enabled cluster on Equalizer for cluster-ip in the
command above. Note that in most Linux distributions, you are configuring an alias for the
loopback interface and should specify a netmask of 255.255.255.255 instead of the netmask
used to configure the cluster on Equalizer.
2. Enter the following command to verify that the loopback alias was created:
# ifconfig lo:dsr
366
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Kommentare zu diesen Handbüchern