TCP Offload Engine (TOE) – Full Analysis

TCP Offload Engine (TOE)

TCP Offloading (also called TCP Chimney, TCP Chimney Offload, TCP Offload Engine) causes network problems since Windows server 2003 SP2.

TCP Offload Engine (TOE) for Windows is a technology for Network Cards that moves the processing of data in the TCP protocol stack from the server CPU to the network card, freeing CPU cycles for other duties. This technology is activated as of the installation of Windows Scalable Network Pack or just after you deploy …Service Pack 2.

All very nice, except the fact that many server administrators have no idea it is currently active on their Windows 2003 Servers, and that it can be the cause of many  – apparently random – network related issues, and performance decreases.

Time for an in-depth investigation!

 

Article Index

Definition – Theory
Problem Description
Which Operating Systems Are Affected (only Windows covered here)
Which Applications Are Impacted?
What is this Windows Server 2003 Scalable Networking Pack?
So how do I quickly check if any Network Traffic is being offloaded to my NIC?
A List of Issues caused when TCP Offload Engine is active on my Servers
Technical Explanation & Example
When should I definitely disable TOE?
What are the different options to CHECK & DISABLE TCP Offload Engine on my servers?
Check And Disable TCP Chimney on Windows 2003 On Server Level
Check And Disable TCP Chimney On Windows 2008 On Server Level
Check And Disable TCP Chimney On NIC Level
Check and Disable TCP Chimney On NIC Teaming Level
Disable TCP Offload by installing a Windows update (hotfix)
FAQ
More technical info
Screenshots of settings and issues
Windows Server 2003 Scalable Networking Pack overview
Hardware affected: (not a definitive list)
Are you sure this is an issue for customers using Microsoft servers and workstations?

 Definition – Theory

TCP Offload Engine (TOE) for Windows moves the processing of data in the TCP protocol stack from the server CPU to the network card, freeing CPU cycles for other duties. The Network Card will use TOE when Windows TOE Chimney is installed, and activated. With TOE, network communications are improved, and server efficiency is increased.

TCP offload Chimney can be set on server level and on NIC level/NIC teaming level. It will only be active when it is enabled on both server and NIC level. 

Problem Description

 Network connectivity issues can occur when servers are equipped with a NIC that uses the Broadcom 5708 chipset, and TCP Offload Engine enabled.  Many types of servers (HP/DELL) servers are equipped with this chipset.

The TCP Chimney Offload feature is enabled by the Windows Server 2003 Scalable Networking Pack. Which is installed by default when you install Service Pack 2 on your server. And currently simply all Windows 2003 server have SP2 installed.

Moreover should you have it disabled in on your NICs in your infrastructure, there is a bug that when upgrading HP Proliant Support Pack from 7 to 8, it may re-activate your TOE settings! 

 http://support.microsoft.com/kb/942861

Which Operating Systems Are Affected (only Windows covered here)

 
       Microsoft Windows XP x64 with KB912222 (Windows Scalable Networking Pack)
       Microsoft Windows Server 2003 Service Pack 1 x86 with KB912222 (Windows Scalable Netw. Pack)
       Microsoft Windows Server 2003 Service Pack 1 x64 with KB912222 (Windows Scalable Netw. Pack)
       Microsoft Windows Server 2003 Service Pack 2All servers with SP2 are affected.
       Microsoft Windows 2008 (all versions) – however TOE is disabled by default.
       Microsoft Windows Vista (all versions)
       Microsoft Windows 7 (all versions)  

Which Applications Are Impacted?


Citrix –  SQL – Exchange  Or any other application running on your system, including OS connectivity itself.

What is this Windows Server 2003 Scalable Networking Pack?


Windows Server 2003 Scalable Networking Pack is a new feature that Microsoft included and activated by default with windows 2003 Service Pack 2.

The Windows Server 2003 Scalable Networking Pack contains stateful and stateless offloads to accelerate the Windows network stack. The update includes the following features:

•        TCP Chimney offload

•        Receive Side Scaling (RSS)

•        Network Direct Memory Access (NetDMA)

http://support.microsoft.com/kb/942861

So how do I quickly check if any Network Traffic is being offloaded to my NIC?

 To check if TCP Chimney Offload is active, administrators can use the netstat.exe command to display current TCP/IP network connections and their state. From a command prompt, you can run the netstat –t command to display a list of TCP Chimney Offloaded connections. An offloaded network connection can be in one of the following states:
 

• In Host – the network connection is being handled by the host CPU

