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

Solution Type  Technical Instruction Sure

Solution  1305639.1 :   How to Remove and Replace a Sun Storage 3510/3511 Midplane:ATR:1011:3  


Related Items
  • Sun Enterprise 3500 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
  •  




In this Document
  Goal
  Solution


Oracle Confidential (INTERNAL). Do not distribute to customers
Reason: FRU CAP

Applies to:

Sun Enterprise 3500 Server - Version: Not Applicable and later   [Release: N/A and later ]
Information in this document applies to any platform.

Goal

How to Remove and Replace a Sun Storage 3510/3511 Midplane

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:(IS A SITE ENGINEER AVAILABLE?)

S3000 series training, including knowledge of Firmware Main Menu

TASK COMPLEXITY: 3

TIME ESTIMATE: 60 minutes

FIELD ENGINEER INSTRUCTIONS

PROBLEM OVERVIEW:

Midplane/Chassis is damaged and needs to be replaced.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

1) Data backup and extractor (out of band) recommended .

2) Stop any I/O activity between the hosts and the array.

3) For SCSI arrays only (3310/3320/SCSI JBODs), shutdown the hosts connected to the array.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

1) Be sure that the array is powered off

2) Be sure that all cables are properly labeled and take note of their original location to avoid mistakes when reconnecting them at the end of the replacement procedure.

3) Disconnect all the cables from the array (both power and signal cables).

4) Remove all components by pulling them out from the chassis, including all disks, power supplies, batteries, controllers, I/O modules, etc.

5) Replace the defective midplane/chassis

6) Insert all components into the new midplane/chassis, including all disks, power supplies, batteries, controllers, I/O modules, etc.

7) Reconnect all the cables back to their original location.

8) Power on the array(**)

For 3310/3320 and SCSI JBODs, take note of the physical location for each disk drive before removing them, as they need to be inserted back into the same location as they were before the midplane/chassis was replaced.

(**) For 3510/3511 the midplane/chassis defines the WWNs for the controllers and other components in the array, including all LUNs. Many SAN features are implemented based on the LUNs WWN (such as LUN filtering, switch zoning, etc). Be aware that some configuration changes in the hosts , switches and array may be needed after the midplane/chassis replacement to reflect the WWN changes.

9) Verify switch ID setting is the same as the replaced midplane.

See Document: 1012692.1 concerning duplicate box ids.

10) Check array unique id . Does unique ID need to be set to old unique ID?

Configuring the new array with the old unique ID may be necessary if device ids must persist)

From sccli prompt, show unique-identifier

From the RAID firmware Main Menu, choose "view and edit Configuration parameters → Controller Parameters → Controller Unique Identifier <hex>."

11) Confirm status of FRUs , logical drives, controller redundancy status

12) Run another extractor (out of band)

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

1) Restart the hosts connected to the array (SCSI arrays only).

2) Verify that the hosts can access the same LUNs as before the midplane/chassis replacement.

3) Resume I/O activity.



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