On Sat, May 12, 2012 at 2:49 AM, Steve Davidson
wrote:
> 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
>
On Friday 11 May 2012 17:49:38 Steve Davidson wrote:
> 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
>
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 privat