Solved

ESXi 5.5 1331829 - Guest VMs Losing network connection random

Posted on 2014-12-24
13
1,072 Views
Last Modified: 2015-04-23
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?
0
Comment
Question by:llarava
  • 5
  • 4
  • 4
13 Comments
 
LVL 118
ID: 40516880
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
 
LVL 28

Expert Comment

by:asavener
ID: 40534163
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
 

Author Comment

by:llarava
ID: 40535960
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
 
LVL 118
ID: 40535981
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
 
LVL 28

Expert Comment

by:asavener
ID: 40536033
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
 
LVL 28

Expert Comment

by:asavener
ID: 40536034
I concur with the recommendation of VMXNET3 vNICs, by the way.
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 

Author Comment

by:llarava
ID: 40567393
0
 
LVL 118
ID: 40567402
Get it escalated to VMware Support.
0
 

Author Comment

by:llarava
ID: 40567420
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
 
LVL 118
ID: 40567449
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
 

Accepted Solution

by:
llarava earned 0 total points
ID: 40594703
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
 
LVL 28

Expert Comment

by:asavener
ID: 40733412
Can you provide the model and software version of the switch?
0
 

Author Closing Comment

by:llarava
ID: 40739670
It's the solution from Cisco TAC
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
VirtualBOX on GNS3 11 95
Multipurpose Server for a very small buisiness 20 106
Get host nic mac address 19 56
vCenter 6.5 install woes 2 38
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to delpoy the vCenter Server Appliance and how to configure its network settings Deploy OVF: Open VM console and configure networking:
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now