HP Matrix Operating Environment 7.0 Release Notes

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 Matrix
OE 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
• ESX storage requirements:
SAN volume presented to an ESX VM Host (RDM disk) that can be added to a Virtual
Connect profile
◦
◦ One datastore shared on a SAN or iSCSI volume (to store the Insight Control virtual
machine management configuration file and RDM mapping file [.vmdk] on the ESX VM
Host)
Not supported: SPM (catalog) storage volumes
In this release, catalog storage pool entries are supported on servers with Virtual Connect
logical servers only. Catalog storage pool entries cannot be used with cross-technology
logical servers that may be activated on an ESX or Integrity VM Host.
• Integrity VM storage requirements:
◦ SAN-based logical server storage is supported, including storage pool entries. File based
storage is not supported with Integrity VM cross-technology logical servers.
NOTE: SAN volumes used for Integrity VM cross-technology logical servers should not
be presented to the Integrity VM Host.
• ESX network requirements:
◦ Single or multiple networks (limited to 4 by ESX)
Not supported: VLAN networks
• Integrity VM network requirements:
◦ Single or multiple networks
Not supported: VLAN networks and Auto-Port Aggregation Link Aggregation configurations
Performing operations on a logical server running as a VM Host
Before performing any operations on a physical server running as a VM Host, make sure that all
jobs related to controlling the VM guests running on the VM Host logical server have been
completed. (A warning message is displayed only when you attempt to deactivate or delete virtual
machines registered with Insight Control virtual machine management.)
28 Issues and suggested actions