SQLServerWiki

“The Only Thing That Is Constant Is Change”

You get a warning during SQL Server 2008 cluster installation for Network Binding Order.

Posted by database-wiki on March 6, 2011

Issue:

You get a warning during SQL Server 2008 cluster installation:

2009-06-01 18:06:02 Slp: Initializing rule      : Network binding order

2009-06-01 18:06:02 Slp: Rule applied features  : ALL

2009-06-01 18:06:02 Slp: Rule is will be executed  : True

2009-06-01 18:06:02 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet

2009-06-01 18:06:02 Slp:   NetworkBindingFacet: Looking up network binding order.

2009-06-01 18:06:02 Slp:   NetworkBindingFacet:   Network: ‘Local Area Connection* 11’ Device: ‘\Device\{CEBDA08A-515C- 4FBA-83B7-2823C78C4F68}’ Domain: ” Adapter Id: ‘{CEBDA08A-515C-4FBA-83B7-2823C78C4F68}’

2009-06-01 18:06:02 Slp:   NetworkBindingFacet:   Network: ‘Private’ Device: ‘\Device\{9A709D31-67FD-4475-A124- B3F156CB1682}’ Domain: ” Adapter Id: ‘{9A709D31-67FD-4475-A124-B3F156CB1682}’

2009-06-01 18:06:02 Slp:   NetworkBindingFacet:   Network: ‘Public’ Device: ‘\Device\{5C4712DD-E684-482F-B5F6- 29A4A250DA1E}’ Domain: ‘Perform.jupiter.domain’ Adapter Id: ‘{5C4712DD-E684-482F-B5F6-29A4A250DA1E}’

2009-06-01 18:06:02 Slp: IsDomainInCorrectBindOrder: The top network interface ‘Local Area Connection* 11’ is bound to domain ” and the current domain is ‘PERFORM.JUPITER.DOMAIN’.

2009-06-01 18:06:02 Slp: Evaluating rule        : IsDomainNetworkTopOfBindings

2009-06-01 18:06:02 Slp: Rule running on machine: SANSYS4

2009-06-01 18:06:02 Slp: Rule evaluation done   : Warning

2009-06-01 18:06:02 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.

2009-06-01 18:06:02 Slp: Send result to channel : RulesEngineNotificationChannel

I have already done a quick repro at my end for this issue:

By default on windows 2008 server clustered environment, Microsoft Failover Cluster Virtual Adapter is on the top of the binding.

Also it is not visible in GUI:

Only way to fix it is to manipulate the registry by going to: hklm\system\currentcontrolset\services\tcpip\parameter\interfaces\ and noting down the GUID of Microsoft Failover Cluster Virtual Adapter.

And reshuffle the binding in hklm\system\currentcontrolset\services\tcpip\linkage\binds

Looking at my Detail.txt

Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet

2009-05-29 00:41:24 Slp:   NetworkBindingFacet: Looking up network binding order.

2009-05-29 00:41:24 Slp:   NetworkBindingFacet:   Network: ‘Local Area Connection* 9’ Device: ‘\Device\{00B2838D-9026-45F5-B121-4C124B5CB92A}’ Domain: ” Adapter Id: ‘{00B2838D-9026-45F5-B121-4C124B5CB92A}’

2009-05-29 00:41:24 Slp:   NetworkBindingFacet:   Network: ‘iSCSI’ Device: ‘\Device\{7E49486F-390D-4394-9592-F192285EBBA1}’ Domain: ” Adapter Id: ‘{7E49486F-390D-4394-9592-F192285EBBA1}’

2009-05-29 00:41:24 Slp:   NetworkBindingFacet:   Network: ‘Corpnet’ Device: ‘\Device\{3C26E0BC-9E18-4061-B70A-7A55C4A8E0C7}’ Domain: ‘DOM167286.LOCAL’ Adapter Id: ‘{3C26E0BC-9E18-4061-B70A-7A55C4A8E0C7}’

2009-05-29 00:41:24 Slp:   NetworkBindingFacet:   Network: ‘LAN2’ Device: ‘\Device\{32A82D51-B65F-4A2C-B65D-56476A5B7923}’ Domain: ” Adapter Id: ‘{32A82D51-B65F-4A2C-B65D-56476A5B7923}’

2009-05-29 00:41:24 Slp:   NetworkBindingFacet:   Network: ‘Local Area Connection’ Device: ‘\Device\{13291679-7A52-4394-8210-77AF7C5C45EE}’ Domain: ” Adapter Id: ‘{13291679-7A52-4394-8210-77AF7C5C45EE}’

2009-05-29 00:41:24 Slp: IsDomainInCorrectBindOrder: The top network interface ‘Local Area Connection* 9’ is bound to domain ” and the current domain is ‘DOM167286.LOCAL’.

2009-05-29 00:41:24 Slp: Evaluating rule        : IsDomainNetworkTopOfBindings

2009-05-29 00:41:24 Slp: Rule running on machine: BLRS2R17-15

2009-05-29 00:41:24 Slp: Rule evaluation done   : Warning

2009-05-29 00:41:24 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.

Now the issue is cause by a Microsoft Failover Cluster Virtual Adapter so KB http://support.microsoft.com/kb/955963 won’t help us. If you wanted to remove the warning you need to manipulate the registry which we don’t support also you can safely ignore this warning.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: