|
> I am running linux-2.4.21 with ipsv-1.0.9 patches on the lvs server.
> real server 1 is a Soalaris 7 system. I have a test service
> running on real server 1, port 5000. (To verify do "telnet
> peter.cs.andrews.edu
> 5000".)
Your lVS-director sounds fine.
> lvs server is configured with:
> ipvsadm -L
> IP Virtual Server version 1.0.9 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP lvs.cc.andrews.edu:5000 rr
> -> peter.cs.andrews.edu:5000 Route 1 0 0
Ok, this sounds fine assuming your DNS is ok.
> When I telnet to lvs:5000 InActConn goes to 1. A sniff on
> peter showes no traffic coming to it on port 5000.
> /proc/sys/net/ipv4/ip_forward is set to one even though there
> is only one interface.
> I have patched, compiled and installed the 2.4.21 kernel and
> rebooted with it. I have run ipvsadmin to generate the above
> tables on the lvs machine. What else should I do to make this work?
Did you read my last email? Did you read the LVS-DR documentation? I
haven't seen you do anything to:
1 - Listen on the VIP (virtual IP). e.g., virtual.cs.andrews.edu:5000 needs
to actually be allowed into the box AND your application needs to listen to
the IP. This means firewall rules. This also means setting up a virtual
interface or a transparent proxy rule like (in redhat kernels only AFAIK):
$IPTABLES -t nat -A PREROUTING -p tcp -d $VIP --dport 80 -j REDIRECT
--to-port 80
2 - Get rid of ARPing on the real servers if using virtual interfaces via
e.g. Julian's hidden patch (RTM!).
> I expect a "telnet lvs 5000" should pass the connection on to
> real server 1. This looked pretty easy in the docs. What am
> I missing?
Your tcpdump probably isn't showing anything because the request has
destination address VIP instead of your Real server IP. Firewall?
|
