[ClusterLabs] RES: RES: Can't get a group of IP address up when moving to a new version of Pacemaker/Corosync

2015-09-04 Thread Carlos Xavier
Tank you Dejan. I Just tested the command the RA is trying to run on a OpenSuse installation ant it worked fine. The command is: " iptables -I INPUT -d 172.31.0.148 -i lo -j CLUSTERIP--new --clustermac b1:0a:7b:8b:9c:70 --total-nodes 2 --local-node 1 --hashmode sourceip-sourceport" Afte

Re: [ClusterLabs] RES: RES: Can't get a group of IP address up when moving to a new version of Pacemaker/Corosync

2015-09-03 Thread Ken Gaillot
On 09/03/2015 01:48 PM, Carlos Xavier wrote: > Tank you very much Ken. > > I'll take a close look at that. > Is there any documentation where I can learn more about the > Pacemaker/IPtables integration? > The chain that needs to be created has the same name of the resource I'm > trying to clone?

Re: [ClusterLabs] RES: RES: Can't get a group of IP address up when moving to a new version of Pacemaker/Corosync

2015-09-03 Thread Victor José Acosta Domínguez
Thanks for answer, can you please tell me how much cost every extra IP? Thanks Regards Victor Acosta RHCE - RHCSA - VCA-DCV 2015-09-03 14:48 GMT-04:00 Carlos Xavier : > Tank you very much Ken. > > I'll take a close look at that. > Is there any documentation where I can learn more about the >

[ClusterLabs] RES: RES: Can't get a group of IP address up when moving to a new version of Pacemaker/Corosync

2015-09-03 Thread Carlos Xavier
Tank you very much Ken. I'll take a close look at that. Is there any documentation where I can learn more about the Pacemaker/IPtables integration? The chain that needs to be created has the same name of the resource I'm trying to clone? Shouldn't the IPaddr2 RA solve this issue by itself? When