SQL Cluster failover cause : Network provider order for BoostFS is reverting after reboot and Solution below

 

This is Faisal Alvi from Microsoft SQL Engine team and I have been told that there is a question about binding order.  SQL has no specific recommendations on network binding order but since traffic to AD domain network is important so if you are getting warning then it is prudent to address it.  As provided by Windows Clustering team already that this warning simply checks that the network adapter configured to access the AD domain network is at the top of the network binding order. If it isn't, performance and availability problems might occurs as the network stack will try to access the AD domain for authentication. Customer needs to check with the vendor why BoosFS is coming at the top after reboot.

+Caution: The network binding rule when installing SQL Server failover clustered instances serves to verify that the network adapter configured to access the Active Directory domain network is at the top of the network binding order. If it isn’t, performance and availability problems might occur as the network stack will try to access the Active Directory domain for authentication. If, for example, the internal/private cluster communication network is at the top of the network binding order, the applications accessing Active Directory can time out because there is no path on the network to go thru Active Directory thru this network adapter.  By default, network binding order is configured in the sequence of how the network adapters were installed and added to the server.

https://docs.microsoft.com/en-us/troubleshoot/sql/install/warning-about-network-binding

Please let me know if there are any further queries.

Comments

Popular posts from this blog

NetSH collection commands

Script for Host entry in remote servers