Error adding second vRPA

Hello E.PEREZ,

Here is a link to a kb that maybe of assistance.

https://dell.to/3I1A54F

Hello Sam L,

Thank you for your help. I try this resolution but I have another error below :

Adding vRPA/s
12% Installing
Installation has failed. Review the error messages below to identify the cause of failure. If installation keeps failing, contact Customer Support.
Retry
Adding new vRPAs to cluster M-vRPA-1.
Input Validation failed. please validate your input with the following errors: [Failed validation - found duplicate IP.:192.168.208.220:[192.168.208.220, 192.168.208.220], Failed validation as not all LAN IPs of version IPv4 are in same network.:ValidateAllIpsSameSubnetTaskResponse(networksList={10.24.24.0/23=[10.24.24.3]}, noNetworkIps=[192.168.208.210]), The IP address is outside the range defined by gateway: 192.168.208.249 and subnet mask: 255.255.254.0:[10.24.24.3]]

The first vRPA is in backup site, its data IP is 192.168.208.220, default gateway is 192.168.208.249.

The second vRPA is in production site, its IP is 10.24.24.3, default gateway is 10.24.24.250.

Regards,
E Perez

Are they in the same cluster? https://dell.to/3JGylOT

Hello,

The two vRPA are in the same cluster ESXi, please find attached screenshot.

Our error is not the same as attached kb you send me. I am able to select the second vRPA on the other host. The error is displayed during the add process, second screenshoot.

Regards,
E Perez

These troubleshooting steps may help https://dell.to/3JNbX6A

https://dell.to/3p2N2UD

Page 29 https://dell.to/3p9J2l4

Hello,

I use the kb below to check the configuration on both ESX and vRPA. I do no find somrthing wrong. Please find below the details.

https://www.dell.com/support/kbdoc/en-us/000021679/recoverpoint-for-virtual-machines-troubleshooting-ip-splitter-connectivity-issues?dgc=SMcid=281920lid=spr6385574259RefID=dtw22_sm6385574259linkId=153353033

STEP 1a - First vRPA - How to identify RPAs DATA IPs and eth port
-----------------------------------------------------------------
M-vRPA-1:
** View settings **
[1] View cluster M-vRPA-1 settings
[M] Main Menu
[B] Back
[Q] Quit
M-vRPA-1: |----------------------------------------------------|
| Cluster M-vRPA-1 |
|----------------------------------------------------|
| Internal cluster name | 0x706454a4b24f21af |
| Product Type | RP_4_VM |
| Cluster management (LAN) IPv4 | 192.168.208.210 |
| Cluster management (LAN) IPv6 | N/A |
| WAN LAN IPV4 netmask | 255.255.254.0 |
| DATA IPV4 netmask | 255.255.254.0 |
| Time zone | Africa/Nairobi |
| Primary DNS server | 192.168.208.219 |
| Secondary DNS server | 192.168.208.218 |
| Primary NTP server | 160.119.216.202 |
| Secondary NTP servers | 192.168.208.1 |
| Local domain | N/A |
| Number of Virtual Ports | 1 |
| | |
| RPA 1 | |
| RPA Nic Topology | data is separated |
| RPA LAN IPv4 | 192.168.208.207 |
| RPA LAN IPv6 | N/A |
| RPA WAN IP | 192.168.208.207 |
| RPA DATA1 IP | 192.168.208.220 |
| RPA DATA2 IP | 192.168.208.220 |
|-------------------------------|--------------------|

|------------------------------------------------------------|
| Gateway | Target netmask | Target subnet |
|---------------------------|----------------|---------------|
| 192.168.208.249 (default) | 0.0.0.0 | default |
|---------------------------|----------------|---------------|

|---------------------|
| RPA Ports |
|---------------------|
| RPA 1 | 3260 |
|-----------|---------|

STEP 1b - Second vRPA - How to identify RPAs DATA IPs and eth port
------------------------------------------------------------------
This menu is not avalaible : -> [2] Setup -> [6] View settings -> [1] View cluster CLUSTER settings

