SQL Server Always On Series-Event id: 1135- Cluster Node 'JBSAG2' was removed from failover cluster

SQL Server Always On Series - Event id: 1135 - Cluster Node 'JBSAG2' was removed from the active failover cluster membership ‪@jbswiki‬#sqlserver #alwayson #cluster
Good day everyone. We will discuss about Event id: 1135 - Cluster Node 'JBSAG2' was removed from the active failover cluster membership.
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Event ID: 1135
Description:
Cluster node 'JBSAG3' 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.
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
Cluster node 'JBSAG3' has been quarantined. The node experienced '3' consecutive failures within a short amount of time and has been removed from the cluster to avoid further disruptions. The node will be quarantined until '2023/03/25-11:02:16.386' 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.
Node Name : JBSAG3
Number of consecutive cluster membership loses: 3
Time quarantine will be automatically cleared: 2023/03/25-11:02:16.386
No matching network interface found for resource 'IP Address 192.168.1.0' IP address '192.168.1.20' (return code was '5035'). If your cluster nodes span different subnets, this may be normal.
Name resolution for the name 6.1.20.172.in-addr.arpa. timed out after none of the configured DNS servers responded.
The local availability replica of availability group 'JBAG' is in a failed state. The replica failed to read or update the persisted configuration data (SQL Server error: 41005). To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
Cluster service failed to start because this node detected that it does not have the latest copy of cluster configuration data. Changes to the cluster occurred while this node was not in membership and as a result was not able to receive configuration data updates.
Guidance:
The Cluster Service service terminated with the following service-specific error:
A quorum of cluster nodes was not present to form a cluster.
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.
[System] 00002420.00002004::2020/01/01-00:40:48.745 DBG Cluster node 'JBSAG3' 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.
[System] 00002420.00002004::2020/01/01-00:40:48.746 DBG Cluster node 'JBSAG2' 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.
[System] 00002420.00004598::2020/01/01-00:40:48.809 DBG The Cluster service was halted to prevent an inconsistency within the failover cluster. The error code was '1359'.
[System] 00002420.0000438c::2020/01/01-00:40:49.173 DBG The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.
[System] 00002420.00005e5c::2020/01/01-00:40:49.174 DBG The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.
You can check what these values are before and after the change using below command,
get-cluster | fl subnet
(get-cluster).SameSubnetDelay = 2000
(get-cluster).CrossSubnetDelay = 4000
Reference : jbswiki.com/2020/01/07/always...