[Cluster-devel] cluster/cman/man cman_tool.8

[Cluster-devel] cluster/cman/man cman_tool.8

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-11-08 09:36:49

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Add an explanation of the node states shown by "cman_tool nodes" and some informastion about the "disallowed" state.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&r1=1.13&r2=1.14

--- cluster/cman/man/cman_tool.8	2007/09/19 15:59:46	1.13
+++ cluster/cman/man/cman_tool.8	2007/11/08 09:36:49	1.14
@@ -1,4 +1,4 @@
-.TH CMAN_TOOL 8 "Nov 23 2004" "Cluster utilities"
+.TH CMAN_TOOL 8 "Nov 8 2007" "Cluster utilities"
 
 .SH NAME
 cman_tool \- Cluster Management Tool
@@ -267,3 +267,69 @@
 .br
 16 Interaction with OpenAIS
 .br
+.SH NOTES
+.br
+the 
+.B nodes
+subcommand shows a list of nodes known to cman. the state is one of the following:
+.br
+M	The node is a member of the cluster
+.br
+X	The node is not a member of the cluster
+.br
+d	The node is known to the cluster but disallowed access to it.
+.br
+.SH DISALLOWED NODES
+Occasionally (but very infrequently I hope) you may see nodes marked as "Disallowed" in cman_tool status or "d" in cman_tool nodes.  This is a bit of a nasty hack to get around mismatch between what the upper layers expect of the cluster manager and OpenAIS.
+.TP
+If a node experiences a momentary lack of connectivity, but one that is long enough to trigger the token timeouts, then it will be removed from the cluster. When connectivity is restored OpenAIS will happily let it rejoin the cluster with no fuss. Sadly the upper layers don't like this very much. They may (indeed probably will have) have changed their internal state while the other node was away and there is no straightforward way to bring the rejoined node up-to-date with that state. When this happens the node is marked "Disallowed" and is not permitted to take part in cman operations.  
+.P
+If the remainder of the cluster is quorate the the node will be sent a kill message and it will be forced to leave the cluster that way. Note that fencing should kick in to remove the node permanently anyway, but it may take longer than the network outage for this to complete.
+
+If the remainder of the cluster is inquorate then we have a problem. The likelihood is that we will have two (or more) partitioned clusters and we cannot decide which is the "right" one. In this case we need to defer to the system administrator to kill an appropriate selection of nodes to restore the cluster to sensible operation.
+
+The latter scenario should be very rare and may indicate a bug somewhere in the code. If the local network is very flaky or busy it may be necessary to increase some of the protocol timeouts for OpenAIS. We are trying to think of better solutions to this problem.
+
+Recovering from this state can, unfortunately, be complicated. Fortunately, in the majority of cases, fencing will do the job for you, and the disallowed state will only be temporary. If it persists, the recommended approach it is to do a cman tool nodes on all systems in the cluster and determine the largest common subset of nodes that are valid members to each other. Then reboot the others and let them rejoin correctly. In the case of a single-node disconnection this should be straightforward, with a large cluster that has experienced a network partition it could get very complicated!
+
+Example:
+
+In this example we have a five node cluster that has experienced a network partition. Here is the output of cman_tool nodes from all systems:
+.nf
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   d   2372   2007-11-05 02:58:55  node-01.example.com
+   2   M   2376   2007-11-05 02:58:56  node-02.example.com
+   3   M   2376   2007-11-05 02:58:56  node-03.example.com
+   4   d   2376   2007-11-05 02:58:56  node-04.example.com
+   5   d   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   d   2372   2007-11-05 02:58:55  node-01.example.com
+   2   M   2376   2007-11-05 02:58:56  node-02.example.com
+   3   M   2376   2007-11-05 02:58:56  node-03.example.com
+   4   d   2376   2007-11-05 02:58:56  node-04.example.com
+   5   d   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+.fi
+In this scenario we should kill the node node-02 and node-03. Of course, the 3 node cluster of node-01, node-04 & node-05 should remain quorate and be able to fenced the two rejoined nodes anyway, but it is possible that the cluster has a qdisk setup that precludes this.
+

