When replicating using the vRanger Virtual Appliance, the above error may be encountered after a redeployment/reconfigure of the Virtual Appliance(s) involved in the Replication job.
The vRanger VAs communicate with each other and the VMware hosts in a secure way, both using SSH protocol over port 22 (in the case of the VA-to-VA communication) and SSL (in the case of VA-to-Host communication). In addition, there is a security (RSA) encryption key associated with each VA and host machine. This enables a "positive" identification of each host and VA so that they may not be impersonated and rendered insecure. When redeploying the Virtual Appliances for vRanger, the RSA key may be changed, even if the name\IP of the Virtual Appliance remains the same. This causes an RSA conflict, as the various hosts/VAs no longer "recognize" the changed key as genuine, and deny communications with the hosts, etc.
1) On each Virtual Appliance, open a putty session (or direct VMConsole session), and logon as "root".
2) DELETE (using the rm command) the /root/.ssh/known_hosts file on each VA affected by the problem.
3) Re-run the replication job. The new RSA key will be imported into the VA machine (the known_hosts file will be recreated), and replications should proceed normally.
