KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Usage of Intel 82574L network adapter or E1000e vNIC in virtual machines from VMware cause data corruption

Last Update: 2016-11-23 11:39:35 UTC

 

Description:

Usage of Intel 82574L network adapter or E1000e vNIC in virtual machines from VMware cause data corruption when TSO (TCP Segmentation Offload) is enabled

The activity protocol of UDP reports the following warning:

ERROR: NIC Intel(R) 82574L Gigabit Adapter detected. The adapter can harm data. To prevent the problem change NIC or disable TSO function manually.

Solution:

Disable ALL TSO functions on these kind of Network Adapter:

- Large Send Offload(IPv4), Large Send Offload(IPv6),

- IPv4 Checksum Offload,

- IPv6 Checksum Offload,

- TCP Checksum Offload (IPv4),

- TCP Checksum Offload (IPv6),

- UDP Checksum Offload (IPv4),

- UDP Checksum Offload (IPv6)' 

 
 
More Information:

The release notes of UDP state the following:

http://documentation.arcserve.com/Arcserve-UDP/Available/V6/ENU/Bookshelf_Files/HTML/Release%20Notes/index.htm?toc.htm?udp_rn_limitation.html

  • When the CA arcserve UDP Server, Agent, or Recovery Point Server is running on machines with Intel 82574L network adapter or E1000e vNIC in virtual machines from VMware, the TCP Segmentation Offload (TSO) will be disabled when starting the CA arcserve UDP Agent Service. This is because a data corruption problem may occur on such environments when TSO is enabled. You can also manually disable TSO or replace with another kind of network adapter to avoid this problem.

    For more information about this problem, see 'Errata 17 - Tx Data Corruption When Using TCP Segmentation Offload' in the following Intel document:

    Intel 82574 Family Gigabit Ethernet Controller Specification Update

Important:
The solution in this document clarify that just disabling TSO as outlined in the Release Notes is not the final solution only.
All TSO parameter must be disabled in order to get this working

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Davide Brami

    The problem is still present on 2 VM but now is random.
    I rebooted VM and I see next days.