Unsolved
This post is more than 5 years old
2 Intern
•
522 Posts
0
1277
July 16th, 2015 05:00
Internal Error on RP4VM 4.3 Cluster Connection
Hi,
I have deployed (2) RP4VM 4.3 clusters (one at each site) and upon using the cluster connect wizard and network troubleshooting, it appears that the WAN networks are not communicating. We are working to resolve that issue, however the error returned by the DM was an "internal error" and to contact EMC support.
My question is if something like a rollback or cleanup needs to be performed at this point and I really need to contact EMC support or if I can just leave it be for now, fix the WAN issues (or change the WAN IP's on the VM's) and then retry the DM? In the past I think I had to run a cleanup when hitting this issue among physical RPA cluster connections, so I'm not sure if anything has changed and wanted to check.
Thanks!
-Keith
Idan
675 Posts
0
July 16th, 2015 06:00
Hi Keith,
That would depend on the the progress of the connect, I would make sure the clusters are not connected via boxmgmt.
If they are, disconnect them and retry the DM connect clusters wizard after you've fixed the WAN issue.
Can you collect logs and send them to me, I would like to make sure the alert is accurate in this case.
Regards,
Idan
fadliz
153 Posts
0
July 16th, 2015 06:00
Just run finish_maintenance_mode before re-running DM after you add the Gws and make sure you can ping the WAN IPs. We have added a sub-section in the Installation Guide under Troubleshooting > vRPA that discuss how to troubleshoot the WAN connectivity issues,
Zahid Fadli
RecoverPoint Corp. Systems Engineering
EMC2
Twitter: @zDataGuy
From: echolaughmk
Reply-To: "jive-1316786792-ot9-2-j7ip@emc-ecn.hosted.jivesoftware.com "
Date: Thursday, July 16, 2015 at 9:00 AM
To: Zahid Fadli
Subject: - Internal Error on RP4VM 4.3 Cluster Connection
ECN
Internal Error on RP4VM 4.3 Cluster Connection
created by echolaughmk in RecoverPoint - View the full discussion
fadliz
153 Posts
0
July 16th, 2015 07:00
Keith,
It depends on where it failed…but I would run it on each to be safe. Then, I would add the Gws using boxmgmt (view Gws first to make sure that the one you added during DM was not already added), perform the ping -I eth0 test from each end and then run DM to connect the clusters.
Zahid Fadli
RP Corp Systems Eng.
Twitter: @zDataGuy
From: echolaughmk
Reply-To: "jive-1316786792-ot9-2-j7jb@emc-ecn.hosted.jivesoftware.com "
Date: Thursday, July 16, 2015 at 10:13 AM
To: Zahid Fadli
Subject: Re: - Internal Error on RP4VM 4.3 Cluster Connection
ECN
Internal Error on RP4VM 4.3 Cluster Connection
reply from echolaughmk in RecoverPoint - View the full discussion
echolaughmk
2 Intern
•
522 Posts
0
July 16th, 2015 07:00
Thanks guys! I will grab the logs and send to you Idan.
Zahid - I run that command on an RPA in each cluster right? Or do I just run it on a particular cluster (the existing cluster I put in the DM during deployment)?
The gateway I tried to add during the cluster connect wizard doesn't show up on the RPA's in CLI when I view settings, which is odd. The cluster don't look to be connected so I will run the command above, change the IP's so they can communicate over eth0, and then re-run the DM.
echolaughmk
2 Intern
•
522 Posts
0
July 16th, 2015 07:00
sweet...I will do that. thanks!
I'm going to change the WAN IP's to something I know that will route actually and then I will run ping test before I retry the DM.
I forgot to mention in the last post - that new section you mentioned looks great...great addition to the guides for those that aren't savvy on the CLI.
stay tuned
bakitup
1 Rookie
•
9 Posts
0
October 5th, 2015 07:00
I have run into the same issue. I have added/removed the additional GW for WAN but still get internal error. I attempted to ping via the command earlier but it will not ping. There are no firewalls, etc between the networks. I can ping the WAN networks from my PC so I don't know why the vRPA won't ping each others WAN IP
Idan
675 Posts
0
October 6th, 2015 04:00
Hi,
Make sure you're pinging with "-I eth0" to go through the WAN interfaces and also if the gateways are properly configured. Also, you would need to run the CLI command finish_maintenance_mode before re-running DM.
Hope that helps,
Idan Kentor
RecoverPoint Corporate Systems Engineering
idan.kentor@emc.com
fadliz
153 Posts
0
October 6th, 2015 04:00
Check the WAN network mapping on the vRPA then. Also make sure to login to the vRPA as admin and run finish_maintainance_mode
Also check the MTU, is the MTU consistent on the vRPA, hypervisor and network? And that port 8082 b/w the RPVM clusters is open.
Thanks,
Zahid
EMC2
Twitter: @zDataGuy
From: jtp
Reply-To: "jive-1217751946-ot9-2-jhkn@emc-ecn.hosted.jivesoftware.com "
Date: Tuesday, October 6, 2015 at 7:34 AM
To: "Fadli, Zahid"
Subject: Re: - Internal Error on RP4VM 4.3 Cluster Connection
ECN
Internal Error on RP4VM 4.3 Cluster Connection
reply from jtp in RecoverPoint - View the full discussion