On Tue, Sep 14, 2010 at 3:59 PM, Dejan Muhamedagic <[email protected]>wrote:
> Him > > On Tue, Sep 14, 2010 at 02:57:12PM +0530, harish tene wrote: > > On Tue, Sep 14, 2010 at 1:12 PM, Florian Haas <[email protected] > >wrote: > > > > > On 2010-09-14 09:19, harish tene wrote: > > > >>>> stonith_host * external/riloe node1 node1_ilo_ipaddress ilo2_login > > > >>>> ilo2_password 1 2.0 off > > > >>>> > > > >>>> stonith_host * external/riloe node2 node2_ilo_ipaddress ilo2_login > > > >>>> ilo2_password 1 2.0 off > > > >>> > > > >>> These lines only apply to non-crm/pacemaker clusters. > > > >>> What are you trying use? > > > >>> > > > >> > > > >> *I am using Heartbeat version 2.1.3.* > > > > > > Bad bad bad idea. Upgrade to Heartbeat 3.0.3 and Pacemaker _before_ you > > > start collecting ideas for writing your own resource or STONITH agents. > > > > > > > @Florian - Thank you for the suggestion. Unfortunately, my existing > system > > does not allow me to upgrade :( though there could be plans for future. > And > > as per my knowledge, the question of cloning still remains for upgraded > > versions too(pls correct me if I am wrong). My intention is to understand > > cloning, and cloning for stonith. > > > > *"Does cloning for stonith for 2 nodes only has any undesired effects? > For a > > 2 node configuration, what is the difference if I clone STONITH and if I > > don’t. Any advantages or dis-advantages of using or not using cloning.*" > > If you're using riloe, definitely better not to use clones. Forgive my ignorance, but my question will be why? Is it for the reason that multiple connections are not allowed to an ILO device? Regards, Harish Just add negative location constraints for the node which the stonith > resource is to manage/fence. See > http://www.clusterlabs.org/doc/crm_fencing.html > And upgrade as soon as you can. > > Thanks, > > Dejan > > > > Regards, > > Harish > > > > > > > Cheers, > > > Florian > > > > > > > > > > > > _______________________________________________ > > > Linux-HA mailing list > > > [email protected] > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > See also: http://linux-ha.org/ReportingProblems > > > > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
