TechOnTip Weblog

Run book for Technocrats

SQL Failover Cluster Network Binding Error

Posted by Brajesh Panda on April 21, 2010

1. Remove Ghost Adapters: Mostly happen in virtual machines or where you uninstall & re-install network cards. In this process, you left some Hidden Adapters or GUID in registry. You have to remove them. If it didn’t apply to your environment or didn’t work for you follow second step.

2. Verify Network Binding of “Domain” Adapters using registry. It may be different than the GUI Open in Network Settings Control Panel.

a. Binding are stored inside the registry

Key Name: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipLinkage

Name: Bind

Type: REG_MULTI_SZ

Data: Device{C7F03A93-3C6E-46F7-B4A8-492C4AF0BD41}

Device{181E62B9-C204-4237-9D9D-6DC16A6CEAE2}

Device{3E9D1781-1418-45A6-B88F-10979F777C15}

Device{3120A369-0C9B-425E-9C84-FE0A54FB3D7B}

Device{78024161-6DA7-4404-9CCA-6687AEC8A73F}

b. Find out to which adapter these GUIDs are referring to “wmic nicconfig get description, SettingID > C:nicconfig.txt

Description SettingID

WAN Miniport (SSTP) {54AB7E97-2074-413D-A578-2119CD23ECB6}

WAN Miniport (L2TP) {C0B9FD38-A0E8-47CA-BF02-5B6D2B663BF7}

WAN Miniport (PPTP) {1D230E0E-4E65-42C2-9859-9B80E1A4E0C5}

WAN Miniport (PPPOE) {E7F554D4-E231-4291-B40E-2031D3F1E55E}

WAN Miniport (IPv6) {A91F2521-CF79-4F98-9E02-6A516B9D496C}

WAN Miniport (Network Monitor) {2131BB57-8C69-4EAE-B5E3-24E4035AB71D}

Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) {181E62B9-C204-4237-9D9D-6DC16A6CEAE2}

Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) {78024161-6DA7-4404-9CCA-6687AEC8A73F}

WAN Miniport (IP) {7F583D1B-4203-4AD0-A6A0-4BD007D21735}

RAS Async Adapter {7C264673-3322-4312-AE60-D09B4E71E368}

Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #3 {3E9D1781-1418-45A6-B88F-10979F777C15}

Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) {3120A369-0C9B-425E-9C84-FE0A54FB3D7B}

Microsoft Failover Cluster Virtual Adapter {C7F03A93-3C6E-46F7-B4A8-492C4AF0BD41}

c. Decision:

i. From Step A & Step B we can see Microsoft Failover Cluster Virtual Adapter with GUID {C7F03A93-3C6E-46F7-B4A8-492C4AF0BD41} is listed on top of the binding order.

ii. As per SQL cluster installation wizard top adapter in the binding sequence must be a DOMAIN adapter & must be able to communicate to production AD Domain.

iii. Generally this value get populated if you have your network card properties is having a DNS suffix value. However in case of Microsoft Failover Cluster Virtual Adapter, this value will not be there because it is a virtual adapter created by failover cluster manager software.

d. To find out a NIC having a DOMAIN attribute value we can verify in the following registry section

i. HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParametersInterfaces; It will list down all interface GUIDs & their related attributes & values

ii. You may able to identify your production/public network card (with correct IP address). It’s DOMAIN attribute may have a value or may not be. If there is no value, you can add your DOMAIN SUFFIX in network card properties in GUI or you can edit in registry.

iii. After you get this domain value populated for the public adapter, which is connected to your domain; You will be moving the GUID to the 1st place in the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipLinkageBind registry key.

iv. You have to do it for both the nodes.

v. Run Installation After this.

Advertisements

One Response to “SQL Failover Cluster Network Binding Error”

  1. […] Windows Event IDs « Powershell: Transfer Output to Txt, CSV, HTML & Variable SQL Failover Cluster Network Binding Error […]

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: