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

Re: [Linux-cluster] two fencing problems


I'm using the fence_apc agent on my cluster with APC 7900s, and fencing
is working perfectly for me, and has for more than 6 months now.

Only thing I had to do was modify the fence_apc agent to allow for the
renamed ports I setup (got rid of the outlet X names, and put in
descriptive server names) and add in the port groups feature I'm using.
One of these days I'll get a few spare minutes to whip up a correct
patch to the agent that can be submitted to the tree.  One that will
work in both the "Outlet X" naming method, and the descriptive port

My device entry inside of fence for a node looks like this:
<device name="AUHAPC01" port="AUHJPSN01A" switch="0"/>

You can test that the cluster is configured correctly to fence a node by
running "fence_node <nodename>"  This will use the cluster's config file
to fence the node, ensuring that all config settings are correct.

> once I remembered to turn off ccsd 
> before updating my cluster.conf by hand so that it didn't end up 
> replacing it with the old one immediately ;-)
When updating the cluster.conf file by hand, you are updating the
config_version attribute of the cluster node, right?  I do updates to my
cluster.conf file by hand pretty much exclusively, while the cluster is
running, and with no problems whatsoever.  Changes propagate as expected
after running "ccs_tool update <cluster.conf filename>"and "cman_tool
version -r <new_version_number>"

Eric Kerin
eric bootseg com

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