Module 8

Logical Networking

NetApp Confidential 1

MODULE 8: LOGICAL NETWORKING

8-1 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Module Objectives

After this module, you should be able to:

 Create NAS data logical interfaces (LIFs)
 Create a LIF failover group
 Migrate and revert a NAS data LIF
 Configure DNS load balancing

NetApp Confidential 2

MODULE OBJECTIVES

8-2 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LIF Characteristics
 An IP address or World Wide Port Name (WWPN) is
associated with a LIF.
 One node-management LIF exists per node. It can fail over
to other data or node-management ports on the same
node.
 One cluster-management LIF exists per cluster. It can fail
over or migrate throughout the cluster.
 Two cluster LIFs exist per node. They can fail over or
migrate only within their node.
 Multiple data LIFs are allowed per data port.
– The are client-facing (NFS, CIFS, iSCSI, and Fibre Channel
access).
– NAS data LIFs can migrate or fail over throughout the cluster.

NetApp Confidential 3

LIF CHARACTERISTICS
Each logical interface (LIF) has an associated role and must be assigned to the correct type of network port.
Data LIFs can have a many-to-one relationship with network ports: Many data IP addresses can be assigned
to a single network port. If the port becomes overburdened, NAS data LIFs can be transparently migrated to
different ports or different nodes. Clients know the data LIF IP address but do not know which node or port is
hosting the LIF. If a NAS data LIF is migrated, the client might unknowingly be contacting a different node.
The NFS mountpoint or CIFS share is unchanged.
A node can have a maximum of 128 LIFs, regardless of the type of LIF.

8-3 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network interface show Command
1 of 2
cluster1::> net int show
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
cluster_mgmt up/up [Link]/24 cluster1-01 e0M true
cluster1-01
clus1 up/up [Link]/16 cluster1-01 e1a true
clus2 up/up [Link]/16 cluster1-01 e2a true
mgmt up/up [Link]/24 cluster1-01 e0a true
cluster1-02
clus1 up/up [Link]/16 cluster1-02 e1a true
clus2 up/up [Link]/16 cluster1-02 e2a true
mgmt up/up [Link]/24 cluster1-02 e0a true
vs7
vs7_lif1 up/up [Link]/24 cluster1-01 e3a true
vs7_lif2 up/up [Link]/24 cluster1-01 e3b false

NetApp Confidential 4

THE NETWORK INTERFACE SHOW COMMAND: 1 OF 2

LIF names must be unique within their scope. For data LIFs, the scope is a data virtual storage server
(Vserver). The scope of a cluster LIF or management LIF is limited to its node. Thus, the same name (for
example, mgmt1) can be used for all the nodes.

8-4 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network interface show Command
2 of 2
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
vs7
vs7_lif1 up/up [Link]/24 cluster1-01 e3a true
vs7_lif2 up/up [Link]/24 cluster1-01 e3b false
vs7_fclif1 up/up 20:0f:00:a0:98:13:d5:d4
cluster1-01 0c true
vs7_fclif2 up/up 20:10:00:a0:98:13:d5:d4
cluster1-01 0d true
vs7_fclif3 up/up 20:14:00:a0:98:13:d5:d4
cluster1-02 0c true
vs7_fclif4 up/up 20:12:00:a0:98:13:d5:d4
cluster1-02 0d true
13 entries were displayed.

NetApp Confidential 5

THE NETWORK INTERFACE SHOW COMMAND: 2 OF 2

Instead of IP addresses, FC LIFs use worldwide port names (WWPNs).

8-5 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Network Ports and Data LIFs
[Link] (vs1_d2)
[Link] (vs1_d1)
[Link] (vs2_d2)
[Link] (vs2_d1)
[Link] (vs2_d3)

21:00:00:2b:34:26:a6:54 (vs1_d4)
[Link] (vs1_d3)
[Link] (vs3_d1)

e0c e0d e0c 0f

node1 node2

NetApp Confidential 6

NETWORK PORTS AND DATA LIFS

In the environment that is shown on this slide, each of the nodes contains two data network ports. Network
port node2 has three data LIFs that are assigned to one port and two on the other port. This slide shows the
many-to-one relationship between LIFs and network ports. The data LIF name is in parentheses after each
network address.
In a NAS environment, the name is not the actual host name that is associated with the IP address. The name
is an internal name that can be used as the host name for the IP address in the DNS. In a NAS environment,
all these IP addresses can share one host name, such that a DNS round robin is used and picks an IP address
every time that the host name is used; for example, for an NFS mount command.
This slide shows how an environment can randomly distribute client connections across a cluster while the
cluster looks to every user and every client as if there is only one storage host.

