User Service Guide, Fifth Edition - HP Integrity rx8640 SEU

NOTE: The secondary core I/O card inserted in the upper slot is identified as core I/O 3 and
the primary core I/O card inserted in the lower slot is identified as core I/O 2.
The SEU will work without the top (secondary) core I/O card installed but it will not operate
without the bottom (primary) core I/O card installed.
Troubleshooting Aids
Troubleshooting
The basic steps in troubleshooting are:
• Identify the failure
• Troubleshoot using tools to categorize the failure
• Troubleshoot with specific procedures to pinpoint bad field replaceable unit (FRU).
• Remove the FRU, replace and then verify that the failure had been eliminated
• Restore the system
The steps below will allow quick assessment and solution of most system failures.
1. Determine what the symptom is. The following is a list of symptom examples:
• Attention LED Blinking
• System Alert present on Console
• System will not power up
• System will not boot
• EMS Event Message received
• MCA occurred
2. Narrow down from the observed problem to the specific troubleshooting procedures and
isolate the failure to a specific part of the machine so that more detailed troubleshooting can
be done to find the specific fix.
Example 4-1 Attention Light Is Blinking
If the attention light is blinking, look for more information as follows:
• Observe the console for a system Alert
• Analyze alert using IPMI decoder
• Analyze last IPMI error logged by the MP using IPMI decoder
At this point, the CE should have a good idea which area of the machine needs to be focused
on. For example, if the symptom was “System won’t power up,” the initial troubleshooting
procedures may have led to a problem with the DC power supplies (48 V) not coming up
after the power switch was turned on.
3. Troubleshoot further to identify in more detail the exact cause of the problem.
4. Determine the FRU or FRUs that will fix the problem.
NOTE: If multiple FRUs are identified as part of the solution, a fix cannot be guaranteed
unless all identified FRUs are replaced.
Contractual commitments may dictate multiple FRU replacements.
There may be specific recovery procedures that need to be done to finish the repair. For
example, if the MP is replaced, customer specific information such as user profiles, network
ID’s and passwords will need to be restored.
A basic “getting started” flow might look like figure 1-1.
80 Troubleshooting