Error Message when replicating. Replicated machines will not boot (4046544)

vRanger 5.2.1 HotAdd or Network based Replication fails after 1 or more successsfull passes then start shows the following error.

Error Message: Warning: Permanently added 'xxx.xxx.xxx.xxx' (RSA) to the list of known hosts.

and will be followed by this error as seen in the logs.

FATAL cant_write can't write vix:r:xx.xx.xx.xx:902:[L3_500_T] test1_r1_Replica/test1_r1_Replica.vmdk:moref=vm-13242:snapshot-13340:3 [at slave_main:569] FATAL internal internal error [at pkt_recv_unlock:82]

In some cases this is caused by having Multiple VA's on the source side of replication, replicating to single source.

VA's are not properly registering RSA keys through replication. Could be the result of Cloned VA's which will then have the same RSA keys.

This can be (at least temporarily) resolved by manually establishing the RSA key from each source VA.

1. Putty into Source VA #1, Log in as ROOT, and SSH to the IP address of the target host as ROOT.

SSH ROOT @xxx.xxx.xxx.xxx

2. It will ask if you want to permanently add this RSA key? Type YES

3. You will have to type in ROOT Password

Do this from each source VA.

This is being published internally for 2 reasons.

1. Because the whole question of when and why we need a VA for each host is being asked by Chris Meyer. 1 per cluster will work for Network based replication? but HotAdd add needs 1 per host? even with shared storage? After this is clarified, it will be pub externally.

2. We are waiting to see if the keys stay once added to the target VA. If they stay for a pass or 2, then it starts erroring again, this will be sub cased and go to dev.