Hi,

I have some servers with Intel 82599ES 10-Gigabit SFI/SFP+ nics, and the SFP+ modules are Intel 10Gig LR (10GSFPLR). These are connected to some fiber-taps, with a single fiber-cable (since the taps are only sending traffic).

This means that we do not get a link on the nic. But will we be able to see the traffic on the nic, using promisc mode in Linux?

I have of course tried the ethtool, but it does not seem to work, despite no warning or error messages. Is it at all possible to force the speed of the nic, without link (and auto-negotiation)?

I currently have two Intel NICs teamed as Team #0.

I'm trying to break the team to use each adapter independently, however, when I try to configure the team via "Intel(R) Advanced Network Services Virtual Adapter" I get a vague error, "GetTeamInfo failed" and the "Settings" tab is empty.

I've tried running the ProSetCl command line tool and it tells me there is no Teams installed.

I've also tried uninstalling the "Intel(R) Advanced Network Services Virtual Adapter" adapter and get a different error message "Teams cannot be removed if a virtual NIC is bound to the team. Remove the virtual NIC before deleting the team." As far as I can tell there is no virtual NIC installed on my machine.

How can I force the removal of the Team #0 adapter so that I can use the individual NICs separately? I appreciate any help/guidance you can provide.

Thanks

Ethan

Same issue as seen elsewhere with the i218-V on a dozen Lenovo e550. Rather than going to two remote locations and popping the cmos on the lot, I'd like to give the ULP enable/disable utility a try.

Hi everyone

I'm coming here because I have a "little" and annoying problem... I'm encoutering random disconnections while using my PC on various stuffs (surfing, online gaming, ...) and i can't figure what the problem is :/

Here's my setup :

- My motherboard is an Asus B85-Plus which has "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"

- All my drivers are up-to-date

- I'm linked to my router by RJ45 through CPL's (Devolo).

- I'm using Windows 7

- My internet access provider does not suffer any disconnections, it comes from "me" (yes, I asked them to check the logs haha)

And here's some exta info's :

- A friend of mine has the exact same setup (hardware, cables, drivers, CPL, OS and IAP) and he doens't suffer any disconnections

- I tried with another brand of CPL, same problem

- I tried with another router behind my provider's one, same problem.

- I tried with a veeeeryyyyy long cable (around 15 metters haha), same problem.

When i'm playing a certain game, Killing Floor 2, it seems that the game send a bunch of pings during a short time ; is it possible that the network card crash because of it ?

When it appears, I have the little yellow "!" on my Internet Acces icon (on windows 7). If I right click, then click on "solve problems", it comes back 99 times on 100...

Thank you very much !

Just when I have a chance to flash a handful of XL710's from v5.02 to v5.05, I noticed today that v6.01 is available.

Q. I looked in the usual places but didn't file any release notes saying what was fixed. Are there any?

Q. Is NVM v6.01 compatible with any of the current VMware ESXi drivers on ESXi v6.0U2 or do we need to wait for a new driver?

VMware Compatibility Guide - I/O Device Search

Q. Any ETA on the VMware Driver to match v6.01?

- David

Hello,

Environment:

OS:  Windows 10E X64 1703

CPU:  Intel i7-6700k 4GHz

RAM: 32GB

NIC:  Intel 1219V / 1211 (on-board) (using latest Intel ANS drivers)

MB:  Gigabyte H170N (r.1)

Router:  Netgear R7000 (DD-WRT)

Gateway: Arris SB 6190 (Comcast)

Background:

I've been using ANS Teaming on and off for the past 6 months.  The team has mostly worked up until a few days ago, and  I have no idea what might have changed in my environment or why this problem might have started.

I create the team generally following this method:

1. Install the ANS driver (reboot)

2.  Unplug NICs from router

3. setup switch: (from different LAN client)

     a. create LAG group

     b. assign ports to LAG group

     c. select static link aggregation on ports 3 & 4

     d. disable STP

     3. Enable TRUNK

4. Create static link aggregation team in ANS

5. Power off computer

6. Power off router

7. Plug NICs into router

8. Power on router

9. Power on computer

Team is created successfully.  (screenshot 1)

Issue:

Receinvg A LOT of errors/dropped connections on the team. If I run a speedtest (speedtest.net) and watch the team in real-time, Err/Drop numbers will spike drastically. There are no errors reported on the router syslog.

