Troubleshooting Failed Org Network Creation in vCloud Director

By | 08/04/2017

Today while working in my lab, I observed that while creating a new VDC in vCD was failing because org network failed to create.

On navigating to Org VDC list and clicking on error, it read the error load and clear that org vdc network can’t be created.


On navigating to Org VDC Networks section and clicking on error, I was able to identify what has caused the network creation failure.


The error stack was reading as below:

From above it was clear that there were some issues with Segment ID settings in NSX and when I verified my settings, i found segment ID was configured while I had prepared my cluster.


The last line of error stack was complaining about “Multicast Address Pool” and when I checked this setting, I found I have not configured any multicast pool under segment-id


After doing a bit more research on this  on google, I went ahead and added a Multicast IP range to segment id.


I deleted my old failed VDC and created a new one and this time it got created without any further issues.


Everything was looking green now.


Similar issue has been explained in VMware KB-2081294 and a good discussion topic on VMTN.

I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing. Be sociable :)

Category: NSX vCloud Director

About Alex Hunt

Hi All I am Manish Jha. I am currently working in OVH US as Operations Support Engineer (vCloud Air Operations). I have around 7 Years of IT experience and have exposure on VMware vSphere, vCloud Director,vSphere Replication, vRealize Automation, NSX and RHEL. If you find any post informational to you please press like and share it across social media and leave your comments if you want to discuss further on any post. Disclaimer: All the information on this website is published in good faith and for general information purpose only. I don’t make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this blog is strictly at your own risk. The Views and opinions published on this blog are my own and not the opinions of my employer or any of the vendors of the product discussed.