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, primary IP address. If it's down, the
secondary VIP is kept down. When the primary address comes back down,
they negotiate over the primary address about which host to enable the
secondary VIP on.

On Thu, May 1, 2014 at 12:31 PM, CS_DBA <[log in to unmask]> wrote:
> Hi All;
>
> we have a failover tool (for a database) that pings te master and if it's
> not responding runs ifdown over ssh to bring an ip alias down, then runs
> ifup of the alias on the standby node.
>
> A possible issue would be if the master was not reachable, thus the ifdown
> fails and once the master becomes available again then we have 2 nodes with
> the ip alias and we risk a split brain issue
>
> Is there a way to disable any traffic from getting to the old master via
> commands we can run outside of the master server?
>
> Thanks in advance