After TWO speedtests, the team will show approx Err: 2000 / Drop 4000 (Screenshot 2)

After 3 days of heavy traffic, the team will show approx Err: 50,000/ Drop: 80,000 (Screenshot 3)

Troubleshooting:

-Ran Intel ANS diagnostics: All tests passed

-Removing team

-Reinstalling NICs, and drivers

-Removing team, running speedtest on individual NICs (Very few err/drops)

-Replaced cables

Any ideas what might be happening?

Thanks,

SV

Screenshot 1:

Screenshot 2:

Screenshot 3:

Hoping someone can help.

Recently upgraded a server running Xen from 3.18.44-20.el6.x86_64 to 4.9.39-29.el6.x86_64 (did a yum update so other packages would have been updated to).

Since rebooting, we randomly get "e1000e: eth0 NIC Link is Down", this happens for only a second, but since we have this interface bonded it can be enough for it to bring down the interface fail over, and then come back again, which causes packet loss.

If tried turning pcie_aspm off, flow control off, nothing seems to help. The problem seems to be worse when high traffic is being used, but also happens randomly as well.

NIC Intel Corporation 82574L Gigabit on a Supermicro box. Driver 3.2.6-k

Have now upgraded to 3.3.5.10, the problem seems to be happening a lot less often, but I'm not sure if its a coincidence.

Hello,

we're having problems with an Intel X710-DA4 retail card on VMware ESXi 6.5u1. After some time (usually minutes to hours) of sustained traffic on the NIC, we're seeing the following in vmkernel.log:

2017-08-11T12:26:02.554Z cpu18:66233)i40en: i40en_HandleMddEvent:6495: Malicious Driver Detection event 0x02 on TX queue 0 PF number 0x03 VF number 0x00

2017-08-11T12:26:02.554Z cpu18:66233)i40en: i40en_HandleMddEvent:6521: TX driver issue detected, PF reset issued

The network port in question is then apparently shut down, although the link stays up, and it does not pass any more network traffic. Only a reboot of the server will reset the network port and allow traffic to flow through it again.

The traffic pattern that leads to that issue usually is TCP traffic of >300MBit/s passing through a firewall virtual machine, entering on one virtual interface and exiting through another.

We are using ESXi 6.5u1 with the built-in i40en driver, as well as the latest NVM firmware version 5.05:

000:82:00.0 8086:1572 8086:0004 vmkernel vmnic2

0000:82:00.1 8086:1572 8086:0000 vmkernel vmnic3

0000:82:00.2 8086:1572 8086:0000 vmkernel vmnic4

0000:82:00.3 8086:1572 8086:0000 vmkernel vmnic5

esxcli network nic get -n vmnic3

   Advertised Auto Negotiation: false

   Advertised Link Modes: 10000BaseSR/Full

   Auto Negotiation: false

   Cable Type: FIBRE

   Current Message Level: -1

   Driver Info:

         Bus Info: 0000:82:00:1

         Driver: i40en

         Firmware Version: 5.05 0x80002898 1.1568.0

         Version: 1.3.1

   Link Detected: true

   Link Status: Up

   Name: vmnic3

   (...)

More details to curtail the problem:

• We are not using SR-IOV.
• The exact driver version is i40en 1.3.1-5vmw.650.1.26.5969303. We have observed the same issue with a previous driver version 1.3.1-1OEM.600.0.0.2768847.
• The issue happens on multiple hosts, all with the same Intel X710-DA4 adapter.

VMware Support has not been able to resolve the issue for us, saying they have been observing issues with all current X710 drivers and cannot point us into any specific direction - other than asking us to turn to Intel for support.

Honestly, at this point we're at our wits end and do not know how to proceed any further - other than switching to a different manufacturer's network hardware altogether.

Thank you for any helpful advice.

Hello,

After a clear installation of Windows 10 64bit I am experiencing frequent disconnecting my internet ethernet connection, especially after awaking from sleep mode.

After rebooting the system the internet connection is functioning again.

I tried to install the newest driver from intel download site more times without success:

Download Intel® Network Adapter Driver for Windows® 10*

My Motherboard: MSI-7760

Failure protocol attached.

I read about a patch which could solve the issue.

Thank you very much for your support!

Vojtech

Hi.

I have an interesting case on two "twin" servers (in a cluster).

Network cards on servers: double X520-2

On the first server:

