We want to run the Corosync heartbeat on the private net and, as a
backup heartbeat, allow Corosync heartbeat on our "public" net as well.
Thus in /etc/corosync/corosync.conf we need something like:
bindaddr_primary: 192.168.57.0
bindaddr_secondary: 125.125.125.0
Our thinking is: if the private net connection fails but everything else
is okay then we don't need to disrupt services since the private net
failure won't affect our users.
Is there any way to do this? Otherwise we need two interfaces connected
to separate switches just for an (HA) heartbeat. We don't want to
recover services when everything is working except the private net or
interface.
Steve
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
