K.5.6 Changing the Settings in Multi-User Mode

This work is to be performed after completing the settings on all the nodes in the cluster system of the copy destination in single-user mode.

Start all the nodes in multi-user mode.
Set up the Cluster Integrity Monitor (CIM).
Delete the CF node names that were used in the copy source, and set the CF node names to be used in the copy destination.
Perform the settings on any node that configures the cluster system.
Example: The CF node names used in the copy source are fuji2 and fuji3, and those used in the copy destination are fuji4 and fuji5.
```
# rcqconfig -d fuji2 fuji3
# rcqconfig -a fuji4 fuji5
```
Checking the CF setting item
Check if the changed CF node name, CIP/SysNode name, and cluster name are correct.
```
a. Checking the CF node name and cluster name
```
Execute the cfconfig -g command on each node to check if the set CF node name and cluster name are correct.
Example: When the CF node name used in the copy destination is fuji4, and the cluster name used in the copy destination is PRIMECLUSTER2
```
# cfconfig -g
fuji4 PRIMECLUSTER2 eth1 eth2
```
```
b. Checking the CIP/Sysnode name
```
Check that all the CIP/SysNode names set in the remote host are enabled to communicate. Check the communication status on all the nodes.
Example: When the SysNode name set in the remote host is fuji5RMS
```
# ping fuji5RMS
```
For a cloud environment, also check the following.
```
c. Ensure that all nodes can join the cluster
```
Execute the cftool -n command on any one node to ensure that all nodes can join the cluster.
Example)Two CF nodes named fuji4 and fuji5
Make sure that Node shows both fuji4 and fuji5, and that State is UP.
```
# cftool -n
Node   Number State Os     Cpu
fuji4  1      UP    Linux  EM 64 T
fuji5  2      UP    Linux  EM 64 T
```
```
d. Verify that the CF over IP configuration is enabled
```
Execute the cftool -d command on all nodes to ensure that the CF over IP configuration is enabled.
Example)One cluster interconnect
Make sure that Device shows only /dev/ipX (X is 0 ~ 3. Show only the number of cluster interconnects).
```
# cftool -d
Number Device      Type  Speed  Mtu  State Configured Address
4      /dev/ip0     6    n/a    1392 UP    YES        0a.00.00.c9.00.00
```
If an error occurs in the above step a or b, check if the CF node name, CIP/SysNode name, and cluster name that are set in /etc/cip.cf, /etc/default/cluster or /etc/hosts are correct.
If you have problems with c and d above, check that the IP address, IP device, and broadcast address of the cluster interconnect are correct.
If an error occurs, take the procedure below:
1. Start the system in single-user mode.
2. Perform "4. Change the CF node name, CIP/SysNode name, and the cluster name." of "K.5.5 Setting up in Single-User Mode" again, and then restart the node.
3. Perform "K.5.6 Changing the Settings in Multi-User Mode " again.
Changing the cluster name of the Cluster Resource Management Facility
Change the cluster name of the Cluster Resource Management Facility.
Perform the settings on any node that configures the cluster system. The last number of each command must be fixed to 1 or 2.
Example: The new cluster name of the copy destination is "PRIMECLUSTER 2."
```
# /etc/opt/FJSVcluster/bin/clsetrsc -n PRIMECLUSTER2 1
# /etc/opt/FJSVcluster/bin/clsetrsc -n PRIMECLUSTER2 2
```
Changing the SF settings
If the target environment is not supported by the version of the source PRIMECLUSTER, perform this procedure after "K.5.11 Upgrade of PRIMECLUSTER."
- When copying between physical environments
  Refer to "5.1.2 Setting up the Shutdown Facility" to determine the type of shutdown agent required on the source and destination.
  Reconfigure the SF if the source and destination require different shutdown agents. Refer to "5.1.2 Setting up the Shutdown Facility" and set the SF settings according to the configuration of the destination.
  If the source and destination require the same shutdown agent, perform the following procedure.
