vMotion TCP/IP Stack

[ciscen]

Hi there,

Changing the IP address of the vMotion VMkernel adapter seems to cause migration failures when vMotion is configured to use the vMotion TCP/IP stack.

The only workaround I've found so far is to remove and re-add the vMotion VMkernel adapter.

Has anyone encountered this issue before? Are there any insights or recommended best practices to resolve this without performing the remove and re-add operation?

Thanks in advance for your help!

[mcity]

I noticed the same, with vMotion configured to use the vMotion TCP/IP stack, which is the default with VCF, you are not able to enable Unified Data Transport (UDT). The checkbox for provisioning is greyed out!

I am keen to see if there is a fix to this!

[ggathagan]

Mcity:

There are two ways to set up a vmkernel for vmotion.
If you choose the default TCP/IP stack. you can select multiple services, including vMotion.

If you set the tcp/ip stack to vMotion stack, all of the services choices are grayed out, since you're indicating that the vmkernel is to be used exclusively for vMotion.
The second is the preferred method.

Since UDT is not a selectable service with the default TCP/IP stack, that infers that the vmotion stack is configured to automatically include UDT.

Sadly, you cannot change the stack on a configured vmkernel, so if you've used method one, you'll have to create a new vmkernel.

[mcity]

Thank you for the detailed response.

The concern is the vmotion TCP/IP stack was setup like this by SDDC
Manager during VCF bring-up, and subsequent VI WLDs also default to the
same.
We don't want to change anything in vcenter that SDDC Manager won't
recognize

--
*The contents of this message and any attachment(s) are confidential,
proprietary to the City of Edmonton, and are intended only for the
addressed recipient. If you have received this in error, please disregard
the contents, inform the sender of the misdirection, and remove it from
your system. The copying, dissemination, or distribution of this message,
if misdirected, is strictly prohibited.*

[ggathagan]

ciscen

Just for clarification: when you change the IP address, is the new address in the same subnet as the old address?
How are the vmkernels on the other hosts configured?

After changing the IP address can you get results by running the following at a terminal session to the vmware host?
ping -c 4 -S vmotion <IP address of another host's vmotion vmkernel>

[ciscen]

Hi,

I changed the IP within the same subnet, so I didn't attempt a ping test since there was no change to any network configuration or layer -just vmotion is failing! I'll try disabling and re-enabling the VMK to see if that resolves the issue.

Again, this issue seems to occur only when vMotion is tied to the vMotion stack. If it's running within the default stack, changing the IP isn't a problem.

[vmotiontheinfo]

Hi @ciscen

If I understood your problem correctly, vMotion stopped working after changing the IP Address of the vMotion vmk.

Did you try to disable & re-enable vmk used for vMotion after changing the IP Address? You can use the below command for the same 

esxcli network ip interface set -i <vmknic> -e false -----> To disable
esxcli network ip interface set -i <vmknic> -e true -----> To enable

[mcity]

Can I run these commands on VCF environment?

One me more thing, we did not change anything on vmotion at all, that's how
SDDC Manager deployed it.

On Wed, Dec 18, 2024, 2:44 a.m. vmotiontheinfo via Broadcom <
[e-mail]> wrote:

