Hi,
sorry but I thought that if we set "rrp_mode" to "active", corosync is
using both rings "at the same time" , isn't it ?
Alain
Le 26/08/2013 15:53, Digimer a écrit :
On 26/08/13 09:14, Francis SOUYRI wrote:
Hello,
Is Corosync works with eth and bond at the same time ?
with the config below I have an error message "[MAIN ] No ring0_addr
specified for node"
totem {
version: 2
secauth: off
cluster_name: cluster
interface {
ringnumber: 0
bindnetaddr: 10.1.1.0
ttl: 1
}
interface {
ringnumber: 1
bindnetaddr: 192.168.1.0
ttl: 1
}
transport: udpu
}
nodelist {
node {
ring0_addr: 10.1.1.1
nodeid: 1
}
node {
ring0_addr: 10.1.1.2
nodeid: 2
}
node {
ring1_addr: 192.168.1.253
}
node {
ring1_addr: 192.168.1.254
}
}
quorum {
provider: corosync_votequorum
}
logging {
to_syslog: yes
}
The addresses 10.1.1.1 (bond0) and 192.168.1.253 (eth2) are on the same
node.
The addresses 10.1.1.2 (bond0) and 192.168.1.254 (eth2) on the other.
Best regards.
Francis
Not "at the same time", no. Corosync will use ring 0 for as long as it
is available and working. If the interface/bond behind ring 0 fails,
it will switch to ring 1.
_______________________________________________
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
