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 Newer SPARC Systems (Web)

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 apply to newer SPARC servers such as T7, M7, and later SPARC series servers.

  • Oracle ILOM firmware 3.2.5.5 or later.

To enable SPARC diagnostics tests to run, do the following:

  1. From the Oracle ILOM web interface, click Host Management > Diagnostics.

    The Diagnostics page appears.

  2. In the Diagnostics page, specify the level and verbosity for each of the following properties:
    • Default — 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.
    • HW Change — Run diagnostics in the event of an AC power cycle, server top cover removal, or FRU (field-replaceable unit) replacement.

    • Error Reset — Run diagnostics in the event of an error-invoked reset.

      Levels:

      The level determines the type of diagnostic tests that will run. You can set the Level property to the following:

      • Off — Prevent POST from running

      • Min — Run a basic suite of diagnostic tests

      • Max — Run a basic suite of diagnostic tests, plus extensive processor and memory tests.

      Verbosity:

      The verbosity determines the amount of debugging output that is printed to the system console. You can set the Verbosity property to the following:

      • None — Prevent debugging output from being printed to the system console.

      • Min — Print a limited amount of debugging output.

      • Normal — Print a moderate amount of debugging output, including test names and results.

      • Max — Print all POST step debugging output.

      • Debug — Print an extensive amount of debugging output, including names of devices being tested, as well as the debugging output for each test.

  3. Click Save.