I.3.10 Changing the Settings of Cluster Application Information

This section describes how to change the SysNode name that constitutes a cluster application and the host name of the takeover network resource as well as the CF node name such as the procedure resource.

Obtain the RMS Configuration name. Follow the procedure below to output the file content. The character string after -c will be the RMS Configuration name. Perform this operation on any one of the nodes constituting a cluster.
Example
If the RMS Configuration name is 'config'
```
# cat /opt/SMAW/SMAWRrms/etc/CONFIG.rms
hvcm -c config <- RMS Configuration name
```

Collect the backup of the configuration file. Perform this operation on all cluster nodes.

Execute the following command.

cd /opt/SMAW/SMAWRrms/build/wizard.d
cp -rp <RMS Configuration name> <RMS Configuration name>.backup

When the takeover network resource is used, execute the following command on all cluster nodes.

cp -p /opt/SMAW/SMAWRrms/etc/hvipalias /opt/SMAW/SMAWRrms/etc/hvipalias.backup

Example

If <RMS Configuration name> is config

# cd /opt/SMAW/SMAWRrms/build/wizard.d
# cp -rp config config.backup
# cp -p /opt/SMAW/SMAWRrms/etc/hvipalias /opt/SMAW/SMAWRrms/etc/hvipalias.backup

Modify the SysNode name of the configuration file. Perform this operation on the same node where the step 1 was performed.
1. Move it to the directory where the configuration file is stored.
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/<RMS Configuration name>
```
  Example
  If <RMS Configuration name> is config
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/config
```
2. Search the target file with the following command.
```
grep -l HvpMachine *
```
  Example
```
# grep -l HvpMachine *
userApp_0.m
userApp_1.m
    :
```
  The displayed ".m" file is the target file.
3. Search and change the line starting "HvpMachine" in the displayed file. Open the file with the vi command.
```
# vi userApp_0.m
HvpApplication=userApp_0
HvpAutoBreak=yes
      :
    (Omitted)
      :
HvpMachine000=fuji2RMS  <- Target line to be changed
HvpMachine001=fuji3RMS  <- Target line to be changed
      :
   (Omitted)
```
  Change the SysNode name that is set in the right side of "-" to the new SysNode name.
  The SysNode name is set by adding RMS (capital letters) to the CF node name.
  The following example indicates when changing the CF node name from fuji2 and fuji3 to fuji4 and fuji5.
  [Before change]
```
HvpMachine000=fuji2RMS
HvpMachine001=fuji3RMS
```
  [After change]
```
HvpMachine000=fuji4RMS
HvpMachine001=fuji5RMS
```
  Perform this procedure on all the ".m" files obtained in step 3-2.
4. Check that the old SysNode does not exist.
  Example
```
# grep HvpMachine *.m
userApp_0.m:HvpMachine000=fuji4RMS
userApp_0.m:HvpMachine001=fuji5RMS
userApp_1.m:HvpMachine000=fuji4RMS
userApp_1.m:HvpMachine001=fuji5RMS
```
5. Rename the <SysNode name>.s file under the directory where the configuration file is stored with the mv command. Change the file with the old SysNode name to the new SysNode name.
  Example
```
# mv fuji2RMS.s fuji4RMS.s
# mv fuji3RMS.s fuji5RMS.s
```
Modify the CF node name of the procedure resource, line switching unit resource, and patrol diagnosis. This operation is only performed on the node where the step 3 was performed.
This procedure is unnecessary if the procedure resource, line switching unit resource, and patrol diagnosis are not being used.
1. Move it to the directory where the configuration file is stored.
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/<RMS Configuration name>
```
  Example
  If <RMS Configuration name> is config
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/config 
```
2. Search the target file with the following command.
```
grep -l HvpCrmScopeFilter *
```
  Example
```
# grep -l HvpCrmScopeFilter *
Procedure0.m
Procedure1.m
   :
```
  The displayed ".m" file is the target file.
3. Search and change the line starting "HvpCrmScopeFilter" in the displayed file. Open the file with the vi command.
```
# vi Procedure0.m
HvpApplType=RESOURCE
HvpApplication=Procedure0
HvpClassNameFilter=BasicApplication
HvpConsistent=consistent
HvpCrmFlags000=OT1800
HvpCrmResourceId000=33
HvpCrmResourceName000=SDISK
HvpCrmScopeFilter=fuji2:fuji3  <- Target line to be changed
HvpPlugin=BasicApplication
HvpPreCheckHeritageIn=''
   :
(Omitted)
```
  Change the CF node name that is set in the right side of "=" to the new CF node name.
  The following example indicates when changing the CF node name from fuji2 and fuji3 to fuji4 and fuji5.
  [Before change]
```
HvpCrmScopeFilter=fuji2:fuji3
```
  [After change]
```
HvpCrmScopeFilter=fuji4:fuji5
```
  Perform this procedure on all the ".m" files displayed in step 4-2.
  Note
  Only one CF node name may be set to HvpCrmScopeFilter due to the resource type.
