Asset ID: |
1-71-1598232.1 |
Update Date: | 2016-01-20 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1598232.1
:
How to Replace the Fan Board in an Oracle Exalytics X2-4 or X3-4 system
Related Items |
- Exalytics In-Memory Machine X2-4
- Exalytics In-Memory Machine X3-4
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
|
Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential).
Reason: internal support doc All Exalytic components are FRU replaced
Applies to:
Exalytics In-Memory Machine X2-4 - Version Not Applicable to Not Applicable [Release N/A]
Exalytics In-Memory Machine X3-4 - Version All Versions to All Versions [Release All Releases]
x86_64
Goal
How to Replace the Fan Board in an Oracle Exalytics X2-4 or X3-4 system
Solution
CAP PROBLEM OVERVIEW: Fan Board replacement
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE ENGINEER NEED:
Oracle Exalytics Server Training.
TIME ESTIMATE: 60 minutes
TASK COMPLEXITY: 3-FRU
FIELD ENGINEER INSTRUCTIONS
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :
If the system is still up and functioning, the customer should perform an orderly and graceful shutdown of applications and OS.
A data backup is not a prerequisite but is a wise precaution.
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
1. Prepare the server for service.
- Power off the server and disconnect the power cords from the power supplies.
- Extend the server to the maintenance position in the rack.
- Attach an anti-static wrist strap.
- Remove the top cover.
- Disconnect any cables plugged into the USB or video connectors on the front of the server.
2. Remove all fan modules
- For each fan module grasp the handle on the fan module using your thumb and forefinger
- Lift the fan module straight up and out of the chassis and set it aside on an antistatic mat. (Caution- When removing a fan module, do not rock it back and forth. Rocking the fan module can cause damage to the fan board connectors)
3. Remove all memory risers
- For each of the memory risers lift them straight up to remove them from the memory module socket.
- set each memory riser aside on an antistatic mat. Attention to the removal order should be taken so that the modules can be replaced in the same locations from which they were removed.
4.Remove the fan board
- Loosen the three captive screws connecting the front memory riser guide to the motherboard.
- Remove the two screws on each side of the outside of the chassis that hold the fan board unit in place.
- Unplug the fan board cable and power cables from motherboard.
- Remove the front memory riser guide by pulling it up and out of the chassis.
- Pull the fan board back and out of chassis.
- set the fan board aside on an antistatic mat
5.Install the replacement Fan Board
- Unpack the replacement fan board unit and place it on an antistatic mat.
- Remove the fan board cable and power cables from the faulty fan board unit and plug them into the fan board on the replacement fan board unit.
- Insert the fan board unit into the chassis, moving it down and toward the front.
- Reposition the front memory riser guide, routing the fan board and power cable through the riser guide.
- Plug the fan board cable and power cable into the connectors on the motherboard.
- Tighten the three captive screws to hold the front memory riser guide in place.
- Secure the fan board unit in place by reinserting and tightening the two screws on each side of the outside of the chassis.
6. Reinstall all the fan modules.
- Install the fan modules back into the server. (The fan modules are keyed to ensure that they are installed in the correct orientation)
- Press down on each of the fan modules and apply firm pressure to fully seat the fan modules.
7. Reinstall all memory risers.
- Align each memory riser with it's riser slot on the motherboard.
- Push each memory riser module into it's associated CPU memory riser slot until the riser module locks in place.
8. Return the Server to operation
- Replace the top cover
- Remove any anti-static measures that were used.
- Return the server to it's normal operating position within the rack.
- Re-install the AC power cords and any data cables that were removed.
- Power on server. Verify that the Power/OK indicator led lights steady on.
9. Set the system serial number if needed.
- The fan board is the primary psnc container in this server so when it is replaced you will normally need to fix the serial number information.
- login to the ILOM as root and then enter the restricted shell to check the psnc values. Follow the example below to enter restricted shell and use the showpsnc command
-> set SESSION mode=restricted
WARNING: The "Restricted Shell" account is provided solely
to allow Services to perform diagnostic tasks.
[(restricted_shell) exalytics0-sp:~]$showpsnc
Primary: fruid:///SYS/FB
Backup 1: fruid:///SYS/DBP
Backup 2: fruid:///SYS/MB
Element | Primary | Backup1 | Backup2
------------------+-------------------+-------------------+-------------------
PPN 0123456789 30142678+1+1 30142678+1+1
PSN 0123456789 1234MED00A 1234MED00A
Product Name SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER
[(escalation_mode) exalytics0-sp:~]# exit
- With a fan board replacement the Primary psnc container will likely not match the Backup entries. If it does not you must enter escalation or service mode to fix it (if all three entries match this step is done)
- Contact the TSC to request an escalation password (service mode will work also if just the copypsnc command ends up needing to be used, if the setpsnc command is needed escalation mode is required. setpsnc is not covered in this procedure).
- Provide your TSC contact the output from the following ILOM commands- "version", "show /SYS product_serial_number", and "show /SP/clock". If the product_serial_number information does not give good output then provide the showpsnc output that was see in step b above as well.
- The TSC will provide an escalation password that is made up of 30 short words. Follow the example below to create a new user with the 'Service' role assigned. The Service role is required to access service or escalation modes. In the following example we will create a user named 'escuser' with the service role.
-> cd /SP/users
/SP/users
-> create escuser
Creating user...
Enter new password: ********
Enter new password again: ********
Created /SP/users/escuser
-> set escuser role=aucros
Set 'role' to 'aucros'
-> show escuser
/SP/users/escuser
Targets:
ssh
Properties:
role = aucros
password = *****
- set the check_physical_presence to false and then exit from the ILOM so that you can login as the newly created user.
-> set /SP check_physical_presence=false
Set 'check_physical_presence' to 'false'
-> show /SP check_physical_presence
/SP
Properties:
check_physical_presence = false
-> exit
- Login using the escuser login and enter escalation mode using the password that was provided by the TSC
exalytics0-sp login: escuser
Password: ********
Oracle(R) Integrated Lights Out Manager
Version 3.1.2.24.c r81341
Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
-> set SESSION mode=escalation
Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** *
Short form password is: HOSE HAAG YAP
[(escalation_mode) exalytics0-sp:~]#
- Use the showpsnc command to confirm the current container values. Confirm that one of the backup containers has a serial number (the value on the PSN line) that matches the system serial number. The system serial number can be checked by comparing to the serial number RFID tag on the front left hand side of the server. After confirming that there is a valid psnc backup use the copypsnc command to write the good data from the backup to the primary container on the fan board. The following example shows copying from backup1 to the primary but you could also copy from backup2 if needed.
[(escalation_mode) exalytics0-sp:~]# showpsnc
Primary: fruid:///SYS/FB
Backup 1: fruid:///SYS/DBP
Backup 2: fruid:///SYS/MB
Element | Primary | Backup1 | Backup2
------------------+-------------------+-------------------+-------------------
PPN 0123456789 30142678+1+1 30142678+1+1
PSN 0123456789 1234MED00A 1234MED00A
Product Name SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER
[(escalation_mode) exalytics0-sp:~]# copypsnc Backup1 Primary
[(escalation_mode) exalytics0-sp:~]# showpsnc
Primary: fruid:///SYS/FB
Backup 1: fruid:///SYS/DBP
Backup 2: fruid:///SYS/MB
Element | Primary | Backup1 | Backup2
------------------+-------------------+-------------------+-------------------
PPN 30142678+1+1 30142678+1+1 30142678+1+1
PSN 1234MED00A 1234MED00A 1234MED00A
Product Name SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER
[(escalation_mode) exalytics0-sp:~]# exit
- At this point if all of the psnc containers match and have the correct serial number data this step is done. If more than one of the psnc containers had non-valid entries then the copypsnc command should be used to copy over the valid data to the other container that is not valid. (ie. "copypsnc Backup1 Backup2" to copy backup1 to backup2) After confirming all psnc data is correct reset the ILOM to confirm that the psnc data persists through a reboot and remove the escalation user if needed.
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
Performing reset on /SP
..........
***login as the root user again and check the psnc data***
-> set SESSION mode=restricted
WARNING: The "Restricted Shell" account is provided solely
to allow Services to perform diagnostic tasks.
[(escalation_mode) exalytics0-sp:~]# showpsnc
Primary: fruid:///SYS/FB
Backup 1: fruid:///SYS/DBP
Backup 2: fruid:///SYS/MB
Element | Primary | Backup1 | Backup2
------------------+-------------------+-------------------+-------------------
PPN 30142678+1+1 30142678+1+1 30142678+1+1
PSN 1234MED00A 1234MED00A 1234MED00A
Product Name SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER SUN FIRE X4470 M2 SERVER
[(escalation_mode) exalytics0-sp:~]# exit
-> cd /SP/users
/SP/users
-> delete escuser
Are you sure you want to delete /SP/users/escuser (y/n)? y
Deleted /SP/users/escuser
- If trouble is encountered during any of the steps of accessing escalation mode and fixing the psnc containers please contact the TSC for assistance.
10. Allow the system to power up and confirm that it functions properly.
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
REFERENCE INFORMATION:
Oracle Exalytics In-Memory Machine Documentation Library
http://docs.oracle.com/cd/E41246_01/index.htm
Sun Server X2-4 Documentation
http://docs.oracle.com/cd/E20781_01/index.html
Attachments
This solution has no attachment