Windows Server 2003, SP 2 & SQL installed & NIC teaming configured. Both NICs are showing high output queue length spiking between 2 to 150 & sometime spiking between 2 to 200. I refered to http://blogs.technet.com/b/yongrhee/archive/2010/07/07/network-interface-output-queue-length-values-extremely-high.aspx & found valuable information but I want to understand in depth. What can be the possible reason & how can I find the root cause? Which counters should I setup to capture output queue length spikes? What sub-counters should I choose? Before updating NIC drivers what settings should I check? Thanks in advance.
- Moved by Boo_MonstersIncMicrosoft contingent staff, Moderator Thursday, January 10, 2013 7:40 AM (From:General)
Thank you for the post.
You may perform the following steps to troubleshoot/nail down the root cause of the perf. Issues.
1. Verify that SNP features (Chimney, RSS and NetDMA) are disabled on a Windows server2003 system
More information is documented in KB articles
948496 An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
950224 A Scalable Networking Pack (SNP) hotfix rollup package is available for Windows Server 2003
If all SNP features are deactivated already proceed with
2. Update NIC driver + update NIC Teaming driver to the latest available version
3. If step two makes no difference, break teaming, which is de-Installing the NIC teaming software.
Nick Gu - MSFT
If you disable teaming, does it still exhibit high queue lengths?
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.
Thats one path we are planning to take though it hasnt been finalized. Dell PowerEdge 6850 & from what I am told by Dell tech support is that these servers are no longer manufactured so I am thinking that its EOL product (no Dell link/document available to verify this). The server is an active node in cluster environment & hosts SQL DB.