Pre-requisites

Before beginning with the process of upgrading, ensure that the following pre-requisites are fulfilled.

Configuring Proxies and Repos

You are required to configure the proxies and repos.

Configure the http proxy in /etc/yum.conf file and also export the proxy's address to the environment.

In /etc/yum.conf, add the following line:
```
proxy=<proxy_server>
```

Export the proxy's address.

export http_proxy=<proxy_server>
export https_proxy=<proxy_server>

Creating a Backup before Upgrading (Optional)

This procedure is optional but is recommended.

Session Monitor enables you to back up the Configuration, Database, Block Storage and essential Session Monitor files of the Session Monitor Servers by providing a Backup and Restore procedure.

For more information, see the Session Monitor Release 6.0 Backup and Restore Guide.

Note:

Currently, there is no rollback option available from an upgrade.

A Note if you Have Not Taken a Backup

Create Historical System Diagnostics with the Create savepoint and Include mysqldump check boxes enabled from the PSA Page. This is mandatory.

Download a copy of the Diagnostics created and save it in a safe location. These diagnostics are required to debug any issues in the future.

For more information, see the System Diagnostics section in the Session Monitor Release 6.0 Installation Guide

Note:

Creating the Savepoint is applicable only for the Mediation Engine. Also, enabling the Create savepoint and Include mysqldump check boxes is mandatory for taking Diagnostics.

Password Policy Changes

With Session Monitor Release 6.0, changes in password policy have been introduced. Password Policy 1 and 2 present in the Secure password policy system setting are now considered insecure and are no longer available in Release 6.0. Only password policy 3 has been retained and this is the only and default option.

For existing users, if there are any users whose password is encrypted using password policy 1, then Session Monitor does not allow upgrade for such systems.

During the upgrade, a pre-test runs to check if any user has password encrypted using password policy 1 – the upgrade fails with the message:

Below users have an insecure password hash created using policy 1
Please change 'Secure password policy' to 3 in the 'System Settings' and change the passwords accordingly...

If the above situation arises, then perform the following steps:

Set the Secure password policy to 3 in the System Settings.
Manually change the passwords of the users whose names appear in the message.
Try to upgrade again. This time it should be successful. Post a successful upgrade, System Settings > Secure Password Policy is set to 3.

For a fresh installation, the Secure Password Policy is set to 3 by default, and there is no option to change it.

Savepoint Restore on Session Monitor Release 6.0 will fail if any user has password encrypted using password policy 1. Perform the fix as given below:

Perform Step 1 and Step 2 given above.
Re-create the Savepoint.
Try to restore.