It makes sense for VMWare to provide optimized nic drivers for their hypervisor, it makes more sense for the the VMWare Tools install to auto-prompt admins for recommendations such as this with a default of "YES (Recommended)". Not sure if they do and folks just tend to skip it thinking it's not needed, or it doesn't even prompt in the first place since it's assumed that everyone will eventually come across the KB which is unlikely since they wouldn't have realized they're having virtual nic throughput issues in the first place and in the interim upper mgmt is pointing fingers @ the application running on said virtual OS which is using said un-optimized nic driver ;). Seems like it's a common issue though with an easy fix, so it's definitely something that should be reported on and resolved as necessary!
From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Friday, November 29, 2013 6:28 PM To: [email protected] Subject: Re: [mssms] RE: Hash errors Seconding the change to VMxNext from emulated E1000 nic. I'm guessing somehow the emulation of the NIC fails when offloading certain aspects of the packet transfer, but we saw this time and time again on one customer. On Wed, Nov 27, 2013 at 2:37 PM, Russ Rimmerman <[email protected]<mailto:[email protected]>> wrote: Ahh the ole E1000 vs VMXNET3 driver. I've seen a LOT of network performance issues with using this default nic driver rather than the one that comes with VMWare Tools. VMXNET3 should definitely help your overall network performance, even if it doesn't solve the hash issues. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kent, Mark Sent: Wednesday, November 27, 2013 10:31 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Hash errors Well this is interesting: http://www.toolzz.com/?p=1085 We have the exact same environment and our VM's are using the E1000 adapter. I am having our VMWare admin change them to the VMXNET 3 adapter to see if that resolves our issues. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Wednesday, November 27, 2013 8:46 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Hash errors I excluded the drives the packages are on, as that is all that is on those drives: DP's. I have turned off BDR for one of the images and will see what happens. Thanks for the blog I will check it out now. I'll also look at the logs Trevor mentions. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Russ Rimmerman Sent: Tuesday, November 26, 2013 10:56 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Hash errors When you say you've excluded SCEP from scanning the DPs, what exclusions did you do, or are you saying you've excluded the DP completely? The most common reason for hash errors from my experience is due to missing AV exclusions. Also have seen LUN errors/issues cause it. I would also test a few packages with BDR disabled as well just for troubleshooting purposes. This may have some helpful info in it too http://blogs.technet.com/b/configmgrteam/archive/2012/05/07/troubleshooting-content-mismatch-warnings-on-a-distribution-point-in-system-center-2012-configuration-manager.aspx. Ignore the part about the known issue with a warning not returning to a success state since you're on R2. Russ Rimmerman MICROSOFT | SR. PREMIER FIELD ENGINEER | System Center Configuration Manager http://blogs.technet.com/b/configmgr_geek_speak/ ________________________________ Office: (832) 252-4558<tel:%28832%29%20252-4558> | [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Tuesday, November 26, 2013 3:12 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Hash errors Is there some way to determine why these occur? I seem to get an inordinate number of them happening. I have excluded SCEP from scanning the DP's but they still occur. This is frustrating. I was hoping this crap would have ended when we moved away from SCCM2007. We are on SCCM2012 R2 running on Server 2012. The servers are running on VMWare 5.1 with an Equilogic iSCSI backend. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State
