Configuring and connecting the MetroCluster IP interfaces

You must configure the MetroCluster IP (MCCIP) interfaces that are used for replication of each node's storage and nonvolatile cache. You then establish the connections using the MCCIP interfaces. This creates iSCSI connections for storage replication.

About this task

You must create two interfaces for each node. The interfaces must be associated with the VLANs defined in the MetroCluster RCF file.

You must create all MetroCluster IP interface 'A' ports in the same VLAN and all MetroCluster IP interface 'B' ports in the other VLAN.

Note: You must choose the MetroCluster IP addresses carefully because you cannot change them after initial configuration.

Considerations for MetroCluster IP configuration

Note: Starting with ONTAP 9.8, certain platforms use a VLAN for the MetroCluster IP interface. By default, each of the two ports uses a different VLAN: 10 and 20. You can also specify a different (non-default) VLAN higher than 100 (between 101—4095) using the -vlan-id parameter in the metrocluster configuration-settings interface create command.

The following platform models use VLANs.

AFF platforms FAS platforms
  • AFF A220
  • AFF A250
  • AFF A400
  • FAS2750
  • FAS500f
  • FAS8300
  • FAS8700
The following IP addresses and subnets are used in the examples:
Node Interface IP address Subnet
node_A_1 MetroCluster IP interface 1 10.1.1.1 10.1.1/24
MetroCluster IP interface 2 10.1.2.1 10.1.2/24
node_A_2 MetroCluster IP interface 1 10.1.1.2 10.1.1/24
MetroCluster IP interface 2 10.1.2.2 10.1.2/24
node_B_1 MetroCluster IP interface 1 10.1.1.3 10.1.1/24
MetroCluster IP interface 2 10.1.2.3 10.1.2/24
node_B_2 MetroCluster IP interface 1 10.1.1.4 10.1.1/24
MetroCluster IP interface 2 10.1.2.4 10.1.2/24
The physical ports used by the MetroCluster IP interfaces depends on the platform model, as shown in the following table.
Platform model MetroCluster IP port VLAN ID  
AFF A800 e0b Not used  
e1b  
AFF A700 and FAS9000 e5a  
e5b  
AFF A320 e0g  
e0h  
AFF A300 and FAS8200 e1a  
e1b  
AFF A220 and FAS2750 e0a 10 On these systems, these physical ports are also used as cluster interfaces.
e0b 20
AFF A250 and FAS500f e0c 10  
e0d 20  

The port usage in the following examples is for an AFF A700 or a FAS9000 system.

