What we've done is set up our machines with crossover Ethernet on Eth1 for synch and has IP addresses for our machines on Eth0 and a "floating" IP address for failover for our applications. This has been working in our production environment for our front end (API) boxes on a MySQL cluster processing a few hundred thousand transactions a day. From a performance standpoint this configuration gave us our highest numbers in our test environment
Simon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anders Bruun Olsen Sent: Wednesday, December 19, 2007 8:50 AM To: General Linux-HA mailing list Subject: Re: [Linux-HA] Failover IP on dedicated interface [EMAIL PROTECTED] wrote: > By having 2 Ethernet ports on each machine, one for the heartbeat and > one as an active interface. If you are using a crossover for the > heartbeat, the active interface would allow you to access the machine > when it was not your active node. I have eth0 connected to our LAN which allows me to access the machines, I do DRBD sync over eth1 connected to an isolated switch and I do heartbeat over a serial cable. Eth2 is dedicated to datacommunication over another isolated switch. -- Anders _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
