"del nsx"
on ESXi command line may also return failed.VMware NSX-T Data Center 3.x
VMware NSX 4.x
You will encounter this issue, when the security-only cluster is configured using button 1 on the image, for example configured at a global level, not at cluster level.
It does not occur if the security-only cluster is configured using button 2.
1. When configuring a security-only cluster, use button 2 from the image above, which is at the cluster level.
2. If you have encountered this issue and you are unable to uninstall NSX from the security-only cluster, use the following procedure:
esxcli software vib list|grep -E 'nsx|vsip'
/etc/init.d/nsx-proxy stop
"nsxcli"
and run the command "del nsx"
on ESXi command line. "esxcli software vib list|grep -E 'nsx|vsip' " .
esxcli software vib list|grep -E 'nsx|vsip'"
on the ESXi host.3.If you believe you have encountered this issue and the above workaround does not work for you, please gather the information below and open a support case with Broadcom Support.
From NSX-Manager root context, run the below commands, save the output to a file, and scp those files off the manager and add to your case. If you login via admin use the command "st en" to switch to the correct context.
/opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -o showTable -t TransportNodeCollection > TransportNodeCollection.txt
/opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -o showTable -t HostTransportNode > HostTransportNode.txt
/opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -o showTable -t InProgressTransportNodeCollection > InProgressTransportNodeCollection
GET https://{{nsx-ip}}/api/v1/transport-nodes
For more information, see Creating and managing Broadcom support cases.