[Cluster-devel] cluster/cman/man cman_tool.8

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-11-08 09:39:10

Modified files:
	cman/man       : cman_tool.8 

Log message:
	add an explanation of the "cman_tool nodes" states and some detail about the
	"disallowed" state.
	bz#323931

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9.2.4&r2=1.9.2.5

--- cluster/cman/man/cman_tool.8	2007/10/12 18:53:57	1.9.2.4
+++ cluster/cman/man/cman_tool.8	2007/11/08 09:39:10	1.9.2.5
@@ -1,4 +1,4 @@
-.TH CMAN_TOOL 8 "Nov 23 2004" "Cluster utilities"
+.TH CMAN_TOOL 8 "Nov 8 2007" "Cluster utilities"
 
 .SH NAME
 cman_tool \- Cluster Management Tool
@@ -267,3 +267,69 @@
 .br
 16 Interaction with OpenAIS
 .br
+.SH NOTES
+.br
+the 
+.B nodes
+subcommand shows a list of nodes known to cman. the state is one of the following:
+.br
+M	The node is a member of the cluster
+.br
+X	The node is not a member of the cluster
+.br
+d	The node is known to the cluster but disallowed access to it.
+.br
+.SH DISALLOWED NODES
+Occasionally (but very infrequently I hope) you may see nodes marked as "Disallowed" in cman_tool status or "d" in cman_tool nodes.  This is a bit of a nasty hack to get around mismatch between what the upper layers expect of the cluster manager and OpenAIS.
+.TP
+If a node experiences a momentary lack of connectivity, but one that is long enough to trigger the token timeouts, then it will be removed from the cluster. When connectivity is restored OpenAIS will happily let it rejoin the cluster with no fuss. Sadly the upper layers don't like this very much. They may (indeed probably will have) have changed their internal state while the other node was away and there is no straightforward way to bring the rejoined node up-to-date with that state. When this happens the node is marked "Disallowed" and is not permitted to take part in cman operations.  
+.P
+If the remainder of the cluster is quorate the the node will be sent a kill message and it will be forced to leave the cluster that way. Note that fencing should kick in to remove the node permanently anyway, but it may take longer than the network outage for this to complete.
+
+If the remainder of the cluster is inquorate then we have a problem. The likelihood is that we will have two (or more) partitioned clusters and we cannot decide which is the "right" one. In this case we need to defer to the system administrator to kill an appropriate selection of nodes to restore the cluster to sensible operation.
+
+The latter scenario should be very rare and may indicate a bug somewhere in the code. If the local network is very flaky or busy it may be necessary to increase some of the protocol timeouts for OpenAIS. We are trying to think of better solutions to this problem.
+
+Recovering from this state can, unfortunately, be complicated. Fortunately, in the majority of cases, fencing will do the job for you, and the disallowed state will only be temporary. If it persists, the recommended approach it is to do a cman tool nodes on all systems in the cluster and determine the largest common subset of nodes that are valid members to each other. Then reboot the others and let them rejoin correctly. In the case of a single-node disconnection this should be straightforward, with a large cluster that has experienced a network partition it could get very complicated!
+
+Example:
+
+In this example we have a five node cluster that has experienced a network partition. Here is the output of cman_tool nodes from all systems:
+.nf
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   d   2372   2007-11-05 02:58:55  node-01.example.com
+   2   M   2376   2007-11-05 02:58:56  node-02.example.com
+   3   M   2376   2007-11-05 02:58:56  node-03.example.com
+   4   d   2376   2007-11-05 02:58:56  node-04.example.com
+   5   d   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   d   2372   2007-11-05 02:58:55  node-01.example.com
+   2   M   2376   2007-11-05 02:58:56  node-02.example.com
+   3   M   2376   2007-11-05 02:58:56  node-03.example.com
+   4   d   2376   2007-11-05 02:58:56  node-04.example.com
+   5   d   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+
+Node  Sts   Inc   Joined               Name
+   1   M   2372   2007-11-05 02:58:55  node-01.example.com
+   2   d   2376   2007-11-05 02:58:56  node-02.example.com
+   3   d   2376   2007-11-05 02:58:56  node-03.example.com
+   4   M   2376   2007-11-05 02:58:56  node-04.example.com
+   5   M   2376   2007-11-05 02:58:56  node-05.example.com
+.fi
+In this scenario we should kill the node node-02 and node-03. Of course, the 3 node cluster of node-01, node-04 & node-05 should remain quorate and be able to fenced the two rejoined nodes anyway, but it is possible that the cluster has a qdisk setup that precludes this.
+

