SME: vMotion Error

[SrVMwarer]

Hello VMwarers,

in a nutshell this my vMtion configurations on VDS and this is my error what shall I do

Note: this is on vCloud this is for learning purposes

[a_p_]

Only a guess. Did you already verify that no other VMkernel port group has vMotion (accidentally) enabled in its settings (e.g. the "Management Network")?

André

[SrVMwarer]

:smileylaugh: :smileygrin: :smileygrin: :smileygrin: :smileygrin: :smileygrin: :smileygrin: I can't imagine we've troubleshooted it for hours via cli, we've missed to enable the service from the beginning as we've changed some designs on the Lab.

another question regarding vMotion, we know that vpxd service that enables us managing hosts where's vMotion service configuration file?

Is it under /etc is it embedded or hidden or so ?

[a_p_]

.. where's vMotion service configuration file?

To be honest, I did never care about this. I can't even tell you whether there is one.

Btw. since you seem to have two dedicated vmnics per host for vMotion, why don't you configure "Multi-NIC vMotion"? It doubles the vMotion throughput at no cost.

See https://kb.vmware.com/s/article/2007467​ for how to configure this.

André

[NathanosBlightc]

another question regarding vMotion, we know that vpxd service that enables us managing hosts where's vMotion service configuration file?

Is it under /etc is it embedded or hidden or so ?

Not vpxd (daemon), There is vpxa in this path: /etc/init.d/ to stop, start, check status and restart the service.

I don't think there is a config file about vMotion because it's part of VMKernel services itself and you just need to enable vMotion for at least one of VMKernel ports (if you have multiple on each host) after migrating from VSS to VDS. Just check dedicated subnet for vMkernal (with vMotion enabled) is configured correctly and your hosts can observe each other in the network to do migration tasks.