Today in Canada is remembrance Day and a good day to write a long post (http://en.wikipedia.org/wiki/Remembrance_Day#Canada). Last night, I had to do a IP migration of an Exchange Server 2007 CCR cluster installed on a Windows Server 2003 and I thought that writing down my notes about the process could help someone else on the same situation. If you have any questions, please drop me a line on the comment section :)
My scenario was pretty straight forward where I had two servers ServerA and ServerB and their original network information can be summarized using the information below:
- LAN: 192.168.1.15
- HeartBeat Interface: 10.10.10.1/255.255.255.252
- LAN Interface: 192.168.1.16
- Heartbeat interface: 10.10.10.2/255.255.255.252
Before going any further a best practice is to document the IP resource names and here it goes:
TOCluster – 192.168.1.17
REsource Name and IP used by Cluster REsource Group.
TOMailCluster – 192.168.18
Resource Name and IP used by Exchange Server (the CMS).
The second step during the planning is to document and test the new IP address that we are going to use. In my case we are going to a different network 10.20.1.x.
My customer had no issue in bringing down the cluster for a little bit during the maintenance window, so my steps to achieve the migration were:
- Please, use this subliminar message to your environment BACKUP, PLAN, LAB, TEST :)
- Make sure that all resources are on ServerB (it doesn’t matter which server just make sure that all of them are on the same)
- Stop cluster services on ServerA and change the service to Manual mode (using services.msc)
- Logged on ServerB, dismount all databases using Exchange Management Console
- Logged on ServerB, dismount all Cluster resources using Cluster Administrator (cluadmin)
Note: If you are using a MNS Quorum you wouldn’t be able to bring it down. Not a problem, keep reading..
- Double click on IP Resource for the Cluster and change to the new Address
- Double click on IP REsource for the CMS (Exchange Resource Group) and change to the new address
- Close Cluster Administrator
- Modify the Cluster Service to Manual (using services.msc)
- Change the LAN Adatper to the new IP Address
- Restart the machine
- Test the Active Directory site information (nltest dsgetsite, nslookup, file:///C|/%3CDC-Name, \<domain-FQDN>)
- Test the network access in general
- If it’s all good, Start the cluster service and change the service to Automatic
- Open Cluster Administrator and bring up just the Cluster Resource Group and check from your workstation if you can ping the name of tha resource (here in our example is tocluster and its new IP address)
- Awesome! At this point you have one node (ServerB) using the new IP address information and at least one resource
- Logged on ServerA, change the LAN adapter to the new IP Address and restart that server
- Logged on ServerA, test AD, network access like we did on steps 12 and 13
- Start the cluster service and configure it back to Automatic (using services.msc)
- Move the Cluster Resource Group between nodes, is it all good? CAn you access all services in both nodes?
- Great we have new IP address on all nodes, at least one resource is working properly
- Now, it’s time to bring it up Exchange Clustered Mailbox Server on ServerB
So these are the main steps to change the IP network of you current Exchange Server 2007 CCR. A few notes that you need to be aware before, during and after the process:
- I stopped the cluster services to provide you ways to roll back the process any time. If you feel confortable you don’t need to stop them. In my humble opinion is easier to control and avoid any mistake during the process
- When you cluster administrator and you can’t connect, don’t panic, there is always the “.” (period) that allow you to connect locally without specifying any IP address
- If you are changing you network you need to plan CAS, HUB and Domain Controllers. If you can keep both networks routing during the transition it’s better
- After the first restart of one of the nodes, check your eventviewer and please make sure that there is no problem accessing the MNS Quorum, you can always try to file:///C|/MNS-Server to validate the communication.
- Make sure that your AD Sites and Services are configured to the new IP address, that’s why I added the nltest to make sure that you are in the same site that you were after changing the IP information
- There always several ways to accomplish the same task, you may find a better way to do that. Your test phase will show you which approach best fits your company/scenario
- Microsoft KB 241828 and 230356 have information about this process
- Ipconfig /flush is your friend. You may want to do that on your Hub Transport Server to flush the MAPI queues after changing the Cluster nodes IPs.
I hope that it helps!