Using the deployment GUI

After successful configuration of the IBM Storage Scale System deployment GUI container and IBM Storage Scale System API server container, you can access the deployment GUI to complete the deployment of IBM Storage Scale Systems.

Ensure that the prerequisites are completed on the system. For more information, see Prerequisites.

To deploy IBM Storage Scale System by using the GUI, complete the following steps:

In a browser, go to the following URL to access the deployment GUI. Replace the <utilityBareMetalIP> with the IP address of the Utility Node.
```
https://<utilityBareMetalIP>:30443/
```
The IBM Storage Scale System deployment GUI wizard is displayed only if the deployment GUI server container is configured correctly. Also, ensure that the machine running the browser can access the GUI port of the Utility Bare-metal server.
In the Welcome section, select the I have placed the Management Server VM QCOW2, Script and the Storage Scale System Build file in the / serv directory on the Utility Bare Metal checkbox.
Select the I accept the License Agreement checkbox to review and accept the license agreement.
After you review the license agreement, click Close on License Agreement. Then, click Next.
In the Network Settings section, follow these steps:
1. Enter the Management Mask and FSP OS Mask values.
2. If required, turn on the Use High-speed Network option.
  The system enables additional options.
3. Turn on Skip Automatic High-speed Network Setup (Requires an existing high-speed network).
  When this option is enabled, the system does not create network bonds on the I/O nodes. Because the system creates only the EMS VM, it creates the required network bonds only on the EMS VM by using the provided configuration.
4. Select a High-speed Network Interface, and enter the High-speed Suffix.
5. Click Next.
In the Enterprise Management section, follow these steps:
1. Enter the Management Server FQDN.
2. Choose a License Type from the drop-down list.
3. Enter the Bare Metal Server Root Password.
4. Turn on the following options based on your requirements:
  - Re-use existing VM EMSVM and skip EMSVM creation
  - Re-use existing VM CESVM and skip CESVM creation
5. Click Next.
In the Node Configuration section, follow these steps:
1. Follow the on-screen instructions to download the CSV template, enter the node details, and upload the file to add the configuration details for multiple nodes.
2. To add nodes individually, click Add, and enter the details manually.
  Note:
  - Use short hostnames (for example, node01), not fully qualified domain names (such as node01.example.com).
  - For the management server virtual machine, use the BMC user and BMC password that are used for the underlying IBM Utility Bare-metal server.
  - For serial numbers, add the IBM serial number provided by the IBM Service Support Representative (SSR) during installation. You can also retrieve the serial number of the nodes by running the essgetconfig command from the CLI.
  - The Utility Hostname and Utility Host IP fields are applicable only for the Protocol VM, AFM Gateway, and Client VM node types.
3. Turn on Reuse Existing EMS VM.
  - With the Skip Automatic High-speed Network Setup enabled, the system uses the existing EMS VM and does not create any network bonds. The system expects all required bonds on both the IO nodes and the EMS VM to already exist. You must manually configure all network bonds before deployment.
  - With the Skip Automatic High-speed Network Setup disabled, the system uses the existing EMS VM but automatically creates the required network bonds on both the IO nodes and the EMS VM based on the configuration that you provide. No manual bond configuration is required unless otherwise specified.
4. Click Next.
In the Cluster Settings section, follow these steps:
1. Enter the Cluster Name and the Storage Scale System Build file name.
2. Click Next.
(Optional) In the Campus Settings section, update the following values, and then click Next:
- Campus Gateway
- Campus IP
- Campus Mask
In the Create File Systems section, update the following details:

Note: If you have enabled the Protocol VM option, you must create a file system and then configure protocols. Otherwise, you can skip this section.
1. Enter a Filesystem Name.
2. Select the nodes from the drop-down list
3. Turn on Create CES Shared Root, and then update the Select Nodes details.
4. Click Next.
In the Configure Protocols section, update the required details based on your previous selections.
(Optional) In the Configure GUI section, create the GUI credentials by entering a username and password, and then click Next.
In the Review Configuration section, verify the details, and then click Start Deployment.
The system displays a confirmation pop-up.
If you want the deployment to stop when an existing EMS VM or Deployment Container is detected, turn on the required option in the Clean-up section.

Note: If you have already enabled the Reuse existing EMS VM option in the Node Configuration section, the system doesn’t display the Clean-up options.
Click Start Deployment.
The deployment begins, and the system displays a message after the deployment is complete.
Note:
- The deployment fails if any existing management server VM or deployment container is detected.
- Deployment runs independently of the browser. You can refresh or close the browser and log in again to view the progress, as long as the deployment continues without errors.
- If the deployment stops due to an error, download the log file to review the output and troubleshoot the issue. After resolving the error, you must restart the deployment from the beginning.
- In the Deployment has been completed successfully dialog, the management GUI for your IBM Storage Scale System is generated automatically based on the IP address provided in the node configuration.
- If the deployment fails or is partially completed, clean up the incomplete deployment before you retry or restart the deployment. Otherwise, the system might detect a partially deployed cluster and redirect you to the Upgrades page instead of starting a new deployment.
Click Finish to complete the deployment.