Diagnostic tests can be used to verify the operation of a server when it is newly installed, when it is upgraded or modified, and when it fails. The following sections list the common testing scenarios:
Run the following diagnostic tests before installing any options:
U-Boot
Pc-Check or UEFIdiag
HWdiag
Tests failed: If the tests identify a server failure:
Check the product notes or release notes for the product or option for any known conditions that might cause a diagnostic test to fail.
If you do not solve the problem by looking in the product notes or release notes, assume that the server was damaged in shipment. Terminate the installation process, and notify Oracle Service. This ensures that the server is covered under warranty.
If you experience a network connectivity problem when placing a server into service for the first time, ensure that the network access point for the server is activated.
Tests passed: If the server passes the tests and has no options to install, you can place it into service.
If the server passes the test and has options to install, install the options and re-run the tests.
If it passes the test with the options installed, you can place it into service.
If the diagnostic tests reveal that an installed option is faulty, remove the option and return it for replacement.
Before installing a server upgrade (memory, hard disk drives, I/O cards, or power supply), take the server out of service and run the diagnostic tests:
Take the server out of service.
Run the U-Boot diagnostic tests.
Run the Pc-Check, UEFIdiag., or HWdiag diagnostic tests.
Install the server upgrade.
Run the U-Boot, HWdiag, and Pc-Check or UEFIdiag diagnostic tests again.
Tests failed: If the diagnostic tests fail, one of the installed options was faulty or the server was damaged when you installed the options. In either case, remove and replace the faulty component, run the diagnostic tests again to confirm that the problem has been corrected, and place the server into service.
Tests passed: Place the server into service.
The server has been operating problem free for a long time, and the Service Action Required LED on the server's front panel illuminates.
Do the following:
Before opening the server's cover, inspect the server and Oracle ILOM service processor (SP) log files for obvious fault messages and any fault LEDs. Refer to your service documentation for details.
Inspect the server's internal components for obvious problems, such as burnt components, or anything that might inhibit proper cooling of a server component.
If the visual inspection does not identify a failed component, run the U-Boot tests and then the Pc-Check or UEFIdiag diagnostic tests to identify the failed component.
If the tests do not identify the failed component, run SunVTS.
If the failed component is a customer-replaceable unit (CRU), replace it. For each model, CRUs are defined in the service manual, the System Handbook, and My Oracle Support.
If the failed component is a field-replaceable unit (FRU), initiate a service request with Oracle Service. FRUs are defined in the service manual for the particular server model.