|
My apologies, it looks like I may have mixed up my idea of VIP's and DIP's.
I've read a lot of the documentation but obviously I have more work to do to
fully understand the setup! As it stands though, I need to diagnose this
problem as part of my job before I can delve deeper into LVS. This setup was
implemented by a contractor some year or so ago, and I've inherited it in its
working state.
Can I please stress that this exact setup works perfectly for the other 10+
clusters set up through this shared load-balancer. The latest cluster set up
does not, however, which is a problem relating to the realservers as explained
in my previous post.
The director is set up somewhat as per the example below (IP addresses removed):
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DB
inet addr:xxx Bcast:xxx Mask:255.255.255.224 <--- IP address of
the load balancer, the one referred to in my example as 1.1.1.1
inet6 addr: fe80::21e:c9ff:febb:32db/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:200798159 errors:0 dropped:48253 overruns:0 frame:0
TX packets:100169922 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:89479150493 (83.3 GiB) TX bytes:17754079422 (16.5 GiB)
Interrupt:169
eth1 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DC
inet6 addr: fe80::21e:c9ff:febb:32dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6872502326 errors:0 dropped:13687083 overruns:0 frame:0
TX packets:4058424468 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1525781469939 (1.3 TiB) TX bytes:1034634399732 (963.5 GiB)
Interrupt:177
eth1.300 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DC
inet6 addr: fe80::21e:c9ff:febb:32dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3674907 errors:0 dropped:0 overruns:0 frame:0
TX packets:13892 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:208084782 (198.4 MiB) TX bytes:583680 (570.0 KiB)
eth1.309 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DC
inet addr:xxx Bcast:0.0.0.0 Mask:255.255.255.248 <--- IP on VLAN
309, added to nodes on this VLAN as loopback
inet6 addr: fe80::21e:c9ff:febb:32dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4754011 errors:0 dropped:0 overruns:0 frame:0
TX packets:4704199 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:677281903 (645.9 MiB) TX bytes:722819063 (689.3 MiB)
eth1.345 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DC
inet addr:xxx Bcast:0.0.0.0 Mask:255.255.255.240 <--- IP on VLAN
345, added to nodes on this VLAN as loopback
inet6 addr: fe80::21e:c9ff:febb:32dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6270400 errors:0 dropped:0 overruns:0 frame:0
TX packets:2918760 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:483982873 (461.5 MiB) TX bytes:213878377 (203.9 MiB)
eth1.519 Link encap:Ethernet HWaddr 00:1E:C9:BB:32:DC
inet addr:xxx Bcast:0.0.0.0 Mask:255.255.255.240 <--- IP on VLAN
345, added to nodes on this VLAN as loopback
inet6 addr: fe80::21e:c9ff:febb:32dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:152931322 errors:0 dropped:0 overruns:0 frame:0
TX packets:162320246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15941864252 (14.8 GiB) TX bytes:18649921966 (17.3 GiB)
<snip>
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:928940 errors:0 dropped:0 overruns:0 frame:0
TX packets:928940 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:82290543 (78.4 MiB) TX bytes:82290543 (78.4 MiB)
I'll put some output in from ipvsadm -L -n as well, to show how all of the
above ties together:
# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP xx.xx.143.77:80 wrr persistent 600
-> xx.xx.143.69:80 Route 1 6 1
-> xx.xx.143.68:80 Route 1 10 14
TCP xx.xx.13.125:80 wrr persistent 600
-> xx.xx.13.113:80 Route 1 0 0
-> xx.xx.13.124:80 Route 1 0 0
TCP xx.xx.63.141:443 wrr persistent 600
-> xx.xx.63.129:443 Route 1 0 0
-> xx.xx.63.130:443 Route 1 0 2
TCP xx.xx.0.133:443 wrr persistent 600
-> xx.xx.0.130:443 Route 1 1 4
-> xx.xx.0.131:443 Route 1 0 0
Hopefully you have a slightly better idea of how our setup looks from that
information. :) As I've said, the problem appears to be with the loopback
interfaces on the nodes, and hope that someone on this list has seen a similar
issue to this in the past and knows how to remedy it. I'm confident that if I
switched the realservers to Windows they'd work perfectly fine with the current
LVS setup. As it stands though, I've got to get it working with Debian.
Does anyone have any up-to-date Lenny realservers currently operating without
issue?
Kind regards,
Chris
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx on behalf of Joseph Mack NA3T
Sent: Tue 01/12/2009 22:00
To: LinuxVirtualServer.org users mailing list.
Subject: Re: [lvs-users] Loopback issue on Debian Lenny realserver
On Tue, 1 Dec 2009, Chris Merrett wrote:
>
> clients
> |
> router (Router for 1.2.3.0/24 is 1.2.3.254)
> |
> __________ |
> | | | VIP 1.2.3.4
> | director |--- DIP 1.1.1.1
> |__________| |
> |
> |
> ------------------------------------
> | | |
> | | |
> RIP1 1.2.3.1 RIP2 1.2.3.2 RIP3 1.2.3.3
> VIP 1.2.3.4 VIP 1.2.3.4 VIP 1.2.3.4
the RIPs should be on the same network at the DIP, which
should be on a private IP.
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
<<winmail.dat>> _______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
