Create Lif (network interface) (2023)

docs.netapp.com
On tap
report

13/04/2023 Associate

A LIF (Network Interface) is an IP address associated with a physical or logical port. In the event of a component failure, the LIF can fail or switch to another physical port, thus continuing to communicate with the network.

Before you begin

The underlying physical or logical network port must be configured as a management mode.
If you are planning to use the sub -mutual name to extract IP addresses and values of the network mask, under -network must exist.
Ziwang contains a pool of IP addresses belonging to the same # 3 -lags Network.de uses a system manager orcabinetOrder.
The mechanism for determining the type of traffic managed by the LIF has changed.For OTAP 9.5 and earlier, the LIFs used roles to determine the types of traffic with whom they will handle.Starting from ONTAP 9.6, the LIFS uses policy policies to determine the traffic types to handle.

About this task

You cannot assign NAS and SAN protocols to the same lifetime.
Supported protocols are SMB, NFS, Flexcache, ISCSI and FC; ISCSI and FC cannot be combined with other protocols. However, NAS and Ethernet SAN protocols can exist on the same physical port.
You can create the IPV4 and IPV6 LIF on the same network sport.
All name mapping and host name resolution services used by SVM (such as DNS, NIS, LDAP, and Active Directory) must have access to at least one LIF access to SVM data traffic.
Inter-node LIFs that handle traffic within the cluster should not be on the same subnet as LIFs that handle management traffic or LIFs that handle data traffic.
Creating a LIF that does not have effective error transfer targets can result in warning messages.
If you have a large number of lives in your cluster, you can check the life ability supported in your cluster:
- System Administrator: As of ONTAP 9.12.0, check the bandwidth on the network interface port.
- CLI: useShowing the network capacity of the surfaceCommand and LIF capability supported by each node through usageDetailed information depicting a network interface capacityCommand (at the level of advanced privileges).
As of Ontap 9.7, if there are other LIFs in the SVM in the same subnet, there is no need to specify the master port. ONTAP automatically selects a random port on the specified master node in other LIFs already configured in the same subnet.
As of ONTAP 9.4, FC-NVME is supported. To create an FC-NVME LIF, learn the following:
- The NVME protocol must support the FC adapter created by an elevator.
- FC-NVME can be the only data protocol for data LIFs.
Each storage virtual machine (SVM) that supports a SAN must be configured with a LIF that handles management traffic.
NVME lifs and name areas must be located on the same node.
Each SVM can be configured with only one NVME LIF to handle data traffic.
When using a -network to create a network interface, Ontap automatically selects the available IP address from the selected sub -mate and assigns it to the network interface.If there are more sub -marshes, you can change the sub -mushroom, but you cannot change the IP address.
When you create (add) an SVM to a network interface, you cannot specify an IP address within the range of an existing subnet. You are getting a subnet conflict error. This issue occurs in other network interface workflows, such as creating or modifying cross-cluster network interfaces in an SVM deployment or a cluster deployment.
Start with Ontap 9.10.1,Network interfaceThe CLI commands include-Ord-protocolNFS parameters via RDMA configuration.Starting from ONTAP 9.12.1, the system manager supports the creation of network interfaces for NFS via RDMA configuration.See for more informationConfiguring LIFS for NFS via RDMA.
Since ONTAP 9.11.1 ISCSI The Lif fault transfer function is available on all SAN ARRAY (ASA) platforms.
iSCSI LIF failover will be automatically enabled (failover rule set toThe only FSR partnerand the value of autogenic creation is set togenuine) On the newly created Isci LIF if there is no LIF in the stated SVM or if all the existing Iscsi Life in the stated SVM activates the ISCSI LIF.
If you upgrade to the ONTAP 9.11.1 or a higher version, the existing ISCSI LIF in SVM did not activate the IZCSI LIF error function using the same failure.disabled) Existing ISCSI LIF in SVM.
ASA platforma ISCSI LIF failover

From Ontap 9.12.0, the procedure you follow depends on which interface you use - System Manager or Cli:

System administrator

Use System Manager to add a network interface

tempo

