Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1018906.1
Update Date:2011-02-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  1018906.1 :   Sun StorEdge[TM] 3510 FC Array and Sun StorEdge[TM] 3511 SATA Array: Replacing the I/O Controller Module  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
230750


Description
This document describes the caveats for replacing a failed controller in a Sun StorEdge[TM] 3510 FC Array or Sun StorEdge[TM] 3511 SATA Array as referenced from the Sun StorEdge[TM] 3000 Family FRU Installation Guide.

NOTE: It is the recommendation by Tier 3 support  that the I/O Controller Modules are "hot-serviceable" and not "hot-swappable". Meaning that all I/O to the array should be stopped before replacing the controller. In some observed cases, I/O is not serviced by the array for up to 10 minutes when the replacement controller is inserted causing applications to fail and possible file system corruption.



Steps to Follow
The following information references the Sun StorEdge 3000 Family FRU Installation Guide.
The latest version can be found at:
http://download.oracle.com/docs/cd/E19957-01/816-7326-16/index.html

SE3000 Controller Replacement for a Dual-Controller Array:

When replacing an I/O Controller Module be sure to follow the correct
'Replacing a Controller' section for the particular SE3000 array type,
after following Section 1.2, Static Electricity Precautions for all procedures.

For controllers with 3.2x firmware,  I/O controller modules are hot-serviceable. Hot-serviceable means that the module can be replaced while the array and hosts are powered on, but all I/O to the array must be stopped during the replacement procedure.

For controllers with 4.x firmware, I/O controller modules are hot-swapable, although it is strongly recommended to halt I/O during the controller replacement procedure.

Caution: All activity between the connected host and the array should cease during this procedure.

If replacement is done while I/O activity occurs, it is possible that hardware errors or configuration errors may be present but undetected, resulting in an unserviceable condition that will only be revealed when the hot-swap is underway. For instance, it is possible that a hardware module might be improperly seated.

It is good practice before replacing a controller FRU to try to verify your system's health. Do not replace a working controller on a channel that is offline.

Important information from the FRU Installation Manual that should be considered:

When a controller is replaced in a dual-controller configuration, the controller firmware of the remaining functional controller automatically overwrites the firmware of the new replacement controller to maintain compatibility. This is referred to as cross-loading. Cross-loading uses the NVRAM configuration settings to synchronize the firmware version of the newly installed controller to match the firmware version of the running controller.

In a dual-controller configuration for FC/SATA, if the controller replacement FRU has a higher SES firmware version than the surviving controller, there will be an SES mismatch with alarms and an amber LED. You must correct the SES mismatch and download the newer SES firmware. For details, see Section 6.3.4, SES Firmware Update Sometimes Required with I/O Controller Module Replacements.

The SES firmware and PLD firmware will have to be upgraded manually if they do not match the existing controller. In a Sun StorEdge 3511 SATA Array, the router firmware may need upgrading if it does not match the existing controller. This can be checked with the sccli show ses command.

Caution: For any firmware upgrade, be sure to follow the upgrade instructions in the patch README file for your array with great care to download and install correctly. If the wrong firmware is installed, or the firmware is installed on the wrong device, your controller might be rendered inoperable. Always be sure to upgrade your SES firmware before trying to determine if you need a PLD upgrade.

SE3000 Controller Replacement Considerations in a Single-controller Configuration:

See Section 6.6 for I/O Controller Replacement for a Single-Controller Array for single controller replacement instructions.

Caution - For FC/SATA single-controller FRU replacements, be sure to follow the instructions in Section 6.6, I/O Controller Replacement for a Single-Controller Array and where necessary, downgrade to firmware version 3.27.
See Section 6.6.1, Downgrading from Controller Firmware Version 4.1x to 3.27 for downgrade instructions.

Caution: All activity between the connected host and the array must cease during the replacement and upgrade/downgrade procedures.

In a single-controller configuration, you cannot restore the NVRAM configuration settings from disk if you replace a version 3.27 controller with a version 4.1x controller. See Section x.6, I/O Controller Replacement for a Single-Controller Array for single controller replacement instructions.

Note: When a controller is installed and initialized or when configuration settings are changed, you are strongly advised to make a record of the new configuration settings and firmware version. This is particularly important in a single controller configuration for re-establishing your configuration settings when a controller is replaced. You can record this information in the Record of Settings appendix in the Sun StorEdge 3000 Family RAID Firmware User s Guide.

Saving the NVRAM Configuration Settings Before replacing a controller:

Save the NVRAM configuration settings to disk. The saved NVRAM file can be used to restore configuration settings only if the replacement controller has the same firmware version as the defective controller.

  1. From the firmware application Main Menu, choose system Functions controller maintenance Save nvram to disks.
  2. Select Yes to confirm. A message informs you that NVRAM information has been successfully saved. Caution: Do not restore the 3.27 NVRAM settings from disk onto a 4.1x controller FRU, or vice versa. The NVRAM structures are incompatible.


Product
Sun StorageTek 3510 FC Array
Sun StorageTek 3511 SATA Array

Internal Comments
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-low-domain@sun.com
<
http://pts-storage.west.sun.com/products/SE33xx/curetoi.html

If you suspect you have a failed crossload during controller replacement, please refer to:
http://pts-storage.west.sun.com/products/SE33xx/toi/nvram.html
for recovery steps. controller, replacement, 3510, 3511, minnow, audited, normalized, hot-swappable, hot-serviceable, I/O, nvram, configuration, NVRAM
Previously Published As
83214

Change History
Date: 2009-12-23
User Name: sue.copeland@sun.com
Action: Update & Currency
Date: 2007-06-29
User Name: 7058
Action: Add Comment
Comment: Notes for Normalizaton:
This document is referenced by: 89127
Subset Root path:
83214-->89127-->89034-->89031-->89050/86520
Project: Minnow Normalization

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback