VMware NetApp FAS 2050HA, Manual

Page: 7 / 21

Teaming ports and assigned to the public VLAN for access to CIFS shares and other network resource by
the desktop virtual machines.
The NetApp FAS2050HA has four 1Gb NICs. The four NICs were configured as two multi-mode VIFs.
One VIF was specifically for VMkernel NFS traffic and was placed on the private, non-routable VLAN.
The other VIF was for CIFS (Home Directories) and management traffic. This configuration allows for an
Active/Active state with both failover and a degree of redundancy in the NFS environment. The two
switch ports for the NFS traffic on each storage controller were assigned to a private, non-routable VLAN
previously configured and the multi-mode VIF was assigned a pre-defined IP address on this VLAN (i.e.
192.168.1.x). In addition two additional NICs on the public VLAN (with each residing on separate
switches) are configured into a multi-mode VIF for CIFS traffic. This configuration can either be done in
the Data ONTAP GUI or from the Data ONTAP service Console. Additionally, the multi-mode VIF
configured for NFS traffic was also assigned an alias IP address to allow for mounting the NFS datastore
to the ESX hosts with different IP addresses to increase throughput and redundancy of the NFS IP link.
Since the Cisco 3750s used in this configuration support cross-stack Etherchannel trunking, each storage
controller requires only one physical connection for NFS traffic to each switch. The two ports were
ombined into one multimode LACP VIF with IP load balancing enabled. c
Figure 2) ESX and NetApp storage controller VIF configuration.
S hown below is a step-by-step of how to perform the network configuration for the NFS VIF in FilerView®.
NOTE: In accordance with NetApp best practices for storage controller configuration the creation of the
management/CIFS VIF was necessary in order to have redundant NICs for management. The creation of
the management/CIFS VIF should be done during the initial setup of the FAS2050 in order to avoid a
6