v For intermittent problems, check the event log; see “Event logs” on page 148 and“DSA messages” on page 228.Performing the checkout procedureTo perform the checkout procedure, complete the following steps:1. Is the server part of a cluster?v No: Go to step 2.v Yes: Shut down all failing servers that are related to the cluster. Go to step 2.2. Complete the following steps:a. Check the power supply LEDs (see “Power-supply LEDs” on page 21).b. Turn off the server and all external devices.c. Check all internal and external devices for compatibility athttp://www.ibm.com/systems/info/x86servers/serverproven/compat/us/.d. Check all cables and power cords.e. Set all display controls to the middle positions.f. Turn on all external devices.g. Turn on the server. If the server does not start, see “Troubleshooting bysymptom” on page 276.h. Check the system-error LED on the operator information panel. If it isflashing, check the light path diagnostics LEDs (see Light path diagnostics).Note: When you slide the light path diagnostics panel out of the server tocheck the LEDs or checkpoint codes, do not run the server continuouslywith light path diagnostics panel outside of the server. The panel shouldonly be outside of the server a short time. The light path diagnostics panelmust remain in the server when the server is running to ensure propercooling.i. Check for the following results:v Successful completion of POST (see “POST” on page 151 for moreinformation)v Successful completion of startup, which is indicated by a readable displayof the operating-system desktop3. Is there a readable image on the monitor screen?v No: Find the failure symptom in “Troubleshooting by symptom” on page276; if necessary, see “Solving undetermined problems” on page 298.v Yes: Run DSA (see “Running the DSA Preboot diagnostic programs” on page153).– If DSA reports an error, follow the instructions in “DSA messages” onpage 228.– If DSA does not report an error but you still suspect a problem, see“Solving undetermined problems” on page 298.Chapter 4. Troubleshooting 143
