HP Matrix Operating Environment Software - Manual (Page 191)

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 host names 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. For more information, see
“Configuring a federated CMS
environment” (page 24) and the HP Matrix Operating Environment Federated CMS Overview
white paper at the following website:
http://www.hp.com/go/matrixoe/docs
Error retrieving images from Ignite-UX deployment server
When using infrastructure orchestration in a federated environment to deploy to an Ignite-UX server
on the primary CMS, the images do not appear from the deployment server. Issue
The Ignite-UX server has not been discovered on the primary CMS. Possible cause
Discover the Ignite-UX server within HP Systems Insight Manager on the primary CMS before
deploying the server. Action
For more information, see “Discovering the Ignite-UX deployment server” (page 41) .
Verifying the CMS configuration 191