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-1305676.1
Update Date:2016-06-06
Keywords:

Solution Type  Technical Instruction Sure

Solution  1305676.1 :   How to Remove and Replace a Sun Storage 3510/3511 FC Array Dual Controller:ATR:1008:3  


Related Items
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3510 FC Array
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP

Applies to:

Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Information in this document applies to any platform.

Goal

How to remove and replace a Sun Storage 3510/3511 FC Array Dual Controller

Solution

*DISPATCH INSTRUCTIONS*

WHAT SKILLS DOES THE ENGINEER NEED:(IS A SITE ENGINEER AVAILABLE?)
Sun StorEdge 3000 Series Training

TIME ESTIMATE: 120 minutes

TASK COMPLEXITY: 3

*FIELD ENGINEER INSTRUCTIONS*

PROBLEM OVERVIEW:
Failed or defective controller in dual controller configuration array.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :
Take serial cable and multiple controller firmware versions.
Extractor/Explorers have been provided.
Ensure customer has backups.
Stop I/O to array if system is not in multipathed configuration.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Check and verify amber LED on controller.
Serial port access to controller to validate the type of controller failure or issues listed in event log.
Verify array health via extractor or sccli access - any undetected hardware issues may lead to further problems during the replacement process

1. Leave array powered on.


2. Connect to Main menu (via serial port or telnet) on the primary active controller.  Verify the controller time, date and timezone settings are correct.  Update if needed

    You can see the Time and date at the top of the Serial port Main Menu.

    If you need to change the time, date or timezone goto:

       Main Menu -> Controller Parameters -> Set Controller Date and Time
                         Select as needed  -> Time Zone
                                                   -> Date and Time

3. Save NVRAM configuration to disk.

    Main Menu -> system Functions -> controller maintenance -> save nvram to disks

4. If both controllers are active, Force fail the controller to be replaced.

    Main Menu -> View and edit Peripheral Devices -> Set Peripheral Device Entry -> Redundant Controller Primary -> Force [Primary / Secondary] Controller ***Select appropriate controller (Primary or Secondary)

5. Verify LED on failed controller is amber.
6. Label and remove cables (Ethernet, Serial, Fibre) and SFPs from controller.
7. Unscrew and disengage thumbscrews on controller from chassis and remove controller by grasping handle or by holding the thumbscrews and pulling out the controller.
8. Install replacement controller and tighten thumbscrews until finger tight. Re-attach cables and SFPs
(The new controller automatically becomes the Secondary controller. The LED will remain amber until the cross-load process completes where the new controller will take on the firmware of the existing controller. This process takes approximately 10 minutes. If the newly installed controller is removed or shutdown during this time it may become inoperable.)
9. Verify firmware on new controller.

    <Ctrl>w (select Secondary Controller) Main Menu -> View System Information

* (If after cross-load completes an alarm is heard, this means that SES and PLD versions on the new controller are not the same as the existing controller. In this case, use the appropriate patch that matches the firmware on the existing controller and follow the README to update/downgrade the SES version, followed by the PLD, if required.)

FIRMWARE UPGRADE
If manual firmware upgrade/downgrade is required, use sccli via a host connected to the array.  An outage may be required, please consult the readme included with the firmware patch.
a. Verify firmware version

    sccli> show inquiry

b. Verify SES and PLD version

    sccli> show ses

c. Ensure you have the correct firmware patch version


d. Download the controller firmware on the array
    sccli> download controller-firmware <Firmware>.bin

    Example: sccli> download controller-firmware SUN423A-3510.bin

    Download the SES on the array
    sccli> download ses-firmware <SES firmware>.s3r

    Example: sccli> download ses-firmware sesfw_3510_1106.s3r

    Download the PLD on the array
    sccli> download <PLD firmware>.s3r

    Example: sccli> download pld-firmware pld1r10.s3r

    Please see patch readme file for specific information on filenames and information on mixed 3510/3511 upgrades.

10. Verify time/date/timzone and battery status.

    sccli> show controller-date  : Note if the date is not correct you can make the correction as advised in Step 1

                            or use the command "sccli set controller-date month day hh:mm:ss year time-zone"

                            For example: # sccli c2t0d0 set controller-date Sep 22 13:43:00 gmt -7

    sccli> show battery-status

Update the in-service date as necessary:

    sccli> show battery-status -u

Recheck battery status

    sccli> show battery-status
    
11.  Check the "Controller Unique Identifier" this should be set to the chassis serial number.
    a.  sccli> show unique-identifier
    b.  sccli> show fru  (chassis/backplane serial number)
            If the unique-identifier does not match the chassis serial number then you can change it using sccli.  This requires a controller reset, and will change the wwn's/ethernet identifiers.
    c.  sccli> set unique-identifier 0 (This will use the chassis serial number after reset)
            Stop all I/O to the hosts
    d.  sccli> reset controller


OBTAIN CUSTOMER ACCEPTANCE
Collect extractor data

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Validate access to storage from hosts

PARTS NOTE:
3.27 FC controller 370-5537-06
4.11G FC controller 370-5537-07 (Must be upgraded to 4.11I or downgraded to 3.27 - not to be left at 4.11G)
4.11I or later FC controller 370-5537-08 (or higher)
4.1x FC controller (RoHS) 371-0532-01
3.27 SATA controller 370-6773-01
4.11G SATA controller 370-6773-02 (Must be upgraded to 4.11I or downgraded to 3.27 - not to be left at 4.11G)
4.11I or later SATA controller 370-6773-03
3.66 SCSI controller 370-5403-05

ADDITIONAL COMMENTS:
(Reference Material):

Sun Storage 3310/3320/3510/3511 Arrays: Identifying and Resolving an Incorrect "Controller Unique Identifier" [ID 1010855.1]
Sun Storage 3000 Arrays: Troubleshooting Controller Problems (Doc ID 1002641.1)
Sun Storage 3510 FC Array and 3511 SATA Array: Replacing the RAID Controller Module (Doc ID 1018906.1)
http://download.oracle.com/docs/cd/E19957-01/816-7326-16/index.html
SE3xxx Firmware Matrix: http://pts-storage.us.oracle.com/products/SE33xx/
Extractor: http://pts-storage.us.oracle.com/products/SE33xx/tools/se3kxtr.036/


References

<NOTE:1018906.1> - Sun Storage 3510 FC Array and 3511 SATA Array: Replacing the RAID Controller Module
<NOTE:1010855.1> - Sun Storage 3310/3320/3510/3511 Arrays: Identifying and Resolving an Incorrect "Controller Unique Identifier"
<NOTE:1002641.1> - Sun Storage 3000 Arrays: Troubleshooting Controller Problems

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