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-1305700.1
Update Date:2016-01-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  1305700.1 :   How to Remove and Replace a Sun Storage 3510/3511 FC Array Single Controller:ATR:1007:3  


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




In this Document
Goal
Solution
References


Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential).
Reason: FRU CAP

Applies to:

Sun Storage 3510 FC Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 3511 SATA Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

How to Remove and Replace a Sun Storage 3510 FC Array Single Controller

Solution

*DISPATCH INSTRUCTIONS*

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

Time Estimate: 90 minutes

TASK COMPLEXITY: 3

*FIELD ENGINEER INSTRUCTIONS*

PROBLEM OVERVIEW:
Failed controller in single controller configuration. Customer is unable to access array via in-band or out-of-band management. Loss of access to storage array LUNs from host. Amber LED on controller

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :
Previous explorer/extractors would be useful (SCCLI access or extractor will not be possible in a single controller down situation)

Take serial cable.

In Direct Attached configuration, host shutdown. In SAN configuration, shutdown of application(s).
Ensure customer has backups.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
-Check and verify amber LED on controller.
-Attempt serial port access to controller to validate type of controller failure from events.
-Check and verify errors in persistent events (if available).

If controller failure is confirmed and controller replacement is indicated, use the following steps: 

  1. If access is available
    1. Save Nvram to host
      1. sccli>upload nvram [file]
         
    2. Shutdown the controller
      1. sccli>shutdown controller 
  2. Keep the array powered on and make sure that the connected hosts are inactive.
  3. Label cabling and connections from array controller to host/SAN switch, expansion units
  4. Remove cables (Ethernet, Serial, Fibre) and SFPs from controller
  5. Unscrew and disengage thumbscrews on controller from chassis and remove controller by grasping handle.
  6. Install replacement controller and re-attach cables and SFPs
  7. Connect to the serial port of the new controller and, if necessary, power on array
  8. Configure a controller IP so that sccli can be used.
  9. Check for controller status of ok in show fru and show enclosure. Check firmware and SES ( SCSI Enclosure Services) level on new controller
    • sccli>show fru
    • sccli>show enclosure
    • Serial>Main Menu>View System Information
         
  10. If saved configuration is available, use this information to validate firmware revision on the old controller and update/downgrade firmware on new controller as needed. (If no configuration file is available then manual configuration will be required with assistance/input from customer). Ensure that the SES firmware version is appropriate to the main controller firmware, and upgrade if necessary.
  11. Restore NVRAM configuration to new controller. Verify what firmware level was on removed controller. DO NOT restore the NVRAM configuration settings from disk if you replaced a version 3.27 controller with a version 4.1x
    • sccli>download nvram [file]  *Note must be same OS when uploaded
    • Main Menu -> System Functions -> Controller Functions -> Restore NVRAM from disks 
      *WARNING* Only perform this function if you are certain that the NVRAM that was last saved is for the correct firmware.
         
  12. If the nvram cannot be uploaded or nvram on the disks is not valid, then the configuration will have to be manually rebuilt.  
  13. Verify configuration settings with customer - lun mappings, channel IDs, IP address, controller unique identifier

 

 

OBTAIN CUSTOMER ACCEPTANCE
-Record configuration settings and firmware version on new controller
-Obtain extractor

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
-Validate access to storage
-Run explorer/extractor from host


ADDITIONAL COMMENTS:
(Reference Material):
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/

Raid Firmware User's Guide:http://docs.oracle.com/cd/E19487-01/817-3711-18/index.html

SCCLI 2.5 User's Guide: http://docs.oracle.com/cd/E19487-01/817-4951-18/index.html

 

References

<NOTE:1018906.1> - Sun Storage 3510 FC Array and 3511 SATA Array: Replacing the RAID Controller Module
<NOTE:1002641.1> - Sun Storage 3000 Arrays: Troubleshooting Controller Problems

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