K.5.5 Setting up in Single-User Mode

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

Start the system in single-user mode.
For physical and virtual environments, boot in single-user mode.
In a cloud environment, disable and restart the automatic startup of the PRIMECLUSTER service by executing the following command on all nodes.
```
#/opt/FJSVpclinst/bin/pclservice off
```
Change the host name and IP addresses.
Change the host name in "/etc/hosts" and "/etc/hostname." If the IP address in "/etc/hosts" changes, also change the IP address.
Change the primary management sever, secondary management server, httpip, and mip in the Web-Based Admin View.
1. Set the IP addresses of the primary management server (fuji4) and the secondary management server (fuji5).
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server 10.20.30.102
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server 10.20.30.103
```
2. Set httpip.
  - fuji4
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip 10.20.30.102
```
  - fuji5
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip 10.20.30.103
```
3. Set mip.
  - fuji4
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip 10.20.30.102
```
  - fuji5
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip 10.20.30.103
```
4. Change the connection target information of the Java application.
  Edit the [Target] parameter from properties of the shortcut and the desktop shortcut of the Java application to change the connection target information.
  Example when the home folder of a Windows login user is "C:\Users\[User name]\":
  - Shortcut for connecting to the primary management server
```
"C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\bin\javaw.exe"
-jar "WVStartup.jar" "10.20.30.102" "8081"
```
  - Shortcut for connecting to the secondary management server
```
"C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\bin\javaw.exe"
-jar "WVStartup.jar" "10.20.30.103" "8081"
```

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."

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
^^^^^       ^^^^^^^^

Change the string of the CF node name and the IP address 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
^^^^^^^^^^^     ^^^^^^^^

Change the CF node name and cluster name described in /etc/default/cluster.

(If the device you use changes, also change the device name.)

physical or virtual environments

[Before change]

nodename fuji2
         ^^^^^
clustername PRIMECLUSTER1
            ^^^^^^^^^^^^^
device eth2
device eth3

nodename fuji3
         ^^^^^
clustername PRIMECLUSTER1
            ^^^^^^^^^^^^^
device eth4
device eth5

[After change]

nodename fuji4
         ^^^^^
clustername PRIMECLUSTER2
            ^^^^^^^^^^^^^
device eth2
device eth3

nodename fuji5
         ^^^^^
clustername PRIMECLUSTER2
            ^^^^^^^^^^^^^
device eth4
device eth5

cloud environments
Change the IP address. Specify the IP address of the interconnect of the own node, the broadcast address of the interconnect of the own node, and the IP address of the remote node, in the device line.

[Before change]

nodename fuji2
         ^^^^^
clustername PRIMECLUSTER1
            ^^^^^^^^^^^^^
device /dev/ip0 172.16.0.1 172.16.0.255 172.16.0.2
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

nodename fuji3
         ^^^^^
clustername PRIMECLUSTER1
            ^^^^^^^^^^^^^
device /dev/ip0 172.16.0.2 172.16.0.255 172.16.0.1
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[After change]

nodename fuji4
         ^^^^^
clustername PRIMECLUSTER2
            ^^^^^^^^^^^^^
device /dev/ip0 172.16.1.3 172.16.1.255 172.16.1.4
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

nodename fuji5
         ^^^^^
clustername PRIMECLUSTER2
            ^^^^^^^^^^^^^
device /dev/ip0 172.16.1.4 172.16.1.255 172.16.1.3
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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 procedure to change the IP address of the GLS. 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."
[physical or virtual environments]
Note
The procedure depends on the 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 network settings to change the IP address of the physical interface.
  [RHEL8]
  Modify the ifcfg-eth0 file and the ifcfg-eth1file to change the IP addresses of both the primary physical interface and the secondary physical interface.
  For [primecl03]
  - Contents of ifcfg-eth0
  [Before change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.181
PREFIX=24
DEVICE=eth0
ONBOOT=yes
```
  [After change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.191
PREFIX=24
DEVICE=eth0
ONBOOT=yes
```
  - Contents of ifcfg-eth1
  [Before change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.181
PREFIX=24
DEVICE=eth1
ONBOOT=no
```
  [After change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.191
PREFIX=24
DEVICE=eth1
ONBOOT=no
```
  For [primecl04]
  - Contents of ifcfg-eth0
  [Before change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.182
PREFIX=24
DEVICE=eth0
ONBOOT=yes
```
  [After change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.192
PREFIX=24
DEVICE=eth0
ONBOOT=yes
```
  - Contents of ifcfg-eth1
  [Before change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.182
PREFIX=24
DEVICE=eth1
ONBOOT=no
```
  [After change]
```
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.34.214.192
PREFIX=24
DEVICE=eth1
ONBOOT=no
```
  [RHEL9]
  Change the IP addresses of both the primary physical interface and the secondary physical interface.
  For [primecl03]
  - Contents of eth0.nmconnection
  [Before change]
```
[ipv4]
address1=10.34.214.181/24
```
  [After change]
```
[ipv4]
address1=10.34.214.191/24
```
  - Contents of eth1.nmconnection
  [Before change]
```
[ipv4]
address1=10.34.214.181/24
```
  [After change]
```
[ipv4]
address1=10.34.214.191/24
```
  For [primecl04]
  - Contents of eth0.nmconnection
  [Before change]
```
[ipv4]
address1=10.34.214.182/24
```
  [After change]
```
[ipv4]
address1=10.34.214.192/24
```
  - Contents of eth1.nmconnection
  [Before change]
```
[ipv4]
address1=10.34.214.182/24
```
  [After change]
```
[ipv4]
address1=10.34.214.192/24
```
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
```
  See
  If there is a change in the interface name to be used, please use the -t option to change the interface name. For details, see the "hanetconfig command" in the "PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function."
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."
[cloud environments]
1. Correct the "/etc/hosts" file.
  [Before change]
```
10.34.214.185 takeoverIP # takeover IP address
10.34.214.1   gw           # Gateway IP Address
```
  [After change]
```
10.34.214.195 takeoverIP # takeover IP address
10.34.214.1   gw           # Gateway IP Address
```
2. Delete all settings for the takeover virtual interface.
```
# /opt/FJSVhanet/usr/sbin/hanethvrsc delete -n all
```
3. Restore bak_ifcfg-eth0 (for RHEL 8) and eth0.nmconnection.bak (for RHEL 9) backed up in “K.3.6 Preparing for the Cloud Environment”
  [RHEL8]
```
# cp -p /etc/sysconfig/network-scripts/bak_ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0
```
  [RHEL9]
```
# cp -p /etc/NetworkManager/system-connections/eth0.nmconnection.bak /etc/NetworkManager/system-connections/eth0.nmconnection
```
4. Modify the network settings.
  [RHEL8]
  Modify the ifcfg-eth0 file and the ifcfg-sha0 file
  - Cancel the comment out PEERDNS and set "static" to BOOTPROTO and "no" to DEFROUTE in the /etc/sysconfig/network-scripts/ifcfg-eth0.
  - Change ONBOOT to "yes" in/etc/sysconfig/network-scripts/ifcfg-sha0 file.
  [RHEL9]
  - Use the nmcli connection modify command to modify the following parameters for eth0:
    - ipv4.method "disabled"
    - ipv4.ignore-auto-dns "yes"
    - ipv4.never-default "yes"
  - Use the nmcli connection modify command to change connection.autoconnect to yes on sha0.
5. Change the network monitoring function settings.
  Delete the existing monitoring target and change it to a virtual router for the copy destination environment. In addition, considering the possibility that the virtual router has stopped for a long time, set up to avoid a failover of the cluster when an error occurs in the transmission route.
```
# /opt/FJSVhanet/usr/sbin/hanetpathmon target -n sha0 -d 
# /opt/FJSVhanet/usr/sbin/hanetpathmon target -n sha0 -p 10.34.214.1
# /opt/FJSVhanet/usr/sbin/hanetpathmon param -n sha0 -f no
```
6. Creating the takeover virtual interface.
  Creates the takeover virtual interface for use in the copy destination environment.
```
# /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -i 10.20.40.200
```

Change the GDS settings.

Make the disks used by the GDS visible to the OS.

The following steps depends on the disk replication method selected in "K.1.3 Copying Method for Data Disk (GDS)."

"When not using the mirroring among servers " of "When making the GDS configuration of the copy destination the same as the configuration of the copy source ", or "When making the GDS configuration of the copy destination different from the configuration of the copy source."
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 the device information in the "/var/opt/FJSVsdx/log/sdx_iscsi.list" file.
  This step is not required if this file does not exist on all nodes.
```
...
Class1 /dev/disk/by-id/scsi-3600000e00... <- Delete all class name lines
...
```
4. Delete all configuration information in the "/etc/sysconfig/devlabel" file.
```
...
/etc/opt/FJSVsdx/.devlabel/Class1/sdx_dev...    <- Delete this line
...
```
5. Delete all the directories named with the class name in "/etc/opt/FJSVsdx/.devlabel" directory.
```
# cd /etc/opt/FJSVsdx/.devlabel
# rm -rf Class1
```

"When using the mirroring among servers " of "When making the GDS configuration of the copy destination the same as the configuration of the copy source "

Change the settings for iSCSI targets used for the mirroring among servers of GDS. Perform the following procedure on all the nodes.

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 NetworkManager.service

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
```
Setting automatic startup of PRIMECLUSTER service
In the cloud environment, execute the following command on all nodes to restore the PRIMECLUSTER service settings that were suppressed in step 1.
```
#/opt/FJSVpclinst/bin/pclservice on
```
After completing above procedure on all the nodes of the copy destination, start up all the nodes in multi-user mode.