Creating a Replication Session between two MSA 2062 storasge arrays

[MehdiTech]

I have two MSA 2062 Storage Arrays which I have to create a replication session between these two arrays. I have them both configured (they are on the same network installed in the same rack) (one has a xxxxxx19.1  and the other has xxxxxx19.2 as the ip) same pool and volume is created on both of them. and these two MSA arrays are connected to HPE  gen 10 servers using FC. when I created the replication session the process was stopped at below 10 percent showing "it was stopped internally" . I need to know everything that have to be considered when creating a replication session (since there are no videos on the internet showing the steps and the documents of the best practice for the storage doesn't include the step by step guide it would be great if someone could help me set this up.)

[ArunKKR]

Hi,  These are the only prerequisites mentioned in SMU guide for replication: 

The prerequisites to create a peer connection are:
l Both systems must be licensed to use replication.
l Both systems must have iSCSI or FC host ports. Ports at both ends of the connection must use the same protocol.
l Both systems must be connected to the same fabric or network via a switch; direct connection between storage
systems is not supported.
l All host port addresses in both systems must be unique, even for ports not in use.
l If iSCSI CHAP is configured for the peer connection, the authentication must be valid.

https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&docLocale=en_US

If the replication has already started and reached 10%, I dont believe any further configuration is required.  Please check SAN switch logs to rule out FC path issues.

Please review the MSA events under Maintenance > Support to check whether it gives any details as to what triggered the replication failure.  You may also try creating a small test volume and check whether replication gets completed. The best option for you would be to log a support case to confirm whether there are any issues from debug logs.

[ArunKKR]

Hello @MehdiTech , 

Let us know if you were able to resolve the issue.
 
If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

[MehdiTech]

I still have the issue and the exact log we get is:

It'd be great to know how we should resolve this issue.

[Moderator edit: Erased the confidential info.]

[ArunKKR]

Hi @MehdiTech ,

Apart from the connectivity issues between 2 arrays I cant think of any reason for this to happen.

Check the events whether any repeated events related to update server task is appearing.

Try replication by creating a small test volume and check whether it gets completed successfully.

Execute the below command and check whether management controller IP address of both controllers are showing up correctly.   show network-parameters

As I mentioned earlier logging an HPE support case and sharing the logs with support team would be the best option to rule out any underlying issues.