Planning for IBM Spectrum Virtualize 3-Site Orchestrator

To install, configure, and manage IBM Spectrum Virtualize 3-Site Orchestrator, the installation must meet several hardware, software, and system requirements.

The system supports IBM Spectrum Virtualize 3-Site Orchestrator to configure and manage Metro Mirror configurations that span three sites. In addition, on system models that support HyperSwap® configurations, you can use IBM Spectrum Virtualize 3-Site Orchestrator to extend the configuration to a third site. Both configurations require that you set up specific objects on each system and 3-Site Orchestrator settings.
Note: Only one instance of IBM Spectrum Virtualize 3-Site Orchestrator to manage the 3-site configuration is supported. Multiple instances can result in unexpected data consistency and inaccurate statuses of both the 3-site configuration and 3-site consistency groups.
IBM Spectrum Virtualize 3-Site Orchestrator Requirements
Ensure that the following requirements are met for IBM Spectrum Virtualize 3-Site Orchestrator:
  • Install Red Hat® Enterprise Linux® (RHEL) version 7.5, or later. Then, install the correct version of IBM Spectrum Virtualize 3-Site Orchestrator on an x64-bit architecture server.
  • The server must have a minimum of 4 GB of random access memory (RAM) and 4-core microprocessors.
  • The OpenSSH utility must be installed.
  • Passwordless SSH login must be available to all sites from the IBM Spectrum Virtualize 3-Site Orchestrator host.
  • Ensure connectivity between all sites and the Linux host where the IBM Spectrum Virtualize 3-Site Orchestrator is installed.
  • For HyperSwap configurations, the host can be physically at any of the three physical sites or at a fourth independent site. The host must have IP connectivity to the HyperSwap system and the auxiliary-far site.
Standby Orchestrator Requirements
Ensure that the following requirements are met for standby orchestrator:
  • The active orchestrator and the standby orchestrator must have access to the Auxfar site.
  • Ensure that 3SiteAdmin users are created on the target sites.
  • Ensure that the passwordless SSH connection between the host and target site is established with the same SSH keys (private and public keys). The path to the SSH key files must be the same on the active orchestrator and the standby orchestrator.
  • The required ports for communication are enabled on the active orchestrator and the standby orchestrator.
  • Ensure that a 3-site configuration is created on one of the orchestrators to configure that orchestrator as active.
Systems Requirements
Consider the following requirements for the systems:
  • If you are using 3-Site Orchestrator with Metro Mirror configurations, all systems must be running either the 8.3.1, 8.4.0, or later release.
    Note: To use the management GUI to configure and manage both 3-site configurations, all systems must be running the 8.4.0.1 release.
  • If you are using 3-Site Orchestrator with HyperSwap configurations, all systems must be running 8.4.0, or later release.
    Note: To use the management GUI to configure and manage both 3-site configurations, all systems must be running the 8.4.0.x release.
  • For both Metro Mirror and HyperSwap configurations, you can configure either a Fibre Channel or an IP partnership. Ensure that all prerequisites for or zoning and network configuration is completed before you configure the partnership.
  • Verify that the Remote Mirroring license is configured correctly per your license agreement on all systems in the 3-site configuration. In the management GUI, select Settings > System > Licensed Functions or use the chlicense command.
Firewall Requirements
For Metro Mirror configurations, three firewall ports must be open for events and SSH tunneling. For HyperSwap configurations, two firewall ports must be open for events and SSH tunneling. Also, port 7003 must be open for both configurations.