1/etc/ocfs2/cluster.conf(5) OCFS2 Manual Pages /etc/ocfs2/cluster.conf(5)
2
6 /etc/ocfs2/cluster.conf - Cluster configuration file for the o2cb clus‐
7 ter stack.
8
10 The cluster layout of the o2cb cluster stack is specified in
11 /etc/ocfs2/cluster.conf. It lists the name of the cluster, the nodes
12 comprising that cluster and its heartbeat regions. The cluster stack
13 expects this file to be the same on all nodes in that cluster.
14 This file should be populated using the o2cb(8) cluster configuration
16 utility. A sample of the same is shown in the example section.
17
20 The configuration file is divided into three types of stanzas, each
21 with a list of parameters and values. The three stanza types are clus‐
22 ter, node and heartbeat. While a configuration file can store defini‐
23 tions of multiple clusters, the o2cb cluster stack allows only one
24 cluster to be active at any one time. The name of this active cluster
25 is stored in /etc/sysconfig/o2cb [o2cb.sysconfig(5)].
26 The cluster stanza specifies the name of the cluster, number of nodes
28 and the heartbeat mode. The cluster name can include up to 16 alphanu‐
29 meric characters [0-9A-Za-z]. No special characters are allowed.
30 ┌───────────────┬────────────────────────────────────────────────────────┐
33 │Parameters │ Description │
34 ├───────────────┼────────────────────────────────────────────────────────┤
35 │node_count │ Number of nodes in the cluster │
36 ├───────────────┼────────────────────────────────────────────────────────┤
37 │heartbeat_mode │ local or global heartbeat │
38 ├───────────────┼────────────────────────────────────────────────────────┤
39 │name │ Cluster name (up to 16 alphanumeric chars [0-9A-Za-z]) │
40 └───────────────┴────────────────────────────────────────────────────────┘
41 The node stanza specifies the node name that is part of the cluster
43 alongwith its IPv4 address, port and node number. The node name must
44 match the hostname. The domain name is not required. For example,
45 appserver1.company.com can be appserver1. The IPv4 address need not be
46 the one associated with that hostname. As in, any valid IPv4 address on
47 that node can be used. The o2cb cluster stack will not attempt to match
48 the node name (hostname) with the specified IPv4 address. A low-latency
49 private interconnect address is recommended for best performance.
50 ┌───────────┬────────────────────────────────────────────────────────────┐
53 │Parameters │ Description │
54 ├───────────┼────────────────────────────────────────────────────────────┤
55 │ip_port │ IPv4 port │
56 ├───────────┼────────────────────────────────────────────────────────────┤
57 │ip_address │ IPv4 address (private interconnect recommended) │
58 ├───────────┼────────────────────────────────────────────────────────────┤
59 │number │ Node number (0 - 254) │
60 ├───────────┼────────────────────────────────────────────────────────────┤
61 │name │ Node name (hostname without the domain name) │
62 ├───────────┼────────────────────────────────────────────────────────────┤
63 │cluster │ Cluster name (should match the name in the cluster stanza) │
64 └───────────┴────────────────────────────────────────────────────────────┘
65 The heartbeat stanza specifies the global heartbeat region UUIDs. A
67 cluster can have up to 32 heartbeat regions. This is an optional stanza
68 and is only required if the global heartbeat mode is enabled. In other
69 words, the regions are only used if heartbeat_mode = global is in the
70 cluster stanza. If not, this stanza is ignored.
71 ┌───────────┬────────────────────────────────────────────────────────────┐
74 │Parameters │ Description │
75 ├───────────┼────────────────────────────────────────────────────────────┤
76 │region │ Heartbeat region UUID │
77 ├───────────┼────────────────────────────────────────────────────────────┤
78 │cluster │ Cluster name (should match the name in the cluster stanza) │
79 └───────────┴────────────────────────────────────────────────────────────┘
80 While manual editing is not recommended, users doing so must follow the
82 format strictly. The stanza should start at the first column and end
83 with a colon. The parameters must start after a tab. A blank line must
84 demarcate each stanza. Care should be taken to avoid stray white-spa‐
85 ces.
86
89 The example below illustrates populating a cluster.conf with a cluster
90 called webcluster, having 3 nodes and 3 global heartbeat regions, using
91 the o2cb(8) utility.
92 $ o2cb add-cluster webcluster
94 $ o2cb add-node webcluster node7 --ip 192.168.0.107 --number 7
96 $ o2cb add-node webcluster node6 --ip 192.168.0.106 --number 6
97 $ o2cb add-node webcluster node10 --ip 192.168.0.110 --number 10
98 $ o2cb add-heartbeat webcluster /dev/sdg1
100 $ o2cb add-heartbeat webcluster /dev/sdk1
101 $ o2cb add-heartbeat webcluster /dev/sdh1
102 $ o2cb heartbeat-mode webcluster global
104 $ o2cb list-cluster webcluster
106 heartbeat:
107 region = 77D95EF51C0149D2823674FCC162CF8B
108 cluster = webcluster
109 heartbeat:
111 region = DCDA2845177F4D59A0F2DCD8DE507CC3
112 cluster = webcluster
113 heartbeat:
115 region = BBA1DBD0F73F449384CE75197D9B7098
116 cluster = webcluster
117 node:
119 ip_port = 7777
120 ip_address = 192.168.0.107
121 number = 7
122 name = node7
123 cluster = webcluster
124 node:
126 ip_port = 7777
127 ip_address = 192.168.0.106
128 number = 6
129 name = node6
130 cluster = webcluster
131 node:
133 ip_port = 7777
134 ip_address = 192.168.0.110
135 number = 10
136 name = node10
137 cluster = webcluster
138 cluster:
140 node_count = 3
141 heartbeat_mode = global
142 name = webcluster
143
146 o2cb(7) o2cb(8) o2cb.sysconfig(5)
147
150 Oracle Corporation
151
154 Copyright © 2004, 2012 Oracle. All rights reserved.
155Version 1.8.7 January 2012 /etc/ocfs2/cluster.conf(5)