Skip to main content
ONTAP MetroCluster

Set up the ONTAP Mediator for a MetroCluster IP configuration

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

You must configure the ONTAP Mediator on the ONTAP node to use it in a MetroCluster IP configuration.

Before you begin

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

    Install or upgrade ONTAP Mediator

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

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

  • 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.

  • Beginning with ONTAP 9.18.1 and ONTAP Mediator 1.11, a single ONTAP Mediator instance can manage up to ten MetroCluster configurations simultaneously. In earlier releases, ONTAP Mediator can support up to five MetroCluster configurations simultaneously.

Steps

  1. Add ONTAP Mediator to ONTAP. The steps depend on whether you want to use an IPv4 or IPv6 address.

    Note

    • You must be running ONTAP 9.18.1 or later and ONTAP Mediator 1.11 or later to use IPv6.

    • If you enable IPv6 on a cluster, you cannot disable it later.
    Use IPv4

    1. Run the following command to add the ONTAP Mediator:

      metrocluster configuration-settings mediator add -mediator-address <mediator_host_ip_address>

      Note You are prompted for the username and password for the Mediator admin user account.
    Use IPv6

    1. Run the following command on both clusters:

      network options ipv6 modify -enabled true

    2. Configure the node-mgmt IP address with IPv6 addresses on all four nodes.

    3. Add the ONTAP Mediator:

      metrocluster configuration-settings mediator add -mediator-address <mediator_host_ipv6_ip_address>

      Note You are prompted for the username and password for the Mediator admin user account.

  2. Verify that the automatic switchover feature is 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
 ---- ---- -------- ------------------ -------------------------------- --------
 node_A_1
      mailbox
           mediator 1.1.1.1       iqn.2012-05.local:mailbox.target.6616cd3f-9ef1-11e9-aada-00a098ccf5d8:a05e1ffb-9ef1-11e9-8f68- 00a098cbca9e:1 up/up
 node_A_2
      mailbox
           mediator 1.1.1.1       iqn.2012-05.local:mailbox.target.6616cd3f-9ef1-11e9-aada-00a098ccf5d8:a05e1ffb-9ef1-11e9-8f68-00a098cbca9e:1 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.

    Important Before using this command, review the Risks and limitations of using MetroCluster automatic forced switchover.

    metrocluster modify -allow-auto-forced-switchover true

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