8-6 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LIF Roles and Compatible Ports

LIF Roles Compatible Port Roles

Cluster Cluster
Data Data
Node-management Node-management or
Data
Cluster-management Node-management or
Data
Intercluster Intercluster or
Data

NetApp Confidential 7

LIF ROLES AND COMPATIBLE PORTS

8-7 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LIF Static Routes
 Are defined paths between LIFs and specific
destination IP addresses through gateways
 Can improve the efficiency of network traffic that
travels through complicated networks
 Have preferences that are associated with them:
When multiple routes are available, the “metric”
specifies the preference order of the route to use.
 Are defined within “routing groups”
 Are created or chosen automatically when a LIF
is created

NetApp Confidential 8

LIF STATIC ROUTES

You can control how LIFs in a Vserver use your network for outbound traffic by configuring routing groups
and static routes. A set of common routes are grouped in a routing group that simplifies the administration of
routes.
 A routing group is a routing table in which each LIF is associated with one routing group and uses only
the routes of that group. Multiple LIFs can share a routing group.
NOTE: If, for purposes of backward compatibility, you want one route per LIF, you can create a separate
routing group for each LIF.
 A static route is a defined route between a LIF and a specific destination IP address. The route can use a
gateway IP address.
Routing groups are created automatically as new LIFs are created, unless a routing group covers that port and
role or network combination.
The node-management LIFs on each node have static routes that are automatically set up for them through the
same default gateway.
If more than one static route is defined for a LIF, each static route has a “metric” value. The administrator
uses the metric values to configure routes so that one is preferred over another. The lower the metric value,
the more preferred the route is. The metric value for a node management LIF is 10. When routes are created
for data LIFs, if no metric is defined, the default value is 20.

8-8 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network routing-groups show
Command 1 of 2
cluster1::> network routing-groups show
Routing
Vserver Group Subnet Role Metric
--------- --------- --------------- ------------ -------
cluster1
c192.168.81.0/24
[Link]/24 cluster-mgmt 20
cluster1-01
c169.254.0.0/16
[Link]/16 cluster 30
i192.168.81.0/24
[Link]/24 intercluster 40
n192.168.81.0/24
[Link]/24 node-mgmt 10

NetApp Confidential 9

THE NETWORK ROUTING-GROUPS SHOW COMMAND: 1 OF 2

8-9 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network routing-groups show
Command 2 of 2
Routing
Vserver Group Subnet Role Metric
--------- --------- --------------- ------------ -------
cluster1-02
c169.254.0.0/16
[Link]/16 cluster 30
i192.168.81.0/24
[Link]/24 intercluster 40
n192.168.81.0/24
[Link]/24 node-mgmt 10
vs1
d192.168.81.0/24
[Link]/24 data 20
vs2
d192.168.81.0/24
[Link]/24 data 20
9 entries were displayed.

NetApp Confidential 10

THE NETWORK ROUTING-GROUPS SHOW COMMAND: 2 OF 2

8-10 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network routing-groups
route show Command
cluster1::> network routing-groups route show
Routing
Vserver Group Destination Gateway Metric
--------- --------- --------------- --------------- ------
cluster1
c192.168.81.0/24
[Link]/0 [Link] 20
cluster1-01
n192.168.81.0/24
[Link]/0 [Link] 10
cluster1-02
n192.168.81.0/24
[Link]/0 [Link] 10
vs1
d192.168.81.0/24
[Link]/0 [Link] 20
vs2
...
5 entries were displayed.

NetApp Confidential 11

THE NETWORK ROUTING-GROUPS ROUTE SHOW COMMAND

As with the network interface show output command, node-management LIFs have a server that
is the node itself. The data LIFs are associated with a data Vserver that the data LIFs are grouped under.

8-11 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 NAS Data LIF Failover and Migration

 “LIF failover” means automatic failover that

occurs because of an outage or reboot.
 “LIF migrate” means manual migration: The
node is not rebooted during manual migration.
 “LIF revert” means manually or automatically
sending a LIF back to its home (node and
port).
 LIF failover is controlled by the failover group.

NetApp Confidential 12

NAS DATA LIF FAILOVER AND MIGRATION

