FailoverCluster: Workaround - Cluster Resource-Timeout (VM switch to another ClusterNode - ResiliencyPeriod)
Aus Wiki-WebPerfect
ResiliencyDefaultPeriod = Duration (in seconds) to allow VM to run on a isolated Node with status "Unmonitored" (before the VMs are switched to another Node.)
Change the ResiliencyDefaultPeriod (Default = 240):
(Get-Cluster).ResiliencyDefaultPeriod = <value>
Additional Information
- Service "VMMS" stopped -> Node = Up & VMs = Up (Can't change Setting of VM or Hyper-V Node)
- Service "SCVMMAgent" stopped -> Node = Up & VMs = Up (VM-Status in VMM = "Host Not Responding")
- Host not reachable (NIC disabled) -> Node = Isolated & VMs = Unmonitored
- If Hyper-V Node is in Status Isolated: After ResiliencyDefaultPeriod -> Node = Down & VMs = switched to another ClusterNode)
More Information: