VMware Cloud Community
AcuteSys
Contributor
Contributor

vCloud Director 8.20 and NSX 6.3.0 - Create Org Network Fails

I have a newly deployed instance of vCD 8.20 and NSX 6.3.0. Everything on the surface looks OK, however I am not seeing any network port groups being created on the DVS.

When I create a Org Network I am getting the following error:

[ bc3f151b-14ba-4985-80d3-dfcc7717e10a ] Cannot deploy organization VDC network  (39980b71-9ff1-4ea0-8b27-60174bd2855b)

com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- Unable to allocate an available resource for resource type Universal Multicast Address Pool., error code 844

When I check the Network Pools - the VXLAN network is GREEN check. vCenter status is GREEN check and I have tried re-entering the user and password for "vShield Manager" even thou we are using NSX. It connects fine it seems. All the Hosts in the host view are GREEN and vCD Agent is deployed.

NSX Manager config looks good, Lookup service and vCenter registration are fine. And I can deploy edges and create networks via vCenter, just appears to be anything from vCD to NSX is no go.

Anybody have any ideas, or suggestions on where I should be looking?

Thanks!

5 Replies
AcuteSys
Contributor
Contributor

Update I tested deploying an edge gateway via vCD and that works, however if I try creating any sort of "Isolated or Routed" org networks it fails.

0 Kudos
Sreec
VMware Employee
VMware Employee

Transport zones created by vCloud Director is set for Multicast mode Replication.The transport zones created for each pVDC must be changed from multicast mode to unicast or hybrid( NSX controllers should be deployed and their status should be green) and ensure we are selecting right network pool for org-vdc

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 7x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
bayupw
Leadership
Leadership

If you would like to use VXLAN, there are a few things to check

- Make sure vSphere cluster is prepared/installed for NSX
- Make sure VXLAN is configured in the cluster

- Make sure Segment ID is configured in the logical networking

- If you would like to use Unicast, change the Transport Zone from Multicast to Unicast. One the Provider vDC is created, go to vSphere Web Client and navigate to NSX Transport Zone, edit the newly created transport zone control plane mode from Multicast to Unicast

Then test again

If you need a step by step guidance, check out this blog post: NSX 6.2 for vCloud Director 8.0 SP

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
AcuteSys
Contributor
Contributor

Sreec and Bayu Wibowo,

Thank you both very much, it was the multicast setting, I switched it from Multicast to Unicast and that cleared it right up. I can research this further, but why does the multicast / unicast setting make such a difference?

0 Kudos
bayupw
Leadership
Leadership

From your error message, we can see the error is saying that either Segment ID is not configured: Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

Or multicast address is not used/configured: Unable to allocate an available resource for resource type Universal Multicast Address Pool., error code 844

As per this KB vCloud Director 5.x and VMware NSX for vSphere 6.x interoperability guidelines (2096351) | VMware KB‌, the default transport zones created by vCD (when Provider vDC is created) is set for Multicast mode

VMware NSX for vSphere with vCloud Director provisions controller-based VXLANs. VMware recommends to leverage Controller based VXLANs. By default, any transport zones created by vCloud Director is set for Multicast mode Replication and can be changed to Unicast or Hybrid mode if the NSX Controllers are deployed.

When using multicast, you would need the physical switches to be configured with L2 multicast (IGMP) and L3 multicast (PIM) when there are routing between the VTEPs

This was a requirement in vShield, but Unicast is now available in NSX: Physical Switch prerequisites for VXLAN setup in vShield 5.1.x and VMware vCloud Director 5.1.x/5.5....

This blog post has a good explanation on how the VXLAN control plane modes work NSX for vSphere: VXLAN Control Plane modes explained | Telecom Occasionally

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