Hi,
some time ago I tried using Intel i350 with Debian Wheezy:
yyyy@xxxx:~/igb-5.2.9.4/src$ uname -a
Linux xxxx 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux
yyyy@xxxx:/home/yyyy/igb-5.2.9.4/src# modinfo igb
filename: /lib/modules/3.2.0-4-amd64/kernel/drivers/net/igb/igb.ko
version: 5.2.9.4
license: GPL
description: Intel(R) Gigabit Ethernet Network Driver
author: Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion: E377200391EBF74638FEDA2
yyyy@xxxx:/home/yyyy/igb-5.2.9.4/src# ip -V
ip utility, iproute2-ss140804
I was using bonding in 802.3ad mode for bonding with an Extreme-Networks switch. I had 2 similar servers, with identical configuration. Old one was using old e1000 interfaces with 802.3ad bonding, l3+l4 hash. New one was using I350-T2 dual port adapter with the same configuration. No Virtual Machines. Issue was on I350 around 20% packets to/from some random source/destination IPs were dropped. Servers were actually cloned so I'm certain there was no misconfiguration. I've tried disabling anti spoof check (https://communities.intel.com/message/192668#192668) but no luck, it doesn't work on my iproute2 and kernel (has this been fixed yet?). Any hints how to compile driver without anti spoof? Did anyone experienced similar symptoms?
In the end the fix was not to use bonding at all. While using 2 separate ports on this I350-T2 adapter, with the same VLANs, the same IPs - everything works flawless. This is why I assume a problem with igb driver on I350-T2 using bonding (with VLANs).
UPDATE: actually I've found Latest Flexible Port Partitioning Paper is now available. Learn about QoS and SR-IOV! which confirms there's an issue with 802.3ad. Can anyone give me a hint how to compile igb driver without anti spoofing feature?
Regards,
Wiadomość była edytowana przez: Bartek Krawczyk