NSX vCloud Retrofit: Overlapping Networks in vCD with NSX Virtual Wires

Part 4: vCloud Director Overlapping Networks:

vCloud Director has the ability to allow Overlapping Network segments configurable from the Administration Tab of the vCD UI. Traditionally for those using VLAN backed External Networks and Network Pools this would represent a potential risk to clients if admins where not careful provisioning network resources. If the same VLAN was mistakenly configured there could be the possibility for client networks to see each other meaning a really bad day for providers of multi-tenancy platforms.

Where this is required is when VXLAN is in play…The VXLAN Transport network is configured on the one VLAN which then carries all the Logical Switch Network Segments or VNI’s. Even though vCD is not aware of NSX you can still connect up Virtual Datacenter vApps and VMs to NSX Edge Gateways via VXLAN virtual wires. To achieve that you need to check the Allow Overlapping External Networks box as shown below.

If this isn’t Checked you will get the following error in the vCD UI

With Overlapping Networks in place your network pools are also able to be VXLAN backed and used in conjunction with retrofitted External Networks connected to NSX Edges for advanced Edge Gateway Services.

Bonus Tip: vCloud Director filters certain PortGroups based on their name of which NSX Created Virtual Wire Portgroups are one of those filtered. To have an NSX Virtual Wire appear in the vCD UI you need to rename the PortGroup similar to what’s shown below.

 

This blog series extends my NSX Bytes Blog Posts to include a more detailed look at how to deploy NSX 6.1.x into an existing vCloud Director Environment. Initially we will be working with vCD 5.5.x which is the non SP Fork of vCD, but as soon as an upgrade path for 5.5.2 -> 5.6.x is released I’ll be including the NSX related improvements in that release.

2 comments

  • Hi Anthony,

    Re. renaming the port group, is this officially documented ? Though it never was recommended to modify entities from vCenter that are managed externally (vCNS or NSX Manager). I guess that’s just a label whereas NSX Manager is grabbing the object id via APIs or something like that?

  • Hello Anthony,
    great piece of information. VMware’s own KB, and the info in VCD GUI, are a bit misleading on this functionality.

    Thanks, Emanuele.

Leave a Reply