Firmware Updates; What Happens To The Gui During Failover - HPE StoreOnce 6500 User Manual

Firmware updates

Firmware updates for system components, such as hard disk drives and BIOS, are included in the
software update package, but they are not implemented as part of the software update process.
You can implement firmware updates in two ways:
• You can use the StoreOnce CLI command hardware update firmware to implement firmware
updates.
See the StoreOnce System CLI Reference Guide for more information on using the command.
• You can initiate a check on installed firmware and then upgrade firmware using the StoreOnce System
Management GUI. See Firmware page on page 166.

What happens to the GUI during failover

NOTE: If the node that fails is not the active Management Console, failover will be transparent to the
user. Events and emails or SNMP (if configured) will notify the user that failover has occurred. It is also
possible to track the progress of failover on the GUI screens as illustrated in this section.
If the node that fails is the active Management Console, users will be logged off and must log back in
again once services are resumed. Even if the failed node is not the active Management Console, Hewlett
Packard Enterprise recommends logging out and logging back into the GUI to refresh it after a failover.
The StoreOnce System page and all the configuration pages below it in the navigator contain a list of all
the configured service sets and their current status.
Example:
There is a single couplet with two service sets. Service Set 1 is currently running on its main node.
Similarly, Service Set 2 is currently running on its main node (and each is configured to be the failover
node for the other).
In the event of a hardware problem that causes the main node on Service Set 1 to fail, the service set
stops temporarily while failover occurs.
As failover progresses, the service set status changes to Unknown.
On completion, the service sets information shows Service Set 1 and Service Set 2 both running on the
same Current Node; the failed node has moved to the failover node without any user intervention and
both service sets are now running correctly.
242 Firmware updates