HP CloudSystem Matrix How-To Guide: ESXi Cluster Provisioning

28
Troubleshooting
This section lists some of the issues that can arise when you are provisioning clusters. Note that changes
to configuration files will require the affected services to be restarted or rebooted.
Issue
If the provisioning fails, "clean-me" logical servers can be created.
Action
Because the ESXi hosts do not have boot disks, it is only necessary to delete the logical servers.
It is not necessary to follow the full manual clean-up process.
Issue
During logical server provisioning and before OO workflows start, the following message
appears:
Workflow execution error: Target blade does not have enough network ports with
network connectivity to support networks configured in LogicalServer.
Possible cause
In the template, the Networks tab of the server group specified redundant network interfaces.
Action
Clear the redundancy or supply an appropriate blade.
Issue
Failure message:
Workflow 00_ConfigureVMADBootProfile_server_begin has failed.
Possible cause
Auto Deploy Depot is not set up correctly in OO.
Action
Configure OO with the correct file path or network path for Auto Deploy Depot. For more
information, see "Step 3: Configure Operations Orchestration properties."
Issue
Failure message:
Workflow 05_CheckServerHasBooted_server_end has failed.
Or a pink screen displays in the iLO blade.
Possible cause
Auto Deploy Depot is corrupt or does not have the necessary drivers.
Action
Reconfigure Auto Deploy Depot image file from HP web site.
Issue
Failure message:
Cannot register the VM Host in HP SIM. Possible causes: a) HP SIM is not
running; b) Incorrect vCenter credentials were supplied; c) vCenter is not
discovered or connected; d) VM Host is not deployed/ready or not started; e)
RSJRAS service is not running with local account credentials (such as
Administrator). If any of these conditions exist, correct the problem and
retry the operation. See the HP Insight Control Virtual Machine Management
User Guide for more details.
Possible cause
The RSJRAS Windows service is not using the administrator
credentials. Or
The OO credentials for the ESXi server are insufficiently complex.