Smaller divisor values result in larger TSO chunks and better throughput as well as CPU utilization. RHEL 6 and SLES 11 SP1 distributions seem to be the optimal one for a no loss network. TSOĭivisor values in the range 2 to 16 are recommended for a low loss network. Tcp_tso_win_divisor controls how aggressive the network stack can be in making TSO requests. Performance considerably and must remain enabled. In networks with very little loss, TSO improves TCP Segmentation Offload (TSO) is enabled by default. In the Emulex documentation, there is the following information: TX packets:1634477316 errors:0 dropped:0 overruns:0 carrier:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Given the fact that HP is delivering servers 'in the flow' to our company, the chipset aren't the same from one box to another but the 10 considered servers are the same series and all have the same problem.Įth0 Link encap:Ethernet HWaddr d4:85:64:56:a1:88 We get a 'Cannot set device ring parameters: Operation not supported' When trying fix this value with ethtool, I get an error : The value is 981 on this one, but a few seconds later it will be 1022 or 956 or something else. Each time we poll, the value is not the same, which could be part of the problem and the TX ring buffer is 0. When querying the RX/TX ring size we get. The blades are BLC460C G7 (serial of one of them : CZJ0370C9Y)īasically, when looking at various parameters of the card, we found that a ethtool -S eth0 The kernel running is a 2.6.32-5-amd64 and it calls the be2net driver for this NIC. It's having a lot of frame error (0,9%) and this issue is disruptin a pack of 12 servers that can't work reliably together.

HPE Blog, Austria, Germany & Switzerland.

Emulex oneconnect driver