Verifying Communication over TCP Port 443 between the Staging Network and the CloudEndure Service Manager

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 between the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. to the CloudEndure Service ManagerThe CloudEndure server., use the following methods to check the connection.

Note: One indication of a communication problem over TCP Port 443 is the appearance/creation of lag in the replication. However, lag could also appear due to other causes.

Note: If you already started the replication, a communication problem between the Staging Area and the CloudEndure Service Manager is manifested in steps 4 & 5 of the replication initiation procedure.

Step 4 error: Failed to resolve CloudEndure Service Manager address in the replication server.

The subnet selected for the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. is configured in a way that prevents DNS lookups to resolve to https://console.cloudendure.com

Make sure that DNS traffic is not blocked. Create a machineA physical or virtual computer. in the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location.’s subnet and try to resolve console.cloudendure.com (either by accessing the destination on your browser or using the following command:

wget https://console.cloudendure.com/

Step 5 error: Failed to authenticate the replication server with the CloudEndure Service Manager

https://console.cloudendure.com/ not reachable via TCP Port 443 by the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location.. Check the subnet you selected in Setup & Info > Replication Settings and ensure that TCP Port 443 is open from your Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. Network.

To verify the integrity of the connection from the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. to the CloudEndure Service ManagerThe CloudEndure server. over TCP Port 443:

1. Launch a vanilla Ubuntu machineA physical or virtual computer. in the default subnet of the default VPC in the same subnet are running.
2. On the machineA physical or virtual computer., run the following command:
   wget https://console.cloudendure.com/(most platforms)
   
3. If the command fails, then that there is a connectivity problem.

Solving Communication Problems over TCP Port 443 between the Staging Area and the CloudEndure Service Manager

To solve communication problems, perform the following instructions according to 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). cloud you are using:

AWS

• DHCP - Check the DHCP options set of the VPC of the Staging Area.
  
  Ensure that the IPv4 CIDR, the DHCP options set, the Route table, and the Network ACL are correct.
  
• DNS – Ensure that you are allowing outbound DNS resolution and connectivity over TCP Port 443.
  
  
  1. Create a machineA physical or virtual computer. in the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location.'s subnet.
  2. From within that machineA physical or virtual computer. try to either:
     
     Browse to https://console.cloudendure.com/ (Windows)
     wget https://console.cloudendure.com/ (Linux)
  
  
• Route Rules - the Route Rules on the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. subnet may be inaccurately set. The Route Rules should allow outbound traffic to the Internet.
  
  To check and set the Route Rules on the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. subnet:
  
  
  1. Sign in to AWS console, click on Services and select VPC under Networking & Content Delivery.
     
  2. On the VPC Dashboard toolbar, select the Route Tables option.
     
  3. On Route Tables page, check the box of the Route Table of your Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks..
     
  4. This will open the details for your Route Table. Navigate to the Routes tab.
     
  5. Within the Target column of the Routes tab, find the route you are using for the outbound communication to the Internet (either igw- Internet Gateway, vgw - VPN or i - EC2 instance). Verify that the address space in the Destination column is covering the CloudEndure IPs and URLs.
     
     

     Note: CloudEndure AWS-specific IPs and URLs include: 52.72.172.158, 52.53.92.136, s3.amazonaws.com, s3.us-west-1.amazonaws.com, s3.eu-west-1.amazonaws.com and outbound access to the EC2 endpoint of the AWS region.

     
     
     
  6. If the address is not 0.0.0.0/0, you will need change it to 0.0.0.0/0.
     
     Click the Edit button.
     
  7. Input 0.0.0.0/0 into the Destination field for the correct Target. Click Save.
     
     

     Note: If you are using VPN, enter a specific IP address range in the Destination column. 

  
  
  
• Network ACL - The network ACL on the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. subnet may block the traffic. Verify that the ephemeral ports are open.