Hi Ben,
Try adding the "restart" lines shown below, this helped me with the persistence issues I was having. Also, make sure the interface names (vusbX) and vswitch reflect what you have configured in esx.
if [ "${vusb0_status}" = "Up" ]; then
esxcfg-vswitch -L vusb0 vSwitch0
esxcfg-vswitch -M vusb0 -p "Management Network" vSwitch0
esxcfg-vswitch -M vusb0 -p "VM Network" vSwitch0
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
fi
Hello,
Thanks a ton for this Fling.
I was able to install it and I can see the adapter via lsusb, but it never shows up in the NIC list:
[root@esx01:/etc/rc.local.d] lsusb
Bus 001 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc.
root@esx01:/etc/rc.local.d] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 54:b2:03:0b:86:e6 1500 Intel Corporation Ethernet Connection (2) I219-V
Any suggestions?
Thanks,
E!
I am also in this boat as is several others in this thread, except the TPLink device for me, what are we missing? Did you solve this?
Can you do graphic tutorials?I can't understand how to operate by looking at the text alone.
Description:
install Installs VIB packages from a URL or depot. VIBs may be installed, upgraded, or downgraded.
WARNING: If your installation requires a reboot, you need to disable HA first.
Cmd options:
-d|--depot=[ <str> ... ]
Specifies full remote URLs of the depot index.xml or server file path pointing to an offline
bundle .zip file.
--dry-run Performs a dry-run only. Report the VIB-level operations that would be performed, but do not
change anything in the system.
-f|--force Bypasses checks for package dependencies, conflicts, obsolescence, and acceptance levels.
Really not recommended unless you know what you are doing. Use of this option will result in a
warning being displayed in the vSphere Client. Use this option only when instructed to do so
by VMware Technical Support.
--maintenance-mode Pretends that maintenance mode is in effect. Otherwise, installation will stop for live
installs that require maintenance mode. This flag has no effect for reboot required
remediations.
--no-live-install Forces an install to /altbootbank even if the VIBs are eligible for live installation or
removal. Will cause installation to be skipped on PXE-booted hosts.
--no-sig-check Bypasses acceptance level verification, including signing. Use of this option poses a large
security risk and will result in a SECURITY ALERT warning being displayed in the vSphere
Client.
--proxy=<str> Specifies a proxy server to use for HTTP, FTP, and HTTPS connections. The format is proxy-
url:port.
-n|--vibname=[ <str> ... ]
Specifies VIBs from a depot, using one of the following forms: name, name:version,
vendor:name, or vendor:name:version.
-v|--viburl=[ <str> ... ]
Specifies one or more URLs to VIB packages to install. http:, https:, ftp:, and file: are all
supported.
There is an type in the instructions page on the script. You have one too many right brackets in the while loop. If you only want to add the nic when the link is up, then it needs to be removed and look like this:
while [[ $count -lt 20 && "${vusb0_status}" != "Up" ]]
I've got a Realtek 8153 USB3 dual NIC and have followed instructions. Sometimes after loading ESXi 6.7, it gives the no supported adapter found. Most of the time, it loads fully and recognizes the NICs, however. DHCP doesn't work, but static assignment works. Good so far.
A problem I haven't been able to solve yet though is with the USB persistence on bootup and connecting the physical adapters to the vswitch where management exists. Having the lines from the instructions in local.sh seems like it would help, but I've found that link detection isn't reliable in my configuration. When one NIC is physically plugged in, vusb0 and vusb1 both show "Link Detected: True" and "Link Status: Up". Also, I can't get vusb0 NIC to work regardless of static IP when connected to vswitch0. If I change physical cabling over to vusb1 and change config again, it works. After a reboot, no mix of vusb0 or vusb1 in the local.sh script seems to help.
Thanks guys for your work on this!