Components Fail to Be Collected in a System Migration Project Due to a Node Connection Error

Symptom

Components fail to be collected in a system migration project. An error is reported indicating that the node is unreachable.

Possible Causes

• In the multi-node scenario, the time on the server or agent node may be incorrect. As a result, the certificate validity verification fails during connection establishment.
• The node where the tool is installed may have a firewall. As a result, the tool cannot communicate with the collected node through a port.

Troubleshooting Procedure

• If the time on the server node is incorrect or the times on both the server and agent nodes are incorrect, perform the following operations:
  1. Calibrate the time of each server node.
     1. Use the NTP server to synchronize the times, ensuring the consistency between the system time and the standard time.
     2. When checking the time of a node, note the time inconsistency caused by the time zones.

        For example, if that the time zone of the node on which the tool is installed is China Standard Time (CST) and that of the node whose components are to be analyzed is Eastern Daylight Time (EDT), you can change EDT to CST.

        1 2	mv /etc/localtime /etc/localtime.bak ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

  2. Reinstall the DevKit. After the installation is complete, add the node again.

• If the time on the server node is correct but the time on the agent node is incorrect, perform the following operations:
  1. Uninstall the agent.
  2. Calibrate the time of the agent node. For details, see 1.
  3. Reinstall the agent.
• If the node connection is blocked by the firewall, perform the following operation:

  In the firewall settings of the installation node, allow the Agent to access the listening port (50051 by default) of the RPC service. For details, see Enabling the Firewall Port.