Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3124

April 28th, 2016 10:00

Recover point register cluster error

hello everyone,

i just installed the latest version of RP for VM ( 4.3.1 SP1) .  i went through the web deployer and everything is fine.

i checked the environnement and iscsi is fine , i can ping my vmkernel.(splitter on esx is ok too)

So to me everything is ok . Exept when i perform the last step of install procedure.

Using vsphere web client, i register the ESX cluster in RP for VM.

i have one error : 

Ping to the splitter on the ESXi

Could not find ip address of the ESXi's splitter                

everything else is green (splitter installed, connectivity etc..) .  so anyone already got this problem?

thanks.

675 Posts

April 29th, 2016 04:00

Hi Pierre,

This is indeed a known issue but it has no effect if that's the only warning in the troubleshoot screen of an individual ESX cluster then this safely be ignored.

Regards,

Idan Kentor

RecoverPoint Corporate Systems Engineering

Twitter: @IdanKentor

1.1K Posts

April 28th, 2016 13:00

Yes, it's a known issue. 4.3 SP1 P1 is the latest RP4VMs release. You can use WDM to perform an NDU this patch version.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: 44 (0) 7730 781169 44%20(0)%207730%20781169>

E-mail: richard.forshaw@emc.com

Twitter: @rw4shaw

April 29th, 2016 00:00

hi,

thanks for the answer.but i think that is the version i installed, here is the name of the file i used.

EMC_RecoverPoint_vRPA_rel4.3.SP1.P1_h.192_md5_76ab7de00fc85796d4c722fe4a895fe0

thanks.

1.1K Posts

April 29th, 2016 05:00

Hi Pierre,

As Idan stated, it is a benign message. The issue is documented as a known issue in the latest version of the Release Notes, although the workaround description is not that clear.

The issue is related to there being no iSCSI port binding and the going forward we will provide an INFO message as opposed to an ERROR message and give more verbiage.

Regards,

Rich Forshaw

RecoverPoint Corporate Systems Engineering

April 29th, 2016 05:00

ok thanks.  it's a lot more clearer .

No Events found!

Top