HP Matrix Operating Environment Software User Manual
Page 81
Task for logical server
OS or software deployment has failed. Check the deployment service to
diagnose the details.
Failure message
•
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.
Possible cause
To verify the LUN and/or server firmware:
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
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
to enter Fast!UTIL and reset the adapter defaults. For more information, see
6.
Perform a manual cleanup process for any affected logical server. See
.
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:
Details
Task
Wipe Disk
Run Script
Shutdown (if
available)
Power Control
2.
Perform a manual cleanup process for any affected logical server.
Action
Provisioning request for
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
job (ID = …) completed with a failure status. The deployment server does
not have the specified system UUID recorded. Deployment Service Connector
cannot confirm the system UUID provided by the caller.
Failure message
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
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
.
Action
Working with services
81