March 2, 2012 at 12:29 pm
The second NIC which I often rename to Heartbeat should be setup before you start thinking about adding SQL and you shouldn't need to assign it to anything during the SQL install. At Failover Cluster Management -> [Cluster name] -> Networks, Cluster User should likely be "Internal" on the second NIC and "Enabled" on the first. This is used for the clusters to talk to each other and not to trade other traffic with the users.
I would not leave the second NICs Cluster Use as "Enabled" (which I'm sure it is), the reason is that if it were to get saturated on a node then it is possible for the other node to think "Failure" and start a fail-over.
CEWII
March 2, 2012 at 12:32 pm
In my scenario both the nics are in the same subnet..I think it should still work...but it wont
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
March 2, 2012 at 12:49 pm
I guess I am wondering why you want to do that. It shouldn't matter if they are in the same subnet (I think). But what are you trying to accomplish with that, at first blush it would seem to confuse which is the NIC in use.
So what is your goal in this scenario?
CEWII
March 2, 2012 at 1:01 pm
The clustering worked well without any issues when I was using only 1 nic in all the three servers. I did not configure a seperate private network for the heartbeat but it still worked..Now I added a new nic card to all the servers and want to test the network failover..but to do that I am getting stuck with the ip is in use error
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
March 2, 2012 at 1:21 pm
You CAN make it work with one NIC but it is not recommended and there are risks associated with that course. I'm asking what your intentions are for the second NIC in each machine.
CEWII
March 2, 2012 at 1:22 pm
You CAN make it work with one NIC but it is not recommended and there are risks associated with that course. I'm asking what your intentions are for the second NIC in each machine.
CEWII
I want to use it for network failover
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
March 2, 2012 at 1:50 pm
Sapen (3/2/2012)
You CAN make it work with one NIC but it is not recommended and there are risks associated with that course. I'm asking what your intentions are for the second NIC in each machine.
CEWII
I want to use it for network failover
you want to use it as a backup to the primary NIC? I had thought of that in the past but I have VERY few networking issues due to the fact that networking has very few moving parts.. Can these two NICs be bonded? I think I'd handle this at the OS level rather than the cluster level.
CEWII
March 3, 2012 at 11:40 am
Sapen (3/2/2012)
The clustering worked well without any issues when I was using only 1 nic in all the three servers. I did not configure a seperate private network for the heartbeat but it still worked..
Yes it would, as the cluster network each nodes NIC was connected to would have been configured for all cluster communications (public and internal).
Sapen (3/2/2012)
Now I added a new nic card to all the servers and want to test the network failover..but to do that I am getting stuck with the ip is in use error
Failover of what exactly? If you require redundancy on the public network then consider teaming the 2 NICs. Teamed NICs however are not supported for heartbeat only networks.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 4, 2012 at 12:00 am
Perry and Elliot,
Thanks for your replies. I was trying to team up the nics for public network failover but i could not find this option in the nic properties window. I dont see a tab for teaming.
Control Panel-->Network and Internet-->Network Connections--> I see "Local area Connection" and "Local area connection 2" both enabled
Local Area Connection-->x2-->Properties-->I dont see the teaming tab.
Do I need to tear down the cluster to team up the nics?
Thanks so much guys.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
March 4, 2012 at 2:54 am
NIC teaming is a function provided by the NIC manufacturer via a software interface. What brand\model of NICs do you have installed?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 4, 2012 at 8:51 am
I have 2 of these on Server 1:
Broadcom netxtreme gigabit ethernet
Server 2:
Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Server 3:
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
March 4, 2012 at 10:38 am
not sure about the Realtek chips but the Broadcom NICs could almost definitely take advantage of the Broadcom network control suite. Check the driver downloads for your server models and see if there are any network control suites available
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 12 posts - 46 through 56 (of 56 total)
You must be logged in to reply to this topic. Login to reply