[Cluster-devel] cluster/cman/man cman_tool.8

[rohara]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	rohara at sourceware.org	2007-10-12 18:53:57

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Update man page to explain 'cman_tool nodes' filter/format options.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9.2.3&r2=1.9.2.4

--- cluster/cman/man/cman_tool.8	2007/09/17 13:59:31	1.9.2.3
+++ cluster/cman/man/cman_tool.8	2007/10/12 18:53:57	1.9.2.4
@@ -242,7 +242,18 @@
 .TP
 .I -a
 Shows the IP address(es) the nodes are communicating on.
-
+.br
+.TP
+.I -n <nodename>
+Shows node information for a specific node. This should be the unqualified node
+name as it appears in 'cman_tool nodes'.
+.br
+.TP
+.I -F <format>
+Specify the format of the output. The format string may contain one or
+more format options, each seperated by a comma. Valid format options
+include: id, name, type, and addr.
+.br
 .SH "DEBUG" OPTIONS
 .TP
 .I -d <value>

[Cluster-devel] cluster/cman/man cman_tool.8

[rohara]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	rohara at sourceware.org	2007-10-12 18:16:30

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Update man page to explain 'cman_tool nodes' filter/format options.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.4.2.5&r2=1.4.2.6

--- cluster/cman/man/cman_tool.8	2007/09/25 20:10:12	1.4.2.5
+++ cluster/cman/man/cman_tool.8	2007/10/12 18:16:30	1.4.2.6
@@ -130,7 +130,6 @@
 Dictates the maximum amount of time cman_tool is prepared to wait. 
 If the operation times out then a status of 2 is returned.
 
-.br
 .SH "JOIN" OPTIONS
 .TP
 .I -X
@@ -219,6 +218,17 @@
 Note that just because cman_tool has given up, does not mean that cman itself
 has stopped trying to join a cluster.
 
+.SH "NODES" OPTIONS
+.TP
+.I -n <nodename>
+Shows node information for a specific node. This should be the unqualified node
+name as it appears in 'cman_tool nodes'.
+.TP
+.I -F <format>
+Specify the format of the output. The format string may contain one or
+more format options, each seperated by a comma. Valid format options
+include: id, name, type, and addr.
+
 .br
 .SH "SERVICES" OUTPUT
 

[Cluster-devel] cluster/cman/man cman_tool.8

[teigland]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	teigland at sourceware.org	2007-09-25 20:10:12

Modified files:
	cman/man       : cman_tool.8 

Log message:
	add some info about services output

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.4.2.4&r2=1.4.2.5

--- cluster/cman/man/cman_tool.8	2005/02/23 16:43:08	1.4.2.4
+++ cluster/cman/man/cman_tool.8	2007/09/25 20:10:12	1.4.2.5
@@ -218,3 +218,79 @@
 is prepared to wait. If the operation times out then a status of 2 is returned.
 Note that just because cman_tool has given up, does not mean that cman itself
 has stopped trying to join a cluster.
