Install Procedure for a Modular Cluster Topology#

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 primary application node.

To check for this node:

  1. Log in on a node in your modular cluster.

  2. To find the primary application node in the cluster:

    $ cluster run application cluster primary role application

    Record the node entry where is_primary: true, for example:

    ---------- VOSS-UN-1, ip=192.168.100.3, role=webproxy,application, loc=cpt

    is_primary: true

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 verify 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.

    Have the IP address available of the node determined to be the primary database node. To find the primary database node in the cluster:

    $ cluster run database cluster primary role database

    Record the node entry IP where is_primary: true, for example:

    ---------- VOSS-UN-2, ip=192.168.100.4, role=database, loc=cpt


    is_primary: true

    This IP address will be used in command parameters during upgrade.

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

    On the primary application node, run:

    cluster run <primary db IP> database config

    Upgrade from the output, ensure that the primary database node ``stateStr`` parameter is set to **PRIMARY and it has the 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 primary application node, run:

    cluster status

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

    On the primary application node, run:

    cluster check

    cluster run all 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 primary application node, run:

    cluster run all security check

    If there are pending security updates, then:

    On the primary application node, run:

    cluster run all security update

    Then reboot all nodes:

    cluster run notme system reboot

    (If node messages: <node name> failed with timeout are displayed, these can be ignored.)

    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.

    On the primary application node, run:

    cluster run notme system shutdown

    Then after 1 minute: run:

    system shutdown

Patch Installation#

On the primary application 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#

  1. On the primary application node, verify the cluster status:

    • cluster status

  2. On each node verify Security Updates, reboot, network connectivity, disk status and NTP.

    • cluster check

  3. If there are pending Security Updates, then run security update on all nodes. On the primary application node, run:

    • cluster run all security update

  4. Reboot all nodes:

    • cluster run notme system reboot

    (If node messages: <node name> failed with timeout are displayed, these can be ignored.)

    • system reboot

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

  5. End the system maintenance mode. On an 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.