Sun Storage 7000 Unified Storage System : How to upgrade a clustered systems

Asset ID:	1-71-1447284.1
Update Date:	2012-04-17
Keywords:

Solution Type Technical Instruction Sure

Solution 1447284.1 : Sun Storage 7000 Unified Storage System : How to upgrade a clustered systems

Applies to:

Sun Storage 7410 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7310 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7420 - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7320 - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
This document gives the procedure to upgrade a 7000 cluster

The service manual documentation can be found there :
https://docs.oracle.com/cd/E26765_01/html/E26399/maintenance__system__updates.html#maintenance__system__updates__cluster_upgrade

Goal

This document is to provide a guidance for doing a cluster update the right way.
There are two separate cluster configurations and processes :

Active-active cluster
active-passive cluster

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

Fix

There are two different cluster configurations and therefore different processes, the following will give an outline of the steps necessary to do the a sucessful cluster update.

1. Active-Active cluster configuration

Action 1: Upload the appliance firmware onto each head of the clustered system. This can be done any time upfront and shorten the maintenance window, as no takeover or failback is required.

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

Action 3: Reset SP of node B

Action 4: Follow the upgrade process 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 B, click takeover. As a consequence node A reboots and all resources will be taken over by node B.

Action 6: Reset SP of node A

Action 7: Follow the upgrade process 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.

Done

2. Active-Passive cluster configuration

A takeover is not needed, a mere failback allows the active node to own all resources. A takeover is also possible and can be considered as safer, as the head reboots with a clean configuration.

Action 1: Upload the appliance firmware onto each head of the clustered system. This can be done any time upfront and shorten the maintenance window, as as no takeover or failback is required if both cluster nodes own private aministration interfaces.

Action 2: From cluster node B click failback. As a consequence node B exports all resources and they will be taken over by node A.

Action 3: Reset SP of node B

Action 4: Follow the upgrade process 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 B click takeover. As a consequence node A reboots and all resources will be taken over by node B.

Action 6: Reset SP of node A

Action 7: From node A follow the upgrade process. As a consequence of the upgrade, node A will reboot once the software has been upgraded. Wait for node A to rejoin the cluster.

Done

Attachments

This solution has no attachment