+
+.br
+.SH "SERVICES" OUTPUT
+
+Lists the gfs, dlm, fence and rgmanager (user) groups registered locally
+with cman.  Cman manages the membership of each group, and coordinates
+their recovery.  The group name, global ID, local ID, State and Code are
+shown for each group.  The nodeid's of the current group members are shown
+on the second line within "[ ... ]".
+
+The following details relate to the internal cman group states and can be
+useful for debugging.
+
+\fBGroup states\fP include:
+.TP 8
+.I run
+normal operation, no transition in progress
+.TP
+.I join
+local node is joining the group
+.TP
+.I update
+local node is adding/removing another node to/from the group
+.TP
+.I recover
+group is being recovered from the failure of a member
+
+
+.TP 0
+\fBRecovery codes\fP indicating the local state of recovery:
+
+.TP 2
+1
+STOP the group has been told to stop in preparation for a recovery
+.TP
+2
+START the group has been told to do recovery
+.TP
+3
+STARTDONE the group has finished recovery locally
+.TP
+4
+BARRIERWAIT the group has finished recovery locally and is waiting for
+remote nodes to finish their recovery, too
+.TP
+5
+BARRIERDONE recovery for the group has completed on all nodes, and all
+nodes have joined the completion barrier
+
+.TP 0
+\fBEvent codes\fP related to nodes joining and leaving the group.  There
+are two forms these codes can take:
+
+.TP 0
+S-se_state,se_flags,se_reply_count
+.TP 4
+"S" indicates that the local node is joining or leaving the group.
+.br
+se_state is the state of the sevent, see SEST_* in sm_internal.h.
+.br
+se_flags are flags in the sevent, see SEFL_* in sm_internal.h.
+.br
+se_reply_count is the number of ack's received for the sevent.
+
+.TP 0
+U-ue_state,ue_flags,ue_nodeid
+.TP 4
+"U" indicates that the local node is processing the join or leave of
+another node.
+.br
+ue_state is the state of the uevent, see UEST_* in sm_internal.h.
+.br
+ue_flags are flags in the uevent, see UEFL_* in sm_internal.h.
+.br
+ue_nodeid is the node whose join or leave the uevent relates to.
+

[Cluster-devel] cluster/cman/man cman_tool.8

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-09-17 13:59:32

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Document debug sub-command

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9.2.2&r2=1.9.2.3

--- cluster/cman/man/cman_tool.8	2007/08/22 13:41:44	1.9.2.2
+++ cluster/cman/man/cman_tool.8	2007/09/17 13:59:31	1.9.2.3
@@ -3,7 +3,7 @@
 .SH NAME
 cman_tool \- Cluster Management Tool
 .SH SYNOPSIS
-.B cman_tool join | leave | kill | expected | votes | version | wait | status | nodes | services [options]
+.B cman_tool join | leave | kill | expected | votes | version | wait | status | nodes | services | debug [options]
 .br
 .SH DESCRIPTION
 .PP
@@ -84,6 +84,14 @@
 Displays the local view of subsystems using cman (deprecated, group_tool
 should be used instead).
 
+.TP
+.I debug
+Sets the debug level of the running cman daemon. Debug output will be
+sent to syslog level LOG_DEBUG. the
+.B -d
+switch specifies the new logging level. This is the same bitmask used
+for cman_tool join -d
+.br
 .SH "LEAVE" OPTIONS
 .TP
 .I -w
@@ -235,3 +243,16 @@
 .I -a
 Shows the IP address(es) the nodes are communicating on.
 
+.SH "DEBUG" OPTIONS
+.TP
+.I -d <value>
+The value is a bitmask of
+.br 
+2 Barriers
+.br
+4 Membership messages
+.br
+8 Daemon operation, including command-line interaction
+.br
+16 Interaction with OpenAIS
+.br

[Cluster-devel] cluster/cman/man cman_tool.8

[teigland]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	teigland at sourceware.org	2007-08-22 13:41:44

Modified files:
	cman/man       : cman_tool.8 

Log message:
	mention group_tool shoud be used instead of cman_tool services

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9.2.1&r2=1.9.2.2

--- cluster/cman/man/cman_tool.8	2007/08/22 09:34:46	1.9.2.1
+++ cluster/cman/man/cman_tool.8	2007/08/22 13:41:44	1.9.2.2
@@ -35,8 +35,8 @@
 shutdown CLVM, fenced and anything else using the cluster manager before
 using 
 .B cman_tool leave.
-Look at 'cman_tool status|services' to see how many (and which) services are
-running.
+Look at 'cman_tool status' and group_tool to see how many (and which)
+subsystems are active.
 .br
 When a node leaves the cluster, the remaining nodes recalculate quorum and this
 may block cluster activity if the required number of votes is not present.
@@ -81,7 +81,8 @@
 
 .TP
 .I services
