If you haven't gotten an answer about this. This is a vSM error propagated to vCloud Director. Basically vCloud is requesting the wrong vdnscope (VXLAN), and vSM errors because it doesn't exist.
This can happen if you have re-prepared VXLAN entirely after vCloud Director is configured for VXLAN.
The fix is to identify the correct vdnscope id from vShield Manager, and update the Network Pool in vCloud Director's database.
Alternatively, you'd have to recreate the entire Provider vDC in vCloud Director to work around the issue aside from the DB update.