NetApp Data ONTAP 8.

2015-07-19 16:56:53
http://www.storageonline.com.cn/storage/nas/netapp-clustered-data-ontap-8-3-network-management-guide/

Data ONTAP 8.2 7-mode NetApp Data ONTAP 8.2 7-Mode
NetApp Data ONTAP 8.3 NetApp Data ONTAP 8.3 -
NetApp Data ONTAP 8.3

Data ONTAP 8.3

Data ONTAP 8.2 7-mode LIF LIF
Data ONTAP 8.2 c-mode

NetApp Data ONTAP 8.3 4 Data ONTAP 8.3

Cluster InterconnectManagement NetworkData Network (Ethernet, FC, or Converged)

2 2

Two cluster connections to each node are typically required for redundancy and improved cluster traffic flow. For the larger
clusters that use higher-end platforms (FAS8040, FAS8060, and FAS8080) that are running clustered Data ONTAP 8.2.1,
four cluster interconnects are the default. Optionally, a FAS8080 can be configured to use 6 cluster interconnect ports with
expansion 10-gigabit Ethernet network interface cards (10- GbE NICs).

For proper configuration of the NetApp CN1601 and CN1610 switches, refer to the CN1601 and CN1610 Switch Setup
and Configuration Guide.

Ethernet port : 1-Gb or 10-Gb Ethernet (10-GbE) ports that can be used in NFS, CIFS, and iSCSI environments

FC port : 4-Gbps, 8-Gbps, or 16-Gbps port that can be used as a target in FC SAN environment. It can be
configured as an initiator for disk shelves or tape drives.

Unified Target Adapter (UTA) port : 10-GbE port that can be used in NFS, CIFS, iSCSI and FCoE environments

Unified Target Adapter 2 (UTA2) port : Configured as either a 10-GbE Ethernet or 16-Gbps FC port 10-Gb
ports can be used in NFS, CIFS, iSCSI, and FCoE environments 16-Gbps FC ports can be used as targets in FC
SAN environments

Interface group : An interface group implements link aggregation by providing a mechanism to group together
multiple network interfaces (links) into one logical interface (aggregate). After an interface group is created, it is
indistinguishable from a physical network interface.

VLAN : Traffic from multiple VLAN s can traverse a link that interconnects two switches by using VLAN tagging.

Logical interfaces (LIFs):for clustered Data ONTAP only

Data ONTAP 7-mode NetApp Data ONTAP 8.2 7-Mode

e FC (slot) 0
e0b 3a FC e3a/3a
UTA FC )

Ethernet ports are named e<location><letter>

e0a is the first port on the controllers motherboard

 e3a is a port on a card in slot 3

FC ports are named <location><letter>

0a is the first port on the controllers motherboard

3a is a port on a card in slot 3

UTA ports have both an Ethernet name and an FC name e<location><letter>/<location><letter>

e0e/0e is the first port on the controllers motherboard

e3a/3a is a port on a card in slot 3

Show commands list only by FC label name (even in Ethernet mode)

FAS8040 and FAS8060

Cluster ed Data ONTAP configuration:

4 x 10-GbE ports for cluster interconnects Supported: two cluster interconnects (e0a and e0c) and two data (e0b
and e0d) Recommended: four cluster interconnects (switched clusters only)

4 x Unified Target Adapter 2 (UTA2) ports can be configured as either 10-GbE or 16-Gbps FC for data Can only
be used for data (not cluster interconnects) Port pairs must be set the same:

4 x GbE ports for data

1 x management port (default for node-management network) e0M runs at GbE SP runs at 10/100

1 x private management port that is used as an alternate control path (ACP) for SAS shelves
 1 x console port (can be configured for SP) To toggle from serial console into SP, use Ctrl-G. To toggle back,
use Ctrl-D.

Data ONTAP 8.3 4 e0a,e0b e0c e0d

Interface Groups
Data ONTAP 7-mode NAS
NetApp Data ONTAP 8.2 7-Mode Isilon

Interface groups 7-mode

