HP Matrix Operating Environment 7.3 Update 1 Release Notes

Logical server management
Logical server management runs on an x86/x64 Windows CMS.
Limitations
Restrictions on using cross-technology logical servers
Cross-technology logical servers can be moved between ProLiant server blades with
Virtual Connect to ESX and back, between Integrity server blades with Virtual Connect
and Integrity VM and back, and between servers with Virtual Connect with unlike
configurations. For more information, see the HP Matrix Operating Environment Logical
Server Management User Guide and the HP Matrix Operating Environment Recovery
Management User Guide at the Enterprise Information Library.
• Valid targets for activating or moving a cross-technology logical server:
ESX VM hosts◦
◦ HP Integrity VM hosts (racks and server blades)
◦ ProLiant c-Class servers with Virtual Connect
◦ HP Integrity servers with Virtual Connect
• Storage requirements:
SAN volume presented to an ESX VM host (RDM disk) that can be added to
a Virtual Connect profile.
◦
◦ One or more shared datastores on a SAN Array to store the HP Insight Control
virtual machine management configuration file and RDM mapping files [.vmdk]
on the ESX VM host. RDM mapping files can be on different SAN based
shared datastores. An iSCSI volume can be used for the HP Insight Control
virtual machine management configuration file, but not the RDM mapping file.
◦ Not supported: SPM catalog storage volumes.
In this release, catalog storage pool entries are supported with Virtual Connect
logical servers only. Catalog storage pool entries cannot be used with
37