Configuring standby orchestrator

Edit online

The active and standby orchestrator can be configured by using the command-line interface (CLI). Both Metro Mirror and HyperSwap® configurations are supported for standby orchestrator. To configure standby orchestrator, you must update the installation version to orchestrator 4.1.

For more information about the prerequisites for configuring standby orchestrator, see Planning for IBM Spectrum Virtualize 3-Site Orchestrator.

Note: Due to security restriction, the following commands in standby orchestrator can work with root privileges only.

ch3siteconfig -startha
ch3siteconfig -startha -standby -config <path of config.tar>
ch3siteconfig -stopha -force
ch3siteconfig -standby -force	
ch3siteconfig -update -config <path of config.tar>

Using the command-line interface

By default after installing 3-site orchestrator, standby orchestrator does not start. To configure the active and standby orchestrator, complete these steps:

To configure active orchestrator, login into orchestrator having 3-site configuration that is already created. Enter ls3siteconfig command and validate if orchestrator_ha_status is showing <empty> value.

[root@localhost home]# ls3siteconfig
master_name Master
master_site_name
master_site_status online
master_ip1 x.xxx.xxx.xx
master_ip1_status reachable
master_ip2
master_ip2_status not_configured
master_port 17160
auxnear_name Aux_Near
auxnear_site_name
auxnear_site_status online
auxnear_ip1 x.xxx.xxx.xx
auxnear_ip1_status reachable
auxnear_ip2
auxnear_ip2_status not_configured
auxnear_port 17161
auxfar_name Auxfar_MM
auxfar_site_status online
auxfar_ip1 x.xxx.xxx.xxx
auxfar_ip1_status reachable
auxfar_ip2
auxfar_ip2_status not_configured
auxfar_port 17162
username rontsu
keyfile /root/.ssh/pw_rsa
topology metromirror
orchestrator_version 4.1.220922160427
orchestrator_ha_status

Note: The possible values for orchestrator_ha_status attribute are:

<empty>: if the standby orchestrator is not configured
online: if the standby orchestrator is configured
offline: if the active orchestrator is not running
standby_offline: if the standby orchestrator is not running
disconnected: if the communication failed with aux-far site

After 3-site configuration is completed by using mk3siteconfig command, enter the following command to start active orchestrator.
```
[root@localhost home]# ch3siteconfig -startha
```
The optional parameter -startha sets the role of orchestrator as an active orchestrator.
Note: The ch3siteconfig command generates a tar file at location /opt/ibm/SpectrumVirtualize/rc3site/config.tar.

To configure standby orchestrator, copy config.tar to standby orchestrator.

[root@localhost home]# scp /opt/ibm/SpectrumVirtualize/rc3site/config.tar root@9.122.123.44:/home
root@9.122.123.44's password:
config.tar                                                                                                                                                 100%   10KB   9.5MB/s   
00:00

Switch to standby orchestrator and enter the following command to configure standby orchestrator.
```
[root@rhel7host108 home]# ch3siteconfig -startha -standby -config /home/config.tar
```

To verify the orchestrator status, enter the ls3siteconfig command to view the resulting output.

[root@localhost home]# ls3siteconfig
master_name Master
master_site_name
master_site_status online
master_ip1 x.xxx.xxx.xx
master_ip1_status reachable
master_ip2
master_ip2_status not_configured
master_port 17160
auxnear_name Aux_Near
auxnear_site_name
auxnear_site_status online
auxnear_ip1 x.xxx.xxx.xx
auxnear_ip1_status reachable
auxnear_ip2
auxnear_ip2_status not_configured
auxnear_port 17161
auxfar_name Auxfar_MM
auxfar_site_status online
auxfar_ip1 x.xxx.xxx.xxx
auxfar_ip1_status reachable
auxfar_ip2
auxfar_ip2_status not_configured
auxfar_port 17162
username rontsu
keyfile /root/.ssh/pw_rsa
topology metromirror
orchestrator_version 4.1.220922160427
orchestrator_ha_status online

Now active and standby orchestrators are configured successfully.