Packet loss using Windows Server 2012 Standard 64bits virtualized on VMware Sphere 5.5 - Poweredge R720 Server

Hello rafaelnmx

There is a known issue with the 5720 driver within VMware 5.x. I would suggest reviewing this article to see if it applies to your situation.

http://www.dell.com/support/troubleshooting/us/en/04/KCS/KcsArticles/ArticleView?c=us&l=en&s=gen&docid=625576

Thanks

Hello Daniel, 

Thanks for answer!

But this procedure has already been performed, so disable NetQueue as updating the network card driver. Driver information used:
driver: tg3
version: 3.133d.v55.1
firmware-version: 5720-v1.25 FFV7.2.14 bc

Recalling that the packet loss only occurs in Windows Server 2012 R2 64 Bits.

Hello Daniel,  Thanks for answer! But this procedure has already been performed, so disable NetQueue as updating the network card driver. Driver information used: driver: tg3 version: 3.133d.v55.1 firmware-version: 5720-v1.25 FFV7.2.14 bc Recalling that the packet loss only occurs in Windows Server 2012 R2 64 Bits.

I installed VMware 5.5 from our custom ISO onto one of my R720s. I then created a VM and installed 2012R2 onto it. I have experienced no network issues with the VM.

If you would like further assistance then I will need to know the specifics about your configuration. This appears to be a configuration issue since I am unable to reproduce it with identical hardware and software.

Thanks

Hello Daniel,

There was some packet loss? What happens here at a period of 24 hours is an average of 5% loss. Apparently it's not significant, but it exists. While on a linux server does not happen any loss. I installed a Windows 2008 server and there are packet loss.

Your network card is Broadcom 5720?

What information from my environment would be most useful?

Thanks.

Do you have a single vSwitch (vSwitch0) with a single NIC with the management (vmk0) as well as the VM network connection (VM Network)?

Or are you using multiple ports on that vSwitch or maybe you created a separate vSwitch for the VM traffic using a different NIC?

Also, I assume you installed the VMware tools on the VM? These are pretty critical. And are you using the default e1000 or did you change to the vmxnet3?

Hello,

I'm using vSwitch1 (vmnic1), out of management and there is only one server that vSwitch1.

Vmtools installed and the driver used is vmxnet3

Thanks.

I just received an email that we released 5.5 update 1. The email stated that it addresses networking issues. If you are able to please update and let me know if the issue still exists.

https://dtxdropbox.dell.com

Login Name: esxi5.5u1
Password: ukqws0tf

The dropbox will be active for about 30 days. It should be available on drivers and downloads by that time.

Thanks

Hello Daniel,

What is the procedure to update using this file?

Thanks.

What is the procedure to update using this file?

To update using a .zip file you will need to use esxcli. There are many ways to do it, but I prefer to copy the .zip file to the host server using something like winscp, and then run the update. The command will be something like this:

esxcli software vib update -d "/full/path/to/file.zip"

Do not extract the file. Leave it in the compressed .zip format. You can read more about updating VMware using .zip files here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008939

Thanks

I just ran the update to make sure it works. After you enter the update command successfully it will sit at a blinking cursor for about 3-5 minutes with no indication that it is updating. After the update completes the screen will fill up with information:

Thanks for the reply! Will perform the procedure as quickly as possible.

Hello,

The update procedure was performed, server restarts, but gotten ESXi appeared the message that the network cards were not found. In your environment is also Broadcom 5720?

Stop using Broadcom NICs at all costs and replace them with Intel NICs.  I've wasted years of my life troubleshooting NIC issues, particularly in the Hyper-V world.  After being convinced by Dell technicians to switch to Intel, I haven't experienced a single NIC issue since.  Broadcom has their own agenda which does not align with real-world practices and I do not consider them to be production-worthy components.  Since then, I've spoken with many technicians who agree that Broadcom NICs are garbage.  Good luck.