Skip to main content
Version: 2.9.0

What is IP Pool Failover?

Introduction​

IP Pool Failover is a distinct process, different from Access Zone Failover. Though both types are similar: IP Pool Failover applies at the network level, and Access Zone applies at the storage and security level.

Specifically, IP Pool Failover is used when there is interest in ensuring continuous connectivity between Clients and Clusters, in case of failure of a node or interface.

Which factors are involved?​

The factors involved in this type of Failover are, on both the Source and Target PowerScale OneFS:

  • The Network Pool
  • The Access Zone
  • SyncIQ Policies

These factors interact in certain ways during Failover in order to help execute the process correctly.

There are Automatic and Manual interactions that are necessary for Failover, for example:

  • Automatic
    • SyncIQ Policy target path is made writeable and source path read-only.
  • Manual
    • NFS Exports must be remounted.

How is IP Pool Failover executed?​

In the simplest terms, the entire process of IP Pool Failover is described as follows:

  1. Failover is initiated. (Manual)
  2. SyncIQ Policies are run one last time. (Automatic)
  3. SmartConnect Zone Names and Aliases are moved to the Target Cluster. (Automatic)
  4. The HOST SPNs are deleted on the Source Cluster and Created on Target Cluster in AD. (Automatic)
  5. SyncIQ Policy target path is made writeable.(Automatic)
  6. Resync prep creates mirror SyncIQ policy and runs it. (Automatic)
  7. Quotas are deleted on Source Cluster and Created on Target Cluster. (Automatic)
  8. Post-Failover Steps. (Manual)

For more information consult the Failover Operations family of articles.

What are the results of IP Pool Failover?​

Once IP Pool Failover is complete, you will find that:

  • SMB Shares and NFS exports/aliases are replicated to the Target Cluster.
  • Mirror SyncIQ Policies are created and have been run.
  • Each Source Pool's SmartConnect Name is mapped with an igls- prefix wherever applicable, be it igls-original- or igls-ignore-.
  • Clients are able to connect to the Failed Over IP Pools without issue.