About This Documentation (PDF and HTML)
Introduction to Diagnostic Tools
Diagnostic Tools for Oracle Servers
Using the Diagnostic Tools to Troubleshoot a Server
U-Boot Diagnostic Startup Tests
U-Boot Diagnostic Startup Tests Overview
System Diagnostic Test Options at Startup
Reporting Diagnostic Failures at System Startup
Running the U-Boot Diagnostic Tests
Sample SP Environmental Variables Showing U-Boot Test Status
Accessing Pc-Check Diagnostics Utility
Accessing the Pc-Check Diagnostics Utility on the Tools and Drivers CD/DVD
How to Access and Run Pc-Check From the Tools and Drivers CD/DVD
How to Access and Run Pc-Check From a USB Device
How to Set Up the Tools and Drivers CD/DVD Image on the PXE Server
How to Access the Tools and Drivers CD/DVD From the Target Server
U-Boot offers three diagnostic modes of operation: -Normal, -Quick, and -Extended. -Normal mode diagnostic tests are run by default each time the server starts up. Other modes of operations (-Quick or -Extended) must be selected to run at startup.
For details about which U-Boot diagnostic tests are run for each mode, see the following table. For details about how to select one of the three U-Boot modes to run at system startup, see How to Select a U-Boot Diagnostic Mode to Run at Startup.
Note - If any of the U-Boot diagnostic tests fail during startup, the server SP will not start. See Reporting Diagnostic Failures at System Startup for additional details.
|
1For rackmount servers, the I2C tests check the connectivity to all I2C devices installed in the chassis. For Oracle's Sun Blade 6000 or 6048 Chassis Modular Systems, the I2C tests check only the connectivity to I2C devices installed on an individual server module.