The VDS may have been manually recreated:
Symptoms may include:
<TIME>
error vpxd[05721] [Originator@6876 sub=coredvsSync
opID=########-1284361-auto-####-h5:########-9f-########] Dvs
[<DVS_ID/Name>] port [###] does not exist; ignored update.<TIME>
warning vpxd[05749] [Originator@6876 sub=coredvsSync
opID=HB-host-####@2####-5b######] Portgroup [<dvportgroup_ID>] should not
be on the host [<ESXi_host_FQDN>]
Collecting diagnostic information for VMware ESXi using vSphere Client
VMware vCenter Server 8.x
VMware vSphere ESXi 8.x
This is typically caused by a synchronization failure between the host and vCenter Server. This generally occurs in the following scenarios:
The below steps describe the process of removing and replacing the current Virtual Distributed Switch:
#net-dvs -d <DVS_name>#vsish -e set /net/portsets/DvsPortset-0/destroy destroy (The DvsPortset # could be different, but it's usually DvsPortset-0))Listing failed for DVSwitch: DvsPortset-0, Error: Unable to get MTU: Status(bad0007) = Bad parameter#rm -f /etc/vmware/dvsdata.db Subscribe to this article to be updated on fix status: KB 275360