HP Matrix Operating Environment Software - Manual (Page 162)

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 19)
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
match existing servers against memory size, disk space and processor
count requirements.
Reservation failed because: Possible cause
•
There were insufficient suitable servers in the server pools referenced in the Create Request.
• One or more servers considered available for use were actually in the maintenance pool.
•
At least one of the server blades in a referenced user server pool already has a profile assigned.
Action • Verify that the infrastructure orchestration server pools referenced in the Create Request contain
sufficient suitable servers taking into account all the server, storage and networking requirements
of the template.
•
Check whether or not any servers were moved to the maintenance pool due to a previous
provisioning failure. Check for “clean-me” logical servers. If there are any, perform a manual
clean-up process. See
“Manual clean-up process (physical)” (page 195) .
•
If these steps do not identify the issues, then verify that each server (blade only), that infrastructure
orchestration considers free, does not have a Virtual Connect profile assigned to it. To do this,
identify each available (not “in use”) server blade in infrastructure orchestration and do the
following:
1. From Systems Insight Manager, select Tools
→Integrated Console→Virtual Connect Enterprise
Manager.
2. Select the Server Profiles tab, and unassign any profile associated with the server blade.
3. From the Matrix OE visualization screen, select Tools
→Logical Servers→Refresh to refresh
Matrix OE and activate the changes.
4. In the infrastructure orchestration console Servers tab, click the circling green arrows icon (to
the left of: Click to refresh server resources) for changes to be detected.
162 Troubleshooting