Run UEFI Diagnostics Automatically (CLI)
- Verify that you have Reset and Host Control (r) role privileges, which you need to diagnose system hardware issues.
- If you want to monitor the progress of diagnostic tests in Enabled or Extended mode, see UEFI Diagnostics Test Modes.
-
Power off the server.
- Type stop /System.
-
To stop the system, type y.
The System OK LED on the front panel is blinking.
-
To access the Host (UEFI shell), start a serial console
redirection:
- Log in to the Oracle ILOM command-line interface (CLI) as root.
- Type start /HOST/console.
- To start the host console, type y.
- To open another ILOM CLI session to manage the power state and start UEFIdiag tests, type y.
-
To verify that the host is in Standby power mode, type show
/System/ power_state.
The System OK LED on the front panel is blinking.
The power state displays as Off.
- To change the directory to /HOST/diag, type cd /HOST/diag.
-
Enter the set mode=<mode>
command to choose one of the following UEFI diagnostic modes:
-
Enabled
-
Extended
For example, to run UEFI diagnostics tests in Enabled mode, type: set mode=enabled.
-
-
Start the UEFI diagnostics.
- Type start /HOST/diag.
- To start the UEFI diagnostics, type y.
The server automatically boots and starts UEFI diagnostic tests. No more action is necessary.
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.If you are running Enabled or Extended diagnostics, the tests run automatically. If there is an internal error, abort the test (see Step 10) 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.
-
To view the progress of the diagnostic tests, type show
/HOST/diag status.
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.
-
Stop the diagnostic tests.
- Type stop /HOST/diag.
- To stop the UEFI diagnostics, type y.
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. You can change the Diagnostics mode or resume the same mode. -
To resume running the diagnostic tests:
- Type start /HOST/diag.
- To start the UEFI diagnostics, type y.
Note - To check the history of the test using ILOM Event logs, type: show /SP/logs/event/list/ type==diags. - View the UEFI Diagnostics logs. See UEFI Diagnostic Logs.