1. Oracle x86 Servers Diagnostics and Troubleshooting Guide
  2. Oracle ILOM Diagnostics
  3. Using a Non-Maskable Interrupt

Using a Non-Maskable Interrupt

Sending a non-maskable interrupt (NMI) to the host operating system can cause the host to stop responding and wait for input from an external debugger. Use this feature only when requested to do so by Oracle Service personnel.

Caution:

Do not send an NMI to the host operating system unless requested to do so by Oracle Service personnel.

To generate an NMI, see:

Generate a Non-Maskable Interrupt (Web)

Note:

The setting for generating a non-maskable interrupt from Oracle ILOM might not be supported on all Oracle servers.

Caution:

Depending on the host OS configuration, generating an NMI might cause the OS to crash, stop responding, or wait for external debugger input.
  1. Obtain permission from Oracle Service prior to performing this procedure.
  2. To generate an NMI from the Oracle ILOM interfaces, verify that you have Reset and Host Control (r) privileges.
  3. From the Oracle ILOM web interface, click Host Management → Diagnostics.
  4. On the Diagnostics page, to send an NMI to the host, click the Generate NMI button.

Generate a Non-Maskable Interrupt (CLI)

Note:

The setting for generating a non-maskable interrupt from Oracle ILOM might not be supported on all Oracle servers.

Caution:

Depending on the host OS configuration, generating a non-maskable interrupt (NMI) might cause the OS to crash, stop responding, or wait for external debugger input.
  1. Obtain permission from Oracle Service personnel before performing this procedure.
  2. To generate an NMI from the Oracle ILOM interfaces, verify that you have Reset and Host Control (r) privileges.
  3. To send an NMI to the host, from the Oracle ILOM CLI, type set /HOST/ generate_host_nmi=true.