While the best practice for upgrading GPFS software level is through the DB2 fixpack, update leveraging existing online or offline software update procedures, applying a GPFS security efix, which may be released in between DB2 fixpacks, requires a manual installation procedure. The instructions outlined in this topic provides the steps to update a DB2 pureScale cluster with GPFS security fixes in an online rolling fashion on AIX and Linux.
Before you begin
Before you install GPFS security fix
- Your instance must be a DB2 pureScale instance.
- You must have root user authority.
- The base level of target GPFS security efix must be the same as the current committed GPFS level in the pureScale cluster. For example, if the current GPFS level in the pureScale cluster is at 22.214.171.124 efix5, and GPFS releases a new security efix9 a month later, the efix to be applied must be from the same GPFS base level 126.96.36.199. The procedures documented in this topic cannot be used to move up the GPFS base level.
- The procedure described below is restricted to be used for security fixes not included in any DB2 fixpacks but has been validated and supported by DB2 as documented in http://www-01.ibm.com/support/docview.wss?uid=swg21986595. Regular GPFS upgrade must follow existing online or offline DB2 upgrade methods.
- 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.
- 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>
db2stop CF <cf_id>
- Stop the instance on the host:
db2stop instance on <hostname>
- Switch to the root ID on the same host and perform the following:
- Enter the maintenance mode on the host:
<DB2_install_dir>/bin/db2cluster -cm -enter -maintenance
<DB2_install_dir>/bin/db2cluster -cfs -enter -maintenance
where <DB2_install_dir> is DB2 installation path.
Proceed to subsequent steps only if the above command returns successfully.
- Verify that GPFS trace is not running:
ps -ef | grep -i trace
If the command above shows processes such as "trace" or "mmtrace", stop the GPFS trace with the following:
Rerun "ps" command above to ensure the trace has been stopped successfully before proceeding.
- Unload GPFS kernel and verify the result:
A zero return value 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.
- (On AIX) Install the target GPFS efix
- Any existing GPFS efixes must be uninstalled first. Run the following command to get the label of any GPFS efix currently installed:
$ /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 GPFS efix:
/usr/sbin/emgr -e <full local path to the efix file>
- Verify the new efix has been applied. The new efix shown by the command below should match with one the of efixes in this link: http://www-01.ibm.com/support/docview.wss?uid=swg21986595
- (On Linux) Install the target GPFS efix
- Proceed to the directory with the new GPFS 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 GPFS Portability Layer (GPL) module:
A zero return value from "echo $?" indicates a successful compilation. Do not proceed unless the compilation is successful.
- Exit the maintenance mode:
<DB2_install_dir>/bin/db2cluster -cm -exit -maintenance
<DB2_install_dir>/bin/db2cluster -cfs -exit -maintenance
- Switch back to the DB2 instance owner for the following steps:
- Start the instance on the host:
db2start instance on <hostname>
- Start the member or CF on the host:
db2start member <member_id>
db2start CF <cf_id>
<DB2_install_dir>/bin/db2cluster -cfs -commit
Original Publication Date
26 July 2016
17 June 2018