Creating a cluster
Create a cluster and add multiple nodes to provide shared storage.
- Create a cluster.

essrun -N <IOnodeclasses> cluster --suffix=-hs
Where the I/O node classes can be similar to the ones in the following examples:- IBM Storage Scale System
3000:
ess30001aandess30001b - IBM Storage Scale System
3500:
ess35001aandess35001b - IBM Storage Scale System
6000:
ess60001aandess60001b
Tip: Use the optional parameters of the essrun command to customize your clusters.For more information, see essrun command in the IBM Storage Scale Systems Command Reference.
- IBM Storage Scale System
3000:
- Add a management server node to the cluster.
essrun -N<IOnode1>cluster --add-ems<MS1>--suffix=-hs - Create a file system.

essrun -N ess3500_x86_64 filesystem --name fs1 --suffix=-hs
Tip: Use the optional parameters of the essrun command to customize your file systems.For more information, see essrun command in the IBM Storage Scale Systems Command Reference
Note:- By default, this command attempts to use all the available space. If you need to create multiple
file systems or a CES shared root file system for protocol nodes, consider by using less space. For
example:

essrun -N<IOnoden>filesystem --suffix=-hs --size 80%
For more options such as blocksize, filesystem size, or RAID code, see
the essrun command in the IBM Storage Scale
System Command Reference.
- This step creates combined metadata + data vdisk sets by using a default RAID code and block size. You can use additional flags to customize or use the mmvdisk command directly for advanced configurations.
If you are updating IBM Storage Scale System
3000,
IBM Storage Scale System
3200, and IBM Storage Scale System
3500
the default set-size is 80% and it must not
be increased.
If you are updating IBM Storage Scale System
5000, the default set-size is
100%.
For additional options, see essrun command. The default block size for
PPC64LE is 16M whereas for IBM Storage Scale System
3000 it is 4M. 
If you are deploying protocol nodes, make sure that you leave space
for CES shared root file system. Adjust the set-size slightly lower when you are creating this
required file system for protocol nodes.
- For IBM Storage Scale System 3500, you must keep 1.5 TB or more space free if future capacity MES is planned (performance to hybrid). Thus, it is recommended to not use all available space when you create a file system for the performance model. The default allocation is 80% of available space when you use the essrun filesystem command (for x86 nodes).
- Before you create a recovery group or a file system, check whether a self-encrypted drive (SED) is required. You cannot enroll recovery groups for the SED support after they are created.
- By default, this command attempts to use all the available space. If you need to create multiple
file systems or a CES shared root file system for protocol nodes, consider by using less space. For
example:
- Add the protocol node to the cluster.
For more information, see Creating a shared root file system for CES.
- Create a
cesSharedRootfile system (if you are deploying protocols).
For more information, see Adding and configuring protocols in an exiting cluster by using IBM Storage Scale installation toolkit.essrun -N<IOnode1>,<IOnode2>filesystem --ces