HP Matrix Operating Environment Software - Manual (Page 150)

•
FAIL—A serious configuration problem was found, which must be resolved for correct operation.
•
WARN—A configuration problem was found. The problem may 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
A check in ioassist failed to communicate with infrastructure orchestration, generating a
TimeoutException. Issue
There was a delay in virtual machine management responding with VM Host details.
The default timeout value for each IOAssist check is two minutes. A timeout indicates that the verified
component (infrastructure orchestration, its subsystem or partner) either is not responding or is
unavailable, or is responding in an undesirable response time. Possible cause
If IOAssist times out, assume that the component is not responding in the expected response time.
Do not assume that the component is unavailable. Any other conclusion is indicated by IOAssist
error messages.
Choose one of the following: Action
•
In ..\Program Files\HP\Matrix infrastructure orchestration\conf\
ioassist.properties
, set timeout.await to a value greater than 120 seconds.
•
In a Windows Command Prompt, execute the ioassist command line.
Manually enabling federated CMS
A federated CMS environment contains one primary CMS running infrastructure orchestration, and
one or more secondary CMSs running Matrix OE.
Matrix infrastructure orchestration federated CMS is enabled by default during new installations.
At the end of a new installation, the Insight Management installer displays: Issue
Warning — HP Matrix infrastructure orchestration was successfully installed but the federated CMS
feature was not enabled. Refer to the HP Matrix infrastructure orchestration User Guide for information
about how to enable federated CMS.
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 resolve 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 “Configuring a federated CMS environment” (page 18)
and the HP Matrix Operating Environment Federated CMS Overview white paper at Matrix
Operating Environment Information Library for detailed information.
Service creation
Physical service creation
Unable to allocate servers and networks in the same Virtual Connect Domain Group
Unable to allocate servers and networks in the same Virtual Connect
Domain Group. Either more available servers are required, or could not
Failure message
150 Troubleshooting