Symptoms
This issue has been seen on a VPLEX-Metro configuration and after issuing the '
rp validate-configuration' command from the VPlexcli it reports that RP-initiators are logged in without a corresponding RPA registration at the affected cluster.
Error may also be reported this way:
Cause
This issue occurs when RPAs are not registered on both Management Servers, or MMCS's, in a VPLEX-Metro configuration.
This issue may also be reported for a VPLEX local if there is one or more RPAs configured on the VPLEX but not yet registered.
Resolution
Log into the management server(s) and then the VPlexcli - using the service account credentials run the following commands:
- rp import-certificate
- rp rpa-cluster add -o <floating management IP of the RP cluster> -u admin -c <cluster-id/name>
Note: if you renamed VPLEX cluster name(s) from the defaults of cluster-1 and cluster-2, you will need to use
the custom cluster name(s) in the cli command.
Example:
VPlexcli:/> rp import-certificate
This command will cause the VPLEX CLI process to restart if security settings are modified. This will require a new log in from all connected CLI and GUI clients.
To proceed type CONTINUE or hit enter to abort:CONTINUE
Please enter the IP address of the RecoverPoint cluster: xxx.xxx.xxx.xxx
VPlexcli:/> rp rpa-cluster add -o 10.10.10.10 -u admin -c cluster-1
Connected to Plex firmware director-1-1-A.
director-1-1-A: Warning: The versions of MgmtServerBase, MgmtServerSoftware, Director Software and Cluster Witness Server are incompatible. See the output of 'version -a' for more details.
Connected to Plex firmware director-1-2-A.
Connected to Plex firmware director-1-2-B.
Connected to Plex firmware director-1-1-B.
Connected to Plex firmware director-2-1-A.
Connected to Plex firmware director-2-1-B.
Connected to Plex firmware director-2-2-A.
Connected to Plex firmware director-2-2-B.
Next to confirm all configured RPAs on the VPLEX have been registered use the ' ll ' command as follows
ll /recoverpoint/rpa-clusters/
VPlexcli:/> ll /recoverpoint/rpa-clusters/
Again if this is a VPLEX-Metro you will need to repeat these steps on the remote cluster as well.
NOTE: To find which cluster the RPA is configured for run the 'health-check' command at at the end look for Recoverpoint
Additional Information
The procedure for adding Recoverpoint to VPLEX specifies that this is a requirement, but the documentation can be misinterpreted causing the RP registration error being reported as noted in this article.