|
Roberto Nibali wrote:
>
> Hello Charles Huang,
>
> > #----------lvs_dr.conf----------------------------------------
> > LVSCONF_FORMAT=1.1
> > LVS_TYPE=VS_DR
> > INITIAL_STATE=on
> > CLEAR_IPVS_TABLES=yes
> > VIP=eth0:0 61.131.4.187 255.255.255.255 61.131.4.187
> > DIP=eth0 61.131.4.170 61.131.4.128 255.255.255.192 61.131.4.191
> > SERVICE=t http wrr ppc 61.131.4.171,2 61.131.4.172,2 61.131.4.173,2
> ^^^^^^^^^^^^^^
sorry, I missed this posting last week.
You don't need the ppc, the script handles persistence for you.
> But then Joe mentions something about linked services and I didn't
> quite follow that one:
ahem, cough, I'll try again.
Most services are handled by a single port entry in ipvsadm.
Some services need extra attention - the following conditions are
handled by the configure script.
https: the key exchanges needed for https require that the service
be persistent.
ftp: this is a multiport (20,21) service.
For LVS-NAT, the multiport setup is handled
by loading the module ip_masq_ftp. For VS-DR, VS-Tun,
the two ports are made persistent.
http/https: if http is forwarded to a realserver which
is also handling https, then http is made persistent, on
the assumption that this is an e-commerce site.
other port pairs: these can be set by adding entries to
the array @persistent_services.
Does this help?
Joe
> LINKED SERVICES
> Multi-port services e.g. ftp (port 20,21 ie ftp,ftp-data)
> or http/https (where connections to port 80 and 443 need
> to go to the same real-server) are called here linked
> services. (For VS-NAT, linking ftp and ftp-data is
> handled by the module ip_masq_ftp, which has to be loaded
> at run time.)
>
> For all other services/forwarding methods, linking of
> services is handled by LVS persistence (which could
> alternately be called "port affinity"). Although we only
> need to link these specific pairs of services, LVS
> persistence links all services on the real-server, not
> just the ones we need to link.
>
> Thus if any of the persistent_services (ftp or https) are
> found in the SERVICES line, then all services on that
> real-server are tied together. Once a client connects to
> that server for any service, all further connections for
> any other service from that client will go to the same
> real-server.
>
> I'm a little bit puzzled myself actually. Let Joe clarify things here :)
>
> Sorry I cannot help you right now,
> Roberto Nibali, ratz
>
> _______________________________________________
> 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
--
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
|
