gssutils - Upgrade EMS menu

Availability

Available with the Elastic Storage Server.

Description

Use this menu to upgrade the ESS system and install latest ESS software on the EMS node. During the upgrade process if a step fails, it must be addressed before moving to the next step. Follow these steps to perform an upgrade of the ESS system.

Menu options

1. Help

Opens this manual page.

2. Backup and Cleanup xCAT Database (optional)

Perform cleanup and backup of xCAT DB. Only required if you are upgrading and xCAT or the Operatin system changes. Perform the following steps if you are upgrading from ESS 5.1.x or ESS 5.2.x.

If upgrading from ESS 5.1.x or ESS 5.2.x, perform cleanup and save a backup copy of the xCAT database:

$ /opt/ibm/gss/install/rhel7/<arch>/samples/gssdeploy -c -r /var/tmp/xcatdb

For example:

On PPC64BE

$ /opt/ibm/gss/install/rhel7/ppc64/samples/gssdeploy -c -r /var/tmp/xcatdb

On PPC64LE

$ /opt/ibm/gss/install/rhel7/ppc64le/samples/gssdeploy -c -r /var/tmp/xcatdb

3. Extract ESS Binaries

Extract the latest ESS binaries to perform an upgrade.

4. Update ESS software repository

Update the ESS management server software repositories with new packages. Use the correct architecture of gssinstall (ppc64 or ppc64le). Make sure you regenerate the gssutils configuration file if using the customized environment file. Once complete, exit gssutils and re-run.

On PPC64BE

$ /usr/bin/python /var/tmp/gssinstall_ppc64 -u

On PPC64LE

$ /usr/bin/python /var/tmp/gssinstall_ppc64le -u

5. Customize gssdeploy script configuration file

This is the first step towards the upgrade of the ESS system. Make sure you know the IP address, host name, and other network parameters of the ESS infrastructure to successfully upgrade the EMS node.

Here users need to change the gssdeploy.cfg according to their environment. User also need to make sure that the /etc/hosts file is updated with the correct host name and IP address. ESS deployment is highly dependent on the /etc/hosts file. Make sure that the file is in the Linux format.

6. Deploy new xCAT from backed-up xCAT DB (Optional)

Deploy new xCAT using the backed-up xCAT database. The backup was taken earlier for the older xCAT database. This step is required if either xCAT is of a newer version or the operating system changed.

If upgrading from ESS 5.1.x or ESS 5.2.x, install tools and xCAT and restore the xCAT database:

$ /var/tmp/gssdeploy -x -r /var/tmp/xcatdb

7. Check for EMS node before upgrade

Run pre-check on the EMS node to check for any error, before upgrade.

$ /opt/ibm/gss/tools/samples/gssprecheck -N ems1 --upgrade --file /var/tmp/gssdeploy.cfg

Note: gssprecheck gives hints on ways to fix any discovered issues. It is recommended to review each found issue carefully though resolution of all might not be mandatory.

8. Perform EMS Upgrade

Perform actual upgrade, if upgrade pre-check doesn't report any issues. Performing an upgrade shuts down the GPFS™ cluster on the EMS node until the upgrade is completed.

9. Check and validate various install parameters

Run install check and check for any deployment errors. All install check errors must be addressed before proceeding further.

$ gssinstallcheck -N ems1

For more information, see gssinstallcheck command.

Press c to change the EMS host name.

10. Back

Exit to the previous menu.

Exit status

0

Successful completion.

nonzero

A failure has occurred.

Security

You must have root authority to run gssutils.