Populating cluster definition file with current cluster state using the installation toolkit

You can use the installation toolkit to populate the cluster definition file with the current cluster state.

Before using this functionality, review its limitations. For more information, see Limitations of config populate option of the installation toolkit.

Note: If you are using the object protocol or proxy enabled call home, the config populate functionality does not extract any password from the current cluster configuration. You must enter the password when prompted.

In the following scenarios, you might need to update the cluster definition file with the current cluster state:

A manually created cluster in which you want to use the installation toolkit
A cluster created using the installation toolkit in which manual changes were done

Use the installation toolkit to populate the cluster definition file as follows:

Define the installer node by issuing the ./spectrumscale setup -s InstallNode command.
Repopulate the cluster definition file with the current cluster state by issuing the ./spectrumscale config populate --node Node command.
Note: This command creates the backup of the existing cluster definition file and it creates a new cluster definition file.
- You can pass --skip nsd flag with config populate command to skip the nsd and filesystem details.
```
./spectrumscale config populate -N node --skip nsd
```
- In a cluster containing ESS, you must specify the EMS node with the config populate command. For example:
```
./spectrumscale config populate --node EMSNode
```
- You can also use this functionality to populate the cluster definition file with file audit logging and call home related information.

If you are performing an upgrade, proceed with the rest of the upgrade steps. For more information, see Upgrading IBM Storage Scale components with the installation toolkit.