Initializing Installation Manager... done
Installation Manager - RecoverPoint Version 5.3.SP2.P2(m.154)
Would you like to set or modify an IP address, gateway or subnet mask for this unconfigured vRPA? (y/n)? n

** Main Menu **
[1] Installation
[2] Setup
[3] Diagnostics
[4] Cluster operations
[5] Shutdown / Reboot operations
[6] System management CLI
[Q] Quit
Enter your selection: 2

** Setup **
[-] Modify settings [unavailable]
[2] Configure repository volume
[3] Get remote settings
[4] Retrieve previous settings
[-] Apply settings [unavailable]
[-] View settings [unavailable]
[7] Reset settings changes
[8] Advanced options
[9] Console configuration
[M] Main Menu
[B] Back
[Q] Quit
Enter your selection:

STEP 2a - First ESX CORE-11 - identify the ESX VMkernel adapter from vSphere
----------------------------------------------------------------------------
[root@CORE-11:~] esxcli network ip interface ipv4 get
Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type Gateway DHCP DNS
---- --------------- ------------- --------------- ------------ ------------- --------
vmk0 192.168.208.202 255.255.254.0 192.168.209.255 STATIC 192.168.208.1 false
vmk1 192.168.208.188 255.255.254.0 192.168.209.255 STATIC 0.0.0.0 false

STEP 2b - Second ESX 10.24.24.1 - identify the ESX VMkernel adapter from vSphere
--------------------------------------------------------------------------------
[root@AME-ESXi-1:~] esxcli network ip interface ipv4 get
Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type Gateway DHCP DNS
---- ------------ ------------- -------------- ------------ ------------ --------
vmk0 10.24.24.1 255.255.255.0 10.24.24.255 STATIC 10.24.24.250 false
vmk1 10.24.24.50 255.255.255.0 10.24.24.255 STATIC 0.0.0.0 false

STEP 3a - First ESX CORE-11 - RP Splitter not installed
----------------------------------------------------------------------------
[root@CORE-11:~] esxcli software vib list|grep RP
RP-Splitter RPESX-00.5.3.2.0.0.m.222.000 EMC PartnerSupported 2022-02-08

STEP 3b - Second ESX 10.24.24.1 - RP Splitter not installed
----------------------------------------------------------------------------
[root@AME-ESXi-1:~] esxcli software vib list|grep RP
RP-Splitter RPESX-00.5.3.2.0.0.m.222.000 EMC PartnerSupported 2022-02-13

STEP 4a - First ESX CORE-11 - RP Splitter not running
----------------------------------------------------------------------------
[root@CORE-11:~] ps|grep kdrive
2099987 2099987 kdriver
2099989 2099987 kdriver
2099990 2099987 kdriver
2099991 2099987 kdriver
2099992 2099987 kdriver
2099993 2099987 kdriver
2099994 2099987 kdriver
2099995 2099987 kdriver
2099996 2099987 kdriver
2099997 2099987 kdriver
2099998 2099987 kdriver
2099999 2099987 kdriver
2100000 2099987 kdriver
2100001 2099987 kdriver
2100002 2099987 kdriver
2100003 2099987 kdriver
2100004 2099987 kdriver
2100005 2099987 kdriver
2100006 2099987 kdriver
2100007 2099987 kdriver
2100008 2099987 kdriver
2100009 2099987 kdriver
2100010 2099987 kdriver
2100011 2099987 kdriver
2100012 2099987 kdriver
2100013 2099987 kdriver
2100014 2099987 kdriver
2100015 2099987 kdriver
2100016 2099987 kdriver
2100017 2099987 kdriver
2100018 2099987 kdriver
2100019 2099987 kdriver
2100020 2099987 kdriver
2100021 2099987 kdriver
2100022 2099987 kdriver
2100024 2099987 kdriver
2100025 2099987 kdriver
2100026 2099987 kdriver
2100027 2099987 kdriver
2100028 2099987 kdriver
2100029 2099987 kdriver
2100030 2099987 kdriver
2100031 2099987 kdriver
2100033 2099987 kdriver
2100034 2099987 kdriver

