VMware Flings Flings

Go back to fling details

New Comment

focheur91300

Nov 19, 2021

Hi,

I have an EXSI with two adapters that I just upgraded.

Update of ESXi-7.0U2d-18538813 to ESXi-7.0U3b-18905247

This is done in the following ways:

1 - I have deleted the old version ESXi702-VMKUSB-NIC-FLING-47140841-component-18150468
2 - Reboot
3 - Installation of ESXi-7.0U3b-18905247
4 - Reboot
5 - Installation of ESXi703-VMKUSB-NIC-FLING-51233328-component-18902399
6 - Reboot

I do have the two adapters that are UP.

I work on Distributed Switch.

The only problem is that the vusb disengages from the Distributed Switch with the reboot of the ESXI.

I have to reconfigure them in VCenter.

Before the update no problem.

Does anyone have any ideas?

Thank you in advance.

Yann@Paris

Jun 16, 2022

Hi, I've got the same issue.

2 USB NIc for Aggregate iSCSI with a Distributed Switch.

The reboot make the Uplink as unconfigured. I need to reconfigure-it after every reboot.

Did you find any solution ?
Best
Yanni

i HAVE**

Using AutoDeploy. Loaded VMware-ESXi-7.0U3b-18905247 and the latest USB fling.

Ran the ISO export and got this error:

I suspect this latest USB driver is incompatible.. Any ideas?

jlmj2009

Feb 06, 2022

FYI, I have the same issue....

I'm using scripts that are tried and tested from earlier v7 releases but it doesnt work on 7.03UC

PS C:\Users\username\Desktop\build> Export-ESXImageProfile -ImageProfile $newProfile -ExportToIso -filepath ESXi-7.0U3c-19193900-standard-NUC.iso
Export-ESXImageProfile : Error retrieving file for VIB 'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328': ("<zipfile.ZipExtFile name='vib20/vmkusb-nic-fling/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib'
mode='r' compress_type=deflate>", "Error opening file object for VIB 'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328': Expected value '[]' for attribute 'swplatforms', but found value
'[<vmware.esximage.Vib.SoftwarePlatform object at 0x0000020C63000088>]'.").
At line:1 char:1
+ Export-ESXImageProfile -ImageProfile $newProfile -ExportToIso -filepa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Export-EsxImageProfile], SoapException
+ FullyQualifiedErrorId : System.Web.Services.Protocols.SoapException,VMware.ImageBuilder.Commands.ExportProfile

El Capitán

Feb 11, 2022

@jlmj2009 I too ran into the same issue ...

so I tried ExportToBundle instead and it worked like a charm. I was upgrading from 7.0U2 so I didn't really need the ISO. The upgrade to 7.0U3c went smoothly from the host CLI. Nuc was able to rejoin my 3 node vSAN cluster and I was back up and running in no time. USB nic was recognized and connected on boot up.

PowerCLI:
Export-ESXImageProfile -ImageProfile ESXi-7.0U3c-19193900-USBNIC -ExportToBundle -Force -filepath ESXi-7.0U3c-19193900-USBNIC.zip

CLI on host:
esxcli software profile install -p ESXi-7.0U3c-19193900-USBNIC -d /vmfs/<volume_name>/ESXi-7.0U3c-19193900-USBNIC.zip

Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true

Best of luck!

jlmj2009

Feb 11, 2022

Thanks, that did the job for me. I was building the .zip file anyway using Export-ESXImageProfile but was using the ISO to perform the upgrade. However, I was able to take the zip and apply that using the CLI on the host command. Worked fine. Appreciate you taking the time to provide a workaround.

El Capitán

Feb 11, 2022

Awesome! Glad to hear that.

Derek

Jan 29, 2022

Update to post: Now using 7.0u3c-19193900-standard with vCenter 7.0.3.00300

ISO export pulls similar error. Still think there is a compatibility issue that needs to be resolved.

