HOTSPOT
A company has a Windows Server 2012 R2 Hyper-V environment that contains a single Active Directory
Domain Services domain named Contoso.com. The environment also has three servers named Host1, Host2,
and Host3 that have the Hyper-V role installed. Youconfigure all of the hosts as a single failover cluster. You
have two guest clusters named VM-Cluster1 and VM-Cluster2. The environment is configured as shown in the
following diagram:
When a virtual machine guest cluster node is migrated to another host, the guest cluster fails over tothe other
node. You must provide high availability for all virtual machines. Guest clusters must NOT fail over if they are
migrated to another host.
You need to configure the guest clusters.
Use the drop-down menus to complete each statement based on the information presented in the screenshot.
Each correct selection is worth one point.
Answer:
Explanation:
SameSubnetDelay and SameSubnetThreshold seem the right answers, even do I didn’t find anything more recent than this:
http://www.happysysadm.com/2012/01/vmotion-of-mscs-cluster-nodes-running.html
I believe the idea here is that heartbeat threshold and delay between the guest nodes is set too low. Live migrations take time and the heartbeat is activating a failover of the guest cluster before the migration can complete. Increasing the thresholds will allow sufficient time for the migration to complete and stop the failover from occurring.
For clarification:
http://blogs.msdn.com/b/clustering/archive/2012/11/21/10370765.aspx
http://technet.microsoft.com/en-us/library/dn440540.aspx
Protect against short-term network interruptions
Failover cluster nodes use the network to send heartbeat packets to other nodes of the cluster. If a node does not receive a response from another node for a specified period of time, the cluster removes the node from cluster membership. By default, a guest cluster node is considered down if it does not respond within 5 seconds. Other nodes that are members of the cluster will take over any clustered roles that were running on the removed node.
Typically, during the live migration of a virtual machine there is a fast final transition when the virtual machine is stopped on the source node and is running on the destination node. However, if something causes the final transition to take longer than the configured heartbeat threshold settings, the guest cluster considers the node to be down even though the live migration eventually succeeds. If the live migration final transition is completed within the TCP time-out interval (typically around 20 seconds), clients that are connected through the network to the virtual machine seamlessly reconnect.
To make the cluster heartbeat time-out more consistent with the TCP time-out interval, you can change the SameSubnetThreshold and CrossSubnetThreshold cluster properties from the default of 5 seconds to 20 seconds. By default, the cluster sends a heartbeat every 1 second. The threshold specifies how many heartbeats to miss in succession before the cluster considers the cluster node to be down.