Please provide your feedback in this short Flings' survey.
Jan 30, 2022

Problem (Persistence of vusbX to DVS post reboot)

This is a three node lab using lenovo's (m700) and before moving to VSAN/NSX i would like to get the network rock solid and surviving reboots (persistent).

I have followed the various blogs and scripts out there. But have hit a roadblock as I suck at scripting. Any insight is appreciated. The USB nics, IPs, etc are persistent upon reboot. Following this blog: and some
of William's blog posts.

Lab Configuration

[root@esxi0:~] esxcli network nic list |grep vusb |awk '{print $1, $8}'
vusb0 7c:c2:c6:2f:53:33
vusb1 7c:c2:c6:2f:24:c0

[root@esxi0:~] esxcli system module parameters list -m vmkusb_nic_fling
Name Type Value Description
--------------------------- ------ ----------------- -----------
usbBusFullScanOnBootEnabled int Enable USB Bus full scan on system boot: 0 No (Default), 1 Yes
usbCdromPassthroughEnabled int Enable USB CDROM device for USB passtrough: 0 No (Default), 1 Yes
usbStorageRegisterDelaySecs int Delay to register cached USB storage device: Min: 0 second, Max: 600 seconds, Default: 10
vusb0_mac string 7c:c2:c6:2f:53:33 Persist vusb0 MAC Address: xx:xx:xx:xx:xx:xx
vusb1_mac string 7c:c2:c6:2f:24:c0 Persist vusb1 MAC Address: xx:xx:xx:xx:xx:xx

The persistence issue is the vusbX (physical adaptor) rebinding to the DVS and PortGroup. In the GUI all I have to do is click on manage physical adaptor and rebind and (done, working). There is no other persistence issues but this binding does not survive reboot.

Any ideas on adjusting the below script to fix the problem or any suggestion, welcomed.