arp could help.
But your best option is to use heartbeat / pacemaker, and deploy hard
fencing such as a networked PDU, or a managed switch.
On Fri, May 2, 2014 at 8:27 AM, John Lauro wrote:
> Any reason not just using heartbeat on the two nodes? (yum install heartbeat)
> Then setup multiple int
Any reason not just using heartbeat on the two nodes? (yum install heartbeat)
Then setup multiple interfaces between the two servers and let heartbeat bring
services up/down as needed, and heartbeat can control which node has the
secondary ip address active, etc.
- Original Message -
>
Don't use the main IP address for your traffic. Use a secondary,
virtual IP address on the same port or ports, say "ifcfg-eth0:1", and
tie it to any of the common VIP monitoring packages such as is used by
the master-master-mysql monitoring program. Basically, they
communicate over the available, p