STEP 4b - Second ESX 10.24.24.1 - RP Splitter not running
----------------------------------------------------------------------------
[root@AME-ESXi-1:~] ps|grep kdrive
2103106 2103106 kdriver
2103108 2103106 kdriver
2103109 2103106 kdriver
2103110 2103106 kdriver
2103111 2103106 kdriver
2103112 2103106 kdriver
2103113 2103106 kdriver
2103114 2103106 kdriver
2103115 2103106 kdriver
2103116 2103106 kdriver
2103117 2103106 kdriver
2103118 2103106 kdriver
2103119 2103106 kdriver
2103120 2103106 kdriver
2103121 2103106 kdriver
2103122 2103106 kdriver
2103123 2103106 kdriver
2103124 2103106 kdriver
2103125 2103106 kdriver
2103126 2103106 kdriver
2103127 2103106 kdriver
2103128 2103106 kdriver
2103129 2103106 kdriver
2103130 2103106 kdriver
2103131 2103106 kdriver
2103132 2103106 kdriver
2103133 2103106 kdriver
2103134 2103106 kdriver
2103135 2103106 kdriver
2103136 2103106 kdriver
2103137 2103106 kdriver
2103138 2103106 kdriver
2103139 2103106 kdriver
2103140 2103106 kdriver
2103141 2103106 kdriver
2103143 2103106 kdriver
2103144 2103106 kdriver
2103145 2103106 kdriver
2103146 2103106 kdriver
2103147 2103106 kdriver
2103148 2103106 kdriver
2103149 2103106 kdriver
2103150 2103106 kdriver
2103151 2103106 kdriver
2103152 2103106 kdriver

STEP 5a - First vRPA M-vRPA-1 - Ping to verify connectivity between vRPAs DATA ports and ESX VMkernel adapter
-----------------------------------------------------------------------------------------------------------
Connectivity issues:
1. Login to the vRPA as root
2. Use ping to verify connectivity between vRPAs DATA ports and ESX VMkernel adapter
ping -I eth0 192.168.208.202
RecoverPoint-0x706454a4b24f21af-RPA1:/root# ping -I eth0 192.168.208.202
PING 192.168.208.202 (192.168.208.202) from 192.168.208.207 eth0: 56(84) bytes of data.
64 bytes from 192.168.208.202: icmp_seq=1 ttl=64 time=0.040 ms
64 bytes from 192.168.208.202: icmp_seq=2 ttl=64 time=0.043 ms
64 bytes from 192.168.208.202: icmp_seq=3 ttl=64 time=0.073 ms
64 bytes from 192.168.208.202: icmp_seq=4 ttl=64 time=0.064 ms

STEP 5b - Second vRPA AME-vRPA-1 - Ping to verify connectivity between vRPAs DATA ports and ESX VMkernel adapter
-----------------------------------------------------------------------------------------------------------
Connectivity issues:
1. Login to the vRPA as root password admin is not working

STEP 6a - First ESX CORE-11 - Ping from the ESX to the vRPAs DATA ports
----------------------------------------------------------------------------
[root@CORE-11:~] vmkping -I vmk0 192.168.208.220
PING 192.168.208.220 (192.168.208.220): 56 data bytes
64 bytes from 192.168.208.220: icmp_seq=0 ttl=64 time=0.096 ms
64 bytes from 192.168.208.220: icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from 192.168.208.220: icmp_seq=2 ttl=64 time=0.089 ms
--- 192.168.208.220 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.085/0.090/0.096 ms

STEP 6b - Second ESX 10.24.24.1 - Ping from the ESX to the vRPAs DATA ports
----------------------------------------------------------------------------
No data port on second vRPA as setup is not finished.

