After having selected a wrong Teaming Policy for the VXLAN vmknics I had to un-prepare the cluster, re-prepare it with the correct policy and setup a new Network Scope in vShield Manager.
Doing it this way was the recommended solution by a VMware support represantative.
Now, when I try to create a VXLAN in vCloud Director I get the following error message:
[ 45b5f0ef-36a0-4340-ab20-e952addb7119 ] Cannot deploy organization VDC network (aae66214-7753-4dcb-8da4-c0a9f1dee568)
com.vmware.vcloud.fabric.nsm.error.VsmException: VSM response error (202): The requested object : vdnscope-4 could not be found. Object identifiers are case sensitive.
How can I re-link vCloud Director to the newly created Network Scope in vSM? If I understand correctly, vSM is using a different Object identifier, now.
I'm running vCloud Director 5.6.4.2619597, vSM 5.5.4-2673026 and latest ESXi 5.5/vCenter Server releases.