HP ProLiant Gen8 Troubleshooting Guide Volume I: Troubleshooting

Hardware problems 61
Cable problems
Drive errors, retries, timeouts, and unwarranted drive failures when using an older
Mini SAS cable
Action: The Mini SAS connector life expectancy is 250 connect/disconnect cycles (for external, internal, and
cable Mini SAS connectors). If using an older cable that could be near the life expectancy, replace the Mini
SAS cable.
Network controller or FlexibleLOM problems
Network controller or FlexibleLOM is installed but not working
Action:
1. Check the network controller or FlexibleLOM LEDs to see if any statuses indicate the source of the
problem. For LED information, see the network controller or server documentation.
2. Be sure no loose connections (on page 17) exist.
3. Be sure the correct cable type is used for the network speed or that the correct SFP or DAC cable is used.
For dual-port 10-GB networking devices, both SFP ports should have the same media (for example,
DAC cable or equal SFP+ module). Mixing different types of SFP (SR/LR) on a single device is not
supported.
4. Be sure the network cable is working by replacing it with a known functional cable.
5. Be sure a software problem has not caused the failure. For more information, see the operating system
documentation.
6. Be sure the server and operating system support the controller. For more information, see the server and
operating system documentation.
7. Be sure the controller is enabled in RBSU or in the UEFI System Utilities.
8. Be sure the server ROM is up to date.
9. Be sure the controller drivers are up to date.
10. Be sure a valid IP address is assigned to the controller and that the configuration settings are correct.
11. Run Insight Diagnostics ("HP Insight Diagnostics" on page 73) and replace failed components as
indicated.
Network controller or FlexibleLOM has stopped working
Action:
1. Check the network controller or FlexibleLOM LEDs to see if any statuses indicate the source of the
problem. For LED information, see the network controller or server documentation.
2. Be sure the correct network driver is installed for the controller and that the driver file is not corrupted.
Reinstall the driver.
3. Be sure no loose connections (on page 17) exist.
4. Be sure the network cable is working by replacing it with a known functional cable.
5. Be sure the network controller or FlexibleLOM is not damaged.