Upgrading from 4.1.1 to 4.2

Why this post ?

Upgrading spectrum scale is as easy as pie. In this post I demonstrate how to upgrade Spectrum Scale from 4.1.1 to 4.2.0.

Where to start ?

Let's start with a Spectrum Scale 4.1.1 cluster.

Here is my 4.1.1 Cluster details -

[root@vwnode1 ~]# mmlscluster

GPFS cluster information
========================
  GPFS cluster name:         vwnode.gpfscluster
  GPFS cluster id:           1175018713363073732
  GPFS UID domain:           vwnode.gpfscluster
  Remote shell command:      /usr/bin/ssh
  Remote file copy command:  /usr/bin/scp
  Repository type:           CCR

 Node  Daemon node name  IP address    Admin node name  Designation
--------------------------------------------------------------------
   1   vwnode1           XXX.XXX.100.111  vwnode1          quorum
   2   vwnode2           XXX.XXX.100.112  vwnode2          quorum
   3   vwnode3           XXX.XXX.100.113  vwnode3          quorum-manager
   4   vwnode4           XXX.XXX.100.114  vwnode4          manager

Let's upgrade

Extract brand new Spectrum Scale ( 4.2.0.1 in my case )

[root@vwnode1 ~]# ./Spectrum_Scale_install-4.2.0.1_x86_64 --silent > /dev/null

You can either fill-up all cluster definition using 'specturmscale' command or just copy old cluster definition file if there is no change in cluster since installation.

[root@vwnode1 images]# cp 
/usr/lpp/mmfs/4.1.1/installer/configuration/clusterdefinition.txt 
/usr/lpp/mmfs/4.2.0.1/installer/configuration/clusterdefinition.txt
cp: overwrite â/usr/lpp/mmfs/4.2.0.1/installer/configuration/clusterdefinition.txtâ? y
[root@vwnode1 images]# 

 You will see lots of warnings if you check for object parameters

[root@vwnode1 images]# /usr/lpp/mmfs/4.2.0.1/installer/spectrumscale config object
[ INFO  ] No changes made. Current settings are as follows:
[ INFO  ] Object File System Name is cesSharedRoot
[ INFO  ] Object File System Mountpoint is /ibm/cesSharedRoot
[ INFO  ] Endpoint Hostname is viknode
[ WARN  ] No value for GPFS Object Base in clusterdefinition file.
[ WARN  ] No value for GPFS Fileset inode allocation in clusterdefinition file.
[ WARN  ] No value for Admin Token in clusterdefinition file.
[ WARN  ] No value for Admin User in clusterdefinition file.
[ WARN  ] No value for Admin Password in clusterdefinition file.
[ WARN  ] No value for Swift User in clusterdefinition file.
[ WARN  ] No value for Swift Password in clusterdefinition file.
[ WARN  ] No value for Database Password in clusterdefinition file.
[ INFO  ] Enable S3 is off
[ WARN  ] No value for Multi-region Data File Path in clusterdefinition file.
[ WARN  ] No value for Region Number for Multi-region in clusterdefinition file.

We need to specify following parameters in order to configure upgrade.

ap  -- Specify the password for the Admin User
dp  -- Specify the password for object database
i     -- Specify the GPFS fileset inode allocation to be used
o    -- Specify the GPFS fileset to be created/used as the

[root@vwnode1 ~]# /usr/lpp/mmfs/4.2.0.1/installer/spectrumscale config object -o my_object_fileset -ap Passw0rd -dp Passw0rd -i 10000
[ INFO  ] Setting GPFS Object Base to my_object_fileset
[ INFO  ] Setting GPFS Fileset inode allocation to 10000
Enter the secret encryption key:
Repeat the secret encryption key:
[ INFO  ] Setting Admin Password
[ INFO  ] Setting Database Password

We also need to configure perform monitoring.
You can either enable or disable performance monitoring as per your requirement.

[root@vwnode1 ~]# /usr/lpp/mmfs/4.2.0.1/installer/spectrumscale config perfmon -r on
[ INFO  ] Setting Enable Performance Monitoring reconfiguration to on

We should do precheck before upgrade.

[root@vwnode1 ~]# /usr/lpp/mmfs/4.2.0.1/installer/spectrumscale upgrade -pr

If upgrade pre-check is successful,  we are ready for upgrade.
Just fire following command which will do upgrade -

[root@vwnode1 ~]# /usr/lpp/mmfs/4.2.0.1/installer/spectrumscale upgrade

Done !

Let's confirm using 'mmfsadm'

[root@vwnode4 ~]# mmfsadm dump version | head -1
Build branch "4.2.0.1 ".