Hi. We have Dell PowerEdge 730s that have Intel X710 cards. LLDP does not work at all. Latest Dell firmware for the card and driver from the VMware HCL. We are running latest ESXi v6.5. I have noticed some threads that LLDP just does not work.
This is very important to us. Is there a time frame when this will be fixed? Thanks,,,
Hello, I've been having trouble with this NIC not booting off of PXE. I've already set the 10Gbe interface as a booting interface in the BIOS. During PXE, I get the error message: PXE structure was not found in the UNDI driver code segment. When it first didn't work, I used nvmupdate64e to update the NIC firmware. nvmupdate now tells me my firmware is up to date (at version 6.01). However, I still get the same exact error message at PXE boot. I have also tried enabling PXE flash firmware for the interfaces. But I still get the same error after all these driver installs and configuration enables.
lspci -vv | grep -i 'Intel Corporation Ethernet Controller X710'
81:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
81:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
./bootutil64e
Port Network Address Location Series WOL Flash Firmware Version
3 6805CA385DF0 129:00.0 40GbE N/A UEFI,PXE Enabled 1.0.66
4 6805CA385DF1 129:00.1 40GbE N/A UEFI,PXE Enabled 1.0.66
ethtool -i eth2
driver: i40e
version: 1.5.10-k
firmware-version: 6.01 0x80003483 1.1747.0
bus-info: 0000:81:00.0
./nvmupdate64e
Num Description Ver. DevId S:B Status
01 Intel (R) I350 Gigabit Network Connection 1.99 1521 00:0001 Update not available
02 Intel(R) Ethernet Converged Network 6.01 1572 00:129 Up to date
Adapter X710-2
Any idea what I need to do to get this interface to PXEboot? eth2 is the interface that I am using.
I just received a few Dell servers to test as replacements for the vendor we currently use for vsphere. I installed ESXi 6.5u1, patched up for spectre/meltdown so I'm now on build 7967591. The servers are hooked into storage via multiple 10gig ethernet paths handled by dual port X710 NIC's:
[root@vm4:~] esxcli network nic get -n vmnic0
Advertised Auto Negotiation: false
Advertised Link Modes: 10000BaseT/Full
Auto Negotiation: false
Cable Type: DA
Current Message Level: -1
Driver Info:
Bus Info: 0000:18:00:0
Driver: i40en
Firmware Version: 6.00 0x800034e6 18.3.6
Version: 1.3.1
Link Detected: true
Link Status: Up
Name: vmnic0
PHYAddress: 0
Pause Autonegotiate: false
Pause RX: true
Pause TX: true
Supported Ports: DA
Supports Auto Negotiation: false
Supports Pause: true
Supports Wakeon: true
Transceiver:
Virtual Address: 00:50:56:5a:d4:93
Wakeon: MagicPacket(tm)
Almost immediately after putting any real load on them, the NIC simply stops passing traffic. What's worse, it remains in an UP state, so vmware never tries the failover link. Seeing this on the vmware side:
2018-04-01T11:30:41.265Z cpu1:65925)StorageApdHandlerEv: 117: Device or filesystem with identifier [e87ff85e-cb1d8034] has exited the All Paths Down state.
2018-04-01T12:39:19.849Z cpu46:66166)i40en: i40en_HandleMddEvent:6495: Malicious Driver Detection event 0x02 on TX queue 0 PF number 0x00 VF number 0x00
2018-04-01T12:39:19.849Z cpu46:66166)i40en: i40en_HandleMddEvent:6521: TX driver issue detected, PF reset issued
That of course lead me to the following two closed threads in this forum:
https://communities.intel.com/thread/117035
https://communities.intel.com/thread/117076
Is it safe to assume this NIC is still broken and will never see fixes, with both sides blaming each other? Can't say it leaves me very happy with Dell either as they knew we were doing vsphere on these, yet they still bundled them.
Hi Intel,
I'd like to get the ULP tool.
Best Regards,
naok
I have issue with i218-LM on Dell E5250. Yellow exclamation mark. Unable to start the network adapter. Code 10.
I tried the latest drivers 12.15.25.6 but without success.
I'd like to give the ULP enable/disable utility a try.
Hello Sharon,
I'm having this issue on my Dell E5250 with a I218-LM and would like to try the ULP tool. Could I get access to it please?
Thanks
I work in IT at a corporation where almost all of our current computers have the Intel Ethernet Connection l218-LM network adapters. I have seen 5 computers in the last 2 months come up with the error where this network suddenly stops working and produces Error Code 10: this device cannot start. I have searched high and low for a solution, and the ULP enable/disable utility is the only thing I haven't tried yet. Can someone please send the utility to me?
Hi all,
I have following baseline:
Dell R630 (2x14 core Xeon, 128GB RAM, 800GB SSD)
x710 4-port NIC, in 10Gbit mode
SUSE12SP1
Latest NIC firmware but default PF/VF drivers (came with OS, v1,3,4)
VF driver blacklisted on hypervisor
Setup according to official Intel and Suse documentation, KVM hypervisor
With test setup, single VM with single VF and untagged traffic, I could achieve basically line-rate numbers: with MTU 1500, there were about 770Kpps and BW of 9.4Gbps, achieved both for UDP and TCP traffic, with no packet drops. There is plenty of processing power, setup is nice and tidy and everything works as it should.
Production setup is a bit different: VM is using 3 VFs, one for each PF (4th PF is not being used). All VFs except first one use untagged traffic. First VF is passing two types of traffic: first one untagged (VLAN 119) and second one tagged (VLAN 1108). Tagging is done inside VM. Setup worked fine for some time, confirming test setup numbers. However, after some time following errors started to appear in hypervisor logs:
Mar 11 14:32:52 test_machine1 kernel: [10423.889924] i40e 0000:01:00.1: TXdriverissuedetected on VF 0
Mar 11 14:32:52 test_machine1 kernel: [10423.889925] i40e 0000:01:00.1: Too many MDD events on VF 0, disabled
And performance numbers became erratic: sometimes it worked perfectly, sometimes it did not. But most importantly, packet drops occured.
So, I've reinstalled everything (hypevisor and VMs), configured exactly as before using automated tools, but upgraded PF and VF drivers to latest ones (v2.0.19/v2.0.16). Errors in logs disappeared, but issue persists. Now I have this in logs:
2017-03-12T11:33:43.356014+01:00 test_machine1 kernel: [ 420.439112] i40e 0000:01:00.1: Unable to add VLAN filter 0 for VF 0, error -22
2017-03-12T11:33:43.376009+01:00 test_machine1 kernel: [ 420.459168] i40e 0000:01:00.0: Unable to add VLAN filter 0 for VF 0, error -22
2017-03-12T11:33:44.352009+01:00 test_machine1 kernel: [ 421.435124] i40e 0000:01:00.2: Unable to add VLAN filter 0 for VF 0, error -22
I've increased VM CPU count number, VF ring sizes, turnet off VF spoofcheck in hypervisor, VM linux software buffers, VM netdev.budget kernel parameter (amount of CPU time assinged for NIC processing) etc. but situation remains the same. Sometimes works perfectly, other time it does not.
Can you please provide some insight? Since rx_dropped counter is increasing in VM, I am suspecting driver/VF issue.
Is there a way to handle this problem, without switching to untagged traffic?
Thank you in advance,
Ante
Hi,
We have had similar issues we are using the Intell X710. Every few weeks since upgrading to ESXi 6.5 the networking on one of our hosts has been locking up. We stumbled across the below article which described the issue well and also mentions disabling the i40en driver.
Install ESXi 6.5 on R730 with Intel X710 |VMware Communities
Note we were on firmware version 1.3.1, did this issue get resolved with an upgrade to 1.4.3 NIC Driver for Intel Ethernet Controllers X710?
Looking in some forums some people ordered new nics to get around the issue.
Craig
Hi.
So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.
Ou snap
Message was edited by: Tiit Talts
This issue was covered here but was NOT resolved and mark answered by accident.
VLANs disabled in Windows 10 Build 17133.1 Version 1803
My steps were as follows
In conclusion, the latest Intel NIC driver 23.1 seems fine but there is something wrong with Windows 10 Build 17133.1 Version 1803 Springs Creators Update, aka Redstone 4.
Hi
We have computers that have Intel AMT enabled. The OOB IP is configured for dhcp but they are not releasing the ip address althought the lease is 24 hrs. Because of that we are having ip address conflicts - the TCPIP stack of one windows machine when it is booted takes a new ip address but the OOB ip of that nic is an old one that conflicts with another windows machine.
Has anyone heard anything about that ? Is this a bug or misconfiguration ?
Thanks a lot
Hello,
I'm having some issues using VLANs on a new system. (See system Specs at Bottom)
Last coupe of days I have tried to update the drivers to make VLANs work on my laptop.
First driver I tried to install went well. I could see The VLAN tab when configuring my network connection.
However when I tried to add a VLAN the laptop gave me a BSOD with BAD_POOL_CALLER as error message.
I tried to reinstall a couple of times, rebooted a few times and it alway repaired itself to the previous Driver installed.
Driver used: Download Intel® Network Adapter Driver for Windows® 10
After some searching on the web I found that alot of people had an issue like this. There was a problem with the ProSet option during the driver installation and one post suggested another driver provided by Intel that would fix the issue crashing.
Using this driver solved the BSOD issue, but whenever I make a VLAN, it deactivates itself. activating it doesn't work, it just stays deactivated.
Driver used: https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=...
After some searching on the web I found this article from 2016 saying that VLAN or teaming or not supported by windows 10 with the ProSet driver.
Because it was an old article I searched for a more recent one and found this.
So I tried to install every driver beginning from the newest one and ending on 22.3 as the article says following:
Every driver has these same issues.
Driver page: Download Intel® Network Adapter Driver for Windows® 10
Anyone here who had/has similar issues?
Are there any known solutions for these issues?
Best regards,
Bert
----------------------------------------------------System Specifications
Manufacturer:Lenovo
Model: X1 Carbon
OS: Windows 10 Pro 64 Bit
Processor: Intel(R) Core(TM) i7-7500U CPU @2.70GHz 2.90GHz
RAM: 16GB
Ethernet adapter: Intel(R) Ethernet Connection (4) I219-V
----------------------------------------------------
Hi, we have been redirected here from this thread in the embedded community: ARM tools for 82574 |Embedded Community
To summarize the important parts of our previous discussion, we have an Intel EXPI9301CT Gigabit CT PCI-e Desktop Adapter, which has an 82574 controller and a Winbond W25X40BVNIG flash. We are trying to use the eepromARMtool to reprogram the MAC address in the flash.
Running ./eepromARMtool -dump -NIC=1 gives us a file whose first line is:
8888 8888 8887 0C20 F746 2014 FFFF FFFF
We want to change the MAC address, so we edit the file that was dumped and change the first line to:
70B3 D501 C307 0C20 F746 2014 FFFF FFFF
Then we run ./eepromARMtool -write -NIC=1 -f=new_mac.otp. If we run the dump command again, the flash appears to have the correct contents. However, if we reboot or power cycle the machine and dump again, the output has returned to its original contents. This seems to imply that our changes were not actually flushed to the flash.
Do you have any advice for how to fix this problem? Thank you!
Hi,
We have been having the same problem since last October when we upgraded to esxi 6.5 and in turn started using the i40en nic driver. With this driver on every few weeks one of our hosts locks up. This post nails the problem better than I can describe Install ESXi 6.5 on R730 with Intel X710 |VMware Communities
Our workaround was to downgrade to the i40e version, unfortunately doing this makes VMware non compliant in update manager and because us IT guys have serious OCD its very annoying. It's also not good as we like to keep a visual view of these hosts so we know when to patch them.
Is this issue going to be fixed? Just to note on more than one occasion we have had production hosts go down because of this issue and we have had to explain to our staff.
Regards
Hello,
We have the same issue. We have 30 Huawei servers with Intel X710 card and vsphere 6.5 u1 patch2. VM network connections on a Distributed Virtual Switch seem to freeze after this error appears in vmware logs:
"2018-03-30T07:35:50.216Z cpu5:66200)i40en: i40en_HandleMddEvent:6495: Malicious Driver Detection event 0x02 on TX queue 0 PF number 0x00 VF number 0x00
2018-03-30T07:35:50.216Z cpu5:66200)i40en: i40en_HandleMddEvent:6521: TX driver issue detected, PF reset issued
2018-03-30T07:36:20.213Z cpu48:70776)WARNING: NetPort: 1934: failed to disable port 0x300000d on DvsPortset-0: Busy
2018-03-30T07:36:20.213Z cpu48:70776)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic1: received a force quiesce for port 0x300000d
2018-03-30T07:36:20.213Z cpu48:70776)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic1: dropped 501 pkts from queue netsched.pools.vm.50331661 while quiescing port 0x300000d"
After this, multiple Dvs ports fail and packets are dropped (vmnic1: dropped 501 pkts from queue).
This has happened on 3 ESXi servers already, causing downtime on VMs.
The logs show the same sequence of events on all 3 servers:
Only way to recover the VM networking is to vMotion to a different host.
I am attaching the vmkernel log file for this server. Issues start at 2018-03-30T07:35:50.216Z
We are really DESPERATED... We are working in big migration project and we are totally frozen!!!
We have tried to installed the last drivers "1.5.8" and the issue happends again.
NEED URGENT HELP!!!
I210-IS In both PMON and Linux, the ID is identified as 1538, but the connection cannot be connected if the network cable is plugged in.
We have 8 brand new HPE DL380 Gen10 servers. Each of these servers has two HPE Ethernet 10Gb 2-port 562SFP+ Adapters. One is embedded and one on a PCI card. This card is based on the Intel X710 controller
HPE Ethernet 10Gb 2-port 562SFP+ Adapter OID8245220 | HPE™
We hooked two DAC cables, one from each card to our Juniper switch. The two ports on the Juniper switch are standard access ports. After installed the HPE customized version of ESXi 6.5 U1 we went into the console and added the two nics. We put in an IP address, gateway, mask, and DNS servers and then rebooted the host. During reboot we had a continuous ping going to the IP address of the ESXi management interface. The ping returned part way through the boot process and after fully booted the ping stopped. If I remove one of the 10Gb nics from the management network, the ping returns. If I use two of the 1Gb interfaces on this server which are based on a Broadcom chipset, the management interface works fine. The server has had all of its firmware upgraded. We are running driver version 1.5.8 and firmware version 10.2.5. The firmware came from here, I think it corresponds to VMWare's version of firmware 6.00
Drivers & Software - HPE Support Center.
I have a ticket opened with HPE but wanted to find out if Intel might have a solution for this
I also have teaming problem with I350-T2 + I219V
I use win10 64-bit with build 14393.2214 (released at 17th, April) and the latest driver (Download Intel® Network Adapter Driver for Windows® 10 )
I can successfully teaming these two adapters(using intel ANS adaptive load balancing), and it works fine in normal situation.
BUT, its fail-over function doesn't work at all.
Here is how I test fail-over function:
I connect with 3 client pc and use Iperf2.0.10 to test the connection speed.
Then, I intentionally disable one adapter, theoretically, it will continue connecting with all 3 pc with a lower speed(which I saw under win8), but the result I see is connection abort (sometimes one or two of them, sometimes all) with two kinds of error message : "write failed, connection reset by peer" or "software cause connection abort".
This problem didn't happen under win8 I test couple weeks ago.
Does anyone have any idea?
Hey!
So I bought two of these NICs and a Dell PowerConnect 2816 to connect two computers with up to a 4Gigabit connection when teamed. The issue is, I can't seem to get the drivers to install properly in windows. ProSet seems to instal for my motherboard built in NIC, which is also INTEL Gigabit-but I dont wan't to team that-I just want a team of the 4 ports on the add in card. According to every single thing I have seen on google, there should be a teaming tab when I click "configure" on one of the Pro 1000PT connections, but it doesn't seem to exist anywhere, and Windows installs the drivers for the device automatically. I have tried installing the latest drivers, but again, it just shows the default Windows drivers installed. Help!
Thanks so much,
Rowan