Using the Diagnostic Tools to Troubleshoot a Server

This section provides some basic troubleshooting recommendations. The following topics are covered:

• Troubleshooting Scenarios

• Diagnostic Test Coverage

• Setting Up a Server for Testing

Troubleshooting Scenarios

There are four basic scenarios that you will encounter during the 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 that you ordered already installed, run the diagnostic tests before placing the server into service. This way you will verify that the server is in good working order (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 needs to 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. Install the options only after determining that the server is in good working order. After installing the options, 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 tests 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 have placed the server into service and it has been operating properly for some 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.

Server Components Tested by Diagnostics Tools provides step-by-step troubleshooting procedures.

Table 1-1 Troubleshooting Scenario 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.

---

Diagnostic Test Coverage

Server Components Tested by Diagnostics Tools shows which server components are tested by the different diagnostic tests: U-Boot, Pc-Check, and Oracle VTS.

Table 1-2 Server Components Tested by Diagnostics Tools

Setting Up a Server for Testing

Diagnostic tests can be run locally using the server’s serial port (SER MGT) or over the network using the server’s network management port (NET MGT). For instructions for connecting the server locally or over the network, see the hardware installation guide for your server.