Skip to main content

Learn about ONTAP Mediator for MetroCluster IP and SnapMirror active sync

Contributors netapp-aoife netapp-sarajane netapp-thomi netapp-camdenc netapp-lenida netapp-dbagwell
PDFs

ONTAP Mediator supports SnapMirror active sync and MetroCluster IP by providing a persistent and fenced store for high-availability (HA) metadata, synchronous node health query functionality to aid in quorum determination, and serving as a ping proxy for controller liveliness.

ONTAP Mediator runs on a Linux host in a third failure domain, separate from your ONTAP clusters, where it provides a persistent, fenced store for HA metadata. ONTAP uses this store, along with the Mediator's node health query and ping-proxy functions, to monitor SnapMirror active sync relationships and MetroCluster IP configurations.

  • ONTAP Mediator uses the node management LIF and cluster management LIF to communicate with each cluster over multiple, redundant paths. This lets ONTAP distinguish between a full site failure and a single InterSwitch Link (ISL) failure.

  • In SnapMirror active sync, if a cluster loses connection to both its peer and ONTAP Mediator, ONTAP treats the peer as unreachable and can automatically fail over to the surviving copy.

  • In MetroCluster IP configurations, ONTAP Mediator assists with a Mediator-assisted automatic unplanned switchover (MAUSO) by storing state information about the MetroCluster nodes and helping determine the appropriate course of action during a failure.

To install or upgrade the on-premise version of ONTAP Mediator, refer to the ONTAP Mediator documentation

For information about ONTAP Cloud Mediator, available beginning with ONTAP 9.17.1, refer to the SnapMirror active sync documentation.