selectNetwork > Overview > Network Interfaces.
choose.
Choose one of the following interface roles:
1. data
2. Cluster
3. SVM management
Select Protocol:
1. SMB/CIFS i NFS
2. iSCSI
3. Fc
4. NVMe/fiberkanal
5. NVME / TCP
Name the LIF or accept the name generated on the basis of your previous choices.
Choose one for family nodes or use a falling menu.
If at least one sub -mate is configured in IPSPACE on the selected SVM, a shower list will appear.
1. If you select a subnet, select it from the drop-down list.
2. If you continue without a subnet, the broadcast domain drop-down menu appears:
  1. Specify the IP address. If you are using an IP address, a warning message will appear.
  2. Specify the subnet mask.
Choose the primary connection from the broadcast domain, the car (recommended), or select one from the Drop -Down.controlcuker menu appears on the basis of selecting a Domain or floor broadcast.
Save the network interface.

Command line interface

Create LIFs using the CLI

tempo

Create LIFs:
```
网络接口创建-vserver _SVM_name_ -lif _lif_name_ -service-policy _service_policy_name_ -home-node _node_name_ -home-port port_name {-adresse _IP_address_ - netmaske _Netmask_value_ | -subnet-name _subnet_name_} -firewall- policy _policy_ -auto-revert {true|false}
```
- - Home nodeIs the node returned aliveRebuilding the network interfaceThe command is launched on the LIF.
  You can also use the -Auto -vet option to determine if the lif -a should automatically return to the master knock and the main connection.
- - The home portis the physical or logical port to which the LIF returns whenNetwork interface recoveryThe command is executed on the LIF.
- You can use the following command to determine the IP address-Addressi- a mesh maskSettings or you can assign from subnet-subnet_namePossibilities.
- When using a subnet to provide IP address and network coverage, if you use the Gateway Definition subnet, you automatically add a default access to the gateway when using the subnet to create the LIF.
- If you assign IP addresses manually (without subnetting) and have clients or domain controllers on different IP Undernets, you may need to configure a default DRUT for gateway.thisCreating a network routeThe manual contains information on creating static routing in SVM.
- - Automatic recoveryAllows you to specify if the data available is returned automatically to your primary node when you change the control base for management or when network connection is established.The default setting isInaccuratelyBut you can place it ongenuineIt depends on the rules of the network of your environment.
- - Service policyStarting with ONTAP 9.5, you can assign service rules to LIFs- Service policyPossibilities.
  When a service policy is specified for a LIF, the policy is used to build the default role, upgrade rules, and data protocol list for the LIF. In ONTAP 9.5, service policies are supported only for intercluster and BGP peering services. In ONTAP 9.6, you can create service rules for multiple data and management services.
- - Data protocolAllows you to create a LIF that supports FCP or NVME / FC protocols.This option is not required when creating IP LIF.
Optional: Assign an IPv6 address in the -Ddress option:
1. Use the show network NDP prefix command to see a list of RA prefixes learned on different interfaces.
  this hereNetwork NDP -Prefix screenThe command may be available at the advanced body level.
2. use the formatPrefix :: EidBuild an IPv6 address manually.
  prefixis a prefix learned on different interfaces.
  concludeidentity card, Choose a random 64-bit hexadecimal number.
LIF confirmation is usedA network interface displayOrder.
Can IP address configuration configuration be reached:

confirm…	use…
IPRCH ADDRESS	Mesh
IPv6 address	Network ping6

Example

The following command creates the LIF and specifies the IP address and value of the network mask, use-Addressi-Net maskParameter:

Mrežno sučelje Create -VServer vs1.example.com -lif Datalif1 -service -service -policy default -data -files -home -node node -4 -home -port e1c -address 192.0.2.0.2.145 -netmask 255.255.255.0 -auto - vraća istinito

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

Mrežno sučelje Create -vServer vs3.example.com -lif DataLif3 -Service-Policy Default-Data-Files -Home-Node-3 -Home-port E1c -subnet-Name Client1_Sub -UBUAUTO-REVERT TRUE

The following commands create the NVME/FC LIF and specifyNVME-FCData Protocol:

create network interface -vserver vs1.example.com -lif datalif1 -data-protocol nvme-fc -home-node node-4 -home-port 1c -address 192.0.2.145 -netmask 255.255.255.0 -auto-revert true

Only information

LIFE DEPARTS
Configuring LIFs for NFS via RDMA