On 19/06/14 08:00 AM, Teerapatr Kittiratanachai wrote:
Dear List,
According to CMAN identify each node in cluster by hostname.
So I configure the IP address in /etc/hosts file as below.
...
172.16.7.1 node00.example.com
172.16.7.2 node01.example.com
...
So the corosync member show as below
[root@node00 ~]# corosync-objctl | grep member
runtime.totem.pg.mrp.srp.members.2.ip=r(0) ip(172.16.7.2)
runtime.totem.pg.mrp.srp.members.2.join_count=1
runtime.totem.pg.mrp.srp.members.2.status=joined
runtime.totem.pg.mrp.srp.members.1.ip=r(0) ip(172.16.7.1)
runtime.totem.pg.mrp.srp.members.1.join_count=1
runtime.totem.pg.mrp.srp.members.1.status=joined
My question is, is it possible to add more than one network for the HA
communicate between these nodes?
e.g. if 172.16.7.0/30 is down. And another network, which be main
access network, still be up. the HA will use UP network to talk
instead of the down one.
Thank you in advance.
Regards,
Teerapatr Kittiratanachai (Te)
You're asking about setting up corosync's redundant ring protocol,
correct? If so, yes. You can use cman's 'altname' element to add a
second name for the node, and then have that name resolve to the network
you want to use as the backup link.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
_______________________________________________
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