@GD,
From the log, it seems you are still using the legacy driver which you installed before, which means the native driver you installed have not enabled.
Would you please try the commands to confirm the above assuming?
#localcli system module list | grep usb
Thanks,
Songtao
Thank you Songtao. I reinstalled the driver and now I think it's ok:
[root@esxi1:~] localcli system module list | grep usb
vmkusb_nic_fling true true
vmkusb false false
[root@esxi1:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vusb0 Pseudo uether Up Up 1000 Full 00:0a:cd:24:c7:d3 1500 ASIX Elec. Corp. AX88179
[root@esxi1:~] localcli system module list | grep usb
usb true true
usbnet true true
usb-storage true true
vmkusb false false
Has anyone found a reliable solution to the NICs dropping out of the vswitch upon hypervisor reboot?
I'm having great performance on a Sophos XG install using an RTL8153 for a 2nd nic on a micro pc, if I can resolve the reboot issue this will be my new permanent firewall.
Thanks a ton to the devs, and I look forward to any updates!
Disregard. For any other fools like me, read the instructions page instead of blindly installing the driver and testing!
Hi William.
I have below problem with USB network adapter. System is installed with Esxi-6.5 update 2
I am not able to ping MTU size over than 1468 and above
[root@esxihost3:~]
[root@esxihost3:~] vmkping -I vmk0 -s 1468 192.168.111.100
PING 192.168.111.100 (192.168.111.100): 1470 data bytes
— 192.168.111.100 ping statistics —
3 packets transmitted, 0 packets received, 100% packet loss
[root@esxihost3:~]
[root@esxihost3:~] vmkping -I vmk0 -s 1500 192.168.111.100
PING 192.168.111.100 (192.168.111.100): 1500 data bytes
— 192.168.111.100 ping statistics —
3 packets transmitted, 0 packets received, 100% packet loss
If I ping below MTU Size 1468 it is pinging.
[root@esxihost3:~]
[root@esxihost3:~] vmkping -I vmk0 -s 1450 192.168.111.100
PING 192.168.111.100 (192.168.111.100): 1460 data bytes
1468 bytes from 192.168.111.100: icmp_seq=0 ttl=63 time=1.209 ms
1468 bytes from 192.168.111.100: icmp_seq=1 ttl=63 time=2.302 ms
1468 bytes from 192.168.111.100: icmp_seq=2 ttl=63 time=2.014 ms
— 192.168.111.100 ping statistics —
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.209/1.842/2.302 ms
[root@esxihost3:~]
[root@esxihost3:~] vmkping -I vmk0 -s 1460 192.168.111.100
PING 192.168.111.100 (192.168.111.100): 1468 data bytes
1476 bytes from 192.168.111.100: icmp_seq=0 ttl=63 time=1.259 ms
1476 bytes from 192.168.111.100: icmp_seq=1 ttl=63 time=4.977 ms
1476 bytes from 192.168.111.100: icmp_seq=2 ttl=63 time=2.204 ms
— 192.168.111.100 ping statistics —
3 packets transmitted, 3 packets received, 0% packet loss
Below is my usb network details:
[root@esxihost3:~]esxcfg-vmknic -l
Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack
vmk0 Management Network IPv4 192.168.110.23 255.255.255.0 192.168.110.255 00:e0:4c:68:00:9b 1500 65535 true STATIC defaultTcpipStack
[root@esxihost3:~]
[root@esxihost3:~]
[root@esxihost3:~]
[root@esxihost3:~]
[root@esxihost3:~]esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vusb0 Pseudo uether Up 1000Mbps Full 00:e0:4c:68:00:9b 1500 Realtek USB 101001000 LAN
vusb1 Pseudo uether Up 1000Mbps Full 00:e0:4c:68:00:6d 1500 Realtek USB 101001000 LAN
Can you help on this
Thanks
Jason
Thanks Jason for the feedback!
This issue should be the known MTU issue which also mentioned by other folks (Txarly89, Jose noticed it too. Thanks All!)
Please expect the following update with the fix, and again, sorry for the inconvenience.
Thanks,
Songtao
I am trying to test this driver on one of the newest Mac mini. (2018). My problem is that I only have USB-C adapters, and plugging anything USB-C while booting (either the installer or the installed ESXI) gives me a purple screen of death. Plugging the adapter after booting doesn't get it to be recognized. Any tips?
Francis,
USB-C on this platform are behind Thunderbolt 3, which is not supported yet. Please avoid using USB-C on this platform, and USB-A(USB3.0) ports should work for you.
Please let me know if you have any question with USB-A ports.
Thanks,
Songtao
Hi, I'm using NUC7i3BNHX with ESXi6.7u1 and i installed ESXi670-VMKUSB-NIC-FLING-20124247-offline_bundle-11613968.zip driver for ASIX AX88179 USB 3.0 Gigabit Ethernet, but i've an issue during high traffic, no response via vusb0:
2019-03-16T22:36:39.075Z cpu2:2097587)<6>ASIX USB Ethernet Adapter:v1.14.4 http://www.asix.com.tw
2019-03-16T22:36:39.075Z cpu2:2097587)<6>vusb%d: mtu 1500
2019-03-16T22:36:39.075Z cpu2:2097587)CpuSched: 697: user latency of 2103994 netpoll-backup 0 changed by 2097587 vmklinux_9:hub_thread -6
2019-03-16T22:36:39.076Z cpu2:2097587)WARNING: LinNet: LinNet_CreateDMAEngine:4022: vusb0, failed to get device properties with error Not supported
2019-03-16T22:36:39.076Z cpu2:2097587)WARNING: LinNet: LinNet_ConnectUplink:11893: vusb0: Failed to create DMA engine with error Not supported, it maybe a pseudo device
2019-03-16T22:36:39.076Z cpu2:2097587)Uplink: 13942: Opening device vusb0
2019-03-16T22:36:39.076Z cpu0:2097207)Uplink: 13791: Detected pseudo-NIC for 'vusb0'
2019-03-16T22:36:39.408Z cpu2:2097587)Uplink: 11681: enabled port 0x3000002 with mac 00:0a:cd:24:c7:d3
2019-03-16T22:36:39.408Z cpu1:2097587)<6>vusb0: register 'ax88179_178a' at usb-0000:00:14.0-3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0a:cd:24:c7:d3
2019-03-16T22:36:39.408Z cpu1:2097587)<6>ax88179_178a 2-3:1.0: interface is claimed by ax88179_178a
2019-03-16T22:36:39.408Z cpu1:2097587)<6>usb 2-3: device is not available for passthrough
2019-03-16T22:36:39.408Z cpu2:2097274)CpuSched: 697: user latency of 2103995 vusb0-0-tx 0 changed by 2097274 NetSchedHelper -6
2019-03-16T22:36:39.409Z cpu1:2097587)<6>usb 2-3: usbfs: registered usb0204
2019-03-16T22:36:42.475Z cpu0:2099694)<6>vusb0: ax88179_178a - Link status is: 1
2019-03-16T22:36:42.476Z cpu3:2100438)<6>vusb0: Write medium type: 0x013b
2019-03-16T22:36:42.477Z cpu3:2100438)<6>vusb0: link up, 1000Mbps, full-duplex, lpa 0xC1E1
-----------------------------------errors:----------
2019-03-16T11:51:55.078Z cpu0:2097555)WARNING: LinNet: netdev_watchdog:3688: NETDEV WATCHDOG: vusb0: transmit timed out
2019-03-16T11:51:55.078Z cpu0:2097555)<6>xhci_hcd 0000:00:14.0: Stopped on Transfer TRB
2019-03-16T11:52:01.084Z cpu0:2097555)WARNING: LinNet: netdev_watchdog:3688: NETDEV WATCHDOG: vusb0: transmit timed out
2019-03-16T11:52:01.084Z cpu0:2097555)<6>xhci_hcd 0000:00:14.0: Stopped on Transfer TRB
2019-03-16T11:52:06.090Z cpu0:2097555)WARNING: LinNet: netdev_watchdog:3688: NETDEV WATCHDOG: vusb0: transmit timed out
2019-03-16T11:52:06.090Z cpu0:2097555)<6>xhci_hcd 0000:00:14.0: Stopped on Transfer TRB
2019-03-16T11:52:12.096Z cpu0:2097555)WARNING: LinNet: netdev_watchdog:3688: NETDEV WATCHDOG: vusb0: transmit timed out
2019-03-16T11:52:12.096Z cpu0:2097555)<6>xhci_hcd 0000:00:14.0: Stopped on Transfer TRB
2019-03-16T11:52:17.101Z cpu2:2097555)WARNING: LinNet: netdev_watchdog:3688: NETDEV WATCHDOG: vusb0: transmit timed out
2019-03-16T12:27:48.636Z cpu3:2097587)<6>xhci_hcd 0000:00:14.0: Output context after successful config ep cmd:
2019-03-16T12:27:48.970Z cpu3:2097587)<6>ASIX USB Ethernet Adapter:v1.14.4 http://www.asix.com.tw
2019-03-16T12:27:48.970Z cpu3:2097587)<6>vusb%d: mtu 1500
2019-03-16T12:27:48.970Z cpu3:2097587)CpuSched: 697: user latency of 2100437 netpoll-backup 0 changed by 2097587 vmklinux_9:hub_thread -6
2019-03-16T12:27:48.971Z cpu3:2097587)WARNING: LinNet: LinNet_CreateDMAEngine:4022: vusb0, failed to get device properties with error Not supported
2019-03-16T12:27:48.971Z cpu3:2097587)WARNING: LinNet: LinNet_ConnectUplink:11893: vusb0: Failed to create DMA engine with error Not supported, it maybe a pseudo device
2019-03-16T12:27:48.971Z cpu3:2097587)Uplink: 13942: Opening device vusb0
2019-03-16T12:27:48.971Z cpu0:2097207)Uplink: 13791: Detected pseudo-NIC for 'vusb0'
2019-03-16T12:27:49.305Z cpu2:2097275)CpuSched: 697: user latency of 2100453 vusb0-0-tx 0 changed by 2097275 NetSchedHelper -6
2019-03-16T12:27:49.305Z cpu3:2097587)Uplink: 11681: enabled port 0x3000002 with mac 00:0a:cd:24:c7:d3
2019-03-16T12:27:49.305Z cpu3:2097587)<6>vusb0: register 'ax88179_178a' at usb-0000:00:14.0-3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0a:cd:24:c7:d3
2019-03-16T12:27:49.305Z cpu3:2097587)<6>ax88179_178a 2-3:1.0: interface is claimed by ax88179_178a
2019-03-16T12:27:49.305Z cpu3:2097587)<6>usb 2-3: device is not available for passthrough
2019-03-16T12:27:49.305Z cpu3:2097587)<6>usb 2-3: usbfs: registered usb0203
2019-03-16T12:27:49.305Z cpu3:2097587)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 2 status = 0x1203
2019-03-16T12:27:49.528Z cpu0:2097539)<6>xhci_hcd 0000:00:14.0: xhci_hub_status_data: stopping port polling.
2019-03-16T12:27:52.298Z cpu0:2097329)<6>vusb0: ax88179_178a - Link status is: 1
2019-03-16T12:27:52.299Z cpu1:2100438)<6>vusb0: Write medium type: 0x013b
2019-03-16T12:27:52.300Z cpu1:2100438)<6>vusb0: link up, 1000Mbps, full-duplex, lpa 0xC1E1