This post goes over how to change IPs on an existing Microsoft Failover Cluster. It also happens to go over some Oracle Failsafe stuff.

Identify New IPs you will be using

• You will need four new IPs for the cluster
• Node1
• Node2
• Microsoft Cluster
• Role
• You need your new subnet mask
• You need your new Gateway IP
• You need your new DNS server IPs
• You may need two additional IPs for the Heartbeat network depending on if you are required to change those.

Confirm Routing to New IPs is in place

You need to keep a connection to the cluster the entire time. You cannot change everything at once. The cluster must remain intact during the IP changes. Your new IPs will need to be able to reach all the existing infrastructure while you make the following changes. Cnfirm your new IPs can still access your Domain Controller, DNS Servers and existing Node and Cluster IPs.

Stop Services Using Microsoft Failover software

1. Open up Failover Cluster manager (Administrative Tools > Failover Cluster Manager)
2. Expand Cluster Name
3. Highlight Roles
4. Select the Role
5. Click on resources at the bottom of the center Pane
6. For Diva Service in the role: Right Click, and select Take offline

Disable Failover for Services

On each service in the role double click and disable failover policies.

1. In your role there are a list of services, double click service
2. Go to policies Tab
3. Select the Do Not restart on Failure option. This will prevent frustration when testing
4. Disable for every service, not just the Diva ones.

Take Database backup

Change Node1 IP

1. Log into Node2
2. Open Failover Cluster Manager
3. Check current owner of the Role
4. Move Role to Node2 using Failover Cluster Manager if not owned by Node2
5. Log into Node1
6. Change IP on Node1 using normal Windows Network Adapter Settings
7. Confirm New IP with ipconfig
8. Confirm You can still ping Node2 and DNS Servers and Domain controller
9. Reboot Node1
10. Update DNS server

Change Node2 IP

1. Log into Node1
2. Open Failover Cluster manager
3. Move Role to Node1
4. Log into Node2
5. Change IP on Node2 Using Normal Windows Network Adapter Settings
6. Confirm new IP with ipconfig
7. Confirm you can still ping Node1 and DNS Servers and Domain controller
8. Reboot Node2
9. Update DNS server

Change Cluster IPs

Change Microsoft Cluster IP

1. From Node1 confirm both Nodes are joined to the cluster

1. Click on the Microsoft Cluster Name in the left frame
2. Expand Cluster Core Resources in the middle frame
3. Expand the Domain Name of the Microsoft Cluster (it will be failed or offline)
4. Double Click the IP
5. Go to the General tab
6. Pick the correct Network Interface (The new one)
7. Change the Address of the Microsoft cluster
8. You probably want to change the Name (at the top of the General tab)
9. Hit Apply
10. Hit OK.
11. Update DNS server
12. Bring it online
13. The IP and the DNS name should both come online

Change Role IP

1. Highlight Roles in the left frame
2. Highlight your Role in the center frame
3. Expand resources Tab at the bottom
4. Expand Role DNS name
5. Double click IP
6. Go to the General tab
7. Pick the correct Network Interface (the new one)
8. Set the correct IP (the new one)
9. Change the name if desired
10. Hit Apply
11. Hit Ok
12. Update DNS Server
13. Bring the IP online
14. The DNS name should come online as well

Adjust Oracle Listener Files (only needed if running Oracle Failsafe)

THIS NEEDS TO BE DONE ON BOTH NODES

1. In Windows Explorer Navigate to %Oracle_Home%\NETWORK\ADMIN
2. Adjust LISTENER.ORA, set this to the new ROLE IP

1. Adjust TNSNAMES.ORA, set this to new ROLE IP
2. Start listener in Failover Cluster manager

Failsafe Validation (only needed if running Oracle Failsafe)

1. On either node go to Failover Cluster Manager
2. Start LIB5 Service(this might take few minutes to start)
3. Open Oracle Failsafe Manager
4. Connect to the Cluster
5. Expand the cluster name
6. Right click the Role name and select Validate

1. You may get a pop up like this if you missed something. Click yes if it is asking to fix something for you.

1. The Operation should complete and may have warnings
2. You can close Oracle Failsafe

Microsoft Cluster Validation

1. On either node go to Microsoft Failover Cluster manager
2. Right click the Microsoft Cluster name in left frame and select validate cluster

1. Click next through the wizard and accept defaults (all tests)
2. It will run through a bunch of tests and give you a report at the end. As long as it says it is suitable for clustering, you are good.

1. Look over the report and fix anything you can

1. Look over all the Warnings, you can click through the report as a webpage and read all the warnings. You may not be able to fix all of them.

Test Core Resources failover

1. Highlight Microsoft cluster name in left frame
2. Identify the current owner in the center frame
3. Right Click Microsoft Cluster name, select more actions, select move cluster, select node
4. Pick the other node from the list and hit ok

1. This will move the Core resources of the Cluster (Quorum Drive, Microsoft cluster IP)
2. Test more restores

Test Role Failover

1. Highlight roles in the left frame
2. Identify the current owner of the role in the center fame
3. Right click the DIVA role name in the center frame and select Move>Select Node
4. Pick the other node from the list and hit ok
5. This will move the Diva role over to the other node
6. Test more restores

Other References

MS cluster – https://support.microsoft.com/en-us/help/230356/changing-the-ip-address-of-network-adapters-in-cluster-server

Failsafe – https://docs.oracle.com/cd/E16161_01/doc.342/e14973/sp3.htm#OFSCN320