Live Migration failing for new cluster node quick migration works on Windows 2019 Datacenter

Sven Fischer 96 Reputation points
2021-09-08T08:58:11.593+00:00

I have a 2019 Failover Cluster, failing to do Live Migrations.

Cluster is using Mellanox Adapters to synchronize with RDMA and has a shared storage pool. Cluster Checks all went green and the SPN are set correctly. Both hosts are physically identical and are both fully updated on Windows Server 2019 Datacenter. Virtual Switches are set up correctly and named identical.
Hyper-V Live Migration Settings are set to Use Kerberos and SMB and the Delegation Settings in Active Directory are set to:
SERVERA:
SERVERB's cifs, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service
SERVERB:
SERVERA's cifs, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service

I can do quick migrations without any problems, but live migrations end up in the following error:

Event ID 21502:
Live migration of 'Virtual Machine VM123' failed.

Virtual machine migration operation for 'VM123' failed at migration source 'SERVERA'. (Virtual machine ID 9B92DFDE-CC03-440A-A7F8-97FD0C85B322)

The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'SERVERB': The specified target is unknown or unreachable (0x80090303).

The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The specified target is unknown or unreachable (0x80090303).

If i google for this errors i always get to "setspn"-solutions.

I hope to get some help on troubleshooting this because this is a really urgent thing.

Appreciate your help with kind regards.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,550 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,601 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
970 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sven Fischer 96 Reputation points
    2021-09-18T07:41:02.587+00:00

    I have found out something interesting:
    Because of the urgency of this project i have reinstalled the whole cluster several times but everytime ended with this error.

    Now i found out that the Domain Controller i was setting this cluster up to was a univention DC instead of a Microsoft DC.

    I thought i'd give it a try and set this whole thing up on a Microsoft DC. Since the error was pretty much DC related there was a big chance of that being the source of the error.

    And what should I say more than: Don't got for univention DC if you want to build a cluster on it. It just emulates the microsoft DC and this leaves some error possibilities on it.

    As soon as it installed the cluster on the Windows Server 2019 DC everything worked out fine!

    Hope this helps some people!

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Limitless Technology 39,476 Reputation points
    2021-09-08T11:36:28.447+00:00

    Hello SvenFischer, try the next:

    Let's suppose that you have a receiving host name SERVERB and a source named SERVERA

    1. In Active Directory Users and Computers snap-in.
    2. From the Computers folder, right-click the computer account of the source server and then click Properties and go to the Delegation tab.
    3. Select Trust this computer for delegation to the specified services only. Under that option, select Use Kerberos only. Click Add.
    4. Click Users or Computers. In the Select Users or Computers dialog box, type the name of the destination server SERVERB .
    5. Repeate save steps for another server.
    6. on each server execute next list:

    setspn -S "Hyper-V Replica Service/SERVERA" SERVERA
    setspn -S "Hyper-V Replica Service/SERVERA.domain.local" SERVERA
    setspn -S "Microsoft Virtual Console Service/SERVERA" SERVERA
    setspn -S "Microsoft Virtual Console Service/WSERVERA.domain.local" SERVERA
    setspn -S "Microsoft Virtual System Migration Service/SERVERA" SERVERA
    setspn -S "Microsoft Virtual System Migration Service/SERVERA.domain.local" SERVERA
    net stop vmms && net start vmms
    gpupdate /force

    You may need to alternate SERVERA, SERVERB (...C, ...D) in every host to solve the issue of live migration on all hosts if appears.

    Hope this helps with your issue,
    Best regards,

    0 comments No comments

  2. Sven Fischer 96 Reputation points
    2021-09-08T11:51:40.277+00:00

    Dear @Limitless Technology

    Hyper-V Live Migration Settings are set to Use Kerberos and SMB and the Delegation Settings in Active Directory are set to:
    Kerberos Only
    SERVERA:
    SERVERB's cifs, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service
    SERVERB:
    SERVERA's cifs, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service

    setspn -l:
    Registered ServicePrincipalNames for CN=SERVERA,CN=Computers,DC=constoso,DC=corp:
    HOST/SERVERA
    HOST/SERVERA.contoso.corp
    Hyper-V Replica Service/SERVERA
    Hyper-V Replica Service/SERVERA.contoso.corp
    Microsoft Virtual Console Service/SERVERA
    Microsoft Virtual Console Service/SERVERA.contoso.corp
    Microsoft Virtual System Migration Service/SERVERA
    Microsoft Virtual System Migration Service/SERVERA.contoso.corp
    MSServerClusterMgmtAPI/SERVERA
    MSServerClusterMgmtAPI/SERVERA.contoso.corp
    RestrictedKrbHost/SERVERA
    RestrictedKrbHost/SERVERA.contoso.corp
    TERMSRV/SERVERA
    TERMSRV/SERVERA.contoso.corp
    WSMAN/SERVERA
    WSMAN/SERVERA.contoso.corp

    Registered ServicePrincipalNames for CN=SERVERB,CN=Computers,DC=contoso,DC=corp:
    HOST/SERVERB
    HOST/SERVERB.contoso.corp
    Hyper-V Replica Service/SERVERB
    Hyper-V Replica Service/SERVERB.contoso.corp
    Microsoft Virtual Console Service/SERVERB
    Microsoft Virtual Console Service/SERVERB.contoso.corp
    Microsoft Virtual System Migration Service/SERVERB
    Microsoft Virtual System Migration Service/SERVERB.contoso.corp
    MSServerClusterMgmtAPI/SERVERB
    MSServerClusterMgmtAPI/SERVERB.contoso.corp
    RestrictedKrbHost/SERVERB
    RestrictedKrbHost/SERVERB.contoso.corp
    TERMSRV/SERVERB
    TERMSRV/SERVERB.contoso.corp
    WSMAN/SERVERB
    WSMAN/SERVERB.contoso.corp

    Error still persists

    0 comments No comments