Changing IP of the cluster

Hello!
We will be moving our two cluster running SQL Server 2005 64-bit SP2 on
Windows 2003 to the different datacenter. IP addressed of both nodes will be
changed by DNS names remain the same. I was wondering if anyone had issues
with this. Out thought is that we just need to update IPs in Cluster Manager.
Comments are welcome.
Igor
Here are the instructions from BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/b685f400-cbfe-4c5d-a070-227a1123dae4.htm
The real key is to only change one network at a time and make sure at least
two networks are enabled for private cluster communication. Always give the
cluster a working private communications path so it can settle cluster-wide
changes.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Igor Marchenko" <IgorMarchenko@.discussions.microsoft.com> wrote in message
news:9F4923C9-03A1-400B-B5A8-6183C47F3827@.microsoft.com...
> Hello!
> We will be moving our two cluster running SQL Server 2005 64-bit SP2 on
> Windows 2003 to the different datacenter. IP addressed of both nodes will
> be
> changed by DNS names remain the same. I was wondering if anyone had issues
> with this. Out thought is that we just need to update IPs in Cluster
> Manager.
> Comments are welcome.
> Igor
>
|||Geoff,
Thanks for your reply! For some reason, I am unable to open this link in
BOL. I am getting 'This programn cannot diplay the webpage...' error. Could
you please send me url to BOL online?
Thanks,
Igor
"Geoff N. Hiten" wrote:

> Here are the instructions from BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/b685f400-cbfe-4c5d-a070-227a1123dae4.htm
> The real key is to only change one network at a time and make sure at least
> two networks are enabled for private cluster communication. Always give the
> cluster a working private communications path so it can settle cluster-wide
> changes.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
> "Igor Marchenko" <IgorMarchenko@.discussions.microsoft.com> wrote in message
> news:9F4923C9-03A1-400B-B5A8-6183C47F3827@.microsoft.com...
>