The two-node cluster is set up and running without any problems as far as I can tell BUT: The cluster validation test gives this warning.

Failed to validate Server Message Block (SMB) share access through the IP address of the fault tolerant network driver for failover clustering (NetFT). The connection was attempted with the Cluster Shared Volumes test user account, from node Hyper-V22.contoso.local to the share on node Hyper-V23.contoso.local. Access is denied.

and

Failed to validate Server Message Block (SMB) share access through the IP address of the fault tolerant network driver for failover clustering (NetFT). The connection was attempted with the Cluster Shared Volumes test user account, from node Hyper-V23.contoso.local to the share on node Hyper-V22.contoso.local. Access is denied.

During the test, this error occurs in the SMBClient log of the node.

169.254.1.88 is the address of the other node's Tunnel Failover Cluster Virtual Adapter.

I cannot ping the remote node's Failover Cluster Virtual Adapter IP address. The firewall is off on all profiles. What is wrong here?

Good day,

I am in the process of upgrading my HyperV servers from 2012r2 to 2016 and came across a question I had not thought about.  Can I run a clustered HyperV system with two <g class="gr_ gr_171 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="171" id="171">differnet</g> versions of Server hosts, 2 - 2012r2 and 1 - 2016? I was going to just <g class="gr_ gr_356 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" data-gr-id="356" id="356">crate</g> a new server and add it in but I am not able to find any documentation of <g class="gr_ gr_678 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="678" id="678">teh</g> best way to remove a node from the cluster and add one to the cluster.  I would like to just build 3 2016 servers and add them to the cluster and remove the others,

Really any help would be appreciated, I ran across a couple of step by steps for other items and those seemed to help the staff be successful and since we are in the medical field everyone wants to be perfect.

Thank you in advance for either question suggestion or answer,

Michael Deininger

Southwest Transplant Alliance

Hi,

Within Windows failover cluster manager I can see my SQL 2012 Always On Availability Group under Roles.
Within the Availability Group; I can add a Client Access Point (AG listener) - manually in the GUI or via the following command:

Add-ClusterResource -Name "crag3" -ResourceType "Network Name" -Group "Contoso-ag1"

Question is, how do I add the "IP Addresses" to this Network Name Resource using PowerShell?
I can do it via the GUI.

Thanks in advance for any help,
HM

Crag2 - was done manually using the GUI and works as expected.

Crag3 - I've created the first part using the above PS command; however I can't figure out how to add the "IP Address" now.

Hello Team,

We are getting missed heartbeat alerts. below is the log from cluster log:

Node 1: Executing locally gumId: 11221, updates: 1, first action: /dm/update
00000b48.00002aa0::2019/08/18-10:08:56.164 INFO  [GUM] Node 1: Executing locally gumId: 11222, updates: 1, first action: /dm/update
00000b48.00002aa0::2019/08/18-10:08:56.183 INFO  [GUM] Node 1: Executing locally gumId: 11223, updates: 1, first action: /dm/update
00000b48.00002f98::2019/08/18-10:08:56.322 INFO  [GUM] Node 1: Executing locally gumId: 11224, updates: 1, first action: /dm/update
00000b48.00002f98::2019/08/18-10:08:56.352 INFO  [GUM] Node 1: Executing locally gumId: 11225, updates: 1, first action: /dm/update
00000b48.00001994::2019/08/18-10:09:02.319 INFO  [IM] got event: LocalEndpoint 137.201.104.205:~3343~ has missed two-fifth consecutive heartbeats from 137.201.104.206:~3343~

cluster validation report : 

The cluster network name xxxxxxx does not have Create Computer Objects permissions on the Organizational Unit OU=Servers,OU=Boise,OU=AMER,DC=na,DC=micron,DC=com. This can result in issues during the creation of additional network names in this OU.

The following servers have updates applied which are pending a reboot to take effect. It is recommended to reboot the servers to complete the patching process.
xxxxxxx
xxxxx

