Asset ID: |
1-71-1310605.1 |
Update Date: | 2018-04-03 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1310605.1
:
How to Remove and Replace a Starcat System Controller Hard Disk Drive:ATR:1530:2
Related Items |
- Sun Fire E25K Server
- Sun Fire 12K Server
- Sun Fire 15K Server
- Sun Fire E20K Server
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP
Applies to:
Sun Fire E25K Server - Version Not Applicable and later
Sun Fire E20K Server - Version Not Applicable and later
Sun Fire 12K Server - Version Not Applicable and later
Sun Fire 15K Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
How to remove and replace a Starcat System Controller HDD
********************************************************************************
To report errors or request improvements on this procedure,
please go to http://support.us.oracle.com and put a comment on Doc ID: 1310605.1
********************************************************************************
Solution
CAP PROBLEM OVERVIEW: HDD Peripheral Failure
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE ENGINEER NEED:
Starcat Training. Knowledge of SMS commands.
TIME ESTIMATE: 90 minutes
TASK COMPLEXITY: 2
FIELD ENGINEER INSTRUCTIONS
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :
N/A
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Note: Before shutting down and replacing an SC make sure that clock from the other SC to all components is in a good state. To check this run "showboards -c" command for SMS 1.4 and later. ( See Document ID: *1006413.1 - Check clock status before replacement of System controllerfor more information )
Note: Please review document 1004598.1 Sun FireTM 12K/15K/E20K/E25K: Recovering from a System Controller disk failure for complete recovery procedures.
- Detach all meta-devices on the failed disk using "metadetach" SVM command.
- Metaclear the meta-devices & metadb created on the failed disk
- Powering Off a System Control (SC) Board
- If this is the main SC ensure the spare SC is available.
- Sync the main to the spare
sc% setdatasync backup
If no messages are reported in /var/opt/SUNWSMS/adm/platform/messages and the command completes, the setdatasync backup was successful.
- As a superuser on the main SC, make a backup copy of the SMS configuration:
sc# smsbackup directory
- From the main SC, failover (switch over) to the spare SC by typing:
sc% setfailover force
- On the main SC, verify that it has assumed the main role and that failover is disabled by typing:
sc% showfailover -r
MAIN
sc% showfailover
SC Failover Status: ENABLED
- On the main SC, disable the failover mechanism by typing:
sc% setfailover off
- Verify the failover is DISABLED by typing:
sc% showfailover
SC Failover Status: DISABLED
Note: Before shutting down and replacing an SC make sure that clock from the other SC to all components is in a good state. To check this run "showboards -c" command for SMS 1.4 and later. ( See Document ID: *1006413.1- Check clock status before replacement of System controller*for more information )
- Shutdown the spare sc:
sc_spare# shutdown -y -g seconds -i 0
- Power off the spare (inactive) SC from the main SC by typing the following SMS command:
sc% poweroff scx
- Remove the SC Board
- Removing a System Control Peripheral Board then Remove the failed HDD from the System Control Peripheral Board
- Remove and replace the hard drive, follow the steps, a. Both the HDD's are connected to the interface on a hanging position with the 4 screws for each HDD.
b. Identify the failed HDD as there are clear marking of HDD's location on the board.
c. Remove the four screws from the center plate of the board.
d. Unscrew the first two screws on the other side of the HDD interface.
e. Hold the HDD with one hand and unscrew the remaining two screws on the HDD interface side.
f. Now slide out the HDD from the hanging position.
g. Insert the new HDD in same position and follow the points 1 to 6 in reverse order.
After inserting the system control peripheral board, follow the below steps for powering on & configuring the new HDD
- Powering On a System Control Peripheral Board
- Power on the target SC from the main SC
sc% resetsc
- Verifying the new System Controller HDD.
- Monitor the SCPost to ensure there are no errors.
- Confirm that SMS sees the SC when powered on by typing the following SMS command:
sc% showboards -v |grep SC
SC0 On SC Spare - -
SC1 On SC Main - -
- Check that the /dev/dsk and /dev/rdsk entries are correct and that the Solaris software can access the disks (format, prtvtoc).
- If the console of spare is required use the below command from main sc,
sms-svc>smsconnectsc
Once the spare SC is booted verify the new HDD is detected in Soalris OS.
Monitor the SCPost to ensure there are no errors.
Check that the /dev/dsk and /dev/rdsk entries are correct and that the Solaris software can access the disks (format, prtvtoc).
Follow the SVM root mirroring procedure to mirror the secondary HDD
a. Copy the table content from first disk to second new disk
b. Add the metadb slice
c. Create the meta-devices on new disk
d. Attach all meta-devices on the new disk
On the main SC, enable the failover function.
sc% setfailover on
Verify the failover is ENABLED by typing:
sc% showfailover
SC Failover Status: ENABLED
If situation requires failover the SPARE SC to MAIN SC.
- On the main SC, enable the failover function.
sc% setfailover on
- Attach all meta-devices on the new disk
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
N/A
PARTS NOTE:
The upper disk(target#3) connects to J2 SCSI backplane connector, and the lower disk(target#2) connects to J3.
REFERENCE INFORMATION:
Service Manual: http://download.oracle.com/docs/cd/E19065-01/servers.e25k/index.html
References
<NOTE:1004598.1> - Sun Fire[TM] 12K/15K/E20K/E25K: Recovering from a System Controller disk failure
<NOTE:1006413.1> - Check Clock Status Before Replacement of System Controller
Attachments
This solution has no attachment