HP Insight Control Server Provisioning 7.2 Online Help

12.24.2 Resolution
This is just a warning. The OS installation will continue and the message will be removed.
12.25 My deployed ESXi server is in maintenance mode
This is the expected behavior. Insight Control server provisioning does not have an agent for ESXi
systems, so when installation completes and the server enters production, there is no notification
to the appliance. The server status icon will always stay in maintenance mode and server properties
might not be reflected properly.
See “Handle an ESXi server once it’s deployed” (page 31) for additional information.
12.26 Jobs completed steps inconsistent with log
12.26.1 Symptom
For some jobs, the displayed number of completed steps might not match the number of steps in
the job log. When this issue occurs it is generally for jobs related to adding a server.
The steps Add iLO-managed Server and Registers IloManagerService might show up as a completed
steps when they actually failed.
12.26.2 Resolution
Look in the standard error log for a failed job to identify the steps that did not complete.
12.27 Resource not found error
12.27.1 Symptom
You might occasionally receive an error message stating a resource (job, server, script, etc.) was
not found.
12.27.2 Resolution
This might be a transient, benign error that can be resolved by selecting another resource and then
returning to your original resource, or refreshing the browser.
12.28 Matrix OE does not show OS Build Plans
12.28.1 Symptom
OS Build Plans do not appear in the Infrastructure Orchestration→software tab.
12.28.2 Possible cause checklist
1. Ensure the “OSType” and “archType” custom attributes have been set correctly on at least
one OS Build Plan as described in “Configure OS Build Plans for use in Matrix OE” (page 32).
2. On the CMS, ensure connectivity to Insight Control server provisioning by using the ping
command to the Deployment IP address.
3. On the CMS, ensure the mxnodesecurity command lists a dsc_sas protocol entry with
the correct MatrixUser user name and password as described in “Integrate with a previously
installed Matrix OE installation” (page 32), and that you are using the Deployment IP address
instead of the Appliance IP address.
4. On the CMS, copy the opswclient.jar to the HP SIM directory as described in “Integrate
with a previously installed Matrix OE installation” (page 32), then restart the HP Systems
Insight Manager service.
108 Troubleshooting index