Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Network adapter does not appear in the ESX/ESXi host within the Virtual Center/vCenter Inventory

Symptoms

After adding a new network adapter to the ESX/ESXi host, it does not appear in the list of network adapters within the Virtual Center/ vCenter inventory.

Purpose

This article provides steps to follow when the network adapter is not displayed in the vCenter inventory.

Resolution

Each step below provides instructions and a link to a document, for performing the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and to identify the proper resolution. They are also ordered in the most appropriate sequence to minimize data loss. After completing each step, check if the network adapter appears in the list under Configuration > Network Adapters. Work through each troubleshooting step in order, and do not skip a step.
 
To troubleshoot issues when the network adapters are not displayed in the vCenter Server inventory: 
  1. Verify that your existing or newly added network adapter is on the hardware compatibility list. For more information, see ESX/ESXi host network adapter compatibility (1003685).
  2. Verify that the hardware is working properly. For more information, see Verifying the integrity of the physical network adapter (1003686). 

If the issue continues to exist after trying the steps in this article:

Tags

cannot-add-network-addapter esx faulty-network-adapter incompatible-network-adapter network-adapter-not-visible no-connectivity virtual-network-uplink

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback


Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
KB: