IBM DataPower Operations Dashboard v1.0.8.6
Note: A more recent version of DPOD is available. See DPOD Documentation for the latest documentation.
Upgrade
DPOD software updates are available from time to time and include enhancements, security updates, component upgrade, bug fixes etc.
Up to version 1.0.8.0, each DPOD fix pack file is not including any previous fix pack. For example: to upgrade from v1.0.5 to v1.0.7 you will need to first upgrade to v1.0.6 with the downloaded fix of v106 and after a successful upgrade to v106 you may apply the fix to v107.
DPOD installation from version 1.0.8.0 and above can apply the latest fix available in fix central. For example: to upgrade from v1.0.7 to latest you will need to first upgrade to v1.0.8 with the downloaded fix of v108 and after a successful upgrade apply the latest fix from fix central.
The following sections describe the process of upgrading an existing installation.
To upgrade cell environment - stop DPOD on the cell manager and all cell members, and then run the following steps for each server separately, first for each cell member and only after for the cell manager
Obtain the software update
DPOD software updates are available through IBM fix central.
The download consists of two types of files :
- The update file in the format of : DPOD-fixpack-<version number>.sfs (for example: DPOD-fixpack-1_0_8_5.sfs)
- The md5 hash calculation of the update file : DPOD-fixpack-<version number>.md5 (for example: DPOD-fixpack-1_0_8_5.md5)
Make Sure squashfs support (only for Non Appliance Installation )
Make sure the update file can be mounted ( squashfs support) using the following command
lsmod | grep squash expected output : squashfs
Copy the software update to the DPOD server
Copy the update files to the following directory on the DPOD server :
/installs/update/fix/TODO
If the directory is missing for some reason, please re create it :
mkdir -p /installs/update/fix/TODO
Make sure there is enough disk space
The software update requirements for available disk space may change from version to version. See version table below.
The disk space is needed at the "/install" mount point and can be displayed using the following command:
df -h /installs Output example: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_inst-lv_inst 7.0G 5.5G 1.6G 79% /installs
During the software update installation, the internal configuration database is being backed-up. The backup requires additional available disk space on the "/installs" mount point.
To calculate the needed available disk space for the internal configuration database backup please use the following command (in this example DB size is 43MB):
du -ksh /app/derby/ Output example: 43M /app/derby/
See the following table for needed available disk space on "/installs" for the software update:
| Version | Needed Available Disk Space |
|---|---|
| 1.0.3 | 700MB + DB SIZE |
| 1.0.4 | 700MB + DB SIZE |
| 1.0.5 | 2500MB + DB SIZE |
| 1.0.6 | 700MB + DB SIZE |
| 1.0.7 | 3000MB + DB SIZE |
| 1.0.8 | 2000MB + DB SIZE |
If there is not enough free disk space on the "/installs" mount point the user may free some by deleting files from the following directories :
| Directory | Description |
|---|---|
| /installs/update/fix/TODO | Remove old DPOD update files (.sfs) |
| /installs/update/fix/backups | Remove old DPOD backup directories |
| /installs/APPL-setup | Remove DPOD installation file |
Install the software update
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.
MonTierUpdateInstaller.sh -u DPOD-update-<version number>.sfs -s DPOD-update-<version number>.md5
For example:
MonTierUpdateInstaller.sh -u DPOD-update-1_3_0.sfs -s DPOD-update-1_3_0.md5
You may encounter the following message:
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.
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 :
error, software update can NOT be applied to this system version. aborting update...
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.
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.
Manual Post Update Installation
Important: After the upgrade is complete, Syslog must be manually re-configured on all monitored devices using the Web Console (under Manage → Monitored Devices).
For more details, please see the section "Configure The New Monitored Device" in Adding Monitored Devices.