Updating FlashGrid software and Linux kernel 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
Linux kernel (can be skipped)

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.

Note: Please review corresponding release notes and check with FlashGrid support before performing any major version update. A major version consists of the first two numbers. The third number represents a revision (hotfix). For example, update from version 19.02.x to 19.05.x is major, but from 19.05.100 to 19.05.200 is a hotfix revision.

Note: 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.

Note: When updating to version 21.06 or later on RHEL 7, jq package must be installed manually before the update, unless EPEL repo is enabled. On OL7 the jq package will be installed automatically, and no manual action is needed. If the jq package is missing during the update then the following error may be reported: "No package jq available. Error: Nothing to do". To install the jq package, download and install the jq rpm and its dependencies: libjq1, oniguruma, jq.

Note: For OS upgrade from RH/OL 7.5, please check Issues and Mandatory Steps before performing upgrade.

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
```
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 re-syncing 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.

Example with kernel update:
```
# bash flashgrid_cluster_node_update-19.5.17.85011.sh
```
Example without kernel update:
```
# bash flashgrid_cluster_node_update-19.5.17.85011.sh skip-kernel-update
```
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 command parameter added.
Reboot the node:
```
# sync; sync
# reboot
```
Before updating the next node, wait until the node boots up, all disks are back online, and resyncing 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 update, flashgrid-cluster command may show the "Configuration check: FAILED" message. 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.