Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Goal

Solution

Prepare the Controller with the Replaced Motherboard

Stage the Files on the Surviving Controller

Update the Replacement Controller Motherboard

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU replacement.

Applies to:

Goal

This document supplements the steps required to synchronize the ILOM BIOS and configuration of a replacement Controller motherboard with it's survivor in versions R6.1.18 and R6.1.19.  Refer to KM <Document 1986007.1> FS System: How to Remove and Replace a Motherboard in an FS1-2 Controller for more details.  It assumes that the Controller motherboard has been successfully replaced.  Do not attempt these steps until that point.

Solution

The solution for this issue requires the following:

• ssh must be enabled on the active Pilot.
• Software transfer program like WinSCP to copy the necessary files from a terminal/laptop to the active Pilot.
• The spbios.tar file attached to this document.

The basic steps to complete this procedure are:

• Prepare the Controller with the replaced motherboard
• Stage the BIOS and configuration files to the surviving Controller
• Update the replacement Controller motherboard.

Prepare the Controller with the Replaced Motherboard

Since the replacement Controller motherboard is a part used in other systems, BIOS file and configuration files need to be updated in order for it to properly function as an FS1-2 Controller.  To accomplish this, the Controller must be in standby mode where the ILOM is up, but the HOST/Controller is not.

1. If not already done, plug the power cords into the Controller power supplies. 
2. Observe the LEDs on the left front side of the Controller. 
3. Just below the power button is the green SP LED.  This LED will fast blink (every second) for about 2 minutes as the ILOM boots. 
4. When the SP LED goes solid, observe the green OK LED. 
   1. If it begins to fast blink, it means that the Controller is also booting and must be stopped. 
   2. Pressing and holding the power button for 7-10 seconds or until the OK LED goes into a slow blink (every 3-5 seconds). 
5. With a slow blinking OK LED, the Controller is now in standby mode.
6. Enable ssh to the active Pilot - reference KM <Document 2029847.1> FS System: How to Enable SSH Access to the Pilot and ssh to it.
7. ssh to the surviving Controller (Controller 1 in this case) and then ping the ILOM IP address of the Controller with the replacement motherboard:
   
   [root@pilot2 ~]# ssh 172.30.80.128
   WN508002000XXXXXX0 # ping 169.254.2.9
   PING 169.254.2.9 (169.254.2.9): 56 data bytes
   64 bytes from 169.254.2.9: seq=0 ttl=64 time=0.621 ms
   64 bytes from 169.254.2.9: seq=1 ttl=64 time=0.466 ms 
   WN508002000XXXXXX0 # exit
   [root@pilot2 ~]#

Stage the Files on the Surviving Controller

1. Using WinSCP (or similar program), copy the tarball into /var/tmp on the active Pilot.
2. Untar the contents of spbios.tar to create a directory called spbios and reveal 3 files inside:
   
   [root@pilot2 ~]# cd /var/tmp
   [root@pilot2 tmp]# tar xvf spbios.tar
   spbios/
   spbios/fs_bios_settings.xml
   spbios/spbios.rom
   spbios/ControllerSpBiosVersionMapping
   [root@pilot2 tmp]#
    
   
   
3. Copy the 3 files to the surviving Controller:
   
   [root@pilot2 tmp]# cd spbios
   [root@pilot2 spbios]# scp ControllerSpBiosVersionMapping 172.30.80.128:/var/tftp
   ControllerSpBiosVersionMapping                                                       100% 128   0.1KB/s 00:00
   [root@pilot2 spbios]# scp spbios.rom 172.30.80.128:/var/tftp/
   spbios.rom                                                                           100% 17MB 16.9MB/s 00:00
   [root@pilot2 spbios]# scp fs_bios_settings.xml 172.30.80.128:/var/tftp/
   fs_bios_settings.xml                                                                 100% 40KB 39.9KB/s 00:00
   [root@pilot2 spbios]#
     
   

Update the Replacement Controller Motherboard

1. ssh to the surviving Controller and load the spbios.rom file:
   
   [root@pilot2 spbios]# ssh 172.30.80.128
   WN508002000XXXXXX0 # fwupdate update sp-bios-firmware -n sp_bios -f /var/tftp/spbios.rom -q -H=169.254.2.9 -U=root
   Enter password (8 to 16 characters):
   ********
   WN508002000XXXXXX0 #
    
   
   NOTE: ILOM password used by the FS1 is changeme.
     
   
   
2. Confirm that HOST_AUTO_POWER_ON is enabled on the replaced Controller motherboard:
   
   WN508002000XXXXXX0 # ipmitool -H 169.254.2.9 -U root -P changeme sunoem cli "show /SP/policy HOST_AUTO_POWER_ON"
   Connected. Use ^D to exit.
   -> show /SP/policy HOST_AUTO_POWER_ON
   
       /SP/policy
          Properties:
                 HOST_AUTO_POWER_ON = enabled
   
   
   
   -> Session closed
   Disconnected
   WN508002000XXXXXX0 #
    
   
   NOTE: If HOST_AUTO_POWER_ON is not enabled, there is likely something wrong with the spbios.rom file.  Please contact Oracle Support for help.
    
   
3. Import the BIOS configuration file:
   
   WN508002000XXXXXX0 # ubiosconfig import all -H 169.254.2.9 -U root -yx /var/tftp/fs_bios_settings.xml
   Enter password :
   ********
   Preparing to restore XML file to BIOS...
   Done preparing to restore settings in /var/tftp/fs_bios_settings.xml to BIOS.
   Restoring BIOS configuration (allow several minutes).................................................
   .....................................................................................................
   .....................Done.
   Import successful.
   WN508002000XXXXXX0 #
   
   
   
4. Bring the replaced Controller motherboard online:
   
   WN508002000XXXXXX0 # ipmitool -H 169.254.2.9 -U root -P changeme chassis power on
   Chassis Power is Up/On
   WN508002000XXXXXX0 #
   
   
   
   

References

This solution has no attachment