VMware Cloud Community
RomanBogachev
Contributor
Contributor

Internal interface of OrgVDC is disconnected

Hello!

I use:

VMware Cloud Director version: 10.1.0.15967236

NSX-v 6.4.6.14819921

Task:

Create a VDC Template That Includes Routed Networking via API

https://pastebin.com/PWVF8gQN

Try headers application/*+json;version=34.0 and application/*+json;version=33.0

When I instantiate a vDC template, everything is fine, except that the interface with the internal network is Disconnected.

If executed the command through the UI - that's ok and interface Connected.

When I was trace commands, I saw that a value was being passed <isConnected>false</isConnected> despite the specified value in api request <Connected>true</Connected>

2020-09-12 20:24:04,631 | TRACE | PUT https://nsx.example.com:443/api/4.0/edges/edge-97/vnics/1 Request body: <?xml version="1.0" encoding="UTF-8"?>

<vnic><label>vNIC_1</label><name>vnic1</name><addressGroups><addressGroup><primaryAddress>192.168.0.1</primaryAddress><subnetMask>255.255.255.0</subnetMask><subnetPrefixLength>24</subnetPrefixLength></addressGroup></addressGroups><type>INTERNAL</type><isConnected>false</isConnected><index>1</index><portgroupId>virtualwire-91</portgroupId><portgroupName>dvs.VCDVSRoutedOVDCNet-5d8a9ef8-7429-4bf9-89aa-6b7fea97199e</portgroupName><enableBridgeMode>false</enableBridgeMode></vnic> | requestId=30d02d93-ab61-4a9a-9471-835210fb1fe4,request=POST https://vcd.example.com/api/org/5146f747-f1d8-4be7-959a-1ec2adbcd778/action/instantiate,requestTime=... 33.0 vcd=ab0ec42e-f1ed-4f54-9604-e6c600102540,task=2161d976-0fcf-4d4f-80db-82e97e3468f6 activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:2161d976-0fcf-4d4f-80db-82e97e3468f6) activity=(com.vmware.vcloud.valc.activities.CreateVdcWithNetworkActivity,urn:uuid:3ce01d48-1b51-495c-bac3-ac1102991276) vcd=2c88414d-85c7-49c4-87e6-79b59318ed54,task=c445fa78-d0a2-4f2c-9683-83a902f76813 activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:c445fa78-d0a2-4f2c-9683-83a902f76813)

Is this a bug or did I make a mistake somewhere in request?

The same example was in vCloud API Programming Guide for Service Providers 33

0 Kudos
0 Replies