Sun Server X4-2L
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
 

Applies to:

Goal

How to Replace a Sun Server X4-2L 24-Slot Disk Backplane.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?:
Sun Server X4-2L Training

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: A Sun Server X4-2L 24-Slot Disk Backplane needs replacement

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

If the system is still up and functioning, customer should perform an orderly and graceful shutdown of applications and OS.  Then power off the server and remove the AC power cords from the system.

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.

1. Power off the server and disconnect the power cords from the power supplies.
2. Extend the server to the maintenance position in the rack.
3. Attach an anti-static wrist strap.

2. Remove the Fan Assembly Door and all of the Fan Modules

1. Using a No. 1 Phillips screwdriver, remove the two screws (one on each side of the chassis) that secure the fan assembly door
2. Slide the fan assembly door toward the rear of the server, and lift and remove the door from the chassis.
3. Using your thumb and forefinger, loosen the captive screw that secures the fan module in the chassis (use a No. 2 Phillips screwdriver if it is too tight to loosen with your fingers).
4. Grasp both the captive screw and the opposite end of the module and lift the fan module straight up and out of the chassis (do not rock it back and forth), and set it aside on an antistatic mat.

3. Remove all of the storage drives from the storage drive cage.

1. On each drive, push the latch release button to open the latch
2. Grasp the latch and pull the drive out of the drive slot.
3. Place the drives on an antistatic mat making sure to note the slot locations that the drives were removed from so that they can be re-installed in their proper slots.

4. Disconnect the cables and remove the storage drive backplane(s)

1. Disconnect the six SAS/SATA cables from the storage drive backplane. Note the cable connections in order to ease proper reconnection of the cables.
2. Disconnect the power cables and the LED cable from the storage drive backplane
3. Using a No. 2 Phillips screwdriver, loosen the two screws that secure the storage drive backplane to the chassis.
4. Lift the storage drive backplane up to release it from the standoff hooks
5. Pull the storage drive backplane away from the standoff hooks and out of the chassis
6. Place the storage drive backplane on an antistatic mat.

5. Install the new storage drive backplane(s) and connect the cables.

1. Lower the storage drive backplane into the server, and position it to engage the standoff hooks
2. Using a No. 2 Phillips screwdriver, install and tighten the two screws to secure the storage drive backplane to the chassis
3. Reconnect the power cables and the LED cable to the storage drive backplane
4. Reconnect the six SAS/SATA cables to the storage drive backplane making sure to connect them in the same order as they were installed previously.

6. Re-install the storage drives into the storage drive cage.

1. Making sure to install the drives back into the same slots from which they were removed align the drive to the drive slot.
2. Slide the drive into the bay until the drive is fully seated.
3. Close the drive latch to lock the drive in place.

7. Re-install the Fans and the Fan Assembly Door.

1. Install the fan modules into the server.
2. For each module press down on the fan module and apply firm pressure to fully seat the fan module.
3. Place the fan assembly door on the chassis and slightly over the fan assembly.
4. Slide the fan assembly door forward and under the lip of the forward top cover until it latches into place
5. Using a No. 2 Phillips screwdriver, install and tighten the screws on each side of the chassis to secure the fan assembly door.

8. Return the Server to operation

1. Remove any anti-static measures that were used.
2. Return the server to it's normal operating position within the rack.
3. Re-install the AC power cords and any data cables that were removed.
4. Power on server. Verify that the Power/OK indicator led lights steady on.

9. Set the system serial number/fruid data if needed.

1. Disk Backplane 0 is the primary psnc container in this server so when it is replaced you will normally need to fix the serial number information.
2. 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) sunx4-2l-sp:~]$showpsnc
   Primary: fruid:///SYS/DBP0
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary           | Backup1           | Backup2           
   ------------------+-------------------+-------------------+-------------------
   PPN                 012345678           32176807+1+1        32176807+1+1       
   PSN                 012345678           1234NM123H          1234NM123H        
   Product Name        SUN SERVER X4-2L    SUN SERVER X4-2L    SUN SERVER X4-2L
   [(restricted_shell) sunx4-2l-sp:~]$exit

3. When Disk Backplane 0 is replaced 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)
4. 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).
5. 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.
6. 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 = *****
7. 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
8. Login using the escuser login and enter escalation mode using the password that was provided by the TSC
   sunx4-2l-sp login: escuser
   Password: ********
   Oracle(R) Integrated Lights Out Manager
   
   Version 3.1.2.32 r82440
   
   Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
   
   -> set SESSION mode=escalation                            
   Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** *
   Short form password is:  NOSE HAAG MED
   
   [(escalation_mode) sunx4-2l-sp:~]#
9. 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) sunx4-2l-sp:~]#showpsnc
   Primary: fruid:///SYS/DBP0
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary           | Backup1           | Backup2           
   ------------------+-------------------+-------------------+-------------------
   PPN                 012345678           32176807+1+1        32176807+1+1       
   PSN                 012345678           1234NM123H          1234NM123H        
   Product Name        SUN SERVER X4-2L    SUN SERVER X4-2L    SUN SERVER X4-2L  
   [(escalation_mode) sunx4-2l-sp:~]# copypsnc Backup1 Primary
   [(escalation_mode) sunx4-2l-sp:~]# showpsnc
   Primary: fruid:///SYS/DBP0
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary           | Backup1           | Backup2           
   ------------------+-------------------+-------------------+-------------------
   PPN                 32176807+1+1        32176807+1+1        32176807+1+1       
   PSN                 1234NM123H          1234NM123H          1234NM123H        
   Product Name        SUN SERVER X4-2L    SUN SERVER X4-2L    SUN SERVER X4-2L
   [(escalation_mode) sunx4-2l-sp:~]# exit
   
   
10. 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.
    
    [(restricted_shell) sunx4-2l-sp:~]$showpsnc
    Primary: fruid:///SYS/DBP0
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0
    
    Element           | Primary           | Backup1           | Backup2           
    ------------------+-------------------+-------------------+-------------------
    PPN                 32176807+1+1        32176807+1+1        32176807+1+1       
    PSN                 1234NM123H          1234NM123H          1234NM123H        
    Product Name        SUN SERVER X4-2L    SUN SERVER X4-2L    SUN SERVER X4-2L  
    [(restricted_shell) sunx4-2l-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
11. If trouble is encountered during any of the steps of accessing escalation mode and fixing the psnc containers please contact the TSC for assistance.

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:
Sun Server X4-2L Documentation

http://docs.oracle.com/cd/E36974_01/index.html

This solution has no attachment