Server migration error: Customer.Client.Network.ConnectFailed

Problem description

A migration task in SMC fails and reports the error message "Customer.Client.Network.ConnectFailed".

Causes

The SMC client on the source system fails to connect to the transit service on the destination instance. The possible causes are as follows:

• The transit service on port 8080 of the destination instance is not running correctly.

• The source server cannot access the IP:8080 port on the destination instance.

Solutions

1. Verify that port 8080 on the destination instance is accessible and running correctly.

   1. Go to the Instances page of the ECS console.

   2. In the upper-left corner, select the region and resource group of the destination instance.

   3. Confirm that the destination instance is in the Running state.

      • If the instance is in the Running state, proceed to the next step.

      • If the instance is in the Stopped state, start the instance.

      • If the instance has been released, create another migration task. For more information, see Migrate a server to an ECS instance.

   4. Click the ID of the destination instance to open the instance details page. On the Scheduled Tasks tab, click Send Command.

      • For Windows: Enter netstat -ano | findstr 8080 and click Execute Now.

      • For Linux systems: In the command input box, enter netstat -ano | grep 8080 and click Execute Now.

      If the command runs successfully and returns output for port 8080, the port is working as expected.

   5. Check the inbound rules of the security group for the destination instance. Ensure that traffic on port 8080 is allowed and no other rules block this port.

      Note

      By default, an SMC migration task automatically associates a temporary security group with the destination instance and allows inbound traffic on port 8080.

   6. Access http://<destination instance IP>:8080 from a server other than the source server to verify that it is working correctly.

      • Linux system: curl http://<destination instance IP>:8080.

      • On Windows: In a browser, go to http://<destination instance IP>:8080.

      If a response in the standard JSON format such as {"code":-101,"message":"smc p2vs get ok."} is returned, the status is normal.

      Note

      By default, the public IP address of the destination instance is used. If you selected the private migration mode, use the private IP address of the destination instance.

2. Check if the network services on the source system are running correctly.

   1. Verify that local network services are running as expected. Check the configurations of the hosts file and DNS.

   2. By default, migration tasks use the public migration mode for data transfer. Make sure that the source system can access the Internet.

   3. If the migration task is configured to use the private migration mode, make sure that a private connection is established between the source system and the destination VPC and vSwitch. For more information, see Private migration.

      Note

      If you are unsure whether a private connection is established, use the public migration mode. If you selected the private migration mode by mistake, switch to the public migration mode and try again.

3. Test the network connectivity from the source system to the destination instance.

   1. In the security group for the destination instance, allow inbound traffic for the ICMP protocol. Then, use the ping command to test the network connection from the source server to the destination instance.

      If the test fails, check your local network and intermediate devices, such as a firewall or proxy, for outbound rules that restrict access by IP address.

   2. Access http://<Destination instance IP address>:8080 to test whether the source server can connect to port 8080 on the destination instance.

      • Linux system: curl http://<destination instance IP>:8080.

      • For Windows: use a browser to access http://<destination-instance-ip>:8080.

      If a normal JSON response such as {"code":-101,"message":"smc p2vs get ok."} is returned, the connection is successful. Otherwise, the connection has failed, and you must check your local network configuration or intermediate network devices, such as firewalls or proxies, for outbound IP or port access restrictions.

   3. Check whether Alibaba Cloud Firewall is enabled. If Alibaba Cloud Firewall is enabled, check whether an access control policy, such as one for the Internet firewall or VPC firewall, is blocking network traffic. For more information, see Internet firewall.

4. After you resolve the network issue, run the SMC client to retry the operation. For more information, see Run the SMC client.