-Displays the local view of the cluster services.
+Displays the local view of subsystems using cman (deprecated, group_tool
+should be used instead).
 
 .SH "LEAVE" OPTIONS
 .TP

[Cluster-devel] cluster/cman/man cman_tool.8

[teigland]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2007-08-22 13:39:57

Modified files:
	cman/man       : cman_tool.8 

Log message:
	mention group_tool should be used instead of cman_tool services

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&r1=1.10&r2=1.11

--- cluster/cman/man/cman_tool.8	2007/08/22 09:34:16	1.10
+++ cluster/cman/man/cman_tool.8	2007/08/22 13:39:57	1.11
@@ -35,8 +35,8 @@
 shutdown CLVM, fenced and anything else using the cluster manager before
 using 
 .B cman_tool leave.
-Look at 'cman_tool status|services' to see how many (and which) services are
-running.
+Look at 'cman_tool status' and group_tool to see how many (and which)
+subsystems are active.
 .br
 When a node leaves the cluster, the remaining nodes recalculate quorum and this
 may block cluster activity if the required number of votes is not present.
@@ -81,7 +81,8 @@
 
 .TP
 .I services
-Displays the local view of the cluster services.
+Displays the local view of subsystems using cman (deprecated, group_tool
+should be used instead).
 
 .SH "LEAVE" OPTIONS
 .TP

[Cluster-devel] cluster/cman/man cman_tool.8

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-08-22 09:34:46

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Update man page for RHEL5

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9&r2=1.9.2.1

--- cluster/cman/man/cman_tool.8	2005/04/27 10:29:32	1.9
+++ cluster/cman/man/cman_tool.8	2007/08/22 09:34:46	1.9.2.1
@@ -120,8 +120,9 @@
 .SH "VERSION" OPTIONS
 .TP
 .I -r <config_version>
-The new config version.
-
+The new config version. You don't need to use this when adding a new node,
+the new cman node will tell the rest of the cluster to get their latest
+version of the config file from CCS automatically.
 .SH "WAIT" OPTIONS
 .TP
 .I -q
@@ -133,13 +134,6 @@
 .br
 .SH "JOIN" OPTIONS
 .TP
-.I -X
-Tells cman_tool to ignore CCS altogether. All of the information necessary
-to join the cluster must be provided on the command-line. Note that if
-you get this wrong, it is possible that the node will form a cluster on
-it's own and ignore a cluster it is supposed to be joining, so this method
-of invocation is not recommended.
-.TP
 .I -c <clustername>
 Provides a text name for the cluster. You can have several clusters on one
 LAN and they are distinguished by this name. Note that the name is hashed to 
@@ -149,7 +143,7 @@
 another name or use different port number for cluster communication.
 .TP
 .I -p <port>
-UDP port number used for cluster communication. This defaults to 6809.
+UDP port number used for cluster communication. This defaults to 5405.
 .TP
 .I -v <votes>
 Number of votes this node has in the cluster. Defaults to 1.
@@ -180,9 +174,8 @@
 .TP
 .I -N <nodeid>
 Overrides the node ID for this node. Normally, nodes are assigned a 
-node id by the cluster join mechanism. If you want to ensure that
-your nodes always have the same number regardless of the order in 
-which they join the cluster then you can hard-code these IDs. 
+node id in CCS. If you specify an incorrect node ID here, the
+node might not be allowed to join the cluster.
 .TP
 .I -o <nodename>
 Override the name this node will have in the cluster. This will
@@ -204,10 +197,6 @@
 is required for IPv6 operation. You should also specify an ethernet 
 interface to bind to this multicast address using the -i option.
 .TP
-.I -i <interface>
-Used in conjunction with -m above to specify the interface for
-multicast to use.
-.TP
 .I -w
 Join and wait until the node is a cluster member.
 .TP
@@ -222,8 +211,26 @@
 command without -w followed by
 .B cman_tool wait.
 .TP