Intel (R) PROSet Monitoring Service crashes:

System

  - Provider

   [Name] Application Error

  - EventID 1000

   [Qualifiers] 0

   Level 2

   Task 100

   Keywords 0x80000000000000

  - TimeCreated

   [SystemTime] 2017-08-29T08: 17: 10.000000000Z

   EventRecordID 1393

   Channel Application

   Computer "!!!"

   Security

- EventData

   IProsetMonitor.exe

   22.4.14.0

   58fe63f7

   ntdll.dll

   6.3.9600.18725

   59380775

   c0000374

   00000000000f1c00

   1B4

   01d3209ef080cb45

   C: \ Windows \ system32 \ IProsetMonitor.exe

   C: \ Windows \ System32 \ ntdll.dll

   73dac95e-8c92-11e7-80c1-b973ac048f3d

After restarting the service, it works for some minutes and turns off again.

actions:

1. The latest drivers from Intel (on both servers)

2. Removed "Teams" and reinstalled the drivers together with "Intel Advanced Network Services"

3. reinstall only "Intel Advanced Network Services"

did not help

The second server is working fine

What else can i do ??

Hello

I'm currently considering to upgrade my home LAN for better NAS transfer capabilities, using Port Teaming at 802.3ad protocol.

I'm using Windows 10 64-bit on my PC. I have built in Intel I219-V adapter on my MB.

I've read about the Windows 10 port teaming issues, which should be already solved, but not all of the NICs are supported on the update.

Here are the options i consider:

1) Buy new Intel I210-T1 Single Ethernet adapter (35-40$) (from HP) and team it with my I219-V - will port teaming work with these two different NICs under Windows 10? (in windows 10 compatibility support table it says that I210 has full support but what about I219?)

2) Buy used Intel I340-T2 Dual Ethernet adapter (25-30$) and apply teaming to both ports - in compatiblity support table it says that I340 doesn't have full support...

3) Buy used Intel 1000 PRO/PT Dual Ethernet Adapter (10-15$) (it's cheaper than used I340, and cheaper than new I210-T1) - in compatiblity support table it says that it doesn't have full support...

10gb/s cards are not affordable... they're too expensive... same as I350-T2 (150$)...

If i had to choose between I350-T2 and 10bg/s adapters - X520-T2 would be a better choice than I350-T2 - X520 has dual 10gb/s ports, and full support, but it costs about 125$...

I don't want to waste my money... I have to by a 802.3ad switch (costs about 100USD), and i don't want to spend too much money - my main goal is to increase NAS transfer rate between my PC and NAS above 112,5 MB/s - so it's not worth spending few hundred bucks...

I also would like to be 100% effective with my choice so i won't stay with few network cards

Please help me to decide which adapter i should by

Hi Sharon,

I have the same problem.

1. FreeBSD 11.1-RELEASE

2. ixl0: <Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k>

ixl0: fw 5.0.40043 api 1.5 nvm 5.04 etid 80002505 oem 0.0.0

3. this is iscsi target server. If traffic with high load is flowing on the server, error log will occur frequently.

ixl0: WARNING: queue 2 appears to be hung!

ixl0: WARNING: Resetting!

ixl0: Malicious Driver Detection event 2 on TX queue 6, pf number 0

ixl0: MDD TX event is for this function!

It does not solve even driver version 1.7

Regards,

Takunii

Hi all,

I am facing some -I think- strange problem with IPV6 and QinQ in a Linux host, and may be someone has faced similar problem (or could provide a hint).

I have some VMs running in a host (KVM), and every time any VM sends an ICMP6 Router Advertisement, we get the following log in syslog:

Aug 10 11:18:36 Hostname kernel: [1722430.045240] IPv6 header not found

For the traffic, I use QinQ (802.1Q in both tags), the inner tag is set with OVS in the tap(or bridge, no difference), and the outer is set with a veth of vlan type, in the following way:

+-------------------------------------------------------+

|                   +-----------+               HOST    |

|                   |           |         Unbuntu 16.04 |

|                   |    VM-1   |         4.4.0-62-generic

|                   |           |                       |

|                   +----+------+                       |

|                        |                              |

|                        |TAG=1                         |

|              +-----------------------+                |

|              |       OVS             |                |

|              +---------+-------------+                |

|                        | veth1.203                    |

|                        |                              |

|                        |                              |

|                        +veth0                         |

|              +---------------------+                  |

|              |      Bridge         |                  |

|              +-------+-------------+                  |

|                      |                                |

|                      |                                |

|                   +--+----+                           |

|                   |ens11f1|                           |

+-------------------------------------------------------+

'Regular traffic' (non ICMP6) seems to work fine, the problem happens apparently only with the Router Advertisement or Neighbour Discovery.

I checked the code writing that log, and I think it's in 'kernel/net/ipv6/exthdrs_core.c'

if (*offset) {

  struct ipv6hdr _ip6, *ip6;

  ip6 = skb_header_pointer(skb, *offset, sizeof(_ip6), &_ip6);

  if (!ip6 || (ip6->version != 6)) {

    printk(KERN_ERR "IPv6 header not found\n");

    return -EBADMSG;

  }

  start = *offset + sizeof(struct ipv6hdr);

  nexthdr = ip6->nexthdr;

}

but both the protocol and protocol version seem right in tcpdump:

11:28:38.675686 02:00:40:00:21:31 > 33:33:00:00:00:01, ethertype 802.1Q (0x8100), length 158: vlan 203, p 0, ethertype 802.1Q, vlan 49, p 0, ethertype IPv6, fe80::40ff:fe00:2131 > ff02::1: ICMP6, router advertisement, length 96

`....`:...........@...!1................... @...............@.!1..........@.... ........*.. ..!1................*.. ..!1............. '.

11:28:39.300076 02:00:40:00:23:2a > 33:33:00:00:00:01, ethertype 802.1Q (0x8100), length 158: vlan 204, p 0, ethertype 802.1Q, vlan 193, p 0, ethertype IPv6, fe80::40ff:fe00:232a > ff02::1: ICMP6, router advertisement, length 96

`....`:...........@...#*...................%@...............@.#*..........@.... ........*.. ..#*................*.. ..#*.............

I already disabled (just in case) all the offloading features in the ethernet card (Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02)).

