Sun ZFS Storage 7420
 
Sun Storage 7410 Unified Storage System
 
Sun Storage 7310 Unified Storage System
 
Sun ZFS Storage 7320
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 

In this Document

Goal

Solution

Preparing for a Software Upgrade

Active-Active cluster configuration

Active-Passive cluster configuration

References

Applies to:

Goal

This document is to provide a guidance for doing a cluster update the correct way.

There are two separate cluster configurations and processes :

Active-Active Cluster
Active-Passive Cluster

Clustered nodes must be upgraded one right after the other.

Important requirement: Before starting the maintenance window, make sure the gzipped firmware tarball has been downloaded and saved on a local host, available to the NAS box in ftp or http.

Review the Release Notes carefully for every version between installed version and version you are going to update to.

Warning: Clustered nodes CANNOT be left at two different code versions longer than 8 hours. Systems left at two different code versions can corrupt data and cause an outage for days in order to repair.

Solution

Preparing for a Software Upgrade

Before you upgrade the software, perform the following actions for clustered controllers.

During the update process, some protocols may experience an outage. See related topics for more information.

1.  Verify your current software version.

In the BUI, go to Maintenance > System.

In the CLI, go to maintenance system updates and enter show

2.  Remove extraneous system updates.

3.  Check the most recent release notes for additional preconditions that should be observed for the software release.

If skipping some software releases, also review the release notes from all applicable previous releases.

See My Oracle Support document Oracle ZFS Storage Appliance: Software Updates (2021771.1)

4. Disable non-critical data services. These services may include replication, NDMP, shadow migration, or others.

Disabling these services can shorten the upgrade time, and ensures that the system has a minimal operation load during the update.

5. Create a backup copy of the management configuration to minimize downtime in the event of an unforeseen failure.

6. Ensure that any resilvering and scrub operations have completed.

In the BUI, go to Configuration > Storage and check the STATUS column next to each pool.

In the CLI, go to configuration storage, enter set pool=    and the name of the pool you want to check, and then enter show

The scrub property indicates whether scrub or resilver operations are active or completed.

7. Ensure that there are no active problems.

In the BUI, go to Maintenance > Problems.

In the CLI, go to maintenance problems show.

8. Perform a health check.

A health check is automatically run as part of the update process, but should also be run independently to check storage health prior to entering a maintenance window.

9. Schedule a maintenance window of at least one hour to allow for disruptions in storage performance and availability during update

Active-Active cluster configuration

Action 1: Upload the appliance firmware onto each head of the clustered system.

Action 2: From cluster node B, click reboot. As a consequence, node B reboots and all resources will be taken over by node A.

Action 3: When the reboot has completed and node B has rejoined the cluster, reset the SP of node B.

Action 4: Follow the upgrade process (See Doc ID 1513423.1) on node B.

- As a consequence of the upgrade, node B will reboot once the software has been upgraded.
- Wait for node B to rejoin the cluster.

Action 5: From cluster node A, click reboot. As a consequence, node A reboots and all resources will be taken over by node B.

Action 6: When the reboot has completed and node A has rejoined the cluster, reset the SP of node A.

Action 7: It is CRITICAL to wait for Hardware (disk firmware) updates to complete on node B.

-> Check using the CLI command "maintenance system updates show"

- Note: HDD FW updates will only be able to complete while cluster is in stripped/owner mode.
- Using Failback too early can result in an unpredictable and unexpected behavior of the cluster, it could even damage pool integrity.

NOTE: JBOD IOM firmware will NOT be upgraded until BOTH cluster heads are running the same Appliance Software Release.
If SIM/IOM firmware exists, these will be completed after the other head is upgraded and rejoined cluster.

Action 8: Follow the upgrade process (See Doc ID 1513423.1) on node A.

- As a consequence of the upgrade, node A will reboot once the software has been upgraded.
- Wait for node A to rejoin the cluster.

Action 9: Failback the cluster to its nominal active/active configuration.

Done

Active-Passive cluster configuration

Assuming node A is active and node B is passive

Action 1: Upload the appliance firmware onto each head of the clustered system.

Action 2: Reset the SP of node B.

Action 3: Follow the upgrade process (See Doc ID 1513423.1) on node B.

- As a consequence of the upgrade, node B will reboot once the software has been upgraded.
- Wait for node B to rejoin the cluster.

Action 4: From cluster node A, click reboot. As a consequence, node A reboots and all resources will be taken over by node B.

Action 5: When the reboot has completed and node A has rejoined the cluster, reset the SP of node A

Action 6: It is CRITICAL to wait for Hardware (disk firmware) updates to complete on node B

-> Check using the CLI command "maintenance system updates show"

- Note: HDD FW updates will only be able to complete while cluster is in stripped/owner mode.

NOTE: JBOD IOM firmware will NOT be upgraded until BOTH cluster heads are running the same Appliance Software Release.

Action 7: Follow the upgrade process (See Doc ID 1513423.1) on node A.

- As a consequence of the upgrade, node A will reboot once the software has been upgraded.
- Wait for node A to rejoin the cluster.

Action 8: Reboot the cluster to its nominal active/passive configuration, as needed

Done

This solution has no attachment