The failover is happening after draining the cluster role

Mohd Arif 921 Reputation points
2023-05-11T04:15:13.6233333+00:00

I have 5 nodes in the Hyper-V cluster, let's say node1, node2, node3, node4, and node5. Eearlier they were sharing Netapp storage for VM storage but now I moved VMs to IBM storage.

To move the VMs on IBM storage

  1. Each node had two Fiber cables, I removed one cable from each server and connected on IBM storage so at this point, one storage was coming from first FC from NetApp and IBM storage was connected via second FC
  2. I configured IBM storage in CSV and migrate all the VMs from NetApp to IBM successfully and gradually move three nodes node1, node2, node3 completely on IBM.
  3. I was removing two remaining nodes node4 and node5 today from NetApp, I already removed NetApp storage so I was just moving the cable from NetApp to IBM, But when I paused node4 I got live migration error as below.But if I do manual migration, the liver migration works. My questions why when I put a node4 in pause mode and drain the roles, live migration fails??
  4. cluster error
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,474 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,532 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,550 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.
960 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,961 Reputation points
    2023-05-18T13:23:21.9133333+00:00

    Hi,

    Thank you for reaching out. So when you pause node4 and drain the roles, the system tries to move the VMs to another node using live migration. But sometimes there can be communication issues between the nodes during this process, which can cause live migration to fail. There are a bunch of reasons why this can happen, like network problems or storage settings that aren't configured properly.

    It's possible that the network configuration on node4 isn't set up to support live migration, which could cause it to fail. But when you do a manual migration, you might be getting around that issue by using a different method to move the VMs.

    To figure out what's going on, you could check the network configuration on node4 and make sure it's set up for live migration. You might also want to take a look at the IBM storage settings and check the VMs themselves for any issues that could be causing the migration to fail. And if all else fails, reviewing the event logs on node4 and the destination node could give you some more clues about what's going wrong.

    Let me know if you had issues with the steps or need further assistance in case the issue persists. Don't forget to mention the results after the steps given above. Thank you!

    0 comments