The following procedure applies to minor updates. Minor updates are those that have the same first two numbers in the version number, for example, from 18.1.30 to 18.1.50. However, update from 18.1 to 18.9 is considered major and may require a different procedure. Contact FlashGrid support for assistance if you need to do a major version update.
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.
To update flashgrid-sf and/or flashgrid-clan RPMs on a running cluster repeat the following steps on each node, one node at a time
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.
If the node is a database node,
a. Stop all local database instances running on the node.
b. Stop Oracle CRS:
# crsctl stop crs
Stop the FlashGrid Storage Fabric services:
# flashgrid-node stop
Stop the FlashGrid Cloud Area Network service, if installed:
# systemctl stop flashgrid-clan
flashgrid-clan(if installed) RPMs using
sudo flashgrid-clan-cfg deploy-config-localafter updating
Reboot the node
Wait until all disks are back online and resyncing operations complete on all disk groups before updating the next node. All disk groups must have zero offline disks and Resync = No.
To update flashgrid-diags RPM on a node
Update the flashgrid-diags RPMs using yum or rpm tool
Restart the flashgrid-node-monitor service:
# systemctl restart flashgrid-node-monitor