Verifying Communication over Port 1500

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.

If there is a connection problem 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. to the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. or the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks., use the following methods to check the connection.

To verify the integrity of the connection from a 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. to the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. over TCP Port 1500:

1. Launch a new Linux machineA physical or virtual computer. in the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. subnet.
2. On the new Linux machineA physical or virtual computer., run the following command to open a listener in the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. subnet:
   nc -l 1500
3. On 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 the following command to check connectivity:
   telnet <new machine ip> 1500
   

   Note: If the Use VPN… box is checked in Replication Settings, then the Private IP of the new Linux machine should be used. If the Use VPN… box is unchecked, then the Public IP should be used.

If the command fails, then there is a connectivity problem.

To fix this, check:

AWS

• 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 (both internal and external) in the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure..
• Check if you checked/unchecked the “Use VPN...” checkbox correctly.