LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: LVS-DR

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: LVS-DR
From: "Alexander Meis" <am@xxxxxxxxxxxxx>
Date: Fri, 12 Dec 2003 17:54:12 +0100
Hi Joseph,

> o  This may not help you a whole lot if you
> don't have the right features built into the kernel
> Do you have all the right stuff turned on in the Networking Options?
> You'll need at least Network packet filtering and IP: policy routing
> (I turn just about everything on here)

ok, now i rebuild the kernel with the packet filtering an policy routing and
there are no errors when i start the rc.lvs_dr on the realserver
the output follows at the end of the mail

on the director i got
IP Virtual Server version 1.0.10 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  192.168.0.110:www rr
  -> 192.168.0.63:www             Route   1      0          0

but
if i do on the .61 oder .10 (my terminal)
wget 192.168.0.110/index.html
Connecting to 192.168.0.110:80... failed: Connection refused.
wget 192.168.0.61/index.html
Connecting to 192.168.0.61:80... failed: Connection refused.

if i do
wget 192.168.0.63/index.html
it works.

are there some sysctl settings i have to make? or where else can the problem
be ?
the Apache ist just Listen 80

Thanks

Alex


*********************

number nics on director 1
LVS realserver type vs-dr
installing default gw 192.168.0.1 for vs-dr
number of default gw 0, first gw
setting default gw to 192.168.0.1
showing routing table

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.0.110   0.0.0.0         255.255.255.255 UH        0 0          0 lo
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
eth0
0.0.0.0         192.168.0.1     0.0.0.0         UG        0 0          0
eth0

checking if DEFAULT_GW 192.168.0.1 is reachable - PING 192.168.0.1
(192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.647 ms

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.647/0.647/0.647/0.000 ms
good
set_realserver_ip_forwarding to OFF (1 on, 0 off).
proc/sys/net/ipv4/ip_forward 0

searching for ipchains
ipchains not loaded, good
loading ip_tables module
find_kernel_function_name_2_4
find_kernel_name_2_4: parameter ip_tables
check_function_in_kernel
function ipt_tables in kernel.
won't look for module.
setting default policy to ACCEPT for LVS devices
clearing iptables/ipchain rules
showing iptables nat rules
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
showing iptables rules
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
correct VIP entry in /etc/iproute2/rt_tables: 200 VIP
deleting ip rule from 192.168.0.110
correct RIP entry in /etc/iproute2/rt_tables: 201 RIP
deleting ip rule from 192.168.0.63 to 192.168.0.0/24
deleting ip rule from 192.168.0.63
ip rules (RIP and VIP tables should be empty)
0:      from all lookup local
32766:  from all lookup main
32767:  from all lookup 253
route table name<->id translation table:
200 VIP
201 RIP

clearing priority routing table
deleting table VIP
ip route flush table VIP
routing table VIP should be empty:
deleting table RIP
ip route flush table RIP
routing table RIP should be empty:
device lo:110 has VIP 192.168.0.110
new VIP device == old VIP device, don't reinstall
DEBUG: device lo:110 has VIP 192.168.0.110 and is UP
DEBUG: removing 192.168.0.110 from lo:110


looking for DIP 192.168.0.61
PING 192.168.0.61 (192.168.0.61) 56(84) bytes of data.
64 bytes from 192.168.0.61: icmp_seq=1 ttl=64 time=0.265 ms

--- 192.168.0.61 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms
found, good
not local, good

looking for VIP on director from realserver

looking for VIP on director from realserver
director is accepting packets on VIP 192.168.0.110, device eth0:110
No VIP on real-server, VIP will be on director.

pinging VIP 192.168.0.110 from RIP
server gw not on director
OK is vs-dr
VIP is in the same network as the RIP
VIP 192.168.0.110 should be pingable
PING 192.168.0.110 (192.168.0.110) 56(84) bytes of data.
64 bytes from 192.168.0.110: icmp_seq=1 ttl=64 time=0.303 ms

--- 192.168.0.110 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.303/0.303/0.303/0.000 ms
good.
LVS_TYPE = vs-dr, VIP device installed
lo is not a tunl device, OK
lo:110 is local, up'ing lo.
install_realserver_vip: configuring Linux 2.4.23
ifconfig output
lo:110    Link encap:Local Loopback
          inet addr:192.168.0.110  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

installing route for VIP 192.168.0.110 on device lo:110
listing routing info for VIP 192.168.0.110
192.168.0.110   0.0.0.0         255.255.255.255 UH        0 0          0 lo
hiding interface lo:110, will not arp

Installing priority routing
lvs type vs-dr, SERVER_GW 192.168.0.1
priority rules
0:      from all lookup local
32766:  from all lookup main
32767:  from all lookup 253
routes VIP
routes RIP
adding rules to RIP with priority 100 from 192.168.0.63 to 192.168.0.0/24
adding routing rules to RIP with priority 100 from 192.168.0.63 to 0/0
showing ip rules for priority 100
100:    from 192.168.0.63 to 192.168.0.0/24 lookup RIP
100:    from 192.168.0.63 lookup RIP
set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table RIP (should be empty):
no gateway - is link route: ip route add table RIP to 192.168.0.0/24 dev
eth0 from 192.168.0.63
route add: return_code 0
ip route for table RIP
192.168.0.0/24 dev eth0  scope link  src 192.168.0.63
set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table RIP (should be empty):
192.168.0.0/24 dev eth0  scope link  src 192.168.0.63
adding route to gateway 192.168.0.61 in table RIP
ip route add table RIP to 0/0 via 192.168.0.61 dev eth0 from 192.168.0.63
route add: return_code 0
ip route for table RIP
192.168.0.0/24 dev eth0  scope link  src 192.168.0.63
default via 192.168.0.61 dev eth0
adding VIP routing rules with priority 99 to realserver.
showing ip rules for prio 99
99:     from 192.168.0.110 lookup VIP
set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table VIP (should be empty):
adding route to gateway 192.168.0.1 in table VIP
ip route add table VIP to 0/0 via 192.168.0.1 dev eth0 from 192.168.0.110
route add: return_code 0
ip route for table VIP
default via 192.168.0.1 dev eth0
removing default gw
showing priority routing
0:      from all lookup local
99:     from 192.168.0.110 lookup VIP
100:    from 192.168.0.63 to 192.168.0.0/24 lookup RIP
100:    from 192.168.0.63 lookup RIP
32766:  from all lookup main
32767:  from all lookup 253
192.168.0.110 dev lo  scope link  src 192.168.0.110
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.63
routing for table VIP
default via 192.168.0.1 dev eth0
routing for table RIP
192.168.0.0/24 dev eth0  scope link  src 192.168.0.63
default via 192.168.0.61 dev eth0
BSD like ps
killing extra ntpd process 1173.
killing ntpd process 1172.
ntpd restarted
not adding filter rules.
The location of the output file rc.lvs is the default = ./
You can change this (and other output files) by editing the variables
$rc_lvs_home, $rc_mon_home, $rc_ntp_home



<Prev in Thread] Current Thread [Next in Thread>