no network connectivity to vm after restart

[samirkallout]

Hello

After I upgraded my vcenter and vsphere to 6.5 whenever I restart any virtual machine I have to disconnect and reconnect network or disable network card and renable in windows to be accessible on network.

What could be the problem?

[MikeStoica]

Did you checked the VM log file?Also the logs in Windows

[diegodco31]

Try updating vmtools.

Do you use vmnic adapter vmxnet3?

[MikeStoica]

Also what VMware tools you have installed? VMware recalled the VMware tools update 10.3.0 because it was causing PSOD and network connection loss on VMXNET3 .http://michaelstoica.com/vmware-tools-version-10-3-0-recall-and-workaround-recommendations-57796/

[PRSSB]

MikeStoica​

I too face the same problem with 6.5 and even with 6.7.0 with hardware version 14 and Vmtool version 10.3.5. All my virtual hosts (windows + linux) having VMXNet3 adapters.

Sometimes the VM gets network connectivity and sometimes it doesn't after reboot. I have logged support request several times but they are not able to identify the problem. They find some problem with the physical network switch. Network admin and switch vendor has verified and tested and found no problem with the switch or connectivity.

To re-establish the network connectivity of VM, I have found  work around. When I add a network adapter to the vm which has lost connectivity, after NA being added, the connectivity re-established. Then I remove the NA which I have recently added.

Do you have any help / suggestion ?

Thank you.

[TL0512]

Has anyone found a solution to this?  We are having the same problem and I have spent over 20 hours on the phone with VMWare.  Unfortunately, we are going in circles.

[jy221]

We are having exactly same issue. VMWare Support can't find the root cause. Does anyone have fix for it?

[Andy90]

I think we also have the same issue.

We have a 6.7 vCenter and running some Client-OS in virtual machine. These machines are restarted nightly and only some virtual machines lost there network connectivity after the reboot.

These virtual machine will boot via PXE-Boot and as the virtual machine will not receive any ip-address from dhcp, the boot-process failed.

After removing the virtual NIC, re-add a completely new one and assign the same mac-address than before, the virtual machine will boot from network again :-)

I will look forward to create a VMware request - but if anybody have a new solution, please provide it, thanks.

[Mark Werner]

We experience the same thing with vSphere 7.0 U3j. VMware Tools 12325 (12.5. Compatibility version 19.

Recently upgraded the compatibility version but we were having the same issue on previous versions of VMware Tools and Compatibility as well.

VMware Support was not able to determine why.

Oddly, it is just on 2 VMs that are on the same VLAN, and the only 2 VMs on that VLAN. But nothing appears a miss there.

[GeoPerkins]

 

How wide-spread of an issue is this for you - all VMs after a restart, occasionally, intermittently?

I am concerned because I am about to embark on an upgrade of VMware Tools 12352 (aka, 12.2.0.21223074) and Hardware version 19 on vCenter 7.0.3k (aka, Version:7.0.3.01300, Build number:21290409) with ESXi 7.0.U2 (aka, Build:18426014).

(I know from years ago there was an incompatibility between ESXi 6.x and a Windows Update that caused the Windows network adapter to ghost the IP address leaving an undefined network adapter. You can to delete the new network adapter in Windows and re-enable the ghosted network adapter to fix it. I am vague on the details. Seems like a Windows 2008r2 issue.)

[Alex_Romeo]

Hi,

The same thing happened to me and it was a problem of incompatibility with the Cisco Nexus 5000 switches

VMware Knowledge Base

Must be disable gratuitous ARP in the Switch (Cisco in my case).

https://kb.vmware.com/s/article/1028373?other.KM_Utility.getArticleMetadata=2&CoveoV2.ContentHandler.getLoader=1&other.KM_Utility.getUser=1&other.KM_Utility.getAllTranslatedLanguages=2&other.KM_Utility.getContentdocument=1&ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&other.KM_Utility.getViewCount=1&r=2&other.KM_Utility.getKnowDetails=1&ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&CoveoV2.EndpointHandler.getEndpoint=1&other.KM_Utility.getUrl=1&other.KM_Utility.getPRNumberLinks=1&other.KM_Utility.getCaseLike=1

Best regards,

Alessandro Romeo

[yopiraj310]

ok, so we have same issue with 3 ubuntu server vms, Exci 8.0 Update 1 version, Im still testing this environment, but as I can see, there is no fix. I cant trust our production vms with this product. 

[Maks Roshchyna]

What about dVS. What version it has? 

Check your settings also there. 

[GeoPerkins]

 Which "product" can't you trust? Ubuntu? EXCI (what is that??) vSphere 6.5?

[VRO123]

I have faced the same issue, in my case I edited the vmx  from VMXNET3 TO E1000, and then VM tools re-Installation 

[Milad Mehrabi]

have you triedto upgrad hw version?

are you sure you selected the correct os in options tab of the edit setting?