00000b48.00001994::2019/08/18-10:09:02.319 INFO  [CHM] Received notification for two-fifth consecutive missed HBs to the remote endpoint 137.201.104.206:~3343~ from 137.201.104.205:~3343~

00000b48.00002aa0::2019/08/18-10:09:02.334 INFO  [CHM] My weights have changed from 0 to 0 0 110

second server :

00002030.00002bc4::2019/08/18-10:09:08.931 INFO  [RES] SQL Server Availability Group: [hadrag] SQL Server component 'io_subsystem' health state has been changed from 'clean' to 'warning' at 2019-08-18 04:09:08.577

00002030.00002bc4::2019/08/18-10:09:18.927 INFO  [RES] SQL Server Availability Group: [hadrag] SQL Server component 'io_subsystem' health state has been changed from 'warning' to 'clean' at 2019-08-18 04:09:18.577

0000301c.00002e54::2019/08/18-10:09:26.324 INFO  [IM] Changing the state of adapters according to result: <class mscs::InterfaceResult>

Please let us know why this heartbeat missing errors come in what kind of situations. Cx told it is not an issue with network. it is vmware

swathi

I have an application which is clustered, currently it writes a log to the hardware that is the active host, if the cluster fails over then the log is created and updated on the new host.

Can I use a scale out cluster to host the log file?

Im concerned about the comments of not changing file metadata rapidly. The log will write several times a second.

Thanks

Hello,

I have a SQL alwaysON setup between on-prem and Azure SQL server (IaaS). Its a 2 node cluster and have configured file share witness for the quorum( On one of the Azure server). There is a site-to-site VPN configured to facilitate all these. 

Of late , we see our primary DB going down due to instability in cluster. It was noticed that our network goes down there by making secondary node and file share in accessible and cluster gets affected . Due to which all the primary DBs becomes in accessible and application downtime. 

This setup was primarily built for DR purpose and accordingly we have placed the quorum on Azure side.

How can we avoid this situation. I assume all this is due to unavailability of Azure node and File share witness ( this too on Azure) are in accessible at the same time whenever network goes down. 

Is there any configuration changes I can make to make the on-prem stable irrespective of the status of secondary node. 

what quorum method I should adapt for these kind of situation. Please help. 

HI,

I've just got a warning from my cluster that one of my CSVs was stopped. But I just dont get what was going on.

From the Failoverclustering-CsvFs protocol I get this message:

"Volume {44179469-89e8-4971-b9ff-057c4579c647} is autopaused. Status 0xC00000C4. Source: Single client contification start."

What does that even mean? Single Client contification?

Best Regards

Daniel

Hi all,

We have two server are running under vmware(esxi) environment. And each VM machine is running Windows 2016 Std. OS and one static IP address. I installed and configured NLB on each server as per this Network Load Balancing documentation. I used "Multicast" mode during NLB configuration. I got below error when i open the NLB application.

Warning
---------------------------
Running NLB Manager on a system with all networks bound to NLB might not work as expected.
If all interfaces are set to run NLB in "unicast" mode, NLB Manager will fail to connect to hosts.
See "Help and Support Center" for unicast communication limitations.
---------------------------
OK   
---------------------------

I don't know why i got above error message even i set "multicast" at nlb configuration. We would like to use "Multicast" mode instead of "Unicast". Do i need to set some configuration on VMware ESXI and switch or router to work NLB with multicast mode. We are using cisco switch.

Best Regards,

Yukon

Make Simple & Easy

Hello Hopefully this is the right location to post this, Our team is setting up Windows failover cluster to be access from across subnets. initially this is in a test environment. the issue we are seeing is that the clients who are on subnet A cannot speak to the Cluster network object nor the IP for the cluster name, which is on Subnet B. The clients can communicate fine with each of the nodes directly just not the cluster name/IP. Also Clients that are on the Same Subnet B can speak to the Cluster Name/IP fine. just not cross subnet. The switch that is connecting both subnets is a cisco 2960G. windows firewall is disabled as well.

