All of lore.kernel.org
 help / color / mirror / Atom feed
From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man cman_tool.8
Date: 22 Aug 2007 09:34:46 -0000	[thread overview]
Message-ID: <20070822093446.22165.qmail@sourceware.org> (raw)

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.
+



             reply	other threads:[~2007-08-22  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  9:34 pcaulfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-08  9:39 [Cluster-devel] cluster/cman/man cman_tool.8 pcaulfield
2007-11-08  9:36 pcaulfield
2007-10-12 18:53 rohara
2007-10-12 18:16 rohara
2007-09-25 20:10 teigland
2007-09-17 13:59 pcaulfield
2007-08-22 13:41 teigland
2007-08-22 13:39 teigland
2007-08-22  9:34 pcaulfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070822093446.22165.qmail@sourceware.org \
    --to=pcaulfield@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.