4. Check that the old CF node name does not exist.
```
grep HvpCrmScopeFilter *.m
```
  Example
```
# grep HvpCrmScopeFilter *.m
Procedure0.m:HvpCrmScopeFilter=fuji4:fuji5
Procedure1.m:HvpCrmScopeFilter=fuji4:fuji5
    :
```
Modify the host name of the takeover network. This procedure is only performed on the same node as step 3.
If the takeover network resource is not used, this step and the following steps 6 and 7 are not necessary. Skip those steps and go to step 8.
1. Move it to the directory where the configuration file is stored.
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/<RMS Configuration name>
```
  Example
  If <RMS Configuration name> is config
```
# cd /opt/SMAW/SMAWRrms/build/wizard.d/config
```
2. Search the target file with the following command.
```
grep -l HvpPlugin=Ipaddress *
```
  Example
```
# grep -l HvpPlugin=Ipaddress *
Ipaddress0.m
Ipaddress1.m
    :
```
  The displayed ".m" file is the target file.
3. In the displayed file, search and change the line starting "HvpInterface". Open the file with the vi command.
```
# vi Ipaddress0.m
HvpApplType=IPADDR
HvpApplication=Ipaddress0
HvpConsistent=consistent
HvpInterface000=V:oldname  <- Target line to be changed
HvpIntfFilter=''
HvpNeedAll=yes
      :
   (Omitted)
```
  Change the host name set in the right side of (":") to the new host name.
  The following example indicates when changing the host name (oldname) corresponding to the IP address of the takeover network to newname.
  [Before change]
```
HvpInterface000=V:oldname
```
  [After change]
```
HvpInterface000=V:newname
```
  Perform this procedure on all the ".m" files obtained in step 4-2.
4. Check that the old host name of the takeover network does not exist.
  Example
```
# grep HvpInterface *.m
Ipaddress0.m: HvpInterface000=V:newname
```
Change the CF node name and the takeover network in the hvipalias file.
This file is stored in /opt/SMAW/SMAWRrms/etc/hvipalias. For each line, the CF node name is set in the first field, the host name of the takeover network is set in the second field, and the network interface to be used for the takeover network is set in the third field. Modify each name to the new name. Perform this operation on all the nodes constituting a cluster.
Example
When the CF node names are changed from fuji2 and fuji3 to fuji4 and fuji5, the host names of the takeover network are changed from oldname to newname, and the network interface to be used for the takeover network are changed from net0 to net1.
[Before change]
fuji2 oldname net0 0xffffff00 # sh_rid=34 rid=32 192.168.100.233 fuji3 oldname net0 0xffffff00 # sh_rid=34 rid=33 192.168.100.233
[After change]
fuji4 newname net1 0xffffff00 # sh_rid=34 rid=32 192.168.100.233 fuji5 newname net1 0xffffff00 # sh_rid=34 rid=33 192.168.100.233
Check that the SysNode name and takeover network in the /etc/inet/hosts file have been changed.

Execute the following command on the same node where the step 1 was performed.

hvw -F Configuration-Activate -xj -n <RMS Configuration name>

Example

# hvw -F Configuration-Activate -xj -n config

In the command output result, check the following contents of (1) and (2).

Testing for RMS to be up somewhere in the cluster ... done.

Arranging sub applications topologically ... done.

Check for all applications being consistent ... done.

Running overall consistency check ... done.

Generating pseudo code [one dot per (sub) application]: ..... done.

Generating RMS resources [one dot per
resource]: ............................................................ done


hvbuild using /usr/opt/reliant/build/wizard.d/config/config.us
About to distribute the new configuration data to hosts: fuji4RMS,fuji5RMS (1)

The new configuration was distributed successfully.

About to put the new configuration in effect ... done.

The activation has finished successfully. (2)
#

In (1), check that the new SysNode name is output.

In (2), check that "The activation has finished successfully." is displayed.

If the output results are different, check the following and take a necessary action:

Check if RMS is in operation on any node that constitutes a cluster. If it is, stop RMS.
Check that all nodes that constitute a cluster run in multi-user mode.
Check that the host name in the /etc/hosts file or the CF node name has been change on all nodes.

After taking the necessary action, perform the operation in step 8 again.

In "I.3.2 Changing IP Address, MAC Address, and Interface Name of GLS," if you change the IP address of GLS, delete the takeover IP address of Gls resource before cloning, and set it again. For how to set it, see "10.3.1 Changing the Cluster Application Configuration", "Creating Gls Resources."
If the RMS environment variables was changed in "I.3.1 Setup in Single-User Mode," return it with the following procedure. Perform this operation on all nodes where RMS is used.
```
# hvsetenv HV_RCSTART 1
# hvsetenv HV_RCSTART
1   <- Check that the returned value is output
```
Execute the following command on any one node to start RMS.
```
# hvcm -a
```