One more interesting tidbit in case someone from the overnight crowd has some idea of what is going on .... I checked with the firewall team and they see no traffic hitting the firewall from my source replication or vCenter server where the destination is the remote vCenter or replication server. I'm not sure if this means the traffic is never getting off the appliance or maybe it means nothing at all, but felt it was worth mentioning.
Could you please run the packet capture at the source and the destination end , it'll let you know how the traffic is flowing and help further to troubleshoot the issue .
Thanks, I'll see what I can do about getting packet capture data. When I am making this connection .... adding a target site to a remote destination in a different SSO domain, is it trying to connect to the remote replication device or vCenter? Is the connection initiated by the source vCenter or vSphere Replication device? I may not have asked for all the correct firewall ports be opened.
vCenter --> vCenter
vCenter - vSphere Replication
vSphere Replication --> vCenter
vSphere Replication --> vSphere Replication
"rather than displaying the vCenter server of the target site, it displays the vSphere Replication appliance at the target site"
do you mean that you see FQDN/IP of the VR appliance instead of the one of the VC server in the "Select a vCenter Server to connect to:" list of the "Connect to Target Site" dialog?
What is listed here is the VRM Site Name: field from the VR appliance Configuration page - it has apparently been changed from the default which is the VC FQDN to something else.
You may find information about the default network ports in the Admin Guide VMware vSphere Replication 6.1 Documentation Center.
The ports are all open. The firewall team can see the traffic being allowed and apparently it is the remote appliance that is denying the connection request. It is listening on all required ports. Another oddity is that even SSH (which i enabled and has port 22 listening) gets denied.