RCA – 19 – Unable to do Live Migration in a Cluster

Issue Description:

Not able to do live migration of hyper-v virtual machine, “TEST2012R2VM” from ABHOST2 to ABHOST1 using Failover Cluster Manager, (Cluster Name : TEST2012R2VM)

_____________________________________________________________________________

System Information: ABHOST1

OS Name        Microsoft Windows Server 2012 R2 Standard

Version        6.3.9600 Build 9600

Other OS Description         Not Available

OS Manufacturer        Microsoft Corporation

System Name        ABHOST1

System Manufacturer        Dell Inc.

System Model        PowerEdge R620

System Type        x64-based PC

System SKU        SKU=NotProvided;ModelName=PowerEdge R620

Processor        Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)

Processor        Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)

BIOS Version/Date        Dell Inc. 2.5.4, 1/22/2016

System Events:

Date

Time

Type/Level

Computer Name

Event Code

Source

Description

3/28/2017

1:30:46 PM

Error

ABHOST1.abc.com

21502

Microsoft-Windows-Hyper-V-High-Availability

Live migration of ‘Virtual Machine TEST2012R2VM’ failed.

3/28/2017

1:30:46 PM

Warning

ABHOST1.abc.com

1155

Microsoft-Windows-FailoverClustering

The pending move for the role ‘TEST2012R2VM’ did not complete.

System Information: ABHOST2

OS Name        Microsoft Windows Server 2012 R2 Standard

Version        6.3.9600 Build 9600

Other OS Description         Not Available

OS Manufacturer        Microsoft Corporation

System Name        ABHOST2

System Manufacturer        Dell Inc.

System Model        PowerEdge R620

System Type        x64-based PC

System SKU        SKU=NotProvided;ModelName=PowerEdge R620

Processor        Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)

Processor        Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)

BIOS Version/Date        Dell Inc. 2.5.4, 1/22/2016

System Events:

Date

Time

Type/Level

Computer Name

Event Code

Source

Description

3/28/2017

1:27:29 PM

Error

ABHOST2.abc.com

4

Microsoft-Windows-Security-Kerberos

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the
server ABHOST1$. The target name used was HTTP/BWGVMCluster.abc.com. This
indicates that the target server failed to decrypt the ticket provided by the
client. This can occur when the target server principal name (SPN) is
registered on an account other than the account the target service is using.
Ensure that the target SPN is only registered on the account used by the
server. This error can also happen if the target service account password is
different than what is configured on the Kerberos Key Distribution Center for
that target service. Ensure that the service on the server and the KDC are
both configured to use the same password. If the server name is not fully
qualified, and the target domain (abc.com) is different from the client
domain (abc.com), check if there are identically named server accounts in
these two domains, or use the fully-qualified name to identify the server.

 Plan:

 

  • We will have to focus our troubleshooting steps from the Active Directory
  • Verify if all the Computer objects with the CNO are in same OU and if all the necessary permissions are given.
  • Verify if the permissions on the DNS entries are configured correctly
  • Run Procmon on the Source and Destination host and then Reproduce the issue. Check if we are getting any Access denied.

Ashutosh Dixit

I am currently working as a Senior Technical Support Engineer with VMware Premier Services for Telco. Before this, I worked as a Technical Lead with Microsoft Enterprise Platform Support for Production and Premier Support. I am an expert in High-Availability, Deployments, and VMware Core technology along with Tanzu and Horizon.

Leave a Reply