|
Hi,
It is very easy. We run lvs using tunneling (ipip) with 3 windows 2000 real
servers, and it works a treat.
The steps are something like:
1. Install a loopback adapter on each real server. I think this is documented
elsewhere
to solve the ARP problem. But basically, go to add new hardware, network,
microsoft,
loopback adapter. Assign this adapter the IP address of the cluster, (VIP).
- Sounds like you have already done this
2. Go to routing and remote access on each real server. Enable if needed. Dont
let it
automatically configure = asking for trouble. Under routing interfaces, add a
new IPTunnel. Now, under IP
Routing - General, add a new interface, selecting the IPTunnel that you have
just created.
For the 'Local address', specify the RIP of that real server. For the Remote
Address,
specify the DIP. Ok through all that and then reboot the real server. - it is
M$ after all.
- Sounds like you have specified the wrong IP address
Thats it. The server should now respond to IPIP requests.
Hope this helps.
Chris
-----Original Message-----
From: AdamMH@xxxxxxx [mailto:AdamMH@xxxxxxx]
Sent: 02 September 2003 22:57
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: windows 2000 real server's
Hello,
I'm wondering if anyone can help me with some lvs/ipvs configuration issues
regarding
Windows' Real Server's and LVS-Tunneling. I've read through the FAQ and
searched through the
archived message groups quite a bit, and have seen more than a few posts
stating it is in
fact possible, however i've yet to accomplish the scenario myself. I have been
able to
configure lvs using Direct Routing, however, when I configure the Microsoft
Loopback
Adapter on the Windows Real Server. The problem is that I would like to do the
same, but
tunnel the connection instead for a machine not on the same network (In another
datacenter). I have been able to achieve this configuration when all Server's
in question
are Linux-based, however when Windows is thrown into the equation things start
to get
messy. I saw a FAQ post regarding setting up some Window's Routing Rule's and
have done so
as follows:
- Created a new General IP Routing Tunnel (Interface) and set it's local and
remote
addresses' to the VIP and Director IP, respectively. I also configurd the
Microsoft
Loopback Adapter to use the VIP, and set it's subnet mask to 255.0.0.0 as was
recommended.
As previously states, thing's work fine when using Direct Routing, however as
soon as I
attempt to use IP Tunneling things start to fall apart. I was thinking this
setup might
perhaps require some additional ip tunnel rules? I wrote a few rules's to do
some
masquerading and such, but I just can't manage to get it working. I've been at
it for a few
days now and the sleep deprivation is I think finally beginning to catch up
with me. :)
I would be extremely grateful if anyone could provide any assistance in regards
to this. :)
Best Regards,
Adam Hammouda
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
Berkeley Alexander
Temple House, 25-26 High Street, Lewes, East Sussex, BN7 2SD
Tel 01273 477784, Fax 01273 478994
www.baonline.co.uk
PLEASE NOTE:
The information in this e-mail is confidential and may be legally privileged.
It may not represent the views of Berkeley Alexander. It is intended solely for
the addressees. Access to this e-mail by anyone else is unauthorised. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful. Any unauthorised recipient should advise the sender immediately of
the error in transmission.
|