sysadmin@olnmpep02318n002:~/andres$ ethtool -k enp2s0f1

Features for enp2s0f1:

rx-checksumming: off

tx-checksumming: off

  tx-checksum-ipv4: off

  tx-checksum-ip-generic: off [fixed]

  tx-checksum-ipv6: off

  tx-checksum-fcoe-crc: off [fixed]

  tx-checksum-sctp: off

scatter-gather: off

  tx-scatter-gather: off

  tx-scatter-gather-fraglist: off [fixed]

tcp-segmentation-offload: off

  tx-tcp-segmentation: off

  tx-tcp-ecn-segmentation: off

  tx-tcp6-segmentation: off

udp-fragmentation-offload: off [fixed]

generic-segmentation-offload: off [requested on]

generic-receive-offload: on

large-receive-offload: off [fixed]

rx-vlan-offload: off

tx-vlan-offload: off

ntuple-filters: on

receive-hashing: on

highdma: on

rx-vlan-filter: off

vlan-challenged: off [fixed]

tx-lockless: off [fixed]

netns-local: off [fixed]

tx-gso-robust: off [fixed]

tx-fcoe-segmentation: off [fixed]

tx-gre-segmentation: on

tx-ipip-segmentation: off [fixed]

tx-sit-segmentation: off [fixed]

tx-udp_tnl-segmentation: on

fcoe-mtu: off [fixed]

tx-nocache-copy: off

loopback: off [fixed]

rx-fcs: off [fixed]

rx-all: off [fixed]

tx-vlan-stag-hw-insert: off [fixed]

rx-vlan-stag-hw-parse: off [fixed]

rx-vlan-stag-filter: off [fixed]

l2-fwd-offload: off [fixed]

busy-poll: off [fixed]

hw-tc-offload: off [fixed]

Any help/hint is trully appreciated!

Regards,

Andrés

I've been trying to troubleshoot this issue now for months on and off and have gotten nowhere.

It seems that WOL is broken when using this hardware under Windows 10.

I've been using the Windows 10 driver that installs by default (version 12.155.22.6 dated 4/5/2016) and have not been able to find a different one (latest ProSet software doesn't contain a driver for this adaptor).

I've set everything up that various internet threads I've read have said to do, this includes:

BIOS:

Enable the adaptor (duh)

Enable Remote Wake Up

Disable Low Power Mode

Windows:

Disable Fast Startup

Make sure, under the Power Management tab, that all the boxes are checked.

