Changing IP Addresses of AlwaysOn Group

Question

Changing IP Addresses of AlwaysOn Group

michaelh-731356

Old Hand

Points: 319
More actions
May 23, 2017 at 11:50 am

#323718

We have 2 nodes in an AlwaysOn group. SQL2014 Enterprise.
We need to change the IP addresses of the nodes, the cluster, and the listener.
They will still remain in the same domain.
The subnet mask shall remain the same.
All will the be the same except the IP Addresses and the default gateway.
What are the steps to accomplish this?
Thanks.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Perry Whittle SSC Guru Points: 233858 More actions · Answer 1

To change the IP address of the cluster nodes themselves, it would be best to evict in each node in turn, change the IP, then add it back

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

michaelh-731356 Old Hand Points: 319 More actions · Answer 2

Thanks. Before evicting a node, should SQL be shutdown? Or the AlwaysOn Group be shutdown? Thanks.

Perry Whittle SSC Guru Points: 233858 More actions · Answer 3

Are you using FCIs or just standalone instances in the AGs?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

michaelh-731356 Old Hand Points: 319 More actions · Answer 4

Standalone instance.

The availability group is setup as a role under the cluster.

Windows is setup as clustered, not SQL.

Thanks.

Perry Whittle SSC Guru Points: 233858 More actions · Answer 5

in that case as i said above

Remove the secondary database(s)
Remove the replica from the Availability Group(s)
evict the node from the cluster
Change the nodes IP address
re introduce to the cluster
re apply the Availability Group config onto the sql instance

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

surru54 Grasshopper Points: 12 More actions · Answer 6

We got same type of scenario came in our environment. Could any one update the right process.

Thanks in advance

This reply was modified 4 years, 10 months ago by surru54.

Perry Whittle SSC Guru Points: 233858 More actions · Answer 7

What is it you are attempting to do exactly

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

surru54 Grasshopper Points: 12 More actions · Answer 8

Our VM servers are in azure cloud and migrating to AWS cloud.

we have 3 nodes in always on availability (1- primary, 1 - secondary, 1 - DR replicas ) for voting purpose using fileshare witness in cluster. SQL Server Version 2012.

After VM's migrating to AWS cloud, IP address will change so how to sort out the issues from Windows cluster and Alwayson Listener.

Thanks

This reply was modified 4 years, 10 months ago by surru54.

Perry Whittle SSC Guru Points: 233858 More actions · Answer 9

I would say it's likely easier to deploy a new system in AWS and then migrate the database(s) to the new system, is this not an option for you?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