Unable to connect to the vCenter Appliance Management interface." /var/run/log/vmkernel.log:YYYY-MM-DDTHH:MM:SS.###Z cpu85:41077519)NetPort: 1660: enabled port 0x2000077 with mac ##:##:##:##:##:##
YYYY-MM-DDTHH:MM:SS.###Z cpu85:41077519)etherswitch: L2Sec_EnforcePortCompliance:172: client testvm01 requested mac address change to ##:##:##:##:##:## on port 0x2000077, disallowed by vswitch policy
YYYY-MM-DDTHH:MM:SS.###Z cpu85:41077519)etherswitch: L2Sec_EnforcePortCompliance:252: client VM has policy violations on port 0x2000077. Port is blocked
YYYY-MM-DDTHH:MM:SS.###Z cpu88:41077516)NetPort: 1879: disabled port 0x2000077
YYYY-MM-DDTHH:MM:SS.###Z cpu52:65778)Net: 3740: disconnected client from port 0x2000077
VMware vCenter Server 6.7
During the vCenter upgrade, the installer deploys a vCenter Appliance as the target in Stage-1. This process may involve a MAC address change, which can result in the installer reporting an error when attempting to enable vCenter Server Appliance Management Interface (VAMI) access.
This is an expected behavior.
As a workaround, perform one of the below steps:
In certain scenarios, the error message "The installer is unable to connect to the vCenter Appliance Management Interface" may occur if port 5480 is blocked on the firewall, preventing the Windows workstation (from which the upgrade is being performed) from accessing the vCenter VAMI page (https://<vCenter_IP/FQDN>:5480) to proceed with upgrade Stage 2, port 5480 must be unblocked on the firewall between the Windows workstation and vCenter.