Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1981290.1
Update Date:2017-06-09
Keywords:
Solution Type  Technical Instruction Sure

Solution  1981290.1 :   FS System: How to Remove and Replace a Power Supply in an FS1-2 Pilot  

Related Items 
    

  • Oracle FS1-2 Flash Storage System
    •  
  • Oracle FS1-2 Cloud System
    •  
Related Categories 
    

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






In this Document


Goal


Solution


References


Applies to:  

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Oracle FS1-2 Cloud System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.



Goal


Outline the steps required to replace an FS1-2 Pilot Power Supply Unit (PSU) using Guided Maintenance.


 


Solution


DISPATCH INSTRUCTIONS
 
 - WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED: 
 
 Product knowledge, FS1-2 Flash Storage System
 
 TIME ESTIMATE: 45 minutes
 
TASK COMPLEXITY: 0
 
 FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:


If you are not very familiar with servicing the Sun Server X4-2 upon which the Pilot is based, it is highly recommended that you look at the animation videos that detail the replace procedures covered in this Caned Action Plan (CAP).  They are available at the Oracle Server Animations.



PROBLEM OVERVIEW: 


FS1-2 Pilot power supply.


What: A Pilot power supply in an FS1-2 has failed and needs to be replaced. 


Where: A failed power supply will have a System Alert for the affected Pilot. 


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


The Pilot with the power supply failure will have a warning status.


 


NOTE: Please review the Knowledge Document 1942676.1 FS System: How to Disable Call Home to Prevent Automatic Service Request ASR Generation before proceeding with the procedure below. The steps contained therein are provided to allow an administrator to de-activate a particular ASR enabled array while performing maintenance or troubleshooting. This will prevent any additional Service Requests from being created unnecessarily.


 


NOTE: The FS1-2 Pilot uses a quorum mechanism for Key Identity Properties (KIP).  The quorum is comprised of the motherboard, disk backplane and power supply 0 which are all encoded with the Product Serial Number (PSN) of the Pilot (not the FS1-2).  At least two of these must agree on the correct PSN or the Pilot will NOT boot.  So as to avoid this problem, this process has the user confirm the PSNs are in sync before attempting the replacement.  NEVER replace one of these quorum devices if the PSNs are not in sync and NEVER replace two of these items at the same time.


  


QRC for this procedure:


Pilot Power Suplly QRC


WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:


    

  1. If replacing power supply 0 (PS0) you must confirm Product Serial Number Containers (PSNCs) are currently synchronized.  If PS1 is being replaced, skip to step #2.
    2. 

      

    1. Use ssh to access the Pilot where the Power Supply is being replaced.
      2. 

        

      1. Software versions prior to R6.1.12 had ssh enabled from the factory.  For versions R6.1.12 and newer, it can be enabled using fscli (30 minutes in this example):

        

        # fscli system -modify -enableSsh 30
        
  
        2. 

      2. Use Putty or similar software to log into the problem Pilot using root/a1s2d3f$

        

        # ssh <IP address of Pilot with failed PS0>
        
  

        3. 

      

    2. Now use ssh to access the bad Pilot's ILOM, changeme is Oracle's default password and should not be changed.

      

      [root@pilot2 ~]# ssh 169.254.2.5 
      Password: 

      Oracle(R) Integrated Lights Out Manager 

      Version 3.1.2.10.b r77700 

      Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved. 

      Warning: password is set to factory default. 

      ->
      
  

      

      NOTE: using the IP address of 169.254.2.5 will ALWAYS connect you to that Pilot's ILOM.  In the example above, starting from Pilot 2, the connection is being made to Pilot 2's ILOM.
      


      3. 

    3. Enter restricted session mode and run the showpsnc command.

      

      -> set SESSION mode=restricted 

      WARNING: The "Restricted Shell" account is provided solely 
      to allow Services to perform diagnostic tasks. 

      [(restricted_shell) ORACLESP-1307FML0VY:~]# showpsnc 
      Primary: fruid:///SYS/DBP0 
      Backup 1: fruid:///SYS/MB 
      Backup 2: fruid:///SYS/PS0 

      Element           | Primary           | Backup1           | Backup2 
      ------------------+-------------------+-------------------+------------------- 
      PPN                 7056044             7056044             7056044 
      PSN                 1307FML0VY          1307FML0VY          1307FML0VY <==== Product Serial Numbers must match.
      Product Name        SUN FIRE X4170 M3   SUN FIRE X4170 M3   SUN FIRE X4170 M3 
      [(restricted_shell) ORACLESP-1307FML0VY:~]#
      
  


      4. 

    4. If all 3 PSNs match, exit all the way out of the FS1-2 and proceed to step 2.
      5. 

    5. If the Disk BackPlane 0 (DBP0) and Motherboard (MB) are the same but Power Supply 0 (PS0) is different, it is safe to proceed to step 2 since that power supply will be replaced.
      6. 

    6. If any other condition exists, STOP!! and re-engage the TSC for steps to correct before proceeding to replace the failed power supply.
      7. 

    7. Type exit twice to terminate the ssh sessions.

      8. 

    

  2. Prepare FS1-2 for service procedure.
    3. 

      

    1. Disable Call-Home to prevent spurious alerts (see Document 1942676.1 FS System: How to disable Call Home to prevent Automatic Service Request ASR Generation).
      2. 

    2. Use ESD precautions.
      3. 

    3. Log into Oracle FS System Manager to access Guided Maintenance:
      4. 

        

      1. Select System tab
        2. 

      2. In the navigation tree, expand Hardware and select Pilots
        3. 

      3. In the main window, right click on the Pilot with the failed motherboard and select Repair Pilot.
        4. 

      4. In the pop-up Repair window, select Power supply followed by the Next button.
        5. 

      5. Follow the steps in Guided Maintenance to identify the Pilot and power supply location.

        6. 

      

    

  3. Remove the defective Pilot power supply.
    4. 

      

    1. Deploy the anti-tip legs in the front of the rack.
      2. 

    2. Slide the Pilot into the service position.
      3. 

    3. If power supply 0 is being replaced, access is increased if you disconnect the Cable Management Arm (CMA) behind the Pilot near the power supplies.
      4. 

        

      1. Lift the tab at the rear of the hinge in the CMA behind the power supplies.
        2. 
Slide the hinge rearward until it is free of the slide rail.

      2. Gently push the CMA away from the power supply area.
        3. 

      

    4. Unplug the power cord from defective power supply.
      5. 

    5. Push green tab inward and use the handle to remove the power supply. 

      6. 

    

  4. Install replacement Pilot power supply.
    5. 

      

    1. Insert the replacement power supply.
      2. 

    2. Attach the power cord.
      3. 

    3. Reattach the CMA hinge behind the power supplies.
      4. 

        

      1. Guide the tab at the front of the hinge into the slot on the slide rail.
        2. 

      2. With the hinge flush against the slide rail, gently push the hinge forward until it snaps back into place.
        3. 

      

    4. If power supply 0 was replaced, the Pilot's ILOM must be reset.  This can be done by one of the following methods:
      5. 

        

      1. SSH: Following the procedure in step 1, re-establish the ssh session with the Pilot that just had the power supply replaced and run the following command:

        

        #[root@pilot2 ~]# ipmitool -H 169.254.2.5 -U root -P changeme sunoem cli "reset /SP" "y" 
        Connected. Use ^D to exit. 
        -> reset /SP 
        Are you sure you want to reset /SP (y/n)? y 
        Performing reset on /SP 
        -> 
        Session closed 
        Disconnected 
        [root@pilot2 ~]# #
        
  
        2. 

      2. Use a paper clip or similar item to reset the SP (ILOM) button in the rear of the Pilot

        Pilot ILOM Reset Button

        

        NOTE: after depressing the reset button, the SP LED in the front left side of the Pilot will start to blink for about 2 minutes indicating it is rebooting.
        
  

        NOTE: Resetting the ILOM/SP will not cause the Pilot itself to reboot.  As such, there will be no interruption to the functions being performed by the Pilot.
        
  
        3. 

      

    5. Using the procedure in step 1 above, confirm the PSNCs are still in sync.
      6. 

    6. If the PSNCs are NOT in sync, escalate to Oracle support before any other maintenance is performed on this Pilot.
      7. 

    7. Type exit to terminate ssh session.

      8. 

    

  5. Return Pilot to FS1-2 System.
    6. 

      

    1. Return the Pilot to the rack position.
      2. 

    2. Return the anti-tip legs to their normal position.
      3. 

    3. When finished, re-enable Call-Home.
      4. 

    




OBTAIN CUSTOMER ACCEPTANCE



WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:


 Confirm the System Alert associated previously is gone and the FS1-2 status is normal/green.



REFERENCE INFORMATION:


 From the Oracle Help Center: http://docs.oracle.com/en/storage/#fla select the Oracle Flash System Documentation Library for more information.



Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback