HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

Linux or ESXi Build Plan fails with a copy boot error
Possible cause and resolutionSymptom
The OS distribution is not present in the Insight Control
server provisioning Media Server.
A Linux or ESXi Build Plan may fail with error message:
Copy Boot Media failed with exit code 3
Run the Insight Control server provisioning Media Server
Setup utility on the Media Server to copy the OS distribution
to the correct folder. Or manually copy the distribution to
the correct folder location.
Wait for HP SA Agent failures
OS Build Plan or add iLO fails at Wait for HP SA Agent step
Possible cause and resolutionSymptom
This indicates the server failed to complete a triggered boot,
start the agent, and register itself with the appliance. This
A Build Plan or add iLO function fails at the Wait for HP
SA Agent step with the following error: “Wait for HP SA
Agent failed with exit code 6.” is one of the most common errors as it can be caused by
any number of things
1. Target server is inaccessible
• The Wait for HP SA Agent step will time out waiting
for the agent to register with the appliance. Make
sure one and only one NIC on the target server is
being used as the deployment NIC, and make sure
that NIC is accessible by the appliance, either on the
same network or routable.
2. atMost parameter is too small
• The Wait for HP SA Agent step waits as long as the
--atMost parameter specifies. The default is 15 minutes.
It is taking longer for the server to boot and the agent
to start. Change the --atMost parameter in the Wait
for HP SA Agent step to something larger.
3. Target server did not get a DHCP address
• Make sure DHCP is configured either on the appliance
or with an external DHCP server. There must be a
properly configured DHCP server that can provide an
IP address and booting information to the target
server.
4. The decommission step broke the agent connection
• It’s possible for the appliance to lose its connection
to the server under the following condition:
a. The server was originally in production and then
booted to a service OS without the decommission
step. Some hardware Build Plans might do this.
b. Later, a boot step calling for the same service OS was
run, but this boot step was followed by a
decommission step, as in most OS installation Build
Plans.
• The result is the decommission step breaks the
appliance connection to the agent and the Build Plan
fails. If this happens, you can run the OS installation
Build Plan again and it should recover. If you want
to bring a system from production back to
maintenance for eventual reinstallation and you want
to avoid this scenario, run one of the Prepare server
for Reprovisioning Build Plans.
90 Troubleshooting