Change replication type from RCIP to RCFC

[prasanth]

We have two P10400 storages, configured with Remote copy over RCIP serving rcgroups of around 20 VVs.
We have established new DARK fiber connectivity across sites & configured RCFC ports on both storages.
When I was adding FC links using the IMC, it has created additional target, instead of using existing target.
Can we able to force use existing RC groups replicate over FC?
Also I have noticed, RCFC target only allow periodic replication & not synchronous replication .
I am wondering, what we missing?

[sharfuddin]

what is the version of 3par ?

RCFC target only allow periodic replication & not synchronous replication
Ans:- there was a bug related to the continuously sync with CA/CLX, last week 3par development release new DLL that will resolve the sync issue.

[prasanth]

Hi Sharfiddin,

Thank you for your reply.

I this this restriction is only applicable while RCFC over an IP network. But we are using DARK fiber for replication.



See below from HP 3PAR Remote Copy® 3.1.1 Software User’s Guide

. The node set up in synchronous mode must use Fibre Channel (RCFC), and the node set up in asynchronous periodic mode must use IP links (RCIP).
. RCFC over an IP network is not supported for two-node Synchronous Long Distance configurations.


I am not sure about the 3PAR Remote Copy® 3.1.2, which we are currently using.

[spencer.ryan]

But we are using DARK fiber for replication.

Stick some Ethernet optics on the ends?

[ailean]

I assume your existing RCIP groups are async, in which case this might be related to the old limitation that once you created the first group between two arrays all subsequent groups had to be the same type (sync or async).
I believe this was improved in 3.1.2GA and 3.1.2MU2 but my understanding is that you need separate physical links and pairings between the arrays to support both at the same time.
I guess that should work with your RCIP and RCFC links but maybe some other restriction or the IMC thinking it's still not allowed (are you running the latest, 4.4.2?), could possibly try via the CLI although that is a little convoluted.
A little drastic but as you only have 20 VVs you could delete the existing rcgroups, then when you recreate the first one again set it as sync via RCFC (this seemed to work when I was looking at this issue on 3.1.1).