I have been having an unusual issue where I have one Windows Server 2012 R2 Standard Guest VM that whenever I reboot that Virtual machine, I get an alarm on the ESXI Host it is attached to saying "Network Connectivity lost" There are several other virtual machines that are identical to this one on the same host. They all can restart without this problem, only the one guest triggers this situation. Inside the guest there is only one NIC card configured.
On the virtual switch this guest VM is attached to, there is only this one vm. Under teaming and failover I have these values:
properties: Number of ports: elastic, MTU 1500
Security: Promiscuous mode: reject, Mac address changes: accept, Forged transmits: accept
Traffic Shaping: status: disabled
Teaming and failover: Load balancing: route based on originating virtual port, network failure detection: beacon probing notify switches: yes Failback: yes
The virtual switch has two physical adapters, both are 1Gbps, both are listed as online. One is listed under Active Adapters, one is listed as Standby Adapters.
The other bizare thing is that I have a icinga monitoring servers on the network, and there is a warning that comes up for this vm: <server>: ping4 PING WARNING - DUPLICATES FOUND! Packet loss = 0% RTA = 0.38 ms.
The VM is statically defined for one IP address. Last night I shut down the VM, and I could no longer ping the ip address that was configured for that VM. When the VM was shut down the warning went away in icinga. When I started the vm back up the warning came back. The arp table of my local machine confirms that I am resolving the IP to the mac address for the NIC card in the VM.
I cannot figure out why icinga thinks there is a duplicate IP or why rebooting the VM triggers an alarm for the esxi host going down.
Any thoughts? Has anyone experienced anything like this?
According to your problem, I want to give you some suggestions. I hope these suggestions give you an idea.
1. Remove your VM nic card and test again. (PoweringOff and On the VM without vNICs), then you can add a new vNIC and test again (this can be helpful to check any kind of MAC or IP address probelm).
2. Clear the configuration of your vNIC in the guest OS (no IP assignment). if the problem persists, it can be the MAC address of your VM.
3. Remove VMKernal port of your ESXi and then re-create it, or reset network configuration of your ESXi host.
Cheers
