[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1535
  • Last Modified:

High percentage of dropped packets in ESXi 4

I see high percentage of dropped packets for my VM. Why could this be happening. I even tried adjusting the recieve buffer with no luck. We are using the 1000v. Please help. Look at the pic below.. 66% omg!
drpx.PNG
0
VMwareLover
Asked:
VMwareLover
  • 6
  • 4
1 Solution
 
bgoeringCommented:
Have you checked for a speed or duplex mismatch between the 1000v port and the vm in question?
0
 
VMwareLoverAuthor Commented:
Yes, they are all at 1gb... its happening to almost all VMs in the envirnoment.
0
 
bgoeringCommented:
Take a look at http://www.ivobeerens.nl/?tag=vmware

The article concerns itself with IPv6 being enabled on Windows 2008 guests, and both disabling IPv6 (not a good idea in 2008) or changing the NIC type to vmxnet3 fix the problem.

If this doesn't work then more information is in order to troubleshoot the problem.

1. What guest OS types are involved (include 32/64 bit information)
2. What are the virtual NICs? E1000, flexible, vmxnet2, vmxnet3, etc.
3. Is vmware tools installed and current on all of the troublesome guests

Good Luck
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
VMwareLoverAuthor Commented:
The ipv6 is enabled. However, I just disabled it and restarted the server but it still has the similar packet loss... %drptx is 0 as before...
I am running windows 2008 R2 (mostly)
e1000
and yes the tools are insatalled on all the VMs and are upto date.
0
 
bgoeringCommented:
I would probably change the NIC to vmxnet3. To do that you must delete the old NIC, then add a new NIC specifying vmxnet3.

It is best to leave IPv6 enabled on 2008 and 2008 R2 because some services don't behave properly without IPv6 to bind to (or so I have been led to believe) and it really shouldn't hurt anything.

The vmxnet3 NIC will often give considerably better network performance than the e1000
0
 
VMwareLoverAuthor Commented:
Once I change the nic to vmxnet3, i see 0 drprx... thats good .. however, what are the drawbacks of using this vs e1000?
0
 
bgoeringCommented:
I don't know of any drawbacks - vmxnet3 supports everything E1000 does and is better "paravirtualized" so there is less overhead and better performance. It is generally recommended to switch to that.
0
 
VMwareLoverAuthor Commented:
interesting! so are there any limitations to this? DRS fails, vMotion etc etc? Any funtionality that it takes away. I guess this cant be used on a FT enabled VM.
0
 
bgoeringCommented:
Absolutely - it can be used for all of the above
0
 
bgoeringCommented:
I should say it CAN be used on FT vm
0

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now