In my first posting in October 2015 I wrote about how when setting up IBM Security Access Manager (ISAM) you need to use Manage System Settings -> Updates and Licensing: Available Updates to install .pkg files, and you need to use Manage System Settings -> Updates and Licensing: Fix Packs to install .fixpack files. But that’s not all you need to know to avoid a System failed to install the fix pack error message with ISAM…
If, for example, you start with a system at 18.104.22.168 (created by building a Virtual Appliance with the 22.214.171.124 ISO ISAM_90_BASE_VIRTUAL_APP_.ISO_MP_.iso and then installing isam_126.96.36.199_20151209-2309.pkg), and try and install 9010_IF1.fixpack (using Manage System Settings -> Updates and Licensing: Fix Packs) you also get the same error: System Error: The system failed to install the fix pack. So (and this is not really a surprise) the fixpack needs to be compatible with the version of ISAM installed.
In order to illustrate how to avoid this error, the process to install 9010_IF1.fixpack on a system at 188.8.131.52 is as follows:
1. First, bring the system up to ISAM 184.108.40.206: install ISAM_9.0.1_BVA_.PKG_FILE_MP_ML.pkg by doing the following:
a. Click Manage System Settings -> Updates and Licensing: Available Updates. The Available Updates page will be displayed.
b. Click Upload. The New Update dialogue box will be displayed.
c. Click Select Update. Navigate to the .pkg file (in this case ISAM_9.0.1_BVA_.PKG_FILE_MP_ML.pkg) and click Save Configuration.
d. The file may take a few minutes to upload. After that the new firmware (220.127.116.11, in this case) will appear in the list of available updates.
e. Select the new firmware and click Install. A confirmation dialogue box will be displayed.
f. Click Yes. A message indicating that the LMI session has ended and that the firmware update is being installed.
g. Wait several minutes for the new firmware to be installed, which includes rebooting the appliance. (Be patient!)
h. Click Manage System Settings -> Updates and Licensing: Firmware Settings. The Partition that is shown as Active will show the new Firmware Version (18.104.22.168, in this case), the previously active partition (22.214.171.124 in this case) will now be the backup partition (and the Last Boot time will show as being in the previous few minutes).
2. Before installing a fixpack it is a good idea to create a firmware backup in case you subsequently want to back out the fixpack, by doing the following. (When you install a new .pkg file it automatically creates a firmware backup, whereas that is not the case when you install a fixpack.) This step will copy the existing firmware (126.96.36.199, in this case) to the backup partition (which previously had 188.8.131.52 installed).
a. Click Manage System Settings -> Updates and Licensing: Firmware Settings.
b. Select the Active Partition and click Create Backup.
c. A confirmation dialogue box will be displayed. Click Yes.
d. A message indicating that the security device is offline because the system is backing up the selected partition.
e. Wait a few minutes for the new firmware to be backed up.
f. Click Manage System Settings -> Updates and Licensing: Firmware Settings. Both partitions will show the same firmware version.
3. It is then possible to install 9010_IF1.fixpack by doing the following:
a. Click Manage System Settings -> Updates and Licensing: Fix Packs.
b. Click New. The Add Fix Pack dialogue box will be displayed.
c. Click Browse for fix pack, navigate to the .fixpack file (in this case 9010_IF1.fixpack) and click Save Configuration.
d. After this the fix pack is uploaded and installed all in one step: the browser will appear to hang for a minute or so, and after that it will show a System Notification that the fix pack has been installed. If you then re-load the URL it will then show the fix pack name (9010_IF1, in this case) and status (column heading ‘Action’, value ‘Installed’) together with a Description (‘This fixpack contains updates to Java on the appliance’).
e. Unlike last time, the appliance may not be automatically rebooted after applying the fix pack.
I hope that this is of use to someone!