4 Oracle ILOM Issues
This section describes important operating notes and known Oracle ILOM issues for Oracle Server X7-8.
For updated information about Oracle ILOM, refer to Oracle Integrated Lights Out Manager (ILOM) documentation at Servers Documentation - Systems Management.
- DIMM Fault SPX86A-800A-95 - Memtest Single Symbol Test Failed - ILOM 5.1.0.21
- System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade
- Oracle ILOM Reports a Fault After Software Upgrade to 4.0.4.20 with Intermittent Occurrence
- Power On Failure After Oracle ILOM Software Upgrade to 4.0.4.20
- Oracle ILOM Reports a BIOS Upgrade Failure Error Fault after Downgrading Software to Software 1.1.2 with BIOS Delay
- Oracle ILOM Reports Fault alert.chassis.fw.bios-upgrade-failure After Firmware Upgrade or Downgrade
- Oracle ILOM Software Downgrade From SW1.1.0 to SW1.0.1 Host Stays In Reboot Loop
- Software 4.0.3.21 X7-8 Exadata Firmware Upgrade from SW1.0 to SW1.2 UEFIcfg Stays in Boot Loop
- POST Halts on port80=0xEF after Software Upgrade or Downgrade (Preserve+Delay_BIOS)
- Oracle ILOM Software Downgrade from 1.3.0 to 1.1.4 Using ipmiflash and Power Cycle Fails Turn On
- Changes to TLSv1.1 Configuration Property as of ILOM 4.0.3.x
- System Might Not Set BIOS to Defaults After Power Cycle
- SSL Must Be Turned On When Booting a Redirected ISO Image
- Reset Takes a Long Time and Causes the Server to Power Cycle
- Deprecation Notice for Oracle ILOM IPMI 2.0 Management Service
- Oracle VTS Network Test Floods Serial Console Triggering Soft Lockups
DIMM Fault SPX86A-800A-95 - Memtest Single Symbol Test Failed - ILOM 5.1.0.21
Bug ID: 34325538, 34445460
Issue: The following DIMM Fault message is seen: SPX86A-800A-95 - Memtest Single Symbol Test Failed (Doc ID 2317012.1)
SPX86A-800A-95 indicates that the ILOM fault manager has received an error report
indicating a memory DIMM produced correctable errors (CE) during both passes of the memory
test.
If the server encounters multiple runtime memory fault related events, increased runtime error messages may be related to DIMM memory testing conditions. Oracle ILOM Adaptive Double DRAM Device Correction (ADDDC) and Post Package Repair (PPR) features are enabled in the server firmware. ADDDC Sparing is a RAS feature to test memory reliability. The Advanced Memory Test (AMT) in the Memory Reference Code (MRC) can fail a DIMM with a single symbol error and then PPR would try to repair the defect.
When enabled, PPR may be able to repair affected DRAM areas on a DIMM. PPR runs when ADDDC was previously activated before reboot or MRC initialization failed memory tests. Upon encountering any memory related fault event during MRC initialization or experiencing certain memory correctable events during runtime that triggers ADDDC on first occurrence, then PPR would be activated after the next system initialization/reboot and attempt to repair the DIMM.
Note:
Certain DIMM manufacturers may exhibit different memory failure patterns, and may not support soft PPR configuration (which enables temporarily attempting a repair action).
Affected Hardware: Oracle Server X9-2, Oracle Server X9-2L, Oracle Server X8-8, Oracle Server X8-2, Oracle Server X8-2L, Oracle Server X7-8, Oracle Server X7-2, Oracle Server X7-2L
Note:
Not all server systems enable ADDDC.
Affected Software:
The following x86 server software Oracle ILOM releases or later, support PPR (Post-Package Repair).
- Oracle Server X9-2 SW1.1.0 ILOM 5.0.2.21 (Does not enable ADDDC.)
- Oracle Server X9-2L SW1.1.0 ILOM 5.0.2.21 (Does not enable ADDDC.)
- Oracle Server X8-8 SW3.2.2.1 ILOM 5.0.2.22 (Does not enable ADDDC.)
- Oracle Server X8-2 SW3.2.2 ILOM 5.0.2.24
- Oracle Server X8-2L SW3.2.2 ILOM 5.0.2.24
- Oracle Server X7-8 SW3.2.2.1 ILOM 5.0.2.22 (Does not enable ADDDC.)
- Oracle Server X7-2 SW3.2.2 ILOM 5.0.2.24
- Oracle Server X7-2L SW3.2.2 ILOM 5.0.2.24
Workaround: Some DIMM faults are recoverable errors if PPR is enabled on the server. If multiple DIMM memory errors are detected on the server:
- Log in to the Oracle ILOM command-line interface (CLI) using an account with admin (a) role privileges.
- From the Oracle ILOM CLI, launch the Oracle ILOM Fault Management Shell.
-> start /SP/faultmgmt/shell Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
- Display information about server components using Oracle ILOM FMA CLI
command.
faultmgmtsp>
fmadm faulty - Manually clear server faults using Oracle ILOM FMA CLI
command.
faultmgmtsp>
fmadm repair <FRU> - Exit the Oracle ILOM Fault Management Shell and return to the the Oracle
ILOM CLI command prompt.
faultmgmtsp>
exit - Upgrade the server to the latest ILOM/UEFI firmware release that supports PPR. The system resets during the firmware upgrade and runs memory tests again.
- If memory related events faults continue to be logged, replace the faulted DIMMs in the server. Log an Oracle Support case through the support portal for further assistance.
For updated information about Oracle ILOM, refer to Oracle Integrated Lights Out Manager (ILOM) documentation at Servers Documentation - Systems Management.
Oracle Service personnel can find more information about the diagnosis and triage of DIMM Fault failures on x86 servers at My Oracle Support. Refer to the Knowledge Article Doc ID 2698328.1. If there are multiple, simultaneous DIMM Fault message problems on a server, Oracle Service personnel can refer to Knowledge Articles Doc IDs 1603015.1 (KA single symbol error) and 2317012.1 (KA multiple symbol errors).
Note:
Adaptive Double DRAM Device Correction (ADDDC) is also referred to as Adaptive Device Correction (ADC) in some Oracle documents.Parent topic: Oracle ILOM Issues
System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade
Important Operating Note
Bug IDs: 28707152, 28632145, 28597111, 27154649, 28188424, 27209590, 28447223
| Bug ID | Issue |
|---|---|
|
28707152 |
/SYS/PS1 fault.chassis.device.sppost intermittent occurrence |
|
28632145 |
POWER-ON-FAILURE AFTER ILOM UPGRADE TO 4.0.4.20 R127037 |
|
28597111 |
Downgrading to SW 1.1.2 (ILOM: 123532 BIOS: 46.02.07.00) with BIOS Delay causes BIOS update failure error. |
|
27154649 |
Oracle Server X7-8 ILOM FW downgrade from SW1.1 to SW1.0.1 host stuck in reboot loop |
|
28188424 |
SW 4.0.3.21 x7-8 exadata firmware upgrade from SW1.0 to SW1.2 ueficfg boot loop |
|
27209590 |
POST halts on port80=0xEF after up/downgrade (Preserve+Delay_BIOS) |
|
28447223 |
Oracle ILOM: X7-8 downgrade 1.3 -> sw 1.1.4 via ipmiflash & power cycle fails turn on |
Issue: On rare occasions, after Oracle Server X7-8 Oracle ILOM software upgrade or downgrade, Oracle Server X7-8 might not power on or the Service Processor POST process stops. You can identify the issue if powering on the server system using a chassis power button fails, or Oracle ILOM power-on user interfaces fail, or the HOST_AUTO_POWER_ON policy fails.
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Software: The following table contains the Oracle Server X7-8 affected software.
| Release | Firmware Upgrade Issues | Firmware Downgrade Issues |
|---|---|---|
|
SW1.0.0 (Oracle ILOM 4.0.0.23) |
Upgrade from 1.0 to any software release. Power cycle power-on stops after Software Release update. Workaround: Clear CMOS from Diag Shell and AC power cycle. |
Software release 1.2.0 downgrade to Software Release 1.0.0 or Software Release 1.0.1 sends hosts into infinite reboot loop. Workaround: Power off host and clear CMOS from Diag Shell. |
|
SW1.0.1 (Oracle ILOM 4.0.0.31) |
Cannot skip 2 ME Changes. For example: Software Release 1.0.1 to Software Release 1.2.0. |
Software release 1.2.0 downgrade to Software Release 1.0.0 or Software Release 1.0.1 sends hosts into infinite reboot loop. Workaround: Power off host and clear CMOS from Diag Shell. |
|
SW1.1.0 (Oracle ILOM 4.0.2.20) |
No issues |
No issues |
|
SW1.1.1 (Oracle ILOM 4.0.2.20.a) |
No issues |
Downgrade from Software Release 1.1.0 or higher to Software Release 1.0.1 or Software Release 1.1.0. Workaround: Power off host and clear CMOS from Diag Shell. |
|
SW1.1.3 (Oracle ILOM 4.0.2.29) |
No issues |
No issues |
|
SW1.1.4 (Oracle ILOM 4.0.2.29.a) |
No issues |
Fixed issue 28447223 X7-8 downgrade Software Release 1.3 to Software Release 1.1.4 via ipmiflash & power cycle fails to turn on Workaround: Manual power on. |
|
SW1.2.0 (Oracle ILOM 4.0.3.21) |
No issues |
Do not downgrade to Software Release 1.2.0 from Software Release 1.3.0, Software Release 1.3.2 to maintain security fixes. Software Release 1.2.0 downgrade to Software Release 1.0.1 or Software Release 1.0.0 sends the host into infinite reboot loop. Workaround: Power off host and clear CMOS from Diag Shell. |
|
SW1.3.0 (Oracle ILOM 4.0.4.20) |
No issues |
Do not downgrade to Software Release 1.2.0 from Software Release 1.3.0, Software Release 1.3.2 to maintain security fixes. Fixed issue 28447223 X7-8 downgrade 1.3 -> sw 1.1.4 via ipmiflash & power cycle fails turn on Workaround: Power off host and clear CMOS from Diag Shell. |
|
SW1.3.2 (Oracle ILOM 4.0.4.28.00) |
FPGA Issue fix for Software Release 1.0.0 up to Software Release 1.3.2. Clear CMOS, reset, AC power cycle. |
Downgrading from Oracle Server X7-8 firmware version 1.3.2 (with FPGA fix) to any Software Release from 1.3.0 to 1.0.0 can expose the FPGA issue. Do not downgrade to Software Release 1.2.0 from Software Release 1.3.0, or Software Release 1.3.2 to maintain security fixes. |
Affected Hardware: Oracle Server X7-8
Workaround: There are multiple ways to avoid or workaround power cycle issues. Choose from the following methods.
-
To avoid power cycle issues when upgrading or downgrading firmware, do not preserve the BIOS configuration.
-
You must update your server firmware and software as soon as possible after a new Software Release becomes available. Software releases often include bug fixes, and updating your server ensures that your server has the latest firmware and software. These updates will increase your system performance, security, and stability.
-
In general, to minimize the chances of encountering power cycle issues, use the latest software update.
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing. -
Upgrade software updates in stepwise increments, between major versions. For example: From Software Release 1.0 to Software Release 1.1, From Software Release 1.1 to Software Release 1.2, From Software Release 1.2 to Software Release 1.3.
-
On rare occasions, after Oracle Server X7-8 does not power on, first check, then view and clear faults using Oracle ILOM FMA (Fault Management Architecture) interfaces. For information about Oracle ILOM FMA, refer to Oracle Integrated Lights Out Manager (ILOM) 4.0 Information Library at https://www.oracle.com/goto/ilom/docs .
-
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Recovery: If a system encounters this issue during a firmware upgrade or downgrade, do the following to recover:
From Oracle ILOM CLI:
-
Power off the host.
->stop -script -force /System -
Wait 30 seconds.
-
Power on the host.
->start -script /System
From Oracle ILOM web interface Summary screen:
-
Power off the host.
-
Wait 30 seconds.
-
Power on the host.
-
The Administrator can safely clear the fault after recovery.
For details, refer to "Managing Server Hardware Faults Using the Oracle ILOM Fault Management Shell" in the Oracle Server X7-8 Service Manual.
If a system encounters this issue during a firmware upgrade or downgrade, and still does not power on after resolving and clearing hardware faults, or does not complete the Service Processor POST process, perform the following steps to power off the host and clear CMOS from the Diag Shell.
-
Power off the host.
Refer to the Oracle Server X7-8 Installation Guide.
-
Clear system CMOS.
-
If powered on, force host power off:
->stop -script -force /System -
Start the Diag Shell:
->start -script /SP/diag/shell -
From the Diag Shell, clear the system CMOS:
diag->hwdiag system clear_cmos -
Exit the Diag Shell:
diag>exit -
Start the host:
->start -script /System
-
-
In the rare case that the Oracle Server X7-8 still fails to power on, perform an AC power cycle, by removing and reinstalling the server AC power cables.
Refer to the Oracle Server X7-8 Service Manual.
-
If the AC power cycle attempt fails, contact an Oracle Service representative for assistance.
Parent topic: Oracle ILOM Issues
Oracle ILOM Reports a Fault After Software Upgrade to 4.0.4.20 with Intermittent Occurrence
Bug ID: 28707152
Issue: After Oracle Server X7-8 is upgraded with Oracle
ILOM Software Release 4.0.2.20 or lower, Oracle ILOM reports the following fault:
fault.chassis.device.sppost. This issue is fixed in Software
Release 1.3.2 that includes the 3B.2F FPGA image. On rare occasion, the fault asserts
during the FPGA firmware upgrade before Oracle ILOM has upgraded to the 3B.2F FPGA image
that includes the fix. The server might not complete the Service Processor power-on
self-test (POST) process.
Note:
Update your system to the latest Software Release before you use the system.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle ILOM Software Releases from 4.0.0.23 to 4.0.2.20.
Workaround: Clear the faults after the Oracle ILOM firmware upgrade completes and the faults should not reappear. This issue has no functional impact on normal system behavior and can be ignored.
For details, refer to "Managing Server Hardware Faults Using the Oracle ILOM Fault Management Shell" in the Oracle Server X7-8 Service Manual.
See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
Parent topic: Oracle ILOM Issues
Power On Failure After Oracle ILOM Software Upgrade to 4.0.4.20
Bug ID: 28632145
Issue: On rare occasion, after Oracle Server X7-8 upgrading to Software Release 1.3.0 with Oracle ILOM 4.0.4.20, the server might not Power On automatically and the Service Processor power-on self-test (POST) process might not complete.
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle Server X7-8 Software Release 1.3.0
Workaround: See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Oracle ILOM Reports a BIOS Upgrade Failure Error Fault after Downgrading Software to Software 1.1.2 with BIOS Delay
Bug ID: 28597111
Issue: When downgrading Oracle Server X7-8 firmware and software to Software Release 1.1.2 (ILOM: 123532 BIOS: 46.02.07.00) with BIOS Delay, a BIOS update failure error displays.
When this fault occurs, Oracle ILOM reports the following failure:
alert.chassis.fw.bios-upgrade-failure
Oracle Server X7-8 might not Power On automatically and the Service Processor power-on self-test (POST) process might not complete after downgrading from Oracle ILOM Software Release 1.3.0 or later to Software Release 1.1.2 using IPMIflash (with preserve BIOS configuration).
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle Server X7-8 Software Release 1.1.2
Workaround: See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Oracle ILOM Reports Fault alert.chassis.fw.bios-upgrade-failure
After Firmware Upgrade or Downgrade
Bug ID: 27209590 Fixed in Oracle ILOM 4.0.2.25.b.
Issue: When upgrading Oracle Server X7-8 software from Software Release 1.0.0 (Oracle ILOM 4.0.0.23) or Software Release 1.0.1 (Oracle ILOM 4.0.0.31) to Software Release 1.1.0 (Oracle ILOM 4.0.2.20) or Software Release 1.1.1 (Oracle ILOM 4.0.2.20.a), or downgrading, the host may not be able to power on the first time if the following options are used:
-
Preserve BIOS configuration
-
Delay BIOS upgrade until next server power off
When this fault occurs, Oracle ILOM reports the following failure:
alert.chassis.fw.bios-upgrade-failure
Affected Software: Oracle Server X7-8 Software Release 1.0.0 (Oracle ILOM 4.0.0.23), Software Release 1.0.1 (Oracle ILOM 4.0.0.31), Software Release 1.1.0 (Oracle ILOM 4.0.2.20), Software Release 1.1.1 (Oracle ILOM 4.0.2.20.a)
Workaround: There are multiple ways to avoid or workaround this issue. Choose one of the following methods.
To avoid this issue when trying to update to Software Release 1.1.0, do not preserve the BIOS configuration and do not use delay BIOS upgrade options.
Method to upgrade to Software Release 1.1.0 and avoid this issue:
-
Create a backup BIOS XML file before updating to Software Release 1.1.0 (Oracle ILOM 4.0.2.20) or Software Release 1.1.1 (Oracle ILOM 4.0.2.20.a).
-
Update to Software Release 1.1.0 (Oracle ILOM 4.0.2.20) or Software Release 1.1.1 (Oracle ILOM 4.0.2.20.a) without using preserve BIOS configuration and delay BIOS options.
-
Boot the host so boot devices are discovered by BIOS.
-
Power off the host.
->stop -script -force /System -
Load the BIOS XML file created in step 1.
Recovery: If a system encounters this issue during a firmware upgrade, do the following to recover:
From Oracle ILOM CLI:
-
Power off the host.
->stop -script -force /System -
Wait 30 seconds.
-
Power on the host.
->start -script /System
From Oracle ILOM web interface Summary screen:
-
Power off the host.
-
Wait 30 seconds.
-
Power on the host.
-
The Administrator can safely clear the fault after recovery.
For details, refer to "Managing Server Hardware Faults Using the Oracle ILOM Fault Management Shell" in the Oracle Server X7-8 Service Manual.
See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Oracle ILOM Software Downgrade From SW1.1.0 to SW1.0.1 Host Stays In Reboot Loop
Bug ID: 27154649 Fixed in Oracle ILOM 4.0.2.20.
Issue: On rare occasion, when downgrading an Oracle Server X7-8 system from Software Release 1.1.0 (Oracle ILOM 4.0.2.20) back to Software Release 1.0.0 (Oracle ILOM 4.0.0.23) or Software Release 1.0.1 (Oracle ILOM 4.0.0.31), the server can continually reset and the host may fail to boot completely the first time.
Affected Software: Oracle Server X7-8 Software Release 1.0.0 (Oracle ILOM 4.0.0.23), Software Release 1.0.1 (Oracle ILOM 4.0.0.31), Software Release 1.1.0 (Oracle ILOM 4.0.2.20), Software Release 1.1.1 (Oracle ILOM 4.0.2.20.a)
Workaround: When this condition occurs, power off the host, clear CMOS and power on the host again.
When the host cannot boot completely the first time, after a firmware downgrade back to Software Release 1.0.0 (Oracle ILOM 4.0.0.23) or Software Release 1.0.1 (Oracle ILOM 4.0.0.31), issue the following commands from Oracle ILOM CLI to recover.
-
Force host power off:
->stop -script -force /System -
Start the Diag Shell:
->start -script /SP/diag/shell -
From the Diag Shell, clear the system CMOS:
diag->hwdiag system clear_cmos -
Exit the Diag Shell:
diag>exit -
Start the host:
->start -script /System
See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Software 4.0.3.21 X7-8 Exadata Firmware Upgrade from SW1.0 to SW1.2 UEFIcfg Stays in Boot Loop
Bug ID: 28188424 Fixed in Oracle ILOM 4.0.3.21.
Issue: Oracle Server X7-8 can continually reset after Software Release 4.0.3.21 x7-8 Exadata server firmware and software upgrade from Software Release 1.0 to Software Release 1.2 UEFI configuration (ueficfg) and remain in a boot loop.
The server might not Power On automatically and the Service Processor power-on self-test (POST) process might not complete after downgrading Oracle ILOM Software Release 1.0.0 to Software Release 1.2.0 using IPMIflash (with preserve BIOS configuration).
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle Server X7-8 Software Release 1.0.0, Software Release 1.2.0
Workaround: See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
POST Halts on port80=0xEF after Software Upgrade or Downgrade (Preserve+Delay_BIOS)
Bug ID: 27209590 Fixed in Oracle ILOM 4.0.2.25.b.
Issue: Oracle Server X7-8 Service Processor power-on self-test (POST) stops on port80=0xEF after upgrading or downgrading system software.
Oracle Server X7-8 Service Processor power-on self-test (POST) process might not complete after upgrading or downgrading system Software Release 1.3.0 to Software Release 1.1.4 using IPMIflash (Preserve+Delay_BIOS with preserve BIOS configuration).
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle Server X7-8 Software Release 1.3.0, Software Release 1.1.4
Workaround: See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When upgrading or downgrading firmware, do not preserve the BIOS configuration.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Oracle ILOM Software Downgrade from 1.3.0 to 1.1.4 Using ipmiflash and Power Cycle Fails Turn On
Bug ID: 28447223 Fixed in Oracle ILOM 4.0.2.20.
Issue: On rare occasion, Oracle Server X7-8 might not Power On automatically and the Service Processor power-on self-test (POST) process might not complete after downgrading Oracle ILOM Software Release 1.3.0 to Software Release 1.1.4 using IPMIflash (with preserve BIOS configuration).
Note:
Update your system to the latest Software Release before you use the system. Downgrade software only when required for testing.Affected Hardware: Oracle Server X7-8
Affected Software: Oracle Server X7-8 Software Release 1.3.0, Software Release 1.1.4
Workaround: See System Might Not Power On with POST After Oracle ILOM Software Upgrade or Downgrade.
When a power-off condition occurs, press the System A or System B server power button on the host system, or use Oracle ILOM CLI commands to power on the Oracle Server X7-8 host system from a local or remote location. Refer to Power On the Server in Oracle Server X7-8 Service Manual.
Parent topic: Oracle ILOM Issues
Changes to TLSv1.1 Configuration Property as of ILOM 4.0.3.x
Important Operating Note
Present Behavior: The Oracle ILOM TLSv1.1 configuration property is Enabled by default.
Future Behavior: The following changes will occur to the TLSv1.1 configuration property sometime after the Oracle ILOM 4.0.3 firmware release:
-
First Change: The TLSv1.1 configuration property will default to Disabled in the next minor release of Oracle ILOM.
-
Second Change: The TLSv1.1 configuration property will no longer be supported and will be removed from all Oracle ILOM user interfaces in the next major release of Oracle ILOM.
For future updates regarding TLSv1.1 support in Oracle ILOM, refer to latest release information in the Oracle ILOM Feature Updates and Release Notes for Firmware 4.0.x at https://docs.oracle.com/cd/E81115_01/index.html .
Parent topic: Oracle ILOM Issues
System Might Not Set BIOS to Defaults After Power Cycle
Bug ID: 26785322
Issue: On rare occasions, typically after an AC power cycle, Oracle Server X7-8 might not set BIOS to defaults. You can identify this issue when the reset_to_defaults property does not change from factory to none after 15 minutes.
To verify the BIOS settings, enter the following command:
-> show -d properties
/System/BIOS reset_to_defaults /System/BIOS Properties: reset_to_defaults = factory
Affected Hardware: Oracle Server X7-8
Workaround: If you encounter this issue, log in to Oracle ILOM and reset the service processor (SP) with the following command:
-> reset /SP
After you reset the SP, re-enter the command to verify the BIOS default settings.
Parent topic: Oracle ILOM Issues
SSL Must Be Turned On When Booting a Redirected ISO Image
Important Operating Note
When booting a redirected ISO image for an operating system installation, turn on SSL (Secure Sockets Layer), which is the default setting. If you do not turn on SSL, the installation might stall or fail. This issue affects all supported operating systems.
Parent topic: Oracle ILOM Issues
Reset Takes a Long Time and Causes the Server to Power Cycle
Important Operating Note
If you have a pending BIOS upgrade, a routine reset takes longer than expected, and causes the server to power cycle and reboot several times. This is expected behavior, as it is necessary to power cycle the server to upgrade the BIOS firmware. If the upgrade includes an FPGA update, it can take as long as 30 minutes to complete the upgrade and the service processor (SP) resets during the process. Since the SP resets during the process, you will need to re-establish any active connection to the SP after the update.
A pending BIOS upgrade exists when the following conditions are true:
-
You update the BIOS and service processor firmware using Oracle Integrated Lights Out Manager (ILOM).
-
You select the Oracle ILOM option to Delay BIOS Upgrade.
-
The host is powered on.
If you reboot the server expecting a routine server reset and instead initiate a (delayed) BIOS upgrade, wait until the upgrade finishes. Do not interrupt the process, as this can result in corrupted firmware and server down time.
Caution:
Firmware corruption and system downtime. Interrupting the firmware upgrade process can corrupt the firmware and render the server inoperable. Do not interrupt the upgrade. Allow the process to finish.Note:
Oracle ILOM and BIOS updates are designed to work together. When you have a pending BIOS upgrade, it is recommended that you install the upgrade by resetting or power cycling your server as soon as possible.For details, refer to "Update the BIOS and Service Processor Firmware (Oracle ILOM)" in the Oracle X7 Series Servers Administration Guide at https://www.oracle.com/goto/x86admindiag/docs .
Parent topic: Oracle ILOM Issues
Deprecation Notice for Oracle ILOM IPMI 2.0 Management Service
Important Operating Note
Present Behavior: IPMI 2.0 Management Sessions - Enabled (default setting).
Future Behavior: The following IPMI Management Service changes will occur in a future Oracle ILOM firmware release after firmware version 4.0.2.
-
First IPMI Service Support Change – The default configuration property for IPMI 2.0 Sessions will change from Enabled to Disabled. Clients relying on Oracle ILOM IPMI 2.0 session support by default will no longer be able to communicate with Oracle ILOM. To enable IPMI communication with Oracle ILOM, perform one of the following:
-
Use the Oracle IPMI TLS service and interface. For more information, refer to “IPMI TLS Service and Interface” in the Oracle ILOM Protocol Management Reference SNMP and IPMI Firmware Release 4.0.x.
or
-
Manually enable the configuration property for IPMI 2.0 Session. For details, refer to “IPMI Service Configuration Properties” in the Oracle ILOM Administrator’s Guide for Configuration and Maintenance Firmware Release 4.0.x.
-
-
Second IPMI Service Support Change – Removal of IPMI 2.0 client support. IPMI 2.0 clients no longer will be able to communicate with Oracle ILOM. Clients relying on IPMI communication will need to use the IPMI TLS service and interface. For more information, refer to “IPMI TLS Service and Interface” in the Oracle ILOM Protocol Management Reference SNMP and IPMI Firmware Release 4.0.x.
For future updates about IPMI Management Service support in Oracle ILOM, refer to the latest firmware release information published in the Oracle ILOM Feature Updates and Release Notes Firmware Release 4.0.x at https://www.oracle.com/goto/ilom/docs .
Parent topic: Oracle ILOM Issues
Oracle VTS Network Test Floods Serial Console Triggering Soft Lockups
Bug ID: 27240264
Issue: The Network test in Oracle VTS floods the Oracle ILOM SP serial console triggering soft lockup events.
Affected Software: Oracle VTS 8.2.0-patch 1.4
Workaround: There are multiple ways to avoid or workaround this issue. Choose one of the following methods.
Disable the Network test (see example below) in the profile and rerun Oracle VTS to resolve the soft lockups issue.
Set the following Network test profile (see example below) and rerun Oracle VTS to resolve soft lockups:
******************************Test_Groups*****************************
[*]Processor Options idle(Pass=0/Error=0)
[*]System_Interconnect Options idle(Pass=0/Error=0)
[*]Memory Options idle(Pass=0/Error=0)
[ ]Network Options idle(Pass=0/Error=0)
[*]Disk Options idle(Pass=0/Error=0)
[*]Removable_Disk Options idle(Pass=0/Error=0)Run Oracle VTS Network test for a shorter time to reduce soft lockup events.
-
Select Options:
[*]Network Options idle(Pass=0/Error=0) -
Enter 10 into
Test Time. SelectApply.Test Time:[0-99999] 10 -
Save the profile.
-
Restart the test.
Parent topic: Oracle ILOM Issues