Why migrate a NAS data LIF? It might be needed for troubleshooting a faulty port or to offload a node whose
data network ports are being saturated with other traffic. The LIF fails over if its current node is rebooted.
Unlike storage failover (SFO), LIF failover or migration does not cause a reboot of the node from which the
LIF is migrating. Also unlike SFO, LIFs can migrate to any node in the cluster, not just within the high-
availability (HA) pair. After a LIF is migrated, the LIF can remain on the new node for as long as the
administrator wants.

8-12 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 NAS Data LIF Failover and Migration
Limits
 Node-management LIFs cannot fail over or
migrate to a port on a different node.
 Cluster-management LIFs and NAS data LIFs
can fail over and migrate across ports and
nodes.
 Cluster LIFs can fail over and migrate only
across ports on the same node.
 Data LIFs are bound to a Vserver and do not
fail over or migrate between Vservers.
 SAN data LIFs never fail over or migrate.

NetApp Confidential 13

NAS DATA LIF FAILOVER AND MIGRATION LIMITS

Data LIFs aren’t permanently tied to their home ports. However, the port to which a LIF is migrating is tied to
a node. This example shows the line between the physical and the logical. Also, a port has a node Vserver
scope; a data LIF has a data Vserver scope.

8-13 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LIF Failover Groups

data1
e0c e0d e0c e0d e0c e0d e0c e0d

NetApp Confidential 14

LIF FAILOVER GROUPS

“LIF failover” means the automatic migration of a NAS data LIF in response to a link failure on the LIF’s
current network port. When such a port failure is detected, the LIF is migrated to a working port. A failover
group contains a set of network ports (physical, VLANs, and interface groups) on one or more nodes. A LIF
can subscribe to a failover group. The network ports that are present in the failover group define the failover
targets for the LIF. You can manage failover groups by adding ports to them, removing ports from them,
renaming them, and displaying information about them.

8-14 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Types of Failover Groups

 System-defined
 User-defined
 Cluster-wide

NetApp Confidential 15

TYPES OF FAILOVER GROUPS

Failover groups for LIFs can be system-defined or user-defined. Additionally, one failover group that is called
“cluster-wide” is maintained automatically.
Failover groups are of the following types:
 System-defined failover groups: These failover groups automatically manage LIF failover targets on a
per-LIF basis and contain data ports from a maximum of two nodes. The data ports include all the data
ports on the home node and all the data ports on another node in the cluster for redundancy.
 User-defined failover groups: These customized failover groups can be created when the system-defined
failover groups do not meet your requirements. For example, you can create a failover group that consists
of 10-GbE ports and enables LIFs to fail over only to the high-bandwidth ports.
 The cluster-wide failover group: This failover group consists of all the data ports in the cluster and
defines the default failover group for the cluster management LIF.

8-15 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 LIF Roles and Failover Groups
LIF Roles Failover Group Failover Target Role Failover Target Nodes

Cluster System-defined (default) Cluster Home node

System-defined (default) Node-management Home node

Node-
management Node-management or
User-defined Home node
data
Cluster-wide (default) Any node
Cluster- Data or
System-defined
management Node-management Home node or any node
User-defined

System-defined (default)
Data Data Home node or any node
User-defined

System-defined (default) Intercluster

Intercluster Home node
User-defined Intercluster or data

NetApp Confidential 16

LIF ROLES AND FAILOVER GROUPS

8-16 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Failover Policies

 nextavail
 priority
 disabled

NOTE: Use -failover-policy priority and a user-defined

failover group to control the order of failover within a failover group.

NetApp Confidential 17

FAILOVER POLICIES
nextavail (default): Enables a LIF to fail over to the next available port, preferring a port on the current node.
In some instances, a LIF configured with the nextavail failover policy selects a failover port on a remote node,
even though a failover port is available on the local node. No outages will be seen in the cluster, because the
LIFs continue to be hosted on valid failover ports.
priority: Given the list of failover targets, if the home port goes down then select the next port from the list in
order, always starting with the first port in the list.
disabled: Disables (prevents) a LIF from failing over.

8-17 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Creating and Deleting Failover Groups
 Creating or adding a port to a failover group:
cluster1::> net int failover-groups create –failover-group
customfailover1 –node cluster1-02 –port e0d

 Renaming a failover group:

cluster1::> net int failover-groups rename –failover-group
customfailover1 –new-name prodfailover1

 Removing a port from a failover group:

cluster1::> net int failover-groups delete –failover-group
customfailover1 –node cluster1-02 –port e0d

 Deleting a failover group:

