Problems due to using the installation toolkit for functions or configurations not supported

Use this information to determine node types, setups, and functions that are supported by the installation toolkit, and to understand how to use the toolkit if a setup is not fully supported.

Support for mixed mode of install, deploy, or upgrade
Support for DMAPI enabled nodes
Support for ESS cluster

Support for mixed mode of install, deploy, or upgrade

You want to use the installation toolkit but you already have an existing cluster. Can the installation toolkit auto-detect your cluster or do you need to manually configure the toolkit?

The installation toolkit is stateless and it does not import an existing cluster configuration into its cluster definition file. As a workaround to this scenario, use the steps that are mentioned in the following sections of the .

If NSDs and file systems exist, you do not need to provide that information to the installation toolkit.

What are valid starting scenarios for which the installation toolkit can be used for an installation or a deployment or an upgrade?

Scenario	Installation toolkit support
No cluster exists and no GPFS RPMs exist on any nodes.	The installation toolkit can be used to install GPFS and create a cluster.
No cluster exists and GPFS RPMs are already installed on nodes.	The installation toolkit can be used to install GPFS and create a cluster.
No cluster exists.	The installation toolkit can be used to configure NTP during GPFS installation and cluster configuration.
A cluster exists.	The installation toolkit can be used to add NSDs.
A cluster exists.	The installation toolkit can be used to add nodes (manager, quorum, admin, nsd, protocol, gui).
A cluster exists and NSDs exist.	The installation toolkit can be used to add file systems.
A cluster exists and some NSDs exist.	The installation toolkit can be used to add more NSDs.
A cluster exists and some protocols are enabled.	The installation toolkit can be used to enable more protocols.
A cluster exists and performance monitoring is enabled.	The installation toolkit can be used to reconfigure performance monitoring.
An ESS cluster exists and protocol nodes are added.	The installation toolkit can be used to add protocols to protocol nodes.
SLES 12, Windows, Ubuntu 16.04, RHEL 7.1, and AIX® nodes exist along with RHEL 8.x, Ubuntu 20.04, and SLES 15 nodes.	The installation toolkit can be used only on RHEL 8.x and 7.x (7.7 and later), Ubuntu 20.04, and SLES 15 nodes.
A cluster is at mixed levels.	The installation toolkit can be used to upgrade all nodes or a subset of nodes to a common code level.

What are invalid starting scenarios for the installation toolkit?

NSDs were not cleaned up or deleted before a cluster deletion.
Unsupported node types were added to the installation toolkit.
File systems or NSDs are served by unsupported node types.
The installation toolkit cannot add or change the configuration. It can use only the file system paths for protocol configuration.
An ESS cluster exists and protocol nodes have not yet been added to the cluster.
Protocol nodes must first be added to the ESS cluster before the installation toolkit can install the protocols.

Does the installation toolkit need to have my entire cluster information?

No, but this depends on the use case. Here are some examples in which the installation toolkit does not need to be made aware of the configuration information of an existing cluster:

Deploying protocols on protocol nodes: The installation toolkit needs only the protocol nodes information and that they are configured to point to cesSharedRoot.
Upgrading protocol nodes: The installation toolkit can upgrade a portion of the cluster such as all protocol nodes. In this case, it does not need to be made aware of other NSD or client/server nodes within the cluster.
Adding protocols to an ESS cluster: The installation toolkit does not need to be made aware of the EMS or I/O nodes. The installation toolkit needs only the protocol nodes information and that they are configured to point to cesSharedRoot.
Adding protocols to a cluster with AIX, SLES 12, Debian, RHEL6, and Windows nodes: The installation toolkit does not need to be made aware of any nodes except for the RHEL 8.x, RHEL 7.x (7.7 or later), Ubuntu 20.04, and SLES 15 protocol nodes. The installation toolkit needs only the protocol nodes information and that they are configured to point to cesSharedRoot.

Can the installation toolkit act on some protocol nodes but not all?

Protocol nodes must always be treated as a group of nodes. Therefore, do not use the installation toolkit to run install, deploy, or upgrade commands on a subset of protocol nodes.

Support for DMAPI enabled nodes

On nodes with DMAPI enabled, the installation toolkit does not provide much help to users in case of an error including whether a DMAPI related function is supported or unsupported.

Use the following steps to verify whether DMAPI is enabled on your nodes and to use the installation toolkit on DMAPI enabled nodes.

Verify that DMAPI is enabled on a file system by using the following command:

 mmlsfs all -z
File system attributes for /dev/fs1:
====================================
flag                value                    description
------------------- ------------------------ -----------------------------------
-z                 yes                      Is DMAPI enabled?

Shut down all functions that are using DMAPI and unmount DMAPI by using the following steps:
1. Shut down all functions that are using DMAPI. This includes HSM policies and IBM Spectrum Archive.
2. Unmount the DMAPI file system from all nodes by using the following command:
```
 mmunmount fs1 -a
```
  Note: If the DMAPI file system is also the CES shared root file system, then you must first shut down GPFS on all protocol nodes before unmounting the file system.
  1. Check whether the DMAPI file system is also the CES shared root file system, use the following command:
```
 mmlsconfig | grep cesSharedRoot  
```
  2. Compare the output of this command with that of Step 1 to determine whether the CES shared root file system has DMAPI enabled.
  3. Shut down GPFS on all protocol nodes by using the following command:
```
 mmshutdown -N cesNodes
```
3. Disable DMAPI by using the following command:
```
 mmchfs fs1 -z no
```
If GPFS was shut down on the protocol nodes in one of the preceding steps, start GPFS on the protocol nodes by using the following command:
```
 mmstartup -N cesNodes
```
Remount the file system on all nodes by using the following command:
```
 mmmount fs1 -a
```
Proceed with using the installation toolkit as now it can be used on all file systems.
After the task is done by using the installation toolkit is completed, enable DMAPI by using the following steps:
1. Unmount the DMAPI file system from all nodes.
  Note: If the DMAPI file system is also the CES shared root file system, shut down GPFS on all protocol nodes before unmounting the file system.
2. Enable DMAPI by using the following command:
```
 mmchfs fs1 -z yes
```
3. Start GPFS on all protocol nodes.
4. Remount the file system on all nodes.

Support for ESS cluster

For information on using the installation toolkit with a cluster containing ESS, see :