VMotion Issue

[hbhungra]

Hi,

I'm facing issue related to VMotion for one of the node as live migration of VM from this node is not working but cold migration is working fine.

I have below setup with VSAN environment.

1.NODE1

2 NODE2

3 NODE3

4 NODE4

Migration of VM from Node1 to any node is not working but from other node to node 1 is working fine.

We are using distributed switch with 10 GB network throughput (TWO dvUPLINK)

Appreciate your quick support.

Regards,

Hakim. B

[TheBobkin · Accepted solution]

Hello Hakim,

Did vMotion from this host work previously or never worked/tested? What % does the process get to and what is the error message?

Does vMotion have it's own vmk and network (and only one tagged for vMotion)?

The times I have seen this (where it wasn't misconfigured from the start) have either been resolved by a dodgy cable being swapped out (you can test which if you have redundant links) or by removing and recreating the vmk interface on the problematic node.

Bob

[hbhungra]

Hi Bob,

Yes it was working fine before.

I have tried with that option like deleting and recreating vmk interface but it didnt work.

Regards,

Hakim.B

[TheBobkin]

Hello Hakim,

What error message it is failing with and when? e.g. when task is initiated or during progress.

Check the vpxa.log/vmkernel.log for more verbose messages related to this failure/inability.

Bob

[hbhungra]

Hi Bob,

Issue with one of the interface, VMotion is working fine after we disabled one of the interface.

Thanks a lot for your support.

Regards,

Hakim. B

[TheBobkin]

Hello Hakim,

Thanks for letting us know that resolved the issue and I am glad to hear my assumption was correct.

For anyone encountering this in future, a common error and/or logging message relating to this may indicate something along the lines of 'insufficient bandwidth' for the vMotion.

Bob