HP Matrix Operating Environment 7.1 Release Notes

The example below shows capupgrade being run on a CMS with 20 servers.
C:\Program Files\HP\Virtual Server Environment\bin>capupgrade
==> For more information, please refer to
"C:\Program Files\HP\Virtual Server Environment\logs\capupgrade.log"
The Performance Index upgrade can take up to 3 minutes.
During this time, the HP Capacity Advisor Data Service
will be offline and data collection will be stopped.
The service will restart automatically at the end of the
capupgrade process.
Do you want to continue? [y\n] y
Progress: 1/20
Progress: 2/20
Progress: 3/20
Progress: 4/20
Progress: 5/20
...
NOTE: The capacity planning scenario editor will display a reminder message until capupgrade
is run.
Support for a rolling upgrade of a CMS federation
To decrease federation downtime, Matrix OE infrastructure orchestration 7.1 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.
IMPORTANT: The primary CMS must be upgraded first.
During a rolling upgrade, a CMS running Matrix OE 7.1 supports basic operations against a
secondary CMS running 7.0. Not all 7.1 features are expected to work against a 7.0 CMS.
The following operations are not supported on a primary CMS running Matrix OE 7.1 with
secondary CMSs running 7.0:
• Manual operating system provisioning of VM guests using resources discovered on a secondary
CMS
• Provisioning a physical server group with auto-provisioned SPM volumes on a secondary CMS
• Changing the memory size or number of CPUs of an existing virtual machine
• Some chargeback operations, including detection of changes made outside of Matrix OE
(and directly in VMware, Hyper-V, OA, and so on)
Hyper-V VM hosts are moved to the IO unassigned pool after upgrade from 6.3
After an upgrade from Matrix OE 6.3 to 7.1, all Hyper-V VM hosts are automatically moved to
the infrastructure orchestration Unassigned server pool. This issue does not occur after an upgrade
from Matrix OE 7.0 to 7.1.
Manually move the Hyper-V VM hosts back to their original server pool in order to provision virtual
servers to Hyper-V VM hosts.
Deactivated logical servers are powered off after upgrade from 6.0 and 6.1
A Matrix OE infrastructure orchestration service that is deactivated before an upgrade from Matrix
OE 6.2 or higher to 7.1 will contain logical servers that remain deactivated after the upgrade.
Their state is not changed.
However, service that is deactivated before an upgrade from Matrix OE 6.0 or 6.1 to 7.1 will
contain logical servers that are powered off after the upgrade. This changes the state of the logical
server from paused to powered off.
10 Description