Network coredump configuration fails with "Connection type not supported" on VMkernel configured on NSX‑T NVDS

Products

• VMware vSphere ESXi

Issue/Introduction

While configuring network coredump, the following error appears:

#esxcli system coredump network set --enable true

Connection type not supported  

Environment

6.5

6.7

7.0

8.0

Cause

The crash dump is created before the vDS is converted to NVDS. So, when you try to configure it, the message "Connection type not supported" appears in the hostd logs.

hostd.log

####-##-##T##:##:##.###Z info hostd[#######] [Originator@####sub=AdapterServer opID=########-##-####-####user=vpxuser:VSPHERE.HCI\Administrator] AdapterServer caught exception; <<###########-####-####-####-############, <TCP '###.#.#
.# : ####'>, <TCP '###.#.#.# : ######'>>, ha-cli-handler-system-coredump-network, vim.EsxCLI.system.coredump.network.set>, N5Vmomi18DynamicMethodFault9ExceptionE(Fault cause: vim.EsxCLI.CLIFault
--> )
--> [context]zKq7AVICAgAAAEskdwEKaG9zdGQAANJCF2xpYnZtYWNvcmUuc28AAd/bDmxpYnZtb21pLnNvAAECrB0CQOGGaG9zdGQAAlqgUgDMxy0AVAMuAAIRPwM7fQBsaWJwdGhyZWFkLnNvLjAABG3RDmxpYmMuc28uNgA=[/context]
####-##-##T##:##:##.###Z info hostd[#######] [Originator@####sub=Solo.Vmomi opID=########-##-####-#### user=vpxuser:VSPHERE.HCI\Administrator] Activation finished; <<<###########-####-####-####-############, <TCP '###.#.#.# : ######'>, <
TCP '###.#.#.# : ######'>>, ha-cli-handler-system-coredump-network, vim.EsxCLI.system.coredump.network.set>
####-##-##T##:##:##.###Z info hostd[#######] [Originator@#### sub=Solo.Vmomi opID=########-##-####-#### user=vpxuser:VSPHERE.HCI\Administrator] Throw vim.EsxCLI.CLIFault
####-##-##T##:##:##.###Z info hostd[#######] [Originator@#### sub=Solo.Vmomi opID=########-##-####-#### user=vpxuser:VSPHERE.HCI\Administrator] Result:
--> (vim.EsxCLI.CLIFault) {
-->    errMsg = (string) [
-->       "Connection type not supported"
-->    ],
-->    msg = "",
--> }
####-##-##T##:##:##.###Z info hostd[#######] [Originator@#### sub=Solo.VmwareCLI opID=########-##-####-####  user=vpxuser:VSPHERE.HCI\Administrator] Dispatch set
####-##-##T##:##:##.###Z info hostd[#######] [Originator@#### sub=Solo.VmwareCLI opID=########-##-####-#### 
user=vpxuser:VSPHERE.HCI\Administrator] Dispatch set done
####-##-##T##:##:##.###Z info hostd[#######] [Originator@#### sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
-->    key = 150,
-->    chainId = 0,
-->    createdTime = "####-##-##T##:##:##Z",
-->    userName = "",
-->    host = (vim.event.HostEventArgument) {
-->       name = "##########.###.###.####.##.##",
-->       host = 'vim.HostSystem:ha-host'
-->    },
-->    eventTypeId = "esx.problem.coredump.unconfigured2",
-->    objectId = "ha-host",
-->    objectType = "vim.HostSystem",
--> }

Resolution

• Network dump collector is not supported on a VMkernel configured on an NSX‑T NVDS. This applies to both CVDS and NVDS. Because of this, the configuration cannot be created on such a setup.
  
  
• Alternatively, the crash dump works if the management VMkernel is moved back to a standard switch from vDS, CVDS, or NVDS.