topic Re: SimpliVity cross-cluster vMotion in HPE SimpliVity

SimpliVity cross-cluster vMotion

CadenLange — Wed, 04 Oct 2023 08:10:32 GMT

Are there any constriants with using VMware Storage vMotion (chaning both host and storage) to migrate a VM from one SimpliVity cluster to a different SimpliVity cluster within the same Federation.

Both clusters are running VMware 7.x on the hosts and the VMware licensing is in place to allow this. So from a VMware prespective it would work, just wanted to make sure there was nothing at a SimpliVity layer that would cause an error?

Although this is between two 2-node clusters, I'm 99% certain the 10Gbe networks are via a switch and not direct connect between nodes.

many thanks

Re: SimpliVity cross-cluster vMotion

Aditya_A — Tue, 26 Sep 2023 08:14:35 GMT

Hi,

One thing you need to ensure is which kernel adapter is set for vMotion.
By default, after deployment of SimpliVity nodes, vmk1 is set for vMotion which is the storage network. Storage network is non-routable as per the pre-requisites, hence can't be used for vMotion across clusters unless gateway is defined.

Hence, on source and target, you must disable vMotion on vmk1 and enable vMotion on vmk0 which uses the routable management network whenever cross-cluster vMotion is needed.

Once vMotion of the VM is complete, you can revert vMotion settings back to vmk1 so that vMotions within cluster happen over 10g and faster.

Moreover, you may take a look at SimpliVity Move feature embedded in plugin which moves a powered down VM to another SimpliVity cluster: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00131388en_us (page 71)

Re: SimpliVity cross-cluster vMotion

Aditya_A — Wed, 27 Sep 2023 07:57:16 GMT

Please let me know if you have further queries.