Hi all
I have 2 sites (both under each others VCenter and in each different domain - PROD and DR)
VCenter is 5.5 on both of them and ESXi on hosts is 5.1
VSphere replication appliance is 5.5.1.4 on both sites as well.
When I try to replicate from one site to the same site it is allowed and possible with all steps available and feasible.
When I try to connect from one site to another (tried it both ways and it works both ways gives the same error) I fail with error message as follows:
cannot connect to the specified site the site might not be available on the network or a network configuration problem might exist check your connection details and try again
I type in IPs instead of FQDN for VCenters when trying to connect and type in DOMAIN\USERNAME with administrative rights on vcenter.
Ive requested all ports to be opened between these 2 sites that are required in VMware KB: Ports that must be open for Site Recovery Manager 1.0.x to 5.5.x, vSphere Replication 1.0...
I've tried everything I could think of.
Do you have any suggestions I can try
Regards
S
Hi,
Are you able to ping from vCenter Server machine (where vSphere Web Client is installed) DR site vCenter Server and VR appliance IP's, also are you able to ping from production site VR appliance to vCenter Server IP and VR appliance IP in DR site?
I suspect that you have some network configuration issue.
Thanks,
Dzhem
Hi
yes I can ping and open ports from production site to DR site (let's call it that way).
From both Vcenter server and from vsphere replication appliance on PROD site I can ping and open ports to DR site VCenter and VSphere replication appliance.
I have requested the same in other direction initially, but seems like only this direction is working for the time being.
I've requested for ports and ICMP to be opened on other direction as well, so when they open it, I'll check. Hopefully in next hour they will do it :smileygrin: :smileygrin:
I'll check and update here
S
OK, to come back on this:
I've tested with networks and all required ports and ping is set between those 2 sites
In both directions
But again the same message
Any other thoguths
Regards
S
Just to clarify you have environment like this:
PROD DR
---------- -------------
VC VM PROD VC VM DR
VR VM PROD VR VM DR
And you are able to perform following operations
VC VM PROD
From VC VM PROD ping VC VM DR
From VC VM PROD ping VR VM DR
From VC VM PROD telnet VC VM DR 80
From VC VM PROD telnet VC VM DR 443
From VC VM PROD telnet VR VM DR 8043
VR VM PROD
From VR VM PROD ping VC VM DR
From VR VM PROD ping VR VM DR
From VR VM PROD telnet VC VM DR 80
From VR VM PROD telnet VC VM DR 443
From VR VM PROD telnet VR VM DR 8043
VC VM DR
From VC VM DR ping VC VM PROD
From VC VM DR ping VR VM PROD
From VC VM DR telnet VC VM PROD 80
From VC VM DR telnet VC VM PROD 443
From VC VM DR telnet VR VM PROD 8043
VR VM DR
From VR VM DR ping VC VM PROD
From VR VM DR ping VR VM PROD
From VR VM DR telnet VC VM PROD 80
From VR VM DR telnet VC VM PROD 443
From VR VM DR telnet VR VM PROD 8043
If you are able to ping and telnet on ports 80, 443 and 8043 I don't see why you can't connect both sites.
Hi
Yes I can ping and telnet in all stated situations
That is why it was strange for me also, so that is why I asked here.
Thank you for desolving it to simple steps and tasks, but again, I've checked it all, and all is ok (ping works and telnet opens to all ports stated and on all machines stated)
Regards
Sasa
In this case I think that you might open a SR and get additional support form VMware support team.
Thanks in advance,
Dzhem
Hi,
You can take a look at vsphere-client-virgo.log at the Web Client / VCVA machine and /opt/vmware/hms/logs/hms.log at the VR appliance.
There will be some details around the failure.
Whether specifying IP address or FQDN might not be relevant - VRMS uses the address as stored in URL property of the com.vmware.vcHms extension at vCenter Server (you can check using https://vcenter_server/mob/, navigate to ExtensionManager, look for com.vmware.vcHms and see server.url) - by default it uses VirtualCenter.FDQN runtime setting for vCenter reverse proxy address.
Regards,
Martin
I've resolved this issue
Seems like even though I was pointing with IP addresses, that was not enough.
After I added all 4 entries into /etc/hosts files and /system32/driivers/etc/hosts, everything ran smoothly
Those 4 entries are IPs and hostnames of VCPROD VCDR, VRPROD and VRDR
Thank you all for trying to help me with this.
I hope this thread will be useful to someone.
S
P.S Strange thing is I can mark my own reply as answer :smileygrin: :smileygrin:. Funny