There are no properties for "Waking" in Advanced Properties for the adaptor so I can't set them, nor is there a PME Event Property to check/change.

---

I know that WOL is possible for this machine because I popped in a PCI NIC and got WOL to work on that NIC, but this integrated adaptor just won't comply.

Lot's of threads out there saying it can be done, but I can't seem to do it on my hardware.

Here's a capture from BOOTUTIL showing that WOL is supposed to work...

---

C:\Intel22.4.0.1\APPS\BootUtil\Winx64>BOOTUTILW64E.EXE

Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.40.1
Copyright (C) 2003-2017 Intel Corporation

Port   Network Address     Location    Series     WOL Flash Firmware                                     Version
==== =============== ======== ======= ===  ============================= =======
1       0024E819DC99        0:25.0       Gigabit    YES  FLASH Not Present

---

One suggestion I found was to update the boot agent (mine is 1.3.81) to the latest (1.5.something) and then throw a flag in the boot agent setup that supports WOL.

However, I do not think I can update the boot agent as BOOTUTIL says there's no flash firmware present to do so, or correct me if I'm wrong.

Ideas on how to update the boot agent?

Aside from that any other ideas?

===

Editing to add infomation

===

Well, I never thought I'd see the day that Linux supported old hardware better than Windows but that day is today.

Reference this thread: Wake on Lan, Windows 10 Pro, integrated 82567LM-3

And see what the Fabrice person says.

The instructions in this referenced thread above were too generic to work verbatim, but they were enough for me to figure my own way to try out WOL under a Linux distro lickety-split.

In a nutshell this person suggests booting to Linux, turning on WOL, then booting back to Windows, as if that would permanently and magically enable WOL in Windows.

Well, nice try, that doesn't work because, I assume, Windows initializes the adapter when it gets back in control.

What DOES work is Linux.  I was able to create a bootable Ubuntu USB stick and in under 5 minutes booted the machine into Ubuntu and tested WOL.  It WORKED. Wow.

So what we have is a crappy Windows 10 driver that doesn't support WOL, at least not with ANY combination of windows settings I've tried.

There have got to be 10s of 1000s of OptiPlex 760s (and not to mention other models with this common adapter) out in the wilds of the business world, and Microsoft and/or Intel, with this stunted driver, has basically shat all over the owners with regards to the management of these computers with these adapters.  If I was a IT guy for a company with 1000 of these and couldn't wake any up to do remote management, I'd be pretty damn grumpy.  I'm grumpy now and I only have 10 of these.

Way to go WinTel.

So, back to the original problem...anyone have any ideas on how it might be gotten to work?

Custom Driver?

Hack current driver?

New driver not commonly known?

Some setting I've missed?

Anything...anything to make this work.

Hello,

I am new to this community. I subscribed to ask a question here because I am really stuck.

My company makes electronic devices that use UDP 100 MB Ethernet communication with a PC (under Windows 7, 8.1 or 10).

It works perfectly with other brands of Ethernet adapters; but there is a strange behavious with the Intel NICs we tried (at least I219-V, I219-LM and I217-LM).

Basically, our electronic devices can be considered as cameras capturing about 150 images per second.

We send a small command on one socket via UDP to tell it to capture an image, then we receive the compressed image as a set of UDP packets on another socket.

Each packet contains up to 1444 bytes of data (to which one can add the data from the different layers of protocols, which in the end does not exceed the standard packet size => no need to use Jumbo packets).

The problem is that, sometimes (this varies from as often as every 5 seconds to as rarely as only once within a 10-mn period), I am waiting forever (until the defined UDP time out) for the data to arrive while it has been sent (I can see it by sniffing the data from another computer connected to the same switch). I could believe that the UDP packet was lost by the Intel NIC, but it has not been lost. If I send a new image capture command, the packets that I was waiting finally arrive, followed by the packets of the new image.

Why are those packets stuck?

Is there any advanced parameter that I could modify from the device driver's configuration window or from a Registry key?

Note that I tried updating the Intel driver to recent versions (last one is 22.4.0.1). It seems to perform a little better that some other versions I tried (like the one installed by default in Windows), but none of the versions I tried work perfectly.

Many thanks in advance if you can help me understand what is wrong (either from me or from the driver). I have been struggling on this problem for months and we have to equip our customers who own a laptop with an Intel NIC with USB adapters with a NIC made by another brand to bypass the problem.

