Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.
Version: 2.15.0

IPv6 Requirements and Considerations

Introduction​

Clusters that serve IPv6 clients can still be protected by Eyeglass DR edition, provided the management and replication paths used by Eyeglass and SyncIQ remain on IPv4. This section covers the requirements for a supported configuration when IPv6 is present in the environment.

Requirements​

  1. Use a dedicated management pool on IPv4 to add clusters to Eyeglass.
  2. Use a dedicated SyncIQ replication pool on IPv4 for all policies that will be failed over.
    • The target host property for each policy must be either the SSIP of the remote cluster, or a SmartConnect FQDN that resolves to an IPv4 address.
  3. Configure SyncIQ policies to use a target host property (SSIP or SmartConnect FQDN) that resolves to an IPv4 address, since this is used to validate cluster replication.
note

IPv6 client-facing pools and zones can coexist with the cluster configuration above. The IPv4 requirement applies specifically to the pools used for Eyeglass management and SyncIQ replication traffic.

Verifying the Configuration​

The legacy source for this page does not include a dedicated troubleshooting procedure — only reference screenshots of a correctly configured environment. At minimum, confirm the following before relying on failover in an IPv6 environment:

  • In the Jobs window, confirm the SyncIQ policy job shows the IPv4 management/replication pool, not an IPv6 pool.
  • In the Pool and Zone Readiness view (pre-failover and pre-failback), confirm the IPv4 pool used for replication passes readiness alongside any IPv6 client-facing pools present on the same cluster.

If you encounter a readiness failure specific to a mixed IPv4/IPv6 environment, or an IPv6 pool is mistakenly selected for replication, contact Superna Support for assistance diagnosing your configuration.

See Also​

  • Prerequisites – Platform compatibility and system requirements before deploying Disaster Recovery.
  • Choosing a Failover Type – Compare failover types and client-side failover experience, including SmartConnect-based designs.