Install Procedure for a Single Node Cluster Environment#

Download Patch Script and Check#

Note

It is recommended that the file download is done prior to the maintenance window.

Download the following file

  • 24.2-Delta-Bundle-patch.script

to the media folder on the single node.

Verify SHA256 checksum#

To verify SHA256 checksum for the patch, run the following command on the node the script was downloaded to:

  • Command : system checksum media/24.2-Delta-Bundle-patch.script

  • Expected: The value in 24.2-Delta-Bundle-patch.script.sha available in the download location.

Pre-Installation, Version Check#

To check the version pre-install:

  1. Log in to the Admin Portal GUI.

  2. Check the information contained in the menu About > Version > Release.

    The release version should be 24.1

Pre-Installation, Security and Health Steps#

  1. Place the system in maintenance mode to suspend any scheduled transactions. Scheduled transactions that are in progress, will be allowed to complete.

    For details on this command, refer to the System Maintenance Mode topic in the Platform Guide.

    On an application node of the system, run:

    cluster maintenance-mode start

    You can verify the maintenance mode status with:

    cluster maintenance-mode status

  2. Verify that the primary database node is the active primary node at the time of upgrade.

    On the single node, run:

    database config

    This is to ensure that the node on which the installation will be initiated, has the:

    1. stateStr parameter set to PRIMARY

    2. highest priority number (highest priority number could vary depending on cluster layout).

    Example output

    <ip address>:27020:
priority: <number>
stateStr: PRIMARY
storageEngine: WiredTiger

  3. Validate the system health.

    On the single node, run:

    app status

  4. Verify network connectivity, disk status, NTP and that there are no pending Security Updates.

    On the single node, run:

    diag disk

    If there is any sign of the paths below are over 80% full, a clean-up is needed to avoid risk of for example full logs occurring during upgrade. Clean-up steps are indicated next to the paths:

    /              (call support if over 80%)
/var/log       (run: log purge)
/opt/platform  (remove any unnecessary files from /media directory)
/tmp           (reboot)

    On the single node, run:

    security check

    If there are pending Security Updates, then run:

    security update

    Then reboot:

    system reboot

    Since all services will be stopped, this takes some time.

  5. Shutdown servers and take snapshots from VMWare or Azure VHD, as applicable.

    Run:

    system shutdown

Patch Installation#

On the single node, run:

  • screen

  • app install media/24.2-Delta-Bundle-patch.script

Note

Before the patch installation starts, the user is prompted to:

  • Continue with the installation.

    Append the --force parameter to remove this prompt.

  • Delete or keep the patch script in the media directory after installation.

    Append the delete-on-success parameter with a yes|no value to the command to remove this prompt.

To remove all prompts, use the command and parameters:

app install media/24.2-Delta-Bundle-patch.script delete-on-success yes --force

  • Close screen: Ctrl-a \

Post-Upgrade, Security and Health Steps#

Verify Security Updates, reboot, network connectivity, disk status and NTP.

On the single node, run:

  • app status

  • diag disk

  • security check

If there are pending Security Updates, then run security update.

On the single node, run:

  • security update

Reboot.

On the single node, run:

  • system reboot

Since all services will be stopped, this takes some time.

  • End the system maintenance mode. On the application node of the system, run:

    cluster maintenance-mode stop

    You can verify the maintenance mode status with:

    cluster maintenance-mode status

    For details on this command, refer to the System Maintenance Mode topic in the Platform Guide.

FIPS#

If FIPS is enabled, FIPS proxy configuration has been included in this release. To apply this package, please run the command security update on each FIPS enabled node in the cluster after the upgrade has been completed. No reboot is required.