Cloud platforms frequently warn about physical loss of connectivity

Cloud platforms frequently warn that physical machines are disconnected. Physical machines are in a reconnected state and cannot be used to create cloud hosts. The warning details are as follows:

(Warning information in Fig.1)

(Figure 2 Physical Offline Details)

Cloud Platform Environment: ZStack Enterprise Version 3.10.8

ZStack Enterprise Version 4.0.0

Network environment: VPC network

Primary Storage Environment: Local Storage

Mirror Server Environment: Mirror Warehouse

Physical Machine Operating System: Centos 7.3

The ZStack management node installs kvmagent on the physical machine as an agent to monitor and manage the physical machine. The above error is generally caused by the physical machine being managed by multiple sets of Zstack cloud platforms.

1. Enter the physical machine background and use the following commands to see which management nodes are managing the current physical machine

Cat / Var/log/ZStack/ZStack-kvmagent. Log |  Grep  Vmsync |  Awk  ' {print $6} '| Sort - U

Example:
 

(Figure 3 queries which management nodes manage the physical machine)

You can see that the physical machine is managed by two management nodes, 172.18.101.200 and 172.18.101.248. In this environment, 172.18.101.200 is the management node of ZStack Enterprise Version 3.10.8 and 172.18.101.248 is the management node of ZStack Enterprise Version 4.0.0. Both platforms are single-management node environments.

2. Enter one of the cloud platforms (in this environment, we enter ZStack Enterprise Version 4.0.0) and click on Resource Center--> Hardware Facilities --> Physical Machine, select the physical machine that is frequently lost, click Delete (note that deleting a physical opportunity makes the cloud hosts and related resources that depend on it unavailable on the platform, be careful)
 

(Figure 4 Delete physical machines on ZStack4.0.0 Enterprise Platform)

3. Viewed on ZStack Enterprise Version 3.10.8, the physical machine ready status shows that it is connected, and the platform no longer frequently warns physical machines of loss of connection information

(Fig. 5 Physical machine ready state returned to normal on ZStack 3.10.8)