cluster1::> net int failover-groups delete –failover-group
customfailover1 *

NetApp Confidential 18

CREATING AND DELETING FAILOVER GROUPS

8-18 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Enabling and Disabling Failover of a LIF

 Enable a LIF to use a user-defined failover

group:
cluster1::> net int modify –vserver vs2 –lif data1
-failover-policy nextavail –failover-group customfailover1

 Enable a LIF to use a system-defined failover

group:
cluster1::> net int modify –vserver vs2 –lif data1
-failover-policy nextavail –failover-group system-defined

 Disable a LIF from failing over:

cluster1::> net int modify –vserver vs2 –lif data1
–failover-policy disabled

NetApp Confidential 19

ENABLING AND DISABLING FAILOVER OF A LIF

The values of the following parameters of the network interface modify command together
determine the failover behavior of LIFs:
 -failover-policy: Enables you to specify the order in which the network ports are chosen during a
LIF failover or enables you to prevent a LIF from failing over. This parameter can have one of the
following values:
– nextavail (default): Enables a LIF to fail over to the next available port, preferring a port on the
current node. In some instances, a LIF configured with the nextavail failover policy selects a
failover port on a remote node, even though a failover port is available on the local node. No outages
will be seen in the cluster as the LIFs continue to be hosted on valid failover ports.
– priority: Enables a LIF to fail over to the first available port specified in the user-defined failover
group (failover targets can be shown with the network interface show -failover
command).
– disabled: Disables a LIF from failing over.
 -failover-group: Specifies the failover behavior configured for the LIF. The value can be set to:
– system-defined: specifies that the LIF uses the implicit system-defined failover behavior for the
LIF's role
– [empty]: specifies that the LIF is not configured to use a failover group
– [user-defined failover group]: specifies that the LIF is configured to fail over to any
available port present in the failover group

8-19 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network interface show
Command
cluster1::> net int show -vserver vs2 -lif vs2_lif1
Vserver Name: vs2
Logical Interface Name: vs2_lif1
Role: data
Data Protocol: nfs, cifs
Home Node: cluster1-02
Home Port: e0d
Current Node: cluster1-02
Current Port: e0d
Operational Status: up
Extended Status: -
Is Home: true
Network Address: [Link]
Netmask: [Link]
IPv4 Link Local: -
Bits in the Netmask: 24
Routing Group Name: d192.168.81.0/24
Administrative Status: up
Failover Policy: nextavail
Firewall Policy: data
Auto Revert: false
Fully Qualified DNS Zone Name: none
DNS Query Listen Enable: false
Failover Group Name: customfailover1

NetApp Confidential 20

THE NETWORK INTERFACE SHOW COMMAND

8-20 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 The network interface failover-
group show Command
cluster1::> net int failover-groups show
(network interface failover-groups show)
Failover
Group Node Port
------------------- ----------------- ----------
clusterwide
cluster1-02 e0c
cluster1-02 e0d
cluster1-02 e0e
cluster1-01 a0a
cluster1-01 e0c
customfailover1
cluster1-02 e0c
cluster1-01 e0c

NetApp Confidential 21

THE NETWORK INTERFACE FAILOVER-GROUP SHOW COMMAND

8-21 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 NAS Load Balancing

 DNS load balancing

– NFSv3, NFSv4, NFSv4.1
– SMB 1.0, SMB 2.0
 Automatic LIF rebalancing
– NFSv3 only

NetApp Confidential 22

NAS LOAD BALANCING

With DNS load balancing enabled, a storage administrator can choose to enable the built-in load balancer to
balance the client LIF network access on the basis of the load of the cluster. Supported NAS protocols include
NFSv3, NFSv4, NFSv4.1, CIFS, and SMB 2.0.
In automatic LIF rebalancing, LIFs are automatically migrated to a less-utilized port, based on the configured
failover rules. Automatic LIF rebalancing allows even distribution of the current load. NFSv3 is the only
supported protocol.

8-22 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 DNS Load-Balancing Characteristics
 Uses internal “DNS zones” that contain multiple data
IP addresses (data LIFs):
– The actual data LIF that is used for an NFS mount is
chosen at NFS mount time.
– NAS data LIFs can be automatically migrated among
nodes to maintain a balanced load.
 Is based on LIF weights:
Weight can be manually or automatically set (based on the
current load in the cluster).
 Provides balanced cluster-wide data LIFs

NetApp Confidential 23

