The network used

[dya]

Regarding VM migration and storage migration, which network is used for each? Management? Compute? Storage?

I asked because it didn't seem possible to specify where to use vMotion like in VMware.

※Apologies if this is unclear due to machine translation.

[CalvinZito]

@dya - asked internally and one of my experts said this: 
We use the management network at least for moving VMs, there’s no way to define a vMotion network like in VMware. As for storage migration flow, will try to check as I don't know. 

[dya]

Thanks for your reply.

I installed the Zabbix agent on the HVM host and verified it.

Regarding VM migration, the management network was indeed being used.
For storage migration, the storage network was being used.

The original configuration had one iSCSI device with Data Store A (GFS2). For this verification, we added another iSCSI device and created Data Store B (GFS2).
After adding the new device, we migrated the virtual machine's disk from Data Store A to Data Store B.

Please point out any errors.

Translated with DeepL.com (free version)

[Manuel Boosch]

In vmware in many scenarios i would prefer a 1Gb uplink for mgmt vSwitch and a 10Gb uplink for a vSwitch with vm traffic portgroups + vmkernel port for vMotion. vMotion migration time for VM's in VMWare depends on the size of the RAM that the virtual machine is using.

If VM migration in HPE VM Essentials is fixed to use the management network, the migration process can take a long time, especially for VMs with high RAM usage - if i use 1Gb uplinks for MGMT.

What is the recommended uplink speed for the management network in hpe vm essentials in this case ?

I guess MGMT & Storage network should be 10Gb then. 

[Arnout_Verbeken]

That's indeed a best practice.

But you won't need 2 dedicated nics for vMotion anymore so in the end, the NIC consumption is even less since you don't need your 2 1Gb mgmt NICs.