Software upgrade and firmware update
To improve stability, performance, and compatibility, upgrade an existing cluster and a file system.
Important: Before you upgrade, download the latest precheck tool from GitHub or obtain a static copy from IBM Fix Central unified container packaging. Extract the tool and run it on the ESS nodes in your cluster to validate system health. For instructions, see the README file in the GitHub repository.
- Upgrade methods
- You can upgrade IBM Storage Scale
System online or offline based
on system availability and maintenance planning. Upgrade can be done by using the following methods.
- Offline upgrade
- This method is faster than an online upgrade. The nodes are upgraded in parallel but the system is typically taken down for a period. You can update all nodes at the same time or a subset of them. Preferred when no cluster exists in the environment, or during a scheduled outage for the system.
- Online upgrade
- This method requires a cluster and file systems, or multiple clusters and file systems. The cluster stays fully available, but requires nodes to be upgraded in a specific order (usually one per building block) to keep recovery groups accessible all the time.
- Protocol nodes
-
- When upgrading protocol nodes, the essrun command does not automatically upgrade IBM Storage Scale. On protocol nodes, use the installation toolkit (recommended) or use the rpm command to upgrade IBM Storage Scale. For more information, see Upgrading IBM Storage Scale protocol nodes and Upgrading IBM Storage Scale components with installation kit.
- If protocol nodes are part of the upgrade procedure, see IBM Storage Scale supported upgrade paths for more information.
- Firmware updates
- After upgrading, use the essinstallcheck command to determine whether a firmware update is required.
- Support matrix
-
Table 1. IBM Storage Scale System supported online upgrade paths To 
7.0.1.0 7.0.0.2 6.2.3.6 6.2.3.5 6.2.3.2 6.2.3.1 6.2.2.0 6.2.1.1 6.2.1.0 6.1.9.8 6.1.9.4 6.1.5.1 6.1.2.9 From 
7.0.1.0 -- -- -- -- -- -- -- -- -- -- -- -- -- 7.0.0.2 
-- -- -- -- -- -- -- -- -- -- -- -- 7.0.0.1 

-- -- -- -- -- -- -- -- -- -- -- 7.0.0.0 

-- -- -- -- -- -- -- -- -- -- -- 6.2.3.6 

-- -- -- -- -- -- -- -- -- -- -- 6.2.3.5 


-- -- -- -- -- -- -- -- -- -- 6.2.3.4 



-- -- -- -- -- -- -- -- -- 6.2.3.3 



-- -- -- -- -- -- -- -- -- 6.2.3.2 



-- -- -- -- -- -- -- -- -- 6.2.3.1 




-- -- -- -- -- -- -- -- 6.2.3.0 





-- -- -- -- -- -- -- 6.2.2.1 





-- -- -- -- -- -- -- 6.2.2.0 





-- -- -- -- -- -- -- 6.2.1.1 






-- -- -- -- -- -- 6.2.1.0 







-- -- -- -- -- 6.2.0.1 








-- -- -- -- 6.2.0.0 








-- -- -- -- 6.1.9.8 








-- -- -- -- 6.1.9.7 









-- -- -- 6.1.9.6 









-- -- -- 6.1.9.5 









-- -- -- 6.1.9.4 









-- -- -- 6.1.9.3 










-- -- 6.1.9.2 










-- -- 6.1.9.1 










-- -- 6.1.9.0 










-- -- 6.1.8.3 










-- -- 6.1.8.2 










-- -- 6.1.8.1 










-- -- 6.1.8.0 










-- -- 6.1.6.1 










-- -- 6.1.6.0 










-- -- 6.1.5.1 










-- -- 6.1.5.0 











-- 6.1.4.1 











-- 6.1.4.0 











-- 6.1.3.1 











-- 6.1.3.0 











-- 6.1.2.9 











-- 6.1.2.8 












6.1.2.7 












6.1.2.6 












6.1.2.5 












6.1.2.4 












6.1.2.3 












6.1.2.2 












6.1.2.1 












6.1.2.0 












- Legend
-
- --: Not applicable
: Supported
: Not supported
- General upgrade requirements
-
- Contact IBM Support when you want to upgrade from versions earlier than 6.1.2.0.
- Downgrades are not supported.
- LTS‑to‑LTS upgrade rules
- Upgrade to the latest level in the current LTS stream before you move to the next LTS level.
- Do not skip LTS levels.
- 6.1.2.x → 6.1.2.9 → 6.1.9.8 → 6.2.3.x
- Refer to the upgrade support matrix table for supported paths.
- Obtain required intermediate versions from IBM Support if these versions are not available on Fix Central.
Note:- Do not upgrade systems that are already on an LTS level to match incoming orders.
- Follow the latest LTS path to reach the target version.
- Building‑block integration
-
- Upgrade to the current LTS stream before adding a new building block.
- Do not integrate a building block that runs a newer LTS level than the existing system.
- Specific upgrade paths
-
- Upgrade from 6.1.9.4 to 6.2.3.4 by using 6.1.9.8 as an intermediate level.
- Direct upgrade from 6.1.2.9 to 6.2.3.x is not supported.
- N‑3 upgrade support
- Direct upgrades are supported within the N‑3 range. For example:
- 6.2.0.x , 6.2.1.x, or 6.2.2.x to 6.2.3.x
- N‑3 coexistence is supported only during the upgrade.
- Platform‑specific restrictions
- Upgrade from 6.2.0.0 or 6.2.0.1 to 6.2.3.x is not supported on Storage Scale System 3500 nodes.
- Upgrade from:
- 6.1.9.4 , 6.2.0.x, or 6.2.1.x (RHEL 9.2) to 6.2.3.5 (RHEL 9.6) is not supported.
- Perform an intermediate upgrade as defined in the upgrade support matrix.
- Supported configurations
-
Table 2. Supported configurations Management server Supported nodes IBM® Storage Scale System Utility Node - IBM Storage Scale System 3000 nodes
- IBM Storage Scale System 3200 nodes
- IBM Storage Scale System 3500 nodes
- IBM Storage Scale System 5000 nodes
- IBM Storage Scale System 6000 nodes
- IBM Storage Scale System Utility Node management server
- IBM Power9 management server
- IBM Power9 protocol node
- IBM Storage Scale System 3500 protocol node (virtual machine)
- IBM Storage Scale System Utility Node protocol node
IBM Power9 management server - IBM Storage Scale System 3000 nodes
- IBM Storage Scale System 3200 nodes
- IBM Storage Scale System 3500 nodes
- IBM Storage Scale System 5000 nodes
- IBM Power9 management server
- IBM Power9 protocol node
- IBM Storage Scale System 3500 protocol node (virtual machine)
Bring your own management server(BYOMS)- IBM Storage Scale System 3500 nodes
- IBM Storage Scale System 3500 protocol node (virtual machine)
- BYOMS (virtual machine)