About This Documentation (PDF and HTML)
Introduction to Diagnostic Tools
Diagnostic Tools for Oracle Servers
Using the Diagnostic Tools to Troubleshoot a Server
Setting Up a Server for Testing
U-Boot Diagnostic Startup Tests
U-Boot Diagnostic Startup Tests Overview
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
There are four basic scenarios that you can expect to encounter during life of a server:
Scenario 1 (Typical first time server installations: No server options need to be installed)—If the server was shipped to you with all the server options you ordered already installed, run the diagnostic tests before placing the server into service. This way you can verify whether the server is in good working order or not (the server might have been damaged in shipment). If the diagnostic tests indicate that the server has a faulty component, notify the seller (Oracle or the Oracle reseller) that the server failed initial testing and should be repaired or replaced.
Scenario 2 (First time server installations: Server options shipped separately and need to be installed)—If the server was shipped to you with options that you need to install, run the diagnostic tests before installing the options. This will ensure that the server arrived in good working order. Only after determining that the server is in good working order should you install the options. After installing the options, you should run the diagnostic tests again to ensure that the server is in good working order with the options installed. Then you can place the server into service. If the diagnostic tests reveal that an installed option is faulty, remove the option and return it for replacement.
Scenario 3 (Upgrading a server: You have placed the server into service and then you receive an upgrade or option that needs to be installed)—In this case, take the server out of service, run the recommended diagnostic tests, install the upgrade, and then run the diagnostic test again before placing the server back into service. If the diagnostic tests reveal that the installed upgrade is faulty, remove the upgrade and return the upgrade for replacement.
Scenario 4 (An in-service server fails: You placed the server into service and it has been operating properly for a period of time but then fails)—In this case, take the server out of service, do a visual inspection of the server’s internal components to see if you can detect any obvious problems (such as a burnt component or dust accumulation that is preventing cooling of server components). If necessary, run the recommended diagnostic tests to identity the faulty component, remove and replace the faulty component, run the diagnostic tests again to ensure that the server has been repaired, and then place the server into service.
Note - For scenario 4, if you have a service contract with Oracle that includes the Automated Service Request (ASR) service, Oracle Service diagnoses and repairs server failures. Whether you have the ASR service or not depends on availability of this support to your site.
The following table provides step-by-step troubleshooting procedures.
|
Caution - If you do not have a replacement component for a failed component and you want to place the server into service, before doing so, replace the faulty component with a filler panel. Placing the server into service without a filler panel in a blank component space could cause the server to overheat and shut down. |