Ping to second vRPA AME-vRPA-1 :
[root@AME-ESXi-1:~] vmkping -I vmk0 10.24.24.3
PING 10.24.24.3 (10.24.24.3): 56 data bytes
64 bytes from 10.24.24.3: icmp_seq=0 ttl=64 time=0.125 ms
64 bytes from 10.24.24.3: icmp_seq=1 ttl=64 time=0.102 ms
64 bytes from 10.24.24.3: icmp_seq=2 ttl=64 time=0.081 ms
--- 10.24.24.3 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.081/0.103/0.125 ms

Ping to second ESX 10.24.24.1 :
[root@AME-ESXi-1:~] vmkping -I vmk0 192.168.208.220
PING 192.168.208.220 (192.168.208.220): 56 data bytes
64 bytes from 192.168.208.220: icmp_seq=0 ttl=61 time=1.784 ms
64 bytes from 192.168.208.220: icmp_seq=1 ttl=61 time=3.286 ms
64 bytes from 192.168.208.220: icmp_seq=2 ttl=61 time=1.786 ms
--- 192.168.208.220 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.784/2.285/3.286 ms

STEP 7a - First vRPA M-vRPA-1 - MTU check
-----------------------------------------------------------------------------------------------------------
** MTU configuration **
[1] View MTU values
[2] Configure MTU values
[M] Main Menu
[B] Back
[Q] Quit
M-vRPA-1: 1
|----------------|
| MTU values |
|----------------|
| WAN_LAN | 1500 |
| DATA | 1500 |
|---------|------|

STEP 7b - Second vRPA AME-vRPA-1 10.24.24.3 - MTU check
-----------------------------------------------------------------------------------------------------------
This menu is not available :
** Main Menu **
[1] Installation
[2] Setup
[3] Diagnostics
[4] Cluster operations
[5] Shutdown / Reboot operations
[6] System management CLI
[Q] Quit
Enter your selection: 2

** Setup **
[-] Modify settings [unavailable]
[2] Configure repository volume
[3] Get remote settings
[4] Retrieve previous settings
[-] Apply settings [unavailable]
[-] View settings [unavailable]
[7] Reset settings changes
[8] Advanced options
[9] Console configuration
[M] Main Menu
[B] Back
[Q] Quit
Enter your selection: 1

** Setup **
[-] Modify settings [unavailable]
[2] Configure repository volume
[3] Get remote settings
[4] Retrieve previous settings
[-] Apply settings [unavailable]
[-] View settings [unavailable]
[7] Reset settings changes
[8] Advanced options
[9] Console configuration
[M] Main Menu
[B] Back
[Q] Quit
Enter your selection:

STEP 8a - First ESX CORE-11 - Testing firewall from ESX
----------------------------------------------------------------------------
[root@CORE-11:~] nc -z 192.168.208.220 5044
Connection to 192.168.208.220 5044 port [tcp/*] succeeded!

STEP 8b - Second ESX 10.24.24.1 - Testing firewall from ESX
----------------------------------------------------------------------------
[root@AME-ESXi-1:~] nc -z 10.24.24.3 5044
no response

STEP 9a - First vRPA M-vRPA-1 - Ping to find duplicate IPs
-----------------------------------------------------------------------------------------------------------
RecoverPoint-0x706454a4b24f21af-RPA1:/root# arping -I eth0 -c 10 192.168.208.220
ARPING 192.168.208.220 from 192.168.208.207 eth0
Sent 10 probes (10 broadcast(s))
Received 0 response(s)
Exit 1

STEP 9b - Second vRPA AME-vRPA-1 10.24.24.3 - Ping to find duplicate IPs
-----------------------------------------------------------------------------------------------------------
Login root is not working.

Regards,
E Perez

The root login not working could be the cause of the issue. It would be best to call phone support, as some of the potential fixes require a phone agent to fix.

Hello Josh,
Could you indicate please the dedicated RP phone number and email address ?

Regards,
E Perez

The phone number is 800-782-4362

Hello Josh,

We are based in East Africa, this phone number will not work. Do you know the number for our region ?

Regards,
E Perez

Which country specifically? I can check for a number, but not all African countries have official support. 

Hello Josh,

Our country is Djibouti (East Africa). Can we have a technical support by email ?

Regards,
E Perez

I am looking into the best contact for there.