Sun Storage 6920 System
 

GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
 
GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
 

During a rolling upgrade of a Sun StorEdge 6920, if the upgrade is aborted, or the upgrade fails, then it is possible for the last phase of the upgrade to be missed. This could affect availability of data as hosts can only access mapped volumes. If the mapping and/or volume definition is lost, then the host will be denied access.

This issue can occur on the following platform:

• Sun StorEdge 6920

The described issue has been observed while attempting to upgrade to firmware version 3.0.1.13. However, this issue may be common and generic to the general upgrade process.

A known cause of this issue is for "auto-save" and "auto-failback" to be left in the disabled state. These settings are normally disabled during an upgrade, and re-enabled by the last phase, which executes the UPGRADE STOP command.

When the DSP is rebooted, or MIC failover occurs, it rereads its "startup.cfg" file. If "auto-save" has been disabled, and the DSP is rebooted with the answer "No" to the question "OK to overwrite configuration file[Y]?" - then the "startup.cfg" file is likely to be out of step with the current configuration.

Running with "auto-failback" disabled may also affect the redundancy and availability of the DSP.

If the described issue occurs, after a DSP reboot, DSP volumes may be renamed to "vol/default-volxx". Mappings between hosts and volumes can be lost, or revert back to a previous configurations.

After a failed upgrade, ensure that the following parameters are set to "enabled" in the DSP:

• auto-save
• auto-failback

Running the command "upgrade stop" should set these to the correct value.

There are no further updates planned for this Sun Alert document. If
you need additional assistance regarding this issue, please contact Sun
Services.


This Sun Alert notification is being provided to you on an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU
ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT
OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This
Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.

 
Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

This solution has no attachment