[Cluster-devel] cluster/cman/man cman.5

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-08-22 08:35:55

Modified files:
	cman/man       : cman.5 

Log message:
	Update man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&r1=1.6&r2=1.7

--- cluster/cman/man/cman.5	2005/02/14 03:53:51	1.6
+++ cluster/cman/man/cman.5	2007/08/22 08:35:54	1.7
@@ -1,5 +1,5 @@
 .\"
-.\"  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
+.\"  Copyright (C) 2004-2007 Red Hat, Inc.  All rights reserved.
 
 .\" groff -t -e -mandoc -Tlatin1 cman.5 | less
 
@@ -23,11 +23,14 @@
 
 \fIUDP port\fR
 .in +7
-By default, cman will use UDP port 6809 for internode communication.  This can
+By default, cman will use UDP port 5405/5404 for internode communication.  This can
 be changed by setting a port number as follows:
 
   <cman port="6809">
   </cman>
+
+This will cause cman to use ports 6809 and 6808 for cluster communications.
+
 .in -7
 
 
@@ -35,7 +38,7 @@
 .in +7
 The expected votes value is used by cman to determine quorum.  The cluster is
 quorate if the sum of votes of existing members is over half of the expected
-votes value.  By default, cman_tool sets the expected votes value to be the sum
+votes value.  By default, cman sets the expected votes value to be the sum
 of votes of all nodes listed in cluster.conf.  This can be overriden by setting
 an explicit expected_votes value as follows:
 
@@ -76,9 +79,8 @@
 \fINode ID\fR
 .in +7
 
-By default, a node is assigned a nodeid by the cluster manager (cman) when
-it joins the cluster.  This can be overriden by specifying a nodeid here.
-Using this option will ensure that a given node always has the same ID.
+All nodes must have a unique node ID. This is a single integer that identifies
+it to the cluster.
 A node's application to join the cluster may be rejected if you try to set
 the nodeid to one that is already used.
 
@@ -89,22 +91,53 @@
 
 \fIMulticast network configuration\fR
 .in +7
-Cman can be configured to use multicast instead of broadcast (broadcast is used
-by default if no multicast parameters are given.)  To configure multicast add
-one line under the <cman> section and another under the <clusternode> section:
+cman uses multicast UDP packets to communicate with other nodes in the cluster.
+By default it will generate a multicast address using 239.192.x.x where x.x is
+the 16bit cluster ID number split into bytes. This, in turn is generated from a 
+hash of the cluster name though it can be specified explicitly. The purpose 
+of this is to allow multiple clusters to share the same subnet - they will each 
+use a different multicast address. You might also/instead want to isolate 
+clusters using the port number as shown above.
+
+It is possible to override the multicast address by specifying it in cluster.conf
+as shown:
 
   <cman>
-      <multicast addr="224.0.0.1"/>
+      <multicast addr="229.192.0.1"/>
   </cman>
 
-  <clusternode name="nd1">
-      <multicast addr="224.0.0.1" interface="eth0"/>
-  </clusternode>
+.in -7
+
+\fICluster ID\fR
+.in +7
+The cluster ID number is used to isolate clusters in the same subnet. Usually it
+is generated from a hash of the cluster name, but it can be overridden here if
+you feel the need. Sometimes cluster names can hash to the same ID.
+
+  <cman>
+      <cluster_id="669"/>
+  </cman>
 
-The multicast addresses must match and the address must be usable on the
-interface name given for the node.
 .in -7
 
+\fIOpenAIS Security key\fR
+.in +7
+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.
+
+  <cman>
+      <keyfile="/etc/openais.key"/>
+  </cman>
+
+Note that this only applies to cluster communication. The DLM does not encrypt 
+traffic.
+
+.in -7
+
+
 
 .sp
 .in -7

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

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

Modified files:
	cman/man       : cman.5 

Log message:
	Update man page for RHEL5

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6&r2=1.6.2.1

--- cluster/cman/man/cman.5	2005/02/14 03:53:51	1.6
+++ cluster/cman/man/cman.5	2007/08/22 08:36:57	1.6.2.1
@@ -1,5 +1,5 @@
 .\"
-.\"  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
+.\"  Copyright (C) 2004-2007 Red Hat, Inc.  All rights reserved.
 
 .\" groff -t -e -mandoc -Tlatin1 cman.5 | less
 
