HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

12 Troubleshooting
The following sections contain troubleshooting information and recommendations for solving issues
found when using Insight Control server provisioning. If you encounter an issue that is not addressed
in this chapter, contact your authorized support representative.
“Troubleshooting basics” (page 74)
“Known Issues and restrictions” (page 75)
“Customer advisories” (page 75)
“Troubleshoot general usage issues” (page 76)
“Troubleshoot installation, setup and update issues” (page 80)
“Troubleshoot adding and booting servers” (page 80)
“Troubleshoot OS Build Plan and build plan step failures” (page 83)
“Troubleshoot directory services” (page 96)
“Status messages” (page 97)
Troubleshooting basics
The following are helpful steps you can follow whenever something does not work as expected:
Look at the job log
Check the job logs for error messages. You can see the logs by clicking the “logs” link
in the jobs details once the job has completed. Error message should be displayed in the
logs.
If you are adding a server via the iLO, there are two jobs that are started—check them
both. Both job names should have the iLO IP address as part of their name.
If you are adding a server via PXE, a single job is created to register the iLO after the
server boots into maintenance. Check the job log to see if there was a failure.
In the job log notice if the OS Build Plan is HP-provided or a customized Build Plan.
Check to see which step failed. Note the steps leading up to the failure.
Verify the parameters of the failed step.
Check the console on the target server.
Is this system in the state you expected? If not, why not?
Check for errors on the screen that can explain the problem.
Re-run the Build Plan and watch the console for errors.
Verify that the server is booting correctly.
Verify that the target server is reachable on the network and that only one NIC is attached to
the Deployment network.
Verify the appliance configuration.
Verify the media server is reachable. Is gateway and/or DHCP properly configured?
Make sure there is a DHCP server on the deployment network.
74 Troubleshooting