Sign Up for the Quarterly Newsletter

USB Network Native Driver for ESXi

Log In to Comment

Closed

#2 MTU MORE THAN 1500

  • Txarly89 • Feb 12, 2019

    I am testing the driver with the USB adapter( Dual StarTech USB 3), and now there is not problem with the loss of packages. But I have seen that when i am going to put the MTU in DVS to 1600 for NSX, it's appear that is ok but when you see the

    log from vmkernel.log

    "
    2019-02-12T20:31:02.864Z cpu0:2097208)WARNING: UetherUplinkMTUSet:432: Set MTU is not supported: Failure
    2019-02-12T20:31:02.864Z cpu0:2097208)WARNING: Uplink: 15740: Failed to set MTU to 1600 on vusb1"

    and when i put the command esxcli network nic list--> The MTU doesn't change

    Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
    ------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
    vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full f4:4d:30:6a:4c:af 1500 Intel Corporation Ethernet Connection (4) I219-V
    vusb0 Pseudo uether Up Up 1000 Full 00:0a:cd:2d:7f:22 1500 ASIX Elec. Corp. AX88179
    vusb1 Pseudo uether Up Up 1000 Full 00:0a:cd:2d:7f:23 1500 ASIX Elec. Corp. AX88179

    I have the adapter dual StarTech USB 3 with the hardware NUC Baby Canyon and the last esxi 6.7 build 1675023

    Thankyou

  • Jose Gomes • Feb 12, 2019

    Hi,

    The ASIX driver doesn't support an MTU size greater than 4k. I assume you meant 16k on your comment above…
    Even the Realtek driver doesn't support anything above 9k (which is normally the case) if you really mean 16k, no USB adapter will support that;

    Regards,

    Jose

  • Txarly89 • Feb 12, 2019

    Hi Jose!

    The default MTU in the VDS is 1500 bytes but if you want to use NSX, you have to increase until to 1600.
    In this point is the error, in the previous there was no problem to put the MTU in 1600 bytes.

    I will hope that that with this commentary is clear

  • Visitor • Feb 12, 2019

    Having the same problem on r8152. The old vmkusb driver can do 9000MTU, but I get this error with this fling:

    Operation failed, diagnostics report: Unable to set MTU to 9000. The following uplinks refused the MTU setting: vusb0

  • aviegas • Feb 17, 2019

    As far as I can determine settings like MTU, duplex and even speed are immutable with this driver. Also, link always shows as "Up", even if there is no cable connected.

  • TomZ • Mar 22, 2019

    I agree with those above. Having a consolidated driver is awesome. It would be great if we could set the vusbX adapter to at leat 1600 for NSX support. Also, those working with NSX-T. You can apply vusb0 to the physical NIC on the N-VDS even though it does not show up in the drop down list. Just type "vusb0" and it will be applied.

  • Mark Snelling • Mar 25, 2019

    I am using the ANKER Aluminum USB 3.0 to Ethernet Adapter (r8152) with this Fling and cannot set the MTU to 9000.

    Key
    haTask-ha-host-vim.host.NetworkSystem.updateNetworkConfig-3342726812

    Description
    Network configuration information

    State
    Failed - An error occurred during host configuration.

    Errors
    Operation failed, diagnostics report: Unable to set MTU to 4000. The following uplinks refused the MTU setting: vusb0

  • malumbaugh • Apr 11, 2019

    I have the plugable model USB3-E1000 and can't get the MTU to go to anything over 1500. This is a deal breaker for me. The USB NIC is useless to me until then

  • Visitor • May 23, 2019
  • William Lam • Jun 17, 2019

    Jumbo Frames is now supported w/latest 1.1 release

  • virtualex • Dec 02, 2019

    Jumbo frames support is still limited to 4000 in these releases. Can we please get support for 9000? There are many use cases that require 9000 support, and currently, I cannot add a StarTech dongle (RTL8153) that supports 9000 to a vSS/vDS that's configured with 9000.

  • Jose Gomes • May 24, 2020

    Tye StarTech adapters are ASIX based, so the maximum MTU is 4000. As mentioned above, MTU up to 9000 is available when using RTL8152 based adapters.

    It's with noting that even with the latest release of the drivers, ingress and agrees speeds are not the same...