@@ -23,11 +23,14 @@
 
 \fIUDP port\fR
 .in +7
-By default, cman will use UDP port 6809 for internode communication.  This can
+By default, cman will use UDP port 5405/5404 for internode communication.  This can
 be changed by setting a port number as follows:
 
   <cman port="6809">
   </cman>
+
+This will cause cman to use ports 6809 and 6808 for cluster communications.
+
 .in -7
 
 
@@ -35,7 +38,7 @@
 .in +7
 The expected votes value is used by cman to determine quorum.  The cluster is
 quorate if the sum of votes of existing members is over half of the expected
-votes value.  By default, cman_tool sets the expected votes value to be the sum
+votes value.  By default, cman sets the expected votes value to be the sum
 of votes of all nodes listed in cluster.conf.  This can be overriden by setting
 an explicit expected_votes value as follows:
 
@@ -76,9 +79,8 @@
 \fINode ID\fR
 .in +7
 
-By default, a node is assigned a nodeid by the cluster manager (cman) when
-it joins the cluster.  This can be overriden by specifying a nodeid here.
-Using this option will ensure that a given node always has the same ID.
+All nodes must have a unique node ID. This is a single integer that identifies
+it to the cluster.
 A node's application to join the cluster may be rejected if you try to set
 the nodeid to one that is already used.
 
@@ -89,22 +91,53 @@
 
 \fIMulticast network configuration\fR
 .in +7
-Cman can be configured to use multicast instead of broadcast (broadcast is used
-by default if no multicast parameters are given.)  To configure multicast add
-one line under the <cman> section and another under the <clusternode> section:
+cman uses multicast UDP packets to communicate with other nodes in the cluster.
+By default it will generate a multicast address using 239.192.x.x where x.x is
+the 16bit cluster ID number split into bytes. This, in turn is generated from a 
+hash of the cluster name though it can be specified explicitly. The purpose 
+of this is to allow multiple clusters to share the same subnet - they will each 
+use a different multicast address. You might also/instead want to isolate 
+clusters using the port number as shown above.
+
+It is possible to override the multicast address by specifying it in cluster.conf
+as shown:
 
   <cman>
-      <multicast addr="224.0.0.1"/>
+      <multicast addr="229.192.0.1"/>
   </cman>
 
-  <clusternode name="nd1">
-      <multicast addr="224.0.0.1" interface="eth0"/>
-  </clusternode>
+.in -7
+
+\fICluster ID\fR
+.in +7
+The cluster ID number is used to isolate clusters in the same subnet. Usually it
+is generated from a hash of the cluster name, but it can be overridden here if
+you feel the need. Sometimes cluster names can hash to the same ID.
+
+  <cman>
+      <cluster_id="669"/>
+  </cman>
 
-The multicast addresses must match and the address must be usable on the
-interface name given for the node.
 .in -7
 
+\fIOpenAIS Security key\fR
+.in +7
+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.
+
+  <cman>
+      <keyfile="/etc/openais.key"/>
+  </cman>
+
+Note that this only applies to cluster communication. The DLM does not encrypt 
+traffic.
+
+.in -7
+
+
 
 .sp
 .in -7

[Cluster-devel] cluster/cman/man cman.5

[teigland]

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

Modified files:
	cman/man       : cman.5 

Log message:
	fix attribute xml format for cluster_id and keyfile

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&r1=1.7&r2=1.8

--- cluster/cman/man/cman.5	2007/08/22 08:35:54	1.7
+++ cluster/cman/man/cman.5	2007/08/22 15:13:11	1.8
@@ -114,8 +114,7 @@
 is generated from a hash of the cluster name, but it can be overridden here if
 you feel the need. Sometimes cluster names can hash to the same ID.
 
-  <cman>
-      <cluster_id="669"/>
+  <cman cluster_id="669">
   </cman>
 
 .in -7
@@ -128,8 +127,7 @@
 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.
 
-  <cman>
-      <keyfile="/etc/openais.key"/>
+  <cman keyfile="/etc/openais.key">
   </cman>
 
 Note that this only applies to cluster communication. The DLM does not encrypt 

[Cluster-devel] cluster/cman/man cman.5

[teigland]

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

Modified files:
	cman/man       : cman.5 

