[Pacemaker] AP9606 fencing device

[Vadym Chepkov]

On Oct 27, 2010, at 7:58 AM, Pavlos Parissis wrote:

> 
> On 27 October 2010 13:43, Vadym Chepkov <vchepkov at gmail.com> wrote:
> 
> On Oct 27, 2010, at 7:27 AM, Pavlos Parissis wrote:
> 
> > On 27 October 2010 13:12, Vadym Chepkov <vchepkov at gmail.com> wrote:
> >>
> >> On Oct 27, 2010, at 3:47 AM, Pavlos Parissis wrote:
> >>>
> >>> Does anyone know any other PDU which works out of box with the
> >>> supplied stonith agents?
> >>>
> >>
> >> I use APC AP7901, works like a charm:
> >>
> >> primitive pdu stonith:external/rackpdu \
> >>        params pduip="10.6.6.6" community="pdu-6" hostlist="AUTO"
> >> clone fencing pdu
> >>
> >> Vadym
> >
> > Then most likely the defaults OIDs of the rackpdu agents matches the
> > OIDs of the AP7901.
> > In my case I have to use OID for the device itself
> > 1.3.6.1.4.1.318.1.1.4.4.2.1.3  and OID for retrieving (snmpwalk) the
> > outlet list .1.3.6.1.4.1.318.1.1.4.4.2.1.4 .
> >
> > Hold on a sec, are you using clone on AP7901? Does it support multiple
> > connections? Mine it doesn't.
> 
> Then it's useless regardless clone or not, you have to have multiple instances, because server can't reliable fence itself, right?
> 
> 
> 
> My understanding is/was that I need to have one resource running on 1 of the 3 nodes in the cluster and if a fence event has to be triggered then pacemaker will send to it to the one stonith resource. I am planning to test that the coming days.[1]
> Am I right? if not then I have to buy a different PDU! :-(
> 

My understanding is you have to have a fencing device for each of your hosts. Are you sure one connection limitation applies for SNMP? Most likely it's only for tcp sessions - ssh/http ?
If you look into rackpdu log you will see this:

Oct 19 12:39:00 xen-11 stonithd: [8606]: debug: external_run_cmd: Calling '/usr/lib64/stonith/plugins/external/rackpdu gethosts'
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_run_cmd: '/usr/lib64/stonith/plugins/external/rackpdu gethosts' output: xen-11 xen-12 Outlet_3 Outlet_4 Outlet_5 Outlet_6 Outlet_7 Outlet_8 
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: running 'rackpdu gethosts' returned 0
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host xen-11
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host xen-12
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_3
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_4
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_5
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_6
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_7
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: external_hostlist: rackpdu host Outlet_8
Oct 19 12:39:01 xen-11 stonithd: [8606]: debug: remove us (xen-11) from the host list for pdu:0

check the last line - the agent is smart enough to know it can't fence itself.

Vadym


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101027/d1bb61c5/attachment-0002.htm>