On 13 Nov 2013, at 11:33 pm, andreas graeper wrote:
> hi,
> pacemaker version is 1.1.7
quite a bit of work has gone into fencing since then, any chance you could try
something newer?
>
> the fence-agent (i thought was one of the standards) calls
> snmpget -a : -c oid
> snmpset -a : -c oid
i stopped/started the resource and now stonith_admin kann see it again .
pcs resource stop fence_1
pcs resource start fence_1
but how can it get lost ?
thanks
andreas
2013/11/13, andreas graeper :
> hi,
> pacemaker version is 1.1.7
>
> the fence-agent (i thought was one of the standards) call
hi,
pacemaker version is 1.1.7
the fence-agent (i thought was one of the standards) calls
snmpget -a : -c oid
snmpset -a : -c oid i 0|1
therefor it needs/uses commandline arguments
-o action
-n port (slot-index)
-a ipaddr
-c community
(udpport is not necessary, cause fix == 161)
or (as
Impossible to comment without knowing the pacemaker version, full config, and
how fence_ifmib works (I assume its a custom agent?)
On 12 Nov 2013, at 1:21 am, andreas graeper wrote:
> hi,
> two nodes.
> n1 (slave) fence_2:stonith:fence_ifmib
> n2 (master) fence_1:stonith:fence_ifmib
>
> n1 was
hi,
two nodes.
n1 (slave) fence_2:stonith:fence_ifmib
n2 (master) fence_1:stonith:fence_ifmib
n1 was fenced cause suddenly not reachable. (reason still unknown)
n2 > stonith_admin -L -> 'fence_1'
n2 > stonith_admin -U fence_1 timed out
n2 > stonith_admin -L -> 'no devices found'
crm
