VMware Cloud Community
petermie
Enthusiast
Enthusiast

Phantom port on DVS for single host

I noticed that my DVS was showing "The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server." and when I went to Show Details it showed me this:

Host: esxservername.local

Parameters vNetwork Distributed Port:239

Clicking the Rectify button says it was successful, but it is not and the problem persists. If I go to the ports tab, I can see port 239 but it says "--" for Connectee and "Link Down" for state. When reviewing the logs on the actual host, I noticed this:

Hostd: warning hostd[2101064] [Originator@6876 sub=Hostsvc.NetworkProvider opID=2385376f-c645 user=vpxuser] Skip saving dvport dvDVSwitchName-239 to /vmfs/volumes/vvol:6000d31000d67602-0000000000000033/naa.6000d31000d67600000000000000006d/.dvsData/50 28 eb 42 df 4c b3 43-1d 4e ed 70 c5 a4 d5 d8/239: file not accessible

So the issue is that it seems this "vvol" doesn't exist (because we don't use them) and somehow the DVS thinks it needs to store config for that port there but fails. Is there any way I can clear out this bad data for that port somehow without removing and re-adding this host to the DVS? I've tried "net-dvs -l" on the host and that port doesn't come up, so i'm not sure where it's coming from

Tags (2)
0 Kudos
4 Replies
petermie
Enthusiast
Enthusiast

No ideas?

0 Kudos
berndweyand
Expert
Expert

i had this some weeks ago with one host. rectify didnt help. i had to disconnect the host from dvs, remove from vcenter and re-add

0 Kudos
Spisarau
Contributor
Contributor

Please refer this article VMware Knowledge Base

Unfortunately it wasn't working solution for me

0 Kudos
Spisarau
Contributor
Contributor

In my case I had the following message in file /var/logs/hostd

Skip saving dvport DSwitch-200 to /vmfs/volumes/vsan:52fdcd3dacea5d87-b653056f5b5709b5/26ead45e-8887-c654-7555-ac1f6bc3b9c8/.dvsData/50 09 19 1d 55 30 37 2c-22 d6 56 de 25 28 6c 8f/200: failed to create dir

After I created folder 26ead45e-8887-c654-7555-ac1f6bc3b9c  a warning message disappeared

0 Kudos