CONTAP-784523: Cross-cluster data transfer or replication fails between peered clusters due to duplicate addresses in stale cluster peer entries
Issue
Data transfer or replication to a remote cluster (for example SnapMirror, FlexCache, or other peering-dependent operations) can fail or behave unpredictably between peered ONTAP clusters when two or more cluster peers have the same intercluster addresses in the same IpSpace. This can occur even when one cluster peer is decommissioned and inactive but it has not been deleted from the cluster peer table.
In
In
{}cluster peer show{}, you might see more than one cluster peer in the same IPspace where the same intercluster peer IP address is associated with different remote clusters. Stale relationships will be seen to be unavailable (for example decommissioned or retired clusters) while newer relationships reuse the same addresses. Cluster peering for the active relationship can still appear configured, which makes the problem easy to miss until cross-cluster traffic fails or a new intercluster connection is required.