Symptoms:
There are two instances of this issue:
YYYY-MM-DDTHH:MM:SS.sssZ info hostd[####][Originator@####] sub=Hostsvc opID=####:#### user=vpxuser:####]Invalid shaping policy: shaper is enabled, but at least one of the avgbps, peakbps or burst is not set.YYYY-MM-DDTHH:MM:SS.sssZ info hostd[####][Originator@####] sub=Hostsvc opID=####:#### user=vpxuser:####]Invalid network policy: there are invalid properties in network traffic shaping policy.YYYY-MM-DDTHH:MM:SS.sssZ info hostd[####][Originator@####] sub=Hostsvc opID=####:#### user=vpxuser:####]Cannot add portgroup [VMotion]: invalid network policy specified:(vim.host.NetworkPolicy) {...--> shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {--> enabled = true,--> burstSize = 104857600,--> }
YYYY-MM-DDTHH:MM:SS.sssZ info hostd[####][Originator@####] sub=Hostsvc opID=####:#### user=vpxuser:####]Cannot set policy for vswitch [vSwitch0], network policy is invalid: (vim.host.NetworkPolicy) {...--> shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {--> enabled = true,--> averageBandwidth = 2000000000,--> }--> }VMware ESXi 7.0
This issue occurs because the system pulls traffic shaping policies from an existing vSwitch or port group to the newly created one. If these parameters in the ConfigStore are extremely large, hostd treats them as "unset," causing configuration validation to fail during the creation process.
esxcli network vswitch standard policy shaping set --vswitch-name <vSwitch> --enabled false