Below is a brief diagram of the setup

Client subnetA => Ciscos 2960 <=> Cluster subnetb 

Since the clients can reach the host individually, and the clients that are on the same subnet can access the cluster resources fine. I am leaning towards this may require a feature/capability in the network to handle communicating to a mac/ip address handled by the cluster. 

Can anyone here point me in the right direction, any assistance most appreciated.

This is 3 node production cluster ( multi subnet cluster). It was working fine. I evicted the DR node and tried to add it back, it throws an error.

I am having issues only in adding the DR node. However I can able to add the DR node to my non-prod or Dev existing cluster. 

FailoverCluster EventViewer

Log Name:      Microsoft-Windows-FailoverClustering/Operational
Source:        Microsoft-Windows-FailoverClustering
Date:          5/09/2019 3:39:06 PM
Event ID:      1281
Task Category: Security Manager
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      DRNODE.orionhealth.saas
Description:
Joiner tried to Create Security Context using Package='Kerberos/NTLM' with Context Requirement ='0' and Timeout ='40000' for the target = 'akl-shrd-pdb1'


Log Name:      Microsoft-Windows-FailoverClustering/Operational
Source:        Microsoft-Windows-FailoverClustering
Date:          5/09/2019 3:38:53 PM
Event ID:      1650
Task Category: Cluster Virtual Adapter
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      DRNODE.orionhealth.saas
Description:
Microsoft Failover Cluster Virtual Adapter (NetFT) has missed more than 40 percent of consecutive heartbeats.

Local endpoint: 10.13.6.200:~3343~
Remote endpoint: 10.10.6.190:~3343~


Error in powershell:-

The clustered role was not successfully created. For more information view the report file below.
Report file location: C:\Windows\cluster\Reports\Add Node Wizard 76cd451a-538a-4fbe-9c52-2f9498396d17 on 2019.09.05 At 15.35.42.htm
Add-ClusterNode : An error occurred while performing the operation.
    An error occurred while adding nodes to the cluster 'CLUST'.
    An error occurred while adding node 'NODE3' to cluster 'CLUST'.
    This operation returned because the timeout period expired



DR Cluster log:

