ESXi vmnic missing and vSwitch assignment fails with error: VSI node (5007:)

Products

• VMware vCenter Server

Issue/Introduction

An ESXi network uplink (e.g., vmnic0) appears missing or completely unassigned when queried via standard inventory visibility commands such as esxcfg-vswitch -l.

The physical NIC displays as Up under esxcli network nic list, but does not appear under any active virtual switch or port group.

Network interfaces attached to the affected switch management network exhibit 100% packet loss to their gateway.

Subsequent attempts to add or re-bind the uplink fail with the following error: Failed to add uplink vmnic0 to vswitch vSwitch0, Error: Uplink already exists: vmnic0

Attempts to remove the uplink via esxcfg-vswitch -D vmnic0  fails with the following error: Failed to remove portgroup: vmnic0, Error: Unable to get node: Not found: VSI node (5007:)

Environment

VMware vSphere ESXi 8.x

Cause

Live kernel runtime memory desynchronization occurs between the low-level vSphere Sysinfo (VSI) tree layer and the hostd management agent engine cache during ungraceful distributed switch migrations or dynamic port provisioning faults, resulting in a phantom interface lock.

Resolution

Execute the following commands in sequence via an active SSH session on the affected ESXi host to clear the kernel lock without restarting the physical server:

1. Force the kernel runtime environment to drop and reinitialize the driver mapping for the target adapter:

   esxcli network nic down -n vmnic0

   esxcli network nic up -n vmnic0

2. Restart the core host daemon engine to force a complete breakdown and rebuilding of the virtual runtime memory state tables: /etc/init.d/hostd restart (Note: Allow approximately 30 to 45 seconds for the daemon to fully re-initialize before passing new network states.)

3. Once the management engine has refreshed, run the standard removal argument against the target virtual switch to completely purge the phantom assignment: esxcli network vswitch standard uplink remove --uplink-name=vmnic0 --vswitch-name=vSwitch0

4. Re-assign the clean physical interface back to the management virtual switch: esxcli network vswitch standard uplink add --uplink-name=vmnic0 --vswitch-name=vSwitch0

5. Verify that the interface successfully links to the virtual switch profile using the command: esxcfg-vswitch -l and confirm gateway connectivity