Oracle FS1-2 Flash Storage System
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU replacement.
Created from <SR 3-11084706856>

Applies to:

Symptoms

 A defective X4-2 Pilot motherboard has been detected.  Using the ILOM command "show /System", you will see something like this:

Attempts to run ipmitool commands to verify the version of ILOM will result in authentication error:

Changes

 New components coming from spares are likely to have newer versions of the ILOM/BIOS.

Cause

 If the FS1-2 System is running R6.1.11 or lower, the rpms packages used to synchronize the ILOM/BIOS on a replacement Pilot motherboard will not work.

Solution

1. Replace the failed X4-2 Pilot Motherboard.  See <Document 1964065.1> FS System: How to Remove and Replace a Motherboard in an FS1-2 Pilot.
2. Apply power to that Pilot but do not allow it to boot all the way up.  Once the SP LED in front left side is solid, and the OK LED starts a fast blink (every second) press and hold the OK button for 7-10 seconds until the OK LED goes into slow blink (every 3-5 seconds).
3. On the surviving Pilot, create the directory /var/tmp/Pilot and copy the 7 files attached to this document into that directory.
4. On the surviving Pilot, flush the dhcp pool and then, wait for replies from the repaired Pilot's ILOM.
   
   [root@pilot2 ~]# echo "" > /var/lib/axiom/dnsmasq_svc.leases
   [root@pilot2 ~]# service dnsmasq_svc restart
   {root@pilot2 ~]# ping 169.254.2.9
    
5. On surviving Pilot, uninstall old hmp programs.
   
   [root@pilot2 ~]# rpm -e --nodeps oracle-hmp-libs-2.2.7-1.el6.x86_64
   [root@pilot2 ~]# rpm -e --nodeps oracle-hmp-tools-2.2.7-1.el6.x86_64
   [root@pilot2 ~]# rpm -e --nodeps oracle-hmp-tools-ubiosconfig-2.2.4-1.el6.x86_64
    
6. On surviving Pilot, install required rpms, make, openssl, and new hmp that are attached to this document.
   
   [root@pilot2 ~]# rpm -ivh make-3.81-20.el6.x86_64.rpm
   [root@pilot2 ~]# rpm -Uvh openssl-1.0.1e-30.el6_6.2.x86_64.rpm
   [root@pilot2 ~]# rpm -ivh oracle-hmp-libs-2.3.2.3-1.el6.x86_64.rpm
   [root@pilot2 ~]# rpm -ivh oracle-hmp-tools-2.3.2.3-1.el6.x86_64.rpm
   [root@pilot2 ~]# rpm -ivh oracle-hmp-tools-ubiosconfig-2.3.2.3-1.el6.x86_64.rpm
    
7. Confirm the hmp rpms package versions:
   
   [root@pilot2 ~]# rpm -qa |grep hmp
   oracle-hmp-libs-2.3.2.3-1.el6.x86_64
   oracle-hmp-tools-ubiosconfig-2.3.2.3-1.el6.x86_64
   oracle-hmp-tools-2.3.2.3-1.el6.x86_64
    
8. On the surviving Pilot, copy the pilot_x4-2_bios_25010603_fs1-2_defaults.xml and pilot_x4-2_ilom_3.1.2.30.b_r86439_fs1-2_defaults.xml configuration files attached to this document to /rpms/firmware.
9. Now, we should have new ubiosconfig, ilomconfig and fwupdate to work with new ILOM firmware 3.2.4-20. On surviving Pilot run the following commands in this order. When prompted for a password, enter changeme:
   
   [root@pilot2 ~]# ubiosconfig import all -H 169.254.2.9 -U root -yx /rpms/firmware/pilot_x4-2_bios_25010603_fs1-2_defaults.xml
   [root@pilot2 ~]# ilomconfig import config -H 169.254.2.9 -U root -y --xmlfile=/rpms/firmware/pilot_x4-2_ilom_3.1.2.30.b_r86439_fs1-2_defaults.xml
   [root@pilot2 ~]# fwupdate update sp-bios-firmware -n sp_bios -f /rpms/firmware/ILOM-3_1_2_30_b_r86439-Sun_Server_X4-2.pkg -o=/var/log/messages -q -H=169.254.2.9 -U=root
    
10. Power cycle the repaired Pilot.
11. Once the repaired Pilot has booted (OK LED is solid), from the surviving Pilot, confirm ILOM firmware version on both Pilots:
    
    
    NOTE: from the surviving Pilot, the IP addresses are:
    169.254.2.5=surviving Pilot
    169.254.2.9=repaired Pilot
    
    
    [root@pilot2 ~]# ipmitool sunoem cli "version"
    -> version
    
    SP firmware 3.1.2.30.b
    SP firmware build number: 86439
    SP firmware date: Mon Jan 20 17:03:25 CST 2014
    SP filesystem version: 0.1.23
    ->
    Session closed
    Disconnected
      
    
    [root@pilot2 ~]# ipmitool -H 169.254.2.9 -U root -P changeme sunoem cli "version"
    Connected. Use ^D to exit.
    -> version
    
    SP firmware 3.1.2.30.b
    SP firmware build number: 86439
    SP firmware date: Mon Jan 20 17:03:25 CST 2014
    SP filesystem version: 0.1.23
    ->
    Session closed
    Disconnected
     
12. Repeat steps 3-6 from the Pilot that was just repaired so that both Pilots are back in sync.
13. Remove the directory /var/tmp/Pilot and its contents from both Pilots.

References

This solution has no attachment