![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Gurus, Running SQL Server 2005 SP2 on a cluster (two nodes, SQL instance running on each, active/active design). Our network team recently forced us to re-IP everything because they changed out the routing switches (don't ask). Now, I was gone for a week when my junior Windows admin re-IP'd the cluster nodes themselves but did NOT re-IP any IP address resources within the Cluster interface itself so I came back from my vacation to both SQL instances down. I re-IP'd the Cluster Group quorum resource successfully (note that the Heartbeat network for this cluster was not changed). However, both SQL instances do NOT come up within Cluster Administrator although I can start them (both SQL Server instances) OUTSIDE of Cluster Administrator. The event logs indicate SQL having an issue contacting network resources. So I followed up by changing the IP of these resources in DNS as well but still no dice. So I went into SQL Configuration management and noticed that the IP addresses in there still reflect the old addresses. Manually changing the IPs to the new addresses followed by a restart of each node did not change anything - the old IP addresses were still there, not the new ones. So I guess one takeaway here is that one does not change IP addresses within the SQL Configuration Management snap-in? Anyone seen this problem before? -- Spin |
#3
| |||
| |||
|
|
When you changed the IP Address of the SQL instance(s) did you follow the following steps: http://msdn.microsoft.com/en-us/libr...0(SQL.90).aspx |
#4
| |||
| |||
|
|
Gurus, Running SQL Server 2005 SP2 on a cluster (two nodes, SQL instance running on each, active/active design). Our network team recently forced us to re-IP everything because they changed out the routing switches (don't ask). Now, I was gone for a week when my junior Windows admin re-IP'd the cluster nodes themselves but did NOT re-IP any IP address resources within the Cluster interface itself so I came back from my vacation to both SQL instances down. I re-IP'd the Cluster Group quorum resource successfully (note that the Heartbeat network for this cluster was not changed). However, both SQL instances do NOT come up within Cluster Administrator although I can start them (both SQL Server instances) OUTSIDE of Cluster Administrator. The event logs indicate SQL having an issue contacting network resources. So I followed up by changing the IP of these resources in DNS as well but still no dice. So I went into SQL Configuration management and noticed that the IP addresses in there still reflect the old addresses. Manually changing the IPs to the new addresses followed by a restart of each node did not change anything - the old IP addresses were still there, not the new ones. So I guess one takeaway here is that one does not change IP addresses within the SQL Configuration Management snap-in? Anyone seen this problem before? -- Spin |
#5
| |||
| |||
|
|
Gurus, Running SQL Server 2005 SP2 on a cluster (two nodes, SQL instance running on each, active/active design). Our network team recently forced us to re-IP everything because they changed out the routing switches (don't ask). Now, I was gone for a week when my junior Windows admin re-IP'd the cluster nodes themselves but did NOT re-IP any IP address resources within the Cluster interface itself so I came back from my vacation to both SQL instances down. I re-IP'd the Cluster Group quorum resource successfully (note that the Heartbeat network for this cluster was not changed). However, both SQL instances do NOT come up within Cluster Administrator although I can start them (both SQL Server instances) OUTSIDE of Cluster Administrator. The event logs indicate SQL having an issue contacting network resources. So I followed up by changing the IP of these resources in DNS as well but still no dice. So I went into SQL Configuration management and noticed that the IP addresses in there still reflect the old addresses. Manually changing the IPs to the new addresses followed by a restart of each node did not change anything - the old IP addresses were still there, not the new ones. So I guess one takeaway here is that one does not change IP addresses within the SQL Configuration Management snap-in? Anyone seen this problem before? -- Spin |
![]() |
| Thread Tools | |
| Display Modes | |
| |