Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1018906.1
Update Date:2017-06-12
Keywords:

Solution Type  Technical Instruction Sure

Solution  1018906.1 :   Sun Storage 3510 FC Array and 3511 SATA Array: Replacing the RAID Controller Module  


Related Items
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3510 FC Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
  •  

PreviouslyPublishedAs
230750


In this Document
Goal
Solution
 SE3000 Controller Replacement for a Dual-Controller Array
 Important Information from the FRU Installation Guide that Should Be Considered
 SE3000 Controller Replacement Considerations in a Single-Controller Configuration
 Saving the NVRAM Configuration Settings Before Replacing a Controller
 Download Locations
References


Applies to:

Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
All Platforms

Goal

This document describes the caveats for replacing a failed RAID controller in a Sun Storage 3510 or 3511 Array, as referenced in the Sun StorEdge 3000 Family FRU Installation Guide. This Guide and all other array documentation may be found on the Oracle Technology Network Oracle Disk Storage Systems Documentation page.

Solution

Caution: It is the recommendation of Product Support that the 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 after the replacement controller is inserted, causing applications to fail and possible file system corruption.

 

SE3000 Controller Replacement for a Dual-Controller Array

When replacing a controller module, follow the steps in Chapter 6 in the Sun StorEdge 3000 Family FRU Installation Guide. It is important to observe static electricity precautions as described in Chapter 1, Section 1.2, "Static Electricity Precautions".

For controllers with 3.2x firmware, 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, modules are hot-swappable, although it is strongly recommended to halt I/O during the replacement 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 Guide that Should Be Considered

When a controller is replaced in a dual-controller configuration, the 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, if the controller replacement FRU has a higher SES firmware version than the surviving controller, there will be a 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 Storage 3511 Array, the router firmware may also 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, the 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

For single-controller FRU replacements, follow the instructions in Section 6.6, "I/O controller Replacement for a single-controller Array" and where applicable, 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.

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 Appendix C, "Record of Settings", in the Sun StorEdge 3000 Family RAID Firmware 4.2x 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 Disk.

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.

 

Download Locations

To download the latest version of the sccli command-line tool, refer to <Document 1004352.1> How to Download and Install Sun Storage Configuration Service Software (SUNWsscs).

To download the latest 3510 firmware, use <Patch 113723-21>.

To download the latest 3511 firmware, use <Patch 113724-12>.

 

Do you still have questions?  You can use My Oracle Support Communities.  Communities put you in touch with industry professionals like yourself.  They are monitored by Oracle support engineers, so you can expect reliable and correct answers.  Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback