Am Dienstag, 16. Februar 2010 20:50:33 schrieb Ciro Iriarte: > 2010/2/16 Michael Schwartzkopff <[email protected]>: > > Am Dienstag, 16. Februar 2010 19:25:47 schrieb Ciro Iriarte: > >> How is the recommended setup to have a high available LVS service?, > >> should we run ldirectord with pacemaker?, should we run ipvasadm > >> outside the cluster? > >> > >> Regards, > >> CI.- > > > > Hi, > > > > I would run the virtual IP (VIP) of the LVS server as a IPaddr2 resource > > of the cluster. If you have a NAT setup you alos would run the DIP as a > > cluster service. > > > > I also like to integrate ldirectord into the cluster since the cluster > > can check if the daemon still is alive. > > > > Greetings, > > > > -- > > Dr. Michael Schwartzkopff > > MultiNET Services GmbH > > Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany > > Tel: +49 - 89 - 45 69 11 0 > > Fax: +49 - 89 - 45 69 11 21 > > mob: +49 - 174 - 343 28 75 > > So, your recommendation would be to run ldirectord as a resource?, > what about the connection table synchronization in failover and > failback events?. I was initially planning to use LVS-NAT, but I'll > give LVS-DR a try... > > CI.-
Connection table sync is the job of ipvsadm. Since this is a part of the kernel module the cluster (userspace!) would not help too much here. I'd start the sync daemons (master and slave) on both machines together with ipvsadm. The corresponding option in debian is "both". So both machines are master and slave. Since only one machine has the VIP this setup works. Greetings, -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [email protected] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
