Table of ContentsView in Frames

Creating a LIF

A LIF is an IP address associated with a physical port. If there is a component failure, a LIF can fail over to or be migrated to a different physical port, thereby continuing to communicate with the cluster.

Before you begin

About this task

Steps

  1. Create a LIF using the network interface create command.
    Example

    The following command creates a LIF and specifies the IP address and network mask values using the -address and -netmask parameters:

    cluster1::> network interface create -vserver vs1 -lif datalif1 -role data -data-protocol cifs,nfs -home-node node-4 -home-port e1c -address 192.0.2.145 -netmask 255.255.255.0 -firewall-policy data -auto-revert true

    The following command creates a LIF and assigns IP address and network mask values from the specified subnet (named client1_sub):

    cluster1::> network interface create -vserver vs3 -lif datalif3 -role data -data-protocol cifs,nfs -home-node node-3 -home-port e1c -subnet-name client1_sub -firewall-policy data -auto-revert true
  2. Optional: If you want to assign an IPv6 address in the -address option:
    1. Use the ndp -p command to view the list of RA prefixes learned on various interfaces.
      The ndp -p command is available from the nodeshell.
    2. Use the format prefix::id to construct the IPv6 address manually.
      prefix is the prefix learned on various interfaces.
      For deriving the id, choose a random 64-bit hexadecimal number.
  3. Verify that the LIF was created successfully by using the network interface show command.
    Example

    The following command shows all the LIFs in cluster1. Data LIFs datalif1 and datalif3 are configured with IPv4 addresses, and datalif4 is configured with an IPv6 address:

    cluster1::> network interface show
    
                Logical    Status     Network          Current      Current Is
    Vserver     Interface  Admin/Oper Address/Mask     Node         Port    Home
    ----------- ---------- ---------- ---------------- ------------ ------- ----
    cluster1
                cluster_mgmt up/up    192.0.2.3/24     node-1       e1a     true
    node-1
                clus1        up/up    192.0.2.12/24    node-1       e0a     true
                clus2        up/up    192.0.2.13/24    node-1       e0b     true
                mgmt1        up/up    192.0.2.68/24    node-1       e1a     true
    node-2
                clus1        up/up    192.0.2.14/24    node-2       e0a     true
                clus2        up/up    192.0.2.15/24    node-2       e0b     true
                mgmt1        up/up    192.0.2.69/24    node-2       e1a     true
    node-3
                clus1        up/up    192.0.2.17/24    node-3       e0a     true
                clus2        up/up    192.0.2.18/24    node-3       e0b     true
                mgmt1        up/up    192.0.2.68/24    node-3       e1a     true
    node-4
                clus1        up/up    192.0.2.20/24    node-4       e0a     true
                clus2        up/up    192.0.2.21/24    node-4       e0b     true
                mgmt1        up/up    192.0.2.70/24    node-4       e1a     true
    vs1
                datalif1     up/down  192.0.2.145/30   node-4       e1c     true
    vs3
                datalif3     up/up    192.0.2.146/30   node-3       e0c     true
                datalif4     up/up    2001::2/64       node-3       e0c     true
    16 entries were displayed.
    
  4. Verify that the configured IP address is reachable:
    To verify an... Use...
    IPv4 address network ping
    IPv6 address network ping6
    Example

    The following command verifies that the IPv4 address on datalif1 is accessible:

    cluster1::> network ping -node node-1 -destination 192.0.2.145
    192.0.2.145 is alive