The example script for Distributed Virtual Switch under Option 2 has a typo in line 6, it's missing the closing bracket on vusb0_status= Thanks for your work on this, adding NIC's on a NUC is a lot more cost-effective using USB adapters than buying the model with extra built-in. :)
The example script for Distributed Virtual Switch under Option 2 has a typo in line 6, it's missing the closing bracket on vusb0_status=
Thanks for your work on this, adding NIC's on a NUC is a lot more cost-effective using USB adapters than buying the model with extra built-in. :)
Apperciate the catch Chris! I've just fixed
There have been vusb detection meccano changes in ESXi 8.0 Update1. Here some findings.
For example, the ISY IAD-1025 USB-C 6-in-1 adapter and the Satechi Typ-C 2-in-1 USB 3.0 USB-Hub adapter, both have built-in an ethernet port. Without the vmkusb fling in the past ESXi releases, the nic port wasn't detected and configured. With ESXi 8.0 Update1, during provisioning with that single nic there is still the message of no 'NIC for management network', but the nic can be configured manually. By applying the modifications recipe (see bottom), it shows up as Name vusb0, Driver cdce, Speed 100, Duplex Full and Description Realtek USB 101001000 LAN.
ESXi 8.0 Update1 contains the vmkusb module version 0.1-16vmw.801.0.0.21495797.
ESXi 8.0 Update1 with installed vmkusb fling v1.12 contains the vmkusb_nic_fling module version 1.12-1vmw.801.0.0.64098092 and the unloaded vmkusb module.
It's still necessary to mark+save the vusb0 network adapter for example in ESXi DCUI explicitly with a cross, even with status "connected" already.
The vusb driver has changed to "uether". The vusb0 link speed shows up as 100 Mbps, full duplex, but now it can be changed to auto-negotiate/1000 Mbps, full duplex/100 Mbps, full duplex/10 Mbps, full duplex.
When changing to 1000 Mbps, full duplex, the link speed shows up correctly, but by pressing the Refresh button, it switches back to 100 Mbps, full duplex.
With respect to the v1.12 requirements, as expected the vmkusb fling cannot detect an onboard Realtek nic (10ec:8168).
It wasn't possible to update from ESXi8.0c with vmkusb fling v1.11 to ESXi8.0U1. Neither the update to vmkusb fling v1.12 nor the update to ESXi8.0U1 worked.
Uninstalling the vmkusb fling v.11 was possible, but installing the vmkusb v1.12 bits not. A fresh installation of ESXi8.0U1 and then an update to vmkusb fling v1.12 finished successfully. I've read from other users that with vSphere Lifecycle Manager the remediation to ESXi8.0U1 with included vmkusb fling v1.12 works flawlessly. Didn't invest time to reproduce the own constellation.
A plugged-in ISY IAD-1025 USB-C 6-in-1 adapter cascaded with usb-c attached Satechi Typ-C 2-in-1 USB 3.0 USB-Hub adapter does not work. Neither vusb0 nor vusb1 are configured.
So far the tinkering.
The most awesome vmkusb feature is APD handling. Simply unplugging the usb-c adapter and reconnecting it works like a charm.
# Start ESXi 8.0 Update1 install until screen no 'NIC for management network'.
# Switch to ESXi Shell
# add vSwitch0
localcli network vswitch standard add --vswitch-name="vSwitch0"
# add vusb0 to vSwitch0
localcli network vswitch standard uplink add -u vusb0 -v "vSwitch0"
# add the Management Network portgroup
localcli network vswitch standard portgroup add --portgroup-name="Management Network" --vswitch-name="vSwitch0"
# list the vSwitch0 configuration
# configure vmkernel network interface
esxcfg-vmknic --add --ip DHCP --portgroup="Management Network"
# A message appears "GetManagementInterface: No interface was tagged for mgmt, selecting new one VmkNic: ProcessTagChanges: Refreshing DCUI after adding management vmknic"
# Leave the console
# Press ALT-F2
With ENTER the setup dialog restarts. Do the (same) config and this time the setup should finish successfully.
Withouth any automation for example with a local.sh, in ESXi DCUI the vusb0 network adapter has explicitly to be marked with a cross, even with status "connected" already.
Are there any USB fling driver updates needed when running the latest Vsphere 7.03l (the latest as of the date of this post) ?
I have literally tried just about every USB 2.5G adapter (specifically the ones that had been referenced as tested at one point) and have the same general issue. I was able to get them working without issue - device recognized, connects at 2.5Gbps, and passes traffic without issue. The problem is I can't get the MTU above 1500. I know there was an issue with 9000 MTU, so I tried 4000, and even lower (assigned these lower values to the vSwitch) - no luck. I know it has to be the USB NIC as the EXACT same tests with my current 1G / Onboard / PCI NIC work perfectly - even up to 9000 MTU. The USB adapters also work with MTU of 9000 when directly connected to my Windows or MAC laptop.
Some of the ones I tested:
CLUB 3D CAC-1420
Cable Matters 201090-N
Any help would be greatly appreciated!
Using latest ESXi 8.0 Update 1. Getting dependencies warning. Is it ok to ignore?
On platform embeddedEsx, VIB VMW_bootbank_vmkusb-nic-fling_1.11-1vmw.800.1.20.61054763 requires vmkapi_incompat_2_10_0_0, but the requirement cannot be satisfied within the ImageProfile.
No, it is not okay to ignore.
With each major release of ESXi (includes Update releases), a new version of the Fling needs to be built/tested. We're currently working on an update, which also includes some additional fixes/enhancements, so please wait until that is available before you upgrade or you will lose USB networking as the current version is NOT compatible, hence the error
I am sure I'm not alone in *really* appreciating the time and effort you guys put into this fling and I look forward to a U1 compatible version :-)