How do I handle node is not reachable! Please check node network connection?

The node fails to be pinged, please check the network configuration and status of the node

How do I handle Authentication failed?

Please check whether the account and password entered in the migration plan are correct, and check whether the network status is normal

How do I handle current migrate partition is invalid?

Please confirm whether the configured partition contains illegal characters and paths that are not allowed, and modify it to a legal path

How do I handle check partition permission failed?

Please confirm the configured SRC_MIGRATE_ROOT_PARTITION path (default /opt) and the permissions and groups of its parent directory either the permission is 755, the group is not required, or the permission is 750, the group is ossgroup. To modify a directory permissions and groups, the command is as follows:(The following commands need to be executed by the root user)

Change directory permissions to 755: chmod 755 {directory name}

Change the directory group to ossgroup: chgrp ossgroup {directory name}

How do I handle sftp connection failed?

If the node is not hardened, check whether the node sftp can connect. If the node is hardened, please confirm whether the sftp of the migrateftpuser user can connect

How do I handle check OS type failed?

Please check if the operating system type of the node matches the actual node

How do I handle the node is occupied by others?

Check whether the IP address of the current node is known based on the details in the migration log. If the IP address is known, perform the operation again (the system automatically ignores this problem). If the IP address is not known, contact the owner of the IP address. After confirmation, you can manually delete the file as prompted or perform the operation again (the system automatically ignores this problem).

What Do I Do If the Migration Fails Because a Proxy Exists on the PC Where EasySuite Resides?

The pre-migration check fails because a proxy is configured on the PC where EasySuite resides. In this case, you need to disable the proxy configured on the PC.

{% load static %}

Windows 10 is used as an example.

  1. Open the CLI and enter set. A proxy is set, as shown in the following figure.

  2. Click Start. Right-click Computer and choose Properties from the shortcut menu. Click Advanced system settings.

  3. On the Advanced tab page, click Environment Variables.

  4. In the System variables area, select the proxy settings in step 1 and click Delete.

    This is a common proxy solution. If there are other proxies on the PC where EasySuite resides, delete them.

  5. After all proxies are deleted, restart the PC where EasySuite resides and then open EasySuite to perform the pre-migration check again.

--------------------------------------------------------------------------------In the NCE-to-NCE migration scenario, please ignore the following contents--------------------------------------------------------------------------------

How Do I Handle the Migration Failure Due to Inconsistency Between the Windows FTP Root Directory and the U2000 Root Disk?

{% load static %}
  1. According to the error information reported by EasySuite, you need to change the FTP root directory of the Windows-based U2000 to the disk D: shown in the following figure.

  2. Log in to the U2000 client.Log in to the NM client.
  3. Choose Administration > Settings > FTP Account Information Management from the main menu.

  4. In the FTP Account Information Management dialog box, click the Configure FTP Account tab and check the disk in the Home Directory column of Default local FTP account.

  5. Right-click Default local FTP account and choose Modify from the shortcut menu. In the Local xFTP Information dialog box, change Home directory to be the same as the U2000 directory confirmed in 1, that is, D. Then, click OK.

  6. If the following dialog box is displayed, click Yes. Then, click OK.

    Restart the SFTP service to for the new directory to take effect. Log in to the U2000 System Monitor client. Right-click minasshd and choose Stop the Service from the shortcut menu. In the confirmation dialog box that is displayed, click Yes. Wait until the service status changes to Stopped.

  7. Right-click minasshd again and choose Start the Service from the shortcut menu. If the service status is Running, the service is restarted successfully.

  8. Change the disk specified in the ftpserver.user.ftpuser.homedirectory field in the D:\oss\server\3rdTools\ftp\apacheftpserver\res\conf\users.properties configuration file to be the same as that in 5 and save the file. In this example, D:\oss is the U2000 installation directory.

  9. Log in to the U2000 System Monitor client. Right-click uflight_dispatcher and choose Stop the Service from the shortcut menu. In the confirmation dialog box that is displayed, click Yes. Wait until the service status changes to Stopped.

  10. Right-click uflight_dispatcher again and choose Start the Service from the shortcut menu. If the service status is Running, the service is restarted successfully.

