Hello,
According to the following statement. all the VTEP's should have the same VLAN ID, even if they are in different subnets, why ? I remeber the VLAN ID can be different...
To add to Sreecs reply, if you have a single vSphere cluster spanned across multiple racks, the same VLAN has to be used. Currently in NSX-v, you cannot configure different VLAN IDs for different ESXi hosts in the same cluster.
For example, this means that a vSphere cluster stretched over 2 or more locations has to use the same VLAN ID. In that case I always use DHCP instead of IP Pools for the VTEP IP addresses and let different DHCP zones land on the different locations, so that the ESXi VTEPs get different IP subnets on a different location and so that the VXLAN transport VLAN doesn't have to be stretched.
If you go via design document it for simplicity sake we are following that practice. That doesn't mean you can have different vlan for VTEP which are part of same DVS,they all should be same. Ideally in cross VC - VTEP will be part of different VLAN for each sites.
To add to Sreecs reply, if you have a single vSphere cluster spanned across multiple racks, the same VLAN has to be used. Currently in NSX-v, you cannot configure different VLAN IDs for different ESXi hosts in the same cluster.
For example, this means that a vSphere cluster stretched over 2 or more locations has to use the same VLAN ID. In that case I always use DHCP instead of IP Pools for the VTEP IP addresses and let different DHCP zones land on the different locations, so that the ESXi VTEPs get different IP subnets on a different location and so that the VXLAN transport VLAN doesn't have to be stretched.
Understand. Thanks.
I just ran in to this. Network guys and I used different VXLAN VLAN IDs at each site, guess we will be changing one of them tomorrow so they match!