9.1.6 Setting Up CRM (Resource Database)

This section explains how to set up the Customer Resource Management (CRM) resource database.

Procedure

Reconfigure the resource database on the existing nodes.
Confirm the following:
- All of the existing nodes have been started.
- CIP entry of the new node is in /etc/cip.cf of the existing nodes.
  The resource database uses /etc/cip.cf to associate CF node names with CIP names.
Reconfigure the resource database.
The procedure is shown below:
1. Log into any one of existing nodes using a system administrator access privilege.
2. Specify the "-a" and the "-g" options in the "clsetp(1M)" command.
```
# /etc/opt/FJSVcluster/bin/clsetup -a node -g file
```
  As a result of this operation, a new node will be added to the resource database of the existing nodes.
  The configuration information on the resource database, created after the execution of the "clsetup(1M)" command, is used when the resource database of the new node is configured. Therefore, do not specify a directory that will be automatically deleted when rebooting the node with the "-g" option (for example: /tmp).
  Specify the CF node name in node, and a full path name of the file name of the resource database configuration information. "tar.Z" extension will be appended to the resource database configuration information.
  For example, to add a new node which has a CF node name of fuji4, and a configuration information file name of /mydir/rdb, the command to be executed will be as shown below:
```
# /etc/opt/FJSVcluster/bin/clsetup -a fuji4 -g /mydir/rdb
```
  The configuration information file of the resource database will be created as /mydir/rdb.tar.Z.
3. Confirm that the new node has been added to the resource database.
  Execute the "clgettree(1)" command, and then confirm that the new node is displayed on the output result. At this time, the state of the new node is displayed as UNKNOWN.
Set up the resource database of the new node.
Confirm the following:
- The content of /etc/cip.cf of the new node must be the same as that of the existing nodes.
  Confirm that the CIP of the new node is in /etc/cip.cf of the new node and that the content of /etc/cip.cf is the same as that of the existing nodes.
- Confirm that the new node is connected to all of the existing nodes by CIP using the "ping(1M)" command.
  If two or more CIPs are configured in the new nodes, use the first CIP for the resource database. Then, connection will be enabled. An example using "fuji4RMS" as the new node is shown below:
```
# ping fuji4RMS
```
  After confirming the above, set up the resource database of the new node.
  The procedure is as follows:
1. Log into the new node using a system administrator access privilege.
2. Copy the "resource database configuration information" file created in Step 2) in "Recreate the settings for the resource database of the existing nodes" to the new node.
3. Specify the -s option in the clsetup(1M) command, and execute it.
```
# /etc/opt/FJSVcluster/bin/clsetup -s file
```
  Specify file with a full path name of the resource database configuration file.
  When the resource database configuration information file "rdb.tar.Z" is copied to /mydir, the command to be executed will be as shown below:
```
# /etc/opt/FJSVcluster/bin/clsetup -s /mydir/rdb.tar.Z
```
4. Confirm that the resource database of the new node is configured.
  Execute the clgettree(1) command for the new node and confirm the following:
  - The new node is displayed.
  - The state of the new node is displayed as ON.
  - The output result is the same as that of the existing nodes.
Register the hardware, which is connected to the new node, to the resource database.
Log into any one of nodes using a system administrator access privilege, and execute the command shown below:
```
# /etc/opt/FJSVcluster/bin/clautoconfig -r
```

Setting up synchronization with the resource database

If the individual nodes are restarted at different times after node expansion, the tuning parameter must be set up to be synchronized with the resource database. For details, see "4.5.1 Start up synchronization and the new node" in the "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."