/var/run/log/hostd.log indicates that following ESXi upgrade, host is unable to locate virtual switch configurations for vSwitch (Name: vSwitch/abc), resulting in the associated port groups being missing.YYY-MM-DDThh:mm:ss info hostd[2099565] [Originator@6876 sub=Hostsvc.NetworkProvider] dvportgroups information not loaded from soap file /etc/vmware/hostd/dvportgroups.xml: no element found.YYY-MM-DDThh:mm:ss warning hostd[2099565] [Originator@6876 sub=Hostsvc.NetworkProvider] Invalid portgroup information in soap xml file : no element foundYYY-MM-DDThh:mm:ss warning hostd[2099565] [Originator@6876 sub=Libs] PortGroup: Unable to fetch configured network policy: Unable to find Vswitch configuration for vSwitch/abcYYY-MM-DDThh:mm:ss error hostd[2099565] [Originator@6876 sub=Hostsvc.NetworkProvider] ProcessVirtualSwitch: Error fetch portgroups for switch vSwitch/abc: Unable to find Vswitch configuration for vSwitch/abcYYY-MM-DDThh:mm:ss warning hostd[2099731] [Originator@6876 sub=Libs] PortGroup: Unable to fetch configured network policy: Unable to find Vswitch configuration for vSwitch/abc
VMware vSphere ESXi 6.x / 7.x / 8.x
vswitch name vSwitch/abc includes a forward slash /, which is causing parsing issues.
To address the issue of missing port groups caused by vSwitch names containing forward slashes, please follow the steps below:
configstorecli config current get -c esx -g network_vss -k switches
configstorecli config current get -c esx -g network_vss -k switches > vswitch.json
vswitch.json file using a text editor (e.g., vi), Remove or rename any vSwitch entries containing forward slashes (/).configstorecli config current set -c esx -g network_vss -k switches -i vswitch.json --overwrite