[Linux-cluster] Fencing using brocade

Frank Hellmann frank at opticalart.de
Wed Sep 13 15:42:39 UTC 2006


Hi!

I can only recommend the system-config-cluster GUI, but if you feel
brave enough you can do it by hand

This example is for a sanbox2, but it should get you going:
 
   ...
        <fence_daemon post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="clusty1" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="sanbox" port="0"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="clusty2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="sanbox" port="1"/>
                                </method>
                        </fence>
                </clusternode>
                        ....
        </clusternodes>
        <fencedevices>
                <fencedevice agent="fence_sanbox2"
ipaddr="xxx.xxx.xxx.xxx" login="username" name="sanbox" passwd="password"/>
        </fencedevices>
   ...

And don't forget to check the fence_brocade manpage for your brocade
switch for further options...
       
       Cheers,

                Frank...

isplist at logicore.net wrote:
>>> I want to use my brocade switch as the fencing device for my cluster. I
>>> cannot find any documentation showing what I need to set up on the brocade
>>> itself and within the cluster.conf file as well to make this work.
>>>       
>
>   
>> The system-config-cluster application supports brocade fencing. It is a
>> two part process - first you define the switch as a fence device; type
>> brocade, then you select a node an click "Manage fencing for this node"
>> and declare a fence instance.
>>     
>
> Ah, I'm at the command line :). 
>
> So, there is nothing I need to do on the brocade itself then? The cluster 
> ports aren't connected directly, they are connected into a compaq hub, then 
> the hub is connected into the brocade. The brocade seems to know about the 
> external ports however since they are listed when I look on the switch.
>
> As for the conf file, I've not found enough information on how to build a good 
> conf file so know this one is probably not even complete. Been working on 
> other parts of the problems then wanting to get to this.
>
> <?xml version="1.0"?>
> <cluster config_version="40" name="vgcomp">
>     <fence_daemon clean_start="1" post_fail_delay="0" post_join_delay="3"/>
> <clusternodes>
>     <clusternode name="cweb92.companions.com" nodeid="92" votes="1"/>
>     <clusternode name="cweb93.companions.com" nodeid="93" votes="1"/>
>     <clusternode name="cweb94.companions.com" nodeid="94" votes="1"/>
>     <clusternode name="dev.companions.com" nodeid="99" votes="1"/>
>     <clusternode name="qm247.companions.com" nodeid="247" votes="1"/>
>     <clusternode name="qm248.companions.com" nodeid="248" votes="1"/>
>     <clusternode name="qm249.companions.com" nodeid="249" votes="1"/>
>     <clusternode name="qm250.companions.com" nodeid="250" votes="1"/>
> </clusternodes>
>         <cman/>
> <fencedevices>
>     <fencedevice agent="fence_brocade" ipaddr="x.x.x.x" login="xxx" 
> name="brocade" passwd="xxx"/>
> </fencedevices>
>         <rm>
>                 <failoverdomains/>
>                 <resources/>
>         </rm>
> </cluster>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>   


-- 
--------------------------------------------------------------------------
Frank Hellmann          Optical Art GmbH           Waterloohain 7a
DI Supervisor           http://www.opticalart.de   22769 Hamburg
frank at opticalart.de     Tel: ++49 40 5111051       Fax: ++49 40 43169199 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20060913/a76a01b6/attachment.htm>


More information about the Linux-cluster mailing list