Changing DAG & DAG members IP addresses

Changing DAG & DAG members IP addresses

This is article describes the steps needed in order to change Database availability Group (DAG) and DAG ' s members IP Addresse S.

The core steps for the "IP addresses changes are based on KB230356 which" how to change the Windows explains ' s IP ad Dresses.

In addition to the steps taken the IP addresses of the cluster's members, we should take into consideration the Exchange System The runs on the cluster ' s infrastructure. Therefore, additional steps regarding to the Exchange system were added to this document.

The Environment:

The existing Exchange environment contains 3 Exchange Mailbox servers in the DAG, one of the servers is also CAS ; HUB.

Before making the IP changes:

–before changing the IP addresses of the servers involved in the Exchange environment, write down as in the next table, T He and the new IP addresses:

#

Server Name

Role

Current IP Address

New IP Address

1

EX141

Mbx/hub/cas

100.100.100.201

100.100.97.201

2

EX142

MBX

100.100.100.202

100.100.97.202

3

EX143

MBX

100.100.100.203

100.100.97.203

4

Dag

Cluster

100.100.100.234

100.100.97.234

–in this case, the current and the new IP addresses are in same subnet (255.255.248.0). This means the no subnet changes needs to take place.

–update all of the other messaging related consumers which this change might prevent them from getting the messaging service During the IP changes period.

–the IP addresses change is reversible. In case this is something gets wrong because of network or other issues, you can revert back to the previous IP addresses con Figuration.

–it is recommended to suspend the databases replication and dismount the databases before the IP making.

Steps taken to change the IP addresses:

* In case you are are moving the dag/nodes to different subnets, add the new IP that would represent the DAG as a mandatory s Tep by running the next command (although can do it via the EMC) before starting the next steps:

Set-databaseavailabilitygroup–identity dag-databaseavailabilitygroupipaddress 100.100.100.234,100.100.97.234

1. Verify that the cluster's resources (IP & Name) are owned by one of the other cluster ' s nodes and not on the node Y ou are going to run the IP changes. In this case, the the ' the ' the ' the ' going to take place on EX141. In order to check which node are owned the cluster ' s resources, we should run the next command:

Cluster Group "Cluster Group"/state

In case EX141 is owned the cluster's, use the "next command to move the" to "other node" in the cluster (E X142):

Cluster Group "Cluster Group"/moveto:ex142

2. Stop all Exchange's services on the Exchange server which it ' s IP was going to be changed.

In order to stop all the Exchange services quickly, stop the Microsoft Exchange Active Directory topology Service (MSEXC Hangeadtopology). Stopping this service would stop all other Exchange services in and the "YES" in the next screenshot:

3. Verify, all of the Exchange ' s services are in "Stopped" and "No monitoring" or "," started up a Gain.

4. Check the Hosts file on all Exchange servers in the environment and verify that it doesn ' t contains the Dag/dag Membe RS IP address. The Hosts file is located at the next path:

C:\Windows\System32\drivers\etc

In case this is the Hosts file contains IP addresses relevant to the DAG or DAG members, change those IP addresses to the new IP addresses.

5. Change the IP addresses of the network adapter on node EX141 to the new IP address. This requires the computer to be rebooted.

6. After the "server is" up and running again, verify "node EX141 was registered in" DNS with A & PTR Records .

7. Verify that node EX141 can ping the domain controllers and so other servers can ping the servers. In addition, check the communication between the server and the HUB & CAS servers.

8. Before changing EX142 IP address, fail the cluster ' s resources (IP & Name) over to the functional node EX141. In order to failover to EX141 node, run the next command:

Cluster Group "Cluster Group"/moveto:ex141

9. Change the IP addresses for the network adapters in node EX142 and reboot the server.

Verify that node EX142 can ping the domain controllers and so other servers can ping EX142. In addition, check the communication between the server and the HUB & CAS servers.

Before changing EX143 IP address, fail ail the cluster ' s resources (IP & Name) over to one of the cluster ' s nodes You are have already changed IP address (EX141 node, in this example). Run the next command:

Cluster Group "Cluster Group"/moveto:ex141

The change is the IP addresses for the network adapters in node EX143 and reboot the server.

Verify that node EX143 can ping the domain controllers and so other servers can ping EX143. In addition, check the communication between the server and the HUB & CAS servers.

Verify that "Cluster service is" up and "all nodes are online:

The DAG IP address to the new IP address (same as cluster). In order to change it, run the next command:

Set-databaseavailabilitygroup–identity dag-databaseavailabilitygroupipaddress 100.100.97.234

This command would remove the old IP addresses of the DAG and leave it with the new "new" IP address.

In case this you have changed the subnet mask as OK, run the "discovernetworks" option, in order to force rediscover Y of all DAG networks:

Set-databaseavailabilitygroup–identity Dag-discovernetworks

Verify that's in "Failover Cluster Manager", which Cluster resources are up and the new IP address:

Verify, all, Exchange services on all nodes are up

Verify to DAG's IP address is changed, run the next command:

Get-databaseavailabilitygroup Dag–status | FL databaseavailabilitygroupip*

At the Failover Cluster Manager, double-click IP addresses resource to open its properties.

On the Parameters tab into the IP Address resource properties, make sure the Network to use box contains the new NE Twork as the network to use:

Verify that "application" and "System" doesn ' t contain any errors related the cluster or exchange.

Verify that the Cluster's IP address are registered with the new IP addresses at the DNS.

24.Now Check that the "cluster is working" by moving and the other cluster ' s members:

Cluster Group "Cluster Group"/move

After the infrastructure (Windows servers, cluster) is configured and working, verify that all databases At mounted state.

Now move/activate one of the "mounted databases to one of the" DAG members and verify this activation is WOR King as expected.