VMware NSX
ESXi 7.x
ESXi 8.x
During the N-VDS to VDS migration process, vCenter Server and ESXi hosts maintain cached or database-level references to old network objects. If a segment is deleted or unconfigured in NSX Manager, the cleanup process may not fully propagate or refresh the state correctly to vCenter and/or the underlying ESXi host database. This can result in a stale record persisting in the vCenter/ESXi inventory until the ESXi hosts network state is fully refreshed.
To remove a stale segment entry from vCenter Server, the affected ESXi hosts should be rebooted. This process forces each ESXi host to refresh its network configuration and object references with vCenter.
Identify Affected Hosts
Determine which ESXi hosts are showing as connected to the stale segment in vCenter Server.(To check: Click on the segment in vCenter → Navigate to the Hosts tab to view)
Enter Maintenance Mode
Place one of the identified ESXi hosts into maintenance mode.
This ensures all virtual machines running on the host are migrated or powered off, preventing service disruption.
Note: Ensure proper DRS/HA configuration is in place, or manually vMotion VMs off the host before proceeding.
Reboot the ESXi Host
From vCenter Server: Right-click the ESXi host and select Reboot.
From the ESXi host DCUI: Select Reboot Host.
Verify the Esxi Host Removed from the Stale Segment
After the ESXi host successfully reboots and reconnects to vCenter Server, verify that the host is no longer shown as connected to the stale segment.(To check: Click on the segment in vCenter → Navigate to the Hosts tab to view)
Exit Maintenance Mode
Once verified, exit maintenance mode for the ESXi host.
Repeat for Other Hosts
Repeat steps 2–5 for any other ESXi hosts showing connections to the stale segment.