Setting up the new cluster in parallel with the original cluster

A parallel upgrade allows you to maintain your existing Platform Symphony cluster while upgrading to the new version of IBM® Spectrum Symphony. First plan appropriately so that you avoid conflicts with the original cluster, then install and configure IBM Spectrum Symphony 7.3.2 with your existing cluster.

1. On Linux®, to avoid conflicts with the original cluster, complete these tasks before installing the new version of IBM Spectrum Symphony:
   1. Specify a new connection base port that is different to the one you are using in your original cluster.
      For example, run:

      setenv BASEPORT 9100

   2. Specify advanced workload execution mode so the new cluster will have the same functionality as the original cluster.
      For example, run:

      setenv SIMPLIFIEDWEM N

2. Install and entitle IBM Spectrum Symphony and on the primary host, configure it, but do not start or test it.
   Refer to Installing and configuring IBM Spectrum Symphony for details, and also consider the following information:

   • On Linux:
     • Specify a different installation directory and different base port. You will probably install with the --prefix option.
     • Set up automatic startup as usual. This will break the feature in the original cluster.
     • When granting root privileges for the egoadmin user, the ego.sudoers file already exists, so use the -p option.
       For example, run:

       egosetsudoers.sh -p

     • Join the cluster as usual.
     • Define the host as a management host, as usual.
   • On Windows:
     • Specify the following parameters when you install. All management hosts in the new cluster must use the same value for each parameter:
       1. For the Installation Directory, specify a path to the new installation directory.
       2. For the Connection Base Port, specify a new connection base port.
       3. For the Cluster Name, specify a different cluster name from the original cluster. You only require setting the cluster name on the primary host.
          Note: Do not use the name of a host or user as the name of your cluster. A suitable name contains no more than 39 uppercase or lowercase characters, numbers, the underscore character (_), or a combination. The name cannot contain spaces, or other special characters (such as an ampersand (&)).

          These names are valid:

          • London_123
          • test_grid
          • 333111

          These names are not valid:

          • A&B
          • grid 22

          Additionally, do not use dates or versions to identify the services because future updates may change the version of the cluster without changing the cluster ID.

       4. If you are prompted for the Cluster ID while installing on a host, specify a different cluster ID from the original cluster (for example, use the cluster name as the cluster ID), and use the same Cluster ID value on every host in the new cluster.
       5. Choose advanced workload execution mode.
3. Install IBM Spectrum Symphony on the remaining management hosts, and configure the hosts, but do not start or test them. Note the same considerations as in step 2.
4. If you have Linux and Windows compute hosts, install IBM Spectrum Symphony on these hosts, configure the hosts, but do not start or test them. Note the same considerations as in step 2.
5. Configure your new cluster:
   1. On Linux, join the primary host and set entitlement. For details, see Setting entitlement on the Linux primary host and starting the cluster. Note that on Windows, entitlement is part of the installation wizard.
   2. Set mast host failover and a shared directory. For details, see Setting up primary host failover.