Asset ID: |
1-71-1310664.1 |
Update Date: | 2018-04-03 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1310664.1
:
How to remove and replace a Starcat System Control Peripheral Board:ATR:1540: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 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
Sun Fire E25K Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
How to remove and replace a Starcat System Control Peripheral Board
Solution
CAP PROBLEM OVERVIEW: System Controller Peripheral Board Failure
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE ENGINEER NEED:
Starcat Training
knowledge of SMS commands
DELIVERY REQUIREMENT:
schedule with maintenance window
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 controller for more information )
If the affected SCper is the spare goto step 6.
- 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: DISABLED
- 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
- 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 and Replace the SC Peripheral Board.
- Remove the connector protective cover from the board being installed and inspect the connector for any damaged or gaps between the pins.
- Ensure board alignment tabs are not bent.
- Inspect the mating connector before inserting the new board.
- Install SC Peripheral Board
- Power on SC Peripheral Board. ( From the main SC type: )
sc% resetsc
- Verify System Control (SC) Peripheral Board
- Monitor SCPOST for any error messages during SC boot. SCPOST messages are output to an SMS console. To read SC SMS console messages, you must attach a console cable and terminal to the SC.
- Ensure that Solaris software can communicate to all the peripheral devices.
- For the DVD-ROM, insert a CD and ensure it mounts properly.
- For hard disks, check that the /dev/dsk and /dev/rdsk entries are correct and that the Solaris software can access the disks (format, prtvtoc).
- For the DAT drive, check that the /dev/rmt entries are correct and that the Solaris software can access the tape device (mt status).
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
N/A
PARTS NOTE:
FRU contains no disks, tape and DVD drive.
REFERENCE INFORMATION:
Service Manual: http://download.oracle.com/docs/cd/E19065-01/servers.e25k/index.html
TIME ESTIMATE:
60 mins
Attachments
This solution has no attachment