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-2251450.1
Update Date:2018-01-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  2251450.1 :   FS System: How to Re-flash a Controller ILOM from Pre-boot Menu  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Procedure must be executed by trained Oracle engineer

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions and later
Information in this document applies to any platform.

Goal

This document explains how to re-flash a Controller SPBIOS image from the Pre-boot Menu.  It applies only if the SP fails to boot with the following error message:

Enter PREBOOT due to boot failures

ILOM Pre-boot Menu

-----------------

Type "h" and [Enter] for a list of commands, or "?" [Enter] for

command-line key bindings. Type "h cmd" for summary of 'cmd' command.

Can not boot to ILOM, use 'net flash' to reflash ILOM.

Service mode enabled; check_physical_presence = 'no ;mfgmode'.

Preboot>
  • If this issue happens during a power cycle, the Controller will not auto boot.
  • If this issue occurs while the Controller is up and running, it will be still ON and functioning.

 

NOTE :

  • Never attempt to flash the ILOM with version that are not installed on the system. If you install a different version, on next clean power on or disruptive upgrade, the FS1 will automatically flash the ILOM with the correct version on the Pilot.
  • ILOM <Bug 26000038> AST2300 stops executing code at "Calibrating Loop Delay.." causes the controller to boot to Preboot. This issue is fixed in 6.2.15 firmware. The actual fix is in the BIOS 3.2.9.21 r117708 that comes with 6.2.15.
  • You cannot just flash the 3.2.9.21 r117708 if you are not on 6.2.15. You need to first upgrade to 6.2.15. You can use either a DU or an NDU, just set the upgrade to ignore hardware status and alerts.

 

Solution

Before attempting to re-image the SP/ILOM, confirm that the white locate button is not stuck or broken:

  • Verify if the locate button is pressed(white button in front and rear). If yes, depress the locate button and execute "reset warm" from Pre-boot.
  • If the locate button is not pressed, power cycle the controller by pulling the power cords.
  • See KM Document 1523297.1 SP (ILOM) enters "ILOM Pre-boot Menu" (Preboot>) after "reset /SP"; Boots fine from a cold start (unplug/plugin power cords).
NOTE: If the SP/ILOM enters Pre-boot while the host is up and running, the Controller should be online. Get customer approval prior power cycling the Controllers.

If both of the above actions didn't help to recover, then proceed with SP/ILOM re-flash.

  1. From the Pre-boot using "net config" configure the SP/ILOM network.
    Preboot> net config

    Note: 'managementport' selects the Ethernet port for ILOM access.
    Pre-boot "net" commands ignore 'managementport' and use the out-of-band port.

    Press Enter by itself to reach the next question.
    Press control-C to discard changes and quit.

    Values for 'ipdiscovery' are { dhcp | static }.
    Set ipdiscovery? [static <by default>]
    Values for 'managementport' are { SP/NET0 | MB/NET0 | MB/NET1 | MB/NET2 | MB/NET3 }.
    Set managementport? [<not set>] SP/NET0
    Set managementport? [SP/NET0]
    Set 'ipaddr' to a numeric IPv4 host.
    Set ipaddr? [<not set>] 169.254.2.9
    Set ipaddr? [169.254.2.9]
    Set 'gatewayip' to a numeric IPv4 host.
    Set gatewayip? [0.0.0.0] 169.254.2.9
    Set gatewayip? [169.254.2.9]
    Set 'netmask' to an IPv4 network mask.
    Set netmask? [255.255.255.0]
    Enter 'y[es]' to commit changes: [no] y
     
  2. Ping surviving Controller.
    Preboot> net ping 169.254.2.10
    Using faradaynic#0 device
    host 169.254.2.10 is alive
     
  3. If the ping to the surviving Controller is successful, re-flash SPBIOS image.
    Preboot> net flash 169.254.2.10 /var/tftp/spbios.rom
     
  4. After the command completes, execute "reset" to reboot the SP/ILOM.
    Done.
    Setting 'preserve_conf' to 'no' so ILOM resets to default configuration.
    Use "edit" to change that. Use "net config" to preserve or initialize
    SP network settings.
    Use "vers" to verify new image in flash.
    Then use "reset" (not "boot") to start the new ILOM image.
    .
    Preboot> reset
     
    • If the SP/ILOM boots normal with new BIOS image, follow below documents to re-mage the Controller BIOS files to make sure proper image files are loaded.
      • Document 2064481.1 FS System: How to Load Missing Controller BIOS Files After Motherboard Replacement
      • Document 1939732.1 FS System: How to Access the Internal Service Guide. Refer to section "Update the Controller BIOS".
    • If the boot fails and enters Preboot again, power cycle it by pulling power cords.
    • If it still fails to boot, engage hardware and platform team to investigate the issue.

 


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