HP Insight Orchestration 6.3 User Guide

• WARN—A configuration problem was found. The problem will not necessarily prevent correct
operation, but it may limit or restrict operation of some features.
• N/A—Not Applicable: the check does not apply to this type of system.
IOAssist execution timeout
The default timeout value for each IOAssist check is two minutes. A timeout indicates that the verified
component (Insight Orchestration, its subsystem or partner) either is not responding or is unavailable,
or is responding in an undesirable response time.
If IOAssist times out, you can only assume that the component is not responding in the expected
response time. You cannot assume that the component is unavailable. Any other conclusion is
indicated by IOAssist error messages.
Error enabling federated CMS during installation
A federated CMS environment contains one primary CMS running Insight Orchestration, and one
or more secondary CMSs running Insight Dynamics.
Insight Orchestration federated CMS is enabled by default during new installations. At the end of
a new installation, the Insight Software installer displays:
Issue
“Failed to enable HP Insight Orchestration Federated mode.”
The CMS IP address cannot be correctly resolved to the CMS FQDN during installation, so the
Installer adds the CMS IP address to the managed_cms_list property. However, the
managed_cms_list must be configured with the CMS FQDN.
Possible cause
In a federated CMS environment, forward DNS lookups resolve CMS hostnames to IP addresses.
Additionally, on the primary CMS, forward and reverse DNS lookups must work for each secondary
CMS.
Action
1. Verify that all DNS lookups can be resolved using the FQDN of each system.
2. Enable federated CMS manually. See “Manually enabling federated CMS in new installations”
(page 11).
See the HP Matrix Operating Environment Federated CMS Overview white paper at HP Insight
Dynamics Information Library for detailed information.
Working with services
Service creation
Physical service creation
Troubleshooting items addressed in this section:
• Unable to allocate servers and networks in the same Virtual Connect Domain Group. Either
more available servers are required, or could not match existing servers against memory size,
disk space and processor count requirements.
• Task for logical server <logical server name> …. Failure: At least one OS or software
deployment has failed.
• Provisioning request for <service_id> has paused. Manual data disk allocation is required.
• 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 specified system UUID recorded.
Deployment Service Connector cannot confirm the system UUID provided by the caller.
• Task for logical server <logical_server_id> has failed. Job <job_id> has exceeded its timeout
value of <nnn> minutes. Marking the job as failed.
• Multiple messages: Could not find server with serial number <serial_number>. Or: Task for
logical server <logical_server_id> has failed. Logical server job <job_id> completed with a
84 Troubleshooting