HPE Morpheus VM Essentials Software
1870419 Members
3428 Online
110549 Solutions
New Discussion

[ Tools ] - [ Migration ]

 
dya
Trusted Contributor

[ Tools ] - [ Migration ]

〇HVM Cluster
   Version: HVM OS26.4, Manager v9.1.0
   HVM Host: 1 server
   Shared Storage: GFS2 x 1

〇VMware
 vcenter: 8.0.3

〇Question
 

I tried to migrate Rocky Linux 9 from VMware to a VME Cluster. I was able to do this in the past, but an issue occurred with v9.1.0.

I have confirmed from the vCenter cloud that the OS of the target VM is set correctly. However, from the results of tcpdump, I found that when running the migration plan, VME Manager and some HVM hosts are attempting to connect to the WinRM port (5985/tcp) of the target VM.

I understand that this can be avoided by unchecking it during the migration plan, but I cannot understand the behavior mentioned above. Is this a bug?

Apologies if it is hard to understand due to machine translation.

1 REPLY 1
dya
Trusted Contributor

Re: [ Tools ] - [ Migration ]

I conducted an investigation. Although the cause was unknown, the issue was resolved by removing the target VM from the VMware cloud once. The details are described below.

  1. Added one Rocky Linux 9 VM to VMware, making a total of two VMs.
    esxi-rocky9
    esxi-rocky9-2

  2. Tested the two VMs by changing their IPs as follows:

    esxi-rocky9 172.16.1.223 -> DHCP( 172.16.3.0/24 )
    esxi-rocky9-2 DHCP( 172.
    16.3.0/24 ) -> 172.16.1.223

  3. The results were as follows:
    esxi-rocky9 ... Failed with both IPs. (Connection to WinRM port (5985/tcp) occurred)
    esxi-rocky9-2 ...
    Succeeded with both IPs. (No connection to WinRM port (5985/tcp))

  4. Suspecting there was some issue with esxi-rocky9 as recognized by VME Manager, I removed the target VM from the VMware cloud, refreshed the VMware cloud, and set the VM's OS to Rocky Linux 9.

  5. When I executed the migration of esxi-rocky9 from [ Tools ] - [ Migration ], no connection to the WinRM port (5985/tcp) was observed, and the migration succeeded.