Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5805

April 21st, 2015 02:00

how to modify WAN IP address of one cluster when it is connected with others

I have cluster1 and cluster2, they connected normally, and remote copy CG is configured, if I use deploy manager to change WAN IP of cluster2, is the operation fully online? will the CG be impacted? and is there anything need to do to CLUSTER1 after the cluster Modification wizard of CLUSTER2 done?

2 Intern

 • 

1.1K Posts

April 21st, 2015 03:00

Pause replication, make the networks changes, then make the changes in via DM, then use the system connectivity test option from one of the RPA's via boxmgmt and if everything is OK resume replication.

1 Rookie

 • 

33 Posts

April 21st, 2015 02:00

thanks Forshr,

If the laptop which run deploy manager cannot connect with management IP of CLUSTER1(can only connect with CLUSTER2), it can still work, the actions which CLUSTER1 need to do will be sent by current WAN connection.  Is my understanding right?

2 Intern

 • 

1.1K Posts

April 21st, 2015 02:00

DM handles this for you. There is no disruption to replication. You may see some short init activity.

2 Intern

 • 

1.1K Posts

April 21st, 2015 02:00

Correct, you only need connectivity to one of the clusters for this requirement.

1 Rookie

 • 

33 Posts

April 21st, 2015 03:00

But If I need to change subnet and router of WAN, and need to do some physical change at the same time (for example, reconnect WAN ports of cluster2 to another eth switch), that means when the cluster Modification Wizard finished, the RPA of CLUSTER2 cannot connect to CLUSTER1, even cannot connect to ROUTER - because they need to be reconnected to other switch.  Is it still possible for the operation keep CG online? need we pause CG first in this condition?

Or the cluster Modification wizard will guide us to check WAN connection when it find WAN connection doesn't restore after it finish the RPA1 modification, and hold RPA2 modification until RPA1 WAN restore?  I think if it work like this, the CG can keep online.

1 Rookie

 • 

33 Posts

April 21st, 2015 04:00

Very clear, Thanks very much.

9 Posts

November 30th, 2018 05:00

I have changed wan ip (5.1) using DM. At the each local cluster level is ok. But both remote clusters will try to communicate each other using the old WAN ip address. Any idea how to force new WAN IP? I'm affraid the full sync, but if required, I can survive even recreating all CGs and refreshing journal volumes, but if I can avoid it ...

675 Posts

December 2nd, 2018 20:00

Hi there,

No need to do anything other than leverage DM cluster modification wizard to update the WAN IPs on the relevant cluster, no need to update the connected clusters, unless IPs on these clusters should be changed as well.

Hope that helps,

Idan

9 Posts

December 5th, 2018 02:00

"Unless IPs on these clusters should be changed as well". Was changed. From DM. On both sites. Each site is reconfigured correctly, but from the local cluster point of view, remote cluster is on the old IPs. I'm looking for the option "connected cluster modification wizzard". To remove cluster to add it again, I will have to remove all the staff from the clustered pair first ...

Solution:

I have returned to the original WAN IP addresses and reconfigured network to be able to use both old and new IP. But it changed conditions - separated networks --> common network.

In this new scenario:

1. I have changed the first WAN IP address (cluster A new WAN_IPs with new routing/gateway, cluster B old WAN_IP). OK - WAN address of the modified cluster A propagated to the Cluster B as a new WAN address of the remote cluster A.

2. After all was green (groups still paused) I have changed cluster B WAN IP  (and routing). After a few seconds information about new WAN IP of the cluster B was propagated to the cluster A. Finished

3. Start replication.

Separated networks:

But if after the first change I will loose ip connectivity (new ip address of cA is unable to access old ip of cB) and next will occurre the second change of the WAN_IP of cB, when cB has NOW no connectivity to cA  --> and next cable reconnect to the new WAN, I don't know.

IF the new WAN IP of cA was transferred to the cB and NEXT WAN_IP of cA was changed THAN after changing WAN_IP of cB and reconnection both clusters to the new network:

cB connects to the already changed WAN_IP of cA (from new WAN IP)

cA is being informed by cB about new WAN_IP of cB

Someone tested it?

2 Intern

 • 

1.1K Posts

December 6th, 2018 09:00

Pause replication before doing this and test the WAN connectivity from both ends using the System Connectivity option through Installation Manager -> Diagnostic -> System Connectivity as admin or boxmgmt depending on your version before resuming replication.

Regards,

Rich

No Events found!

Top