Fan-In IP Pool Failover Configuration
Introduction
In a Fan-In configuration for IP Pool failover, multiple source clusters replicate data to a single target failover cluster. This document includes specifics about the requirements and configuration steps for this topology, as well as example diagrams and tables demonstrating the configuration of SyncIQ policies, IP Pool assignments, and mapping hints for a Fan-In setup between clusters.
Requirements
IP Pool Failover Requirements
A Fan-In IP Pool Failover configuration builds on the requirements outlined in the IP Pool Failover Prerequisites document.
Dedicated IP Pools
For each source cluster, the target cluster must have a dedicated IP pool that acts as the failover target.
For example, if there are three source clusters, each with one IP pool, the target cluster will require three corresponding IP pools to ensure proper failover.
Configuration Example
The following diagram gives an example of a fan-in configuration topology, where two source clusters fail over to one target cluster. For this example:
cluster20
serves as Source Cluster 01.cluster31
serves as Source Cluster 02.cluster21
is the Target Cluster.
Dual non-overlapping IP Pools are set up on the source clusters, while four non-overlapping IP Pools are configured on the target cluster. In this example, all IP Pools are assigned to the default System access zone of their corresponding cluster.
SMB Shares
source01-smb01
is configured on the Source 01 cluster.source02-smb01
is configured on the Source 02 cluster.
SMB shares are managed through the Microsoft DFS server.
NFS exports
/ifs/data/source01-nfs01
export is configured on Source 01 cluster/ifs/data/source02-nfs01
export is configured on Source 02 cluster
SyncIQ Policies
The following SyncIQ policies are configured for this example:
SyncIQ Policy to Pool Assignments
The following table illustrates the SyncIQ Policy to IP Pool assignments:
The assignments are also illustrated in the following diagram:
Mapping Hints
The igls mapping hints, including igls-ignore, must also be configured for this dual IP Pool setup.
Based on the diagram above, here is an example of the igls and igls-ignore mapping hints:
The mappings can also be seen in the following diagram:
Configuration Steps
The steps for configuring an IP Pool Failover, including Fan-In configurations, are outlined in the IP Pool Procedures document.
For this setup, special attention should be given to policy mapping and the use of mapping hints (such as igls-ignore) to ensure proper failover behavior.
See Also
For Fan-Out Failover configurations, see the Fan-Out IP Pool Failover document.