1ccs_tool(8) ccs_tool(8)
2
6 ccs_tool - The tool used to make online queries to the cluster configu‐
7 ration.
8
11 ccs_tool [OPTION].. <command>
12
15 ccs_tool is part of the Cluster Configuration System (CCS). It used to
16 peform different kind of queries to the cluster configuration and has
17 support for some cluster.conf editing functions.
18
21 -h Help. Print out the usage.
22 -V Print the version information.
24 sub-commands have their own options, see below for more detail
26
28 query <xpath query>
29 Perform an xpath query on running cluster configuration.
30 addnode [options] <node> [<fenceoption=value>]...
33 Adds a new node to the cluster configuration file. Fencing
34 device options are specified as key=value pairs (as many as
35 required) and are entered into the configuration file as is. See
36 the documentation for your fencing agent for more details (eg a
37 powerswitch fence device may need to know which port the node is
38 connected to).
39 Options:
40 -v <votes> Number of votes for this node (mandatory)
41 -n <nodeid> Node id for this node (optional)
42 -i <interface> Network interface to use for this node. Manda‐
43 tory if the cluster is using multicast as transport. Forbidden
44 if not.
45 -m <multicast> Multicast address for cluster. Only allowed on
46 the first node to be added to the file. Subsequent nodes will
47 use either multicast or broadcast depending on the properties of
48 the first node.
49 -f <fencedevice> Name of fence device to use for this node. The
50 fence device section must already have been added to the file,
51 probably using the addfence command.
52 -c <file> Config file to use. Defaults to /etc/clus‐
53 ter/cluster.conf
54 -o <file> Output file. Defaults to the same as -c
55 delnode [options] <node>
60 Delete a node from the cluster configuration file. Note: there
61 is no "edit" command so to change the properties of a node you
62 must delete it and add it back in with the new properties.
63 Options:
64 -c <file> Config file to use. Defaults to /etc/clus‐
65 ter/cluster.conf
66 -o <file> Output file. Defaults to the same as -c
67 addfence [options] <name> <agent> [<option>=<value>]...
72 Adds a new fence device section to the cluster configuration
73 file. <agent> is the name of the fence agent that controls the
74 device. the options following are entered as key-value pairs.
75 See the fence agent documentation for details about these. eg:
76 you may need to enter the IP address and username/password for a
77 powerswitch fencing device.
78 Options:
79 -c <file> Config file to use. Defaults to /etc/clus‐
80 ter/cluster.conf
81 -o <file> Output file. Defaults to the same as -c
82 delfence [options] <node>
85 Deletes a fencing device from the cluster configuration file.
86 delfence will allow you to remove a fence device that is in use
87 by nodes. This is to allow changes to be made, but be aware
88 that it may produce an invalid configuration file if you don't
89 add it back in again.
90 Options:
91 -c <file> Config file to use. Defaults to /etc/clus‐
92 ter/cluster.conf
93 -o <file> Output file. Defaults to the same as -c
94 lsnode [options]
98 List the nodes in the configuration file. This is (hopefully
99 obviously) not necessarily the same as the nodes currently in
100 the cluster, but it should be a superset.
101 Options:
102 -v Verbose. Lists all the properties of the node,
103 and the node-specific properties of the fence device too.
104 -c <file> Config file to use. Defaults to /etc/clus‐
105 ter/cluster.conf
106 lsfence [options]
110 List all the fence devices in the cluster configuration file.
111 Options:
112 -v Verbose. Lists all the properties of the fence
113 device rather than just the names and agents.
114 -c <file> Config file to use. Defaults to /etc/clus‐
115 ter/cluster.conf
116 create [options] <clustername>
120 Create a new, skeleton, configuration file. Note that "create"
121 on its own will not create a valid configuration file. Fence
122 agents and nodes will need to be added to it before handing it
123 over to ccsd. The new configuration file will have a version
124 number of 1. Subsequent addnode/delnode/addfence/delfence opera‐
125 tions will increment the version number by 1 each time.
126 Options:
127 -c <file> Config file to create. Defaults to /etc/clus‐
128 ter/cluster.conf
129 addnodeids
132 Adds node ID numbers to all the nodes in cluster.conf. In RHEL4,
133 node IDs were optional and assigned by cman when a node joined
134 the cluster. In RHEL5 they must be pre-assigned in cluster.conf.
135 This command will not change any node IDs that are already set
136 in cluster.conf, it will simply add unique node ID numbers to
137 nodes that do not already have them.
138
142 cluster.conf(5)
143 ccs_tool(8)