Operations that Need to Be Performed on the Source Node that Runs Windows OS

Windows Server 2008 is used as an example.

{% load static %}

1. If the firewall of Windows OS on the source node is enabled, the network will be disconnected and the migration cannot be performed. Before the migration, ensure that the firewall is disabled.

2. Before performing all operations in this section, log in to Windows OS as the administrator. If security hardening has been performed, use the Windows security hardening account to log in.

  1. Upload the EasySuite software package (NCEV100R019C00SPC601_v*_EasySuite_Migrate.zip) to Windows OS of the U2000 server, decompress the package to any directory (whose name does not contain migrate, for example, cannot be D:\migrate), and open the project\engr\PrepareForWindowsMigration directory. The PreparingforWindowsMigration.bat file is displayed, as shown in the following figure.

    • Do not delete the preceding decompression directory before the migration rollback.
    • Before running the PreparingfoWindowsMigrate.bat script, ensure that the migrate_backup directory does not exist on Windows OS where the U2000 server is located because the initial configurations of the system is backed up in the directory. If the directory exists, move the contents in the directory to another directory and delete the directory.
    • Ensure that the four files in the preceding figure are in the same directory. The backup.ps1 file backs up the initial configurations of the system. The DoingAfterWindowsMigration.bat and restore.ps1 files are used for migration rollback. For details about the rollback procedure, see Restoring the Configuration on the Source Node that Runs Windows OS in the Migrate Guide.

  2. Right-click the PreparingforWindowsMigration.bat file and choose Run as administrator from the shortcut menu.

  3. Press any key to continue. You can resolve the problem using the solutions provided in this section or according to the displayed information in the script execution results. (If you need to specify yes/no or y/n, enter yes or y.)
  4. After the script is executed, the following CLI is displayed (which can be closed directly), indicating that the script is executed successfully. If the following CLI is not displayed, rectify the fault by referring to What Do I Do If the Windows Automatic Script Fails to Be Executed?

What Do I Do If the Windows Automatic Script Fails to Be Executed?

{% load static %}
  1. If the following information is displayed, the file is not run as an administrator. Close the console, right-click the PreparingforWindowsMigration.bat file, and choose Run as administrator from the shortcut menu. If the following information is still displayed, perform 4 to 12.

  2. If the following information is displayed, you need to log in to the U2000 System Monitor client to start the minasshd process. After the process is started, right-click the script and choose Run as administrator from the shortcut menu.

  3. If the following information is displayed (the command output may be different from that shown in the figure, and the key statement is "Access is denied"), perform 4 to 12.

  4. Ensure that you have logged in to Windows OS as the administrator for which a password has been set. If security hardening has been performed, use the Windows security hardening account to log in.
  5. If you log in to the OS as the security hardening account, check whether the OS has been restarted after security hardening. Specifically, choose Start > All Programs > Huawei > Setwin > Setwin. Check whether the program can be opened as an administrator. If the program cannot be opened, restart U2000 by referring to the U2000 Windows security hardening software and guide, and run the PreparingforWindowsMigration.bat script again. If the program can be opened, perform 6 to 12.
  6. Log in to Windows OS, click Start in the lower left corner of the desktop, and enter cmd in the search box.
  7. In the search result, right-click cmd and choose Run as administrator from the shortcut menu.
  8. In the search result, right-click cmd and choose Run as administrator from the shortcut menu.

  9. After you choose Run as administrator, the cmd console is displayed.

  10. Run the following command:

    reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

  11. Run the following command:

    cmd /c taskkill /f /im explorer.exe&&explorer.exe

  12. Run the PreparingforWindowsMigration.bat script again.
  13. The script is executed successfully. If there are other problems that are not described in this section, contact Huawei R&D engineers.