Please run finish_maintenance_mode from admin cli on both clusters, also check that the security level match (from boxmgmt: accessible, authenticated or auth & encrypted), and rerun the DM wizard.
I did as you suggested Fadliz, I ran the finish_maintenance_mode on both clusters, and then attempted to add connect the clusters with both the GUI and the CLI. I've tried all there of the security levels, and I still get the "
Internal error. Remote cluster did not provide a certificate" error.
I even removed the vRPAs at both data centers, and started over, hoping it was a setting that wasn't correct during the deployment of the OVA file. And i'm still getting the same error.
Assuming all routes are correct and that you were able to ping -I eth0 to remote sites, have you checked all ports are open between the 2 sites? Check the Security Guide, esp port 8082. If that all checks out ok and still having issues, we might have to regenerate encryption keys which requires SE user, but this is unlikely since you re-installed.
I was able to ping from all 4 RPA's to the remote WAN interfaces, using the ping -I eth0 command. I confirmed with our networking group there aren't any firewalls between the devices.
Can you point me to where the Security Guide for RP4VM's 4.3 is? It wasn't in the zip file that I downloaded, and I haven't been able to google it, or find it on the support site.
fadliz
153 Posts
0
July 23rd, 2015 14:00
Aaron,
Please run finish_maintenance_mode from admin cli on both clusters, also check that the security level match (from boxmgmt: accessible, authenticated or auth & encrypted), and rerun the DM wizard.
Sent from my iPhone
aseier
3 Posts
0
July 24th, 2015 11:00
I did as you suggested Fadliz, I ran the finish_maintenance_mode on both clusters, and then attempted to add connect the clusters with both the GUI and the CLI. I've tried all there of the security levels, and I still get the "
Internal error. Remote cluster did not provide a certificate" error.
I even removed the vRPAs at both data centers, and started over, hoping it was a setting that wasn't correct during the deployment of the OVA file. And i'm still getting the same error.
Any other suggestions?
Aaron
fadliz
153 Posts
0
July 24th, 2015 12:00
Assuming all routes are correct and that you were able to ping -I eth0 to remote sites, have you checked all ports are open between the 2 sites? Check the Security Guide, esp port 8082. If that all checks out ok and still having issues, we might have to regenerate encryption keys which requires SE user, but this is unlikely since you re-installed.
Zahid Fadli
EMC2
Twitter: @zDataGuy
From: aseier
Reply-To: "jive-633413242-ot9-2-j8ne@emc-ecn.hosted.jivesoftware.com "
Date: Friday, July 24, 2015 at 2:40 PM
To: Zahid Fadli
Subject: Re: - RP4VM 4.3 Cluster Connection error
ECN
RP4VM 4.3 Cluster Connection error
reply from aseier in RecoverPoint - View the full discussion
aseier
3 Posts
0
July 24th, 2015 13:00
Hey Zahid,
I was able to ping from all 4 RPA's to the remote WAN interfaces, using the ping -I eth0 command. I confirmed with our networking group there aren't any firewalls between the devices.
Can you point me to where the Security Guide for RP4VM's 4.3 is? It wasn't in the zip file that I downloaded, and I haven't been able to google it, or find it on the support site.
How do we obtain the SE user credentials?
Thanks,
Aaron