• Offloading – the network connection is in the process of being transferred to the offload target

• Uploading – the network connection is in the process of being transferred back to the host CPU

• Offloaded – the network connection is being handled by the offload target

 C:\>netstat –t

Active Connections

  Proto  Local Address          Foreign Address        State           Offload State
  TCP    127.0.0.1:12372        10.10.10.11:64882  ESTABLISHED     Offloaded   —>TCP Offload Engine is currently active!
 TCP    127.0.0.1:12372        10.10.10.11:64900  ESTABLISHED     Offloaded
  TCP    127.0.0.1:64848        10.10.10.11:12372  TIME_WAIT       Offloaded

 If you quickly want to query multiple servers to see if this is active use this PSEXEC command to query your servers

 C:\>PSEXEC.exe \\SERVER1,SERVER2,SERVER3 netstat -t |find /i “Offloaded” | sort

REMARK: NESTAT.EXE bug!   There is a very annoying netstat bug on Windows 2003. When using netstat.exe –t, sometimes you get no result. It looks like the exe is refusing to work… To resolve, use netstat.exe –a first, and then try again. Weird and annoying bug…

A List of Issues caused when TCP Offload Engine is active on my Servers

 The following issues may arise:

Errors when applications connect to a SQL server

http://support.microsoft.com/kb/942861 

You may experience many network-related problems after you install Windows Server 2003 Service Pack 2 on a computer that has a TCP/IP Offload-enabled network adapter.

 

http://support.microsoft.com/default.aspx?scid=kb;EN- US;948496

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION.

An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers

 

·        When using a VPN connection, you receive a following error message.lconnection.

·        You cannot create a Remote Desktop Protocol (RDP) connection to the server.

·        You cannot connect to shares on the server from a computer on the local area network.

·        You cannot join a client computer to the domain.

·        You cannot connect to the Exchange server from a computer that is running Microsoft Outlook.

·        Inactive Outlook connections to the Exchange server may not be cleaned up.

·        You experience slow network performance.

·        You may experience slow network performance when you communicate with a Windows Vista-based computer.

·        You cannot create an outgoing FTP connection from the server.

·        The Dynamic Host Configuration Protocol (DHCP) server service crashes.

·        You experience slow performance when you log on to the domain.

·        Network Address Translation (NAT) clients that are located behind Windows Small Business Server 2003 or Internet Security and Acceleration (ISA) Server experience intermittent connection failures.

·        You experience intermittent RPC communications failures.

·        The server stops responding.

·        The server runs low on nonpaged pool memory

 

http://support.microsoft.com/default.aspx?scid=kb;EN- US;948496

 

Some problems occur after installing Windows Server 2003 SP2

 

·        If it is an Exchange server, Exchange Queues become clogged in the MAPI delivery queue. Messages get stuck in this queue and cannot be delivered properly.

·        ActiveSync may not work on the Exchange Server 2003.

·        For the IIS server, browsing the Public and/or Default Website in IIS results in error “Page cannot be displayed”.

·        Non-Paged Pool (KERNEL) memory becomes exhausted.

·        For a printer server, the printing job may be partially missing.

·        For a SQL server, if you have an application that connects to SQL Server by using TCP/IP, you may intermittently receive error messages.

http://support.microsoft.com/default.aspx?scid=kb;EN- US;945977

 

Having Network Problems on Win2003 SP2

http://blogs.msdn.com/b/jamesche/archive/2007/12/19/having-network-problems-on-win2003- sp2.aspx

Windows 2003 Scalable Networking pack and its possible effects on Exchange (part 1):

http://msexchangeteam.com/archive/2007/07/18/446400.aspx

Windows 2003 Scalable Networking pack and its possible effects on Exchange – Part 2:

http://msexchangeteam.com/archive/2008/03/12/448421.aspx

http://blogs.technet.com/b/networking/archive/2007/11/04/sp2-scalable-networking-pack- connectivity-issues.aspx

http://blogs.technet.com/b/networking/archive/2007/11/04/sp2- scalable-networking-pack-connectivity-issues.aspx

 

Dell PowerEdge & Broadcom Issues

http://mbccs.blogspot.com/2008/01/dell-poweredge-broadcom- issues.html

A Windows Server 2003-based computer may stop responding during shutdown after you install the Scalable Networking Pack

http://support.microsoft.com/default.aspx?scid=kb;EN- US;940202

 

