[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] configuring bladecenter fence device



To address:

As per my understanding, IP address is IP address of management module
of IBM blade center, login/password represent credentials to access
the same.

>> Correct.

However did not get the parameter 'Blade'. How does it play role in
fencing?

>> If I recall correctly the blade= is the identifier used to identify the blade in the AMM.  I can't remember if it is a number of a slot or a user defined name.  It corresponds to 

# fence_bladecenter -h 

   -n, --plug=<id>                Physical plug number on device or
                                        name of virtual machine
If the fencing code:

        "port" : {
                "getopt" : "n:",
                "longopt" : "plug",
                "help" : "-n, --plug=<id>                Physical plug number on device or\n" + 
                "                                        name of virtual machine",
                "required" : "1",
                "shortdesc" : "Physical plug number or name of virtual machine",
                "order" : 1 },

To test this try running:

/sbin/fence_bladecenter -a <ip or hostname of bladecenter> -l <login> -p <passwd> -n <blade number of the blade you want to fence> -o status -v

An example cluster.conf looks like:

                <clusternode name="node1" votes="1">
                        <fence>
                                <method name="1">
                                        <device blade="2" name="chassis_fence"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="node2" votes="1">
                        <fence>
                                <method name="1">
                                        <device blade="3" name="chassis_fence"/>
                                </method>
                        </fence>

       <fencedevices>
                <fencedevice agent="fence_bladecenter" ipaddr="XXX.XXX.1.143" login="rchs_fence" name="chassis_fence" 
passwd="XXXXXXX"/>
        </fencedevices>

-Ben




----- Original Message -----
> Hi all,
> 
> >From RHCS documentation, I could see that bladecenter is one of the
> fence devices -
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/ap-fence-device-param-CA.html
> 
> Table B.9. IBM Blade Center
> Field Description
> Name A name for the IBM BladeCenter device connected to the cluster.
> IP Address The IP address assigned to the device.
> Login The login name used to access the device.
> Password The password used to authenticate the connection to the
> device.
> Password Script (optional) The script that supplies a password for
> access to the fence device. Using this supersedes the Password
> parameter.
> Blade The blade of the device.
> Use SSH (Rhel 5.4 and later) Indicates that system will use SSH to
> access the device.
> 
> As per my understanding, IP address is IP address of management module
> of IBM blade center, login/password represent credentials to access
> the same.
> 
> However did not get the parameter 'Blade'. How does it play role in
> fencing?
> 
> In a situation where there are two blades - Blade-1 and Blade-2 and
> if Blade-1 goes down(hardware node failure), Blade-2 should fence out
> Blade-1, in that situation fenced on Blade-2 should power off(?)
> blade-2 using fence_bladecenter, so how should below sniplet of
> cluster.conf file should look like? -
> 
> 
> <clusternodes>
> <clusternode name="blade1" nodeid="1" votes="1">
> <fence>
> <method name="1">
> <device blade="?????"
> name="BLADECENTER"/>
> </method>
> </fence>
> </clusternode>
> <clusternode name="blade2" nodeid="2" votes="1">
> <fence>
> <method name="1">
> <device blade="????"
> name="BLADECENTER"/>
> </method>
> </fence>
> </clusternode>
> </clusternodes>
> 
> In which situation fence_bladecenter would be used to power on the
> blade?
> 
> Your gratefully
> 
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]