Exch 2010: IP Conflict and cluster name offline when live migrating on HyperV

Home Forums Messaging Software Exchange 2007 / 2010 / 2013 Exch 2010: IP Conflict and cluster name offline when live migrating on HyperV

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #161124

    HyperV 2008 R2
    2 nodes actve-active

    Exchange 2010
    DAG with 2 nodes

    When I live migrate I get the following errors

    File share witness resource ‘File Share Witness (\ex2010quorum.cemm.localDAG.cemm.local)’ failed a periodic health check on file share ‘\ex2010quorum.cemm.localDAG.cemm.local’. Please ensure that file share ‘\ex2010quorum.cemm.localDAG.cemm.local’ exists and is accessible by the cluster.

    -> Thats not true. It’s online and working.

    Cluster resource ‘File Share Witness (\ex2010quorum.cemm.localDAG.cemm.local)’ in clustered service or application ‘Cluster Group’ failed.

    Cluster node ‘CEMMSRV119’ was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

    Cluster IP address resource ‘Cluster IP Address’ cannot be brought online because a duplicate IP address ‘193.171.186.253’ was detected on the network. Please ensure all IP addresses are unique.

    Cluster resource ‘Cluster IP Address’ in clustered service or application ‘Cluster Group’ failed.

    Cluster IP address resource ‘Cluster IP Address’ cannot be brought online because a duplicate IP address ‘193.171.186.253’ was detected on the network. Please ensure all IP addresses are unique.

    Cluster resource ‘Cluster IP Address’ in clustered service or application ‘Cluster Group’ failed.

    The Cluster service failed to bring clustered service or application ‘Cluster Group’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.