MSA Storage
1845844 Members
3565 Online
110250 Solutions
New Discussion

Re: MSA 2050 Replication issue

 
SamFan
Occasional Contributor

MSA 2050 Replication issue

Hi guys

I hava 3 MSA 2050 storages, and each replication to the other.

"A to B to C to A"

Recently, B MSA got some issue and we have replaced some parts.

Raid/disk and controller is working fine now.

But at the replication function is missing config.

In UI its empty, so I try to reconfig the replication and peer connections.

And it shows duplicate names, but in cli there is also empty.

I also cant delete peer connection on A & C.

Is there any solutions for this?

 

Thank guys

4 REPLIES 4
Sahana_S
HPE Pro

Re: MSA 2050 Replication issue

Hello @SamFan ,

The duplicate names and inability to delete peer connections suggest leftover metadata or system state issues.

Try to follow the below steps:

  1. Validate hardware health and firmware versions.
  2. Clear stale peer connection metadata using the CLI.
  3. Reset replication configuration if necessary.
  4. Recreate replication relationships in a clean state.
  5. If issues persist, engage HPE Support for further analysis.

I hope this helps!

Thanks and Regards,
Sahana S



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
SamFan
Occasional Contributor

Re: MSA 2050 Replication issue

Hi 

Thank you for reply!

  1. Clear stale peer connection metadata using the CLI.
  2. Reset replication configuration if necessary.

Is there commad for these two?

I cant delete and I cant see any config in this command.

 

Thank you

Sahana_S
HPE Pro

Re: MSA 2050 Replication issue

Hello @SamFan ,

On each system (A, B, and C), check the peer connection list using the command "show peers", look for duplicated names, invalid entries, or missing peer connections.
If duplicate peer connections exist, try deleting them using "delete peer-connection <peer-name>".
If deletion fails due to corruption, you may need to restart the controllers (optional).

To reset replication configuration:
1. On each system, ensure no active replication sessions are running.
2. Clear all replication relationships on A, B and C. (delete all-replications)
3. Then reconfigure the peer connections and replications.

If the issue persists, contact HPE Support for further assistance.

Hope this information has helped you, Please click on the "Thumbs Up/Kudo" icon as a token of appreciation. Also, if this post has helped to solve your issue, consider marking this as an "Accepted Solution".

Thanks and Regards,
Sahana S





I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
kyla598ellis
Occasional Visitor

Re: MSA 2050 Replication issue


@SamFan MyAarpMedicare wrote:

Hi guys

I hava 3 MSA 2050 storages, and each replication to the other.

"A to B to C to A"

Recently, B MSA got some issue and we have replaced some parts.

Raid/disk and controller is working fine now.

But at the replication function is missing config.

In UI its empty, so I try to reconfig the replication and peer connections.

And it shows duplicate names, but in cli there is also empty.

I also cant delete peer connection on A & C.

Is there any solutions for this?

 

Thank guys


Hello @SamFan,

This sounds like a replication metadata mismatch. Try these steps:

1. Clear stale peer connections via CLI using `delete peer-connection` on A & C.
2. Reset replication config on B using `clear replication-queue` and reinitialize with `create peer-connection` and `create replication-set`.
3. Ensure all systems have matching firmware versions** and valid licenses.

Refer to this CLI guide for exact commands. A full config reset may be needed if corruption persists.

Best Regards,
Kyla Ellis