Note: In most cases using FlashGrid Cluster Node Update package is recommended for updating FlashGrid software.
Note: Please review the 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, an 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 a rolling fashion is not recommended. FlashGrid services should not be stopped while the GI cluster is in rolling patching mode.
Updating FlashGrid SF and CLAN
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 an 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 Storage Fabric services on the node:
# flashgrid-node stop -
Stop the FlashGrid Cloud Area Network service on the node:
# systemctl stop flashgrid-clan - Update the
flashgrid-sfand/orflashgrid-clanRPMs on the node usingyumorrpmtool. - Run
sudo flashgrid-clan-cfg deploy-config-localafter updatingflashgrid-clanRPM. -
Reboot the node:
# sync; sync # reboot
-
Wait until all disks are back online and resyncing operations are complete on all disk groups before updating the next node. All disk groups must have zero offline disks, and Resync = No.
# flashgrid-cluster
Updating FlashGrid Diags
To update the flashgrid-diags RPM on a node, follow these steps.
- Update the
flashgrid-diagsRPMs using the yum or rpm tool. -
Restart the
flashgrid-node-monitorservice:# systemctl restart flashgrid-node-monitor
Updating FlashGrid Health Check
To update the flashgrid-health-check RPM on a node, follow these steps.
- Update the
flashgrid-health-checkRPMs using the yum or rpm tool. -
Restart the
flashgrid-health-checkservice:# systemctl restart flashgrid-health-check