Log message:
	fix attribute xml format for cluster_id and keyfile

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6.2.1&r2=1.6.2.2

--- cluster/cman/man/cman.5	2007/08/22 08:36:57	1.6.2.1
+++ cluster/cman/man/cman.5	2007/08/22 15:13:37	1.6.2.2
@@ -114,8 +114,7 @@
 is generated from a hash of the cluster name, but it can be overridden here if
 you feel the need. Sometimes cluster names can hash to the same ID.
 
-  <cman>
-      <cluster_id="669"/>
+  <cman cluster_id="669">
   </cman>
 
 .in -7
@@ -128,8 +127,7 @@
 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.
 
-  <cman>
-      <keyfile="/etc/openais.key"/>
+  <cman keyfile="/etc/openais.key">
   </cman>
 
 Note that this only applies to cluster communication. The DLM does not encrypt 

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-08-22 15:13:58

Modified files:
	cman/man       : cman.5 

Log message:
	Add some information about setting up multi-home (redundant ring)

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

--- cluster/cman/man/cman.5	2007/08/22 15:13:11	1.8
+++ cluster/cman/man/cman.5	2007/08/22 15:13:58	1.9
@@ -86,6 +86,27 @@
 
   <clusternode name="nd1" nodeid="1">
   </clusternode>
+
+.in -7
+\fIMulti-home configuration\fR
+.in +7
+It is quite common to use multiple ethernet adaptors for cluster nodes, so
+they will tolerate the failure of one link. A common way to do this is to use
+ethernet bonding. Alternatively you can get openais to run in redundant ring
+mode by specifying an 'altname' for the node. This is an alternative name by
+which the node is known, that resolves to another IP address used on the 
+other ethernet adaptor(s). You can optionally specify a different port and/or 
+multicast address for each altname in use. Up to 9 altnames (10 interfaces 
+in total) can be used.
+
+Note that if you are using the DLM with cman/openais then you MUST tell it 
+to use SCTP as it's communications protocol as TCP does not support multihoming.
+
+  <clusternode name="nd1" nodeid="1"> 
+     <altname name="nd1a" port="6809" mcast="229.192.0.2"/>
+  </clusternode>
+
+  <dlm protocol="sctp"/>
 .in -7
 
 

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-08-22 15:43:55

Modified files:
	cman/man       : cman.5 

Log message:
	Add some info about openais.conf parameters

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

--- cluster/cman/man/cman.5	2007/08/22 15:13:58	1.9
+++ cluster/cman/man/cman.5	2007/08/22 15:43:55	1.10
@@ -153,14 +153,51 @@
 
 Note that this only applies to cluster communication. The DLM does not encrypt 
 traffic.
-
 .in -7
 
 
+\fIOther OpenAIS parameters\fR
+.in +7
+In addition to the cman-specific sections, cman also loads in configuration for openAIS from CCS from the following keys:
+
+<totem>
+<logging>
+<event>
+<aisexec>
+<group>
+
+See the 
+.B openais.conf(5)
+man page for more information on keys that are valid for these sections. 
+Note that the <clusternodes> section will overwrite things in these sections 
+and options on the cman_tool command line will override both. 
+In particular setting things like bindnetaddr, mcastaddr, mcastport & 
+nodeid in this section will always be replaced by the values in <clusternodes>.
+
+cman does not use the openais.conf file at all. What it does do is 
+load the values from CCS into internal OpenAIS data structures that 
+map onto the entries to openais.conf. So that's why you can add an 
+entry in a <totem> section in CCS and it will be used by totem.
+
+Here's how to increase the token timeout to five seconds:
+
+  <totem token="5000"/>
+
+And this is how to add extra AIS logging options to cman & CPG:
+
+  <logging to_stderr="yes">
+    <logger ident="CPG" debug="on" to_stderr="yes">
+    </logger>
+    <logger ident="CMAN" debug="on" to_stderr="yes">
+    </logger>
+  </logging>
+
+.in -7
+
 
 .sp
 .in -7
 \fBSEE ALSO\fP
 .in +7
-cluster.conf(5), ccs(7), cman_tool(8)
+cluster.conf(5), openais.conf(5), ccs(7), cman_tool(8)
 

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-08-22 15:48:03

Modified files:
	cman/man       : cman.5 

Log message:
	Add openais.conf information to man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6.2.2&r2=1.6.2.3

