HP Matrix Operating Environment Software User Manual
Page 82
Task for logical server
failed.
Failure message
•
Server blade firmware.
•
Errors in storage presentation, multipath or zoning configuration, or failed components.
•
Timeout value for create logical server request is too short
Additional possible causes if using the Insight Control deployment server.
•
Insight Control server deployment has been reconfigured in a way that has modified the default
PXE boot sequence so that it no longer works with Insight Orchestration
•
Issue with server deployment ProLiant Support Pack (PSP).
Possible cause
Review the job status on the deployment server and investigate any issues discovered there.
•
If using the Insight Control deployment server, review the job status by:
1.
Locate the Provisioning logical server message which identifies the server blade
in use.
2.
Use Remote desktop and log into the server deployment server.
3.
Locate the server blade in the Computers pane of the server deployment console. Review
the job status in the details pane.
4.
If the “in progress” icon is shown against the last task, right-click and select Properties
to display the Job Schedule information.
5.
If the current status is shown as Executing file: "hpsum.exe", verify that server
deployment has the latest ProLiant Support Pack in the appropriate ..\Altiris\
eXpress\Deployment Server\lib\software\
folder. Also check for any customer
advisories pertaining to the drivers in the ProLiant Support Pack. In particular see
•
If using Ignite-UX as the deployment server, review the status of the client by executing this
command on the Ignite-UX server:
/opt/ignite/bin/ignite client list –m xml –l status
Check the Ignite-UX client’s install log in the file:
/var/opt/ignite/clients/
•
For HP Server Automation, review the job status:
1.
Log into the HP Server Automation Client.
2.
Check for “Run OS Sequence” jobs in the Jobs & Sessions section.
3.
Click on the job and examine the details.
•
These issues can also indicate a possible firmware issue with the server. See
•
Contact your storage administrator to ensure that your storage presentation, zoning, operating
system distribution, and drivers all support multipath SAN environments
•
To set the timeout value, see
“Modifying the logical server timeout value”
.
•
Whatever the cause, always check whether or not there are any “clean-me” logical servers. If
so, perform a manual cleanup process. See
Action
82
Troubleshooting