[Problem Description]
Trigger condition:
l Windows server 2003 SP2 or Windows server 2008 is in use.
l The NIC drive version is not the latest.
For example, the version of the NIC drive BCM5716C is 4.8.4.1, which is released on December 23, 2008. This type of NIC drives does not comply with Windows server 2008.
Symptom:
1. A third-party network management system (NMS) uses TL1 commands to collect data through port 9819. However, port 9819 disconnection frequently occurs, resulting in data collection failure.
2. NEs are sometimes unreachable. The Windows server cannot receive NE response packets. However, the switch connected to the server can receive NE response packets.
[Identification Method]
1. The U2000 uses Windows server 2003 SP2 or Windows server 2008.
2. The NIC drive version is not the latest.
For example, the version of the NIC drive BCM5716C is 4.8.4.1, which is released on December 23, 2008. This type of NIC drives does not comply with Windows server 2008.
3. The current SNP configurations on the U2000 server are the same as those depicted in the figure below.
4. Some packets are captured on the Ethernet switch but not on the U2000 server.
[Root Cause]
The NIC drive of the Windows server is incompatible with the ICT/IP protocol stack of the Windows OS, resulting in packet loss when the NIC parses packets. Therefore, some packets cannot be captured on the U2000 server. However, data packets have been sent to the U2000 server.
[Impact and Risk]
Third-party NMSs and the U2000 are disconnected, resulting in data collection failure and unreachable NEs.
[Measures and Solutions]
Preventive measure:
Disable the SNP function of the OS TCP/IP protocol stack. Some advanced TCP/IP functions are called SNP.
Run the following commands in the Windows CLI:
netsh interface tcp set global chimney=disabled
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuning=disabled
netsh interface tcp set global netDMA=disabled
Verify whether the configurations have been set to the following.
Solution:
1. Upgrade the NIC drive to the latest version.
2. Disable the SNP function. For details, see Preventive measure.
Reply from Microsoft: Because SNP and NIC drive work in coordination, and commissioning the SNP and NIC drive is difficult. Disabling SNP is recommended.
