Asset ID: |
1-71-1310451.1 |
Update Date: | 2018-05-17 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1310451.1
:
How to Replace a Sun Fire X4600 CPU Filler Board
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
|
In this Document
Applies to:
Sun Fire X4600 Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
How to Replace a Sun Fire X4600 CPU Filler Board.
Solution
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
No special skills required, Customer Replaceable Unit (CRU) procedure
TIME ESTIMATE: 30 minutes
TASK COMPLEXITY: 0
FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
PROBLEM OVERVIEW: A Sun Fire X4600 CPU Filler Board needs replacement
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :
Data backup not required but recommended as a precaution
Orderly shutdown of applications
Shutdown of OS and power down of server
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Ensure standard ESD procedures are followed
1. Power off the server and unplug (REMOVE) the power cords
2. Remove the main cover
3. Locate the CPU filler board that needs to be replaced
4. Remove the CPU filler board by simultaneously rotating the plastic levers on both sides to 90 degree position and gently lift the board straight up
5. Ensure the plastic levers of the replacement CPU filler board are in the open (vertical) position. Align the module with the guides and gently Insert the replacement CPU filler board into the same bay/slot. Close the levers downwards so they are in flat (horizontal) position
6. Replace the main cover
7. Re-attach power cords
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Power on and bring up system. Verify no issues (all CPUs are visible to OS)
PARTS NOTE:
REFERENCE INFORMATION:
Sun Fire x4600 and Sun Fire x4600 M2 Servers Service Manual
http://download.oracle.com/docs/cd/E19121-01/
Attachments
This solution has no attachment