VMware Networking Community
Dongjianhua
Enthusiast
Enthusiast
Jump to solution

Two questions about NSX&VXLAN

1. Can I use the same IP subnet for both esxi management network(vmk0) and VXLAN VTEP? Or should them use different subnet?

2. Is it possible to configure the vmotion&FT vmkernel port to the vxlan logical switch ? So I can do vmotion&FT over the L3 network ?

0 Kudos
1 Solution

Accepted Solutions
bayupw
Leadership
Leadership
Jump to solution

1. Technically you can and I would say it is fine for lab setup.

If you don't have any VLAN, you can just put "0" and VXLAN will pass along untagged traffic.

Just like the VMware Hands On Lab as below

vxlan.png

On production environment, it is recommended to separate them as per NSX Design Guide VMware® NSX for vSphere Network Virtualization Design Guide ver 3.0

nsx-vlans.PNG

2. I can't find the documentation but last time VMware does not support vMotion over VXLAN http://www.yellow-bricks.com/2013/01/29/vmotion-over-vxlan-is-it-supported/

If you need vMotion over L3, this can be achieved without VXLAN.

Per vSphere 6.0, vMotion traffic is fully supported over an L3 network. You just need to put the vMotion vmkernels on the vMotion TCP/IP stack and assign a dedicated default gateway (which can be different with ESXi management network default gateway).

On vSphere 5.5, you can use static routing but you would need go through the RPQ process and allow VMware validate designs on a case-by-case basis so it can be supported by VMware.

Not sure about FT over L3 network. but please note that FT requires minimum 1Gbps logging network and probably more bandwidth in vSphere 6.

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw

View solution in original post

0 Kudos
2 Replies
bayupw
Leadership
Leadership
Jump to solution

1. Technically you can and I would say it is fine for lab setup.

If you don't have any VLAN, you can just put "0" and VXLAN will pass along untagged traffic.

Just like the VMware Hands On Lab as below

vxlan.png

On production environment, it is recommended to separate them as per NSX Design Guide VMware® NSX for vSphere Network Virtualization Design Guide ver 3.0

nsx-vlans.PNG

2. I can't find the documentation but last time VMware does not support vMotion over VXLAN http://www.yellow-bricks.com/2013/01/29/vmotion-over-vxlan-is-it-supported/

If you need vMotion over L3, this can be achieved without VXLAN.

Per vSphere 6.0, vMotion traffic is fully supported over an L3 network. You just need to put the vMotion vmkernels on the vMotion TCP/IP stack and assign a dedicated default gateway (which can be different with ESXi management network default gateway).

On vSphere 5.5, you can use static routing but you would need go through the RPQ process and allow VMware validate designs on a case-by-case basis so it can be supported by VMware.

Not sure about FT over L3 network. but please note that FT requires minimum 1Gbps logging network and probably more bandwidth in vSphere 6.

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
0 Kudos
Dongjianhua
Enthusiast
Enthusiast
Jump to solution

Thanks.

0 Kudos