Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Failover Cluster SQL 2012 - Is a Second NIC Still needed in separate VLAN

$
0
0

Hi All:

I am trying to get clarification on best practices building out a 2 node SQL Failover Cluster Instance.  I have read it is best to have a secondary NIC in another subnet for redundancy (I have read this is depreciated) however when you validate the cluster in Windows is looks like it wants that.

So I basically add another NIC within VMware, in another subnet/VLAN and just assign it IP and S/N mask.  Below is a sample of how it would be configured.  However now when I run the validate cluster wizard it tells me "connectivity checks using UDP on port 3343" have failed.  This is obviously because I do not have a L3 gateway defined on that NIC I am assuming.  I have also read this is normal (as it is just a warning).  Is it best practice to have a secondary NIC in another subnet and if so can that warning be disregarded.  I guess if that primary NIC failed, and the gateway was gone, would it start to use that secondary NIC?  Just want to make sure my design is sound.

So far
NODE 1
NIC 1
IP = 192.168.100.10
SN = 255.255.255.0
GW = 192.168.100.1

NIC 2
IP = 192.168.200.10
SN = 255.255.255.0
GW = NONE ASSIGNED


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>