LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: LVS with mark tracking

To: "'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: LVS with mark tracking
From: "Tan, Guan Boon" <guan.boon.tan@xxxxxxxxx>
Date: Sun, 18 Feb 2001 21:52:59 -0800
Hi,

        This is just a desired network setup. I haven't setup this
successful yet. The network diagram should be like this. Anyone who setup
this successfully ? 

Regards
Guan Boon

-----Original Message-----
From: Roberto Nibali [mailto:ratz@xxxxxx]
Sent: Sunday, February 18, 2001 6:18 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: LVS with mark tracking


> The problem for multihoming
> Many companies require for high availability by using links to more than
one
> ISP. The ISP market is not as mature as other countries and we find that
> each ISP is either unwilling or unable to provide proper BGP support. This
> places and overhead on the content provider or hosting site to use
multiple
> address spaces, one registered address space per ISP.

Ok, seen that over here too.
 
> The solution
> One solution to this problem would be to create a dummy VIP for each ISP
> connection. To the dummy VIP address a member is added that would be
> unavailable should the link or ISP be unavailable. The availability of the
> member could be checked using a simple ping. Should the member be

Ping is IMHO not reliable enough and do you really want to enable
ICMP echo_request and reply to/from your LVS-box?

> unavailable then the VIP will also be unavailable since it has only one
> member. To ensure that the director sends ping checks to the correct ISP
> connection a static host route should be added to the director routing
table
> to force the check through the correct ISP connection and thus the correct
> interface address.

Oups, I'm a but confused, tell me, did the sketch below reflect
your setup correctly or did it?

> Now that we have a mechanism to determining the availability, from the
> Internet, of each registered address space we can tie the dummy VIP port
and
> real VIP port together using DNS. DNS is configured to use a VIP only if
the
> real port and the dummy VIP port are both available.It means that DNS
should

You mean template based healthchecking and dynamic DNS reconfiguration?

> be intelligent health check the vip. Should either VIP port be unavailable
> then the real VIP address will not be returned to the client.

I really start thinking, that I got you're setup wrong. Please tell me
if the sketch does show your desired network setup.
 
>     ____________      ____________    ____________
>    |            |    |            |  |            |
>    |  ISP1      |    |  ISP2      |  |  ISP3      |
>    |____________|    |____________|  |____________|
>          |                 |               |
>          |                 |               |
>       (router)         (router)         (router)
>          |                 |               |
>          +-----------+     |     +---------+
>                   ___|_____|_____|____
>                  |                    |
>                  |   director (VIP)   |
>                  |____________________|
>                            |
>                            |
>                            |
>          ------------------------------------
>          |                 |                |
>          |                 |                |
> 
>     ____________      ____________    ____________
>    |            |    |            |  |            |
>    |real-server1|    |real-server2|  |real-server3|
>    |____________|    |____________|  |____________|

Regards,
Roberto Nibali, ratz

-- 
mailto: `echo NrOatSz@xxxxxxxxx | sed 's/[NOSPAM]//g'`

_______________________________________________
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

Attachment: LVS.ZIP
Description: Binary data

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