Procedure

  1. Confirm that each node has disk automatic assignment enabled: storage disk option show
    Disk automatic assignment will assign pool 0 and pool 1 disks on a shelf-by-shelf basis.
    The Auto Assign column indicates whether disk automatic assignment is enabled.
    Node        BKg. FW. Upd.  Auto Copy   Auto Assign  Auto Assign Policy
    ----------  -------------  ----------  -----------  ------------------
    node_A_1             on           on           on           default
    node_A_2             on           on           on           default
    2 entries were displayed.
    
  2. Verify you can create MetroCluster IP interfaces on the nodes: metrocluster configuration-settings show-status
    All nodes should be ready:
    Cluster       Node         Configuration Settings Status
    ----------    -----------  ---------------------------------
    cluster_A
                  node_A_1     ready for interface create
                  node_A_2     ready for interface create
    cluster_B
                  node_B_1     ready for interface create
                  node_B_2     ready for interface create
    4 entries were displayed.
    
  3. Create the interfaces on node_A_1.
    Note: The port usage in the following examples is for an AFF A700 or a FAS9000 system (e5a and e5b). You must configure the interfaces on the correct ports for your platform model, as given above.
    1. Configure the interface on port e5a on node_A_1: metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5a -address ip-address -netmask netmask
      The following example shows the creation of the interface on port e5a on node_A_1 with IP address 10.1.1.1:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_1 -home-port e5a -address 10.1.1.1 -netmask 255.255.255.0 
      [Job 28] Job succeeded: Interface Create is successful.
      cluster_A::>
    2. Configure the interface on port e5b on node_A_1: metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5b -address ip-address -netmask netmask
      The following example shows the creation of the interface on port e5b on node_A_1 with IP address 10.1.2.1:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_1 -home-port e5b -address 10.1.2.1 -netmask 255.255.255.0 
      [Job 28] Job succeeded: Interface Create is successful.
      cluster_A::>
    Note: You can verify that these interfaces are present using the metrocluster configuration-settings interface show command.
  4. Create the interfaces on node_A_2.
    Note: The port usage in the following examples is for an AFF A700 or a FAS9000 system (e5a and e5b). You must configure the interfaces on the correct ports for your platform model, as given above.
    1. Configure the interface on port e5a on node_A_2: metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5a -address ip-address -netmask netmask
      The following example shows the creation of the interface on port e5a on node_A_2 with IP address 10.1.1.2:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_2 -home-port e5a -address 10.1.1.2 -netmask 255.255.255.0 
      [Job 28] Job succeeded: Interface Create is successful.
      cluster_A::>
    2. Configure the interface on port e5b on node_A_2: metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5b -address ip-address -netmask netmask
      The following example shows the creation of the interface on port e5b on node_A_2 with IP address 10.1.2.2:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_2 -home-port e5b -address 10.1.2.2 -netmask 255.255.255.0
      [Job 28] Job succeeded: Interface Create is successful.
      cluster_A::>
  5. Create the interfaces on node_B_1.
    Note: The port usage in the following examples is for an AFF A700s or a FAS9000system (e5a and e5b). You must configure the interfaces on the correct ports for your platform model, as given in above.
    1. Configure the interface on port e5a on node_B_1:metrocluster configuration-settings interface create -cluster-namecluster-name-home-nodenode-name-home-port e5a -addressip-address-netmask netmask
      The following example shows the creation of the interface on port e5a on node_B_1 with IP address 10.1.1.3:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_B_1 -home-port e5a -address 10.1.1.3 -netmask 255.255.255.0
      [Job 28] Job succeeded: Interface Create is successful.cluster_A::>
    2. Configure the interface on port e5b on node_B_1: metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5a -addressip-address -netmask netmask
      The following example shows the creation of the interface on port e5b on node_B_1 with IP address 10.1.2.3:
      cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_B_1 -home-port e5b -address 10.1.2.3 -netmask 255.255.255.0
      [Job 28] Job succeeded: Interface Create is successful.cluster_A::>
  6. Create the interfaces on node_B_2.
    Note: The port usage in the following examples is for an AFF A700s or a FDvM200 system (e5a and e5b). You must configure the interfaces on the correct ports for your platform model, as given above.
    1. Configure the interface on port e5a on node_B_2:metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5a -addressip-addresip-addresss ip-address -netmask netmask
      The following example shows the creation of the interface on port e5a on node_B_2 with IP address 10.1.1.4:
      cluster_B::>metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_2 -home-port e5a -address 10.1.1.4 -netmask 255.255.255.0
      [Job 28] Job succeeded: Interface Create is successful.cluster_A::>
    2. Configure the interface on port e5b on node_B_2:metrocluster configuration-settings interface create -cluster-name cluster-name -home-node node-name -home-port e5b -address ip-address -netmask netmask
      The following example shows the creation of the interface on port e5b on node_B_2 with IP address 10.1.2.4:
      cluster_B::> metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_2 -home-port e5b -address 10.1.2.4 -netmask 255.255.255.0
      [Job 28] Job succeeded: Interface Create is successful.
      cluster_A::>
  7. Verify that the interfaces have been configured: metrocluster configuration-settings interface show
    The following example shows that the configuration state for each interface is completed.
    cluster_A::> metrocluster configuration-settings interface show
    DR                                                              Config
    Group Cluster Node    Network Address Netmask         Gateway   State
    ----- ------- ------- --------------- --------------- --------- ----------
    1     cluster_A  node_A_1
                     Home Port: e5a
                          10.1.1.1     255.255.255.0   -         completed
                     Home Port: e5b
                          10.1.2.1     255.255.255.0   -         completed
                     node_A_2
                     Home Port: e5a
                          10.1.1.2     255.255.255.0   -         completed
                     Home Port: e5b
                          10.1.2.2     255.255.255.0   -         completed
          cluster_B  node_B_1
                     Home Port: e5a
                          10.1.1.3     255.255.255.0   -         completed
                     Home Port: e5b
                          10.1.2.3     255.255.255.0   -         completed
                     node_B_2
                     Home Port: e5a
                          10.1.1.4     255.255.255.0   -         completed
                     Home Port: e5b
                          10.1.2.4     255.255.255.0   -         completed
    8 entries were displayed.
    cluster_A::>
  8. Verify that the nodes are ready to connect the MetroCluster interfaces: metrocluster configuration-settings show-status
    The following example shows all nodes in the ready for connection state:
    Cluster       Node         Configuration Settings Status
    ----------    -----------  ---------------------------------
    cluster_A
                  node_A_1     ready for connection connect
                  node_A_2     ready for connection connect
    cluster_B
                  node_B_1     ready for connection connect
                  node_B_2     ready for connection connect
    4 entries were displayed.
    
  9. Establish the connections: metrocluster configuration-settings connection connect
    The IP addresses cannot be changed after you issue this command.
    The following example shows cluster_A is successfully connected:
    cluster_A::> metrocluster configuration-settings connection connect
    [Job 53] Job succeeded: Connect is successful.
    cluster_A::>
  10. Verify that the connections have been established: metrocluster configuration-settings show-status
    The configuration settings status for all nodes should be completed:
    Cluster       Node         Configuration Settings Status
    ----------    -----------  ---------------------------------
    cluster_A
                  node_A_1     completed
                  node_A_2     completed
    cluster_B
                  node_B_1     completed
                  node_B_2     completed
    4 entries were displayed.
    
  11. Verify that the iSCSI connections have been established:
    1. Change to the advanced privilege level: set -privilege advanced
      You need to respond with y when you are prompted to continue into advanced mode and you see the advanced mode prompt (*>).
    2. Display the connections: storage iscsi-initiator show
      On systems running ONTAP 9.5, there are eight MCCIP initiators on each cluster that should appear in the output.

      On systems running ONTAP 9.4 and earlier, there are four MCCIP initiators on each cluster that should appear in the output.

      The following example shows the eight MCCIP initiators on a cluster running ONTAP 9.5:
      cluster_A::*> storage iscsi-initiator show
      Node Type Label    Target Portal           Target Name                      Admin/Op
      ---- ---- -------- ------------------      -------------------------------- --------
      
      cluster_A-01
           dr_auxiliary
                    mccip-aux-a-initiator 
                         10.227.16.113:65200     prod506.com.company:abab44       up/up
                    mccip-aux-a-initiator2 
                         10.227.16.113:65200     prod507.com.company:abab44       up/up
                    mccip-aux-b-initiator    
                         10.227.95.166:65200     prod506.com.company:abab44       up/up
                    mccip-aux-b-initiator2 
                         10.227.95.166:65200     prod507.com.company:abab44       up/up
           dr_partner
                    mccip-pri-a-initiator 
                         10.227.16.112:65200     prod506.com.company:cdcd88       up/up
                    mccip-pri-a-initiator2 
                         10.227.16.112:65200     prod507.com.company:cdcd88       up/up
                    mccip-pri-b-initiator 
                         10.227.95.165:65200     prod506.com.company:cdcd88       up/up
                    mccip-pri-b-initiator2 
                         10.227.95.165:65200     prod507.com.company:cdcd88       up/up
      cluster_A-02
           dr_auxiliary
                    mccip-aux-a-initiator 
                         10.227.16.112:65200     prod506.com.company:cdcd88       up/up
                    mccip-aux-a-initiator2 
                         10.227.16.112:65200     prod507.com.company:cdcd88       up/up
                    mccip-aux-b-initiator 
                         10.227.95.165:65200     prod506.com.company:cdcd88       up/up
                    mccip-aux-b-initiator2 
                         10.227.95.165:65200     prod507.com.company:cdcd88       up/up
           dr_partner
                    mccip-pri-a-initiator 
                         10.227.16.113:65200     prod506.com.company:abab44       up/up
                    mccip-pri-a-initiator2 
                         10.227.16.113:65200     prod507.com.company:abab44       up/up
                    mccip-pri-b-initiator 
                         10.227.95.166:65200     prod506.com.company:abab44       up/up
                    mccip-pri-b-initiator2 
                         10.227.95.166:65200     prod507.com.company:abab44       up/up
      16 entries were displayed.
    3. Return to the admin privilege level: set -privilege admin
  12. Verify that the nodes are ready for final implementation of the MetroCluster configuration: metrocluster node show
    cluster_A::> metrocluster node show
    DR                               Configuration  DR
    Group Cluster Node               State          Mirroring Mode
    ----- ------- ------------------ -------------- --------- ----
    -     cluster_A
                  node_A_1           ready to configure -     -
                  node_A_2           ready to configure -     -
    2 entries were displayed.
    cluster_A::>
    cluster_B::> metrocluster node show
    DR                               Configuration  DR
    Group Cluster Node               State          Mirroring Mode
    ----- ------- ------------------ -------------- --------- ----
    -     cluster_B
                  node_B_1           ready to configure -     -
                  node_B_2           ready to configure -     -
    2 entries were displayed.
    cluster_B::>