On a Windows Server 2003-based computer that has a TCP Chimney Offload network adapter, the TCP data stream may be corrupted when the network adapter indicates an MDL chain whose starting MDL has a nonzero offset

http://support.microsoft.com/default.aspx?scid=kb;EN- US;947775

 

TCP traffic stops after you enable both receive-side scaling and Internet Connection Sharing in Windows Vista or in Windows Server 2003 with Service Pack 1 or Service Pack 2

http://support.microsoft.com/default.aspx?scid=kb;EN- US;927168

 

You receive a Stop error message when a computer that is using a TCP/IP Offload Engine (TOE)-enabled adapter is running under low resources in Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;EN- US;945466

 

A Windows Server 2003-based computer responds slowly to RDP connections or to SMB connections that are made from a Windows Vista-based computer

http://support.microsoft.com/default.aspx?scid=kb;EN-US;947773

 

 

A Windows Server 2003-based computer responds slowly to RDP connections or to SMB connections that are made from a Windows Vista-based computer

http://support.microsoft.com/default.aspx?scid=kb;EN-US;940202

Network applications that use the NetBT keep-alive transmissions may not work correctly after you install the Windows Server 2003 Scalable Networking Pack on a Windows Server 2003-based computer

http://support.microsoft.com/default.aspx?scid=kb;EN- US;924325

Stop error occurs when a computer that is TCP Offload Engine (TOE) enabled is running under stress with a “low resource simulation” mode

http://support.microsoft.com/default.aspx?scid=kb;EN-US;945466

TCP traffic stops after you enable both receive-side scaling and Internet Connection Sharing in Windows Vista or in Windows Server 2003 with Service Pack 1 or Service Pack 2

http://support.microsoft.com/default.aspx?scid=kb;EN-US;927168

Slow Network copy and connection drops in Windows 7

http://www.windowsreference.com/windows-vista/slow-network-copy-and-connection-drops-in-windows- 7/

HP Advisory: ProLiant Support Pack (PSP) – Upgrading PSP Version 7.xx to Version 8.xx May Enable TCP Offload Engine (TOE) Feature on NC-Series 1Gb Multifunction Network Interface Adapters

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp? lang=en&cc=us&objectID=c01681083&jumpid=reg_R1002_USEN

HP Advisory: Windows Server 2003/2008 – VLAN Will Disable/Disconnect When Configured on Non-Teamed Network After Enabling/Disabling the TCP/IP Offload Engine (TOE) Property on ProLiant Server Using Network Configuration Utility (NCU) Version 9.65

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp? lang=en&cc=us&objectID=c01781210&jumpid=reg_R1002_USEN 

HP Advisory: Network Configuration Utility Version 8.55 (Or Earlier) Allows TCP/IP Offload Engine (TOE) Functionality to be Configured on Unsupported Network Teams Resulting in Possible Loss of Network Connectivity or Inability to Establish a Connection

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp? lang=en&cc=us&objectID=c00855264&jumpid=reg_R1002_USEN 

HP Advisory: (Revision) ProLiant Servers May Become Unresponsive or Generate a STOP 0x000000D1 Blue Screen When Running HP NIC Teaming and Microsoft Windows Server 2003 SP1 with the Scalable Networking Pack (SNP) and TCP/IP Offload Engine (TOE)

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp? lang=en&cc=us&objectID=c00747687&jumpid=reg_R1002_USEN

 

Technical Explanation & Example

 ·       TCP Offload Engine/ TCP Chimney is one of many features which help offload much of the network processing from the CPU and into the network card. The problem with it is that some network cards don’t do it correctly. When this happens, checksums get messed up or packets get mangled in mysterious ways. Mangled packets are as good as dropped packets and therefore don’t make it to their destination.  http://serverfault.com/questions/9923/why-does-the-tcp-chimney-offload-feature-on-some-ethernet-cards-fail-to-pass- some 

·        TCP Chimney is a new feature that improves network performance by offloading handling of TCP packets to the hardware layer, specifically to the network interface card (NIC). It works great if your NIC and NIC driver are capable. If they aren’t, you will see strange network issues. 

·        IMPORTANT: Issue occurs both on NICs and on Teamed NICs. There goes your 100% availability! 

·        Microsoft has disabled the SNP settings by default on Windows 2008! You will need to enable them… at your own risk! 

NOTE: these network issues, disconnects seems to appear random. Most likely any of the support teams will find any structure in the disconnects. 

Example: You have a application running on Citrix that connects to a SQL database. All servers have Windows 2003 SP2. 

