Table of ContentsView in Frames

Configuring intercluster LIFs to use dedicated intercluster ports

Configuring intercluster LIFs to use dedicated data ports allows greater bandwidth than using shared data ports on your intercluster networks for cluster peer relationships.

About this task

In this example, a two-node cluster exists in which each node has two data ports, e0e and e0f, which are dedicated for intercluster replication. In your own environment, you would replace the ports, networks, IP addresses, subnet masks, and subnets with those specific to your environment.

To learn more about LIFs and port types, see the Clustered Data ONTAP Network Management Guide

Steps

  1. Check the role of the ports in the cluster by using the network port show command.
    Example
    cluster01::> network port show
                                          Auto-Negot  Duplex     Speed(Mbps)
    Node   Port   Role         Link MTU   Admin/Oper  Admin/Oper Admin/Oper
    ------ ------ ------------ ---- ----- ----------- ---------- ----------
    cluster01-01
           e0a    cluster      up   1500  true/true   full/full  auto/1000
           e0b    cluster      up   1500  true/true   full/full  auto/1000
           e0c    data         up   1500  true/true   full/full  auto/1000
           e0d    data         up   1500  true/true   full/full  auto/1000
           e0e    data         up   1500  true/true   full/full  auto/1000
           e0f    data         up   1500  true/true   full/full  auto/1000
    cluster01-02
           e0a    cluster      up   1500  true/true   full/full  auto/1000
           e0b    cluster      up   1500  true/true   full/full  auto/1000
           e0c    data         up   1500  true/true   full/full  auto/1000
           e0d    data         up   1500  true/true   full/full  auto/1000
           e0e    data         up   1500  true/true   full/full  auto/1000
           e0f    data         up   1500  true/true   full/full  auto/1000
  2. Determine whether any of the LIFs are using ports that are dedicated for replication by using the network interface show command.
    Example
    cluster01::> network interface show
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    cluster01
                cluster_mgmt up/up    192.168.0.xxx/24   cluster01-01  e0c     true
    vs1
                vs1_lif1     up/up    192.168.0.151/24   cluster01-01  e0e     true
  3. If a LIF is using one of the ports dedicated to replication, then assign the LIF to a different home port by using the network interface modify command.
    The LIF cannot remain on the port you want to dedicate to replication, because intercluster ports cannot host data LIFs.

    The network interface modify operation is nondisruptive, because the LIF has not yet moved from port e0e. The network interface modify command shown below changes the port to which the LIF returns when the network interface revert command is issued.

    Example
    cluster01::> network interface modify -vserver vs1 -lif vs_lif1 -home-node cluster01-01 -home-port e0d
    
    cluster01::> network interface show
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    cluster01
                cluster_mgmt up/up    192.168.0.xxx/24   cluster01-01  e0c     true
    vs1
                vs1_lif1     up/up    192.168.0.151/24   cluster01-01  e0e     false
  4. Revert the LIF to its new home port by using the network interface revert command.
    Assigning the LIF to a different port by combining the network interface modify and network interface revert commands avoids the risk that the LIF might fail back to its original port.
    Example
    cluster01::> network interface revert -vserver vs1 -lif vs_lif1 
    
    cluster01::> network interface show
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    cluster01
                cluster_mgmt up/up    192.168.0.xxx/24   cluster01-01  e0c     true
    vs1
                vs1_lif1     up/up    192.168.0.151/24   cluster01-01  e0d     true
  5. After all LIFs have been migrated off the ports dedicated for replication, change the role of the port used on each node to intercluster by using the network port modify command.
    Example
    cluster01::> network port modify -node cluster01-01 -port e0e -role intercluster
    
    cluster01::> network port modify -node cluster01-01 -port e0f -role intercluster
    
    cluster01::> network port modify -node cluster01-02 -port e0e -role intercluster
    
    cluster01::> network port modify -node cluster01-02 -port e0f -role intercluster
  6. Verify that the roles of the correct ports have been changed to intercluster by using the network port show command with the -role intercluster parameter.
    Example
    cluster01::> network port show –role intercluster
                                          Auto-Negot  Duplex     Speed(Mbps)
    Node   Port   Role         Link MTU   Admin/Oper  Admin/Oper Admin/Oper
    ------ ------ ------------ ---- ----- ----------- ---------- ----------
    cluster01-01
           e0e    intercluster up   1500  true/true   full/full  auto/1000
           e0f    intercluster up   1500  true/true   full/full  auto/1000
    cluster01-02
           e0e    intercluster up   1500  true/true   full/full  auto/1000
           e0f    intercluster up   1500  true/true   full/full  auto/1000
  7. Create an intercluster LIF on each node in cluster01 by using the network interface create command.
    Example
    This example uses the LIF naming convention nodename_icl# for the intercluster LIF.
    cluster01::> network interface create -vserver cluster01-01 -lif cluster01-01_icl01 -role intercluster -home-node cluster01-01 -home-port e0e 
    -address 192.168.1.201 -netmask 255.255.255.0
    Info: Your interface was created successfully; the routing group i192.168.1.0/24 was created
    
    cluster01::> network interface create -vserver cluster01-02 -lif cluster01-02_icl01 -role intercluster -home-node cluster01-02 -home-port e0e 
    -address 192.168.1.202 -netmask 255.255.255.0
    Info: Your interface was created successfully; the routing group i192.168.1.0/24 was created
  8. Verify that the intercluster LIFs are configured for redundancy by using the network interface show command with the -role intercluster and -failover parameters.
    Example
    The LIFs in this example are assigned the e0e home port on each node. If the e0e port fails, the LIF can fail over to the e0f port because e0f is also assigned the role of intercluster.

    The intercluster LIF is assigned to an intercluster port; therefore, a non-modifiable failover group is created automatically, and contains all ports with the intercluster role on that node. Intercluster failover groups are node specific; therefore, if changes are required, they must be managed for each node because different nodes might use different ports for replication.

    cluster01::> network interface show -role intercluster –failover
             Logical         Home                  Failover        Failover
    Vserver  Interface       Node:Port             Group Usage     Group
    -------- --------------- --------------------- --------------- --------
    cluster01-01
             cluster01-01_icl01 cluster01-01:e0e   system-defined
                                 Failover Targets: cluster01-01:e0e,
                                                   cluster01-01:e0f
    cluster01-02
             cluster01-02_icl01 cluster01-02:e0e   system-defined
                                 Failover Targets: cluster01-02:e0e,
                                                   cluster01-02:e0f
  9. Verify that the intercluster LIFs were created properly by using the network interface show command.
    Example
    cluster01::> network interface show
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    cluster01
                cluster_mgmt up/up    192.168.0.xxx/24   cluster01-01  e0c     true
    cluster01-01
                cluster01-01_icl01
                             up/up    192.168.1.201/24   cluster01-01  e0e     true
                clus1        up/up    169.254.xx.xx/24   cluster01-01  e0a     true
                clus2        up/up    169.254.xx.xx/24   cluster01-01  e0b     true
                mgmt1        up/up    192.168.0.xxx/24   cluster01-01  e0c     true
    cluster01-02
                cluster01-02_icl01
                             up/up    192.168.1.202/24   cluster01-02  e0e     true
                clus1        up/up    169.254.xx.xx/24   cluster01-02  e0a     true
                clus2        up/up    169.254.xx.xx/24   cluster01-02  e0b     true
                mgmt1        up/up    192.168.0.xxx/24   cluster01-02  e0c     true
  10. Display routing groups by using the network routing-group show command with the -role intercluster parameter to determine whether the intercluster network needs intercluster routes.
    An intercluster routing group is created automatically for the intercluster LIFs.
    Example
    cluster01::> network routing-group show –role intercluster
              Routing
    Vserver   Group     Subnet          Role         Metric
    --------- --------- --------------- ------------ -------
    cluster01-01
              i192.168.1.0/24
                        192.168.1.0/24  intercluster 40
    cluster01-02
              i192.168.1.0/24
                        192.168.1.0/24  intercluster 40
  11. Display the routes in the cluster by using the network routing-group show command to determine whether intercluster routes are available or you must create them.
    Creating a route is required only if the intercluster addresses in both clusters are not on the same subnet and a specific route is needed for communication between the clusters.
    Example
    In this example, no intercluster routes are available.
    cluster01::> network routing-group route show
              Routing
    Vserver   Group     Destination     Gateway         Metric
    --------- --------- --------------- --------------- ------
    cluster01
              c192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     20
    cluster01-01
              n192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     10
    cluster01-02
              n192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     10
  12. If communication between intercluster LIFs in different clusters requires routing, create an intercluster route by using the network routing-groups route create command.
    The intercluster networks apply to each node; therefore, you must create an intercluster route on each node.
    Example
    In this example, 192.168.1.1 is the gateway address for the 192.168.1.0/24 network.
    Note: If the destination is specified as 0.0.0.0/0, then it becomes the default route for the intercluster network.
    cluster01::> network routing-groups route create -server cluster01-01 -routing-group i192.168.1.0/24 -destination 0.0.0.0/0 -gateway 192.168.1.1 -metric 40
    
    cluster01::> network routing-groups route create -server cluster01-02 -routing-group i192.168.1.0/24 -destination 0.0.0.0/0 -gateway 192.168.1.1 -metric 40
  13. Display the newly created routes by using the network routing-groups route show command to confirm that you created the routes correctly.
    Although the intercluster routes do not have an assigned role, they are assigned to the routing group i192.168.1.0/24, which is assigned the role of intercluster. These routes are only used for intercluster communication.
    Example
    cluster01::> network routing-group route show
              Routing
    Vserver   Group     Destination     Gateway         Metric
    --------- --------- --------------- --------------- ------
    cluster01
              c192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     20
    cluster01-01
              n192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     10
              i192.168.1.0/24
                        0.0.0.0/0       192.168.1.1     40
    cluster01-02
              n192.168.0.0/24
                        0.0.0.0/0       192.168.0.1     10
              i192.168.1.0/24
                        0.0.0.0/0       192.168.1.1     40
  14. Repeat these steps to configure intercluster networking in the other cluster.
  15. Verify that the ports have access to the proper subnets, VLANs, and so on.
    Dedicating ports for replication in one cluster does not require dedicating ports in all clusters; one cluster might use dedicated ports, while the other cluster shares data ports for intercluster replication.