[Pacemaker] AP9606 fencing device

[Pavlos Parissis]

On 17 November 2010 04:15, Devin Reade <gdr at gno.org> wrote:

> --On Wednesday, October 27, 2010 09:47:14 AM +0200 Pavlos Parissis
> <pavlos.parissis at gmail.com> wrote:
>
> > I have a APC AP9606 PDU and I am trying to find a stonith agent which
> > works with that PDU.
>
> I know that this is an old thread, but I'll reply anyway.
>
> I have a one cluster that uses an old APC AP9606 for which I've not
> been able to obtain a flash update.  In particular, it is:
>     hardware revision: J13
>     APP version 2.2.0
>     AOS version 3.0.3
>
> It is running just fine (see caveat below) with the following
> configuration,
> and I can attest that it has properly stonith'd nodes many times.
>
> primitive msw stonith:apcmastersnmp \
>        operations $id="msw-operations" \
>        op monitor interval="15" timeout="15" start-delay="15" \
>        params ipaddr="IPADDR" port="161" community="COMMUNITY"
> clone msw-clone msw \
>        meta clone-max="2" target-role="started"
>
> (yeah, that monitor interval is probably a little quick ...)
>
> That particular cluster is getting long in the tooth:
>     pacemaker-1.0.5-4.6.x86_64
>     openais-0.80.5-15.1.x86_64
>
> The caveat is that this PDU used to work with the default implementation,
> however at some point someone updated the OIDs in apcmastersnmp to
> match newer firmware.  Therefore, I had to reverse patch that RA:
>
> ===============================================================
> --- apcmastersnmp.c.orig        2009-09-26 16:12:27.000000000 -0600
> +++ apcmastersnmp.c     2009-09-28 16:46:17.000000000 -0600
> @@ -137,12 +137,12 @@
>  #define OUTLET_NO_CMD_PEND             2
>
>  /* oids */
> -#define OID_IDENT                      ".1.3.6.1.4.1.318.1.1.12.1.5.0"
> -#define OID_NUM_OUTLETS
> ".1.3.6.1.4.1.318.1.1.12.1.8.0"
> -#define OID_OUTLET_NAMES
> ".1.3.6.1.4.1.318.1.1.12.3.4.1.1.2.%i"
> -#define OID_OUTLET_STATE
> ".1.3.6.1.4.1.318.1.1.12.3.3.1.1.4.%i"
> -#define OID_OUTLET_COMMAND_PENDING
> ".1.3.6.1.4.1.318.1.1.12.3.5.1.1.5.%i"
> -#define OID_OUTLET_REBOOT_DURATION
> ".1.3.6.1.4.1.318.1.1.12.3.4.1.1.6.%i"
> +#define OID_IDENT                      ".1.3.6.1.4.1.318.1.1.4.1.4.0"
> +#define OID_NUM_OUTLETS                ".1.3.6.1.4.1.318.1.1.4.4.1.0"
> +#define OID_OUTLET_NAMES               ".1.3.6.1.4.1.318.1.1.4.5.2.1.3.%i"
> +#define OID_OUTLET_STATE               ".1.3.6.1.4.1.318.1.1.4.4.2.1.3.%i"
> +#define OID_OUTLET_COMMAND_PENDING     ".1.3.6.1.4.1.318.1.1.4.4.2.1.2.%i"
> +#define OID_OUTLET_REBOOT_DURATION     ".1.3.6.1.4.1.318.1.1.4.5.2.1.5.%i"
>
>  /*
>        snmpset -c private -v1 172.16.0.32:161
> ===============================================================
>
>
I faced the same problem and because I didn't want to modify the code of
apcmastersnmp RA, I used the rackpdu RA where I could set OIDs in the
parameters.
This RA worked perfectly until the PDU died!
I suggest to use the rackpdu RA because if you upgrade your cluster software
your modification will be gone.

Cheers,
Pavlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101117/15b91c28/attachment-0001.html>