--- cluster/cman/man/cman.5	2007/08/22 15:13:37	1.6.2.2
+++ cluster/cman/man/cman.5	2007/08/22 15:48:03	1.6.2.3
@@ -136,10 +136,49 @@
 .in -7
 
 
+\fIOther OpenAIS parameters\fR
+.in +7
+In addition to the cman-specific sections, cman also loads in configuration for openAIS from CCS from the following keys:
+
+<totem>
+<logging>
+<event>
+<aisexec>
+<group>
+
+See the 
+.B openais.conf(5)
+man page for more information on keys that are valid for these sections. 
+Note that the <clusternodes> section will overwrite things in these sections 
+and options on the cman_tool command line will override both. 
+In particular setting things like bindnetaddr, mcastaddr, mcastport & 
+nodeid in this section will always be replaced by the values in <clusternodes>.
+
+cman does not use the openais.conf file at all. What it does do is 
+load the values from CCS into internal OpenAIS data structures that 
+map onto the entries to openais.conf. So that's why you can add an 
+entry in a <totem> section in CCS and it will be used by totem.
+
+Here's how to increase the token timeout to five seconds:
+
+  <totem token="5000"/>
+
+And this is how to add extra AIS logging options to cman & CPG:
+
+  <logging to_stderr="yes">
+    <logger ident="CPG" debug="on" to_stderr="yes">
+    </logger>
+    <logger ident="CMAN" debug="on" to_stderr="yes">
+    </logger>
+  </logging>
+
+.in -7
+
+
 
 .sp
 .in -7
 \fBSEE ALSO\fP
 .in +7
-cluster.conf(5), ccs(7), cman_tool(8)
+cluster.conf(5), openais.conf(5), ccs(7), cman_tool(8)
 

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	pcaulfield at sourceware.org	2007-08-23 08:42:07

Modified files:
	cman/man       : cman.5 

Log message:
	Mention the openais.conf parameters that cman overrides.

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

--- cluster/cman/man/cman.5	2007/08/22 15:43:55	1.10
+++ cluster/cman/man/cman.5	2007/08/23 08:42:06	1.11
@@ -174,6 +174,22 @@
 In particular setting things like bindnetaddr, mcastaddr, mcastport & 
 nodeid in this section will always be replaced by the values in <clusternodes>.
 
+Several openais.conf items are overridden by cman by default. You can still change
+these in cluster.conf but the defaults are different from those documented in
+the openais.conf(5) man page. They are:
+
+  <totem
+   vsftype="none"
+   token="10000"
+   token_retransmits_before_loss_const="20"
+   join="60"
+   consensus="4800"
+   rrp_mode="none"
+   <!-- or rrp_mode="active" if altnames are present >
+   />
+   <logging syslog_facility="local4" />
+   <aisexec user="root" group="root" />
+
 cman does not use the openais.conf file at all. What it does do is 
 load the values from CCS into internal OpenAIS data structures that 
 map onto the entries to openais.conf. So that's why you can add an 

[Cluster-devel] cluster/cman/man cman.5

[pcaulfield]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	pcaulfield at sourceware.org	2007-08-23 08:43:29

Modified files:
	cman/man       : cman.5 

Log message:
	Mention the openais.conf parameters that cman overrides.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6.2.3&r2=1.6.2.4

--- cluster/cman/man/cman.5	2007/08/22 15:48:03	1.6.2.3
+++ cluster/cman/man/cman.5	2007/08/23 08:43:29	1.6.2.4
@@ -154,6 +154,22 @@
 In particular setting things like bindnetaddr, mcastaddr, mcastport & 
 nodeid in this section will always be replaced by the values in <clusternodes>.
 
+Several openais.conf items are overridden by cman by default. You can still change
+these in cluster.conf but the defaults are different from those documented in
+the openais.conf(5) man page. They are:
+
+  <totem
+   vsftype="none"
+   token="10000"
+   token_retransmits_before_loss_const="20"
+   join="60"
+   consensus="4800"
+   rrp_mode="none"
+   <!-- or rrp_mode="active" if altnames are present >
+   />
+   <logging syslog_facility="local4" />
+   <aisexec user="root" group="root" />
+
 cman does not use the openais.conf file at all. What it does do is 
 load the values from CCS into internal OpenAIS data structures that 
 map onto the entries to openais.conf. So that's why you can add an 

