Updating FlashGrid software using FlashGrid Cluster Node Update package – FlashGrid Help Center

FlashGrid Cluster Node Update package is a single self-extracting bash script file that allows updating the following components:

FlashGrid Storage Fabric RPM
FlashGrid Diagnostics RPM
FlashGrid Cloud Area Network RPM
FlashGrid Health Checker RPM

Using this package makes it easier to have the update performed to the latest validated set of software components and helps avoid accidental installation of incompatible software versions.

Prerequisites

Determine your current version of FlashGrid by running the following as root:

# rpm -qi flashgrid-skycluster

If you are performing a major update (for example, update from version 22.03.x to 22.06.x, or 21.x to 23.x), please review corresponding release notes and check with FlashGrid support before performing update
If upgrading from v21.02 or older on RHEL7, you will need to install the jq package manually (if on OL7, this will be installed automatically from the OL7 repository). To install the jq package, download and install the jq rpm and its dependencies: libjq1, oniguruma, jq.
If upgrading from v21.06 or older on RHEL7/OL7, the openssl11-libs package must be installed manually before the update. If the openssl11-libs package is missing during the update then the following error may be reported: "Requires: libcrypto.so.1.1()(64bit)". This can be installed from the EPEL repository, or you can manually download and install from the following locations:

RHEL7: https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/o/openssl11-libs-1.1.1k-5.el7.x86_64.rpm

OL7: https://yum.oracle.com/repo/OracleLinux/OL7/developer_EPEL/x86_64/getPackage/openssl11-libs-1.1.1k-5.el7.x86_64.rpm

Notes

Simultaneously updating FlashGrid software and applying Grid Infrastructure patches in rolling fashion is not recommended. FlashGrid services should not be stopped while GI cluster is in rolling patching mode.
From v22.9, the "skip-kernel-update" option was removed from the node update script. OS updates are no longer applied as part of the FlashGrid update process.
Only if updating the OS simultaneously with the FlashGrid software, please also check Notes in the Updating OS article.

Rolling update procedure, one node at a time (no database downtime required)

This procedure is recommended when database services must stay up during the update.

To update software using FlashGrid Cluster Node Update package on a running cluster, repeat the following steps on each node, one node at a time:

Create backup snapshot of the OS disk

a. Flush OS buffers:
```
# sync; sync;
```
b. Create snapshot of the OS disk using the cloud console or CLI.
Make sure there are no other nodes that are in offline or resync state. All disk groups must have zero offline disks and Resync = No:
```
# flashgrid-cluster
```
If the node is a database node,

a. Stop all local database instances running on the node.

b. Stop Oracle CRS on the node:
```
# crsctl stop crs
```
Stop the FlashGrid Diagnostics monitoring service:
```
# systemctl stop flashgrid-node-monitor
```
Stop the FlashGrid Storage Fabric services on the node:
```
# flashgrid-node stop
```
Stop the FlashGrid Cloud Area Network service on the node:
```
# systemctl stop flashgrid-clan
```
Run the update script as root. Use the file name with a correct version number.
```
# bash flashgrid_cluster_node_update-X.Y.Z.NNNNN.sh
```
Note: When updating from version 20.06 or earlier, the following error may be reported: FlashGrid Cluster setup not found. In such case, double-check that you are running the update on a correct system and then re-run it with force-cluster the command parameter added.
Only if updating the OS simultaneously with the FlashGrid software, install the OS updates:
```
# yum update
```
Flush the OS buffers and reboot the node:
```
# sync; sync; reboot
```
Before updating the next node, wait until the node boots up, all disks are back online, and resync operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No before it is safe to update the next node.
```
# flashgrid-cluster
```

Note: After the update the flashgrid-cluster command may show the "Configuration check: FAILED" and "Cluster verification: FAILED" messages. This happens because configuration updates are applied locally. This message should disappear after the update is applied to all nodes in the cluster.

After the software update is complete on all nodes, upload diags to FlashGrid support. This will allow FlashGrid support to have up-to-date records of the software versions used on your systems.

Procedure for simultaneous update on all nodes (requires database downtime)

This procedure is recommended for faster deployment of a FlashGrid software update on non-production systems or during a maintenance window when database downtime is allowed.

Create a backup snapshot of the OS disk from all database and quorum nodes

a. Flush OS buffers:
```
# sync; sync
```
b. Create snapshot of the OS disk using the cloud console or CLI.
Make sure there are no nodes that are in offline or resync state. All disk groups must have zero offline disks and Resync = No, by running the following on any node:
```
# flashgrid-cluster
```
Stop all databases
Stop Oracle cluster services, by running the following command on any database node:
```
# crsctl stop cluster -all
```
Stop the FlashGrid Diagnostics monitoring service on all nodes (including storage/quorum):
```
# systemctl stop flashgrid-node-monitor
```
Stop the FlashGrid Storage Fabric services on all nodes (including storage/quorum):
```
# flashgrid-node stop
```
Stop the FlashGrid Cloud Area Network service on all nodes (including storage/quorum):
```
# systemctl stop flashgrid-clan
```
Run the update script as root on all nodes (including storage/quorum). Use the file name with a correct version number.
```
# bash flashgrid_cluster_node_update-X.Y.Z.NNNNN.sh
```
Note: When updating from version 20.06 or earlier, the following error may be reported: FlashGrid Cluster setup not found. In such case, double-check that you are running the update on the correct system and then re-run it with force-cluster command parameter added.
Only if updating the OS simultaneously with the FlashGrid software, install the OS updates:
```
# yum update
```
Reboot all nodes (including storage/quorum). The reboot can be done simultaneously or one by one.
```
# sync; sync; reboot
```
Wait until all nodes boot up, all disks are back online, and resync operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No
```
# flashgrid-cluster
```

After the software update is complete on all nodes, upload diags to FlashGrid support. This will allow FlashGrid support to have up-to-date records of the software versions used on your systems.