HP ProLiant DL160se ProLiant DL100 Series Servers User Guide - Page 17
Troubleshooting, Common problem resolution, Loose connections, Service notifications
View all HP ProLiant DL160se manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 17 highlights
Troubleshooting Common problem resolution Loose connections (on page 17) Service notifications (on page 17) Loose connections Action: • Be sure all power cords are securely connected. • Be sure all cables are properly aligned and securely connected for all external and internal components. • Remove and check all data and power cables for damage. Be sure no cables have bent pins or damaged connectors. • If a fixed cable tray is available for the server, be sure the cords and cables connected to the server are routed correctly through the tray. • Be sure each device is properly seated. Avoid bending or flexing circuit boards when reseating components. • If a device has latches, be sure they are completely closed and locked. • Check any interlock or interconnect LEDs that may indicate a component is not connected properly. • If problems continue to occur, remove and reinstall each device, checking the connectors and sockets for bent pins or other damage. Service notifications To find out the latest service notifications, refer to the HP website (http://www.hp.com/products/servers/platforms). Select the appropriate server model, and then click the Documentation link on the product page. Problem diagnosis This section covers the steps to take in order to diagnose a problem quickly. To effectively troubleshoot a problem, HP recommends that you start with the first flowchart in this section, "Start diagnosis flowchart (on page 21)," and follow the appropriate diagnostic path. If the other flowcharts do not provide a troubleshooting solution, follow the diagnostic steps in "General diagnosis flowchart (on page 22)." The General diagnosis flowchart is a generic troubleshooting process to be used when the problem is not server-specific or is not easily categorized into the other flowcharts. Troubleshooting 17