00000918.00001528::2019/09/05-00:59:08.498 DBG   [NETFTAPI] Signaled NetftLocalConnect event for fe80::14:a91:8f79:5d8f
00000918.00001528::2019/09/05-00:59:08.498 DBG   [NETFTEVM] FTI NetFT event handler got event: Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.00001230::2019/09/05-00:59:08.498 DBG   [NETFTEVM] FTI NetFT event dispatcher pushing event: Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.00001230::2019/09/05-00:59:08.498 DBG   [FTI][Initiator] Got Netft event Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.00001528::2019/09/05-00:59:08.498 DBG   [NETFTEVM] TM NetFT event handler got event: Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.0000096c::2019/09/05-00:59:08.498 DBG   [NETFTEVM] TM NetFT event dispatcher pushing event: Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.0000096c::2019/09/05-00:59:08.498 INFO  [IM] got event: Local endpoint fe80::14:a91:8f79:5d8f:~0~ connected
00000918.00001528::2019/09/05-00:59:08.498 DBG   [WM] Filtering event NETFT_LOCAL_CONNECT? 1
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [NODE] Node 1: New join with n4: stage: 'Send Current Membership Status for Join Policy'
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [MM] Node 1: Adding a stream to existing node 4
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [NODE] Node 1: n4 node object adding stream
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [NODE] Node 1: n4 node object got a channel
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [NODE] Node 1: Using new stream to n4, setting epoch to 1
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [NODE] Node 1: Done closing stream to n4
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [NODE] Node 1: My Fault Tolerant Session Id is now 8d14d294-1635-416f-9e7c-44450c2a9cce
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [NODE] Node 1: No reconnect in progress to n4, updating send queue based on new stream.
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [NODE] Node 1: Treating stream with n4 as new connection because epoch (1) is <= 1.
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [MQ-Node1] Clearing 0 unsent and 0 unacknowledged messages.
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [NODE] Node 1: Highest version with n4 = Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008, lowest = Major 8 Minor 9600 Upgrade 3 ClusterVersion 0x00080003
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [NODE] Node 1: Done processing new stream to n4.
00000918.0000155c::2019/09/05-00:59:08.503 DBG   [CHANNEL 10.10.6.190:~3343~] Close().
00000918.000012f0::2019/09/05-00:59:08.503 INFO  [RGP] node 1: Node Connected 4 00000000000000000000000000000000000000000000000000000000000010010
00000918.000012f0::2019/09/05-00:59:08.503 INFO  [RGP] sending to node(4) 1: 001(1) => 001(1) +() -() [()] , ()
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [PULLER NODE1] Just about to start reading from <refcounted count='3' typeid='.?AVSimpleSecureStream@mscs_security@@'/>
00000918.0000155c::2019/09/05-00:59:08.503 INFO  [RGP] node 1: received new information from 4 starting the timer
00000918.00001528::2019/09/05-00:59:08.798 INFO  [RGP] node 1: Tick
00000918.00001528::2019/09/05-00:59:08.798 INFO  [RGP] node 1: selected partition 10903(3 4) as node 4 has quorum
00000918.00001528::2019/09/05-00:59:08.798 INFO  [RGP] node 1: selected partition 10903(3 4) to join [using info from 4]
00000918.00001528::2019/09/05-00:59:08.798 INFO  [RGP] node 1: cannot join yet. no connection to (3)
00000918.00001528::2019/09/05-00:59:08.798 INFO  [RGP] sending to all nodes 1: 001(1) => 001(1) +() -() [()] , ()
00000918.00001528::2019/09/05-00:59:08.798 DBG   [NODE] Node 1: eating message sent to the dead node 3
00000918.00000dbc::2019/09/05-00:59:08.798 INFO  [RGP] node 1: received new information from 1 starting the timer
00000918.00001528::2019/09/05-00:59:09.111 INFO  [RGP] node 1: Tick
00000918.00001528::2019/09/05-00:59:09.111 INFO  [RGP] node 1: selected partition 10903(3 4) as node 4 has quorum
00000918.00001528::2019/09/05-00:59:09.111 INFO  [RGP] node 1: selected partition 10903(3 4) to join [using info from 4]
00000918.00001528::2019/09/05-00:59:09.111 INFO  [RGP] node 1: cannot join yet. no connection to (3)
00000918.00001528::2019/09/05-00:59:09.111 INFO  [RGP] sending to all nodes 1: 001(1) => 001(1) +() -() [()] , ()
00000918.00001528::2019/09/05-00:59:09.111 DBG   [NODE] Node 1: eating message sent to the dead node 3
00000918.00001524::2019/09/05-00:59:10.507 DBG   [NETFTAPI] received NsiParameterNotification for 169.254.93.143 (IpDadStateInvalid)
00000918.000015a4::2019/09/05-00:59:10.507 DBG   [NETFTAPI] received NsiDeleteInstance for 169.254.93.143
00000918.000015a4::2019/09/05-00:59:10.507 WARN  [NETFTAPI] Failed to query parameters for 169.254.93.143 (status 0x80070490)
00000918.000015a4::2019/09/05-00:59:10.507 DBG   [NETFTAPI] Signaled NetftLocalAdd event for 169.254.93.143
00000918.000015a4::2019/09/05-00:59:10.507 DBG   [NETFTEVM] FTI NetFT event handler ignoring PnP add event for IPv4 LinkLocal address 169.254.93.143:~0~
00000918.000015a4::2019/09/05-00:59:10.507 DBG   [NETFTEVM] TM NetFT event handler ignoring PnP add event for IPv4 LinkLocal address 169.254.93.143:~0~
00000918.000015a4::2019/09/05-00:59:10.507 DBG   [WM] Filtering event NETFT_LOCAL_ADD? 1
00000918.000015a4::2019/09/05-00:59:10.509 WARN  [NETFTAPI] Failed to query parameters for 169.254.93.143 (status 0x80070490)
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTAPI] Signaled NetftLocalRemove event for 169.254.93.143
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] FTI NetFT event handler ignoring PnP remove event for IPv4 LinkLocal address 169.254.93.143:~0~
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] TM NetFT event handler ignoring PnP remove event for IPv4 LinkLocal address 169.254.93.143:~0~
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [WM] Filtering event NETFT_LOCAL_REMOVE? 1
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTAPI] received NsiParameterNotification for 169.254.1.68 (IpDadStatePreferred)
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTAPI] Signaled NetftLocalAdd event for 169.254.1.68
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] FTI NetFT event handler ignoring PnP add event for IPv4 LinkLocal address 169.254.1.68:~0~
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] TM NetFT event handler ignoring PnP add event for IPv4 LinkLocal address 169.254.1.68:~0~
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [WM] Filtering event NETFT_LOCAL_ADD? 1
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTAPI] Signaled NetftLocalConnect event for 169.254.1.68
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] FTI NetFT event handler got event: Local endpoint 169.254.1.68:~0~ connected
00000918.00001230::2019/09/05-00:59:10.509 DBG   [NETFTEVM] FTI NetFT event dispatcher pushing event: Local endpoint 169.254.1.68:~0~ connected
00000918.00001230::2019/09/05-00:59:10.509 DBG   [FTI][Initiator] Got Netft event Local endpoint 169.254.1.68:~0~ connected
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [NETFTEVM] TM NetFT event handler got event: Local endpoint 169.254.1.68:~0~ connected
00000918.0000096c::2019/09/05-00:59:10.509 DBG   [NETFTEVM] TM NetFT event dispatcher pushing event: Local endpoint 169.254.1.68:~0~ connected
00000918.0000096c::2019/09/05-00:59:10.509 INFO  [IM] got event: Local endpoint 169.254.1.68:~0~ connected
00000918.000015a4::2019/09/05-00:59:10.509 DBG   [WM] Filtering event NETFT_LOCAL_CONNECT? 1
00000918.000015a4::2019/09/05-00:59:10.510 DBG   [NETFTAPI] received NsiAddInstance for fe80::5efe:169.254.1.68
00000918.000015a4::2019/09/05-00:59:10.510 DBG   [NETFTAPI] received NsiParameterNotification for fe80::5efe:169.254.1.68 (IpDadStateDeprecated)
00000918.0000152c::2019/09/05-00:59:17.174 DBG   [CORE] WriteVersionFunctor: beginning write attempts
00000918.00001530::2019/09/05-00:59:37.222 DBG   [NETFT] FTI NetFT event handler deregistration successful.
00000918.00001530::2019/09/05-00:59:37.222 INFO  [NODE] Node 1: New join with n3: stage: 'Wait for Heartbeats on Initial NetFT Route' status (1460) reason: '[FTI][Initiator] Aborting connection because NetFT route to node NODE2 on virtual IP fe80::35c4:f902:cbd4:33ef:~3343~ has failed to come up.'
00000918.00001530::2019/09/05-00:59:37.276 INFO  [CORE] Node 1: Clearing cookie e7920b13-f4cf-46bb-84ba-79562d7745d8
00000918.00001530::2019/09/05-00:59:37.276 INFO  [CORE] Node 1: Cookie Cache 465e1aa8-175f-4879-a473-0ad991998962 [NODE1]
00000918.00001530::2019/09/05-00:59:37.276 DBG   [CHANNEL 10.10.6.191:~3343~] Close().
00000918.00001530::2019/09/05-00:59:37.329 WARN  cxl::ConnectWorker::operator (): (1460)' because of '[FTI][Initiator] Aborting connection because NetFT route to node NODE2 on virtual IP fe80::35c4:f902:cbd4:33ef:~3343~ has failed to come up.'