> Hi @ciscen If I understood your problem correctly, vMotion stopped working
> after changing the IP Address of the vMotion vmk. Did you try to... -posted
> to the "ESXi" community
> [image: Broadcom] <https: community.broadcom.com>
> ESXi
> <https: community.broadcom.com vmware-cloud-foundation communities community-home digestviewer?communitykey=185ca20b-b56d-41b3-a4b8-aad095f0d970>
> Post New Message <[e-mail]>
> Re: vMotion TCP/IP Stack
> <https: community.broadcom.com vmware-cloud-foundation discussion vmotion-tcpip-stack#bm9d6974f4-e00b-4e33-96a0-0193d9237f8f>
> Reply to Group
> <[e-mail]?subject=re:+vmotion+tcp ip+stack> Reply
> to Sender
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions postreply?messagekey=9d6974f4-e00b-4e33-96a0-0193d9237f8f&ListKey=55c8b146-5ac3-4a1a-b108-018ed42b7ecc&SenderKey=a924912d-b9e1-4ffe-8e55-04b54d05a2ca>
> [image: vmotiontheinfo]
> <https: community.broadcom.com network members profile?userkey=a924912d-b9e1-4ffe-8e55-04b54d05a2ca>
> Dec 18, 2024 4:42 AM
> vmotiontheinfo
> <https: community.broadcom.com network members profile?userkey=a924912d-b9e1-4ffe-8e55-04b54d05a2ca>
>
> Hi @ciscen
> <https: community.broadcom.com vmware-cloud-foundation network members profile?userkey=9a8e1a79-9603-4c17-b007-27bca7da686c>
>
> If I understood your problem correctly, vMotion stopped working after
> changing the IP Address of the vMotion vmk.
>
> Did you try to disable & re-enable vmk used for vMotion after changing the
> IP Address? You can use the below command for the same
>
> esxcli network ip interface set -i <vmknic> -e false -----> To disable
> esxcli network ip interface set -i <vmknic> -e true -----> To enable
> *Reply to Group Online
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions postreply?messagekey=9d6974f4-e00b-4e33-96a0-0193d9237f8f&ListKey=55c8b146-5ac3-4a1a-b108-018ed42b7ecc>*
> *Reply to Group via Email
> <[e-mail]?subject=re:+vmotion+tcp ip+stack>*
> *View Thread
> <https: community.broadcom.com vmware-cloud-foundation discussion vmotion-tcpip-stack#bm9d6974f4-e00b-4e33-96a0-0193d9237f8f>*
> *Recommend
> <https: community.broadcom.com:443 vmware-cloud-foundation discussion vmotion-tcpip-stack?messagekey=9d6974f4-e00b-4e33-96a0-0193d9237f8f&cmd=rate&cmdarg=add#bm9d6974f4-e00b-4e33-96a0-0193d9237f8f>*
> *Forward
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions forwardmessages?messagekey=9d6974f4-e00b-4e33-96a0-0193d9237f8f&ListKey=55c8b146-5ac3-4a1a-b108-018ed42b7ecc>*
> *Flag as Inappropriate
> <https: community.broadcom.com vmware-cloud-foundation discussion vmotion-tcpip-stack?markappropriate=9d6974f4-e00b-4e33-96a0-0193d9237f8f#bm9d6974f4-e00b-4e33-96a0-0193d9237f8f>*
>
> -------------------------------------------
> Original Message:
> Sent: Dec 17, 2024 12:52 PM
> From: ciscen
> Subject: vMotion TCP/IP Stack
>
> Hi there,
>
> Changing the IP address of the vMotion VMkernel adapter seems to cause
> migration failures when vMotion is configured to use the vMotion TCP/IP
> stack.
>
> The only workaround I've found so far is to remove and re-add the vMotion
> VMkernel adapter.
>
> Has anyone encountered this issue before? Are there any insights or
> recommended best practices to resolve this without performing the remove
> and re-add operation?
>
> Thanks in advance for your help!
>
>
>
>
> You are receiving this notification because you followed the 'vMotion
> TCP/IP Stack' message thread. If you do not wish to follow this, please
> click here
> <https: community.broadcom.com higherlogic common unfollow.aspx?userkey=95980736-128a-431b-913e-131882c8d99c&sKey=KeyRemoved&ItemKey=2fea738e-6006-4f74-9e6c-0193d5bd097a>.
>
>
> Update your email preferences
> <https: community.broadcom.com go.aspx?c=Preferences§ion=email> to
> choose the types of email you receive
>
> Unsubscribe from all participation emails
> <https: community.broadcom.com higherlogic egroups unsubscribe.aspx?userkey=95980736-128a-431b-913e-131882c8d99c&sKey=KeyRemoved&mClass=Social>
>

--
*The contents of this message and any attachment(s) are confidential,
proprietary to the City of Edmonton, and are intended only for the
addressed recipient. If you have received this in error, please disregard
the contents, inform the sender of the misdirection, and remove it from
your system. The copying, dissemination, or distribution of this message,
if misdirected, is strictly prohibited.*

[vmotiontheinfo]

Apologies, I am not completely aware of this scenario when VCF is brought into the picture. My recommendation was generic regarding vMotion Technology.

[mcity]

Understood, thanks


--

Thanks,




[image: Edmonton_sig_RGB_S.jpg]

*Joseph Muchemi*

Server Solutions VMware Specialist - Storage and Virtualization

TECHNOLOGY INFRASTRUCTURE OPERATIONS

FINANCIAL AND CORPORATE SERVICES | OPEN CITY AND TECHNOLOGY



Phone: [phone] Cell

E-Mail: [e-mail]


City of Edmonton

19th Floor, Century Place

9803 - 102a Ave NW

Edmonton AB T5J 3A3

--
*The contents of this message and any attachment(s) are confidential,
proprietary to the City of Edmonton, and are intended only for the
addressed recipient. If you have received this in error, please disregard
the contents, inform the sender of the misdirection, and remove it from
your system. The copying, dissemination, or distribution of this message,
if misdirected, is strictly prohibited.*