HP Insight Orchestration 6.3 User Guide

Configuring a federated CMS environment
An Insight Orchestration federated CMS environment is one where multiple management servers
cooperatively share the responsibility for managing a larger number of resources than can be
managed by a single server.
An Insight Orchestration federated CMS environment:
• allows up to four times increased scalability for service catalog-based auto-provisioning (up
to 6000 virtual machines), over the current single-CMS limitation of 1500 managed virtual
machines
• contains one primary CMS running Insight Orchestration, and one or more secondary CMSs
running Insight Dynamics (Insight Orchestration cannot be installed on secondary CMSs)
The primary CMS manages the aggregated resources of all CMSs. Insight Orchestration must be
installed only on this server. A secondary CMS is a CMS that participates in the federation, where
resources exist and provisioning from Insight Orchestration may occur, but Insight Orchestration
does not run directly on secondary CMSs.
To execute Insight Orchestration provisioning across multiple CMSs, Insight Orchestration on the
primary CMS uses the secondary CMSs logical server management, VMM (virtual machine
management), and other supporting software layers.
For more information, see the HP Matrix Operating Environment Federated CMS Overview white
paper at HP Insight Dynamics Information Library.
Manually enabling federated CMS in new installations
Federated CMS is enabled by default in new installations. However, during the installation
procedure, if the CMS IP address is not resolved to the Fully Qualified Domain Name (FQDN),
one of the following errors is displayed:
Failed to enable HP Insight Orchestration Federated mode.
HP Matrix OE infrastructure orchestration was successfully installed but the federated CMS feature was not
enabled.
If you performed a new installation of Insight Software 6.3, and federated CMS was not successfully
enabled during the installation, perform the following steps to configure a federated CMS
environment.
WARNING! Do not manually enable federated CMS if you are upgrading to Insight Software
6.3 from an earlier release. If your environment contains existing Insight Orchestration services,
enabling federated CMS after an upgrade will cause existing services to fail.
Contact HP for information about enabling federated CMS after an upgrade to 6.3.
1. Set up and verify DNS on primary CMS and secondary CMSs
In a federated environment, Domain Name Service (DNS) is used to resolve CMS hostnames
to IP addresses.
• On the primary CMS, forward and reverse DNS lookups must resolve for each secondary
CMS using the FQDN of each system.
• If the primary CMS is configured with a static IP address, the DNS suffix must be configured
in the hostname.
a. On a Windows system, edit Computer Properties (Change Settings)
b. Change the Computer Name
c. Click the More button
d. Include the primary DNS suffix
By default, the primary DNS suffix of a computer's FQDN is the same as the Active
Directory domain to which the computer is joined.
e. Save and restart the machine.
Configuring a federated CMS environment 11