February 19, 2013 at 12:03 pm
Hello All,
First time poster so if this has been asked, please forgive. I have searched the forums but didn't find what I was looking for.
I have a 2 server node SQL Cluster, running on identical Dell hardware, in the same datacenter, in the same subnet, both running 2008R2 OS and SQL 2008R2. In addition, all network configurations on the NICs are statically entered on the servers and not being pulled via DHCP. We are using (2) NICs per server. One for the network and one for the cluster heartbeat.
When the servers are rebooted and the SQL failover process runs its natural course, we do not lose any network configuration info on the networked NICs. All network info remains on both servers.
If we log into either server and manually do a failover, either by "Move this service or application to another node" or "Simulate failure of this resource", the server that was the ACTIVE node loses its Gateway IP Info as soon as the failover completes. All other network info remains unchanged and intact.
It doesn't matter which server we are on, and which server we are failing over to. The server with the ACTIVE node at the time of the failover loses its Gateway IP info but nothing else.
This does not happen when failovers happen on their own due to server reboots (like patch days).
All hardware and network configurations, with the exception of specific IP Address configs, are all the same.
Any ideas?
Thanks in advance for your time.
Dan
February 20, 2013 at 5:40 am
You mean the TCP/IP-Gateway, or the Cluster IP?
Greetz
Query Shepherd
February 21, 2013 at 9:09 am
The TCP/IP-Gateway on the server's NIC.
Before the Node failover, under TCP/IPv4 properties, as well as ipconfig/all, the server shows:
(These are statically assigned and not pushed out via DHCP.)
Server IP Address
Subnet Mask
Default Gateway
Preferred DNS
Alternate DNS
After the Node failover, under TCP/IPv4 properties, as well as ipconfig/all, the server shows:
Server IP Address
Subnet Mask
No Default Gateway
Preferred DNS
Alternate DNS
This only happens to the server with the ACTIVE node at the time of the failover.
Thanks.
Dan
May 2, 2013 at 1:40 pm
Hi
Did you ever fix this, I have the exact same issue, everything is the same except I am on HP servers.
Thanks
May 10, 2014 at 3:39 am
Hi,
I do facing the same problem but running on vmware . Anyone got solution ?
Regard
Wvoong
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply