Oracle FS1-2 Flash Storage System
 
Oracle FS1-2 Cloud System
 

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

In addition to the physical replacement of the Hard Disk Drive in the Pilot, the Pilot image will also need to be copied from the surviving Pilot.

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Part being replaced is a FRU and image copy is complex.

Applies to:

Goal

The purpose of this document is to outline the steps required to replace a Hard Disk Drive in an FS1-2 Pilot using Guided Maintenance 

Solution

DISPATCH INSTRUCTIONS

  WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?:

Product knowledge, FS1-2 Flash Storage System

  TIME ESTIMATE: 90 minutes

  TASK COMPLEXITY: 2

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

  PROBLEM OVERVIEW:

    WHAT: A Hard Disk Drive (HDD) in an FS1-2 Pilot needs to be replaced

    WHERE: The FS1-2 problem Pilot will be listed in the System Alerts.

    WHY: The HDD has failed or is in danger of failing.

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

The Pilot with the problem HDD will need to be powered off during the physical replacement.  The surviving Pilot must be functioning normally so that the pilot image can be copied from it to the new HDD.

QRC for this procedure:
 

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

1. Prepare 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 failed or failing HDD and select Repair Pilot option.
   4. In the pop-up Modify window, select the SAS HDD from the pull-down menu and then click on Next.
   5. Click Next again to turn on the White Locate LED for the problem Pilot.
   6. Instructions for HDD replacement can be downloaded from the next screen but it is recommended that the FE use this CAP as it also contains a timeline.
   7. Clicking Next will offline the problem Pilot.  If it was still the active Pilot, a failover to it's partner will now happen and you will lose connection to the GUI.
   8. Wait for the green OK LED of the problem Pilot to to slow-blink (every 3 seconds).
      
      
4. Extend the anti-tip legs in front of the rack.
5. Slide the Pilot into the service position.
6. Unplug both power cables.
   
   NOTE: If the Pilot is an X5-2 version, remove the top cover and 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.
    
2. Replace Pilot HDD.
1. Use the square button on the front of the Pilot HDD to eject it.
2. Remove the Pilot HDD.
3. Install the replacement HDD.
   
   
3. Re-image the replacement Pilot HDD.
   
   NOTE: for Systems running R6.2.5 or higher, please use the Pilot Rescue Image to re-image the replaced Pilot HDD if possible.  See Document 2148252.1 FS System: How to Use the Pilot Rescue Image.
    
1. Unplug the ethernet cable from Net-2 (see cover panel for location).
2. Unplug the ethernet cable from Net Mgr and plug it into the Net-2 location.
3. Enable SSH on the FS1-2 for 60 minutes (see Document 2029847.1 FS System: How to Enable ssh on the Pilot. 
4. ssh into the working pilot (see Document 2046703.1 FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System) and flush the current network tables on the active Pilot:
   
   For FS1-2 systems running R6.1.x:
   # echo "" > /var/lib/dnsmasq_svc.leases
   #service dnsmasq_svc restart
     
   
   For FS1-2 systems running R6.2.x:
   # echo "" > /var/lib/axiom/dnsmasq_pmi.leases
   # service dnsmasq_pmi restart
     
   The first command will not produce any output, but the second will display two lines with green [OK]s on the right side of the screen.
   
   
5. Reattach both power cords and observe the LEDs on the front left side of the Pilot (all times are approximate from power on):
   
   
• The SP LED on the Pilot should fast-blink (every second).
• After about two minutes, it will turn solid and the OK LED will slow-blink.
• After about two and a half minutes the OK LED will fast-blink.
• After about four and a half minutes the OK LED will go solid.
• At about twenty-two minutes, the image copy will complete and the OK LED will again slow-blink indicating it is rebooting with the new image.
• At about twenty-two and a half minutes, the OK LED will fast-blink.
• At about twenty-four and a half minutes the OK LED will go solid.
• At about twenty-seven and a half minutes, the Pilot should finish it's reboot.
  
  
6. After about twenty-five minutes, use a command tool or other terminal to ping the IP address assigned to the problem Pilot.
7. When ping responds, remove the ethernet cable from the problem Pilot's Net-2 and plug it into Net Mgt.
   
   NOTE: if ping does not respond after 30 minutes, connect up a monitor and keyboard.  If you see an "Unsupported Hardware Detected" error message, select OK and process should resume.  See <Bug 21564611> for additional details.
    
4. Restore the original Pilot inter-connections.
1. Disconnect the cable in Net-2 and return it to it's original location, Net Mgr.
2. Reconnect the cable originally in Net-2.
   
   
5. Return the Pilot to the FS1-2 system.
1. Return the Pilot to it's racked position.
2. Re-flush the Network Tables again
   
   For FS1-2 systems running R6.1.x:
   
   #echo "" > /var/lib/dnsmasq_svc.leases
   #service dnsmasq_svc restart
    
   For FS1-2 systems running R6.2.x:
   # echo "" > /var/lib/axiom/dnsmasq_pmi.leases
   # service dnsmasq_pmi restart
     
3. Check the GUI to confirm that both Pilots are normal and functioning.  If not, check the following issues and recommended remedies:
   
   
• Network connections in the Pilot may be in an inconsistent state.  This can be cleared by rebooting the Pilot again.
• Pilots will be normal but Hardware Status Icon in the lower left corner of the GUI may still be yellow.  This can be cleared by a logout/login of the GUI.
  
  
4. Confirm that the following files and directories contain the same information on both Pilots:
   
   /var/lib/pillar/pcp/Compatibility.xml
   /rpms/AxiomONE-SW-installed/*
   /rpms/AxiomONE-SW-previous/*
   /rpms/AxiomONE-SW-staged/*
   /rpms/firmware/*
   /rpms/pillar-pilot-os/*
   
   If any or all of these files are missing, use scp to copy them from the good Pilot image. 
   
   NOTE: If this system has never gone through a software upgrade or had one staged, the contents of  AxiomONE-SW-previous and AxiomONE-SW-staged may be empty.
   
    
   Example of copying the files from Pilot 1 to Pilot 2:
   
   [root@pilot1 /]# scp /var/lib/pillar/pcp/Compatibility.xml pilot2:/var/lib/pillar/pcp/Compatibility.xml
   [root@pilot1 /]# scp -r /rpms/AxiomONE-SW-installed pilot2:/rpms/AxiomONE-SW-installed
     
   
   
   NOTE: Do not copy over the /rpms directory as it is also a filesystem and doing so will also copy over the lost+found directory.
     
   
   
5. Check the timezone setting to confirm it is set to UTC:
   [root@pilot1 ~]# ls -l /etc/localtime
   lrwxrwxrwx 1 root root 23 Nov 9 22:08 /etc/localtime -> /usr/share/zoneinfo/UTC
   [root@pilot1 ~]#
     
   If the timezone is NOT set to UTC, contact Oracle support for additional help resolving <Bug 22241151>.
   
   
6. If any other issue are observed, please contact the owner of the Service Request for additional help.
7. 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 replacement Pilot HDD is seen by the FS1-2 Flash Storage System and the system has reverted to a normal/green state.

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

This solution has no attachment