<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">Hi,</div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr"><br></div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">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:</div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">1. Assuming I am not using mcast communication, heartbeat is mandating me to configure second node info either in ha.cf or in /etc/hosts file with associated IP address. Why can't it come up by itself as Master to start with?</div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr"><br></div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">2. If I update ha.cf with the 2nd node info and use 'heartbeat -r' CRM first sends stop on the Master before sending start.</div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr"><br></div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">Appreciate any help or pointers.</div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr"><br></div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">Thanks,<br></div><div id="yui_3_16_0_1_1415407536278_9019" dir="ltr">Aridbh.</div></div></body></html>