none
Windows 2012 R2 Cluster Fails - RDM Disks

    Întrebare

  • Hi Everyone,

    We have a 2 node Windows 2012 R2 Failover cluster configured with Shared RDM's running on VMware. All of a sudden, the resources got failed over to the other node.

    Below are the sequence of events triggered.

    Ownership of cluster disk 'Cluster Disk 3' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

    Cluster resource 'Cluster Disk 3' of type 'Physical Disk' in clustered role 'XXXX' failed.

    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    Ownership of cluster disk 'Cluster Disk 2' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

    Ownership of cluster disk 'Cluster Disk 4' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

    Can someone let me know what was actually happened here. 


    miercuri, 4 iulie 2018 19:05

Toate mesajele

  • Hi,

    Thanks for your question.

    According to the error message, please check the network communication between cluster nodes and storage disks if it works properly.

    Is the cluster disks configured with iSCSI or SAN? Please also check the storage connection drivers.

    Hope this helps. I look forward hearing your good news.

    If you have any question and concern, please feel free to let me know.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    joi, 5 iulie 2018 08:08
    Moderator
  • Hi

    Most probably the VMs have lost the connection to the disk because all the disks have been lost at the same time. Please check the physical connections.

    Also go through the logs in the ESXi host for more information on this

    Regards,
    Bala N

    joi, 5 iulie 2018 08:12
  • Hi,

    How are things going on? Was your issue resolved?

    Please feel free to let us know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    vineri, 6 iulie 2018 07:05
    Moderator
  • Hi Michael,

    Issue is resolved after we restarted the cluster service on one node. By doing this all the cluster core resources came online. But we would like to know what caused this issue.  These RDM disks are directly mapped to this VM's from 3 PAR storage and they are shared RDM's between the hosts.

    We have checked with our VMWare team and they said as RDMs will be directly mapped to VM, no ESXI role would be present.

    Looking forward for your response.

    Regards,

    Srinivas0781

    vineri, 6 iulie 2018 20:57
  • "checked with our VMWare team and they said as RDMs will be directly mapped to VM, no ESXI role would be present."

    Interesting statement.  RDM disks are unique to VMware.  They have nothing to do with Windows or Hyper-V server.  The only way they can be presented to VMs is via ESX services.  VMware has its own rules for configuring clusters with RDM disks because it is not a format that is natively recognized by Windows.  When using RDM disks presented to a cluster, you need to rely on VMware.  Microsoft does not have access to any of that code.


    tim

    sâmbătă, 7 iulie 2018 12:19