I'm setting up vCloud Director 5.1.1 (clean install) and using the new VCNS 5.1.2a. During the Provider vDC setup, a new VXLAN is automatically created ("PvDC_Name-VXLAN") and immediately displays an error saying that it "Cannot create Network Pool". The only option is to "repair". There is not an option to delete it, or modify it.
From doing a little "google-ing", I found that this article by PunchingClouds (http://www.punchingclouds.com/2012/09/09/vcloud-director-5-1-vxlan-configuration/), it says that I have to "prepare" vShield so that it will allow the VXLAN creation. Unfortunately, during step 2 (figure 3), when I go to prepare the Segment ID - I get the error: "not licensed for entity vcloud-netsec vxlan" (as seen in the attached pic).
I've also read similiar articles by Duncan Epping at Yellow Bricks: http://www.yellow-bricks.com/2012/10/03/configuring-vxlan/
and Mike Laverick: http://communities.vmware.com/people/Mike_Laverick/blog/2012/11/19/part-23a-my-vcloud-journey-journa...
however, these did not help. Mike's method of prepping involved prepping the "Connectivity" using the wizard. This does nothing for me. I click "Finish" and the little wizard blinks but doesn't do anything. It doesn't go away, display an error, or create activity within vCenter.
I've checked the licensing of the VCNS and have even gone and upgraded one of my vShield 5 Edge licenses to VCNS Advanced, but still get the same. My co-worker can recreate this on a completely seperate lab. So this brings me to a number of questions:
1) Is this supposed to be normal?
2) Did I miss something somewhere?
Here's my setup:
(2) Dell PowerEdge R620
ESXi 5.1.0 build 914609
vCenter 5.1 build 947673
vCloud Director 5.1.1 build 868405
vCloud Networking & Security 5.1.2a build 943471
