Flings

 View Only

 USB Network Native Driver for ESXi ESXi80U3 repeatedly disconnects and reconnects

Takumi Takahata's profile image
Takumi Takahata posted Jun 27, 2024 01:13 AM

After upgrading to ESXi 8 Update 3 and USB Network Native Driver for ESXi ESXi80U3(75399077), the NIC started disconnecting and reconnecting repeatedly every second.

The configuration used is as follows:

  • Host: NUC 13 Pro Kit NUC13ANHi7 + Intel LAN and USB Add-on Assembly Module NUCIOALUWS
  • USB NIC: AS-U2.5G2 (Chipset RTL8156B)

Since I am using only one USB NIC, I chose Option 1 from Persisting USB NIC Bindings.

Before the update, I was using ESXi 8 Update 2 and Driver ESXi80U2(67561870) and there were no problems.

To troubleshoot the issue, we have tried the following:

  • Physically removed the USB NIC from the NUC and reconnected it
  • Restarted the ESXi host and started it up from a shutdown

I also connected the USB NIC to a Windows environment and it worked without any issues.


The following log is output every second in the ESXi events in vSphere Client.
This situation has been output immediately after the update.

Description:
Physical NIC vusb0 linkstate is down.
Related events:
There are no related events.


Description:
Physical NIC vusb0 linkstate is up.
Related events:
There are no related events. 

There is no information in the changelog, but have there been any changes to the Chipset RTL8156B NIC?
Also, has anyone experienced the same symptoms?

I would appreciate it if you could let me know if there is a way to avoid this by changing the settings.

Thansks.

Attachment  View in library
durdin's profile image
durdin

Hi, I've updated the lab today to 8u3 with NIC fling to 1.14-1. I've tested the USB adapter from D-LINK: DUB-1312 (chipset AX88179) and with this adapter, everything works fine. However, with another adapter from D-Link: DUB-2315 (chipset RTL8156B), I am experiencing similar or same symptoms. Whatever I do, the link goes immediately down and several events appear in events reporting link going up and down. I've tried also setting the speed manually to all possible options (2.5, 1, auto) and this does not have any effect. With previous fling version 1.12 everything worked fine, so I bet there's some code change preventing the adapter to work reliably. I guess for now best option would be to not to upgrade to U3, try downgrading fling, or pick different adapter, until this thread is noticed by someone who could actually check the code.

durdin's profile image
durdin

Hi, After a bit digging seems the great Willam Lam already had solution for couple of weeks in the discussion part of following blog post - williamlam.com: 2024/06 nested-esxi-virtual-appliance-usb-network-native-driver-for-esxi-for-vsphere-8-0-update-3

There's link to updated debug version of fling which fixes the problem, but as it's debug version with extended logging etc, I recommend installing it only on systems where the problem is occurring and they are not production-critical machines. 

Direct link to vib: VMW_bootbank_vmkusb-nic-fling_1_14-2vmw_803_0_0_76444229.vib

Nikolay Utyaganov's profile image
Nikolay Utyaganov

Hello,

I'd like to confirm that the solution offered by William Lan and reported here by @durdin (debug version 1.14-2 of USB NIC fling VIB) really works - tested with both 1G RTL8153 and 2.5G RTL8156 adapters. No more link up/down every second!

BTW, in my case the adapters based on AX88179 chit didn't suffer the problem with version 1.14-1

Anyway, thanks a lot for the solution - and looking forward to see the regular release of ver.1.14-2 !

Takumi Takahata's profile image
Takumi Takahata

Developer William Lam announced the release of a fixed version.

https://x.com/lamw/status/1821592254731186562

After applying ESXi80U3 (76444229), the RTL8156B NIC problem seems to be resolved.
It no longer disconnects and connects at least every second.
Also, the PSOD seems to have been addressed as well.

Thanks to William Lam and the other developers of the modified version, to those who provided him with the support bundle, and to those who provided information in this thread.