Cannot add portgroup to vSwitch: "Operation failed! A specified parameter was not correct"

Products

• VMware vSphere ESXi

Issue/Introduction

Administrators are unable to add a new portgroup to a standard virtual switch (e.g., vSwitch0) on an ESXi host. When attempting to add the portgroup, the operation aborts with the following error message:

Operation failed! A specified parameter was not correct

Reviewing the /var/run/log/hostd.log On the affected ESXi host, the following strict configuration validation failures:

 

2026-03-23T18:53:34.815Z info hostd[2100698] [Originator@6876 sub=Hostsvc opID=x.x.x.x user=admin] Invalid NIC order: one of more PNIC specified are not uplinked to vswitch.
2026-03-23T18:53:34.815Z info hostd[2100698] [Originator@6876 sub=Hostsvc.NetworkVmkSimulator opID=x.x.x.x user=admin] Cannot add portgroup
Management Network]: invalid network policy specified:(vim.host.policy)

 

Reviewing the Standard Switch configuration from logs, we see a discrepancy between one of the portgroups on the vSwitch and the vSwitch assigned uplinks as shown below:

Switch Name      Num Ports  Used Ports  Configured Ports  MTU       Uplinks
vSwitch0         X          X               1500      vmnic2,vmnic3

PortGroup Name                            VLAN ID  Used Ports  Uplinks
Management Network                        X     1           vmnic2,vmnic4 <<<< References vmnic associated with a different Standard switch

Environment

VMware ESXi 7.0.3

Cause

The issue is caused by an invalid network policy on a pre-existing portgroup on the same virtual switch. Specifically, an existing portgroup retains an active uplink teaming policy referencing a physical adapter (e.g., vmnic4) that is physically bound to a different virtual switch or no longer assigned to the current switch. This mismatch forces the ESXi host daemon to reject the entire network configuration payload during new portgroup additions.

Resolution

Workaround:

1. Access the vSphere Client or the ESXi Host Client.

2. Navigate to the networking configuration for the affected ESXi host and select the standard virtual switch encountering the issue (e.g., vSwitch0).

3. Inspect the teaming and failover policy for all pre-existing portgroups on the switch (e.g., Management Network).

4. Modify the portgroup configurations to realign the active and standby uplinks so they strictly match the physical adapters currently assigned to the virtual switch (e.g., assigning vmnic2 and vmnic3, while removing the invalid vmnic4).

5. Save the corrected network policy.

6. Once the invalid policy is corrected and the switch state is valid, execute the operation to add the new portgroup.

Additional Information

Similar KBs referencing the same error with log examples:

Unable to remove uplinks from Distributed Switch - "Invalid network policy" "Cannot add portgroup"

Unable to Create a New VMkernel Adapter on a Standard Switch - “Invalid Network Policy” or “Cannot Set Policy”

Standard or Distributed Switch changes fail with the error "A specified parameter was not correct"