M.3.2 Setup in Single-User Mode

Execute the following procedure on all the nodes of the copy destination.

Start the system in single-user mode.
Change the host name.
Change the host name in "/etc/hosts", "/etc/sysconfig/network (for RHEL6)", and "/etc/hostname (for RHEL7)".

Change the primary management sever, secondary management server, httpip, and mip in the Web-Based Admin View.

Set the IP addresses of the primary management server and the secondary management server.

# /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server <IP-address-of-primary-management-server>
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server <IP-address-of-secondary-management-server>

Set httpip.

# /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip <IP-address-used-for-a-client>

Set mip.

# /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip <IP-address-for-identifying-own-host>

Change the CF node name, CIP/SysNode name, and the cluster name.
Note
For the naming conventions (cluster name and CF node name), see "5.1.1 Setting Up CF and CIP."
1. Change the string of the CF node name within the CF node name and the CIP/SysNode name that are described in /etc/cip.cf.
  [Before change]
```
fuji2       fuji2RMS:netmask:255.255.255.0
fuji3       fuji3RMS:netmask:255.255.255.0
```
  [After change]
```
fuji4       fuji4RMS:netmask:255.255.255.0
fuji5       fuji5RMS:netmask:255.255.255.0
```
2. Change the string of the CF node name within the CIP/SysNode name that are described in /etc/hosts.
  [Before change]
```
192.168.0.1     fuji2RMS
192.168.0.2     fuji3RMS
```
  [After change]
```
192.168.0.3     fuji4RMS
192.168.0.4     fuji5RMS
```
3. Change the CF node name and cluster name described in /etc/default/cluster.
  [Before change]
```
nodename fuji2
clustername PRIMECLUSTER1
device eth2
device eth3
```
  [After change]
```
nodename fuji4
clustername PRIMECLUSTER2
device eth2
device eth3
```
Cancel the SF settings.
Save "/etc/opt/SMAW/SMAWsf/rcsd.cfg" to the rcsd.org file.
```
# mv /etc/opt/SMAW/SMAWsf/rcsd.cfg /etc/opt/SMAW/SMAWsf/rcsd.org
```
Change the node name of the Cluster Resource Management Facility.
Execute the following command to change the node name of the Cluster Resource Management Facility.
```
# /etc/opt/FJSVcluster/bin/clchgnodename
```
Delete the information in the management partition of GFS.
Note
This procedure is unnecessary when the GFS Shared File System is not being used.
Delete the information in the management partition of the GFS Shared File System. Execute the following command on all the nodes.
```
# rm /var/opt/FJSVsfcfs/sfcfsrm.conf
```
Change the IP Address of GLS.
If you are using GLS, perform the following settings. Change the settings on all the nodes.
See
For details on the settings, see "PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function."
Note
The procedure depends on the data communication mode. The following procedure is for changing the IP address within the same network as the configuration using the NIC switching mode.
1. Correct the "/etc/hosts" file.
  [Before change]
```
10.34.214.185 takeoverIP # Virtual IP
10.34.214.181 primecl01  # primecl01 physical IP
10.34.214.182 primecl02  # primecl02 physical IP
10.34.214.188 swhub1     # primary HUB IP
10.34.214.189 swhub2     # secondary HUB IP
```
  [After change]
```
10.34.214.195 takeoverIP2 # Virtual IP
10.34.214.191 primecl03   # primecl03 physical IP
10.34.214.192 primecl04   # primecl04 physical IP
10.34.214.188 swhub1      # primary HUB IP
10.34.214.189 swhub2      # secondary HUB IP
```
2. Delete all settings for the takeover virtual Interface.
```
# /opt/FJSVhanet/usr/sbin/hanethvrsc delete -n all
```
3. Modify the ifcfg-eth0 file to change the IP address of the primary physical interface.
  For [primecl03]
  [Before change]
```
DEVICE=eth0
BOOTPROTO=static
HOTPLUG=no
IPADDR=10.34.214.181
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
```
  [After change]
```
DEVICE=eth0
BOOTPROTO=static
HOTPLUG=no
IPADDR=10.34.214.191
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
```
  For [primecl04]
  [Before change]
```
DEVICE=eth0
BOOTPROTO=static
HOTPLUG=no
IPADDR=10.34.214.182
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
```
  [After change]
```
DEVICE=eth0
BOOTPROTO=static
HOTPLUG=no
IPADDR=10.34.214.192
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
```
4. Change the IP address of the virtual interface.
  For [primecl03]
```
# /opt/FJSVhanet/usr/sbin/hanetconfig modify -n sha0 -i 10.34.214.195 -e 10.34.214.191
```
  For [primecl04]
```
# /opt/FJSVhanet/usr/sbin/hanetconfig modify -n sha0 -i 10.34.214.195 -e 10.34.214.192
```
5. Reregister the settings of the takeover virtual Interface.
```
# /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
```
See
For changing the IP address to a different network, the subnet mask of the virtual interface and the monitoring IP address of the HUB monitoring function need to be changed. For details, see "PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function."

Change the GDS settings.

When the mirroring among servers is not used
Delete the local class and shared class definitions of GDS. Perform the following procedure on all the nodes.
1. Delete the settings of class name in the "/etc/opt/FJSVsdx/sysdb.d/class.db" file.
```
...
Class1          <- Delete all the lines of class name
...
```
2. Delete all files named with the class name in the "/etc/opt/FJSVsdx/sysdb.d" directory.
```
# cd /etc/opt/FJSVsdx/sysdb.d
# rm Class1
```
3. Delete all configuration information in the "/etc/sysconfig/devlabel" file.
```
...
/etc/opt/FJSVsdx/.devlabel/Class1/sdx_dev...    <- Delete this line
...
```
4. Delete all the directories named with the class name in "/etc/opt/FJSVsdx/.devlabel" directory.
```
# cd /etc/opt/FJSVsdx/.devlabel
# rm -rf Class1
```

When the mirroring among servers is used

Change the settings for iSCSI targets used in GDS. Perform the following procedure on all the nodes.

[RHEL6]

Delete the registered target portal.
Example: The IP address used for the mirroring among servers of the copy source node is "192.168.56.20".
```
# iscsiadm -m discovery --op delete --portal 192.168.56.20
```
Start the network service.
```
# service network start
```

Change the IP address entries in /etc/tgt/targets.conf and the path of the by-id link.

Example: Change the IP address to "192.168.56.21" and "192.168.56.11", and the path of the by-id link to "/dev/disk/by-id/scsi-3500000e111c56610".

[Before change]

# GDS netmirror definition start
<target target-0101>
initiator-address 192.168.56.20
initiator-address 192.168.56.10
write-cache off
 <backing-store /dev/disk/by-id/scsi-3500000e111e68e00>
  scsi_id SDX-01
 </backing-store>
</target>
# GDS netmirror definition end

[After change]

# GDS netmirror definition start
<target target-0101>
initiator-address 192.168.56.21
initiator-address 192.168.56.11
write-cache off
 <backing-store /dev/disk/by-id/scsi-3500000e111c56610>
  scsi_id SDX-01
 </backing-store>
</target>
# GDS netmirror definition end

Start the tgtd service.
```
# service tgtd start
```
On all the nodes, change the IP addresses that are described in /etc/opt/FJSVsdx/.sdxnetmirror_ipaddr, which is the configuration file of the mirroring among servers.
[Before change]
```
192.168.56.10
192.168.56.20
```
[After change]
```
192.168.56.11
192.168.56.21
```
Establish the iSCSI session.
For the procedure, see "Establishing iSCSI Session" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

[RHEL7]

Delete the registered target portal.
Example: The IP address used for the mirroring among servers of the copy source node is "192.168.56.20".
```
# iscsiadm -m discovery --op delete --portal 192.168.56.20
```

Start the network service.

# systemctl start network.service

The following message may be output, however, it does not affect the operation of GDS. No corrective action is required.

Error getting authority: Error initializing authority: Could not connect:
No such file or directory (g-io-error-quark, 1)

Copy the configuration information file of the iSCSI target.

# cp /etc/target/saveconfig.json copy_destination_file_name

Change the IP address and the path of the by-id link described in the copy destination file explained in step 3 above.