DNS LOAD-BALANCING CHARACTERISTICS

The DNS server resolves names to LIFs based on the weight of a LIF. A Vserver can be associated with a
DNS load-balancing zone, and LIFs can be created or modified to be associated with a specific DNS zone. A
fully-qualified domain name can be added to a LIF to create a DNS load-balancing zone by specifying a
dns-zone parameter in the network interface create command.
Two methods can be used to specify the weight of a LIF: The storage administrator can specify a LIF weight,
or the LIF weight can be generated based on the load of the cluster. Ultimately, this feature helps to balance
the overall use of the cluster. This feature does not increase the performance of any one individual node;
rather, this feature guarantees that each node is used more evenly. The result is better performance use from
the entire cluster.
DNS load balancing also improves the simplicity of maintaining the cluster. Instead of manually determining
which LIFs are used when mounting a specific global namespace, the administrator can let the system
dynamically decide which LIF is the most appropriate. And after a LIF is chosen, that LIF can be migrated to
a different node automatically to guarantee that the network load remains balanced throughout the cluster.

8-23 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 DNS Load-Balancing Commands
 Assigning a weight to a LIF by using the network
interface modify command:
cluster1::> net int modify –vserver vs2 –lif data1 –lb-weight 7

 Creating a DNS load-balancing zone by using the

network interface create command:
cluster1::> net int create –vserver vs2 –lif data1 -role data -home-
node cluster1-01 -home-port e0c -address [Link] -netmask
[Link] -dns-zone [Link]

 Adding a LIF to a load-balancing zone by using the

network interface modify command:
cluster1::> net int modify –vserver vs2 –lif data2 –dns-zone
[Link]

NetApp Confidential 24

DNS LOAD-BALANCING COMMANDS

See KB article 1013801 for step-by-step configuration information.

8-24 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Automatic LIF Rebalancing
 LIFs are automatically migrated to a less-utilized port.
 Migration allows even distribution of the current load.
 LIFs are migrated based on the weights.
 Automatic LIF rebalancing is available only under the
advanced privilege level of operation.

NetApp Confidential 25

AUTOMATIC LIF REBALANCING

In automatic LIF rebalancing, LIFs are migrated based on the weights assigned to the LIFs.
When new NICs are added to the cluster, these network ports are automatically included when load is
calculated dynamically the next time. You must ensure that the new network ports are a part of the failover
group to which the LIFs belong.
Automatic LIF rebalancing is available only under advanced privilege level of operation.

8-25 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Automatic LIF Rebalancing Commands

 Enabling automatic LIF rebalancing by using

the network interface modify
command:
cluster1::*> net int modify –vserver vs2 –lif data1 –failover-
policy priority –failover-group failover-group_2 –allow-lb-
migrate true

 Enabling automatic LIF rebalancing on

multiple LIFs (data1, data2, data3) by using
the network interface modify command:
cluster1::*> net int modify –vserver vs2 –lif data1..data3
–failover-policy priority –failover-group failover-group_2
–allow-lb-migrate true

NetApp Confidential 26

AUTOMATIC LIF REBALANCING COMMANDS

Because automatic LIF rebalancing is disabled for CIFS, automatic LIF rebalancing should not be enabled on
the DNS load-balancing zone that is configured for CIFS connections.

8-26 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Verifying the LIF Rebalancing Setting: The
network interface show Command
cluster1::*> network interface show –lif data1 –instance

Vserver Name: vs2

Logical Interface Name: data1
Role: data
...
Auto Revert: -
Sticky Flag: -
Fully Qualified DNS Zone Name: none
DNS Query Listen Enable: false
Load Balancing Migrate Allowed: true
Load Balanced Weight: load
Failover Group Name: failover-group_2
FCP WWPN: -
Address family: ipv4
Comment: -

NetApp Confidential 27

VERIFYING THE LIF REBALANCING SETTING:

THE NETWORK INTERFACE SHOW COMMAND

8-27 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Module Summary

Now that you have completed this module, you

should be able to:
 Create NAS data LIFs
 Create a LIF failover group
 Migrate and revert a NAS data LIF
 Configure DNS load balancing

NetApp Confidential 28

MODULE SUMMARY

8-28 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
 Exercise
Module 8: Logical Networking
Time Estimate: 45 minutes

NetApp Confidential 29

EXERCISE
Please refer to your exercise guide.

8-29 Clustered Data ONTAP Administration: Logical Networking

© 2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.