When creating a host profile, hardcoding tcpstacks such as 'mirror' or 'ops' without first configuring the tcpstack on the ESXi host can lead to host profile application failure. This may leave the host in a partially configured state and potentially result in the loss of the vmk0 network configuration.
vCenter 8.0
Host Profile does not support adding mirror or ops netstack during remediation if not already there.
To verify the configuration before applying the host profile, run the following command:esxcli network ip netstack list
This is a known issue impacting VMware ESXi.
Workaround:
Before initiating host profile remediation, manually create the required tcpstacks on the ESXi host that are referenced in the host profile. Use one or both of the following commands to configure the appropriate stacks:esxcli network ip netstack add -N mirroresxcli network ip netstack add -N ops