1. For PRIMERGY, change the entries for the CF node names and the IP address for IPMI (BMC or iRMC) in "/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg".
  Example: When changing the values as follows.
```
CF node name      IP address for IPMI (BMC or iRMC)
fuji2 -> fuji4    10.20.30.200 -> 10.20.30.202
fuji3 -> fuji5    10.20.30.201 -> 10.20.30.203
```
  [Before change]
```
fuji2 10.20.30.200:root:D0860AB04E1B8FA3 cycle
fuji3 10.20.30.201:root:D0860AB04E1B8FA3 cycle
```
  [After change]
```
fuji4 10.20.30.202:root:D0860AB04E1B8FA3 cycle
fuji5 10.20.30.203:root:D0860AB04E1B8FA3 cycle
```
2. For PRIMEQUEST 3000 series, execute the following procedure:
  1. Change the setting of iRMC. For the setup instructions, see the following manual:
    - "PRIMEQUEST 3000 Series Installation Manual"
    You must create a user so that PRIMECLUSTER can link with iRMC. On all PRIMEQUEST 3000 instances that make up the PRIMECLUSTER system, make sure to create a user to control iRMC.
    - Both IPv4 Console Redirection Setup and IPv6 Console Redirection Setup
    - PRIMEQUEST 3000 (except B model)
    To create a user to control iRMC, use "set irmc user" command.
    For how to use "set irmc user" command, refer to the following manual:
    - "PRIMEQUEST 3000 Series Tool Reference (MMB)"
    - PRIMEQUEST 3000 B model
    To create a user to control iRMC, log in to iRMC Web Interface and create the user from "User Management" page of "Settings" menu.
    For how to use iRMC Web Interface, refer to the following manual page:
    - "FUJITSU Server PRIMEQUEST 3000 Series Business Model iRMC S5 Web Interface"
  2. Change the setting of MMB (except B model). For the setup instructions, see the following manual:
    - "PRIMEQUEST 3000 Series Installation Manual"
    You must create the RMCP user so that PRIMECLUSTER can link with the MMB units.
    On all PRIMEQUEST 3000 instances that make up the PRIMECLUSTER system, make sure to create a user to control the MMB units with RMCP. To create a user to control MMB with RMCP, log in to MMB Web-UI, and create the user from "Remote Server Management" screen of "Network Configuration" menu. Create the user as shown below:
    - [Privilege]: "Admin"
    - [Status]: "Enabled"
    For details about creating a user who uses RMCP to control the MMB units, see the following manual provided with the unit:
    - "PRIMEQUEST 3000 Series Operation and Management Manual"
  3. Delete the iRMC/MMB information used in the copy source CF node.
    Example: When deleting the iRMC/MMB information of the copy source fuji2, fuji3
```
# /etc/opt/FJSVcluster/bin/clirmcsetup -d fuji2
# /etc/opt/FJSVcluster/bin/clirmcsetup -d fuji3
```
  4. Execute "clirmcsetup -a irmc" command and register the iRMC information of the copy destination node. For how to use "clirmcsetup" command, refer to the manual page of clirmcsetup.
```
# /etc/opt/FJSVcluster/bin/clirmcsetup -a irmc irmc-user
Enter User's Password:
Re-Enter User's Password:
```
    For irmc-user and User's Password, enter the user and password created in step a.
  5. Execute "clirmcsetup -a mmb" command and register the MMB information of the copy destination node (except B model). For how to use "clirmcsetup" command, refer to the manual page of clirmcsetup.
```
# /etc/opt/FJSVcluster/bin/clirmcsetup -a mmb mmb-user
Enter User's Password:
Re-Enter User's Password:
```
    For mmb-user and User's Password, enter the user and password created in step b.
  6. Check that the iRMC asynchronous monitoring daemon has started.
