Share via

Windows Server 2019 - Hyper-V - FailOver Cluster | CSV Change Node Owner Failure

Anonymous
2022-01-15T12:05:11.183+00:00

Our Hyper-V Architecture is as following:

2 Physical Nodes , On each one , Windows Server 2019 Datacenter
Hyper-V Role installed on each one
Failover Cluster
Nimble Storage
iSCSI connection between the Hyper-V Nodes to Nimble Storage Array
MPIO on Windows is Enabled
Nimble DSM for Windows MPIO is installed

both Physical servers can communicate within the iSCSI network to the Nimble Storage , it is not network issue on the iSCSI network , I already checked this and I can say 100% this is not Network issue on the iSCSI network.

The LUN on Nimble is accessible by both 2 Physical Nodes , so this is not the problem.

now what is the problem ?

The Problem is with changing Cluster Disk (CSV) Node owner.
one I try to move the owner on the CSV then I encounter an issue.

here are some screenshots of the errors:

165293-1.jpg

and more screenshots of the errors:

165294-2.jpg

and more screenshots of the errors:

165240-3.jpg

and more screenshots of the errors:

165335-4.jpg

and more screenshots of the errors:

165351-5.jpg

and more screenshots of the errors:

165352-6.jpg

and more screenshots of the errors:

165277-7.jpg

and more screenshots of the errors:

165248-8.jpg

and more screenshots of the errors:

165255-9.jpg

and more screenshots of the errors:

165249-10.jpg

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
Windows for business | Windows Server | Storage high availability | Clustering and high availability
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
Windows for business | Windows Server | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Nico 0 Reputation points
    2023-01-18T10:27:40.2133333+00:00

    Hi! We too are seeing the same issue in our environment. Same configuration as onemancrew.

    No results with tiket in Hpe and Microsoft.

    Were you able to solve the problem?

    Thanks!

    Was this answer helpful?

    0 comments No comments

  2. Joseph D Varner 1 Reputation point
    2022-07-27T20:20:06.98+00:00

    I wish I had an answer for you. We are seeing the same issue in our environment. Very similar setup to you, same errors, and the only difference is we have 4 physical nodes.

    You asked this back in January and NO one from MS has answered. Speaks volumes.....

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.