Step 10: Failed to establish communication between the CloudEndure Agent and the replication server

Important! The information provided in this section is for general Troubleshooting guidance only. The information is provided on "AS IS" basis, with no guarantee of completeness, accuracy or timeliness, and without warranty or representations of any kind, expressed or implied. In no event will CloudEndure and/or its subsidiaries and/or their employees or service providers be liable to you or anyone else for any decision made or action taken in reliance on the information provided above or for any direct, indirect, consequential, special or similar damages (including any kind of loss), even if advised of the possibility of such damages. CloudEndure is not responsible for the update, validation or support of troubleshooting information.

Possible causes for failure

There are cases where the installation is indicated as successful, but the progress is stopped at the last step of the replication initiation sequence - Establish communication between the CloudEndure Agent and the Replication Server. Usually, this means that the AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. could not establish a communication with the CloudEndure Service ManagerThe CloudEndure server..

1. A firewall, either on the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. or on the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). side, is preventing the CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. from reaching the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. on TCP Port 1500.
1. To verify, create a new machineA physical or virtual computer. on the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. subnet and run nc -l 1500
2. From the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. run: telnet <new machine ip> 1500
If this test fails, then check:
• The Network ACL on the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). subnet.
• Route rules on the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). subnet.
• Firewall permissions (internal/external) in the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). subnet.
2. The Use VPN… checkbox was mistakenly selected or deselected in Setup & Info > Replication Settings.

Note: After you fixes the problem, it may take up to 30 minutes to re-establish the communication.