HP Insight Management 7.3 Installation and Configuration Guide

infrastructure orchestration Federated CMS is enabled by default during new installations, provided
that the domain name server is prepared.
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 work for each secondary
CMS. Verify that all DNS lookups can be resolved using the FQDN of each system.
For more information, and for instructions on enabling a federated CMS environment after an
upgrade to 7.3, see the HP Matrix Operating Environment Logical Server Management User Guide
at http://www.hp.com/go/matrixoe/docs.
NOTE: If you are upgrading both the operating system version running on the CMS and Insight
Management, ensure that the combination of OS version and IM version is supported throughout
the upgrade process. See the HP Insight Management 7.3 Support Matrix for supported operating
system and IM versions.
Consider two possible upgrade scenarios:
• The source operating system is supported by Insight Management 7.3. In this case, upgrade
Insight Management and then upgrade the operating system. For example, if you are upgrading
IM 6.3 to 7.3 and Windows 2008 to 2012, upgrade IM to 7.3, then upgrade the operating
system to Windows 2012.
• The source operating system or any other prerequisite (such as a database) is not supported
by IM 7.3. In this case you must perform intermediate upgrade cycles to reach the target state.
For example, if you are upgrading IM 6.3 to 7.3 and Windows 2003 to 2012, first upgrade
IM 6.3 to 7.0, then upgrade Windows 2003 to 2008, then upgrade IM 7.0 to 7.3, and
finally upgrade Windows 2008 to 2012. You may want to perform a data migration before
the final upgrade to ensure that the target CMS has a fresh operating system installation. See
the Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.3
system white paper for more information.
Support for a rolling upgrade of a CMS federation
To decrease federation downtime, Matrix infrastructure orchestration 7.3 includes support for a
rolling upgrade of a federated CMS environment. A rolling upgrade temporarily allows a federation
containing CMSs running different versions of Matrix OE during the upgrade process.
During a rolling upgrade, a CMS running Matrix infrastructure orchestration 7.3 supports basic
operations against a secondary CMS running 7.1. Not all 7.3 features are expected to work
against a 7.1 CMS. The following new features in 7.3 are not supported during a rolling upgrade:
• Changing the memory size or number of CPUs of an existing virtual machine.
• Attaching a physical disk (LUN) to a virtual server group.
• Some charge back operations, including detection of changes made outside of Matrix OE
(and directly in VMware, Hyper-V, OA, and so on).
IMPORTANT: The primary CMS has the most recent version of Matrix OE in the federation and
therefore must be upgraded first.
Requirements for CMS identification changes
If any of the following key attributes of the CMS operating system needs to be modified after Insight
Management has been installed, use the CMS Reconfigure tool.
The key attributes are:
• Hostname
• IP address associated with the hostname
Support for a rolling upgrade of a CMS federation 13