Configuration lost for portgroup when modified in ESXi 7.0 Update 2
Article ID: 318051
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
When modifying a portgroup such as when renaming it, or while upgrading a virtual standard switch, the settings of the portgroup, such as for VLAN ID, seem to disappear.
This issue may also be observed where changes to the VLAN ID made on a port group are not maintained after a reboot.
After running the following command:
esxcfg-vmknic -l
After running the following command:
esxcfg-vmknic -l
All vmknics are accessible and the enabled value for all of them shows as true.
In the case of renaming a portgroup, in vpxa.log the incremented changes refer to the old name AFTER the point of renaming, and referencing the new name. Example below, using a hypothetical port group with an old name of "VM-OLDNAME", and a new name of "VM-NEWNAME", the old name appearing in increments after the new name was established is seen:
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (615): HostChanged|configManager.networkSystem:networkInfo.vswitch["key-vim.host.VirtualSwitch-vSwitch1"].portgroup["key-vim.host.PortGroup-VM-NEWNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (616): HostChanged|configManager.networkSystem:networkInfo.portgroup["key-vim.host.PortGroup-VM-NEWNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (617): HostChanged|configManager.networkSystem:networkInfo.vswitch["key-vim.host.VirtualSwitch-vSwitch1"].portgroup["key-vim.host.PortGroup-VM-OLDNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (618): HostChanged|configManager.networkSystem:networkInfo.portgroup["key-vim.host.PortGroup-VM-OLDNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109713] [Originator@6876 sub=vpxLro opID=jsu5bexs-44775-auto-q5b-h5:70016391-38-60732aa0-30] [VpxLRO] -- FINISH lro-4430
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1110204] [Originator@6876 sub=vpxaInvtHost opID=TIF-46efd36f update=10077] Increment master gen. no to (619): HostConfig:VpxaInvtHostListener::HostChanged(network)
In the case of renaming a portgroup, in vpxa.log the incremented changes refer to the old name AFTER the point of renaming, and referencing the new name. Example below, using a hypothetical port group with an old name of "VM-OLDNAME", and a new name of "VM-NEWNAME", the old name appearing in increments after the new name was established is seen:
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (615): HostChanged|configManager.networkSystem:networkInfo.vswitch["key-vim.host.VirtualSwitch-vSwitch1"].portgroup["key-vim.host.PortGroup-VM-NEWNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (616): HostChanged|configManager.networkSystem:networkInfo.portgroup["key-vim.host.PortGroup-VM-NEWNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (617): HostChanged|configManager.networkSystem:networkInfo.vswitch["key-vim.host.VirtualSwitch-vSwitch1"].portgroup["key-vim.host.PortGroup-VM-OLDNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109556] [Originator@6876 sub=vpxaInvtHost opID=TIF-37c5e5bb update=10076] Increment master gen. no to (618): HostChanged|configManager.networkSystem:networkInfo.portgroup["key-vim.host.PortGroup-VM-OLDNAME"]
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1109713] [Originator@6876 sub=vpxLro opID=jsu5bexs-44775-auto-q5b-h5:70016391-38-60732aa0-30] [VpxLRO] -- FINISH lro-4430
YYYY-MM-DDTHH:MM:SS.XXXX info vpxa[1110204] [Originator@6876 sub=vpxaInvtHost opID=TIF-46efd36f update=10077] Increment master gen. no to (619): HostConfig:VpxaInvtHostListener::HostChanged(network)
Environment
VMware vSphere ESXi 7.0.2
Cause
In ESXi 7.0 Update 2, a code change causes a new portgroup sub-object to be created by mistake when it is modified, rather than modifying the current port group as intended. The sub-object is missing the settings required for the portgroup to work properly.
Resolution
The resolution is to upgrade ESXi host to 7.0 Update 3 or newer.
Workaround:
A work-around is to edit the affected portgroups' settings to re-input the VLAN or other values as required.
Workaround:
A work-around is to edit the affected portgroups' settings to re-input the VLAN or other values as required.
Additional Information
If all vmknics are NOT accessible and enabled this KB article may apply:
Post upgrade to 7.0 U2, ESXi hosts do not show the vmkernel interfaces
Impact/Risks:
Virtual machines attached to the portgroup may be unable to access the network until the settings are re-entered into it.
Feedback
Yes
No
Powered by
