HP Insight Orchestration 6.3 User Guide

failure status. Failure: Exception creating connection to: 15.2.50.138; nested exception is:
java.net.NoRouteToHostException: No route to host: connect. Or: Task for logical server
<logical_server_id> has failed. Logical server job <job_id> completed with a failure status.f
Failure: no such object in table.
• Manual Storage Provisioning email states that more data LUNs than are required should be
added.
• Cannot add servers to an existing service using a Static IP address.
• Provisioning request remains paused during a manual storage allocation (approximately 5%);
cannot create a storage pool on HP Insight Dynamics because the VCDG is not listed on the
Storage Pools screen.
• Operating system deployment process through Insight Control server deployment fails when
deploying to a SAN booted physical server.
• Service creation fails in the in the target reconfiguration phase.
• Service creation fails for physical requests when Windows Server OS is selected.
• Request with a future start date stays at 10% (Progress field), with status of Reserved (rather
than Scheduled).
• Physical server provisioning using Insight Control server deployment fails during the final
personalization step when the CMS is configured with an automatic proxy configuration script
in IE.
• Server reservation and allocation fail, even though servers exist in the assigned pool that will
satisfy the template requirements.
• Create request fails, but the service is still listed in the Service tab in “Reserved” state, and no
resources are allocated.
Unable to allocate servers and networks in the same Virtual Connect
Domain Group. Either more available servers are required, or could not
Failure message
match existing servers against memory size, disk space and processor
count requirements.
Reservation failed because:Possible cause
• There were insufficient suitable servers in the server pools referenced in the Create Request.
• One or more servers considered available for use were actually in the maintenance pool.
• At least one of the server blades in a referenced user server pool already has a profile assigned.
Action
• Verify that the Insight Orchestration server pools referenced in the Create Request contain sufficient
suitable servers taking into account all the server, storage and networking requirements of the
template.
• Check whether or not any servers were moved to the maintenance pool due to a previous
provisioning failure. Check for “clean-me” logical servers. If there are any, perform a manual
clean-up process. See “Manual clean-up process (physical)” (page 112).
• If these steps do not identify the issues, then verify that each server (blade only), that Insight
Orchestration considers free, does not have a Virtual Connect profile assigned to it. To do this,
identify each available (not “in use”) server blade in Insight Orchestration and do the following:
1. From Systems Insight Manager, select Tools→Integrated Console→Virtual Connect Enterprise
Manager (VCEM).
2. Select the Server Profiles tab, and unassign any profile associated with the server blade.
3. From the Virtualization Manager screen, select Tools→Logical Servers→Refresh to refresh HP
Insight Dynamics and activate your changes.
4. In the Insight Orchestration console Servers tab, click the circling green arrows icon (to the
left of: Click to refresh server resources) for changes to be detected.
Working with services 85