Interface groups must be named by using the syntax a<number><letter>.

A port that is already a member of an interface group cannot be added to another interface group.

Multimode load balancing methods: mac: Network traffic is distributed on the basis of MAC addresses. ip:
Network traffic is distributed on the basis of IP addresses. sequential: Network traffic is distributed as it is received.
port: Network traffic is distributed on the basis of the transport layer (TCP/UDP)ports.

For more information about load balancing, please refer to TR-4182: Ethernet Storage Best Practices for Cluster ed Data
ONTAP Configurations.

Interface Group

Due to the limited capabilities of single mode, it is recommended that you do not use this type of interface group in
clustered Data ONTAP

To take advantage of all the performance and resiliency functionality of dynamic multimode ( LACP ), it is
recommended when you use interface groups

o Requires an LACP -enabled switch

o All the interfaces in the group will be active, will share the same MAC address, and will use load balancing
outbound traffic (not inbound)
 o A single host will not achieve larger bandwidth than any of the constituent connection (two 10-GbE
20GbE)

o May not have any advantages for iSCSI hosts

For more information, refer to TR-4182: Ethernet Storage Best Practices for Clustered Data ONTAP Configurations.

VLAN

Ports, Interface Groups, and VLANs

Ports are the physical network adapters that are cabled to a switch or a virtualization. This switch or virtualization
subdivides or groups the physical ports. Ports can be arranged in a hierarchy, with VLANs subdividing the interface

groups. In 7-Mode, interface

groups can be created from ports or other interface groups; the latter are called secondlevel interface groups. You can
create a second-level interface group by using two multimode interface groups. Second-level interface groups enable you
to provide a standby multimode interface group in case the primary multimode interface group fails. VLANs cannot be
created from other VLANs, and interface groups cannot be created from VLANs. In clustered Data ONTAP, interface
groups cannot be created from other interface groups, VLANs cannot be created from other VLANs, and interface groups
cannot be created from VLANs. NOTE: You cannot create VLANs or interface groups on cluster ports on clustered Data
ONTAP.

IPspaces

Data ONTAP 8.3 An IPspace defines a distinct IP address space in which virtual storage systems can
participate. IP addresses that are defined for an IPspace are applicable only within that IPspace. A distinct routing table is
maintained for each IPspace. No cross-IPspace traffic routing happens. Each IPspace has a unique loopback interface
thatis assigned to it. The loopback traffic on each IPspace is completely isolated from the loopback traffic on other
IPspaces
IPspaces IP NAS
IP IP IP IPspaces

IPspaces 10.0.0.0
SVM IPspaces IPspaces SVM subnet ports SVM

IPSPACES

2 IPspaces IPspace SVM(Vfiler) CLI Vserver

Data ONTAP 8.3 IPspaces

labcluster2::> network ipspace show

IPspace Vserver List Broadcast Domains

------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

labcluster2 Default

2 entries were displayed.

Default IPspace
This IPspace is a container for ports, subnets, and SVMs that serve data. If your configuration does not need separate
IPspaces for clients, all SVMs can be created in this IPspace. This IPspace also contains the cluster management and
node management ports.
Cluster IPspace
This IPspace contains all cluster ports from all nodes in the cluster. It is created automatically when the cluster is created.
It provides connectivity to the internal private cluster network. As additional nodes join the cluster, cluster ports from those
nodes are added to the Cluster IPspace. IPspace

IPspace

IPspace 2 IPspaces 2
IPspaces

labcluster2::> network ipspace create -ipspace IPspace_Sales

labcluster2::> network ipspace create -ipspace IPspace_Market

labcluster2::> network ipspace show

IPspace Vserver List Broadcast Domains

------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

labcluster2 Default

IPspace_Market

IPspace_Market -

IPspace_Sales

IPspace_Sales -

4 entries were displayed.

labcluster2::> network ipspace show -ipspace IPspace_Market

IPspace name: IPspace_Market

Ports: -

Broadcast Domains: -
 Vservers: IPspace_Market