Example: Change the IP address to "192.168.56.11", and the path of the by-id link to "/dev/disk/by-id/scsi-3500000e111c56610".

[Before change]

{
  "fabric_modules": [],
  "storage_objects": [
    {
...
      "dev": "/dev/disk/by-id/scsi-3500000e111e68e00",
      "name": "store1",
      "plugin": " block ",
      "readonly": false,
      "write_back": false,
      "wwn": "4a98bfb0-7d7e-4bc8-962c-0b3cf192b214"
    }
...
          "portals": [
            {
              "ip_address": "192.168.56.20",
              "iser": false,
              "port": 3260
            }
          ],
...

[After change]

{
  "fabric_modules": [],
  "storage_objects": [
    {
...
      "dev": "/dev/disk/by-id/scsi-3500000e111c56610",
      "name": "store1",
      "plugin": "block",
      "readonly": false,
      "write_back": false,
      "wwn": "4a98bfb0-7d7e-4bc8-962c-0b3cf192b214"
    }
...
          "portals": [
            {
              "ip_address": "192.168.56.21",
              "iser": false,
              "port": 3260
            }
          ],
...

Apply the changes in the configuration information file of the iSCSI target modified in step 4 above to the target.
```
# targetctl restore file_name
```
The following message may be output, however, it does not affect the operation of GDS. No corrective action is required.
```
Unable to load target_core_user
```

Make sure that the iSCSI target is set correctly.

# targetcli ls

[Output example]

o- / ............................................................................. [...]
  o- backstores .................................................................. [...]
  | o- block ...................................................... [Storage Objects: 1]
  | | o- store1  [/dev/disk/by-id/scsi-3500000e111c56610 (16.0GiB) write-thru activated]
                   (1)
  | o- fileio ..................................................... [Storage Objects: 0]

  | o- pscsi ...................................................... [Storage Objects: 0]
  | o- ramdisk .................................................... [Storage Objects: 0]
  o- iscsi ................................................................ [Targets: 1]
  | o- iqn.2003-01.org.linux-iscsi.node1.x8664:sn.6e665c7c1be0 ............... [TPGs: 1]
  |   o- tpg1 ................................................... [no-gen-acls, no-auth]
  |     o- acls .............................................................. [ACLs: 2]
  |     | o- iqn.1994-05.com.redhat:dee92ff9979d ...................... [Mapped LUNs: 1]
  |     | | o- mapped_lun0 .................................... [lun0 block/store1 (rw)]
  |     | o- iqn.1994-05.com.redhat:fa7eb9cf483c ...................... [Mapped LUNs: 1]
  |     |   o- mapped_lun0 .................................... [lun0 block/store1 (rw)]
  |     o- luns .............................................................. [LUNs: 1]
  |     | o- lun0 .............. [block/store1 (/dev/disk/by-id/scsi-3500000e111c56610)]
                                                 (2)
  |     o- portals ........................................................ [Portals: 1]
  |       o- 192.168.56.21:3260................................................. [OK]
             (3)
  o- loopback ............................................................. [Targets: 0]

Point

Make sure to confirm the command output about the following item.

- Applying the changed path (Example of output(1),(2))

- Applying the changed IP address (Example of output(3))

Save the target information restored in step 5.
```
# targetctl save
```
On all the nodes, change the IP addresses that are described in /etc/opt/FJSVsdx/.sdxnetmirror_ipaddr, which is the configuration file of the mirroring among servers.
[Before change]
```
192.168.56.10
192.168.56.20
```
[After change]
```
192.168.56.11
192.168.56.21
```
Establish the iSCSI session.
For the procedure, see "Establishing iSCSI Session" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

Restrict the automatic startup of RMS.
Check the settings of the current automatic startup of RMS and execute the following command according to the settings.
```
# hvsetenv HV_RCSTART
1    <- Check this value
```
- If "0" is set, the automatic startup of RMS has been restricted. Go to Step 11.
- If "1" is set, execute the following commands to restrict the automatic startup of RMS.
```
# hvsetenv HV_RCSTART 0
# hvsetenv HV_RCSTART
0    <- Check "0" is output
```
After completing above procedure on all the nodes of the copy destination, start up all the nodes in multi-user mode.