Completing the HyperSwap configuration in IBM Spectrum Virtualize 3-Site Orchestrator

Edit online

After you create the 3-Site Administrator users on each system and create the list of known hosts on the 3-Site Orchestrator, you need to complete the configuration process before you can configure 3-site replication.

Note: For RHEL 8.x version, private key is not recognized and you need to run below command with private key file path.
ssh-keygen -p -m PEM -f <private key file path>
Ensure you have the following information before you complete the 3-Site Orchestrator configuration:
  • All management IP addresses for each system in the configuration. Each system can have two IP addresses that are configured as management IP addresses for redundancy; however, the second IP address is optional.
  • The username for the 3-Site Orchestrator user.
  • The location of the corresponding key file that is used to authentication SSH connections between the systems and the 3-Site Orchestrator.
On the 3-Site Orchestrator host, complete these steps:
  1. Enter the following command: 
    [root@ORCH-HOST ~]# mk3siteconfig -ip1 x.xxx.xxx.xx,x.xxx.xxx.xx -keyfile /
'root/.ssh/id_rsa' -username tsuser  -port 6000 -topology hyperswap
    where x.xxx.xxx.xx represents the management IP addresses the HyperSwap® system at the near sites and the system at the Auxiliary Far site. The -keyfile value is the file path where the SSH private key is on the Orchestrator host. The -username value specifies the name of the user that has 3-Site Orchestrator administrator privileges. The value in the -port parameter is the starting address of the two port numbers, one for the HyperSwap system that is split between the master and auxiliary-near sites, and the second for the auxiliary-far site. For example, if 6000 is set as -port, then the master port and the auxiliary-near port (master_port and auxnear_port) is set at 6000 and the auxiliary-far port (auxfar_port) is set at 6001.
    Note: The mk3siteconfig command generates a tar file at location /opt/ibm/SpectrumVirtualize/rc3site/config.tar.
  2. To verify the configuration, enter the following command: 
    [root@ORCH-HOST cli]# ls3siteconfig
master_name Master
master_site_name site1
master_site_status online
master_ip1 x.xxx.xxx.xx
master_ip1_status reachable
master_ip2
master_ip2_status not_configured
master_port 6000
auxnear_name Master
auxnear_site_name site2
auxnear_site_status online
auxnear_ip1 x.xxx.xxx.xx
auxnear_ip1_status reachable
auxnear_ip2
auxnear_ip2_status not_configured
auxnear_port 6000
auxfar_name AuxFar
auxfar_site_status online
auxfar_ip1 x.xxx.xxx.xx
auxfar_ip1_status reachable
auxfar_ip2
auxfar_ip2_status not_configured
auxfar_port 6001
username tsuser
keyfile /root/.ssh/id_rsa
topology hyperswap
    The master_site_name and auxnear_site_name display the site names within the HyperSwap configuration. The master_site_status or the auxnear_site_status indicates the availability of individual nodes in the sites within the HyperSwap configuration. For example, if master_site_name site1 has two nodes and both are offline, then master_site_status is marked as offline.

To complete the HyperSwap configuration with 3-Site Orchestrator, you can either add a HyperSwap relationship to a 3-site consistency group or convert an existing HyperSwap consistency group to a 3-site consistency group. For more information, see Converting a HyperSwap consistency group to a 3-site consistency group or Adding a HyperSwap relationship to an existing 3-site consistency group.