|
Thanks for the reply. We talked the folks with the foundry box into
throwing it out :-)
I still would like to know if it is possible to cascade LVS machines if
they are at different locations using different IP addresses.
Let me explain what I mean
The folks who ran the Foundry and whose Web Application we host are located
in the States and use different IP addresses than we do.
Now they have got a spare Web Server which they wanted to run as sort of a
hot standby machine, thats why they set up this Foundry thing.
Over here at our place in Germany I run two directors with heartbeat and
behind them a two sets of Real Servers consisting of two machines each.
Each set autonomous and one is for the folks in the States. The method I
use is DR and it works well.
Here is the question: Can I set up a LVS machine in the States that directs
the traffic to the LVS machine at our place and our Real Servers answer
back?
I can not set the default route on the director here in Germany to point to
the machine in the States because the box is on a different network and
because I dont want to run traffic over that box for the other set of Web
Servers.
I once played a bit with iproute2 doing routing based on source addresses
and the like but I don't know whether this would be an option.
Any ideas on this ?
Thanks for helping
Best regards
Robert Gehr
"A ship in a harbour is safe, but that's not what ships are built for"
========================================
web2CAD AG
Emailfabrikstrs. 12
92224 Amberg / Germany
visit: http://www.web2cad.com
Joseph Mack
<mack.joseph@ An:
lvs-users@xxxxxxxxxxxxxxxxxxxxxx, Robert Gehr/GENIUS/DE
epa.gov> Kopie:
Thema: Re: Cascaded with Foundry
19.09.2001
12:46
robert.gehr@xxxxxxxxxx wrote:
>
> Hello there
>
> Let me desribe my Problem (Setup)
I take it that your LVS appears to be a leaf node in a foundry cluster.
The LVS preserves server-client semantics, so whatever a single node
can do attached to a Foundry box, the LVS will do too.
Let's see if I have your problem:
I don't know how a Foundry box works. Either it's NAT or DSR, or from
what you've said is a straight proxy. However it works, what you get
is a packet that the dst_addr has been changed from 233.233.233.233 to
244.244.244.244.
If you send your replies back to the Foundry box, does it convert
244.244.244.244
back to 233.233.233.233?
Do you want to directly reply to the client and not go through the Foundry?
In that case you'll have to NAT the source address on the replies
> Would it be a solution for me to mangle the outgoing IP address from the
> Real Servers to become the IP address of the Foundry box ?
I think so.
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
|
