Operating Environment Software Instruction Manual

At least one OS or software deployment has failed
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 infrastructure 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” (page 197).
5. For a suspected 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” (page 200).
6. Perform a manual clean-up process for any affected logical server. See “Manual clean-up process
(physical)” (page 195).
To modify the Insight Control server deployment job:
1. Follow the steps 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 clean-up process for any affected logical server.
Provisioning request for service has paused
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
Timeout occurs while provisioning storage in a multi-disk request
Timeout occurred while provisioning storage.Failure message
Submitting a multi-disk request (for example, a logical server group with one server, one private
disk, and one shared disk) takes longer than expected and times out.
Possible cause
Action 1. In the infrastructure orchestration console Requests tab, delete the paused request.
2. Edit the timeout.generate.storage.entry property in the infrastructure orchestration
properties file in the default location at C:\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties.
3. Increase the default timeout from 25 minutes (1500 seconds) to 60 minutes (3600 seconds).
4. Edit the spm_timeout property in the logical server management properties file in the default
location at C:\Program Files\HP\Virtual Server Environment\conf\lsa\
lsa.properties.
Service creation 163