Re: [Pacemaker] How to avoid CRM sending stop when ha.cf gets 2nd node configured

2014-11-10 Thread Lars Ellenberg
On Sat, Nov 08, 2014 at 12:58:36AM +, aridh bose wrote: Hi, While using heartbeat and pacemaker, is it possible to bringup first node which can go as Master, followed by second node which should go as Slave without causing any issues to the first node? Currently, I see a  couple of

Re: [Pacemaker] How to avoid CRM sending stop when ha.cf gets 2nd node configured

2014-11-09 Thread Andrew Beekhof
On 8 Nov 2014, at 11:58 am, aridh bose ari...@yahoo.com wrote: Hi, While using heartbeat and pacemaker, is it possible to bringup first node which can go as Master, followed by second node which should go as Slave without causing any issues to the first node? Currently, I see a couple

[Pacemaker] How to avoid CRM sending stop when ha.cf gets 2nd node configured

2014-11-07 Thread aridh bose
Hi, While using heartbeat and pacemaker, is it possible to bringup first node which can go as Master, followed by second node which should go as Slave without causing any issues to the first node? Currently, I see a  couple of problems in achieving this:1. Assuming I am not using mcast