About the segment for creating VTEP

[networlddsg]

Hello

VTEP is recognized with no problem even if it is created in the same segment as ESXi managed vmkernel.

Is it correct?

◆ Reasons to check

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/nsx/vmw-nsx-network-virtu...

120 pages

VXLAN / VTEP and Management are created in different segments.

Is this only recommended?

Is it OK to create VXLAN / VTEP and Management in the same segment?

[Sreec · Accepted solution]

Traffic segregation is a key point in any network design. VTEP&Management subnet can be same,but not at all a good approach in enterprise network design. Ideally in any vSphere network design Management,vMotion,Storage(IP) etc will be on unique VLAN and with NSX VXLAN traffic we should continue to stick with same approach . In this below example respective ESXI traffic & VXLAN is trunked and connected to unique SVI . Also remember VXLAN tcp stack is different from any other stack,so using a unique gateway for VXLAN is totally supported.

[amolnjadhav]

> Is this only recommended?

Yes, Do separate out Management and vTEP Traffic.

>Is it OK to create VXLAN / VTEP and Management in the same segment?

As Sree mentioned in previous comment it is not good practice to have VTEP/Management network in same network.

Configuration will work fine if vtep/ESX Management is in same network.

[networlddsg]

Thankyou!

[networlddsg]

Thankyou!