Order of steps to change IP segment address and it's resources - Windows 2008 R2

Question

I have a 2 node cluster in windows 2008 R2 AD on an HP Proliant DL380 G6 server with an attached MSA2012sa DAS storage where the resources recite.  Resources are mainly data, no apps.
I need to change the IP segment/address of the cluster & storage to a new DS3 circuit.  I've tried to follow some of the discussion threads on this topic, but i'm confused.
Please advice the order I should do things:
1.  in cluster manager, take resources offline, then change the cluster IP and the resources IP
    --is it possible to change ips when it's offline?
    --or should I shut down the cluster?  is it possible to change when cluster is shut down?
    --where does the ip of cluster itself get changed?  I rt clicked on the cluster object and there is no option to change it
       (in AD or in cluster manager).
2.  in network properties of each physical node, change the public IP address
     --Should I change one at a time, reboot, then do the other?
     --Should changing node ip be done before changing cluster & resources ip?
     --anything needs to be done to the quorum disk?
Advice will be very much appreciated.  I've read thru a bunch of threads on changing ip but I need to brake it down in order.  Thank you.
-Cocoflor
HR

Answer 1

Well, I gave it a try.  Only this was on a 2012 R2 cluster, so I cannot vouch for 2008 R2.  (But I have extreme faith in the cluster engineers that it most likely works the same there.  Again, prove it in a lab.)
Here is what I did.  I had a cluster with a single network and everything was configured on that network - let's call it old-NIC.  I added another network by adding a new NIC to each node - let-s call it new-NIC.  I configured that new-NIC
on a different subnet.
OLD CONFIGURATION:  Cluster IP - 192.168.1.30;  Cluster Access Point for clustered service 192.168.1.33;  Node1 IP - 192.168.1.31;  Node2 IP - 192.168.1.32
NEW, DESIRED CONFIGURATION: Cluster IP - 192.168.2.30;  Cluster Access Point for clustered service 192.168.2.33;  Node1 IP - 192.168.2.31;  Node2 IP - 192.168.2.32
The old-NIC on node1 was configured with gateway and DNS registration.  I removed the gateway and DNS registration from this NIC.
I configured new-NIC on node1 with gateway and DNS.  I then issued an ipconfig /registerdns to get the new name for the node into DNS.
Repeat above steps for node2.
I went into Cluster Manager and configured both old-NIC and new-NIC to be available for both Cluster and Client access.
I selected the properties of the CAP for the service and changed the IP address to new-NIC cluster IP.  When accepted, I executed another ipconfig /registerdns.
I then selected the cluster core resource IP and did the same thing - changed the IP to the new-NIC address.  When accepted, I executed another ipconfig /registerdns.
Obviously during the change in the IP addresses on the cluster, services became unavailable while the services were stopped/started to reconfigure with the addresses.  Once the change was made and the services back up and running, the services were
available via the new-NIC IP addresses.
There should be NO connections to the cluster during this change.  After updating the IP addresses on the cluster, you might have to issue an ipconfig /flushdns from the clients so they are forced to re-query DNS to be able to find things under the
new IP addresses.
All tests were performed in lab VMs.
. : | : . : | : . tim