00000918.00001530::2019/09/05-01:00:07.531 DBG   [JPM] Node 1: contacts size for node NODE2 is 1, current index 0
00000918.00001530::2019/09/05-01:00:07.531 DBG   [JPM] Node 1: Trying to connect to node NODE2 (IP: 10.10.6.191:~0~)
00000918.00001530::2019/09/05-01:00:07.531 DBG   [HM] Trying to connect to NODE2 at 10.10.6.191:~3343~
00000918.00001524::2019/09/05-01:00:07.547 INFO  [CONNECT] 10.10.6.191:~3343~: Established connection to remote endpoint 10.10.6.191:~3343~.
00000918.00001524::2019/09/05-01:00:07.547 INFO  [SV] New real route: local (10.13.6.200:~49794~) to remote NODE2 (10.10.6.191:~3343~).
00000918.00001524::2019/09/05-01:00:07.547 INFO  [SV] Got a new outgoing stream to NODE2 at 10.10.6.191:~3343~
00000918.00001524::2019/09/05-01:00:07.547 DBG   [SM] Joiner: Initialized with SPN = NODE2, RequiredCtxAttrib = 0, HandShakeTimeout = 40000
00000918.0000154c::2019/09/05-01:00:07.547 DBG   [SM] Handling auth handshake posted by thread id 5412
00000918.0000154c::2019/09/05-01:00:07.547 DBG   [SM] Joiner: Versions: 1-10
00000918.0000154c::2019/09/05-01:00:07.547 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1723, service principal name HOST/NODE2, auth type MSG_AUTH_PACKAGE::KerberosAuth, attr: 83998
00000918.0000154c::2019/09/05-01:00:07.547 DBG   [SM] Joiner: Sending SSPI blob of size 1723 to Sponsor
00000918.0000154c::2019/09/05-01:00:07.563 DBG   [SM] Joiner: Switching to Schannel
00000918.00001524::2019/09/05-01:00:07.578 DBG   [Schannel] Client: Chosen Cert's version = 2, serialNo = <vector len='16'>00000918.00001524::2019/09/05-01:00:07.735 INFO  [SV] Authentication and authorization were successful
00000918.00001524::2019/09/05-01:00:07.735 INFO  [VER] Got new TCP connection. Exchanging version data.
00000918.00001524::2019/09/05-01:00:07.735 DBG   [VER] Calculated cluster versions: highest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008], lowest [Major 8 Minor 9600 Upgrade 3 ClusterVersion 0x00080003] with exclude node list: (3)
00000918.00001524::2019/09/05-01:00:07.735 INFO  [VER] Checking version compatibility for node NODE2 id 3 with following versions: highest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008], lowest [Major 8 Minor 9600 Upgrade 3 ClusterVersion 0x00080003].
00000918.00001524::2019/09/05-01:00:07.735 INFO  [VER] Version check passed: node and cluster highest supported versions match. Other node still supports lower level, so joining in downlevel mode.
00000918.00001524::2019/09/05-01:00:07.735 INFO  mscs::VersionManagerAgent::IsCompatible: First run: setting CFL to 8.3 manually instead of looking for value in database
00000918.00001524::2019/09/05-01:00:07.735 DBG   [CORE-Dbg] IsCompatible: setting operating version to 8.3 on first run
00000918.00001524::2019/09/05-01:00:07.750 INFO  [SV] Negotiating message security level.
00000918.00001524::2019/09/05-01:00:07.750 INFO  [SV] Already protecting connection with message security level 'Sign'.
00000918.00001524::2019/09/05-01:00:07.750 INFO  [FTI] Got new raw TCP/IP connection.
00000918.00001524::2019/09/05-01:00:07.765 INFO  [FTI][Initiator] This node (1) is initiator
00000918.00001524::2019/09/05-01:00:07.765 DBG   [FTI][Initiator] Cookie for remote node is e7920b13-f4cf-46bb-84ba-79562d7745d8
00000918.00001524::2019/09/05-01:00:07.765 DBG   [FTI] Stream already exists to node 3: false
00000918.00001524::2019/09/05-01:00:07.783 INFO  [FTI][Initiator] Trying to select best endpoints among 169.254.1.68:~3343~, fe80::14:a91:8f79:5d8f:~3343~ (first pair) and 169.254.3.177:~3343~, fe80::35c4:f902:cbd4:33ef:~3343~ (second pair)
00000918.00001524::2019/09/05-01:00:07.785 INFO  [HM] Marking route from realLocal 10.13.6.200:~49794~ -> realRemote 10.10.6.191:~3343~ as a cross-subnet route
00000918.00001524::2019/09/05-01:00:07.785 INFO  [RouteDb] Route virtual fe80::14:a91:8f79:5d8f:~0~ to virtual fe80::35c4:f902:cbd4:33ef:~0~ added
00000918.00001524::2019/09/05-01:00:07.785 DBG   [NETFT] Removing route <struct mscs::FaultTolerantRoute>
00000918.00001524::2019/09/05-01:00:07.785 DBG     <realLocal>10.13.6.200:~3343~</realLocal>
00000918.00001524::2019/09/05-01:00:07.785 DBG     <realRemote>10.10.6.191:~3343~</realRemote>
00000918.00001524::2019/09/05-01:00:07.785 DBG     <virtualLocal>fe80::14:a91:8f79:5d8f:~0~</virtualLocal>
00000918.00001524::2019/09/05-01:00:07.785 DBG     <virtualRemote>fe80::35c4:f902:cbd4:33ef:~0~</virtualRemote>
00000918.00001524::2019/09/05-01:00:07.785 DBG     <Delay>1000</Delay>

