Go to main content

Oracle® x86 Servers Diagnostics and Troubleshooting Guide

Exit Print View

Updated: January 2020

Run UEFI Diagnostics Automatically (Web)

  1. Verify that you have Reset and Host Control (r) role privileges, which you need to diagnose system hardware issues.
  2. If you want to monitor the progress of diagnostic tests in Enabled or Extended mode, see UEFI Diagnostics Test Modes.
  3. Power the server to Standby power mode:
    1. In the Oracle ILOM web interface, click Host Management → Power Control.
    2. In the Select Action list box select a Power Off option, and then click Save.

      The System OK LED on the front panel is blinking.

  4. Start a video or serial console redirection:
    1. In the navigation pane, click Remote Control → Redirection.
    2. Select a redirection: Video or Serial.
    3. Click Launch Remote Console.

      Several dialog boxes might appear. Click to accept them, as necessary.

      A redirection window appears when the redirection is established. For video redirection, ensure that (Full Control) appears in the title bar of the remote console window.

  5. Click Host Management → Diagnostics.
  6. On the Diagnostics page, perform the following steps:
    1. In the Mode list box, select Enabled or Extended mode.

      For details about the diagnostic levels, see UEFI Diagnostics Test Modes.

    2. Click Save.

      The Start Diagnostics button is enabled.

    3. Click Start Diagnostics.

      An informational message about controlling diagnostics through the remote console application appears.

      Note -  As UEFI diagnostics boot, you might see messages stating that you can use function keys to interrupt the boot process. These messages do not apply to UEFI diagnostics. Do not press any function keys when starting the UEFI diagnostics.
    4. Click OK to clear the message and proceed with the diagnostic tests.

      The Diagnostics Status field indicates the progress of the diagnostic tests.

      If you are running Enabled or Extended diagnostics, the tests run automatically. If there is an internal error, you can abort the test (see Step 6e) or wait for ILOM to detect the error and restore the system to Disabled mode, which could take more than one hour. The Status field is updated accordingly.

      Note -  The boot process can take several minutes, and might include an extra power cycle.

      Note -  To check the history of the test using Oracle ILOM event log, select ILOM Administration → Logs → Event → Filter → Custom Filter → Event Type → Diags.


      Caution  -  Do not disrupt the test progress by changing the server power state. If there is an unexpected AC power cycle and a test is in progress, configure Diagnostics mode again starting from Step 3. Internal variables could be corrupted and setting a new mode or resetting the same mode fixes any potential issue.

    5. To safely disrupt the diagnostic tests, click Stop Diagnostics.

      Note -  When you stop running the diagnostic tests, wait approximately 40 seconds while Oracle ILOM is searching for CPU errors, before you enter another command. Because the host power status is off, you can change the Diagnostics mode or resume the same mode.
    6. View the UEFI Diagnostics logs. See UEFI Diagnostic Logs.