HP Insight Orchestration 6.0 User Guide

The Insight Control virtual machine management template that is being used was created when the virtual
machine was in a suspended state.
Possible cause
Provisioning will fail during customization with an error message if the virtual machine management template
is created when the virtual machine is in a suspended state and then used in Insight Orchestration. To resolve
Action
this issue, you must power off the virtual machine before creating virtual machine management template from
the virtual machine.
Task for logical server <ls name> has failed. Failure: Service console load
average on the source server is greater than the threshold value. Retry the
operation later.
Failure message
The load average on the source or target VMHost may be too high. You can verify this issue by examining the
virtual machine management logfile at: C:\Program Files\HP\Virtual Machine
Possible cause
Management\log\hpvmmsvc.log. Look for logging messages similar to the following. If found, this indicates
that the VMHost identified with the “Source server” tag has exceed the allowable threshold and will result in a
VM failing to deploy.
2009/07/29 08:31:02 | INFO - Source server 16.92.61.30 load average for 5 Minute
-> 1.85
2009/07/29 08:31:02 | INFO - Source server 16.92.61.30 load average for 15 Minute
-> 2.27
2009/07/29 08:31:02 | WARN - Source server 16.92.61.30 load average exceeded the
threshold
The memory and CPU shares that are allocated to the VMware Service Console may be increased to obtain
better performance on the VMHost. For more information, see “Increasing VMware Service console memory
and CPU shares”
Action
Service deletion
Physical
Troubleshooting items addressed in this section:
• Insight Orchestration Delete Service request leaves clean-me logical servers.
• Insight Orchestration did not correctly erase the disk during deprovisioning.
• An infrastructure service has been deleted, but I did not delete it.
• A delete request has failed. The environment must be manually cleaned.
Insight Orchestration Delete Service request leaves “clean-me” logical serversIssue
If using Insight Control server deployment, the job “Erase ProLiant ML/DL/BL Array Configuration
{LinuxPE}” has not been mocified for Insight Orchestration.
Possible cause
If using Ignite-UX, the client has not been set up with permission to run the erase disk job in HP Systems Insight
Manager.
If using Insight Control server deployment, follow Step 9 in the Creating server deployment job folders procedure.
The job must have only two steps:
DetailsTask
Action
Wipe DiskRun Script
Shutdown (if
available)
Power Control
If using Ignite-UX, the client must be set up to run the erase disk following provisioning by running the command:
mxagentconfig –a –n <ip> –u <username> –p <root password>
Insight Orchestration did not correctly erase the disk during deprovisioning.Issue
The Insight Control server deployment erase disk job name is not correct.Possible cause
For Insight Orchestration to correctly erase the disk content when deprovisioning physical servers using a
non-English server deployment version, there must be an English Erase ProLiant ML/DL/BL Array
Action
Configuration {LinuxPE} job under the Server Deployment Toolbox\1 – Hardware
Configuration\Array\ server deployment folder. You can copy and paste the equivalent non-English server
Working with services 67