Insight Dynamics 6.1 Release Notes

ProLiant c-Class Servers with Virtual Connect—
— ESX Hosts: 3.5, 3.5i, 4.0, and 4.0i
• Storage:
— One SAN-based storage volume (ESX refers to this as an RDM volume)
— Data store on SAN, SAS, iSCSI (VM host location for VM configuration files)
— Not supported: Redundancy of RDM volumes
— Not supported: Shared RDM volumes
— Not supported: SPM-based storage volumes
• Network: One network connection
Performing operations on a logical server running as a VM host
HP Insight Dynamics supports a logical server that is a physical server (including logical servers
on Virtual Connect whose storage is configured to use a local disk, and logical servers on non-HP
physical servers) running a VM host, and supports logical servers that are guest VMs on that
physical server. In order to protect the VM guests from inadvertent operations, a logical server
that is a physical server running as a VM host has the following restrictions:
• Deactivate, move, power off, and delete operations on the VM host logical server are not
supported while there are guest VM logical servers residing on the VM host logical server.
You must move the guest VM logical servers off of the VM host logical server before
performing any of these operations on the VM host logical server.
• Deactivate, move, power off, and delete operations on the VM host logical server are not
supported while there are running jobs on a VM guest logical server or on the VM host
logical server that could result in creating or leaving a VM guest logical server on the VM
host logical server.
Managing a CMS as a logical server is not supported
HP strongly recommends that systems running Central Management Server (CMS) software not
be managed as logical servers. This includes the Insight Dynamics CMS, as well as any other
CMS managed by the Insight Dynamics CMS.
Note that logical server management does not prevent you from managing a CMS as a logical
server. For example, Insight Dynamics will allow any managed node, including the CMS, to be
selected for moving or other logical server operations; doing so may result in unpredictable
results.
Hyper-V cluster shared volume created with GPT disk partitioning system is not supported
If you attempt to move a Hyper-V virtual machine logical server to a Hyper-V VM host that is
configured with cluster shared volume (CSV) storage with a GUID partition table (GPT) disk
partitioning system, the target host is rejected with the error:
VM Host was filtered out because the data storage of logical server
logical-server-name does not match the available storage on VM Host hyper-v-vm-host-name.
Suggested action Recreate the CSV using master boot record (MBR) storage. GPT disks are
required only if you need volumes that exceed 2TB.
Moving a logical server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host is not supported
A limitation from Microsoft prevents you from moving or reactivating a virtual machine logical
server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host. An error message is displayed
if you attempt the operation.
You can move or reactivate a virtual machine logical server from a Hyper-V R1 host to a Hyper-V
R2 host.
28 Issues and suggested actions