The installer is unable to connect to the vCenter Appliance Management interface
"ESXi - /var/run/log/vmkernel.log:
20xx-xx-xxTxx:xx:xx.xxxZ cpu85:41077519)NetPort: 1660: enabled port 0x2000077 with mac 00:50:56:a0:b2:72
20xx-xx-xxTxx:xx:xx.xxxZ cpu85:41077519)etherswitch: L2Sec_EnforcePortCompliance:172: client testvm01 requested mac address change to 00:50:56:a0:b2:72 on port 0x2000077, disallowed by vswitch policy
20xx-xx-xxTxx:xx:xx.xxxZ cpu85:41077519)etherswitch: L2Sec_EnforcePortCompliance:252: client testvm01 has policy violations on port 0x2000077. Port is blocked
20xx-xx-xxTxx:xx:xx.xxxZ cpu88:41077516)NetPort: 1879: disabled port 0x2000077
20xx-xx-xxTxx:xx:xx.xxxZ cpu52:65778)Net: 3740: disconnected client from port 0x2000077
VMware vCenter Server
During the upgrade, the installer deploys a vCenter appliance as target during stage 1. This step might involve a MAC change during the same stage which can cause the installer to report the error while enabling vCenter Server Appliance Management Interface (VAMI) access.
This is an expected behavior.
As a workaround, perform one of the below steps:
In some scenarios, same error message "The installer is unable to connect to the vCenter Appliance Management Interface."
will be reported when port 5480 is blocked on firewall so windows workstation (from where upgrade is performed) is unable to connect to vCenter VAMI page (https://<vcenter ip/fqdn>:5480
). Port 5480 needs to be unblocked between windows workstation and vCenter on firewall in order to proceed to upgrade stage two.