RecoverPoint for VMs and vCenter Appliance

vCSA should work w/ RPVM even though qualification is not complete at this time. What version of vSphere and VC are you using? Do you have additional plugins in the env - I see VCHSNavigatorNodeFilter' while loading plugin id com.vmware.vcim.ngc.vCHSPluginInstaller.vchsplugininstaller

Does the plugin see the RP cluster? When you click on the RPVM plugin, do you see the cluster with any warning/errors in the dashboard? Also check health of the RPVM cluster - you can do so from the Plugin dashboard or by connecting to the system via SSH and running get_system_status.

The vSphere version is 5.5 and the vCenter appliance is 5.5.0.20200 Build 2183109.

The only additional plug-in that we have other than what is installed by default is the vSphere replication plug-in.  Could vSphere replication be somehow interfering with it?  I would guess not but not sure...

It looks as if the plug-in does not see the cluster.  On the RPforVMs dashboard it never gets the cluster settings and gives that spinning progress bar.  On the admin tab it does see the two clusters though but no information about them when I click on them.  Eventually, the webclient will timeout and it will also affect other functions in the webclient not related to RPforVMs.

For get_system_status, do I do that through the boxmgmt login or the admin login?

Another question and this is about the IP configuration.  Each vRPA requires four IPs it seems with one for LAN, WAN, and two iSCSIs.  Does it matter if the LAN and WAN IP are shared by the iSCSI IPs?  So the LAN IP is the same at the first iSCSI IP and the WAN IP is the same as the second iSCSI IP. I know it is not ideal but would it cause issues?

Thx!

you can run using admin user

DC_RPA1_RPA2> get_sys

get_syslog_settings         get_system_settings

get_system_report           get_system_status

get_system_report_settings

DC_RPA1_RPA2> get_system_status

Select the category of issues to 'ENTER': 7

Enter the RPA cluster name, or press 'ENTER' for all RPA clusters:

Another question and this is about the IP configuration.  Each vRPA requires four IPs it seems with one for LAN, WAN, and two iSCSIs.  Does it matter if the LAN and WAN IP are shared by the iSCSI IPs?  So the LAN IP is the same at the first iSCSI IP and the WAN IP is the same as the second iSCSI IP. I know it is not ideal but would it cause issues?

ideally each RPA has two IPs, one for mgmt purpose (LAN) & another for Replication (WAN)

so for two node cluster, total 4 IPs Plus one floating IP to manage cluster as a whole.

I hope iSCSI is used as substitute to FC...

You got to have 4 distinct IPs for each vRPA: LAN,WAN and 2 iSCSI IPs. each RP4VM cluster must also have another cluster management IP.

The iSCSI ports are used for communication between the ESX splitter and the vRPAs as well as an interface to access virtual disks (production, replica, repository and journals).

The recommendation is to have different networks for LAN,WAN and iSCSI.

Regards,

Idan

Hi,

Besides the spinning progress bar which is a known issue where there are no configured CGs, are you seeing the RP4VM clusters under administration or when trying to protect a VM (when requested to select the RP4VM cluster to replicate this VM) ?

As for networking, I understand that you have 2 vswitches/dvswitches - one for LAN/iSCSI1 and the other is for WAN/iSCSI2. I agree it's not ideal since intersite data transfer is used on the same network/NIC as the vRPA to ESX splitter communication. That being said, I don't see an issue with that configuration.

Regards,

Idan

The iSCSI interfaces are distinct ports on the vRPAs (eth2,eth3). So yes you need 4 unique IPs per vRPA (plus the floating mgmt IP). The iSCSI interfaces on the vRPAs are used for splitter communication and to access vmdks.

It's highly recommended to have separate subnets for LAN, WAN and iSCSI.

Sent from my iPhone

So I had the network reconfigured...we had to expand out the subnet in order to get more IPs.

Each vRPA has unique IPs for LAN, WAN, and the two iSCSI interfaces but it is still not working.

Everything configures correctly through the deployment manager but the webclient just doesn't seem to work properly.  In addition, when accessing RPforVMs on the webclient it crushes the vCenter appliance.  It eventually times out and I have to reconnect.  I have attached the console output from the RPforVMs plug-in and it is mostly "producer fault" errors whatever those are.

Thx!

Hello there,

The producer fault errors are of little importance same as most of the information in the webclient console log. After restarting the web client, are you able to launch the RP4VM web client plugin ? if so, do you see RP4VM cluster(s) under Administration ?.

Regards,

Idan

The clusters do appear under the administration tab.  I have two set up and both are showing up in the tab.

On the protection tab, the VMs aren't showing up though.  The progress bar justs spins and spins and nothing ever shows up as is the case under the dashboard in the consistency group transfer status area.

Thx!

This is normal and should be fixed in the next patch. As soon as you protect a VM from the RecoverPoint for VMs tab in the Web Client the RecoverPoint for VMs Management portion of the plugin will update with the VM and CG info.

Can you elaborate on what you're seeing when you're trying to protect a VM by right clicking it, selecting All RecoverPoint for Virtual Machines .. and Protect ?

Alternatively, try protecting a VM through the RP4VM tab in the VM summary tab or through the RecoverPoint for Virtual Machines tab.

Once the VM is protected, you will see it under Virtual Machines under the Protection tab in the plugin.

Regards,

Idan

Thanks for the response but the VMs never show up in the protection tab.  So I can't protect them because I cannot select them.  Also, when right-clicking on VM outside of the RP4VMs plug-in area and then selecting to protect it doesn't work either.

Take a look at the Protection section on the attached Whitepaper that I released this week.

Hello

I have the same bug, that means that I can´t see the RP4VM cluster in the vSphere web client, wether in the dashboard view nor in the Administration tab.

I have already restarted the vSphere web client service and altough rebooted both vRPAs.

What can I do, is this a known bug?