It seems like a significant problem to have fence_ipmilan issue a power-off followed by a power-on with a 2 node cluster. As described both nodes power-off and are then unable to issue the required power-on. Does anyone know a solution to this? This seems to make a 2-node cluster with ipmi fencing pointless. It looks like fence_ipmilan needs to support sending a cycle instead of a poweroff than a poweron?
According to fence_ipmilan.c it looks like cycle is not an option although it is an option for ipmitool. (ipmitool -H <ipaddr> -U <userid> -P <password> chassis power cycle)
>From fence_ipmilan.c:
switch(op) {
case ST_POWERON:
snprintf(arg, sizeof(arg),
"%s chassis power on", cmd);
break;
case ST_POWEROFF:
snprintf(arg, sizeof(arg),
"%s chassis power off", cmd);
break;
case ST_STATUS:
snprintf(arg, sizeof(arg),
"%s chassis power status", cmd);
break;
}
Thanks,
Dan
-------------- Original message ----------------------
From: "Zachacker, Maik" <zachacker@xxxxxx>
> >> Also is there a way to configure fence_ipmilan in cluster.xml to
> reboot
> >> rather than stop the server? fence_ipmilan by itself takes the -o
> >> option (on,off,reboot)
> >
> > I use fence_ipmilan (with CS4 Update 2) it does at
> > first poweroff AND then poweron ... except if it does not get
> > the off status after the poweroff. (check agent ipmilan.c)
>
> I use fence_ilo and fence_apc (CS4U3) - both first poweroff and then
> poweron too. This is only a problem in a two node configuration because
> both nodes send the poweroff command and non of them can send the
> poweron command because both are down.
>
> The most fence-devices have an option or action tag, that is not
> available via the cluster configuration tool. They can be used to force
> a reboot (default) or an poweroff.
>
> <fencedevice action="off" agent="fence_ilo" .../>
> <fencedevice agent="fence_apc" option="off" .../>
>
> Maik Zachacker
> --
> Maik Zachacker
> IBH Prof. Dr. Horn GmbH, Dresden, Germany
>
>
> --
>
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
