USB NIC Issue Resolution Summary

Date: 2025-07-21
Issue: USB NIC adapters not detected as vmnic1 on Intel NUCs
Status: ✅ RESOLVED

Problem Identification

Original Issue

• All three Intel NUCs had only vmnic0 (built-in Intel NIC) visible
• USB NIC adapters (ASIX AX88179) were detected by lsusb but not functioning as network interfaces
• Expected to see vmnic1 for the USB adapters

Root Cause

• Incompatible VIB: vmkusb-nic-fling version 1.10 was built for ESXi 7.0.3
• API Mismatch: ESXi 8.0.3 uses different kernel APIs, causing module load failures
• Error Message: Ignoring invalid required namespace <com.vmware.vmkapi.incompat#v2_9_0_0>

Solution Implemented

1. Downloaded Correct VIB

• Source: VMware Flings - USB Network Native Driver for ESXi
• File: ESXi803-VMKUSB-NIC-FLING-76444229-component-24179899.zip
• Version: 1.14-2vmw.803.0.0.76444229 (ESXi 8.0.3 compatible)

2. Updated All Hosts

For each Intel NUC:

1. Removed old VIB: vmkusb-nic-fling 1.10
2. Installed new VIB: vmkusb-nic-fling 1.14
3. Rebooted host
4. Verified USB NIC functionality

Results

Final Network Interface Status

Host	Built-in NIC	USB NIC	Status
esxi-nuc-01.markalston.net	vmnic0 (Intel I219-LM)	vusb0 (ASIX AX88179)	✅ Working
esxi-nuc-02.markalston.net	vmnic0 (Intel I219-LM)	vusb0 (ASIX AX88179)	✅ Working
esxi-nuc-03.markalston.net	vmnic0 (Intel I219-LM)	vusb0 (ASIX AX88179)	✅ Working

Key Details

• Interface Name: USB NICs appear as vusb0 (not vmnic1 as expected)
• Speed: All interfaces running at 1000 Mbps Full Duplex
• Driver: uether driver for USB adapters
• MAC Addresses: Each adapter has unique MAC address

Impact on vCenter Configuration

Benefits Gained

✅ Dual NIC Configuration: Can now separate traffic types
✅ Network Redundancy: Management traffic redundancy available
✅ Better Performance: Dedicated NICs for different traffic types
✅ vMotion Capability: Separate vMotion network possible

Important Considerations

❌ vLCM Still Not Possible: Community VIBs prevent single image management
⚠️ Traditional Cluster Required: Must use baseline management approach
⚠️ Community Support: USB NIC drivers are community-supported

Network Design Options

Option 1: Dual NIC Separation

• vmnic0: Management + VM traffic
• vusb0: vMotion + Storage traffic

Option 2: Redundant Management

• vmnic0: Primary management
• vusb0: Secondary management (failover)

Option 3: VLAN Segmentation

• Use both NICs with VLANs for complete traffic separation
• Management (VLAN 10), vMotion (VLAN 20), Storage (VLAN 30), VMs (VLAN 100)

Tools Created

Script	Purpose
scripts/check-usb-nic-status.sh	Check USB NIC status on hosts
scripts/update-single-host-usb.sh	Update USB NIC VIB on single host
scripts/verify-all-usb-nics.sh	Verify USB NICs on all hosts
scripts/update-usb-nic-fling.sh	Batch update all hosts

Documentation Created

File	Purpose
docs/guides/esxi/usb-nic-troubleshooting.md	Detailed troubleshooting guide
docs/guides/esxi/usb-nic-esxi8-solution.md	Solution options and procedures
docs/status/usb-nic-resolution-summary.md	This summary report

Next Steps

Now that dual NICs are available:

1. Configure Traditional Cluster (not vLCM due to community VIBs)
2. Set up Distributed Switches for better network management
3. Configure Network Separation:
   • Management network
   • vMotion network
   • Storage network
   • VM networks
4. Test Network Performance and redundancy
5. Deploy Production Workloads

Lessons Learned

1. VIB Compatibility Critical: Always verify VIB compatibility with ESXi version
2. Community VIBs Impact: Community drivers prevent vLCM usage
3. Interface Naming: USB NICs use vusb0 naming convention, not vmnic1
4. VMware Flings: Good source for updated community drivers
5. Testing Approach: Always test on one host before deploying to all

Command Reference

# Check network interfaces
esxcli network nic list

# Check installed VIBs
esxcli software vib list | grep usb

# Check USB devices
lsusb

# Check for module errors
dmesg | grep -i usb

# Install new VIB (ESXi 8.0.3)
esxcli software vib install -d /tmp/ESXi803-VMKUSB-NIC-FLING*.zip --no-sig-check

---

Resolution Complete: All Intel NUCs now have functioning dual network interfaces and are ready for advanced vCenter cluster configuration with proper network separation.