ESS Quick Deployment Guide
This guide is for system administrators, installers, and programmers of IBM Storage Scale clusters who are experienced with the operating systems on which each IBM Storage Scale cluster is based.
![Start of change](./delta.gif)
![End of change](./deltaend.gif)
ESS quick deployment sheet
![Quick deployment steps](ESS_QUICK_SHEET_620.png)
Support matrix
Release | OS | Runs on | Can upgrade or deploy |
---|---|---|---|
ESS Utility Node | Red Hat® Enterprise Linux 9.2 (PPC64LE) | N/A |
|
![]() ![]() |
![]() ![]() |
![]()
![]() |
![]()
![]() |
ESS 3200 ![]() ![]() |
Red Hat Enterprise Linux 8.8 (x86_64) |
|
|
ESS 3000 6.2.0.1 | Red Hat Enterprise Linux 8.8 (x86_64) |
|
|
ESS 5000 ![]() ![]() |
Red Hat Enterprise Linux 8.8 (PPC64LE) |
|
|
1 x86 EMS (BYOE) can only upgrade or deploy the ESS 3500 node(s) and the VM image itself. |
Network requirements
![1-Gb network switch](ess_1gbnetworkswitch.png)
![Logical view of the two switches](ess_switchesview.png)
Code version
All supported ESS nodes are supported within two editions: Data Management Edition and Data Access Edition. An example of package names is as follows:
![Start of change](./delta.gif)
ess_6.2.0.1_0430-19_dme_ppc64le.tar.xz
ess_6.2.0.1_0430-19_dae_ppc64le.tar.xz
ess_6.2.0.1_0430-19_dme_x86_64.tar.xz
ess_6.2.0.1_0430-19_dae_x86_64.tar.xz
![End of change](./deltaend.gif)
- The versions shown here might not be the GA version available on IBM® Fix Central. It is recommended to go to IBM Fix Central and download the latest code.
- ppc64le in the package name implies that each container runs on a POWER®-based EMS. For details about functions supported by respective containers, see Support matrix.
- The x86 packages run on ESS Utility Node EMS or BYOE.
Scale_System_DME_UNIFIED-6.2.0.1-x86_64-EMS.tgz
Scale_System_DAE_UNIFIED-6.2.0.1-x86_64-EMS.tgz
Scale_System_DME_UNIFIED-6.2.0.1-ppc64LE-EMS.tgz
Scale_System_DAE_UNIFIED-6.2.0.1-ppc64LE-EMS.tgz
![Start of change](./delta.gif)
Upgrade guidance
Review the IBM Storage Scale System (https://www.ibm.com/support/pages/ibmsearch?tc=STHMCM&dc=D600&&sortby=desc) and IBM Storage Scale (https://www.ibm.com/support/pages/ibmsearch?tc=STXKQY&dc=D600&&sortby=desc) flashes and advisories before an upgrade to decide which version would be better to upgrade IBM Storage Scale System.
![](ess_upgrade_chart_1.png)
![Start of change](./delta.gif)
- Upgrades to ESS 6.1.2.x follow the N-2 rule. You can upgrade from ESS 6.1.2.x, 6.1.1.x (that is, 6.1.1.2) or 6.1.0.x.
- Upgrades to ESS 6.1.5.x follow N-3 rule. You can upgrade from 6.1.2.x, 6.1.3.x, and 6.1.4.x.
Starting with ESS 6.1.5.x, further jumps adhere to the N-3 rule
![End of change](./deltaend.gif)
![End of change](./deltaend.gif)
Node classes
All building blocks have node classes except the EMS node. Instead of a node list, you can use these node classes in the essrun command when the inventory file contains these nodes. (The essrun config load command adds the nodes to the inventory file.)
![Start of change](./delta.gif)
- 5000: ess_ppc64le
- 3000: ess_x86_64
- 3200: ess3200_x86_64
- 3500: ess3500_x86_64
Protocol Power9: ces_ppc64le
- 6000: s6k_x86_64
![End of change](./deltaend.gif)
Deployment/upgrade instructions
- Log in to the EMS (over management) and set root password.
- Check whether the campus connection is set by using nmtui to set an address.
- Set the EMS hostname.
- Log out and log in over the campus connection.
- Set up the /etc/hosts
file.
127.0.0.1 localhost localhost.localdomain.local localhost4 localhost4.localdomain4 ## Management IPs 192.168.45.0/24 192.168.45.20 ems1.localdomain.local ems1 192.168.45.21 essio1.localdomain.local essio1 192.168.45.22 essio2.localdomain.local essio2 192.168.45.23 prt1.localdomain.local prt1 192.168.45.24 prt2.localdomain.local prt2 ## High-speed IPs 10.0.11.0/24 10.0.11.1 ems1-hs.localdomain.local ems1-hs 10.0.11.2 essio1-hs.localdomain.local essio1-hs 10.0.11.3 essio2-hs.localdomain.local essio2-hs 10.0.11.4 pr1-hs.localdomain.local prt1-hs 10.0.11.5 pr2-hs.localdomain.local prt2-hs ## Protocol CES IPs 10.0.11.100 prt_ces1.localdomain.local prt_ces1 10.0.11.101 prt_ces1.localdomain.local prt_ces1 10.0.11.102 prt_ces2.localdomain.local prt_ces2 10.0.11.103 prt_ces2.localdomain.local prt_ces2
- Copy the GA code into the /home/deploy directory.
- Decompress the inner xz
file.
xz --decompress ess_6.2.0.1_0430-19_dme_ppc64le.tar.xz
Note: You can choose a DME or DAE file according to the configuration. - Extract tar file.
tar xvf ess_6.2.0.1_0430-19_dme_ppc64le.tar.xz
- Run the installer.
- Start the
container.
sh ess_6.2.0.1_0430-19_dme_ppc64le
- Before the upgrade from a lower version than IBM Storage Scale
System 6.1.8.x, run a cleanup, and use a container
name that is not resolvable. Complete the following steps for the cleanup:
- Check whether the current EMS FQDN essems1.gpfs.net correct.
- Provide the desired and resolvable container hostname.
- Provide the FSP container IP of the container.
- If an inventory file exists, clean up it.
- Start the
container.
- Run Config load.
essrun -N ems1,essio1,essio2 config load -p
Attention: Protocol nodes in the container need not to be updated. Therefore, do not select protocol nodes when you issue this command. - Run update
--precheck.
essrun -N ems1,essio1,essio2 update --precheck
- Update EMS.When you upgrade ESS 5000 nodes, you cannot upgrade the firmware because of a restriction. For example,
Add the --offline option for an offline upgrade and the --online option an online only upgrade.essrun -N ess5kio1,ess5kio2 updateLe
- Update EMS offline.
essrun -N ems1 update --offline
- If you are prompted to reboot then run the command again.
- If you need to restart the container after reboot run the following command:
./essmkyml --restart
- Update the EMS again.
essrun -N ems1 update --offline
- Update EMS offline.
- Update I/O nodes.
- Update I/O nodes
online.
essrun -N <Node List/Node Name> update
- Update I/O nodes
offline.
essrun -N <Node List/Node Name> update --offline
- Update I/O nodes
online.
- Update POWER firmware. For more information see, Upgrading POWER9 firmware appendix in ESS Deployment Guide.
- Create network
bonds.
essrun -N ems1,essio1,essio2 network --suffix=-hs
- Run network
test.
ssh essio1
ESSENV=TEST essnettest -N essio1,essio2 --suffix=-hs
- Create a
cluster.
essrun -N <Node List/Node Name> cluster --suffix=-hs
- Add EMS.
essrun -N essio1 cluster --add-ems ems1 --suffix=-hs
- Create a file
system.
essrun -N ess3500_x86_64 filesystem --name fs1 --suffix=-hs
Note: For ESS 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). - Final installation check per node.
essinstallcheck -N localhost
- Check whether all nodes
performance.
gnrhealthcheck
mmhealth node show -a
- Set up Chrony/NTP.
- Set up call home.
- Enable added security (SELinux/firewall/sudo/admin central).
- Configure the
GUI/collectors.
essrun -N ems1,essio1,essio2 gui --configure
- Set up conserver.
- Set up protocol services (3500 or P8/P9 Protocol nodes or ESS Utility Protocol Node).
- Set up client nodes.