HP Insight Control Server Provisioning 7.2 Online Help

12.32.3 atMost parameter is too small
The Wait for HP SA Agent step waits as long as the --atMost parameter specifies. 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.
12.32.4 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 the NIC on the target server is accessible by the appliance, either on the same network
or routable.
12.32.5 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.
12.32.6 The BIOS hardware date and time are incorrect
Correct the date and time in BIOS or boot the server to the Linux service OS. The Linux service OS
will synchronize its time to the time on the appliance.
12.32.7 The decommission step broke the agent connection
It’s possible for the appliance to lose its connection to the server under the following condition:
1. The server was originally in production and then booted to a service OS without the
decommission step. Some hardware Build Plans might do this.
2. 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.
12.33 Server is in WinPE after capture image
12.33.1 Symptom
The target server is left in the WinPE service OS after the capture image Build Plan is run.
12.33.2 Resolution
This is the expected behavior. You will need to deploy the image you just captured back to the
reference server.
12.34 When booting the appliance, UNEXPECTED INCONSISTENCY
error
When booting the appliance, the boot process fails with an “UNEXPECTED INCONSISTENCY”
error and requests an fsck be run. This happens when the date and time on the VM host is
incorrect and is set to a date earlier than the date the appliance was created or last booted.
Change the date and time on the VM host to the correct time and reboot the appliance.
110 Troubleshooting index