[Cluster-devel] cluster/cman/man cman.5

[teigland]

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2007-08-23 14:37:35

Modified files:
	cman/man       : cman.5 

Log message:
	rewording and embellishing some bits related to openais.conf

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

--- cluster/cman/man/cman.5	2007/08/23 08:42:06	1.11
+++ cluster/cman/man/cman.5	2007/08/23 14:37:35	1.12
@@ -17,7 +17,14 @@
 Cman configuration values are placed in the <cman> </cman> section of
 \fBcluster.conf\fP.  Per-node configuration related to cman is placed
 in the standard <clusternode> </clusternode> sections.  All cman
-configuration settings are optional; usually none are used.
+configuration settings are optional; usually none are used.  The <cman>
+section is placed under the <cluster> section in cluster.conf.
+
+  <cluster>
+    <cman>
+    </cman>
+    ...
+  </cluster>
 .in -7
 
 
@@ -140,7 +147,7 @@
 
 .in -7
 
-\fIOpenAIS Security key\fR
+\fIopenais security key\fR
 .in +7
 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
@@ -156,50 +163,52 @@
 .in -7
 
 
-\fIOther OpenAIS parameters\fR
+\fIOther openais parameters\fR
 .in +7
-In addition to the cman-specific sections, cman also loads in configuration for openAIS from CCS from the following keys:
-
-<totem>
-<logging>
-<event>
-<aisexec>
-<group>
+When openais is started by cman (cman_tool runs aisexec), the openais.conf
+file is not used.  Many of the configuration parameters listed in
+openais.conf can be set in cluster.conf (CCS) instead.  Cman will read
+openais parameters from the following sections in cluster.conf and load
+them into openais:
+
+  <cluster>
+    <totem />
+    <logging />
+    <event />
+    <aisexec />
+    <group />
+  </cluster>
 
 See the 
 .B openais.conf(5)
-man page for more information on keys that are valid for these sections. 
-Note that the <clusternodes> section will overwrite things in these sections 
-and options on the cman_tool command line will override both. 
-In particular setting things like bindnetaddr, mcastaddr, mcastport & 
-nodeid in this section will always be replaced by the values in <clusternodes>.
-
-Several openais.conf items are overridden by cman by default. You can still change
-these in cluster.conf but the defaults are different from those documented in
-the openais.conf(5) man page. They are:
+man page for more information on keys that are valid for these sections.
+Note that settings in the <clusternodes> section will override settings in
+the sections above, and options on the cman_tool command line will
+override both.  In particular, settings like bindnetaddr, mcastaddr,
+mcastport and nodeid will always be replaced by values in <clusternodes>.
+
+Cman uses different defaults for some of the openais parameters listed in
+openais.conf(5).  If you wish to use a non-default setting, they can be
+configured in cluster.conf as shown above.  Cman uses the following
+default values:
 
   <totem
-   vsftype="none"
-   token="10000"
-   token_retransmits_before_loss_const="20"
-   join="60"
-   consensus="4800"
-   rrp_mode="none"
-   <!-- or rrp_mode="active" if altnames are present >
-   />
-   <logging syslog_facility="local4" />
-   <aisexec user="root" group="root" />
-
-cman does not use the openais.conf file at all. What it does do is 
-load the values from CCS into internal OpenAIS data structures that 
-map onto the entries to openais.conf. So that's why you can add an 
-entry in a <totem> section in CCS and it will be used by totem.
+    vsftype="none"
+    token="10000"
+    token_retransmits_before_loss_const="20"
+    join="60"
+    consensus="4800"
+    rrp_mode="none"
+    <!-- or rrp_mode="active" if altnames are present >
+  />
+  <logging syslog_facility="local4" />
+  <aisexec user="root" group="root" />
 
-Here's how to increase the token timeout to five seconds:
+Here's how to set the token timeout to five seconds:
 
   <totem token="5000"/>
 
-And this is how to add extra AIS logging options to cman & CPG:
+And this is how to add extra openais logging options to CMAN and CPG:
 
   <logging to_stderr="yes">
     <logger ident="CPG" debug="on" to_stderr="yes">

[Cluster-devel] cluster/cman/man cman.5

[teigland]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	teigland at sourceware.org	2007-08-23 14:40:33

