- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus VM Essentials Software
- >
- [ Tools ] - [ Migration ]
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
a week ago
[ 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday - last edited Friday
Friday - last edited Friday
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.
Added one Rocky Linux 9 VM to VMware, making a total of two VMs.
esxi-rocky9
esxi-rocky9-2Tested 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.223The 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))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.
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.