Upgrading to version 1.0.31.0

Follow the instructions after this to upgrade the Integrated Analytics System to version 1.0.31.0.

Before you begin

Read the Release notes for information on any known issues that might affect your IAS version upgrade.
If your system uses Integrated Analytics System 1.0.2x.x and configured with an external LDAP configuration, you must back it up before upgrading to 1.0.31.0. After the upgrade, you might need to restore the LDAP configurations. It is not required, if you use Integrated Analytics System 1.0.30.0.
Do the following procedures to backup the LDAP configuration before upgrading
1. Copy the backup script:
```
cp /localrepo/<bundle_name>/EXTRACT/bundle/app_img/ldap/ap_ldap_backup_restore.pl /opt/ibm/appliance/platform/ldap/bin/
```
2. Create an LDAP configuration backup:
```
/opt/ibm/appliance/platform/ldap/bin/ap_ldap_backup_restore.pl backup
```
Do the following procedure to restore the LDAP configuration after upgrading
1. Restore the LDAP configuration
```
/opt/ibm/appliance/platform/ldap/bin/ap_ldap_backup_restore.pl restore
```
If you are using Integrated Analytics System 1.0.2x.x, make a full backup of your database before upgrading to 1.0.31.0.
If your system is using Integrated Analytics System 1.0.2x.x, make a backup of all EMC client NetWorker configuration data before upgrading to 1.0.31.0. You must restore the configuration data after upgrading.
Before starting the upgrade, make sure that no third-party tools are configured (example: OSST driver or OneAgent (Dynatrace).
Before starting the upgrade, ensure that no third-party backup and restoration utilities are configured. For example, TSM, Lintape NFS, EMC. If they are configured, you must disable them before upgrading and then re-enable them once the upgrade is complete.
Before starting the upgrade:
- Run the following command to make sure that Guardium is not running:
```
podman exec -it dashDB /opt/ibm/guardium/guard_stap/guard-config-update –status
```
  Also, make sure that the output does not show: STAP : enabled
- Run the following command to make sure that AFM-DR is stopped:
```
systemctl stop apafmdr
```
- If you have DSX preinstalled and not using it, open a service ticket to uninstall it.
The minimum security patch that is required for upgrading to 1.0.31.0 is:
- SP23 for 1.0.25.0 to 1.0.28.x releases (RHEL 7)
- SP4 for 1.0.30.0 to 1.0.30.0 IF1 release (RHEL 8)
If you have any additional rpms or modules installed on your system in addition to those provided, remove them before proceeding with the upgrade.
If you are using the BLUDR functionality, make sure to follow the procedures listed below before updating to 1.0.31.0:
- Before ending replication on both source and target systems, make sure that all replication sets are caught up and the LAST CONSISTENCY POINT is current for all replication sets.
- Backup the files or folders listed below from both the source and target systems. You must restore the BLUDR settings after upgrading:
  - $BLUDR_SHARED_DIR/settings_backup/server.env file
  - $BLUDR_SHARED_DIR/logs/replication
  - $BLUDR_SHARED_DIR/certificates
- Make sure the contents of the server.env and asnpwd.aut files from $BLUDR_SHARED_DIR/logs/replication are same after the upgrade.
  Note: In 1.0.31.0, the file server.env contains extra contents.
If you use Microsoft Active Directory for user management, before upgrading to 1.0.31.0, make sure that the AD DNS server has proper SRV records configured for the Kerberos realm's DNS domain. Example of an SRV record to add:
```
_kerberos._tcp.[domain]. 3600 IN SRV 0 100 88 [kdc-hostname]
```
- _kerberos._tcp.[domain]: The service name for Kerberos over TCP in the target domain (for example, the DNS domain tied to your Kerberos realm).
- 3600: TTL (Time to Live) in seconds (1 hour; adjustable as needed).
- IN SRV: Indicates this is an SRV (Service) record.
- 0: Priority—sets the preference order if multiple SRV records exist (lower = higher priority; 0 is highest).
- 100: Weight—balances load among same-priority records (arbitrary for a single KDC; typically 100).
- 88: Port where the KDC listens (Kerberos standard).
- [kdc-hostname]: The fully qualified hostname of the KDC (must resolve to it's IP via an A record).

Procedure

Download or copy the Integrated Analytics System bundle to /localrepo.

Note: The upgrade bundle must be downloaded to the actual /localrepo partition on the node running the upgrade. GPFS is stopped during the upgrade, so if the bundle is downloaded to GPFS storage, the upgrade fails.
Run ap issues and resolve any of the issues that might impact the upgrade process.
Copy the tar.gz file from the downloaded location to a directory on node0101 with the same name as the version of the file name.
1. Create the new directory outside the container on node0101:
```
mkdir /localrepo/1.0.31.0_release
```
  In this case, /localrepo defines the upgrade directory for the --upgrade-directory parameter that is used later.
  The directory name cannot start with release or iias prefix. Use the release number.
2. Move the upgrade package (tar.gz) file into this new directory:
```
mv package.tar.gz /localrepo/1.0.31.0_release
```
Start a session that continues if your connection is dropped.
1. If you are upgrading from Integrated Analytics System 1.0.2x.x, run the following command:
```
screen -S apupgrade
```
  If you get disconnected, the upgrade continues. To reconnect, run the screen -rd apupgrade command.
  After RHEL upgrade, the screen command no longer works as it is removed in RHEL 8. But, the upgrade continues in the background. Run the following command to track it:
```
tail -f /var/log/appliance/apupgrade/apupgrade.log
```
2. If you are upgrading from Integrated Analytics System 1.0.30.0 or later, run the following command:
```
tmux new-session -A -s apupgrade
```
  If you get disconnected, the upgrade continues. To reconnect, run the following command:
```
tmux attach -t apupgrade
```

Run the following command to upgrade the apupgrade:

apupgrade --upgrade-apupgrade --upgrade-directory /localrepo --use-version 1.0.31.0_release

Note: Run apupgrade only as the root user.

Perform an upgrade pre-check.
The pre-check step is also run as part of the upgrade, but it is advised to run it before you start the actual upgrade so that the system health can be verified and fixed when needed.
```
apupgrade --preliminary-check --upgrade-directory /localrepo --use-version 1.0.31.0_release
```
Refer to upgrading timings, as the times provided in the preliminary check might not be accurate.
Run apupgrade --upgrade --upgrade-directory <upgrade_directory> --use-version 1.0.31.0_release
Note:
- Do not use the --force-restart option as the upgrade process might fail with errors.
Example:
```
apupgrade --upgrade --upgrade-directory /localrepo --use-version 1.0.31.0_release
```

Follow the status of the upgrade by reviewing the following logs:

/var/log/appliance/apupgrade/apupgrade.log
/var/log/appliance/apupgrade/apupgrade.log.tracelog
/var/log/appliance/apupgrade/apupgrade.1.0.x.x_release.status

Optional: Ensure that the Platform Manager and the system are up and running after all upgrades are complete.
1. The command ap state should return Ready.
2. The commands ap issues and ap issues -sw should be clear of problems. If not, fix any issues, and run the command apstart.
Note: If you are using db_migrate_iias, contact IBM support after the 1.0.31.0 upgrade is complete to assure continuous operations.

Results

After a successful upgrade to 1.0.31.0, ap version -s output shows the components versions that follow:

[root@sail68-t03-n1 ~]# ap version -s
Appliance software version is 1.0.31.0

All component versions are synchronized.

+-----------------------------+-----------------------------------------------------------------+
| Component Name              | Version                                                         |
+-----------------------------+-----------------------------------------------------------------+
| Appliance platform software | 1.0.31.0-20250406202532b735                                     |
| apcomms                     | 2.4.33.0-20241209135130b4114                                    |
| appkg_install               | 1.0.31.0-20250404073656b6766                                    |
| apupgrade                   | 1.0.31.0-20250404073648b6766                                    |
| callhome                    | 1.2.0.0-20250121144534b10                                       |
| containerapi                | 1.0.31.0-20250224072758b6000                                    |
| dashdb                      | 11.5.9.0_cn2-20250404-1355                                      |
| gpfs                        | 5.1.9.0-9                                                       |
| gpfsconfig                  | 1.0.31.0-20250319160440b6429                                    |
| jwtservice                  | 1.0.12.0-20241111031307b1                                       |
| magneto                     | 1.0.31.0-20250318101811b6398                                    |
| nodeos                      | 1.0.31.0-20250319153604b6429                                    |
| pfscfg                      | 2.0.2.15-20250221053200b2                                       |
| platformbackups             | 1.0.20.0-20241111002156b3122                                    |
| platformservices            | pfs-ppc64le-standalone-utils        : 2.0.2.17-20241111025254b2 |
|                             | pfs-ppc64le-image                   : 2.0.2.17-20241111025254b2 |
|                             | pfs-software                        : 1.1.31.0-20250305053406b5 |
| platformservicesfirmware    | pfs-cumulus-fabsw-firmware          : 1.3.1.0-b1                |
|                             | pfs-raritan-ts-firmware             : 1.4.0.0-b1                |
|                             | pfs-cumulus-mgtsw-firmware          : 1.2.1.0-b1                |
|                             | pfs-ibm-fsn-firmware                : 1.11.1.0-b1               |
|                             | pfs-ibm-fcsw-firmware               : 1.3.0.0-b1                |
|                             | pfs-delta-rpc-firmware              : 1.2.1.0-b2                |
|                             | pfs-ibm-dsn-firmware                : 1.7.0.0-b1                |
|                             | pfs-ibm-node-firmware               : 1.8.1.0-b3                |
| psklm                       | 1.0.23.0-20241114224610b1                                       |
| supporttools                | 1.0.31.0-20250303055122b6087                                    |
| svsutils                    | 2.0.2.15-20250221053050b5                                       |
| web_console                 | 1.0.30.0-202408210036                                           |
+-----------------------------+-----------------------------------------------------------------+