|
We would like to begin to migrate from a heartbeat2
setup to a Pacemaker/Corosync setup. We have a couple of
questions however and would be grateful if anyone had some answers
to help us along.
Currently we have 2 data centers separated by a dedicated
circuit between them for DRBD and Heartbeat2 replication/sync.
Our current setup uses 2 vlans that are connected to a core
router on both sides of the circuit.
Corosync1: (hypera-1)
vlan:1 -- local router. ip address: (eth0.658: 192.168.0.2/31)
vlan:2 -- router on other side of wan link. ip
address: (eth1.758: 192.168.1.2/31)
dummy0: 192.168.2.1/32
Corosync2: (hypera-2)
vlan:1 -- local router. ip address: (eth0.659 192.168.1.4/31)
vlan:2 -- router on other side of wan link ip
address: (eth1.759 192.168.0.4/31)
dummy0: 192.168.3.1/32
We would like to be able to have corosync use both
vlans for adjacent communication. We don't have them on the
same subnet so we assume we need to run udpu. I have pasted our
current heartbeat2 setup for some clarification.
hypera-1:
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility daemon
keepalive 1
deadtime 10
warntime 5
initdead 30
udpport 694
ucast eth0.658 192.168.3.1
ucast eth1.758 192.168.3.1
node hypera-1
node hypera-2
crm respawn
hypera-2:
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility daemon
keepalive 1
deadtime 10
warntime 5
initdead 30
udpport 694
ucast eth0.659 192.168.2.1
ucast eth1.759 192.168.2.1
node hypera-1
node hypera-2
crm respawn
My question is can we have corosync replicate a
similar setup? Thank you.
David W. Jablonski | Systems Administrator | INOC | Madison, WI USA O: +1-608-204-0202 | F: +1-608-663-4558 | djablonski@xxxxxxxx | www.inoc.com Service. Not Software.® |
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
