December 12, 2013 at 11:37 am
Hello,
We have a two-node active/active SQL Server 2008 Std Cluster on Windows 2008 on Production.
After a network maintenance, the network card (not heart-beat) of one node has no gateway ip. We want to fix it without causing a failover.
I assume when we set gateway ip, the network card will be reset, and the ip will be temporarily unavailable, then fail-over happens. Am I right?
Is there a way to play with dependencies not to initiate failover during fixing network card?
Thanks,
Kuzey
December 12, 2013 at 7:35 pm
Kuzey (12/12/2013)
Hello,We have a two-node active/active SQL Server 2008 Std Cluster on Windows 2008 on Production.
After a network maintenance, the network card (not heart-beat) of one node has no gateway ip. We want to fix it without causing a failover.
I assume when we set gateway ip, the network card will be reset, and the ip will be temporarily unavailable, then fail-over happens. Am I right?
Is there a way to play with dependencies not to initiate failover during fixing network card?
Thanks,
Kuzey
Since you are not changing anything on the NIC used for the heartbeat, you should not get a failover. I would expect that the users may get a break because their connections may be severed but the failover wouldn't be initiated because the standby node can still communicate with the active node.
December 12, 2013 at 9:55 pm
Off the top of my head there will probably not be a fail-over. Your users may experience some lost connections.
But as I think about it I don't think the network card will be reset at all, the default gateway is a function of routing which is handled at a windows layer and not the NIC specifically. If affects the routing tables.. So the more I think about it the less I think you will have an issue.
CEWII
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply