Windows 10: Windows Server 2019 Failovercluster physical mgmt cluster nic connection error

We have a 2 Node MS Failovercluster on Windows Server 2019 in use. The network configuration is based on several physical multiport nics where the Hyper-V Switch is on Broadcom 10GBit 57412 NIC´s SET teaming and servicing the cluster VM´s and CSV network. The Cluster management network is an separate Intel 1 GBit 350 -T4 NICs as Host-based LBFO teaming and generally working as designed.During the backup hours in the night the cluster management network is producing Cluster Event ID´s 1126 and 1129 and the Cluster configuration cannot be accessed in a timely manner.The problem is repeating each

:)

 

Managing Server 2019 clustering

SQL Server 2019 Always-on implemented on 2 Nodes on Windows Server 2022 and when i perform manual failover to the second node I got this warning "the current wsfc cluster quorum vote configuration is not recommended for this availability group", and the Always-on availability group is healthy and no problem with it.

i tried the following without no luck

1. Update Windows Server 2022 to latest update
   
2. reconfigure WSFC quorum to use Defualt configuration
   
3. reconfigure WSFC quorum to use Witness fileShare.
   

 

2 NICs on Windows 2019 for SQL Server AlwaysOn Availability Group - RPC keeps failing

Hi all,

I wonder if anyone can help, I am stuck with a problem where the RPC service keeps failing every time I try to set up a new WSFC;

The clustered role was not successfully created. For more information view the report file below.

Report file location: C:\Windows\cluster\Reports\Create Cluster Wizard wsfcluster on 2022.05.09 At 09.19.49.htm

New-Cluster : An error occurred while performing the operation.

An error occurred while creating the cluster 'wsfcluster'.

An error occurred creating cluster 'wsfcluster'.

The RPC server is unavailable

Here is my setup (in AWS):

2x EC2 Instances

2x NICs

Server 1:

NIC 1 - Range 172.22.208.128/26

NIC 2 - Range 172.22.208.192/27

Server 2:

NIC 1 - Range 172.22.209.128/26

NIC 2 - Range 172.22.209.192/27

Problem:

When trying to run New-Cluster cmdlet, I keep receiving the RPC server is unavailable.

Steps taken so far:

- Checked all firewall settings, made sure Port 135 was open, remote assist, IPv6, etc. All Open.

- Turned firewall off, still no different.

- Rebooted RPC service.

- Check IP routing via route print cmdlet. Everything looks right.

Things to note:

- The CIDR ranges are on the same VPC so can communicate.

- The 2 nodes in question have communication between all ports open between them from a security group point of view.

- I have built 2 clusters successfully with only 1 NIC each follow all the same steps, this has only been a problem since adding a secondary NIC.

- The Test-Cluster cmdlet comes back with no issues at all.

Cheers,

James

 

Windows Failover Clustering - SQL Server - Latency on Connection

Hello,

We've just set up a two-node Windows Failover cluster (WFSC) on Windows Server 2019 across AWS regions (Oregon and Ohio) using Sios DataKeeper to replicate the files. We installed two SQL 2017 instances on the cluster. We adjusted the heartbeat settings to be more forgiving of a multi-subnet config with 2 seconds instead of 1 on the cross-subnet settings. (We run 4 other clusters across AWS Availability Zones (AZ) with no problems, this is our first cross-region cluster.)

There were no issues during setup. The two roles can easily move between the two hosts with no hesitation or errors.

The problem we're having is that sporadically, connections to the SQL instances can take up to 5-10 seconds to connect. In a tool like SQL Server Management Studio, it will always eventually connect, but some things time out. Annoyingly, if you disconnect and reconnect, it will sometimes instantly reconnect. Other times, not.

We don't see this behavior on any of our cross-AZ clusters, only this new cross-region cluster. There's no errors or warning in the Windows Logs, or any of the Failover Clustering logs, including verbose.

Anybody have any ideas or suggestions?

Thanks.