1
2
3cman(5)                                                   cman(5)
4

NAME

6       cman ‐ cluster.conf cman configuration section
7
8
9

DESCRIPTION

11       Cman configuration values are placed in the <cman> </cman>
12       section of cluster.conf.  Per‐node  configuration  related
13       to  cman  is  placed in the standard <clusternode> </clus‐
14       ternode> sections.  All cman  configuration  settings  are
15       optional; usually none are used.
16
17

UDP port

19       By default, cman will use UDP port 6809 for internode com‐
20       munication.  This can be changed by setting a port  number
21       as follows:
22
23         <cman port="6809">
24         </cman>
25
26

Expected votes

28       The expected votes value is used by cman to determine quo‐
29       rum.  The cluster is quorate if the sum of votes of exist‐
30       ing  members is over half of the expected votes value.  By
31       default, cman_tool sets the expected votes value to be the
32       sum  of  votes  of all nodes listed in cluster.conf.  This
33       can be overriden by  setting  an  explicit  expected_votes
34       value as follows:
35
36         <cman expected_votes="3">
37         </cman>
38
39       If  the  cluster becomes partitioned, improper use of this
40       option can result in more than one partition gaining  quo‐
41       rum.   In  that event, nodes in each partition will enable
42       cluster services.
43
44

Two node clusters

46       Ordinarily, the loss of quorum after one out of two  nodes
47       fails  will prevent the remaining node from continuing (if
48       both nodes have one vote.)  Special configuration  options
49       can be set to allow the one remaining node to continue op‐
50       erating if the other fails.  To do this  only  two  nodes,
51       each  with  one vote, can be defined in cluster.conf.  The
52       two_node and expected_votes values must then be set  to  1
53       in the cman section as follows.
54
55         <cman two_node="1" expected_votes="1">
56         </cman>
57
58

Node votes

60       By  default,  a node is given one vote toward the calcula‐
61       tion of quorum.  This can be changed by giving  a  node  a
62       specific number of votes as follows:
63
64         <clusternode name="nd1" votes="2">
65         </clusternode>
66
67

Node ID

69
70       By  default,  a  node  is assigned a nodeid by the cluster
71       manager (cman) when it joins the  cluster.   This  can  be
72       overriden  by specifying a nodeid here.  Using this option
73       will ensure that a given node always has the same  ID.   A
74       node’s  application to join the cluster may be rejected if
75       you try to set the nodeid to one that is already used.
76
77         <clusternode name="nd1" nodeid="1">
78         </clusternode>
79
80

Multicast network configuration

82       Cman can be configured to use multicast instead of  broad‐
83       cast (broadcast is used by default if no multicast parame‐
84       ters are given.)  To configure multicast add one line  un‐
85       der the <cman> section and another under the <clusternode>
86       section:
87
88         <cman>
89             <multicast addr="224.0.0.1"/>
90         </cman>
91
92         <clusternode name="nd1">
93             <multicast addr="224.0.0.1" interface="eth0"/>
94         </clusternode>
95
96       The multicast addresses must match and the address must be
97       usable on the interface name given for the node.
98
99
100

SEE ALSO

102       cluster.conf(5), ccs(7), cman_tool(8)
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
Impressum