[Pacemaker] CMAN with multiple networks for HA communication

Christine Caulfield ccaulfie at redhat.com
Fri Jun 20 09:49:13 CEST 2014


On 20/06/14 04:33, Teerapatr Kittiratanachai wrote:
> For IP address issue, I will find about that concern and take
> responsibility on risk for now.
>
> For multiple altname's, as I found in
> http://rpm.pbone.net/index.php3/stat/45/idpl/8711809/numer/5/nazwa/cman
> it said that
>
>>
>> Multi-home configuration .... Up to 9 altnames (10 interfaces in total) can be used.
>>
>
> Is that the old document?
>


It's a current document (based on cman.5 in the distribution) but it is 
actually very wrong. corosync only supports a maximum of 2 interfaces - 
that's 1 only altname!

Chrissie


> On Fri, Jun 20, 2014 at 10:27 AM, Digimer <lists at alteeve.ca> wrote:
>> Using raw IPs is not recommended. I remember Chrissie explaining the reason
>> why a couple of years ago, but I can't remember that reasoning right not.
>>
>> As for multiple altname's, that is not possible. Corosync's RRP (redundant
>> ring protocol) supports a primary and backup ring only.
>>
>> digimer
>>
>>
>> On 19/06/14 11:24 PM, Teerapatr Kittiratanachai wrote:
>>>
>>> I just already try this. It work !!
>>> I don't understand that why there is no example in the Internet using
>>> IP address as node name or altname.
>>>
>>> But I cann't add more than one altname, can you give me the xml
>>> example or the ccs command ?
>>>
>>> Thanks
>>> --Te
>>>
>>> On Fri, Jun 20, 2014 at 9:56 AM, Digimer <lists at alteeve.ca> wrote:
>>>>
>>>> Strictly speaking, it might be possible, but I haven't tried it myself
>>>> and I
>>>> certainly don't recommend it.
>>>>
>>>>
>>>> On 19/06/14 10:29 PM, Teerapatr Kittiratanachai wrote:
>>>>>
>>>>>
>>>>> Great, It work.
>>>>>
>>>>> Is it possible to use IP address as node name or altname?
>>>>> But I guess not.
>>>>>
>>>>> --Te
>>>>>
>>>>> On Thu, Jun 19, 2014 at 9:20 PM, Digimer <lists at alteeve.ca> wrote:
>>>>>>
>>>>>>
>>>>>> 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 at 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 at 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
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pacemaker mailing list: Pacemaker at 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
>>>>>
>>>>
>>>>
>>>> --
>>>> 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 at 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
>>>
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at 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
>>>
>>
>>
>> --
>> 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 at 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
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
>




More information about the Pacemaker mailing list