VM network configuration mismatch between vSphere Client and Managed Object Browser (MOB)

Products

• VMware vCenter Server

Issue/Introduction

Virtual Machine (VM) network configuration displayed in the vSphere Client does not match the information presented in the Managed Object Browser (MOB).

The vSphere Client UI shows a higher number of virtual network adapters (NICs) than the Managed Object Browser (MOB).

Environment

VMware vCenter Server 7.x

VMware vCenter Server 8.x

Cause

This is expected behavior by design.

The vSphere Client enumerates every individual virtual hardware device, while the MOB displays unique logical network backings (Port Groups). If multiple vNICs are assigned to the exact same Port Group, the MOB consolidates these connections into a single network entry.

Example: If both Network Adapter 2 and Network Adapter 3 are connected to the "VM Network" Port Group, the vSphere Client will show two distinct adapters, but the MOB will only display one network connection entry for that Port Group.

Resolution

Because this is expected behavior, no corrective action is required. However, if you need to retrieve an accurate 1:1 hardware count of all configured network adapters via the MOB, you must query the virtual hardware device directly rather than the logical network.

Follow these steps to verify/fetch the actual hardware state:

1. Identify the Managed Object ID (MoRef ID) of the affected Virtual Machine.
2. Navigate directly to the Virtual Hardware configuration in the MOB using the following URL: https://<vcenter-fqdn>/mob/?moid=<vm-moref>&doPath=config.hardware
   
3. Locate the device property, which is of type VirtualDevice[].
4. Expand the list to view all attached hardware components.
   
5. Verify that each configured vNIC is listed as an individual VirtualEthernetCard object within this list.

This method bypasses the logical network grouping and provides a direct reflection of the VM's .vmx configuration file.