|
hariharan wrote:
>
> hi,
> i read ur query on MARC .
> i hope im not troubling with this query .
>
> we have been trying out the procedurs given at
> www.linuxvirtualserver.org/ step by step .
>
> we have tried out with all the kernel versions . til the recent 2.2.17 .
>
> we have 2 interface on the director
> eth0 - ( IP 192.168.1.208 )
> eth1 - ( IP 172.16.1.1 )
> this is the gateway for all the 172.16.1.* series machines
>
> procedure followed :
>
> 1 . there is a patch available for ipvsadm .
> we apply the patch as cat <kernel-patch>.patch | patch -p1
>
> 2. we compile the kernel with all the IP options enabled .
> should we enable all or selected as modues or into kernel ?
>
> 3 . next we restart into new kernel .
>
> 4 . output of ifconfig
>
> eth0 Link encap:Ethernet HWaddr 00:80:C8:05:0A:F0
> inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:6428 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1819 errors:0 dropped:0 overruns:0 carrier:0
> collisions:61 txqueuelen:100
> Interrupt:9 Base address:0xe800
>
> eth1 Link encap:Ethernet HWaddr 00:10:B5:62:55:AD
> inet addr:172.16.1.1 Bcast:172.16.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:461 errors:0 dropped:0 overruns:0 frame:0
> TX packets:675 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:10 Base address:0xe400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
>
> 5 . out put of route
>
> [root@Director /root]# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.208 0.0.0.0 255.255.255.255 UH 0 0 0
> eth0
> 172.16.1.1 0.0.0.0 255.255.255.255 UH 0 0 0
> eth1
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 172.16.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.1.2 0.0.0.0 UG 0 0 0
> eth0
>
> 6. output of ipchains
>
> [root@Director /root]# ipchains -L
> Chain input (policy ACCEPT):
> Chain forward (policy ACCEPT):
> target prot opt source destination ports
> MASQ all ------ 172.16.1.0/24 anywhere n/a
> MASQ all ------ 172.16.1.3 anywhere n/a
> MASQ all ------ 172.16.1.4 anywhere n/a
> Chain output (policy ACCEPT):
>
> 7 . content of balance.sh ( shell script to enable loadbalancing module )
>
> #!/bin/bash
> #/sbin/ipvsadm -A -t 192.168.1.208:80 -s wlc
> /sbin/ipvsadm -A -t 192.168.1.208:23 -s rr
>
> /sbin/ipvsadm -a -t 192.168.1.208:23 -r 172.16.1.3 -m -w 1
> /sbin/ipvsadm -a -t 192.168.1.208:23 -r 172.16.1.4 -m -w 2
>
> after all this . telnet load balancing is enabled on the director .
>
> this means when I telnet to 192.168.1.208 it should load balance between
> 172.168.1.3 and 172.168.1.4 .
> but im not able to telnet at all .
> If u find any thing wong in my procedure . please let me know . im stuck up
> here . I am online all the time checking my mail .
>
> Please point out the mistakes I am making . if possible mail me any
> documented material u have on this subject .
>
> Thanking u in advance.
what is the default route for the real-servers - it should be the director?
Please read the HOWTO on setting up VS-NAT
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
