9.1.8 Setting Up RMS

This section explains how to register a new node (SysNode) in a userApplication that has been running on an existing node.

Procedure

Configuration for each resource
Take the following steps depending upon the resources in the existing userApplication:
- Cmdline
  Create the Start, Stop, and Check scripts in the new node or copy them from the existing node. If "Path enter" is selected from "Creation method" when creating the existing Cmdline resource, specify the paths to the scripts. If "New" is selected, the scripts under /opt/FJSVwvucw/scripts/start, /opt/FJSVwvucw/scripts/stop, and /opt/FJSVwvucw/scripts/check must be stored in the same directory of the new node. You also need to add the access privilege by executing the "chmod(1)" command.
- Gds
  Take the following steps to expand the cluster scope:
  1. Expand the cluster scope.
    See "5.4 Changes" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
  2. Execute the following command on any one of the cluster nodes:
```
# /opt/SMAW/SMAWRrms/bin/hvgdsetup -a class
hvgdsetup with -a option performs the following tasks on
nodes to which the specified disk class belongs.
  1) Make GDS disk class on resource database not activated
     automatically when the node boots. If this operation has
      been done before, nothing will be performed anymore.
  2) Next make volumes of the specified disk class
     enabled manual online on a node on which an application
     is offline or faulted while the application is online
     or standby on another node.
  3) Then make volumes of the specified disk class stopped
     immediately.
     This process is executed on the nodes to which the disk
     class belongs.
Do you want to continue with these processes ? [yes/no]
```
    The following message might appear after executing the "hvgdsetup" command. This does not disrupt ongoing operation.
```
FJSVcluster: error: clrmd: 7516: An error occurred in the resource deactivation processing. (resource:resource rid:rid detail:detail)
WARNING !!
Failed to control 'dc_class' in the following node(s).
  node(s) node_name:  
Check the state of the nodes. If any nodes have failed, you may ignore this message.
```
- Fsystem
  If the file system is UFS, add the mount point entry to /etc/vfstab on the new node.
  If the file system is GFS, take the following steps and then create a GFS local file system on the GDS volume of the new node.
  Confirm that a GDS volume is available, and that the volume is ACTIVE. If the volume is STOP, start the volume. For information on how to start a volume, see "4.2.3 Operation" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
  1. Acquire hostid for the new node.
```
node3 # hostid 
80b1a621
```
  2. Add the information on the new node to the GFS local file system by executing the following command on any one of the existing cluster nodes.
```
node1 # sfxnode -a -n node3 -i 80b1a621 /dev/sfdsk/class/rdsk/volume
```
  3. Register the GFS local file system on the new node by executing the following command:
```
node3 # sfxadm -A /dev/sfdsk/class/rdsk/volume
```
  4. Using the vi text editor, add the entry of the GFS local file system to /etc/vfstab in the new node.
    Each line must begin with #RMS#."
```
node3# vi /etc/vfstab
#RMS#/dev/sfdsk/class/dsk/volume /dev/sfdsk/class/rdsk/volume /disk1 sfxfs - no -
```
  5. Create a mount point in the new node.
```
node3 # mkdir /disk1
```
- Gls
  Take the following steps for Gls:
  1. Set up the virtual interface for the takeover IP address on the new node and register it as a cluster resource. For details, see the "PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function."
  2. Restart Gls by executing the following command:
```
node3# /opt/FJSVhanet/usr/sbin/resethanet -s
```
- Takeover network
  Nothing needs be done at this time. In Procedure 3, however, it is necessary to recreate the resources.
- Procedure
  Create a state transition procedure on the new node and register the procedure resource with the cluster resource manager. For more details, see "F.1 Registering a Procedure Resource".
- Process monitoring
  Add the startup command to the new node. Also, you need to add the access privilege by using the "chmod(1)" command. Then, recreate the resources in Procedure 3.
Deleting userApplication
Delete the existing userApplication by using the userApplication Configuration Wizard. At this time, select "Delete only userApplication."
For more details, see "8.1.1 Changing the Cluster Application Configuration."
Recreating the takeover network and process monitoring resources
If the takeover network resource and the process monitoring resource are registered in the cluster system, first delete and then recreate those resources.
See "8.8.2 Deleting a Resource," "6.6.1.5 Creating Takeover Network Resources," and "6.6.1.7 Creating Process Monitoring Resources."
Recreating userApplication
Recreate the userApplication that was deleted in Procedure 2, using the same procedure as that used to create it. Note that the new node must be registered when SysNode is to be selected. For details, see "6.6.2 Creating Cluster Applications."
Copy /opt/SMAW/SMAWRrms/bin/hvenv.local of the existing node to /opt/SMAW/SMAWRrms/bin/ of the new node.
Edit /opt/SMAW/SMAWRrms/bin/hvenv.local in each node with the "vi" editor, and delete the following entry:
```
export HV_RCSTART=0
```