Go to main content

Oracle® ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 3.2.x

Exit Print View

Updated: April 2018
 
 

Enable Host Diagnostics to Run on Legacy SPARC Servers (CLI)

Before You Begin

  • The Reset and Host control (r) role is required to modify the SPARC diagnostic properties in Oracle ILOM on SPARC systems.

  • The Steps in this procedure are applicable to legacy SPARC servers such as M6, M5, T5 and some earlier T series servers.

To enable SPARC server diagnostics tests to run when the system is powered on, do the following:


Note -  CLI paths for multi-domain SPARC servers are not described in the following procedure. To set PDomain-specific diagnostics, append /Servers/PDomains/PDomain_n/ to the beginning of the CLI paths listed below.
  1. In the Oracle ILOM CLI, issue the set command to configure the host diagnostic trigger for running tests:

    set /HOST/diag trigger=[none, power-on-reset, error-reset, all-reset]

    where trigger = [none, power-on-reset, error-reset, all-reset]

    • none — Do not run diagnostic tests.

    • power-on-reset — Run diagnostics in the event of a routine power on, power cycle, or reset.


      Note -  This setting does not apply in the event of an AC power cycle, hardware change, or error-invoked reset.
    • error-reset — Run diagnostics upon any error-invoked power reset.

    • all-resets — Run diagnostics whenever a power reset occurs.

  2. Set the diagnostic test level for the diagnostic trigger that you specified in Step 1:
    • If you specified power-on-reset or all-resets, type:

      set /HOST/diag power_on_level=[min, max]

    • If you specified error-on-reset or all-resets, type:

      set /HOST/diag error_reset_level=[min, max]

      where level = [min, max]

      • min — Run the minimum set of diagnostics to partially verify the health of the system.

      • max (default) — Run the maximum set of diagnostics to fully verify the health of the system.

  3. Set the verbosity output for the diagnostic trigger that you specified in Step 1:
    • If you specified power-on-reset or all-resets, type:

      set /HOST/diag power_on_verbosity=[none, min, max, normal, debug]

    • If you specified error-on-reset or all-resets, type:

      set /HOST/diag error_reset_verbosity=[none, min, max, normal, debug]

      where verbosity = [none, min, max, normal, debug]

      • none — Do not print output to the system console while diagnostics are run, unless a fault is detected.

      • min — Print limited output to the system console while diagnostics are run.

      • max — Print the full output to the system console while diagnostics are run, including the name and results for each test.

      • normal (default) — Print a moderate amount of output to the system console while diagnostics are ran.

      • debug — Print extensive debugging output to the system console while diagnostics are run, including device testing and debugging output for each test.

  4. Set the diagnostic mode to either: 1) run the diagnostic tests at boot; or 2) disable the diagnostics tests from running at boot.

    set /HOST/diag mode=[off, default]

    where mode = [off, default]

    • off – Prevents the diagnostic test specified in Step 1 from running.

    • (default) – Runs the diagnostic test specified in Step 1.