Overcoming the “No vmknic tagged for management” Error During ESXi 8.0.3 Installation with a USB NIC

Estimated reading time: 4 minutes

While building a VMware ESXi 8.0.3 host with a USB networking controller, I hit a snag that’s likely familiar to anyone venturing into this setup. The installation process threw up this error:

Exception: No vmknic tagged for management was found.

This halted my progress, but after some trial and error, I found a reliable fix that worked for my setup. Below, I’ll share two methods to resolve this issue—one involving manual CLI configuration and another leveraging ESXi’s built-in recovery tools. If you’re facing the same error, one of these should get you back on track.

The Problem

The error occurs because ESXi struggles to automatically configure a management network when using a USB NIC. Without a properly tagged vmknic (virtual management network interface), the installation can’t complete its configuration phase. Here are two ways to tackle it.

Option 1: Manual Configuration via CLI

This approach involves jumping into the ESXi console to manually set up the network during installation.

1. Start the ESXi Installation: Boot your server with the ESXi 8.0.3 installer and proceed until it stalls (often around 81%).
2. Access the Console: Press Alt+F1 to switch to the command-line interface.
3. Identify the USB NIC: Run esxcfg-nics -l to list all network interfaces. Locate your USB NIC (e.g., vmnic0).
4. Set Up the Management Network: Execute these commands:

esxcfg-vswitch -l
esxcfg-vswitch -a vSwitch0
esxcfg-vswitch -L vmnic0 vSwitch0
esxcfg-vmknic -a -i DHCP -p "Management Network"

1. This creates a virtual switch, links your USB NIC to it, and assigns a management interface (swap DHCP for a static IP if needed, e.g., -i 192.168.1.100 -n 255.255.255.0).
2. Verify: Check with esxcfg-vmknic -l to ensure the management vmknic is listed.
3. Resume: Return to the installer with Alt+F2 and retry. It should proceed without issues.

When to Use This: If you’re comfortable with CLI and want to fix things mid-installation, this is a solid option.

Option 2: Post-Install Network Restore (My Preferred Fix)

This is the method I ultimately used, and it’s simpler if you’re okay with a reboot. Here’s how it works:

1. Start the Installation: Launch the ESXi 8.0.3 installer and let it run until it fails at 81%. At this point, ESXi is technically installed but not configured.
2. Reboot the System: Remove the installation media (USB or CD) and reboot the server.
3. Log In: Once ESXi loads, press F2 and log in as root with no password. (Note: The password you set during installation isn’t saved due to the configuration failure.)
4. Check Network Options: You’ll notice all network settings are greyed out, indicating the USB NIC (e.g., vusb0) hasn’t been properly detected.
5. Restore Network Settings: Navigate to Network Restore Options in the menu, then select Restore Network Settings. Confirm the action.
6. Log Out and Back In: Exit the menu, log out, and log back in as root.
7. Success: The network options should now be accessible, and the USB NIC (vusb0) will be detected and usable.

Why This Worked for Me: This method leverages ESXi’s built-in recovery tools to reset and re-detect the network configuration post-install. It’s quick, avoids CLI complexity, and got my host fully operational.

Why This Happens

ESXi’s installer expects a management network to be available, but USB NICs don’t always play nicely out of the box. Option 1 forces the configuration during setup, while Option 2 lets the system sort itself out after a reboot. Both address the core issue: no vmknic tagged for management.

Final Thoughts

I went with Option 2 for its simplicity, but having Option 1 as a fallback is great for flexibility. If you’re building an ESXi host with a USB NIC, don’t let this error derail you—these fixes have you covered. Let me know in the comments if you’ve run into this or found other workarounds!