labcluster2::> network ipspace show -ipspace IPspace_Sales

IPspace name: IPspace_Sales

Ports: -

Broadcast Domains: -

Vservers: IPspace_Sales

2 IPspace SVM Broadcast Domains

SVM

Broadcast Domains

Broadcast Domains Broadcast domains are commonly used when a system administrator wants to
reserve specific ports for use by a certain client or group of clients. A broadcast domain should include ports from many
nodes in the cluster to provide high availability for the connections to SVMs

SVM
2 Broadcast domains Default Cluster

labcluster2::> network port broadcast-domain show

IPspace Broadcast Update

Name Domain Name MTU Port List Status Details

------- ----------- ------ ----------------------------- --------------

Cluster Cluster 1500

labcluster2-01:e0a complete

labcluster2-01:e0b complete
 labcluster2-02:e0a complete

labcluster2-02:e0b complete

Default Default 1500

labcluster2-01:e0c complete

labcluster2-01:e0d complete

labcluster2-02:e0c complete

labcluster2-02:e0d complete

2 IPspaces Broadcast Domains SVM

Broadcast Domains 4 2

labcluster2::> network port show

Speed (Mbps)

Node Port IPspace Broadcast Domain Link MTU Admin/Oper

------ --------- ------------ ---------------- ----- ------- ------------

labcluster2-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

e0e Default - up 1500 auto/1000

e0f Default - up 1500 auto/1000

labcluster2-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

e0e Default - up 1500 auto/1000

e0f Default - up 1500 auto/1000

12 entries were displayed.

Broadcast Domains

2 Broadcast Domains IPspaces Sales IPspaces

Market

labcluster2::> network port broadcast-domain create -broadcast-domain bcast_Sales -mtu 1500 -ipspace
IPspace_Sales -ports labcluster2-01:e0e,labcluster2-02:e0e

labcluster2::> network port broadcast-domain create -broadcast-domain bcast_Market -mtu 1500 -ipspace
IPspace_Market -ports labcluster2-01:e0f,labcluster2-02:e0f

labcluster2::> network port broadcast-domain show

IPspace Broadcast Update

Name Domain Name MTU Port List Status Details

------- ----------- ------ ----------------------------- --------------

Cluster Cluster 1500

labcluster2-01:e0a complete

labcluster2-01:e0b complete

labcluster2-02:e0a complete

labcluster2-02:e0b complete

Default Default 1500

labcluster2-01:e0c complete

labcluster2-01:e0d complete
 labcluster2-02:e0c complete

labcluster2-02:e0d complete

IPspace_Market

bcast_Market 1500

labcluster2-01:e0f complete

labcluster2-02:e0f complete

IPspace_Sales

bcast_Sales 1500

labcluster2-01:e0e complete

labcluster2-02:e0e complete

4 entries were displayed.

IPspaces

labcluster2::> network ipspace show

IPspace Vserver List Broadcast Domains

------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

labcluster2 Default

IPspace_Market

IPspace_Market bcast_Market

IPspace_Sales

IPspace_Sales bcast_Sales
4 entries were displayed.

Subnet
Broadcast Domains IP IP Pool IP
LIF IP IP LIF IP IP

Subnet

2 IP subnet IPspaces

labcluster2::> network subnet create -subnet-name subnet_Sales -broadcast-domain bcast_Sales -ipspace

IPspace_Sales -subnet 192.168.0.0/24 -gateway 192.168.0.130 -ip-ranges 192.168.0.30-192.168.0.35

labcluster2::> network subnet create -subnet-name subnet_Market -broadcast-domain bcast_Market

-ipspace IPspace_Market -subnet 192.168.0.0/24 -gateway 192.168.0.130 -ip-ranges 192.168.0.30-
192.168.0.35

labcluster2::> network subnet show

IPspace: IPspace_Market

Subnet Broadcast Avail/

Name Subnet Domain Gateway Total Ranges

--------- ---------------- --------- --------------- --------- ---------------

subnet_Market

