This might not answer your question, but at least explain what's going on from vCloud Director's perspective.
- in vCD a new isolated network is requested
- the network pool for the org vDC is VXLAN
- vCD sends the new vWire request to vShield/NSX to provision
- vCD waits to see that a new port group is created with the expected friendly name value
- Once vCD sees the new port group, record the unique reference in the vCD DB
- If an Edge is required, deploy an Edge to protect the network and assign an uplink.
The uplinks (quantity and order) for the purposes of VXLAN should be rather abstracted from vCD's view. If this were vCNI, vCD would definitely care about created the Port Group directly.
What I wonder, is if vShield Manager records the DVS and uplink data from the host when you prepare the host/cluster for VXLAN (which is when you pick a DvSwitch and set MTU/etc).
Assuming you are using "failover order" configured for your VXLAN, you can try to use REST API call to change the uplink names in vCNS manager (almost similar to what you can see in KB 2093324).
Note : I recommend to backup or snapshot the Manager first! Just in case ....
Headers required as:
Content-Type : application/xml
Use GET on the following to the prepared VDS':
( obviously replace the <manager> part with the name or IP of your vShield/vCNS manager )
You will get something like this (this is just a part of it if you have more than one vDS) :
Modify the <uplinkPortName> parts as you need. For example:
Leave the rest as it is.
Then use execute a "PUT" for the URL below in the REST client containing the above ( in step 2./ ) modified body (and again: assuming you are using failover order).
Note: Replace the "dvs-18" with the id in between <objectId> and </objectId> to what you got in the GET query ( again in bold and red ),
You should get a HTTP 200 code if all is OK. See : vShield API Guide around page 154, but personally I think the "Edit Teaming Policy" part is not correct.
This will not change any existing port-group setting in vCenter. You will need to edit them manually. This change is only for any further VXLAN v-wire creation.
P.s: I did my best to test and try the above example, but no guarantee and no support provided. For support please open a service request with VMware.
Bingo. That worked. Time for a blog post documenting it all for posterity...