![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2071839.1 : X4170 / False PSU Hangs In ILOM And ILOM Instability
-> ls /SYSTEM Temporary internal error (get_obj_child_count) Although the prompt is returned, however the iLOM is actually somehow corrupted, other commands does not work: -> show /SP hostname -> show /SP/network show: Invalid target /SP/network Recommend Work Around 1. Backup ilom configuration 2. Reset to factory 3. Recover lLOM configuration. 4. Upgrade ILOM In this Document
Created from <SR 3-11524875191> Applies to:Sun Fire X4170 M2 Server - Version All Versions and laterInformation in this document applies to any platform. SymptomsSun Fire X4170 M2 Faulting Power Supplies in ILOM and ILOM hanging and unstable - X4170 M2 iLOM does not work properly after upgraded to 3.1.2.20.e (buildr93424) or 3.1.2.20.f (build 99495).
> show /SP/faultmgmt/0/faults/ /SP/faultmgmt/0/faults ChangesCompatibility between ilom and oracle hardware management pack. Cause Root cause is still under investigation, however it is believed that Oracle Hardware Management Pack prior to 2.3.2.2 is causing the hardware fault and logging to ilom and attributing to the unresponsiveness. SolutionWorkarounds:Currently the workaround is to reset the ilom to factory defaults and install the newest Oracle Hardware Management Pack (OHMP) version for the OS and platform. Steps below discuss how to backup ilom/BIOS settings prior to resetting to factory defaults. When resetting to factory defaults, it is required to have a serial connection to the server to add the network configuration for the SP. Please review the Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection for WEBGUI and CLI instructions.
1. Reset the ilom to factory default as noted in the X4170m2 service manual: Reset Factory Defaults for SP and Oracle ILOM BIOS The provided steps are command line. This can also be done from the WEBGUI as documented above. Using backup/restore presumes the system works long enough to complete the firmware upgrade. Reports from several users were that ILOM was unusable sooner than that. Should that be the case skip to step 2. a. Backup Oracle ILOM configuration to a file dump -destination URI /SP/config b. Reset Oracle ILOM configuration to factory default set /SP reset_to_defaults=factory c.Reset the Oracle ILOM SP by performing one of the following: From the web interface, click Host Management > Power Control >from the pull down select > Reset. From the CLI, type: reset /SP Oracle ILOM resets BIOS configuration parameters to factory defaults and returns None as the Sync Status state. d. Reconfigure SP network configurations e. Restore Oracle ILOM configuration from a file >> If step 1 was performed. load -source URI/SP/config
2. Install the newest version of OHMP for the system available in MOS Patches and Updates. Search on "Hardware Management Pack" and choose the correct patch bundle for your operating system.
Current released version of this writing is OHMP 2.3.4 on MOS.
ReferencesBasic CLI Command Reference - http://docs.oracle.com/cd/E24707_01/pdf/E24520.pdfOracle Integrated Lights Out Manager (ILOM) 3.1 - http://docs.oracle.com/cd/E24707_01/pdf/E24522.pd <BUG:20428463> - ILOM BECOMES SLOW AND UNUSABLE Attachments This solution has no attachment |
||||||||||||||||||||||
|