Wednesday, November 2, 2011

SQL Server Cluster Network Binding Order

When setting up a SQL Server cluster the Setup Support Rules report a Warning for the Network binding order. Specifically:

Rule Check Result
Rule "Network binding order" generated a warning.
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order.

However, the binding order is correct. MS KB article 955963 mentions this issue:
You receive a warning about the network binding order on the Setup Support Rules page when you install SQL Server 2008 in a failover cluster
http://support.microsoft.com/kb/955963

In this particular instance I do have a disabled network adapter, an IBM USB Remote NDIS Network Device but no ghosted network adapter. I enabled the IBM adapter, but still got the same error message.

Details.txt showed the following:
2011-10-11 18:14:43 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet
2011-10-11 18:14:43 Slp: NetworkBindingFacet: Looking up network binding order.
2011-10-11 18:14:43 Slp: NetworkBindingFacet: Network: 'Local Area Connection* 9' Device: '\Device\{BD878763-E1BB-45D6-BFBC-E23DF023E411}' Domain: '' Adapter Id: '{BD878763-E1BB-45D6-BFBC-E23DF023E411}'
2011-10-11 18:14:43 Slp: NetworkBindingFacet: Network: 'Heartbeat' Device: '\Device\{CD08E636-4E30-4AFB-A3B7-513DE2F7EBC9}' Domain: '' Adapter Id: '{CD08E636-4E30-4AFB-A3B7-513DE2F7EBC9}'2011-10-11 18:14:43 Slp: NetworkBindingFacet: Network: 'Production' Device: '\Device\{2BA45633-51E0-4D89-83A1-74DF64B0E9C0}' Domain: 'notpublishingithere.local' Adapter Id: '{2BA45633-51E0-4D89-83A1-74DF64B0E9C0}'
2011-10-11 18:14:43 Slp: NetworkBindingFacet: Network: '(IBM)' Device: '\Device\{4AED0A34-EF02-4AFD-B410-4381462C0C9B}' Domain: '' Adapter Id: '{4AED0A34-EF02-4AFD-B410-4381462C0C9B}'
2011-10-11 18:14:43 Slp: IsDomainInCorrectBindOrder: The top network interface 'Local Area Connection* 9' is bound to domain '' and the current domain is 'notpublishingithere.LOCAL'.
2011-10-11 18:14:43 Slp: Evaluating rule : IsDomainNetworkTopOfBindings
2011-10-11 18:14:43 Slp: Rule running on machine: xxxWSVR004
2011-10-11 18:14:43 Slp: Rule evaluation done : Warning
2011-10-11 18:14:43 Slp: Rule evaluation message: The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order.

There are only three NICs in the cluster node (Production, Heartbeat and IBM) but details.txt is showing an extra one: "Local Area Connection* 9".

NICs were renamed on the nodes, so perhaps this is some sort of a hangover. I'll revisit it in the future when I have some more time to reproduce the problem in the lab.

B

No comments: