Skip to main content
ONTAP MetroCluster

Configure the ONTAP Mediator service from a MetroCluster IP configuration

Contributors netapp-martyh netapp-aoife netapp-pcarriga netapp-folivia netapp-thomi thrisun

The ONTAP Mediator service must be configured on the ONTAP node for use in a MetroCluster IP configuration.

Before you begin
  • The ONTAP Mediator must have been successfully installed on a network location that can be reached by both MetroCluster sites.

  • You must have the IP address of the host running the ONTAP Mediator service.

  • You must have the username and password for the ONTAP Mediator service.

  • All nodes of the MetroCluster IP configuration must be online.

Caution Beginning with ONTAP 9.12.1, you can enable the MetroCluster automatic forced switchover feature in a MetroCluster IP configuration. This feature is an extension of the Mediator-assisted unplanned switchover. Before you enable this feature, review the Risks and limitations of using MetroCluster automatic forced switchover.
About this task
  • This task enables automatic unplanned switchover by default.

  • This task can be performed on the ONTAP interface of any node in the MetroCluster IP configuration.

  • A single installation of the ONTAP Mediator service can be configured with up to five MetroCluster IP configurations.

  1. Add the ONTAP Mediator service to ONTAP:

    metrocluster configuration-settings mediator add -mediator-address ip-address-of-mediator-host

    Note You will be prompted for the username and password for the Mediator admin user account.
  2. Verify that the automatic switchover feature in enabled:

    metrocluster show

  3. Verify that the Mediator is now running.

    1. Show the Mediator virtual disks:

      storage disk show -container-type mediator

       cluster_A::> storage disk show -container-type mediator
                              Usable           Disk    Container   Container
       Disk                   Size Shelf Bay Type    Type        Name      Owner
       ---------------- ---------- ----- --- ------- ----------- --------- --------
       NET-1.5                   -     -   - VMDISK  mediator    -         node_A_2
       NET-1.6                   -     -   - VMDISK  mediator    -         node_B_1
       NET-1.7                   -     -   - VMDISK  mediator    -         node_B_2
       NET-1.8                   -     -   - VMDISK  mediator    -         node_A_1
    2. Set the privilege mode to advanced:

      set advanced

       cluster_A::> set advanced
    3. Display the initiators labelled as mediator:

      storage iscsi-initiator show -label mediator

       cluster_A::*> storage iscsi-initiator show -label mediator
         (storage iscsi-initiator show)
        +                                                                     Status
       Node Type Label    Target Portal      Target Name                      Admin/Op
       ---- ---- -------- ------------------ -------------------------------- --------
                 mediator 00a098cbca9e:1 up/up
                 mediator up/up
    4. Verify the state of the automatic unplanned switchover (AUSO) failure domain:

      metrocluster show

      Note The following example output applies to ONTAP 9.13.1 and later. For ONTAP 9.12.1 and earlier, the AUSO failure domain state should be auso-on-cluster-disaster.
      cluster_A::> metrocluster show
      Cluster                   Entry Name          State
      ------------------------- ------------------- -----------
      Local: cluster_A         Configuration state configured
                                Mode                normal
                                AUSO Failure Domain auso-on-dr-group-disaster
      Remote: cluster_B         Configuration state configured
                                Mode                normal
                                AUSO Failure Domain auso-on-dr-group-disaster
  4. Optionally, configure MetroCluster automatic forced switchover.

    You can only use the following command in advanced privilege level.

    metrocluster modify -allow-auto-forced-switchover true

    cluster_A::*> metrocluster modify -allow-auto-forced-switchover true