Modified files:
	cman/man       : cman.5 

Log message:
	rewording and embellishing some bits related to openais.conf

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.6.2.4&r2=1.6.2.5

--- cluster/cman/man/cman.5	2007/08/23 08:43:29	1.6.2.4
+++ cluster/cman/man/cman.5	2007/08/23 14:40:33	1.6.2.5
@@ -17,7 +17,14 @@
 Cman configuration values are placed in the <cman> </cman> section of
 \fBcluster.conf\fP.  Per-node configuration related to cman is placed
 in the standard <clusternode> </clusternode> sections.  All cman
-configuration settings are optional; usually none are used.
+configuration settings are optional; usually none are used.  The <cman>
+section is placed under the <cluster> section in cluster.conf.
+
+  <cluster>
+    <cman>
+    </cman>
+    ...
+  </cluster>
 .in -7
 
 
@@ -119,7 +126,7 @@
 
 .in -7
 
-\fIOpenAIS Security key\fR
+\fIopenais security key\fR
 .in +7
 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
@@ -132,54 +139,55 @@
 
 Note that this only applies to cluster communication. The DLM does not encrypt 
 traffic.
-
 .in -7
 
 
-\fIOther OpenAIS parameters\fR
+\fIOther openais parameters\fR
 .in +7
-In addition to the cman-specific sections, cman also loads in configuration for openAIS from CCS from the following keys:
-
-<totem>
-<logging>
-<event>
-<aisexec>
-<group>
+When openais is started by cman (cman_tool runs aisexec), the openais.conf
+file is not used.  Many of the configuration parameters listed in
+openais.conf can be set in cluster.conf (CCS) instead.  Cman will read
+openais parameters from the following sections in cluster.conf and load
+them into openais:
+
+  <cluster>
+    <totem />
+    <logging />
+    <event />
+    <aisexec />
+    <group />
+  </cluster>
 
 See the 
 .B openais.conf(5)
-man page for more information on keys that are valid for these sections. 
-Note that the <clusternodes> section will overwrite things in these sections 
-and options on the cman_tool command line will override both. 
-In particular setting things like bindnetaddr, mcastaddr, mcastport & 
-nodeid in this section will always be replaced by the values in <clusternodes>.
-
-Several openais.conf items are overridden by cman by default. You can still change
-these in cluster.conf but the defaults are different from those documented in
-the openais.conf(5) man page. They are:
+man page for more information on keys that are valid for these sections.
+Note that settings in the <clusternodes> section will override settings in
+the sections above, and options on the cman_tool command line will
+override both.  In particular, settings like bindnetaddr, mcastaddr,
+mcastport and nodeid will always be replaced by values in <clusternodes>.
+
+Cman uses different defaults for some of the openais parameters listed in
+openais.conf(5).  If you wish to use a non-default setting, they can be
+configured in cluster.conf as shown above.  Cman uses the following
+default values:
 
   <totem
-   vsftype="none"
-   token="10000"
-   token_retransmits_before_loss_const="20"
-   join="60"
-   consensus="4800"
-   rrp_mode="none"
-   <!-- or rrp_mode="active" if altnames are present >
-   />
-   <logging syslog_facility="local4" />
-   <aisexec user="root" group="root" />
-
-cman does not use the openais.conf file at all. What it does do is 
-load the values from CCS into internal OpenAIS data structures that 
-map onto the entries to openais.conf. So that's why you can add an 
-entry in a <totem> section in CCS and it will be used by totem.
+    vsftype="none"
+    token="10000"
+    token_retransmits_before_loss_const="20"
+    join="60"
+    consensus="4800"
+    rrp_mode="none"
+    <!-- or rrp_mode="active" if altnames are present >
+  />
+  <logging syslog_facility="local4" />
+  <aisexec user="root" group="root" />
 
-Here's how to increase the token timeout to five seconds:
+Here's how to set the token timeout to five seconds:
 
   <totem token="5000"/>
 
-And this is how to add extra AIS logging options to cman & CPG:
+And this is how to add extra openais logging options to CMAN and CPG:
 
   <logging to_stderr="yes">
     <logger ident="CPG" debug="on" to_stderr="yes">
@@ -191,7 +199,6 @@
 .in -7
 
 
-
 .sp
 .in -7
 \fBSEE ALSO\fP