An error occured while performing the task<br/>(None, None, 'Error retrieving file for VIB \'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\': ("<_io.BufferedReader name=\'/storage/imagebuilder/vibs/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\'>", "Error opening file object for VIB \'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\': Expected value \'[]\' for attribute \'swplatforms\', but found value \'[<vmware.esximage.Vib.SoftwarePlatform object at 0x7fc105c57cd0>]\'."); ("<_io.BufferedReader name=\'/storage/imagebuilder/vibs/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\'>", "Error opening file object for VIB \'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\': Expected value \'[]\' for attribute \'swplatforms\', but found value \'[<vmware.esximage.Vib.SoftwarePlatform object at 0x7fc1042f9a90>]\'."); ("<_io.BufferedReader name=\'/storage/imagebuilder/vibs/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\'>", "Error opening file object for VIB \'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\': Expected value \'[]\' for attribute \'swplatforms\', but found value \'[<vmware.esximage.Vib.SoftwarePlatform object at 0x7fc105c57950>]\'."); ("<zipfile.ZipExtFile name=\'vib20/vmkusb-nic-fling/VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328.vib\' mode=\'r\' compress_type=deflate>", "Error opening file object for VIB \'VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328\': Expected value \'[]\' for attribute \'swplatforms\', but found value \'[<vmware.esximage.Vib.SoftwarePlatform object at 0x7fc1042f9550>]\'.").')

Derek

Nov 18, 2021

Additional Update: Using VMware PowerCLI we get a little more descriptive on the issue.

PS D:\esx> Export-EsxImageProfile -ImageProfile esxcustom .\esxcustom.iso -ExportToIso -Force
WARNING: The image profile fails validation. The ISO / Offline Bundle will still be generated but may contain errors and may not boot or be functional. Errors:
WARNING: VIB VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328 requires vmkapi_incompat_2_9_0_0, but the requirement cannot be satisfied within the ImageProfile.
WARNING: VIB VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.703.0.15.51233328 requires vmkapi_2_9_0_0, but the requirement cannot be satisfied within the ImageProfile.

goblin

Nov 15, 2021

Ever since I followed these steps on my NUC10i7FNH (with the onboard ethernet as management NIC and a single UGREEN AX88179 USB NIC attached):

- while running ESXi 7.0 U2d, uninstalled ESXi702-VMKUSB-NIC-FLING-47140841-component-18150468.zip, and reboot
- updated to 7.0 U3a, and reboot
- installed ESXi703-VMKUSB-NIC-FLING-51233328-component-18902399.zip, and reboot

My vswitch that uses the USB NIC now shows no uplink/physical adapter after a reboot. The USB NIC appears to be enabled in the GUI, and when I edit the vswitch, it shows the uplink, but when I boot up a VM on that vswitch, it definitely gets no network. I have to edit the vswitch, delete the uplink, save it, then add the uplink back in, save it, and it works only until the next reboot. Updated to 7.0 U3b and still seeing the same issue. Everything worked great with 7.0 U2d with the USB NIC persisting just fine through reboots.

Anyone seeing the same or have any ideas?

Stephan

Nov 18, 2021

I experienced the same issue. My solution is a bit nasty, I added the following commands after esxcfg-vswitch -R.

sleep 2
esxcli network nic down -n vusb0
sleep 2
esxcli network nic up -n vusb0

Maybe it will work for your setup as well.

Adriano Fante

Nov 04, 2021

Is there a date for release the new version compatible with Esxi 7.0 U3 ?

Stephan

Nov 10, 2021

Version 1.9 of the driver works with the ESXi-7.0U3a-18825058 standard.
Perhaps there should be a brief guide on how to upgrade from older versions. Below you can see how I did it:
1. Remove older Fling drivers, if any: esxcli software component remove -n VMware-vmkusb-nic-fling
2. Update to the latest profile supported by the driver
3. Install the new driver that corresponds to the Flings driver.
4. Reboot
5. You may have to remove the USB network card from the virtual switch in VMware. This could be the case due to the settings of /etc/rc.local.d/local.sh. With the official guide here, it shouldn't be necessary.

USB Network Native Driver for ESXi