SMS.3802 Failed to Establish an SSH Connection with the Target Server
Symptom
The migration task failed, and you received the error message "sms.3802 Failed to establish an SSH connection with the target server."
Problem Analysis
During a migration, an SSH connection must be established between the source server and target server. If the SSH connection is not set up, the preceding error message is displayed. You are advised to review the following parts to locate the cause of the SSH connection failure.
- Checking Whether Port 22 Is Allowed in the Security Group of the Target Server and Whether the Source IP Address Is Configured Correctly
- Checking Whether the Target Server Is Stopped
- Checking Whether the VPC or IP Address of the Target Server Is Changed During the Migration
- Checking Whether the Migration Is Performed over a Private Network that Is Not Connected to the Target Server
- Checking the Firewall Settings of the Source Server
- Checking Whether Security Alarms Are Generated on the Source or Target Server or the EIP of the Source or Target Server Is Frozen
- Checking Whether the Public Keys on the Linux Source and Target Server Are the Same
Checking Whether Port 22 Is Allowed in the Security Group of the Target Server and Whether the Source IP Address Is Configured Correctly
- Log in to the management console.
- Under Compute, click Elastic Cloud Server. In the ECS list, click the name of the target ECS.
- On the ECS details page, click the Security Groups tab. Check whether port 22 is opened and whether the source IP address is specified correctly.
If port 22 is not opened in the inbound direction, add an inbound rule for port 22. If such an inbound rule exists but the source IP address is not 0.0.0.0/0 or the IP address of the source server, change the source IP address to 0.0.0.0/0.
For details, see How Do I Configure Security Group Rules for Target Servers?
Checking Whether the Target Server Is Stopped
- Log in to the management console.
- Under Compute, click Elastic Cloud Server. Locate the target ECS and view its status. If the ECS is stopped, choose More > Start in the Operation column.
Checking Whether the VPC or IP Address of the Target Server Is Changed During the Migration
If the VPC or IP address of the target server is changed during the migration, change it back to the original VPC or IP address. Otherwise, you will need to repeat the migration.
Checking Whether the Migration Is Performed over a Private Network that Is Not Connected to the Target Server
Check whether a private network is used for the migration and whether the source and target servers are in different private networks. If yes, use the public network for migration or connect the two private networks.
Checking the Firewall Settings of the Source Server
Check whether the outbound traffic is blocked by the source server firewall. If yes, permit the traffic and continue the migration.
Checking Whether Security Alarms Are Generated on the Source or Target Server or the EIP of the Source or Target Server Is Frozen
Check whether security alarms are generated on the source or target servers or the EIP of the source or target server is frozen.
- If this problem is happening on the source server, contact the source cloud service provider for troubleshooting.
- If this problem is happening on the target server, contact Huawei Cloud for troubleshooting.
Checking Whether the Public Keys on the Linux Source and Target Server Are the Same
During the migration, an SSH public key that matches the target server is generated in the /root/.ssh/known_hosts file on the source server, as shown in the following figure. sms@localhost indicates that the public key is generated by the SMS Agent. {target_ip} indicates the IP address used for migration of the target server.
Compare the public key file with that of the corresponding key pair algorithm in /etc/ssh on the target server. If there is any inconsistent information, delete the corresponding lines from the /root/.ssh/known_hosts file on the source server, delete the migration task, and perform the migration again.
Known Errors and Solutions FAQs
- SMS.0202 AK/SK Authentication Failed. Ensure that the AK and SK Are Correct
- SMS.0203 Connection from Source Server to API Gateway Timed Out
- SMS.0204 Insufficient Permissions. Obtain the Required Fine-Grained Permissions
- SMS.0205 Incorrect System Time or Time Zone On Source Server
- SMS.0206 Only x86 Servers Can Be Migrated
- SMS.0210 Failed to Create File on Target Server
- SMS.0303 Unable to Access Domain Name
- SMS.0410 Failed to Obtain NIC Information
- SMS.0412 Target Server Does Not Exist
- SMS.0515 Migration Failed. Source Disk Information Has Changed. Delete Target Server Configuration and Restart the Agent
- SMS.0609 An Older Version of Agent Is Detected. Please Exit The Current Program, Uninstall the Old Agent Completely, and Install the Newest One
- SMS.0805 Failed to Migrate Partition to Target Server
- SMS.0806 Failed to Synchronize Partition to Target Server
- SMS.1105 Disk Creation Failed
- SMS.1106 Failed to Delete Disk XXX
- SMS.1204 Failed to Create File on Source Server
- SMS.1205 Failed to Load WMI
- SMS.1351: Mount Point /xxx Detected on the Source Server, Which Has No Free Space. Ensure that There Is at Least 1 MB of Space
- SMS.1352: Unknown Physical Volumes Detected on the Source Server
- SMS.1353: Bind Mount or Repeated Mount Detected on /xxx of the Source Server
- SMS.1402 SSH Client Not Installed
- SMS.1414 The Migration Module Stopped Abnormally and Cannot Synchronize Data
- SMS.1807 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Confirm that Port 8900 Is Enabled
- SMS.1901 Agent Could Not Read Disk Information
- SMS.1902 Failed to Start the I/O Monitoring Module
- SMS.1904 Failed to Create a Snapshot for the Windows Server
- SMS.2802 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Port 8899 Is Enabled
- SMS.3205 Failed to Mount Partition XXX to Directory XXX
- SMS.3802 Failed to Establish an SSH Connection with the Target Server
- SMS.5102 Agent Startup Failed Because the noexec Permission Is Unavailable on /tmp in Linux
- SMS.5105 Agent Startup Failed. Insufficient Permissions to Add Files to or Delete Files from xxx
- SMS.5108 Failed to Execute df -TH
- SMS.6303 The Installed Agent Is of an Earlier Version. Download the Latest Version
- SMS.6509 Incompatible File System of the Source Server
- SMS.6511 The Source Server Lacks Driver Files
- SMS.6517 rsync Not Installed on the Source Server
- SMS.6528 Complete Real-name Authentication to Invoke SMS APIs
- SMS.6533 VSS Not Installed on the Source Server
- SMS.6537 SMS Cannot Migrate System Disks Larger Than 1 TB
- SMS.6562: Component i386-pc Not Found on Source Server For solution, see SMS API Reference
- SMS.6563: File initrd or initramfs of the xxxx version Not Found Under /boot Directory For solution, see SMS API Reference
- SMS.6616 The Current OS Does Not Support Block-level Migration/SMS.6617 The Current Kernel Version Does Not Support Block-level Migration
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore