|
Thanks,
I suspect I'll end up using a dual connection setup where the initial
Client->Director->RealServer connection simply transmits the secondary
server IP back to the client - the client then reconnects through SSL to the
real server's other interface.
My goal is to keep the Director load as low as possible as I will probably
need to run some other services on it - I'll have to modify the scheduling
logic because now the real-server's Director tracked connections are not
representative of server load. I thought I might have to do this anyways
because server load will probably not be correllated with # of
connections...
Thanks again.
> -----Original Message-----
> From: Joseph Mack [SMTP:mack.joseph@xxxxxxx]
> Sent: Thursday, January 31, 2002 11:43 AM
> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Dual NIC'd Real Servers under LVS-DR
>
> Keith Hellman wrote:
>
> >
> > I do have one nagging lack-of-understanding:
> >
> > I have attached a diagram as plain text.
>
> got it. we're reaching new heights of ascii art.
>
> My understanding is that the following happens:
> > 1 A client connects to the VIP on the Director
> > 2 The Director (using DR) mods the MAC to an appropriate value for
> a
> > real server, and retransmits on the LAN A
> > 3 The RS picks this packet up, and when it transmits back to the
> > client, it will go out the default interface (LAN B) - avoiding the LAN
> A
>
> I'm not sure where LAN A is, but basically yes.
>
> > Here are my questions/impressions:
> > A I'm under the impression that under VS-DR, the Director does not
> > finish the TCP session setup - it passes the first packet (SYN?)
> directly to
> > the RS and the RS finishes the session setup with the client - is this
> > correct? Note that I'm only interested in DR.
>
> yes
>
> > B Packets sent from the real server for TCP/IP session initiation,
> as
> > well as application layer transmission, will always be sent across LAN B
> -
> > is this correct?
>
> it depends. packets with src_addr=VIP get sent via B to the internet.
> Connections
> initiated on the realserver have nothing to do with the function of the
> LVS
> and can will have src_addr=DIP. They can be sent anywhere. For an example
> see
>
> http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-13.html#ss13
> .10
>
> > C Packets from the Client will ALWAYS go through the Director, and
> be
> > re-routed to the appropriate real server (through LAN A) - is this
> correct?
>
> yes
>
> > Or will the IP address of the real-server's default interface actually
> be
> > 'noticed' by the client (perhaps not at the application layer, but
> inside
> > the networking stack...) and 100% of client<->RS communications will
> happen
> > across LAN B?
>
> the client only knows about the VIP and sees the LVS as one machine.
>
> 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
>
> _______________________________________________
> 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
|
