Change 2005 failover cluster IP

#31

Names can be tricky. Cl;ustering has to verify the uniqueness of the name
in the namespace which requires response or timeout from a domain
controller.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

"Jeremy" <Jeremy (AT) discussions (DOT) microsoft.com> wrote

Quote:

Thanks for confirming this for me. We made the change and everything
works.
We have noticed one qwirk however. When we fail either the cluster group
or
sql group to either node everything moves really fast except the cluster
name
or sql name, it seems to hang to 1+ minute or so then comes online. This
is
not huge issue at the moment, but I would like to figure it out. We did
not
change the cluster name or the SQL name. I have verified the network
adapter
order is correct and that the internal nic is for internal only and public
nic is for public only in the cluster admin.

"Linchi Shea" wrote:

Sounds reasonable to me. I'd want to have the network folks on standby
while
this is being worked on as sometimes it may take some time for the change
to
work through the network, and you can go crazy in between, although
changing
IP addresses is probably less problematic than changing network names.

Linchi

"Jeremy" wrote:

I have to re-IP our SQL 2005 failover cluster to a new IP and I have
looked
at the following KB articles.

How to change the network IP addresses of SQL Server failover cluster
instances
http://support.microsoft.com/default.aspx/kb/244980

Changing the IP address of network adapters in cluster server
http://support.microsoft.com/kb/230356

Here is the plan that I plan to follow, based on the KB articles and
information from several forums. Can anyone please provide any
suggestions
or see any issues with this plan. Please note that downtime will be
scheduled when I do this so being offline is not a problem.

1) Log into the local console for both nodes. Open cluster admin with
“.”
2) Take SQL Group offline on active node that is holding the Cluster
group
and SQL group.
3) Re-ip “passive” node and reboot node
4) after the “passive” node has rebooted, on “active” (node with SQL
group
offline), go to cluster group, and change the
4a) IP of the cluster ip in the parameters
4b) change the DTC IP the new IP on the new subnet
4c) change the SQL IP to the new IP on the new subnet.
5) Move Cluster Groups to the “passive” node
6) Move SQL group to the “Passive” node .
7) re-ip the former “active node” to the new subnet and IP and reboot.
8) when the node is back online and the cluster admin console on the
“passive”/second node is showing the cluster as healthy, bring the SQL
group
back online.
9) Check the SQL log to see that SQL is listening on the new address
10) fail the groups back to the normal “active”/primary node now

Thanks for any help in advance.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Change 2005 failover cluster IP

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Change 2005 failover cluster IP - 09-18-2008 , 07:55 AM