Upgrading of IBM Storage Scale level with a security-related efix

While the best practice for upgrading IBM® Storage Scale Scale software level is through the Db2® fixpack update leveraging existing online or offline software update procedures, IBM Storage Scale security efix, which may be released in between Db2 fixpacks, requires manual installation procedures. The instructions outlined in this topic provides the steps of updating a Db2 pureScale® cluster with IBM Storage Scale security fixes in an online rolling fashion on AIX® and Linux®.

Before you begin

Important: To run the db2cm utility as the root user, ensure the DB2INSTANCE environment variable is set to the instance owner.

Before you install IBM Storage Scale security fix

Your instance must be a Db2 pureScale instance.
You must have root user authority.
You must have root access.

Restrictions

The base level of target IBM Storage Scale security efix must be the same as the current committed IBM Storage Scale level in the pureScale cluster. For example, if the current IBM Storage Scale level in the pureScale cluster is at 3.5.0.24 efix5, and IBM Storage Scale releases a new security efix9 a month later, the efix to be applied must be from the same IBM Storage Scale base level 3.5.0.24. The procedures documented in this topic cannot be used to move up the IBM Storage Scale base level.
The procedures described below is restricted to be used for security fixes not included in any Db2 fixpacks but have been validated and supported by Db2 as documented in http://www-01.ibm.com/support/docview.wss?uid=swg21986595. Regular IBM Storage Scale upgrade must follow existing online or offline Db2 upgrade methods.

Procedure

Download the target efix files locally on each host in the cluster.
Log on to a host in the cluster and perform the following steps as Db2 instance owner.
1. Stop all Db2 processes on the host. Use one of the following depending on whether the host is a member or CF:
```
db2stop member <member_id>  quiesce <quiesce_timeout>
```
  or
```
db2stop CF <cf_id>
```
2. Stop the instance on the host:
```
db2stop instance on <hostname>
```
Switch to the root ID on the same host and perform the following :
1. Enter the maintenance mode on the host:
  On AIX systems, run the following commands:
```
DB2INSTANCE=<instanceName> <DB2_install_dir>/bin/db2cluster -cm -enter -maintenance
<DB2_install_dir>/bin/db2cluster -cfs -enter -maintenance
```
  where <DB2_install_dir> is Db2 installation path
  On Linux systems, run the following commands:
```
DB2INSTANCE=<instanceName> <DB2_install_dir>/bin/db2cm -cm -enter -maintenance
<DB2_install_dir>/bin/db2cm -cfs -enter -maintenance
```
  where <DB2_install_dir> is Db2 installation path.
  Proceed to subsequent steps only if the above command returns successfully.
2. Verify that IBM Storage Scale trace is not running:
```
ps -ef | grep -i trace
```
  If the command above shows processes such as "trace" or "mmtrace", stop the IBM Storage Scale trace with the following:
```
/usr/lpp/mmfs/bin/mmtrace stop
```
  Rerun "ps" command above to ensure the trace has been stopped successfully before proceeding.
3. Unload IBM Storage Scale kernel and verify the result:
```
/usr/lpp/mmfs/bin/mmfsenv -u
echo $?
```
  A zero return from the "echo ?" command indicates a successful unload. A non-zero value means the unload has failed. In that case, a reboot of the host must be performed before proceeding.
4. Install the target IBM Storage Scale efix.
  1. On AIX, any existing IBM Storage Scale efix must be uninstalled first. Run the following command to get the label of any IBM Storage Scale efix currently installed.
```
/usr/sbin/emgr -P
```
    Sample output:
```
$ /usr/sbin/emgr -P
PACKAGE                                                  INSTALLER   LABEL
 ======================================================== =========== ==========
 gpfs.base                                                installp    g350p24e5
```
    Use the LABEL to remove the efix(es) that correspond with the gpfs.base package:
```
/usr/sbin/emgr -r -L <GPFS_efix_label>
```
    Install the target IBM Storage Scale efix:
```
/usr/sbin/emgr -e <full local path to the efix file>
```
    Verify the new efix has been applied, the label returned by the command below should match with one the of efixes in this link : http://www-01.ibm.com/support/docview.wss?uid=swg21986595
```
/usr/sbin/emgr -l
```
  2. On Linux, proceed to the directory with the new IBM Storage Scale efix. For each package (starting with the gpfs.base-packages) run the following to install it:
```
rpm -Uvh --force <rpm package>
```
    Verify the installation by:
```
rpm -qa | grep -i gpfs
```
    Run the following command to compile the IBM Storage Scale Portability Layer (GPL) module:
```
cd /usr/lpp/mmfs/src
export SHARKCLONEROOT=/usr/lpp/mmfs/src
make Autoconfig
make World
make InstallImages
echo $?       
```
    A zero return code from "echo $?" indicates a successful compilation. Do not proceed unless the compilation is successful.
5. Exit the maintenance mode:
  On AIX systems, run the following commands:
```
DB2INSTANCE=<instanceName> <DB2_install_dir>/bin/db2cluster -cm -exit -maintenance
<DB2_install_dir>/bin/db2cluster -cfs -exit -maintenance
```
  On Linux systems, run the following commands:
```
DB2INSTANCE=<instanceName> <DB2_install_dir>/bin/db2cm -cm -exit -maintenance
<DB2_install_dir>/bin/db2cm -cfs -exit -maintenance
```
Switch back to the Db2 instance owner for the following steps:
1. Start the instance on the host:
```
db2start instance on <hostname>
```
2. Start the member or CF on the host:
```
db2start member <member_id>
```
  or
```
db2start CF <cf_id>
```
Repeat steps 2 to 4 above on the rest of the hosts in the same cluster.
Before committing to the new IBM Storage Scale level, allow applications to run for a short period of time to ensure the update does not introduce unexpected behavior. When ready, switch to the root ID on any online host in the cluster to commit the new IBM Storage Scale level with the following command:
On AIX systems, run the following command:
```
<DB2_install_dir>/bin/db2cluster -cfs -commit
```
On Linux systems, run the following command:
```
<DB2_install_dir>/bin/db2cm -cfs -commit
```