Suddenly users report random disconnections with an application connecting to SQL. The application team will send the SQL support group for investigation. Since the application runs on Citrix, it goes next to the Citrix team. The Citrix team doesn’t find any changes on any the Citrix server and asks assistance from the network team. Those don’t find any recent changes on their infrastructure, and no problems on switches and routers. Besides, no other customers have complained and other servers on the VLAN work just fine.
“Looks like an application issue” and the ticket goes back to the application team.  
Some time passes before all infrastructure is checked (SQL, OS/CPU/memory/load, …) and finally a SQL profiler trace or Wireshark is installed on the server, where errors are detected.

Why did this suddenly happen? Well, it is an issue that can start any day: the server encountered a peak of network traffic, and the server started offloading more traffic to the NIC, which at some point was unable to handle the traffic, resulting in packet loss, and random disconnects.

When should I definitely disable TOE?

 ·        Disable TCP Offload when connecting to SQL database Server.

 REASON:  Performance and usability. When TCP Chimney is enabled it will often result in failed connectivity to SQL Server and/or dropped packets and connections that affect SQL server

http://blogs.msdn.com/b/cindygross/archive/2009/10/22/sql-server- and-tcp-chimney.aspx

 ·        Disable TCP Offload on Citrix Servers. 

REASON:  Issues have been reported when having this setting on:

o   Several hosted applications display network/SQL errors

o   ICA display not processed in time causing an incorrect order of showing the screen (or being slow and and then suddenly catching up (too) fast)

o   Citrix sessions disconnect 

·        Disable TCP Offload on exchange servers 

·        Disable it generally on ALL servers when you don’t want to troubleshoot complex very random connectivity issues – unless you notice increased speed (and no connectivity issues) with this setting enabled. The speed increase is not significant enough to take risks. 

What are the different options to CHECK & DISABLE TCP Offload Engine on my servers?

 Before going into the detailed action to resolve it, let’s have a look at the different solutions high level. We will describe the detailed actions for the first 3 option in the next paragraph below. In order of preference:

 1.       Disable TCP offload setting on server level via netsh command (recommended!)

                  = easy, no reboot

 2.       Disable TCP offload setting on the NIC or Network Teaming via user interface

                  = Semi- difficult,

·        since sometimes this settings is called differently on some NICs – meaning: consult your driver manual (Erm… my driver has a manual?)

o   Checksum offload

o   TCP Checksum Offload (IPv4)

o   TCP Checksum Offload (IPv6)

o   TCP offload engine

o   Many more, and very confusing names…

·        since network teaming software vary (Dell/HP, …) and by recreating Teamings, settings may go lost, or may be re-enabled by creating the teaming.

                             

3.       Install Windows update (hotfix)

           = easy, requires reboot, but too much effort.

 

4.       Disable TCP offload setting on server level via registry
   = easy, requires reboot  

5.       Update NIC drivers (may or may not resolve the issue, depending on the efficiency of the new driver. You will need to test it)                                                                                                                                                                                                                                                                        

6.       Disable TCP offload setting on the NIC or Network Teaming via registry
   = difficult, one needs to find the right key at the right place. (Good luck!)

 7.       Add a new NIC to your server and use this one
                  = Little drastic
 

Check And Disable TCP Chimney on Windows 2003 On Server Level

  A.      CHECK the TOE status on your server:

 On Windows 2003 there is no command for that.  You need to query a registry key. Run the following command:

 C:\>reg query HKLM\SYSTEM \CurrentControlSet\Services\Tcpip\Parameters /v EnableTCPChimney 

EnableTCPChimney    REG_DWORD    0x1                     &n bsp;              –> TCP Chimney is enabled on server level OR
EnableTCPChimney    REG_DWORD    0x0                          &n bsp;         –> TCP Chimney is disabled on server level

 B.       DISABLE TOE on your server:

C:\>netsh int ip set chimney disabled

Ok.

 image001
With netsh you can enable/disable TCP Chimney on server level

Check And Disable TCP Chimney On Windows 2008 On Server Level 

A.       A.  CHECK the TOE status on your server:

netsh int tcp show global

Output:

image002

 With netsh you can also query the TOE status on Windows 2008, on Windows 2003 you need to check the registry.

B.  Enable/Disable TOE

 
C:\>netsh int ip set chimney disabled

Ok.

 image001With netsh you can enable/disable TCP Chimney on server level

 Full article for Windows 2008 – and changing RSS settings, etc. : http://support.microsoft.com/kb/951037 