```
# /etc/opt/FJSVcluster/bin/clirmcmonctl
```
    If "The devirmcd daemon exists." is displayed, the iRMC asynchronous monitoring daemon has started.
    If "The devirmcd daemon does not exist." is displayed, the iRMC asynchronous monitoring daemon has not started.
    Execute the following command to start the iRMC asynchronous monitoring daemon.
```
# /etc/opt/FJSVcluster/bin/clirmcmonctl start
```
3. Restore the saved rcsd.org file to the rcsd.cfg file.
```
# mv /etc/opt/SMAW/SMAWsf/rcsd.org /etc/opt/SMAW/SMAWsf/rcsd.cfg
```
4. Change the CF node names and the IP addresses of the administrative LANs (admIP) described in /etc/opt/SMAW/SMAWsf/rcsd.cfg.
  Example: When changing the values as follows
```
CF node name    IP address of administrative LAN
fuji2 -> fuji4    10.20.30.100 -> 10.20.30.102
fuji3 -> fuji5    10.20.30.101 -> 10.20.30.103
```
  [Before change]
```
fuji2,weight=1,admIP=10.20.30.100:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
fuji3,weight=1,admIP=10.20.30.101:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
```
  [After change]
```
fuji4,weight=1,admIP=10.20.30.102:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
fuji5,weight=1,admIP=10.20.30.103:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
```
5. If the destination server is PRIMERGY RX1330M3, RX4770M3, TX1320M3, TX1330M3, CX1430M1 or third-party server, delete SA_lkcd from/etc/opt/SMAW/SMAWsf/rcsd.cfg.
  [Before change]
```
fuji2,weight=1,admIP=10.20.30.100:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
fuji3,weight=1,admIP=10.20.30.101:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
```
  [After change]
```
fuji2,weight=1,admIP=10.20.30.100:SA_ipmi,timeout=25
fuji3,weight=1,admIP=10.20.30.101:SA_ipmi,timeout=25
```
6. Set up the kdump shutdown agent if the destination is PRIMERGY expect for RX1330M3, RX4770M3, TX1320M3, TX1330M31, or CX1430M1 and kdump is used to collect crash dumps. Execute the following command on any one of the nodes.
```
# /etc/opt/FJSVcllkcd/bin/panicinfo_setup
panicinfo_setup: WARNING: /etc/panicinfo.conf file already exists.
(I)nitialize, (C)opy or (Q)uit (I/C/Q) ? <- Input I
```
7. Start up the Shutdown Facility.
```
# sdtool -b
```
  Use sdtool -s to confirm whether the shutdown daemon (rcsd) is active.
```
# sdtool -s
```
  By executing sdtool -s on all the nodes, the composition of the shutdown facility can be confirmed.
  Note
  Confirm the shutdown facility operates normally by the display result of the sdtool -s command.
  There is a possibility that the configuration settings of the agent or hardware are not correct when any of the following statuses are displayed though setting the shutdown facility is completed.
  - InitFailed is displayed in Init State.
  - Unknown or TestFailed is displayed in Test State.
  Confirm whether the error message is output to the /var/log/messages file. Then, take corrective actions according to the content of the output message.
- When copying from a physical environment to a virtual environment
  Reconfigure the SF. Depending on the configuration of the shutdown facility at the copy destination, set the SF by referring to "G.2.3.2 Setting Up the Shutdown Facility (when using VMware vCenter Server Functional Cooperation)" in the "Appendix G Using PRIMECLUSTER in a VMware Environment" or "G.2.3.3 Setting Up the Shutdown Facility (when using I/O fencing function)."
