ESXi Host Profile remediation fails while creating mirror or ops network stack using vSphere Client

Products

• VMware vSphere ESXi

Issue/Introduction

Remediating host profile generates error "A specified parameter was not correct" in Vsphere UI

Environment

ESXI 8.0 U2x
ESX 8.0 U3x

Cause

Currently Host Profile do not support adding mirror and ops netstack during remediation.

Following snippets are observed in the logs.

Hostd.log
---------

2025-06-12T00:14:03.136Z In(166) Hostd[2098656]: [Originator@6876 sub=Hostsvc opID=###312kq-###6974-auto-###9z-h5:####0975-c4-01-94-##d9-##fe sid=5####b48 user=vpxuser] UpdateNetwork with Config: (vim.host.NetworkConfig) {
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> netStackSpec = (vim.host.NetworkConfig.NetStackSpec) [
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> (vim.host.NetworkConfig.NetStackSpec) {
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> netStackInstance = (vim.host.NetStackInstance) {
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> key = "ops", 
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> name = "ops", 
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> congestionControlAlgorithm = "newreno", 
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> }, 
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> operation = "add"
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> }
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> ], 
2025-06-12T00:14:03.136Z In(166) Hostd[2098620]: --> }

2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->    netStackSpec = (vim.host.NetworkConfig.NetStackSpec) [
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->       (vim.host.NetworkConfig.NetStackSpec) {
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->          netStackInstance = (vim.host.NetStackInstance) {
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->             key = "mirror",
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->             name = "mirror",
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->             congestionControlAlgorithm = "newreno",
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->          },
2025-05-30T20:32:15.441Z In(166) Hostd[2098799]: -->          operation = "add"

Resolution

Workaround is to add the mirror and ops network before remediating the host

1.On each host to apply the host profile, please manually run the following esxcli commands to add the two netstacks.
  # esxcli network ip netstack add -N mirror
  # esxcli network ip netstack add -N ops

2.Use the esxcli list command to make sure the netstacks are successfully added before the remediation.

# esxcli network ip netstack list

defaultTcpipStack
   Key: defaultTcpipStack
   Name: defaultTcpipStack
   State: 4660

mirror
   Key: mirror <-------
   Name: mirror
   State: 4660

ops
   Key: ops <-------
   Name: ops
   State: 4660

Additional Information

Broadcom Engineering is working to fix this in future releases.