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

Creating intercluster LIFs that use dedicated ports involves creating a failover group for the dedicated ports and assigning LIFs to those ports. In this procedure, a two-node cluster exists in which each node has two data ports that you have added, e0e and e0f. These ports are ones you will dedicate for intercluster replication and currently are in the default IPspace. These ports will be grouped together as targets for the intercluster LIFs you are configuring. You must configure intercluster LIFs on the peer cluster before you can create cluster peer relationships. In your own environment, you would replace the ports, networks, IP addresses, subnet masks, and subnets with those specific to your environment.

Steps

  1. List the ports in the cluster by using network port show command.
    Example
    cluster01::> network port show
                                                                 Speed (Mbps)
    Node   Port      IPspace      Broadcast Domain Link   MTU    Admin/Oper
    ------ --------- ------------ ---------------- ----- ------- ------------
    cluster01-01
           e0a       Cluster      Cluster          up       1500  auto/1000
           e0b       Cluster      Cluster          up       1500  auto/1000
           e0c       Default      Default          up       1500  auto/1000
           e0d       Default      Default          up       1500  auto/1000
           e0e       Default      Default          up       1500  auto/1000
           e0f       Default      Default          up       1500  auto/1000
    cluster01-02
           e0a       Cluster      Cluster          up       1500  auto/1000
           e0b       Cluster      Cluster          up       1500  auto/1000
           e0c       Default      Default          up       1500  auto/1000
           e0d       Default      Default          up       1500  auto/1000
           e0e       Default      Default          up       1500  auto/1000
           e0f       Default      Default          up       1500  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
    Ports e0e and e0f do not appear in the following output; therefore, they do not have any LIFs located on them:
    cluster01::> network interface show -fields home-port,curr-port
    vserver lif                  home-port curr-port
    ------- -------------------- --------- ---------
    Cluster cluster01-01_clus1   e0a       e0a
    Cluster cluster01-01_clus2   e0b       e0b
    Cluster cluster01-02_clus1   e0a       e0a
    Cluster cluster01-02_clus2   e0b       e0b
    cluster01
            cluster_mgmt         e0c       e0c
    cluster01
            cluster01-01_mgmt1   e0c       e0c
    cluster01
            cluster01-02_mgmt1   e0c       e0c
    
  3. If a LIF is using a port that you want dedicated to intercluster connectivity, migrate the LIF to a different port.
    1. Migrate the LIF to another port by using the network interface migrate command.
      Example
      The following example assumes that the data LIF named cluster01_data01 uses port e0e and you want only an intercluster LIF to use that port:
      cluster01::> network interface migrate -vserver cluster01
      -lif cluster01_data01 -dest-node cluster01-01 -dest-port e0d
    2. You might need to modify the migrated LIF home port to reflect the new port where the LIF should reside by using the network interface modify command:
      Example
      cluster01::> network interface modify -vserver cluster01
      -lif cluster01_data01 -home-node cluster01-01 -home-port e0d
  4. Group the ports that you will use for the intercluster LIFs by using the network interface failover-groups create command.
    Example
    cluster01::> network interface failover-groups create -vserver cluster01 
    -failover-group intercluster01 -targets cluster01-01:e0e,cluster01-01:e0f,
    cluster01-02:e0e,cluster01-02:e0f
  5. Display the failover-group that you created by using the network interface failover-groups show command.
    Example
    cluster01::> network interface failover-groups show
                                      Failover
    Vserver          Group            Targets
    ---------------- ---------------- --------------------------------------------
    Cluster
                     Cluster
                                      cluster01-01:e0a, cluster01-01:e0b,
                                      cluster01-02:e0a, cluster01-02:e0b
    cluster01
                     Default
                                      cluster01-01:e0c, cluster01-01:e0d,
                                      cluster01-02:e0c, cluster01-02:e0d,
                                      cluster01-01:e0e, cluster01-01:e0f
                                      cluster01-02:e0e, cluster01-02:e0f
                     intercluster01
                                      cluster01-01:e0e, cluster01-01:e0f
                                      cluster01-02:e0e, cluster01-02:e0f
  6. Create an intercluster LIF on the admin SVM cluster01 by using the network interface create command.
    Example
    This example uses the LIF naming convention adminSVMname_icl# for the intercluster LIF:
    cluster01::> network interface create -vserver cluster01 -lif cluster01_icl01 -role intercluster -home-node cluster01-01 -home-port e0e 
    -address 192.168.1.201 -netmask 255.255.255.0 -failover-group intercluster01
    
    cluster01::> network interface create -vserver cluster01 -lif cluster01_icl02 -role intercluster -home-node cluster01-02 -home-port e0e 
    -address 192.168.1.202 -netmask 255.255.255.0 -failover-group intercluster01
    
  7. 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
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    Cluster
                cluster01-01_clus_1 
                             up/up    192.168.0.xxx/24   cluster01-01  e0a     true
                cluster01-01_clus_2 
                             up/up    192.168.0.xxx/24   cluster01-01  e0b     true
                cluster01-02_clus_1 
                             up/up    192.168.0.xxx/24   cluster01-01  e0a     true
                cluster01-02_clus_2 
                             up/up    192.168.0.xxx/24   cluster01-01  e0b     true
    cluster01
                cluster_mgmt up/up    192.168.0.xxx/24   cluster01-01  e0c     true
                cluster01_icl01
                             up/up    192.168.1.201/24   cluster01-01  e0e     true
                cluster01_icl02
                             up/up    192.168.1.202/24   cluster01-02  e0e     true
                cluster01-01_mgmt1
                             up/up    192.168.0.xxx/24   cluster01-01  e0c     true
                cluster01-02_mgmt1        
                             up/up    192.168.0.xxx/24   cluster01-02  e0c     true
    
  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.
    cluster01::> network interface show -role intercluster –failover
             Logical         Home                  Failover        Failover
    Vserver  Interface       Node:Port             Policy          Group
    -------- --------------- --------------------- --------------- --------
    cluster01-01
             cluster01-01_icl01 cluster01-01:e0e   local-only      intercluster01
                                Failover Targets:  cluster01-01:e0e,
                                                   cluster01-01:e0f
             cluster01-01_icl02 cluster01-02:e0e   local-only      intercluster01
                                Failover Targets:  cluster01-02:e0e,
                                                   cluster01-02:e0f
  9. Display the routes in the cluster by using the network route 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 route show
    Vserver   Destination     Gateway         Metric
    --------- --------------- --------------- ------
    Cluster
              0.0.0.0/0       192.168.0.1     20
    cluster01
              0.0.0.0/0       192.168.0.1     10
    
  10. If communication between intercluster LIFs in different clusters requires routing, create an intercluster route by using the network route create command.
    The gateway of the new route should be on the same subnet as the intercluster LIF.
    Example
    In this example, 192.168.1.1 is the gateway address for the 192.168.1.0/24 network. If the destination is specified as 0.0.0.0/0, then it becomes a default route for the intercluster network.
    cluster01::> network route create -vserver cluster01 
    -destination 0.0.0.0/0 -gateway 192.168.1.1 -metric 40
    
  11. Verify that you created the routes correctly by using the network route show command.
    Example
    cluster01::> network route show
    Vserver   Destination     Gateway         Metric
    --------- --------------- --------------- ------
    Cluster
              0.0.0.0/0       192.168.0.1     20
    cluster01
              0.0.0.0/0       192.168.0.1     10
              0.0.0.0/0       192.168.1.1     40
    
  12. Repeat these steps to configure intercluster networking in the peer cluster.
  13. 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.