- When copying between virtual environments
  If you are copying between KVM environments, see "5.1.2.5 Setup Procedure for Shutdown Facility in Virtual Machine Environment" to set the SF.
  If copying to a VMware environment with a different configuration ( shutdown facility), reconfigure the SF. Depending on the configuration of the shutdown facility at the copy destination, refer to "G.2.3.2 Setting Up the Shutdown Facility (when using VMware vCenter Server Functional Cooperation)" in the "Appendix G Using PRIMECLUSTER in a VMware Environment" or "G.2.3.3 Setting Up the Shutdown Facility (when using I/O fencing function)" in the VMware environment to set the SF.
  If copying to a VMware environment with the same configuration (shutdown facility), perform the following procedure.
1. If you are copying between VMware environments and you want to use the VMware vCenter Server Functional Cooperation for both the source and destination, perform the following procedure.
  Modify /etc/opt/SMAW/SMAWsf/SA_vwvmr.cfg with the following contents on all guest OSes (nodes) of the cluster. (Example of the same case except for the IP address of VMware vCenter Server)
  Example: When changing the values as follows
```
CF node name    IP address of administrative LAN
fuji2 -> fuji4    10.20.30.200 -> 10.20.30.202
fuji3 -> fuji5    10.20.30.201 -> 10.20.30.203
```
  [Before change]
```
##
## node1's information.
##
CFName: fuji2
VMName: vm1
vCenter_IP: 10.20.30.200
vCenter_Port:
user: Administrator@vsphere.local
passwd: D0860AB04E1B8FA3
##
## node2's information.
##
CFName: fuji3
VMName: vm2
vCenter_IP: 10.20.30.201
vCenter_Port:
user: Administrator@vsphere.local
passwd: D0860AB04E1B8FA3
```
  [After change]
```
##
## node1's information.
##
CFName: fuji4
VMName: vm1
vCenter_IP: 10.20.30.202
vCenter_Port:
user: Administrator@vsphere.local
passwd: D0860AB04E1B8FA3
##
## node2's information.
##
CFName: fuji5
VMName: vm2
vCenter_IP: 10.20.30.203
vCenter_Port:
user: Administrator@vsphere.local
passwd: D0860AB04E1B8FA3
```
2. If you are copying between VMware environments and you want to use I/O fencing function for both the source and destination, perform the following procedure.
  Modify /etc/opt/SMAW/SMAWsf/SA_icmp.cfg with the following contents on all guest OSes (nodes) of the cluster.
  Example: When changing the values as follows
```
CF node name   IP address for checking whether the node is alive.
fuji2->fuji4    192.168.0.1->192.168.0.3
fuji3->fuji5    192.168.0.2->192.168.0.4
```
  [Before change]
```
TIME_OUT=5
fuji2:192.168.0.1:eth2,eth3
fuji3:192.168.0.2:eth2,eth3
```
  [After change]
```
TIME_OUT=5
fuji4:192.168.0.3:eth2,eth3
fuji5:192.168.0.4:eth2,eth3
```
3. Restore the saved rcsd.org file to the rcsd.cfg file.
```
# mv /etc/opt/SMAW/SMAWsf/rcsd.org /etc/opt/SMAW/SMAWsf/rcsd.cfg
```
4. Change the CF node names, and the IP addresses of the administrative LANs (admIP) described in /etc/opt/SMAW/SMAWsf/rcsd.cfg.
  Example: When changing the values as follows
```
CF node name    IP address of administrative LAN
fuji2->fuji4    10.20.30.100->10.20.30.102
fuji3->fuji5    10.20.30.101->10.20.30.103
```
  [Before change]
```
fuji2,weight=1,admIP=10.20.30.100:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
fuji3,weight=1,admIP=10.20.30.101:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
```
  [After change]
```
fuji4,weight=1,admIP=10.20.30.102:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
fuji5,weight=1,admIP=10.20.30.103:agent=SA_lkcd,timeout=25:SA_ipmi,timeout=25
```
5. Start up the Shutdown Facility.
```
# sdtool -b
```
  Use sdtool -s to confirm whether the shutdown daemon (rcsd) is active.
