[Linux-cluster] [Q] Good documentation about command line interface??

[Hiroyuki Sato]

Dear members.

I'm newbie Red Hat cluster.

Could you point me to good documentation about command line interface??
 ( cman_tool, css_tool, ccs_test, fence_ack_manual ..)

Especially the following topics.

  * How to rejoin to node.
  * How to leave from node.
  * How to use fence_ack_manual
  * How to manage cluster with command line tools.

One of my problem is here.

The status of gfs3 which in my test cluster is JOIN_STOP_WAIT.
I don't know how to re-join it.

# /usr/sbin/cman_tool services
type             level name     id       state
fence            0     default  00000000 JOIN_STOP_WAIT

I found a keyword 'fenced_override'. This file. should be named pipe.
Howevre I can't find that file in /var/run/cluter directory in my clusters.
fenced working on all of clusters.

Sincerely.


* Environment

  CentOS 5.6


* Configurations

<?xml version="1.0"?>
<cluster name="arch_gfs1" config_version="21">
  <cman expected_votes="1">
  </cman>
  <clusternodes>
    <clusternode name="gfs1.doma.in" votes="1" nodeid="5">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs1.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs2.doma.in" votes="1" nodeid="6">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs2.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs3.doma.in" votes="1" nodeid="7">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs3.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client1.doma.in" votes="1" nodeid="21">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client1.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client2.doma.in" votes="1" nodeid="22">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client2.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client3.doma.in" votes="1" nodeid="23">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client3.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client4.doma.in" votes="1" nodeid="24">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client4.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client5.doma.in" votes="1" nodeid="25">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client5.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client6.doma.in" votes="1" nodeid="26">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client6.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client7.doma.in" votes="1" nodeid="27">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client7.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client8.doma.in" votes="1" nodeid="28">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client8.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client9.doma.in" votes="1" nodeid="29">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client9.doma.in"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="gfs_client10.doma.in" votes="1" nodeid="30">
      <fence>
        <method name="single">
          <device name="manual" nodename="gfs_client10.doma.in"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <fencedevices>
    <fencedevice name="manual" agent="fence_manual"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
  </rm>
</cluster>


-- 
Hiroyuki Sato