Karl

I was looking at picking up a few x550-T2 Ethernet adapters. Driver support for Windows Server 2012 R2 is confirmed on these pages:

Intel® Ethernet Controller X550-AT Product Specifications

Intel® Ethernet Converged Network Adapter X550 Product Brief

Intel® Ethernet Adapters Supported in Windows Server 2012 R2*

However, when trying to download the driver from here, I can't find it:

Downloads for Intel® Ethernet Converged Network Adapter X550-T2

Where is the 2012 driver?

I'd also like to confirm that the x550-t2 is using the x550-at2 controller as listed below and not the x550-bt2. The bt2 has physical support for 8 pcie lanes versus only 4 pcie lanes in the at2 which is an issue if one doesn't have pcie 3.0 slots. I just want to know the limitations before purchasing.

Intel® Ethernet Converged Network Adapter X550-T2 Product Specifications

Greetings, Intel Community Members.

I have been testing a direct connection between two eSXI 6.5 hosts both with Intel 10 Gbit FA DA cards in them.

I have tried both PCI Passthrough and normal and no matter what I do, no matter how many settings I change in the drivers, windows settings you name I am unable to get over 1.56gbps between the two.

Before you suggest a bottleneck of disks, they both do 900MB/sec Read and 600MB/sec Write so it is not that.  I am at a loss, tried other cables etc and I am just stumped. 

I am using iperf to do the tests between the two but like I said it literally will not budge above 1.56gbps.  The cards are both in pcie 3.0 x8 slots, I have also went into both bios and disabled the "Memory Mapped IO above 4GB" setting.

Any clues or ideas would be appreciated.

Thanks

I currently have two Intel NICs teamed as Team #0.

I'm trying to break the team to use each adapter independently, however, when I try to configure the team via "Intel(R) Advanced Network Services Virtual Adapter" I get a vague error, "GetTeamInfo failed" and the "Settings" tab is empty.

I've tried running the ProSetCl command line tool and it tells me there is no Teams installed.

I've also tried uninstalling the "Intel(R) Advanced Network Services Virtual Adapter" adapter and get a different error message "Teams cannot be removed if a virtual NIC is bound to the team. Remove the virtual NIC before deleting the team." As far as I can tell there is no virtual NIC installed on my machine.

How can I force the removal of the Team #0 adapter so that I can use the individual NICs separately? I appreciate any help/guidance you can provide.

Thanks

Ethan

I have the same problem with kernel 4.4.77, ixgbe driver version 5.2.1 and ixgbevf 4.2.1. OS ALT Linux.

Spoof cheking was disabled, but no ping in two VM with the same vlan.

dmesg host:

[162311.173561] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

[162313.177679] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162315.181748] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

[162333.211099] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162337.217085] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162339.220074] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

# ip li show eth0

7: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000

    link/ether a0:36:9f:25:80:5e brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 1 MAC da:55:a4:db:0f:d5, spoof checking off, link-state auto, trust off, query_rss off

    vf 2 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 3 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 4 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 5 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 6 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 7 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 8 MAC 9a:1f:86:df:b1:d8, spoof checking off, link-state auto, trust off, query_rss off

    vf 9 MAC aa:b7:85:e1:1b:06, spoof checking off, link-state auto, trust off, query_rss off

    vf 10 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 11 MAC 9a:1f:86:df:b1:d8, spoof checking off, link-state auto, trust off, query_rss off

    vf 12 MAC aa:b7:85:e1:1b:06, spoof checking off, link-state auto, trust off, query_rss off

    vf 13 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

hi,

     I want to set the rx rate for one vf, currently i found txrate can be set by command: ip link set eth2 vf 0 rate 1000

i check the ip link help message, only see rate TXRATE in red color.

[root@c0209 ~]# ip link help

Usage: ip link add [link DEV] [ name ] NAME

...

       ip link set { dev DEVICE | group DEVGROUP } [ { up | down } ]

                      [ vf NUM [ mac LLADDR ]

                   [ vlan VLANID [ qos VLAN-QOS ] ]

                   [ rate TXRATE ] ]

                   [ spoofchk { on | off} ] ]

                   [ query_rss { on | off} ] ]

                   [ state { auto | enable | disable} ] ]

i want to know how to set the rx rate for individual vf.

OS:centos7.2

NIC: Intel 82599ES

Many Thanks

majorin