Share via

Windows failover 2 node Cluster completed Need to configure the NIC Teaming

Jayakumar D (EXT) / TELC 0 Reputation points
2025-09-24T16:25:36.5133333+00:00

hi,

I am configure 2 node failover cluster in HP- ProLiant DL360 Gen10 Plus Physical Server.

Every daily one time Node 1 automatically moved to Quarantine mode

stopped cluster in Node 1 it Will automatically resume after some time.

Local cluster node has been quarantined by 'cluster nodes'. The node will be quarantined until '2025/09/24-16:39:16.265' and then the node will automatically attempt to re-join the cluster.

Refer to the System and Application event logs to determine the issues on this node. When the issue is resolved, quarantine can be manually cleared to allow the node to rejoin with the 'Start-ClusterNode –ClearQuarantine' Windows PowerShell cmdlet.

QuarantineType : Quarantined by cluster nodes

Time quarantine will be automatically cleared: 2025/09/24-16:39:16.265

Windows for business | Windows Server | Storage high availability | Clustering and high availability
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chen Tran 3,205 Reputation points Independent Advisor
    2025-09-24T17:26:55.4066667+00:00

    Hello Jayakumar,

    Thank you for posting question on Microsoft Windows Forum.

    Based on the issue description, I would like to share my personal insight as well as my extra research into this issue.

    Well! The cluster service on each node sends regular heartbeat packets to the other nodes (over UDP port 3343 by default). If Node 2 does not receive heartbeats from Node 1 for a specific period (the SameSubnetThreshold), it assumes Node 1 is down or has a problem. If this happens repeatedly in a short time frame (by default, 3 failures within an hour), the cluster will proactively place the problematic node in quarantine to prevent it from constantly joining and leaving, which destabilizes the cluster. The following are the potential troubleshooting steps to further narrowing down cause of the issue.

    1.Check Event Logs.

    • Look at System and FailoverClustering logs around the time Node 1 goes into quarantine.
    • Pay attention to errors like Event ID 1135 (node removed from cluster) or Event ID 1561/1562 (network issues).

    2.Verify Network Configuration.

    • Ensure NIC Teaming or Switch-Independent teaming is configured correctly.
    • Confirm cluster heartbeat and storage networks are isolated and stable.
    • Test with ping -t <other node> to check for packet loss.

    3.Check Cluster Quarantine Settings.

    • Run the following PowerShell command.
    • Get-Cluster | Format-List -Property Quarantine*
    • QuarantineThreshold (default = 3)
    • QuarantineDuration (default = 7200 seconds). If needed, you can adjust these values, but it’s better to fix the root cause.

    4.Firmware & Driver Updates.

    • Update NIC drivers, BIOS, and iLO firmware on the HPE ProLiant DL360 Gen10 Plus servers.
    • HPE provides a Service Pack for ProLiant (SPP) that bundles tested firmware and drivers.

    5.Storage Path Validation.

    • Run Cluster Validation Wizard from Failover Cluster Manager.
    • Check for warnings on storage, networking, or system configuration.

    You can refer to the following article for more information.

    Hope the above information is helpful!

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.