Charles Peter

We have a Failover cluster of 3 nodes each node having 2 x 1Gbps NICs which are teamed and used for management and VM traffic on the front (the team is also a trunk carrying traffic for multiple vlans). Team is a switch dependant LACP setup and works fine. 

The backend storage is storage space direct and the NICs were not setup by us. I am struggling to understand how they have been setup and how they are meant to work.  The setup is - 

2 x 10Gbps NICs per node but not teamed as far as I can tell

There are 2 storage vlans and each NIC is a trunk allowing both vlans.  

Each vlan is associated with a different IP subnet and NIC1 has an IP from one of the subnets with NIC2 having an IP from the other subnet. 

So basically  - 

NIC1 - allows vlans 10 and 11 with an IP of 192.168.3.1/27  from vlan 10

NIC2 - allows vlans 10 and 11 with an IP of 192.168.4.1/27  from vlan 11

Does this sound right to anybody because coming from a network background if it is trunk I would expect a vswitch somewhere ie. as in the front end.  And I just don't understand how this is meant to work as we have been told both storage NICs are active on each node. 

Any insights would be very much appreciated. 

SV

running a 4 node nested vm hyper-converged failover cluster.  On one of my nodes, i can not acceess the shared cluster resources.  

Logon failure: the user has not been granted the requested logon type at this computer

