Start a Conversation

Unsolved

This post is more than 5 years old

A

5 Practitioner

 • 

274.2K Posts

1492

August 26th, 2016 07:00

What is the procedure for converting fibre connection for CRR to WAN connection?

Is there a document procedure for converting fibre channel intersite connection to WAN connection?

August 26th, 2016 10:00

I assuming you are referring to sending the replication data across Fibre Channel between your sites.  Are you talking about modifying an existing environment, or is this a new deployment?

Assuming you have IP connectivity between sites, there's no need for running remote replication over FibreChannel, you just need to ensure that the WAN ports on your appliances are able to communicate to each other.

5 Practitioner

 • 

274.2K Posts

August 27th, 2016 04:00

Hi Misterodd,

Assuming you are a 4.x RP version and have an already existing replication going on FC and want to change replication over to WAN, First a checklist to ensure a smooth transition:

1- Check MTU between sites need to set MTU correctly in case of using VPN between sites etc..

2- We prefer WAN and LAN be in seperate subnets for ease of routing the packets and isolating network issues.

3- Need to add a routing on each Site to the other Site WAN network ID to add a routing rule specifically for the WAN interface eth0.

4- Review the Security guide of your RP version to make sure all ports RP will need are not being blocked or manipulated by firewall or Proxy.

5- NAT is not supported.

6- If using Sync replication need to ensure latency on WAN wont exceed 4 ms round time trip if not so might hit perfomance issues and need to re-consider Async replication instead.

7- Of course we are speaking of Physical RPAs and not vRPAs.

Now the steps are easy provided you have configured  IP correctly and configured route correctly on each RP cluster inside the RP system,

1- Login as boxmgmt to cluster Site IP via ssh of one of the RP clusters involved preferably the source cluster or Prod cluster

2- Choose option 4 "Cluster operations"

3- Choose again option 4 " Configure connection types to other clusters in the system"

4- this option will take you through a wizard to specify type FC or IP and the other site connection with.

5- if all is ok and WAN communication can be established it should change successfully.

Thx,

MAG

5 Practitioner

 • 

274.2K Posts

August 29th, 2016 06:00

Thanks for your input, it has been very helpful...

1.1K Posts

August 30th, 2016 05:00

Hi,

1. When converting remote replication from FC to IP, ensure that the proper IP addresses and Gateways are defined at each cluster and that you’re able to perform a ping test from each site to the remote site. When performing a ping test using the boxmgmt user via the Installation Manager menu, issue the following command though the internal command option using the WAN interface eth0 as follows:

· ping -I eth0

Twitter: @rw4shaw

EMC Europe Limited

Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.

1.1K Posts

August 31st, 2016 10:00

Hi,

1. When converting remote replication from FC to IP, ensure that the proper IP addresses and Gateways are defined at each cluster and that you’re able to perform a ping test from each site to the remote site. When performing a ping test using the boxmgmt user via the Installation Manager menu, issue the following command though the internal command option using the WAN interface eth0 as follows:

ping -I eth0

Twitter: @rw4shaw

EMC Europe Limited

Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.

1.1K Posts

August 31st, 2016 10:00

Hi,

1. When converting remote replication from FC to IP, ensure that the proper IP addresses and Gateways are defined at each cluster and that you’re able to perform a ping test from each site to the remote site. When performing a ping test using the boxmgmt user via the Installation Manager menu, issue the following command though the internal command option using the WAN interface eth0 as follows, ping –l eth0

2. Ensure that all required network ports are opened as specified in the RecoverPoint 4.x Security Guide .

3. After validating IP connectivity between the clusters, detach each RPA from the cluster using the Cluster operations -> Detach RPA from cluster option using boxmgmt.

4. Modify connection type using the Configure connection types to other clusters in the system -> Configure cluster connection types option using boxmgmt.

5. Attach the RPA back to the cluster (I would recommend performing steps 3 – 5 on parallel nodes, i.e. RPA1/RPA1, RPA2/RPA2 etc).

6. Repeat for the other RPAs in the cluster.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint and RecoverPoint for VMs

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: +44 (0) 7730 781169

E-mail: richard.forshaw@emc.com

Twitter: @rw4shaw

EMC Europe Limited

Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.

No Events found!

Top