Preparing for Sun StorEdge[TM] 6920 Upgrades

Asset ID:	1-75-1002638.1
Update Date:	2010-08-26
Keywords:

Solution Type Troubleshooting Sure

Solution 1002638.1 : Preparing for Sun StorEdge[TM] 6920 Upgrades

Related Items


Sun Storage 6920 System

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays

PreviouslyPublishedAs
203638

Description
The purpose of this document is not to resolve issues specific to upgrading the StorEdge[TM] 6920 product. It is to address potential planning issues that are common for upgrading the product, and to direct the support path for this action properly.
Common Concerns are:

How to plan for an upgrade
Where to get the latest firmware/baseline image
How to upgrade
How to handle problems during an upgrade

Steps to Follow
Preparing for Sun StorEdge[TM] 6920 Upgrades

1. Please verify whether you are currently in the middle of an upgrade, or
in the planning stages of an upgrade.

If you are planning for an upgrade, continue to step 2.

If you are in the middle of an upgrade, skip to step 3.

2. Please be aware, that Sun recommends the following for any and all Sun StorEdge[TM] 6920 upgrades.

Please review the content of the Product Release Notes for the revision to which you are migrating.
Services Involvement: We recommend that you open a Service Request with us prior to any upgrade action.
Take an outage: We recommend taking an outage for all data services the 6920 provides, during the upgrade. While it is possible to perform a rolling upgrade for some releases, it is not recommended.
Upgrade to the Minimum Recommended Release. The current minimum is 3.0.1.22. The current release is 3.2.0.38.

Note: Upgrades to Releases 3.0.1.26 or 3.2.0.38 REQUIRE a Service Call

Customers who have Sun StorEdge Remote Response(SSRR) activated on their
systems will require a disabling of that service prior to the upgrade. This
de-activation sequence can take up to five(5) business days to complete.

Should you follow our recommendations please collect a Solution Extract.
Details on collecting a solution extract can be found in <Document: 1003756.1>

3. If you are having problems during an upgrade:

Attempt to get a solution extract, as documented above
Please contact your local support representative or support center.

Product
Sun StorageTek 6920 System
Sun StorageTek 6920 Maintenance Update 2
Sun StorageTek 6920 Maintenance Update 1

Internal Comments
Preparing for Sun StorEdge[TM] 6920 Upgrades

This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-os-disk-mid-domain@sun.com

The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK

Internal Employees please note:

If this is a planning issue, a review of the Extractor is absolutely necessary. This will also require the disabling of SSRR. Make your customers aware that servicing the deactivation takes up to 5 business days to complete. You will need to assign a task to radiance group RSS. Please try

to put a date in the summary line. The RSS group will send the CASE OWNER,

the new array password, to be sent to the field for the upgrade. After the upgrade is complete, a NEW TASK to the RSS group needs to be created to ACTIVATE SSRR again.

A review of <Document: 1005447.1> Serves as a basic checklist against the extractor outputs.

An escalation to STORAGE-TSC backline is recommended for the review of the extractor prior to the upgrade. Please put the text "6920 Upgrade Health Check"

in the escalation summary.

Minimum Accepted Levels are detailed in <Document: 1000061.1> Engineers should be recommending the latest revisions available to a customer. The latest revision is release 3.2.0.38

6920, upgrade, troubleshooting, audited
Previously Published As
89107

Change History
Date: 2007-12-10
User Name: 7058
Action: Approved
Comment: Fixed broken link.
Version: 11
Date: 2007-12-10
User Name: 7058
Action: Update Started
Comment: Fix link.
Version: 0
Date: 2007-10-23
User Name: 95826
Action: Approved
Comment: - verified metadata
- changed review date to 2008-09-23
- checked normalized data
- checked for TM - none added
- checked audience : contract
Publishing
Version: 10
Date: 2007-10-23
User Name: 95826
Action: Accept
Comment:
Version: 0

Attachments

This solution has no attachment