Thanks Brad. This is exactly what I was running into on these servers.
On Fri, Dec 6, 2013 at 8:48 AM, Brad DeHart <[email protected]> wrote: > We experienced this issue recently as well. The Virtual Machine Queues > (VMQ) feature seems to have some issues with Broadcom NICs. On all of the > physical adapters, in the adapter configuration, disable the Virtual > Machine Queues feature. It is in the Advanced tab. That took us from huge > latency spikes back to solid, sub 1ms latency. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jim Majorowicz > *Sent:* Wednesday, December 4, 2013 4:44 PM > *To:* [email protected] > *Subject:* Re: [NTSysADM] Possible Network issue with 2012 R2 Hyper-V > > > > Jim, > > > > I'll take a look at those settings here tomorrow. What I figured out this > afternoon is that is something to do with the Virtual Switch or NIC on the > VM itself. Connectivity to the Host PC which uses the IP assigned to the > Hyper-V Virtual Switch works just fine, but a PING to the VM will regularly > come back with times in the hundreds of MS rather than 1 or less. > > > > > > On Wed, Dec 4, 2013 at 1:00 PM, Kennedy, Jim <[email protected]> > wrote: > > I had similar issues with one of our 2012 hyper-v servers. The other is > always fine and the 208 R2 ones are always fine. Some of the NICs would > flip to ‘unknown’ networks. This certainly caused disconnects. > > > > I hit the below with gpedit and force it to private. > > > > Computer Configuration | Windows Settings | Security Setting | Network > List Manager Policies > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jim Majorowicz > *Sent:* Wednesday, December 4, 2013 3:54 PM > *To:* [email protected] > *Subject:* [NTSysADM] Possible Network issue with 2012 R2 Hyper-V > > > > I just installed a new server with a client and they appear to be > experiencing some Network Latency issues as in files take seconds to open, > the PC will frequently kick themselves into "Offline" mode, and there are > so many components in play I'm little hesitant as to even know where to > start, so if you all can help point me in the right direction.... > > > > New Server: > > Dell PE T320 > > 2 x Broadcom NetXtreme Gigabit NICs (Onboard) Set in a Team. > > Virtual Ethernet Adaptor Switch configured with static IP used to connect > to Host box. > > > > Connected Switch: (I do not manage this switch, and the company that does > will no longer support.) > > Sprint 6124SX3 > > (connected to two ports) > > > > Fibre to two other Sprint switches in another part of the building. All > of this will be replaced when the new Phone system is put in. > > > > The PCs are all connected to the network *THROUGH* the added port on the > Shoretel VoIP phone. Nothing with the phone system has been updated in > over 5 years. > > > > I used the Windows 2012 R2 Hyper-V Best Practices Checklist from the blog > to setup the server and pretty much just went with the default settings. > > > > Internet is a slow antiquated partial T1, soon to be replaced. > > > > How do I figure out what is causing the access lag? > > > > ------------------------------ > > Kern Health Systems Confidentiality Statement: > > This email and any attachments are legally privileged and can contain > business proprietary and/or confidential information intended for a > specific individual and purpose. This information is intended only for the > use of the individual or entity named above. The authorized recipient of > this information is prohibited from disclosing this information to any > other party unless required to do so by law or regulation and is required > to destroy the information after its stated need has been fulfilled. > > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution, or action taken in reliance on the > contents of these documents is strictly prohibited. If you have received > this information in error, please notify the sender immediately and arrange > for the return or destruction of these documents. >
