HP Matrix Operating Environment 7.3 Update 1 Release Notes

If this error message appears, the HAProxy configuration file is too big and the
infrastructure orchestration/OO Load Balancer workflows are not able to process this
request. To create many services that use this load balancer, HP recommends that you
use the F5 BIG-IP Load Balancer. For more information, see the F5 - BIG-IP Local Traffic
Manager website at http://h17007.www1.hp.com/one/alliance/f5/big-ip.htm?
jumpid=reg_r1002_usen_c-001_title_r0001.
Migrating from one CMS to another using Operations Orchestration
If you are using Matrix with Operations Orchestration (OO) workflows, you may
experience workflow failures after migrating from one CMS to another CMS. These
failures have two sets of possible causes and actions:
1. Duplication of values
The Run ID values from one CMS are not migrated via the DMT (Data Migration
Tool) when moving from one CMS to another. The new CMS will start the values
over rather than resuming from a previous value, resulting in duplicate values.
Suggested action
Run the SQL script provided in the Data Migration of an Existing Microsoft Windows
CMS to a New Insight Management 7.3 System white paper available at Enterprise
Information Library.
2. Lack of necessary information
The logic of the OO workflow is dependent on remote information or some state
information that is not available or appropriate on the new CMS. If you are using
the Custom Hostnames feature, for example, and have modified the sample OO
workflows to support your specific server naming strategy, the migration tool will
not handle workflow-customized server-naming strategies. If your workflow stored
state information on the CMS, it was probably not migrated to the new CMS.
Suggested action
Modify the OO workflows on the new CMS as appropriate. You must ensure that
the workflows and any external resources are manually updated to run properly
on the new CMS (for example, to provide necessary connectivity information to a
remote server with a database of custom hostnames, or to provide suitable state
information based on previous work done on the prior CMS). For more information,
see the Data Migration of an Existing Microsoft Windows CMS to a New Insight
Management 7.3 System white paper available at Enterprise Information Library.
VM disks using different datastores
Designer allows boot and data disks connected to Virtual Server Groups to use different
"storage volume names". This feature allows VM boot and data disks to be allocated
to different storage volumes with the following limitations:
NOTE: VM logical servers manually created from Matrix OE visualization can also
specify VM disks on different data stores.
• Integrity VM disks must all use the same storage volume names, or be blank.
• Cloud server disks do not support storage volume names and must be blank.
• Hyper-V VM Linked Clone disks must have the same storage volume names, or be
blank. They cannot be spread across different datastores.
• Microsoft does not support VM Linked Clone using multiple data stores.
22