i have 2 volumes created w/ s2d across these four nodes, i get this error every time i try accessing them via navigating file explorer to c:\clusterstorage\volum.....

IT guy

Hi Experts,

Can I have multiple SQL Cluster configured on a single environment (Windows Cluster?

For example - I have a 5 Node Windows 2012 R2 Windows Failover Cluster on which I want to configure 2 nodes to run as SQL 2008 Cluster, 4 nodes as SQL 2012 Cluster & 2 Nodes with 2016 Cluster. 

The combination of nodes can be in any number (2 - SQL 2012, 4 -  SQL 2008 or 5 - SQL 2016) but underlying I have only 5 nodes that will form the cluster. So, a single CNO (of 5 nodes) under which there will be multiple SQL Clusters (of 2, 3, 4 or 5 Nodes).

Is that possible? Above all, is that a recommended & supported scenario?

Thanks!

We have 3 Dell servers we are trying to put into a cluster, and a 4th machine will be added later (VM). My issue now is I do not know how to set up the storage on the machines PRIOR to creating the Cluster so that the disks will be recognized as usable by the cluster. Currently when I use Cluster Manager and hit storage>right click disks>add disk, I get an error saying "No disks suitable for cluster disks were found. For diagnostic info about disks available to the cluster, use the Validate a Configuration Wizard to run Storage Tests." 

So I checked the validation test and this is what I see (copy and pasted from validation test):

No disks were found on which to perform cluster validation tests. To correct this, review the following possible causes:
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
* The disks are unsuitable for clustering. Boot volumes, system volumes, disks used for paging or dump files, etc., are examples of disks unsuitable for clustering.
* Review the "List Disks" test. Ensure that the disks you want to test are unmasked, that is, your masking or zoning does not prevent access to the disks. If the disks seem to be unmasked or zoned correctly but could not be tested, try restarting the servers before running the validation tests again.
* The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication between nodes. If your solution is based on replication between nodes, you do not need to rerun Storage tests. Instead, work with the provider of your replication solution to ensure that replicated copies of the cluster configuration database can be maintained across the nodes.
* The disks are Online in the cluster and are in maintenance mode.
No disks were found on which to perform cluster validation tests.

Hi All,

I am trying to move a node from one node to another using Move-ClusterGroup, it moves cluster group from active node to passive node but after few seconds it is coming back to the previous node.

$cg=(Get-ClusterGRoup).Name|Select-First1

Move-ClusterGroup "$cg" -Node $onode

Are there any reasons for this behavior? and how it can be fixed.

Thanks in advance

Roger

I'm working on my first Hyper-V cluster on Server 2016. Going through the validation, I have a warning about cluster log size less than 1536.  So I search how to increase that and find: https://docs.microsoft.com/en-us/powershell/module/failoverclusters/set-clusterlog?view=win10-ps

However, when running powershell on the hosts, either as admin or not, and running:

Set-ClusterLog -Size 2048

All I get is:

Any ideas why am I unable to set this?

Thank you.

Hi, I have a two node, Hyper-V Cluster with about a dozen VMs. As time went by migrating between nodes have slowed. Specifically a SQL Server with about 300 GB disk takes about four minutes to move from one node two the other, and during the process I see it's status as "shutting down" making it offline for a noticeable while.

The servers are Dell PowerEdge 530s with a Compellent (Dell) SC2020 with low latency. I recently connect to 10 GB NIS together peer to peer as a cluster only network in hopes to reduce migration time. It did not seem to make any difference.

Anyone have ideas on why the migration is slow and how to speed it up?

Thanks,

Ken

Ken

Hi,

I have four node S2D cluster with 2019 OS. This is lab environment with SSD+HDD disks and 10Gbps network. Cluster is working fine, I have great performances but there is one issue that bothers me.

Every time I patch nodes, and I restart one of the nodes I have to wait for Storage Jobs to finish (so that data is synced). I know that I have to wait this out and I monitor this with get-storagejob command. When jobs finish, I continue updating other server nodes. What bothers me is time I have to wait for these jobs to finish. They can take more than 60-80min. 

Is there any way to speed this process up? I see that network and disks are not utilized fully when storage jobs are being done. I found online that this is intentionally throttled by Microsoft not to mess with VM performances. However, since this is Lab environment, I would love to speed this process up if possible, because in this way, patching takes to much time...

BR,

Soko