As stated previously in Target cluster SmartConnect zones, SyncIQ only functions under static IP pool allocation strategies. A dynamic allocation of IPs leads to SyncIQ failures.
During data replication, certain SyncIQ packets set the “Do not fragment” (DF) bit, causing the connection to fail if fragmentation is required. A common instance is if jumbo frames are configured on the cluster, but are not supported on all network devices, requiring fragmentation at a specific hop. If jumbo frames are configured, ensure that they are supported end-to-end on all hops between the source and target cluster, eliminating the need for fragmentation. Otherwise, set the network subnet used by SyncIQ to an MTU of 1500. For more information about jumbo frames, see the white paper.
During the design phase of SyncIQ policies and network hierarchy, note that SyncIQ is not zone aware, requiring SyncIQ policies and data replication to be aligned with the System Access Zone. If a new SyncIQ policy, or an existing policy, is configured for anything other than the System Access Zone, the configuration fails with an error message. The SyncIQ requirement for this zone applies to the source and target clusters. Taking this requirement into account during the design phase allows administrators to plan policies, subnets, and pools accordingly, if SyncIQ replication must be limited to a set of nodes and interfaces.