3.1 Resource Database configuration

This section discusses how to set up the Resource Database for the first time on a new cluster. The following procedure assumes that the Resource Database has not previously been configured on any of the nodes in the cluster.

Before you begin configuring the Resource Database, you must first make sure that CIP is properly configured on all the nodes. The Resource Database uses CIP for communicating between nodes, so it is essential that CIP is working.

The Resource Database also uses the CIP configuration file /etc/cip.cf to establish the mapping between the CF node name and the CIP name for a node. If a particular node has multiple CIP interfaces, then only the first one is used. This will correspond to the first CIP entry for a node in /etc/cip.cf. It will also correspond to cip0 on the node itself.

Because the Resource Database uses /etc/cip.cf to map between CF and CIP names, it is critical that this file be the same on all the nodes. If you used the Cluster Admin CF Wizard to configure CIP, then this will already be the case. If you created some /etc/cip.cf files by hand, then you need to make sure that all the nodes are specified and they are the same across the cluster.

In general, the CIP configuration is fairly simple. You can use the Cluster Admin CF Wizard to configure a CIP subnet after you have configured CF. If you use the Wizard, then you will not need to do any additional CIP configuration. See the Section "1.1 CF, CIP, and CIM configuration" for more details.

After CIP has been configured, you can configure the Resource Database on a new cluster by using the following procedure. This procedure must be done on all the nodes in the cluster.

Log in to the node with system administrator authority.
Verify that the node can communicate with other nodes in the cluster over CIP.
To test CIP network connectivity, execute the ping(1M) command or the ping6(8) command (when using the IPv6 address). The file /etc/cip.cf contains the CIP names that you should use in the ping(1M) command or the ping6(8) command.
If you are using RMS and you have only defined a single CIP subnetwork, then the CIP names will be of the following form:
```
cfnameRMS
```
For example, if you have two nodes in your cluster named fuji2 and fuji3, then the CIP names for RMS would be fuji2RMS and fuji3RMS, respectively. You could then run the following commands:
```
fuji2# ping fuji3RMS
fuji3# ping fuji2RMS
```
This tests the CIP connectivity.
Execute the clsetup command. When used for the first time to set up the Resource Database on a node, it is called without any arguments as follows:
```
# /etc/opt/FJSVcluster/bin/clsetup
```
Execute the clgettree command to verify that the Resource Database was successfully configured on the node, as shown in the following:
```
# /etc/opt/FJSVcluster/bin/clgettree
```
The command should complete without producing any error messages, and you should see the Resource Database configuration displayed in a tree format.
For example, on a two-node cluster consisting of fuji2 and fuji3, the clgettree command might produce output similar to the following:
```
Cluster 1 cluster
      Domain 2 Domain0
          Shared 7 SHD_Domain0
               Node 3 fuji2 UNKNOWN
               Node 5 fuji3 UNKNOWN
```

If you need to change the CIP configuration to fix the problem, you will also need to run the clinitreset command and start the information process over.

The format of clgettree is more fully described in its manual page. For the purpose of setting up the cluster, you need to check the following:

Each node in the cluster should be referenced in a line that begins with the word Node.
The clgettree output must be identical on all the nodes.

If either of the above conditions is not met, then it is possible that you may have an error in the CIP configuration. Double-check the CIP configuration using the methods described earlier in this section. The actual steps are as follows:

Make sure that CIP is properly configured and running.
Run clinitreset on all the nodes in the cluster.
```
# /etc/opt/FJSVcluster/bin/clinitreset
```
Reboot each node.
Rerun the clsetup command on each node.
```
# /etc/opt/FJSVcluster/bin/clsetup
```
Use the clgettree command to verify the configuration.
```
# /etc/opt/FJSVcluster/bin/clgettree
```