+.I -k <keyfile>
+All traffic sent out by cman/openais is encrypted. By default the security key 
+used is simply the cluster name. If you need more security you can specify a
+key file that contains the key used to encrypt cluster communications.
+Of course, the contents of the key file must be the same on all nodes in the
+cluster. It is up to you to securely copy the file to the nodes.
+.TP
 .I -t <seconds>
 If -w or -q is also specified then -t dictates the maximum amount of time cman_tool
 is prepared to wait. If the operation times out then a status of 2 is returned.
 Note that just because cman_tool has given up, does not mean that cman itself
 has stopped trying to join a cluster.
+.br
+.SH "NODES" OPTIONS
+.TP
+.I -f
+Shows the date/time the node was last fenced (if it has bee fenced), and also
+the fence system that was used.
+.br
+.TP
+.I -a
+Shows the IP address(es) the nodes are communicating on.
+

[Cluster-devel] cluster/cman/man cman_tool.8

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-08-22 09:34:16

Modified files:
	cman/man       : cman_tool.8 

Log message:
	Update man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&r1=1.9&r2=1.10

--- cluster/cman/man/cman_tool.8	2005/04/27 10:29:32	1.9
+++ cluster/cman/man/cman_tool.8	2007/08/22 09:34:16	1.10
@@ -120,8 +120,9 @@
 .SH "VERSION" OPTIONS
 .TP
 .I -r <config_version>
-The new config version.
-
+The new config version. You don't need to use this when adding a new node,
+the new cman node will tell the rest of the cluster to get their latest
+version of the config file from CCS automatically.
 .SH "WAIT" OPTIONS
 .TP
 .I -q
@@ -133,13 +134,6 @@
 .br
 .SH "JOIN" OPTIONS
 .TP
-.I -X
-Tells cman_tool to ignore CCS altogether. All of the information necessary
-to join the cluster must be provided on the command-line. Note that if
-you get this wrong, it is possible that the node will form a cluster on
-it's own and ignore a cluster it is supposed to be joining, so this method
-of invocation is not recommended.
-.TP
 .I -c <clustername>
 Provides a text name for the cluster. You can have several clusters on one
 LAN and they are distinguished by this name. Note that the name is hashed to 
@@ -149,7 +143,7 @@
 another name or use different port number for cluster communication.
 .TP
 .I -p <port>
-UDP port number used for cluster communication. This defaults to 6809.
+UDP port number used for cluster communication. This defaults to 5405.
 .TP
 .I -v <votes>
 Number of votes this node has in the cluster. Defaults to 1.
@@ -180,9 +174,8 @@
 .TP
 .I -N <nodeid>
 Overrides the node ID for this node. Normally, nodes are assigned a 
-node id by the cluster join mechanism. If you want to ensure that
-your nodes always have the same number regardless of the order in 
-which they join the cluster then you can hard-code these IDs. 
+node id in CCS. If you specify an incorrect node ID here, the
+node might not be allowed to join the cluster.
 .TP
 .I -o <nodename>
 Override the name this node will have in the cluster. This will
@@ -204,10 +197,6 @@
 is required for IPv6 operation. You should also specify an ethernet 
 interface to bind to this multicast address using the -i option.
 .TP
-.I -i <interface>
-Used in conjunction with -m above to specify the interface for
-multicast to use.
-.TP
 .I -w
 Join and wait until the node is a cluster member.
 .TP
@@ -222,8 +211,26 @@
 command without -w followed by
 .B cman_tool wait.
 .TP
+.I -k <keyfile>
+All traffic sent out by cman/openais is encrypted. By default the security key 
+used is simply the cluster name. If you need more security you can specify a
+key file that contains the key used to encrypt cluster communications.
+Of course, the contents of the key file must be the same on all nodes in the
+cluster. It is up to you to securely copy the file to the nodes.
+.TP
 .I -t <seconds>
 If -w or -q is also specified then -t dictates the maximum amount of time cman_tool
 is prepared to wait. If the operation times out then a status of 2 is returned.
 Note that just because cman_tool has given up, does not mean that cman itself
 has stopped trying to join a cluster.
+.br
+.SH "NODES" OPTIONS
+.TP
+.I -f
+Shows the date/time the node was last fenced (if it has bee fenced), and also
+the fence system that was used.
+.br
+.TP
+.I -a
+Shows the IP address(es) the nodes are communicating on.
+