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.
Simon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anders Bruun Olsen Sent: Wednesday, December 19, 2007 8:23 AM To: General Linux-HA mailing list Subject: Re: [Linux-HA] Failover IP on dedicated interface Dejan Muhamedagic wrote: >> To sum up, I have eth2 dedicated to a specific IP on both cluster nodes >> and I want heartbeat to do failover for it. Is there a way to do this >> without ending up with eth2:0, with the current resource scripts? > Why do you need to move the real interface addresses? What's > wrong with using virtual IPs? There is nothing wrong with it per se. I just think it is a bit awkward that I need to have eth2 up with no IP just so the failover IP can be added as a secondary IP. It seems cleaner to have heartbeat bring eth2 online when it starts and then when failover happens the secondary node brings eth2 up there with the correct IP and all. -- 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
