[Linux-cluster] iSCSI fence agent?

[Matthew B. Brookover]

This is a bit of a hack, but it works with unh-iscsi and iptables.  I
took one of the other fencing tools and modified it up to do an 'ssh
root at iscsitarget  iptables -A INPUT -s a.b.c.d -p all -j REJECT' to
disable an iscsi initiator.  The enable command deletes the rule.

You will need to set up ssh to run without passwords.

Matt


On Mon, 2004-10-11 at 21:33, David Teigland wrote:

> On Tue, Oct 12, 2004 at 11:08:19AM +0800, Chung Hsien Hu wrote:
> > Hi,
> > I am trying to setup a storage environment with GFS and iSCSI.
> > By using the open community projects of iSCSI initiator and target 
> > sides, I could
> > access the remote disk via iSCSI without too much problem.
> > But which fence agent should I indicate for GFS in the /etc/cluster.conf?
> 
> It might be nice for someone to write a fencing agent that would talk to
> the iscsi target software.  Until then you can use network power switches
> or manual fencing to experiment.
> 
> > I got these error on my log.
> > 
> > lock_dlm: init_fence error -1
> > GFS: can't mount proto = lock_dlm, table = innocluster:iscsi45, hostdata =
> 
> This is because the fence daemon (fenced) is either not running or has not
> started up correctly (maybe it can't connect to ccsd).  You can diagnose
> fenced problems by using the debug flag: "fenced -D".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20041012/dd671aef/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_iptables
Type: text/x-perl
Size: 5691 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20041012/dd671aef/attachment.bin>