[Pacemaker] How should I configure the STONITH?

[Qiu Zhigang]

Hi


> -----Original Message-----
> From: Andreas Kurz [mailto:andreas at hastexo.com]
> Sent: Wednesday, December 21, 2011 6:53 AM
> To: pacemaker at oss.clusterlabs.org
> Subject: Re: [Pacemaker] How should I configure the STONITH?
> 
> Hello,
> 
> On 12/20/2011 05:01 AM, Qiu Zhigang wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: Andreas Kurz [mailto:andreas at hastexo.com]
> >> Sent: Monday, December 19, 2011 6:50 PM
> >> To: pacemaker at oss.clusterlabs.org
> >> Subject: Re: [Pacemaker] How should I configure the STONITH?
> >>
> >> Hello,
> >>
> >> On 12/19/2011 08:31 AM, Qiu Zhigang wrote:
> >>> Hi all,
> >>>
> >>> I want to configure the STONITH, but I couldn't find the following
> >>> CLI described in the reference material (like
> >>> Pacemaker-1.1-Pacemaker_Explained-en-US.pdf).
> >>>
> >>> stonith -L
> >>> stonith -t ibmhmc -n
> >>> stonith -t apcmaster -h
> >>>
> >>> I only found the stonith_admin command, but when I execute this cli,
> >>> some problem occurred.
> >>>
> >>> [root at h10_151 ~]# stonith_admin  -L
> >>> stonith_admin[14402]: 2011/12/19_15:29:20 info: crm_log_init_worker:
> >>> Changed active directory to /var/lib/heartbeat/cores/root
> >>> stonith_admin[14402]: 2011/12/19_15:29:20 notice: log_data_element:
> >>> st_callback: st_notify_disconnect <notify t="st_notify"
> >>> subt="st_notify_disconnect" />
> >>>
> >>> What's the reason of this problem ?
> >>>
> >>> Moreover I didn't find the stonith plugins, which rpm package
> >>> contain the stonith plugins ? I use the redhat 6, pacemaker version
> >>> is pacemaker-1.1.2-7.el6.x86_64.rpm.
> >>
> >> RHEL6 and derivates ship "fence-agents" package known from it's
> >> redaht-cluster and not the stonith agents ... the agents are all
> >> named "fence_*' and come with nice man-pages.
> >>
> >> You can use them (nearly) like the stonith agents that used to come
> >> with Pacemaker as prerequisite.
> >
> > Thank you, but I'm doubt the way of configure fence-agents in pacemaker.
> > Could I configure like following? If this isn't right, please point me
> > the right way, thank you.
> >
> > configure
> > primitive st-apc stonith: fence_apc \
> > params ip="xx.xx.xx.xx" username="admin" password="password"
> > clone fencing st-apc
> > commit
> 
> try something like this for the primitive:
> 
> primitive st-apc stonith:fence_apc \
> 	params ipaddr="xx.xx.xx.xx" login="admin" passwd="password" \
> 	action="reboot" port="dummy" pcmk_host_list="node1 node2" \
> 	pcmk_host_map="node1:1,node2:2" pcmk_host_check="static-list"
> 
> "man stonithd" and "man fence_apc" should also be helpful
> 
Thank you, I'll try.

> >
> > Another question is about Quorum device, which component is the quorum
> > device in pacemaker, like qdisk in CMAN, is SBD?
> 
> corosync or heatbeat CCM do this job for Pacemaker ... deliver node
availability
> information so Pacemaker can calculate quorum based on node count.
> 
But how to process the split-brain with 2-nodes ? In cman we could use qdisk
to 
arbitrate the quorum node, what about the corosync+pacemaker?

> Regards,
> Andreas
> 
> --
> Need help with Pacemaker?
> http://www.hastexo.com/now
> 
> >
> >
> > Best Regards,
> > Qiu Zhigang
> >>
> >> Regards,
> >> Andreas
> >>
> >> --
> >> Need help with Pacemaker?
> >> http://www.hastexo.com/now
> >>
> >>>
> >>>
> >>> Best Regards,
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
>