Unsolved
This post is more than 5 years old
3 Posts
0
1157
January 12th, 2017 14:00
vRPA selection not working
I've created two virtual machine based on the EMC_RecoverPoint_vRPA-RP4VMs_rel5.0.P1_d.207.ova and I'm trying to create a vRPA cluster from them. The two VMs are on the same VMware datacentre on two different hosts, their IPs are 192.168.0.21 and 192.168.0.22 they share the same subnet 255.255.0.0 and default route. However when creating the cluster only one vRPA vm appears in the vRPA selection list. There doesn't seem to be an option to add a vRPA by its IP address which would be the obvious solution. I've also tried creating a single vRPA cluster and adding a second one, again nothing is found when searching for other vRPAs.
Any help or pointers would be appreciated.
alphablox
3 Posts
0
January 15th, 2017 14:00
They are brand new VMs created using the vSphere client from the .ova, they are on the same cluster which is why its odd they can't see each other. I can connect to the webserver running on each vRPA from my PC showing that the IP settings are good. The vmware cluster is setup with a vCenter server appliance running 5.5.0.5100 with vSphere 5 Essentials Plus so it might be some obscure API issue ? I'm am following this up with support and will advise when they find a resolution.
Idan
675 Posts
1
January 16th, 2017 03:00
Hi Justin,
Can you verify that that both vRPAs reside on the same cluster ? if they are, just for troubleshooting purposes, can you vMotion the 2nd vRPA to the same ESX as the first one.
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
@IdanKentor
alphablox
3 Posts
0
January 16th, 2017 14:00
They are on the same cluster of three hosts, moving them to the same ESXi host causes the second vRPA to appear in the selection list which is very odd. Putting them on any other host prevents them from being seen. Do they need to be on the same shared storage ?
Idan
675 Posts
0
January 17th, 2017 07:00
They do not need to be on the same shared storage, they do need to be able to access the same repository VMDK which is created during deployment. I'll follow-up with support since I understand you've raised a case.
Regards,
Idan