Operating Environment Software Owner's manual

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 cleanup process. See
“Manual clean-up process”.
• 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→VSE Management→Virtual Connect Enterprise
Manager (VCEM)→VCEM Homepage.
2. Select the Profiles tab, and unassign any profile associated with the server blade.
3. From the Insight Dynamics Management 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.
Task for logical server <logical server name> …. Failure: At least one OS or
software deployment has failed. Check the deployment service to diagnose the
details.
Failure message
Possible cause
• Problem with a LUN allocated to server or firmware issue on server
• Insight Control server deployment Erase ProLiant ML/DL/BL Array Configuration {LinuxPE}
job has not been modified for Insight Orchestration.
To verify the LUN and/or server firmware:Action
1. Use Remote desktop and log into the server deployment server.
2. Verify that the server deployment console for the enclosure bay for the logical server XYZ. The message
should state RDeploy: The disk was not found.
3. From the request messages, identify the LUN that has been allocated to the logical server.
4. If the message indicates a possible server WWN issue with the LUN, see “Configuring storage pool entries,
FC zones, and disk array presentations”.
5. If you suspect a firmware error, use iLO to observe the progress of booting the server. If the message WARNING
Adapter NVRAM contains invalid data displays, press <ALT-Q> to enter Fast!UTIL and reset the
adapter defaults. For more information, see “Correcting a checksum error”.
6. Perform a manual cleanup process for any affected logical server. See “Manual clean-up process”.
To modify the Insight Control server deployment job:
1. Follow Step 9 in the Creating server deployment job folders procedure. The job must have only two steps:
DetailsTask
Wipe DiskRun Script
Shutdown (if
available)
Power Control
2. Perform a manual cleanup process for any affected logical server. See “Manual clean-up process”.
Provisioning request for <service_id> has paused. Manual data disk allocation is
required.
Failure message
This error indicates that insufficient LUNs exist to provision the service.Possible cause
Create the LUNS and continue provisioning.Action
Task for logical server <logical_server_id> has failed. Logical server job (ID
= …) completed with a failure status. The deployment server does not have the
Failure message
specified system UUID recorded. Deployment Service Connector cannot confirm the
system UUID provided by the caller.
The deployment server cannot bootstrap the server. This issue can occur if the LUN attached to the server already
has an OS deployed to it such that the server is booting from the presented LUN rather than booting into the
designated deployment server.
Possible cause
Action 1. Locate the Provisioning logical server message which identifies the server blade in use.
2. Perform a manual cleanup process for any affected logical server. See “Manual clean-up process”.
Working with services 63