Add New Member operation

You can update the deployment of your IBM Storage Scale ServerPrimary configuration by adding a new Mirror or Tiebreaker configuration to the IBM Storage Scale cluster.

About this task

You can add one configuration at a time, keeping in mind the following conditions:

You must add a Mirror configuration before you add a Tiebreaker configuration.
This Add New Member operation can be run only on a IBM Storage Scale Primary deployment, or on a IBM Storage Scale deployment that is behaving as a Primary configuration (for example, a IBM Storage Scale Mirror configuration deployment that has been elected by the Tiebreaker instance to run as the Primary configuration and receive IBM Storage Scale Client requests).
You cannot attach a Mirror or Tiebreaker configuration if it was previously used. Be sure to attach a newly deployed Mirror or Tiebreaker configuration.

Procedure

Expand the Manage Cluster section of the GPFS_Manager operations.
Expand the Add New Member node.
In the Member Type field, select the IBM Storage Scale Configuration type (Mirror or Tiebreaker) to add to the cluster.
In the Manager IP field, enter the IP address of the GPFS_Manager virtual machine deployed with the specified type of configuration that you are adding to this Primary configuration.
If you are adding an external IBM Storage Scale Tiebreaker node, enter the IP address of the system where the external IBM Storage Scale Tiebreaker node is located.
Click Submit.
Click Confirm when asked to validate your request.

Results

A new entry is displayed under the Operation Execution Results list, with the name Add New Member. When completed, the status of the operation changes from Active to Done.

If you are adding a Mirror configuration, you get one of the following results:

Success: The primary configuration is able to communicate with the GPFS_Manager virtual machine for the Mirror configuration. The result of the operation is available as a link in the Return Value column of the Operation Execution Results list. Click the link to display the output of the operation and to verify that the log is clean.
Error: The specified Mirror configuration is already part of another IBM Storage Scale cluster.
You receive an error message in the log, indicating that the node was not added to the cluster, because the node already belongs to a IBM Storage Scale cluster.
Error: The Primary configuration already has a Mirror configuration attached.
You receive an error message, indicating that you cannot attach a Mirror configuration to a Primary configuration if one is already attached.
Error: The Primary configuration already has a Passive configuration attached.
You receive an error message indicating that you cannot attach a Mirror or Tiebreaker configuration to a Primary configuration if a Passive configuration is already attached.
Error: The Primary configuration was not able to communicate with the GPFS_Manager virtual machine for the Mirror configuration.
You receive an error message, similar to the following example:
```
GPFS-Manager.11402320054789.GPFS_Manager: Add Mirror Error: Unable to communicate with the mirror manager [1.1.1.1]. Make sure this is a Mirror Manager IP and that the same key management is set on the Mirror Manager.
```
This error might occur for either of the following reasons:
- The specified IP address of the GPFS_Manager virtual machine for the deployed Mirror configuration is incorrect. To recover, enter the correct IP address and run the operation again.
- The IBM Storage Scale Mirror instance does not have the IBM Storage Scale Managers Key that matches the IBM Storage Scale Managers Key for the IBM Storage Scale Primary configuration. To recover, retrieve the IBM Storage Scale Managers Key from this Primary instance, then install this key on the Mirror instance. For more information on how to retrieve and install keys, see the Related link.
  After you install the IBM Storage Scale Managers Key on the IBM Storage Scale Mirror instance, return to this IBM Storage Scale Primary instance and run this operation again.

If you are adding a Tiebreaker configuration, you get one of the following results:

Success: The primary configuration is able to communicate with the GPFS_Manager virtual machine for the Tiebreaker configuration. The result of the operation is available as a link in the Return Value column of the Operation Execution Results list. Click the link to display the output of the operation and to verify that the log is clean.
Error: The Primary configuration does not already have a Mirror configuration attached.
You receive an error message, similar to the following example, indicating that you must attach a Mirror configuration to a Primary configuration first, and then attach the Tiebreaker configuration:
```
GPFS-Manager.11403009527517.GPFS_Manager: Add Tie Error: This configuration has no mirror. Before you add the tie <ip_address> you need to attach the mirror.
```
Error: The Primary configuration already has a Passive configuration attached.
You receive an error message indicating that you cannot attach a Mirror or Tiebreaker configuration to a Primary configuration if a Passive configuration is already attached.
Error: The Primary configuration was not able to communicate with the GPFS_Manager virtual machine for the Tiebreaker configuration.
You receive an error message, similar to the following example:
```
GPFS-Manager.11402320054789.GPFS_Manager: Add Tie Error: Unable to communicate with the tie manager [1.1.1.1]. Make sure this is a Tiebreaker Manager IP and that the same key management is set on the Tiebreaker Manager.
```
This error might occur for either of the following reasons:
- The specified IP address of the GPFS_Manager virtual machine for the deployed Tiebreaker configuration is incorrect. To recover, enter the correct IP address and run the operation again.
- The IBM Storage Scale Tiebreaker instance does not have the IBM Storage Scale Managers Key that matches the IBM Storage Scale Managers Key for the IBM Storage Scale Primary configuration. To recover, retrieve the IBM Storage Scale Managers Key from this Primary instance, then install this key on the Tiebreaker instance. For more information on how to retrieve and install keys, see the Related link.
  After you install the IBM Storage Scale Managers Key on the IBM Storage Scale Tiebreaker instance, return to this IBM Storage Scale Primary instance and run this operation again.

If you are adding a Passive configuration, you get one of the following results:

Success: The primary configuration is able to communicate with the GPFS_Manager virtual machine for the Passive configuration. The result of the operation is available as a link in the Return Value column of the Operation Execution Results list. Click the link to display the output of the operation and to verify that the log is clean.
Error: The specified Passive configuration is already part of another IBM Storage Scale cluster.
You receive an error message in the log, indicating that the node was not added to the cluster, because the node already belongs to a IBM Storage Scale cluster.
Error: The Primary configuration already has a Passive configuration attached.
You receive an error message, indicating that you cannot attach a Passive configuration to a Primary configuration if one is already attached.
Error: The Primary configuration already has a Mirror configuration attached.
You receive an error message indicating that you cannot attach a Passive configuration to a Primary configuration if a Mirror configuration is already attached.
Error: The Primary configuration was not able to communicate with the GPFS_Manager virtual machine for the Passive configuration.
You receive an error message, similar to the following example:
```
GPFS-Manager.11402320054789.GPFS_Manager: Add Passive Error: Unable to communicate with the passive manager [1.1.1.1]. Make sure this is a Passive Manager IP and that the same key management is set on the Passive Manager.
```
This error might occur for either of the following reasons:
- The specified IP address of the GPFS_Manager virtual machine for the deployed Passive configuration is incorrect. To recover, enter the correct IP address and run the operation again.
- The IBM Storage Scale Passive instance does not have the IBM Storage Scale Managers Key that matches the IBM Storage Scale Managers Key for the IBM Storage Scale Primary configuration. To recover, retrieve the IBM Storage Scale Managers Key from this Primary instance, then install this key on the Passive instance. For more information on how to retrieve and install keys, see the Related links.
  After you install the IBM Storage Scale Managers Key on the IBM Storage Scale Passive instance, return to this IBM Storage Scale Primary instance and run this operation again.