It is a specific port group that exists on a Distributed Virtual Switch.
I'm running the code directly against an ESXI 6.5 host (to add the vmotion interface).
There is nothing at all useful that I can see in the vpxd.logs on the vsphere appliance, nor in the vpxa.log file on the ESXi hosts itself and this is the hostd.log
2017-08-25T11:12:54.451Z info hostd[3DAC1B70] [Originator@6876 sub=Vimsvc.TaskManager opID=c6307be9 user=root] Task Created : haTask-ha-host-vim.host.NetworkSystem.addVirtualNic-1739
2017-08-25T11:12:54.451Z info hostd[3DAC1B70] [Originator@6876 sub=Default opID=c6307be9 user=root] AdapterServer caught exception: vmodl.fault.InvalidArgument
2017-08-25T11:12:54.451Z info hostd[3DAC1B70] [Originator@6876 sub=Vimsvc.TaskManager opID=c6307be9 user=root] Task Completed : haTask-ha-host-vim.host.NetworkSystem.addVirtualNic-1739 Status error
2017-08-25T11:12:54.451Z info hostd[3DAC1B70] [Originator@6876 sub=Solo.Vmomi opID=c6307be9 user=root] Activation [N5Vmomi10ActivationE:0xffec5650] : Invoke done [addVirtualNic] on [vim.host.NetworkSystem:networkSystem]
2017-08-25T11:12:54.451Z verbose hostd[3DAC1B70] [Originator@6876 sub=Solo.Vmomi opID=c6307be9 user=root] Arg portgroup:
--> ""
2017-08-25T11:12:54.451Z verbose hostd[3DAC1B70] [Originator@6876 sub=Solo.Vmomi opID=c6307be9 user=root] Arg nic:
--> (vim.host.VirtualNic.Specification) {
--> ip = (vim.host.IpConfig) {
--> dhcp = false,
--> ipAddress = "192.168.20.25",
--> subnetMask = "255.255.255.0",
--> ipV6Config = (vim.host.IpConfig.IpV6AddressConfiguration) null
--> },
--> mac = <unset>,
--> distributedVirtualPort = (vim.dvs.PortConnection) {
--> switchUuid = "63 6b 18 50 44 a0 48 05-92 e8 87 5f dc e2 e8 04",
--> portgroupKey = "dvportgroup-4384",
--> portKey = <unset>,
--> connectionCookie = <unset>
--> },
--> portgroup = <unset>,
--> mtu = 9000,
--> tsoEnabled = true,
--> netStackInstanceKey = "vmotion",
--> opaqueNetwork = (vim.host.VirtualNic.OpaqueNetworkSpec) null,
--> externalId = <unset>,
--> pinnedPnic = <unset>,
--> }
2017-08-25T11:12:54.452Z info hostd[3DAC1B70] [Originator@6876 sub=Solo.Vmomi opID=c6307be9 user=root] Throw vmodl.fault.InvalidArgument
2017-08-25T11:12:54.452Z info hostd[3DAC1B70] [Originator@6876 sub=Solo.Vmomi opID=c6307be9 user=root] Result:
--> (vmodl.fault.InvalidArgument) {
--> faultCause = (vmodl.MethodFault) null,
--> invalidProperty = "spec.distributedVirtualPort",
--> msg = ""
--> }
This is 'home lab' but I'm getting the same error on different distributed virtual Switch (v6 - with 6.5 vcsa) and different hosts (6.0.0). I'll keep trying over the next few days,
esxcli on test host shows
[root@esx4:~] esxcli network vswitch dvs vmware list
FunkySwitch
Name: FunkySwitch
VDS ID: 63 6b 18 50 44 a0 48 05-92 e8 87 5f dc e2 e8 04
Class: etherswitch
Num Ports: 1752
Used Ports: 4
Configured Ports: 512
MTU: 9000
CDP Status: listen
Beacon Timeout: -1
Uplinks: vmnic3, vmnic2
VMware Branded: true
DVPort:
...
...
...
Client:
DVPortgroup ID: dvportgroup-4384
In Use: false
Port ID: 66
The reasoning behind doing it this way because it appears that - at the time of writing - that the cmdlet New-VMHostNetworkAdapter doesn't let us specify the TCP/IP network stack to be vmotion.
