Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DPOD software update updates are available from time to time and includes include enhancements, security updates, component upgrade, bug fix fixes etc.
The following sections describe the process of upgrading an existing installation. 

Obtain the software update

DPOD software updates are available through IBM fix central.

The download consists of two types of files :

  1. The update file in the format of : DPOD-fixpack-<version number>.sfs (for example: DPOD-fixpack-1_0_5.sfs)
  2. The md5 hash calculation of the update file : DPOD-update-<version number>.md5

Copy the software update to the DPOD server

Copy the update files to the following directory on the DPOD server :

 

DPOD acts like a virtual appliance but is packaged as an ISO file to support installation on both physical and virtual installation scenarios.  

When Installing DPOD from an ISO file, The first step is to instal the Appliance which means install and configure the OS preloaded on the ISO (CentOS).

Completing the steps below will create a DPOD-ready appliance to install DPOD's software on.

 

You MUST NOT add or install any packages / RPMs to the installation of DPOD or once it was installed already unless instructed by support.

You MUST NOT update the CentOS version or any other component within DPOD using external repositories (for example do not use yum update)

The only supported way to upgrade platform and/or component is by apply a product Fix Pack.

OS Installation

...

Code Block
themeRDark
/installs/update/fix/TODO


If the directory is missing for some reason, please re create it :


Code Block
themeRDark
mkdir -p /installs/update/fix/TODO

Install the software update

Note

A technical issue prevents upgrading DPOD installations that were installed using version 1.0.2.0 ISO file.
Before upgrading an 1.0.2.0 ISO-based DPOD installation to a newer version, please run the following command from a console / ssh session:
cd /installs
rm -rf dev-tools

To identify the ISO version used for your installation, please run the CLI Admin utility (app-util.sh) and select option 9 (system version).
The version appears in the ISO file name next to the "package_name" attribute, for example: ibm-DPOD-STD-APPL-1.0.2.0-2016-11-15_03_50_10_731-IST-BLD212.iso

Run the following command from the location you downloaded the update files to.

Code Block
themeRDark
MonTierUpdateInstaller.sh -u DPOD-update-<version number>.sfs -s DPOD-update-<version number>.md5

For example:

Code Block
themeRDark
MonTierUpdateInstaller.sh -u DPOD-update-1_3_0.sfs -s DPOD-update-1_3_0.md5

You may encounter the following message:

Code Block
themeRDark
INFO file MonTierUpdateInstaller.sh was updated successfully.
INFO important !!! Please run MonTierUpdateInstaller.sh again.

This message means that the MonTierUpdateInstaller.sh was updated and you should rerun the command.
After running the command again you will be prompted to confirm the software update process. press "Y" to confirm or "N" to abort.

 

Code Block
themeRDark
Software update :

   Please DO NOT interrupt during the process !

   Are you sure you want to continue ? [y/n]


When the software update level is not compatible with the current system version you will receive the following message on the console output : 

Code Block
themeRDark
error, software update can NOT be applied to this system version. aborting update...

 

Note

Do Not interrupt the software update process after it has begun

When the software update completes, the system will display the following messages on the console output.

Code Block
themeRDark
Starting software update. log file is /installs/update/fix/logs/montier-update-2016-08-01_16-13-35.log
stopping application ...
application stopped successfully.
starting software update.....
updated complete successfully
starting application ...
application strated successfully.
update DPOD-update-1_3_0.sfs was installed successfully. log file /installs/update/fix/logs/montier-update-2016-08-01_16-13-35.log

Please review the upgrade log file if the console displays any error messages.