Highlighted
Contributor
Contributor

vMotion from NSX-T Overlay Segment to VMConAWS Overlay Segment

Hi,

can anyone explain me why it is not possible to vMotion from a local NSX-T Overlay segment to a VMConAWS Segment?

I get the following error message during vMotion:

"Currently connected network interface" 'Network adapter 1' cannot use network 'L2-Demo, (nsx.LogicalSwitch:5d8f634a-ece3-47ec-98df-0b5d2316794f)', because "the type of the destination network is not supported for vMotion based on the source network type".

BR Johannes

 

0 Kudos
3 Replies
Highlighted
VMware Employee
VMware Employee

Hi Johannes,

thank you for reaching out and for your question.

 

To get a better understanding of the issue, could you share a little more about your environment?
Like: what vSphere/NSX-T Versions are you running on-premises, what vHardware Version are you using, is HLM enabled, what kind of connection to the SDDC you are utilising, etc. 

It would be best if you could check the following doc in addition (or beforehand), to see if this may help you in finding a solution to your challenge:
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-DC377E35-... 

Please let me know if this might have helped you already, or if you'd need further assistance. Happy to help.

 

All the best & stay safe,

Rick

Rick Hoffmann
Cloud Customer Success Architect - VMware Cloud
VMware Inc.
http://cloudsuccess.blog
0 Kudos
Highlighted
Contributor
Contributor

Hi Rick,

here are details of our environment:

  • On-Prem: VCF 4.1 (vCenter 7U1, vSphere 7U1, NSX-T 3.0.2)
  • VMConAWS: SDDC version 1.12v2
  • VPN: L3 Policy-based
  • VM Hardware: v14
  • HLM with vCenter Cloud Gateway

vMotion works from a normal dvPortgroup to the VMConAWS Overlay without problems.
vMotion form VMConAWS Overlay to any local portgroup (NSX-T or standard Distributed) works as well.
Only vMotion from a local NSX-T Overlay to VMConAWS, the error message mentioned before appears.

I found the following in docs mentioned above: "Note: SDDCs configured with NSX-T do not support hot vMotion to or from on-premises VXLAN encapsulated networks (NSX for vSphere) or Geneve Datacenter Overlay networks (NSX-T)." 

The question is: what's the reason for that?

BR Johannes

0 Kudos
Highlighted
VMware Employee
VMware Employee

Thank you for your detailed response.

As you've found, there is no support for vmotion of a VM which resides on an encapsuled VXLAN/Geneve Network.
Unfortunately, I do not have an answer as of now, where these implications are derived from. 
I am in touch with the corresponding Product Management Team to get an answer, but due to the holiday season (in the US) I can't promise you an ETA.
Once I have an answer, I will certainly update you here.

However, you'd able to extend an NSX Overlay Network utilising HCX:
https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-0FD13F6B-67AC-4495-91C9-3CCD66791464.... 

If this has you interested, I'd also like to point you to the limitations page of HCX, as it also has some requirements:
https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-DBDB4D1B-60B6-4D16-936B-4AC632606909.... 

As stated above, I will update you as soon as I have more information on hand. 

Thanks again for reaching out,
Rick

Rick Hoffmann
Cloud Customer Success Architect - VMware Cloud
VMware Inc.
http://cloudsuccess.blog
0 Kudos