Table of ContentsView in Frames

Configuring intercluster LIFs to share data ports

Configuring intercluster LIFs to share data ports enables you to use existing data ports to create intercluster networks for cluster peer relationships. Sharing data ports reduces the number of ports you might need for intercluster networking.

About this task

Creating intercluster LIFs that share data ports involves assigning LIFs to existing data ports. In this procedure, a two-node cluster exists in which each node has two data ports, e0c and e0d, and these data ports are in the default IPspace. These are the two data ports that are shared for intercluster replication. You must configure intercluster LIFs on the peer cluster before you can create cluster peer relationships. In your own environment, you 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 the 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
    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
    
  2. 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 e0c -address 192.168.1.201 -netmask 255.255.255.0 
    
    cluster01::> network interface create -vserver cluster01 -lif cluster01_icl02 -role intercluster 
    -home-node cluster01-02 -home-port e0c -address 192.168.1.202 -netmask 255.255.255.0 
    
  3. Verify that the intercluster LIFs were created properly by using the network interface show command with the -role intercluster parameter:
    Example
    cluster01::> network interface show –role intercluster
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    cluster01
                cluster01_icl01
                           up/up      192.168.1.201/24   cluster01-01  e0c     true
                cluster01_icl02
                           up/up      192.168.1.202/24   cluster01-02  e0c     true
  4. Verify that the intercluster LIFs are configured to be redundant by using the network interface show command with the -role intercluster and -failover parameters.
    Example
    The LIFs in this example are assigned the e0c port on each node. If the e0c port fails, the LIF can fail over to the e0d port.
    cluster01::> network interface show -role intercluster –failover
             Logical         Home                  Failover        Failover
    Vserver  Interface       Node:Port             Policy          Group
    -------- --------------- --------------------- --------------- --------
    cluster01
             cluster01_icl01 cluster01-01:e0c   local-only      192.168.1.201/24
                                Failover Targets: cluster01-01:e0c,
                                                  cluster01-01:e0d
             cluster01_icl02 cluster01-02:e0c   local-only      192.168.1.201/24
                                Failover Targets: cluster01-02:e0c,
                                                  cluster01-02:e0d
                            
  5. 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
    
  6. 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
    
  7. 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
    
  8. Repeat these steps on the cluster to which you want to connect.