Check And Disable TCP Chimney On NIC Level

 A.      CHECK the TOE status on your NIC

First we can check if your NIC support TCP offloading :

C:\>netsh int ip show offload 
TCP Transmit Checksum
IP Transmit Checksum
TCP Receive Checksum
IP Receive Checksum
TCP Large Send
TCP Chimney Offload                 –> Your NIC supports TCP Offloading engine, it may be active.
 

 
B.      DISABLE TOE status on your NIC

 Go into the advanced settings and find change the setting to DISABLED. Disable your NIC and Enable it again for the change to apply.

 image004
TCP offload engine currently disabled on this Network Card, here called Checksum Offload.

 image007
TCP offload engine currently enabled on this Network Card, here called TCP Checksum Offload (IPv4).

Check and Disable TCP Chimney On NIC Teaming Level

 There is no way to check this command line. You will need to open the teaming software (HP/Broadcom, …) and check and disable this setting.
On some teaming software the TOE option is ENABLED by default!

 image003 
TCP offload engine enabled on HP Network Teaming.Default: Enabled!

Disable TCP Offload by installing a Windows update (hotfix)

A very tiny update to turn off default SNP features http://support.microsoft.com/default.aspx?scid=kb;EN-US;948496
This is a reliability update. Install this update to disable features in the Scalable Networking Pack (SNP) that are turned on by default, and which may affect your computer’s performance.
Both 32 bit and 64 bit version. This update just turns off all 3 registry keys on server level. That’s all. 

FAQ

 1.       Does it affect Windows 2000 (server) machines.

No, only the OSs listed above in Which Operating Systems Are Affected (only Windows covered here)

 2.       Can it exist on MY windows 2003/2008 server?

Yes, on those IF

·        The options are enabled on server level (registry)

·        The Network interface card supports TCP Offloading

·        The setting is enabled on the Network interface card OR on the teaming of two Network interface cards

Screenshots of settings and issues

  image005
Hosted application suddenly looses connection to SQL backend. Go troubleshoot that error!

 image006
MS Access application looses connection to SQL backend. “General network error”

More technical info

 

Chipset info from Broadcom

 

 

The BCM5708C is the industry’s first single-chip Gigabit Ethernet controller that supports the PCI Express® bus architecture.

The BCM5708C NetXtreme II® network interface controller continues the product family’s distinction of supporting a TCP/IP offload engine (TOE) and iSCSI on a single-chip platform.

 

Broadcom Demonstrates Industry’s First Fully Integrated TCP/IP Offload Engine (TOE) that Supports Microsoft’s TCP Chimney Architecture

http://www.broadcom.com/press/release.php?id=522952

 

Trace SQL problems with SQL Server Profiler

http://blogs.msdn.com/b/psssql/archive/2008/10/01/windows-scalable-networking-pack- possible-performance-and-concurrency-impacts-to-sql-server-workloads.aspx

 

Trace SQL problems with SQL Server Profiler and with network tracer (network monitor or wireshark)

http://blogs.msdn.com/b/psssql/archive/2010/02/21/tcp- offloading-again.aspx

 

 

Windows Server 2003 Scalable Networking Pack overview

 The architectural goal of the Scalable Networking initiative is to scale applications in the Windows family of operating systems to new levels of performance at a variety of cost points. Because of the variety of cost points and because of the variation in workload, the initiative includes the following two fundamental approaches:

·        Stateful offloads

·        Stateless offloads

TCP Chimney is a stateful offload. TCP Chimney offload enables TCP/IP processing to be offloaded to network adapters that can handle the TCP/IP processing in hardware. Each TCP Chimney offload-capable network adapter has a finite number of connections that it can support in hardware. TCP connections will be offloaded to hardware as long as the hardware can support these connections. After the hardware offload connection limit has been reached, all additional connections are handled by the host stack.

 RSS and NetDMA are stateless offloads. Where multiple CPUs reside in a single computer, the Windows networking stack limits “receive” protocol processing to a single CPU. RSS resolves this issue by enabling the packets that are received from a network adapter to be balanced across multiple CPUs. NetDMA allows for a Direct Memory Access (DMA) engine on the Peripheral Component Interconnect (PCI) bus. The TCP/IP stack can use the DMA engine to copy data instead of interrupting the CPU to handle the copy operation.

http://support.microsoft.com/kb/912222 

