The following are helpful steps to follow whenever something does not work as expected:
-
View the job log
-
Check the job logs for error messages. You can view the logs by clicking the Logs link in the Jobs details once the job has completed. Messages in the logs are the best way to figure out what went wrong.
-
If you are adding a server using the iLO, usually three jobs are started—check them. Two of the job names should have the iLO IP address as part of their name and the other job will be near these two.
-
If you are adding a server using 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 determine if the OS Build Plan is Hewlett Packard Enterprise provided or a customized Build Plan. If it's a customized Build Plan, try the Hewlett Packard Enterprise provided template to see if the customizations are the problem.
-
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 the gateway and/or DHCP properly configured?
-
Make sure there is a DHCP server on the deployment network.
-
If using an external DHCP server, make sure it is properly configured as described in the Insight Control Server Provisioning Installation Guide and has all the non-standard parameters defined.
-
-
Check the Media Server
-
Run the ProLiant SW — Validate Media Server Settings Build Plan. This Build Plan checks for most Media Server issues.
-
Make sure the Media Server is booted and reachable by the target servers on the deployment network.
-
Verify that you can access the files on the Media Server using the file share and HTTP.
-
Make sure the correct distribution files are on the Media Server. For OS distributions, only 64–bit server OSs are supported.
-
Make sure the directory name on the Media Server matches the data provided in the Build Plan.
-
For more Media Server troubleshooting, see Set Media Source step and Media Server troubleshooting.
-
-
Check for known hardware/software considerations and restrictions
-
Certain combinations of hardware, software, and, target server configuration can cause interoperability issues. As these issues are discovered, they are documented in the Hardware and software specific instructions and exceptions section. Issues found late in the release are listed in the Release Notes. Always check these sections to see if your configuration has a known issue.
-
-
User Interface issues
-
Refresh the browser display.
-
If refresh doesn’t fix the issue, clear the cache and try again.
-
These preliminary steps often lead you quickly to the source of any problems. If not, the detailed information in the following sections will provide guidance on locating and resolving operational issues.
If you are having trouble with your Build Plans, one of the most powerful troubleshooting steps is the ability to enter commands on your system console while the server is still in the service OS. Doing this enables you verify proper operation of your media server, hard drives, network connections. See Access the command prompt on your target server while in the service OS.