Description

During an SMC migration job, the error message "S0_* An error occurred in the invocation of SMC by the SMC client." is reported. Possible S0_* error codes include:

• S0_U28

• S0_U7

• S0_U56

• S0_U6

• S0_U35

• S0_U52

Cause

The source server cannot establish a network connection to the required SMC service endpoints.

Solution

1. Check the SMC endpoints.

   SMC service domains include the client download address, the default activation code domain, and the Alibaba Cloud AccessKey ID/Secret (AK/SK) domain, as described below:

   • SMC client storage address:

     • Default public domain: https://p2v-tools.oss-cn-hangzhou.aliyuncs.com

   • Default public domain (for command-line import or client import by generating and entering an activation code, or entering an AK/SK):

     • Default public domain: https://smc.aliyuncs.com (server IP addresses: 101.37.132.1, 47.111.202.72).

   • Private domain (private network migration):

     • Activation code private domain: https://.axt.aliyun.com (accessible only from within Alibaba Cloud ECS).

     • AK/SK private domain: https://smc.vpc-proxy.aliyuncs.com (accessible only from within Alibaba Cloud ECS).

   Note

   • SMC domains use HTTPS on port 443 by default. HTTP on port 80 may not be supported.

   • If you can directly access a virtual private cloud (VPC) in an Alibaba Cloud region from your on-premises data center, virtual machine environment, or cloud host, consider using the private network transmission migration solution. Private network migration is faster and more stable than public network migration.

2. Check the source server's network configuration.

   1. Verify that the local network service on the source server is running and that the hosts file and DNS settings are correctly configured.

   2. SMC migrates data over the Internet by default. Make sure that the source server has Internet access.

   3. If you migrate data over a VPC, make sure that the source server is connected to the specified VPC and vSwitch. For more information, see Migrate servers over a private network.

      Note

      If you are unsure whether the source server can reach the specified VPC and vSwitch, set the Network Type parameter to Public Network when you create the migration job. If the job fails with VPC selected, switch to Public Network and try again.

3. Verify network connectivity from the source server to the SMC endpoints.

   1. On the source server, use the ping command to test basic network connectivity to the SMC endpoints.

      If the connection fails, check local network configurations and intermediate network devices. Verify that the SMC endpoint IP address is not blocked by a firewall and that the proxy server allows outbound traffic to the endpoint.

   2. Run the curl command on Linux, or open the SMC endpoint URL in a browser on Windows, to verify that the source server can reach the endpoint.

      If the test fails, check local network configurations and intermediate network devices. Verify that the IP address and port of the SMC endpoint are not blocked by a firewall and that the proxy server allows outbound traffic to the endpoint.

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