```
# sdtool -s
```
  By executing sdtool -s on all the nodes, the composition of the shutdown facility can be confirmed.
  Note
  Confirm the shutdown facility operates normally by the display result of the sdtool -s command.
  There is a possibility that the configuration settings of the agent or hardware are not correct when any of the following statuses are displayed though setting the shutdown facility is completed.
  - InitFailed is displayed in Init State.
  - Unknown or TestFailed is displayed in Test State.
  Confirm whether the error message is output to the /var/log/messages file. Then, take corrective actions according to the content of the output message.
- When copying between cloud environments
1. Restore the saved rcsd.org file to the rcsd.cfg file.
```
# mv /etc/opt/SMAW/SMAWsf/rcsd.org /etc/opt/SMAW/SMAWsf/rcsd.cfg
```
2. Change the CF node names, and the IP addresses of the administrative LANs (admIP) described in /etc/opt/SMAW/SMAWsf/rcsd.cfg.
  Example: When changing the values as follows
```
CF node name    IP address of administrative LAN
fuji2->fuji4    10.20.30.100->10.20.30.102
fuji3->fuji5    10.20.30.101->10.20.30.103
```
  [Before change]
```
fuji2,weight=1,admIP=10.20.30.100:agent=SA_vmk5r,timeout=125
fuji3,weight=1,admIP=10.20.30.101:agent=SA_vmk5r,timeout=125
```
  [After change]
```
fuji4,weight=1,admIP=10.20.30.102:agent=SA_vmk5r,timeout=125
fuji5,weight=1,admIP=10.20.30.103:agent=SA_vmk5r,timeout=125
```
3. Change the CF node names, and the virtual server names of FJcloud-O on which the cluster host is running described in /etc/opt/SMAW/SMAWsf/SA_vmk5r.cfg.
  Example: When changing the values as follows
```
CF node name   virtual server name
fuji2->fuji4    vm1->vm3
fuji3->fuji5    vm2->vm4
```
  [Before change]
```
fuji2 vm1 pcl O/gm+AYuWwE7ow3dgVG/Nw== cycle
fuji3 vm2 pcl O/gm+AYuWwE7ow3dgVG/Nw== cycle
```
  [After change]
```
fuji4 vm3 pcl O/gm+AYuWwE7ow3dgVG/Nw== cycle
fuji5 vm4 pcl O/gm+AYuWwE7ow3dgVG/Nw== cycle
```
4. Change the PROJECT_NAME described in /opt/SMAW/SMAWRrms/etc/k5_endpoint.cfg to the name of the project to build the cluster on the FJcloud-O to be replicated.
  Example: When changing the values as follows
```
PROJECT_NAME
primecluster_project1->primecluster_project2 
```
  [Before change]
```
DOMAIN_NAME=primecluster_domain
PROJECT_NAME=primecluster_project1
IDENTITY=https://identity.jp-east-3.cloud.global.fujitsu.com
COMPUTE=https://compute.jp-east-3.cloud.global.fujitsu.com
```
  [After change]
```
DOMAIN_NAME=primecluster_domain
PROJECT_NAME=primecluster_project2
IDENTITY=https://identity.jp-east-3.cloud.global.fujitsu.com
COMPUTE=https://compute.jp-east-3.cloud.global.fujitsu.com
```
5. Start up the Shutdown Facility.
```
# sdtool -b
```
  Use sdtool -s to confirm whether the shutdown daemon (rcsd) is active.
```
# sdtool -s
```
  By executing sdtool -s on all the nodes, the composition of the shutdown facility can be confirmed.
  Note
  Confirm the shutdown facility operates normally by the display result of the sdtool -s command.
  There is a possibility that the configuration settings of the agent or hardware are not correct when any of the following statuses are displayed though setting the shutdown facility is completed.
  - InitFailed is displayed in Init State.
  - Unknown or TestFailed is displayed in Test State.
  Confirm whether the error message is output to the /var/log/messages file. Then, take corrective actions according to the content of the output message.