Asset ID: |
1-71-1347513.1 |
Update Date: | 2018-05-09 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1347513.1
:
How to Replace a Sun Fire X4170 M2 Motherboard
Related Items |
- Oracle Key Manager
- Sun Fire X4170 M2 Server
- Sun StorageTek Crypto Key Management System
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP
Applies to:
Oracle Key Manager - Version 1.1.0 to 2.5.1 [Release 1.0 to 2.0]
Sun StorageTek Crypto Key Management System - Version All Versions to All Versions [Release All Releases]
Sun Fire X4170 M2 Server - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
Goal
How to Replace a Sun Fire X4170 M2 Motherboard.
Solution
DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE ENGINEER NEED: X4170 M2 Product Training
- TIME ESTIMATE: 90 minutes
- TASK COMPLEXITY: 3
FIELD ENGINEER INSTRUCTIONS
- PROBLEM OVERVIEW: Motherboard Replacement
- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?
System must be offline.
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Prior to removing any part please see following document and NOTE:
How to update product serial number on systems which implement Top Level Identifier functionality (Doc ID 1280913.1)
The Backup 1 FRU ID container of the X4170M2 is on the MB .
To prevent that we can't enable the sunservice user due to bug 16581800
it is required to verify the FRU data on all 3 containers before and after
the MB replacement. I also recommend we should explicit add the comment that just one part with FRU containers should be replaced at a time.
FYI - if the FRU data is just correct on 2 containers and was not automatically updated on the 3rd container AND we replace one part with one valid container we would run into bug 16581800. Therefore I recommend to verify the FRU data of all 3 containers BEFORE we start with the MB replacement and of course finally AFTER the MB replacement.
1. Prepare the server for service
- Check with the customer if there are any customized BIOS settings that will need to be restored on the replacement system board.
- Power off the server and disconnect the power cord(s) from the power supply(ies).
- Remove the server from the rack.
- Attach an antistatic wrist strap.
- Remove the top cover.
2. Removing Motherboard
- Disconnect SAS cables from SAS PCIe card or the on-board SATA connectors on the motherboard.
- If you are removing the motherboard because it has failed and needs to be replaced, remove the following components from the motherboard:
- DDR3 DIMMs.
- PCIe risers and attached PCIe cards.
- CPUs.
- Remove the motherboard.
- Disconnect PDB ribbon cable.
- Remove four screws that secure motherboard to the bus bar.
- Loosen green captive screw on front of the motherboard that secures the motherboard to chassis.
- Using finger loop just below the four screws that secure motherboard to the bus bar, carefully slide the motherboard to rear of chassis, lift out of chassis, and place on an antistatic mat.
- Remove screw that secures finger loop/air plenum to motherboard and set aside.
3. Installing Motherboard
- Install finger loop/air plenum that you removed from old motherboard on replacement motherboard just below the four screw holes that are used to secure motherboard to bus bar.
- Place motherboard into chassis. Position motherboard carefully.
- Install four screws that secure motherboard to bus bar.
- Tighten green captive screw on front of motherboard that secures motherboard to chassis.
- If you are replacing the motherboard because it failed and needed to be replaced, you can now reinstall the reusable components: Memory DIMMS , PCIe risers and attached PCIe cards, CPUs.
- Carefully connect PDB ribbon cable to motherboard.
- Reconnect SAS storage drive cables to SAS PCIe card or on-board SATA connectors located on the motherboard.
4. Return server to operation.
- Install top cover.
- Install server into the rack.
- Return server to normal rack position.
- Reconnect power cord(s) to the power supply(s) and power on server.
- Verify that the AC Present LED is lit.
- If the customer indicated that there were custom BIOS settings that would need to be restored after the board replacement go into the BIOS setup and restore the settings.
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Boot up system and verify full functionality
- PARTS NOTE:Ensure the socket covers are installed on the old motherboard before packaging. Document any socket damage observed on the return tag.
- REFERENCE INFORMATION:
Sun Fire X4170 M2 Server Service Manual
http://download.oracle.com/docs/cd/E19762-01/E22369-02/index.html
SB replacement can lead to to a serial number of '00000000' which will break ASR if the SBs are not reprogrammed after replacement. In order to reprogram the serial number you will first need access into 'Service Mode' and this requires a long password which is obtained from our TSC backline. This 'Escalation' password is needed to reprogram the serial number of the system board.
An Escalation password (similar to service password) is valid for 48 hours, and is provided by our TSC backline. The following information is needed in order for the TSC backline to generate your temporary password granting access to Service Mode in order to reprogram the serial number.
You will initially need to provide the following information:
..ILOM Version? (see "version" output)
..Serial Number? (-> show /SYS [ or /CH ] product_serial_number )
..When you will be onsite? (How soon do you need this escalation password?)
Please refer to document 'x86_serial_number_10_min_1.1.2.pdf' for additional scope on reprogramming the serial number of the system board.
Attachments
This solution has no attachment