JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle® x86 Servers Diagnostics Guide For Servers Supporting Oracle ILOM 3.0.x
search filter icon
search icon

Document Information

Preface

1.  Introduction to Diagnostic Tools

About Diagnostic Tools

Strategy for Diagnostics

To Diagnose Server Problems

Service Processor

Standalone Package-Based Diagnostics

Offline Operating System-Based Diagnostics

Online Operating System-Based Diagnostics

Diagnostic Tools for Oracle Servers

BIOS POST

U-Boot

Pc-Check

Oracle VTS

Snapshot Utility

Using the Diagnostic Tools to Troubleshoot a Server

Troubleshooting Scenarios

Diagnostic Test Coverage

Setting Up a Server for Testing

2.  U-Boot Diagnostic Start-Up Tests

U-Boot Diagnostic Start-Up Tests Overview

Server Diagnostic Test Options at Start-Up

U-Boot Diagnostic Test Modes - Normal, Quick, and Extended

Reporting of Diagnostic Failures at Server Start-Up

Running the U-Boot Diagnostic Tests

Before You Begin

To Select a U-Boot Diagnostic Mode to Run at Start-Up

Sample U-Boot Test Output

U-Boot Normal Mode - Test Output Sample

U-Boot Quick Mode - Test Output Sample

U-Boot Extended Mode - Test Output Sample

Sample SP Environmental Variables Showing U-Boot Test Status

3.  Pc-Check Diagnostics Utility

Pc-Check Diagnostics Overview

Accessing the Pc-Check Diagnostics Utility

To Access Pc-Check Using the Oracle ILOM Web Interface

To Access Pc-Check Using the Oracle ILOM CLI

System Information Menu

System Information Menu Options

Advanced Diagnostics Tests

Advanced Diagnostics Tests Menu Options

Immediate Burn-in Testing

Immediate Burn-in Testing Menu Options

Deferred Burn-in Testing

To Create and Save Scripts for Deferred Burn-in Testing

Show Results Summary

Show Results Summary Menu Options

Print Results Report

About Pc-Check

Exit to DOS

Index

Running the U-Boot Diagnostic Tests

The U-Boot diagnostic test in -Normal mode automatically runs each time you start your server. However, if you would like to run the U-Boot diagnostic test in -Quick or -Extended mode, you must select these modes to run at start-up. For further details on how to select one of the three U-Boot diagnostic modes to run at start-up, see To Select a U-Boot Diagnostic Mode to Run at Start-Up

Before You Begin

All U-Boot diagnostic tests are required to run from a serial connection. You must have either a hyper terminal or a local or network serial console connected to the server.

For information about how to connect a local serial console to the serial port on the server, refer to the installation guide for your server. For information about how to establish a network serial connection to the SP, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Daily Management – Concepts Guide.

To Select a U-Boot Diagnostic Mode to Run at Start-Up

  1. Establish a serial connection to the server SP.

    For details, see either the installation guide for your server or the Oracle Integrated Lights Out Manager (ILOM) 3.0 Daily Management – Concepts Guide.

  2. Power cycle or restart the server.

    The Power/OK LED blinks slowly as U-Boot executes. The U-Boot output is sent directly to the server serial port.

    For details on how to power on or restart your server, see the installation guide for your server.

  3. Watch for the following prompt in the U-Boot output and do one of the following:
     
    Enter Diagnostics Mode {'q'uick/'n'ormal (default)/e'x'tended]...
    • Type “n” to enable -Normal mode U-Boot tests; or let the countdown continue to run Normal mode.
    • Type “q” to enable -Quick mode U-Boot tests.
    • Type “x” to enable -Extended mode U-Boot component tests.
  4. Monitor U-Boot output from the serial console connection.

    If there is a diagnostic failure, the SP will not start. See Reporting of Diagnostic Failures at Server Start-Up for further details.