ESXi 5.5 1331829 - Guest VMs Losing network connection random

We are running ESXi5.5 1331829 - single cluster 7 hosts and vCenter 5,5 build 1476327.  Some guest VMs are Losing network connection randomly. Multiple OS's (Windows 2012 r2, Windows 2008 R2, Windows 2003) and different ESXi hosts (all running the same ESXi version).  The connectivity comes back by either rebooting the guest VM or by enabling disabling the network card.

1.)      At random VMs experience loss of network connectivity. The symptoms appear to be similar even though the versions are different. This is happening on ESXi 5.1 our production is running 5.5

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2072694

The second issue we have seen is a little different where we have the following issue:

2.)      After a reboot of a Windows 2012 R2 the VMs are getting a 169.254.X IP address. This issue seems to be documented in the VMware KB.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012646

Can anyone provide any advice?
llaravaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would recommend using thre VMXNET3 network interface in the VMs.

Not the E1000 legacy interface.

Make sure VMware Tools is installed to support this network interface.

Is this true ?
0
asavenerCommented:
Do you have multiple vCenter servers, even if they are controlling different clusters?

The auto-generated MAC addresses of the vNICs can conflict, if you're running multiple vCenter servers and they have the same Unique ID.

Virtual machine MAC address conflicts or have a duplicate MAC Address when creating a virtual machine (1024025)
0
llaravaAuthor Commented:
Andrew Hancock - I have the tools installed. So are the E1000 adapter not recommended for 2008R2 and 2012R2? Are there any KB's that describe the issue I am running into with E1000's. I am going to have to change interfaces all the servers which will require a lot of effort and I need to be sure this is the issue.  (issue #1)

Have you run into issue # 2 and are you applying the suggested solution? to all the Windows 2012 R2 servers? Or simply using VMXNET3?

After a reboot of a Windows 2012 R2 the VMs are getting a 169.254.X IP address. This issue seems to be documented in the VMware KB.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012646
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's always been recommended to use the VMXNET interfaces from when VMware introduced them, many years ago.

The driver is virtualised, rather than the emulated legacy E1000 driver, which should only be used for installation.

We have never gone production with VMware VMs using any other driver than VMXNET3 (latest). It also runs at 10GBe.
0
asavenerCommented:
Are you using static addresses, or DHCP?

169.254.x.x just means the client was unable to obtain a DHCP address.  It could indicate network issues, an exhausted address space, a DHCP server that had not completed a reboot, or human intervention such as removing a static address.
0
asavenerCommented:
I concur with the recommendation of VMXNET3 vNICs, by the way.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Get it escalated to VMware Support.
0
llaravaAuthor Commented:
This is NOT a VMware issue. But a Microsoft/Cisco one. There are no solutions available just workarounds and I just wanted to know if someone ran into this before and what was the option that they decided to go with.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We've not seen this issue before, VMware Support if you have support, will be able to check the logs, and give you a direction, as to where to look.

Do you not have a VMware Support contract ?

If this is truly a combined Microsoft/Cisco issue, you will have to change switch fabric or firmwares.
0
llaravaAuthor Commented:
We had a call with Cisco TAC support here are the commands to disable IP device tracking correctly which solved the issue.

nmsp attach suppress
ip device tracking maximum 0
ip device tracking probe use-svi
ip device tracking probe delay 10
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
asavenerCommented:
Can you provide the model and software version of the switch?
0
llaravaAuthor Commented:
It's the solution from Cisco TAC
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.