Failover cluster node show quarantine of windows server 2016

Question

_{Saturday, October 20, 2018 1:24 PM}

we have implemented server 2016 node hyper-v cluster . our one node show quarantine we have run start-clusternode cq  but the problem is same please help me.

All replies (9)

_{Tuesday, October 23, 2018 11:44 AM ✅Answered}

Multiple time we have run the commond but node going to quarantine and also i keep the node 5 hours in ideal mode but node to show quarantine in failover cluster .

We have decide to evict node from cluster again join to the cluster  afterwards it work perfect .

_{Saturday, October 20, 2018 5:14 PM}

Hello Sandeep,

Do you receive any errors/warnings when performing the Start-ClusterNode -CQ?

When a cluster node is in quarantine it means the following:

• The node is no longer allowed to join the cluster for a fixed time period (default: 2 hours)­
• This action prevents flapping nodes from negatively impacting other nodes and the overall cluster health
• By default, a node is quarantined, if it ungracefully leaves the cluster, three times within an hour
• VMs hosted by the node are gracefully drained once quarantined
• No more than 25% of nodes can be quarantined at any given time

Do you see clues in the FailoverCluster event log?

Best regards,
Leon

Blog: https://thesystemcenterblog.com LinkedIn:

_{Monday, October 22, 2018 5:42 AM}

I tried running Start-ClusterNode -ClearQuarantine command but it does not make any difference

_{Wednesday, November 7, 2018 6:53 AM}

Hi,

Thanks for your sharing and support.

Best Regards,

Frank

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Sunday, March 31, 2019 3:51 PM | 2 votes}

Hello.

We are having a similar issue.

An event had occurred to cause quarantine on 4 separate AG Clusters 2016.

The problem was cleared.

I used Failover Cluster Manager console to "start cluster service" under "more actions" on the quarantined node.

The nodes came up green and the ag databases are synching  again however the status for the quarantine node still remains "quarantine".

Start-ClusterNode -clearquarantine results with state="up"

But Get-ClusterNode returns StatusInformation="Quarantined"   still (instead of normal)

The 2 hour quarantine period is many hours past also.

I see no other issues. How do we clear this status?

Any help is appreciated.

Thanks

Mark

_{Wednesday, May 29, 2019 4:30 PM}

Thank you Mark!

Running "Start-ClusterNode -ClearQuarantine" on the node helped our situation.

_{Wednesday, June 10, 2020 6:12 PM}

I have the exact same issue, did you get any fix for this, if yes, can you share what worked with you?

Thanks.

_{Wednesday, June 10, 2020 6:13 PM}

Hello.

We are having a similar issue.

An event had occurred to cause quarantine on 4 separate AG Clusters 2016.

The problem was cleared.

I used Failover Cluster Manager console to "start cluster service" under "more actions" on the quarantined node.

The nodes came up green and the ag databases are synching  again however the status for the quarantine node still remains "quarantine".

Start-ClusterNode -clearquarantine results with state="up"

But Get-ClusterNode returns StatusInformation="Quarantined"   still (instead of normal)

The 2 hour quarantine period is many hours past also.

I see no other issues. How do we clear this status?

Any help is appreciated.

Thanks

Mark

I have same issue as quoted. any help?

_{Thursday, June 11, 2020 5:09 AM}

We had done evict the node from cluster and Reboot the node and then add the node in cluster.