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-1947995.1
Update Date:2017-12-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  1947995.1 :   FS System: How to Remove and Replace a SAS HBA 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
  •  


Instructions on how to replace a Pilot SAS HBA in an FS1-2.

In this Document
Goal
Solution
References


Applies to:

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

Goal

The purpose of this document is to outline the steps required to replace an FS1-2 Pilot SAS HBA using the Guided Maintenance.

Solution

DISPATCH INSTRUCTIONS

- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:

Product knowledge, FS1-2 Flash Storage System

TIME ESTIMATE: 30 minutes

TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW:

What: The Pilot SAS HBA in an FS1-2 has failed and needs to be replaced. 

Where: There will be a System Alert that identifies the problem Pilot. 

Why: An FS1-2 Pilot SAS HBA has failed.

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

The Pilot with the SAS HBA failure will have a warning status.  The other Pilot must have a normal status as this procedure requires a Pilot failover if the problem is detected on the current active Pilot.  The problem Pilot must be powered off in order to replace the failed SAS HBA.

NOTE: At this time, the only PCIe card in any of the Risers is a SAS HBA card in Riser 3.

 

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.

QRC for this procedure:

Pilot SAS HBA QRC

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

  1. Prepare the FS1-2 for service procedure.
    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. Use ESD precautions.
    3. Log into Oracle FS System Manager to access Guided Maintenance:
      1. Select System tab
      2. In the navigation tree, expand Hardware and select Pilots
      3. In the main window, right click on the Pilot with the failed SAS HBA and select Repair Pilot.
      4. In the pop-up Pilot Repair window, select SAS HBA from the pull-down menu and the click on Next.
      5. Follow the steps in Guided Maintenance to identify and place the Pilot offline.

  2. Access the SAS HBA.
    1. Deploy the anti-tip legs in the front of the rack.
    2. Slide the Pilot into the service position.
    3. Unplug both power cords.
    4. Open the Fan door to make top cover removal easier.
    5. Slide the Top Cover back and remove.

  3. Remove the SAS HBA.
    1. Optional - remove the PCIe filler by pulling up on green colored lever in the rear outside of the chassis.
    2. Remove the Riser by lifting the release tab and lift it clear of the Pilot chassis.
    3. Unplug the SAS cables connected to the SAS HBA.  Be sure to note which cable goes into which port on the HBA.
    4. Note the slot the SAS HBA is in and then remove it from the Riser.

      NOTE: If the Pilot is an X5-2 version, check to see if an Oracle System Assistant (OSA) USB drive is installed internally on the Pilot motherboard.  If one is installed, proactively remove it.  While having the OSA USB drive installed does not affect day to day operations of the FS1-2, it will create problems if the Pilot needs to be re-imaged in the future.


  4. Install the replacement SAS HBA
    1. Install the replacement SAS HBA into the same slot of the Riser.
    2. Reconnect the SAS cables to the HBA.
    3. Install the Riser back into the motherboard.  Be sure to catch the slot on the chassis with a tab on the SAS HBA.
    4. Lock it in place by returning the release tab to the secure position.
    5. If filler was removed in step 9, re-install it by inserting the tab into the slot on the Riser and lock it in place with the lever.
    6. Close the Top Cover.
    7. Close Fan door.

  5. Return the Pilot to the FS1-2 system.
    1. Plug in both power cords.
    2. Return the Pilot to the rack position.
    3. Return the anti-tip legs to their normal position.
    4. When finished, re-enable Call-Home.


OBTAIN CUSTOMER ACCEPTANCE


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

Confirm that the replacement SAS HBA was successful - the System Alert associated with it should be gone and the FS1-2 should be normal/green.

Note: because the Pilot must cold start, it may take up to 10 minutes for the boot process to complete and the Pilot to return to a normal status.

REFERENCE INFORMATION:

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

References

<NOTE:1939732.1> - FS System: How to access Internal Field Service Guides

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback