WebSphere® Load Balancer setup
To setup a single Apache server to work with Load Balancer, your ifconfig
file
must be modified.
eth0 Link encap:Ethernet HWaddr 00:09:6B:1A:C2:11
inet addr:10.10.80.80 Bcast:10.10.80.255 Mask:255.255.255.0
inet6 addr: fe80::9:6b00:341a:c211/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:26873 errors:0 dropped:0 overruns:0 frame:0
TX packets:38275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3024755 (2.8 Mb) TX bytes:43256184 (41.2 Mb)
eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:03
inet addr:192.168.30.80 Bcast:192.168.30.255 Mask:255.255.255.0
inet6 addr: fe80::200:0:900:3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:32802244 errors:0 dropped:0 overruns:0 frame:0
TX packets:32799805 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3028590615 (2888.2 Mb) TX bytes:4077951685 (3889.0 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2442 errors:0 dropped:0 overruns:0 frame:0
TX packets:2442 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:218635 (213.5 Kb) TX bytes:218635 (213.5 Kb)
The
/etc/hosts
file needs to be as follows: #
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.30.82 www.ptest.com
10.10.80.82 www.ptest2.com
192.168.30.100 webserver1.vlan1.com webserver1
192.168.30.80 lbserver.pdl.pok.ibm.com lbserver
lbserver:~ #
A start script and a stop script are needed for Load Balancer. Both scripts
are run from the root. The start script we used was
load_balancer_start.sh
and
looked like: #!/bin/bash
dsserver start
sleep 5
dscontrol executor start
dscontrol cluster add www.ptest.com
dscontrol port add www.ptest.com@80
dscontrol port add www.ptest.com@443
dscontrol server add www.ptest.com@80@webserver1.vlan1.com
dscontrol server add www.ptest.com@443@webserver1.vlan1.com
dscontrol executor configure www.ptest.com
dscontrol manager start
dscontrol advisor start http 80
dscontrol server report www.ptest.com@80@webserver1.vlan1.com
dscontrol server status www.ptest.com@80@webserver1.vlan1.com
ifconfig eth1:0 192.168.30.82 netmask 255.255.255.0 up
#ifconfig
exit
The stop script we used was
load_balancer_stop.sh
and
looked like: #!/bin/bash
#
dscontrol manager stop
dscontrol executor stop
dsserver stop