- Two Physical Remote Datacenters
- Two external 6.5 PSC’s at each Datacenter (4 total in the same SSO domain, ring topology)
- Two 6.5 VCSA’s at each Datacenter each pointed to a PSC in the same datacenter (no load balancer)
If you login to site 1 VCSA and choose site 2’s VCSA; any option for VUM (ex. root VC object or VUM admin area) returns the text errors below. Same happens when logged into site 2’s VCSA and trying to manage site 1’s VUM.
“interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader”
Problem occurred while connecting to the Update Manager server. See the vSphere Web Client logs for more details.
If you read the manual TCP port 8084 “The port used by vSphere Update Manager client plug-in to connect to the vSphere Update Manager SOAP server. ”
When you ran curl -v telnet://target ip address:8084 to the remote VCSA, it failed. Once the port was opened on the firewall VUM was accessible from any the VCSA in any direction.
Lesson learned – TCP port 8084 does need to be open (two way communication) between all 6.5 VCSA’s when they are are in an enhanced link mode.