HP Matrix Operating Environment Federated CMS Overview

6
Figure 4: IO Multi site federated CMS solution architecture example
Environment configuration requirements
 A high speed, low-latency IP network connection between the primary and all secondary sites
 Maximum round-trip network latency of 200ms
 Minimum network bandwidth of 1 Gpbs
 Each data center must have a Matrix CMS installed and configured
 Each CMS instance, and its managed resources, including enclosures, physical servers and storage arrays, are co-
located in the same data center
 vCenter server: A vCenter server must be set up for each CMS with virtual managed resources
 SPEs: SPEs are defined in each CMS
 Deployment server: limited support for physical provisioning. The primary must have access to all deployment
servers in the federation which may be not allowed in a multisite environment.
Best practices
Upgrading a single CMS to an IO federated CMS environment
A single CMS can be upgraded to become a primary CMS after installation. This is the common case when the
infrastructure increasingly grows over time and nears maximum capacity of the existing Matrix Operating
Environment infrastructure. When the maximum capacity is approached and the expectation is for the growth to
continue, a federated environment can be planned and implemented. Ideally, when a single CMS reaches close to
2/3 of its maximum capacity (in 7.0, the maximum capacity is 2,500 managed nodes), the CMS is updated to
become a primary CMS and a secondary CMS is added to the federation.
Note: Once a CMS is part of a federation and has services deployed to it, that CMS cannot be broken out from the
federation and managed individually. In order to remove a CMS from the federation, all services that are provisioned