192.168.0.0/24 bcast_Market

192.168.0.130 6/6 192.168.0.30-192.168.0.35

IPspace: IPspace_Sales

Subnet Broadcast Avail/

Name Subnet Domain Gateway Total Ranges

--------- ---------------- --------- --------------- --------- ---------------

subnet_Sales

192.168.0.0/24 bcast_Sales

192.168.0.130 6/6 192.168.0.30-192.168.0.35

2 entries were displayed.

Logical Interfaces(LIF)

An IP address or World Wide Port Name (WWPN) is associated with a LIF

If subnets are configured (recommended), IP addresses are automatically assigned when a LIF is created

If subnets are not configured, IP addresses must be manually assigned when LIF is created

WWPNs are automatically assigned when an FC LIF is created

One node-management LIF exists per node

One cluster-management LIF exists per cluster

Two* cluster LIFs exist per node

Multiple data LIFs are allowed per port (Client-facing: NFS, CIFS, iSCSI,and FC access)

For intercluster peering, intercluster LIFs must be created on each node

LIF LIFlabcluster2-01_mgmt1 labcluster2-02_mgmt1

LIFcluster_mgmt 2 LIF

labcluster2::> network interface show

Logical Status Network Current Current Is

Vserver Interface Admin/Oper Address/Mask Node Port Home

----------- ---------- ---------- ------------------ ------------- ------- ----

Cluster

labcluster2-01_clus1
 up/up 192.168.10.12/24 labcluster2-01

e0a true

labcluster2-01_clus2

up/up 192.168.10.13/24 labcluster2-01

e0b true

labcluster2-02_clus1

up/up 192.168.10.10/24 labcluster2-02

e0a true

labcluster2-02_clus2

up/up 192.168.10.11/24 labcluster2-02

e0b true

labcluster2

cluster_mgmt up/up 192.168.0.40/24 labcluster2-01

e0d true

labcluster2-01_mgmt1

up/up 192.168.0.21/24 labcluster2-01

e0c true

labcluster2-02_mgmt1

up/up 192.168.0.20/24 labcluster2-02

e0c true

7 entries were displayed.

LIF Port IP Port port LIF

port
 LIF

c1::> network interface create vserver SVM_A-1 lif SVM_A-1_lif2 role data data-protocol nfs home-node c1-
02 home-port e0f subnet-name subnet_A SVM LIF
home-node home-port

The home-node parameter is the node to which the LIF returns when the network interface revert command is run
on the LIF.

The home-port parameter is the port or interface group to which the LIF returns when the network interface revert
command is run on the LIF.

Nondisruptive LIF Configuration

Clustered Data ONTAP 8 has always supported nondisruptive LIF configuration. The process of performing a failover has
changed throughout the versions leading up to the 8.3 release. Here is a brief history:

Data ONTAP 8.0: Failover rules (network interface failover) were the primary way to control failover based on port
role and priority.

Data ONTAP 8.1: Failover groups (network interface failover-groups) became theprimary method to control
failover. Failover rules were deprecated.

Data ONTAP 8.3: Failover groups and failover policies were changed to work with broadcast domains. There are
fewer failover groups and more failover policies.

Conceptually, LIF failover is similar in the different versions of clustered Data ONTAP, but the configuration is very
different. This lesson discusses only examples of clustered Data ONTAP 8.3. For more information about how to configure
LIF failover in older versions of clustered Data ONTAP, refer to the Network Management Guide for the version of
clustered Data ONTAP that you are configuring.

Network Load Balancing

Isilon SmartConnectIsilonSmartConnect

Clients can mount to an SVM by either: Specifying a LIFs IP address or Specifying a host name (for multiple
managed IP addresses)

Load balancing dynamically evaluates the load on LIFs and either: Selects an appropriately loaded LIF or Moves a
LIF to a less loaded port

Load balancing types: DNS load balancing (NFS or CIFS); On-box (zoning based); Off-box (round robin);
Automatic LIF rebalancing (NFSv3 only)