HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

Possible cause and resolutionSymptom
If a Linux OS Build Plan fails during a PXE-less deployment
on the Create stub partition step with the following error
then review the possible causes and resolution:
2. There is a previously installed Windows OS on the boot
disk and SAN.
• The boot disk on the target server is connected to a
SAN with a multi-path configuration and contains a
previously installed Windows operating system. Edit
the Build Plan and add the Unmount all Boot Disk
Partitions step before the Create stub partition step.
Re-run the Build Plan.
Check iLO service step failures
OS Build Plan fails on Check iLO Service step
The Symptom in all cases is that the OS Build Plain fails on Check iLO Service step. Possible causes
are the numbered items in the right-hand column, with suggested resolutions shown in the bulleted
paragraphs immediately below.
Possible cause and resolutionSymptom
OS Build Plan fails on Check iLO Service step 1. The target server does not have an iLO.
• Insight Control server provisioning only supports
ProLiant servers with embedded iLO management
processors when deploying to physical servers.
2. The iLO is not reachable.
• Verify the network connectivity from the appliance to
the iLO NIC on the target server.
3. The appliance has not associated an iLO with the server.
• The target server has an iLO but there is not an iLO
associated with the server in the appliance database,
or automatic iLO registration failed during PXE boot.
If your target server was discovered via PXE, check
the iLO registration job status to see if the register iLO
and create iLO account tasks failed. You might need
to delete and add the server again. If the server was
added while in production or if the server was
migrated from RDP, iLO information can be provided
on the Add server screen. Be sure to select Do not
boot to maintenance.
4. The target server is a VM guest.
• Remove the Check iLO Service step from the OS Build
Plan.
See the online help topic “Create an OS Build Plan
for VM guest deployment”.
Intelligent Provisioning firmware update failures
If you experience a failure with the ProLiant SW — Intelligent Provisioning Firmware Update Build
Plan, the actions shown below may assist in troubleshooting the problem.
• Verify that your target server is a Gen8 server or newer, as earlier servers do not support
Intelligent Provisioning.
• Check if you have set your IPversion custom attribute and, if you have set it, make sure
that it contains a valid value which corresponds to a subdirectory name under the Media/ip
directory on your Media Server. Setting the IPversion custom attribute is not required. By
default, the subdirectory under the Media/ip directory with the largest value, determined by
sort order, is selected. For example, if the directories Media/ip/1.50 and Media/ip/1.60
94 Troubleshooting