Now we are going to talk about Logical InterFaces or Lifs and their characteristics.
Roles will vary depending on the type/quantity of additional interface cards installed. Before creating/joining the cluster, modify the network port roles to match the desired configuration.
Node management lif
The lif used by administrators to connect to and manage a node. These ports can be VLAN-tagged virtual ports where the underlying physical port is used for other traffic. The default port for node management differs depending on hardware platform. Some platforms have a dedicated management port (e0M). The role of such a port cannot be changed, and these ports cannot be used for data traffic.
The lif used for intracluster traffic only. By default, each node has two cluster lifs on 10-GbE ports enabled for jumbo frames.
In some cases, nodes on FAS22xx systems will be configured with a single 10-GbE cluster port.
The lif used for data traffic. These lips are accessed by NFS, CIFS, FC, and iSCSI clients for data requests. Each node has a minimum of one data lif.
You can create VLANs and interface groups on physical ports. VLANs and interface groups have the data role by default, and the role cannot be modified.
The ports used for cross-cluster communication. An intercluster lif should be routable to another intercluster lif or the data lif of another cluster. Intercluster lifs can be on physical ports or virtual ports.
During the configuration of a cluster, default roles are assigned to each network port. The network port for each role varies depending on the platform. You can modify these assignments later, depending on your needs.
To modify a port, in most cases it’s useful to bring the port first down.