The Windows Server 2003 Scalable Networking Pack updates the Network Driver Interface Specification (NDIS). After you install the update, there is no user interface to configure the options that are associated with the Windows Server 2003 Scalable Networking Pack. By default, the options are turned on. You can configure the options by using the Netsh.exe tool or by using the registry. http://support.microsoft.com/kb/912222

 Hardware affected: (not a definitive list)

  ·        Network Interface Cards (NICs)

 Broadcom NetXtreme II

Broadcom NetXtreme II 5708 Dual Port Ethernet Mezzanine Card

HP BL20p G3 Dual NC370i Multifunction Network Adapter

HP BL25/35/45p Dual NC370i Multifunction Network Adapter

HP BladeSystem Dual NC370i Multifunction Network Adapter,

HP NC320m PCI Express Gigabit server adapter

HP NC370F PCI-X Multifunction Gigabit Server Adapter

HP NC370F PCI-X Multifunction Gigabit Server Adapter

HP NC370i Multifunction Gigabit Server Adapter

HP NC370T PCI-X Multifunction Gigabit Server Adapter

HP NC370T PCI-X Multifunction Gigabit Server Adapter

HP NC371i Integrated PCI-X Multifunction Gigabit Server Adapter

HP NC373F PCI Express Multifunction Gigabit Server Adapter

HP NC373F PCI-E Multifunction 1000SX Gigabit Svr Adapter

HP NC373i Integrated Multifunction Gigabit Server Adapter

HP NC373i Multifunction Gigabit Server Adapter

HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter

HP NC373m PCI Express Multifunction Gigabit Server Adapter

HP NC373T PCI Express Multifunction Gigabit Server Adapter

HP NC373T PCI Express Multifunction Gigabit Server Adapter

HP NC374m Dual port Multifunction network adapter

HP NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter

HP NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter for HP BladeSystem

HP NC380T PCI Express Dual Port Multifunction Gig Server Adapter

HP NC380T PCI-E Dual Port Multifunction Gigabit Server Adapter

HP NC382i Integrated Dual Port PCI Express Gigabit Server Adapter

HP NC382m PCI Express Dual Port Multifunction Gigabit Server Adapter

HP NC382T PCI Express Dual Port Server Adapter

HP NC532i Dual Port 10GbE Multifunction BL-c Adapter

HP NC532m Dual Port 10GbE Multifunction BL-c Adapter

 ·        HP Server server series

 HP ProLiant DL320 G4 Server series

HP ProLiant DL320 G5 Server series

HP ProLiant DL360 G4 Server series

HP ProLiant DL360 G4p Server series

HP ProLiant DL360 G5 Server series

HP ProLiant DL365 Server series

HP ProLiant DL380 G4 Packaged Cluster with MSA1000

HP ProLiant DL380 G4 Packaged Cluster with MSA500 G2

HP ProLiant DL380 G4 Server series

HP ProLiant DL380 G5 Server series

HP ProLiant DL385 Packaged Cluster with MSA500G2

HP ProLiant DL385 Server series

HP ProLiant DL560 Server series

HP ProLiant DL580 G3 Server series

HP ProLiant DL580 G4 Server series

HP ProLiant DL585 G2 Server series

HP ProLiant DL585 Server series

HP ProLiant ML310 G4 Server series

HP ProLiant ML330 G3 Server series

HP ProLiant ML350 G4 Server series

HP ProLiant ML350 G4p Server series

HP ProLiant ML350 G5 Server series

HP ProLiant ML370 G4 Server series

HP ProLiant ML370 G5 Server series

HP ProLiant ML530 G2 Server series

HP ProLiant ML570 G3 Server series

HP ProLiant ML570 G4 Server series

 ·        HP Server Blade series

 HP ProLiant BL25p G2 Server series

HP ProLiant BL25p Server series

HP ProLiant BL30p Server series

HP ProLiant BL35p Server series

HP ProLiant BL40p Server series

HP ProLiant BL45p G2 Server series

HP ProLiant BL45p Server series

HP ProLiant BL460c Server series

HP ProLiant BL465c Server series

HP ProLiant BL480c Server series

HP ProLiant BL685c Server series

  ·        DELL Server series

 Dell PowerEdge 2900

Dell PowerEdge 2950

 Are you sure this is an issue for customers using Microsoft servers and workstations?

Oh yes, it is!

http://blogs.msdn.com/b/psssql/archive/2010/02/21/tcp-offloading- again.aspx

Luckily with customers migrating to Windows 2008/R2 this problem will not occur anymore.

Leave a Reply

Your email address will not be published. Required fields are marked *