VMware NetApp FAS 2050HA Manuel utilisateur
Contents
1IntroductiontoVMwareView...........................................................................2
2AboutThisGuide...................................................................................................2
3HardwareandSoftwareRequirements.........................................................2
3.1 Terminology...............................................................................................................................................................................2
3.2 HardwareResources..............................................................................................................................................................3
3.3 SoftwareResources................................................................................................................................................................4
4PhysicalArchitecture...........................................................................................5
4.1 NetworkArchitecture............................................................................................................................................................5
4.2 StorageArchitecture..............................................................................................................................................................9
4.3 NetAppDataONTAPConfiguration...............................................................................................................................10
4.4 IntelligentReadCaching.....................................................................................................................................................13
4.5 DeduplicationSetup.............................................................................................................................................................13
4.6 VMwareESXConfiguration...............................................................................................................................................14
5ValidationResults...............................................................................................16
5.1 ApplicationResponseTime...............................................................................................................................................16
5.2 StorageSystemIOSummary............................................................................................................................................17
6Summary................................................................................................................18
7Acknowledgments...............................................................................................18
8References.............................................................................................................18
1 INTRODUCTION TO VMWARE VIEW
Built on VMware’s industry-leading virtualization platform, VMware® View is a Universal Client solution
that lets you manage operating systems, hardware, applications and users independently of each other,
wherever they may reside. VMware® View streamlines desktop and application management, reduces
costs and increases data security through centralization, resulting in greater end user flexibility and IT
control. VMware View enables customers to extend the value of VMware Infrastructure and virtual
desktop infrastructure (VDI) environments to encompass not only desktops in the datacenter but also
applications and the delivery of these environments securely to remote clients, online or off, anywhere.
VMware View transforms the way customers use and manage desktop operating systems. Desktop
instances can be rapidly deployed in secure data centers to facilitate high availability and disaster
recovery, protect the integrity of enterprise information, and remove data from local devices that are
susceptible to theft or loss. Isolating each desktop instance in its own virtual machine eliminates typical
application compatibility issues and improves and delivers a more personal computing environment.
2 ABOUT THIS GUIDE
This deployment guide provides a detailed summary and characterization for designing and configuring a
NetApp FAS2050HA storage system for use with VMware View and Linked Clones. It describes a
validated configuration for a 1000 user workload where 500 desktops are in persistent access mode and
500 users are in non-persistent access mode. This guide can be easily scaled up for larger deployments
by simply increasing the number of servers, storage controllers, and storage needed.
The configuration presented was validated in accordance with a recommended architecture as defined
in the VMware View Reference Architecture: A Guide to Large-scale VMware View Deployments. This
guide is intended to offer Systems Architects and Administrators guidance with the configuration of a
NetApp FAS2050HA storage system for use with such VMware View based environments. The
information provided in this guide also can be helpful to anyone looking to deploy VMware View with
Linked Clones using a NetApp FAS2050HA. In addition, due to all NetApp FAS storage controllers
having the same feature and management interface consistency with Data ONTAP®, all of these
guidelines can also be directly applied to entry-level and enterprise-class NetApp FAS storage controllers.
All of the NetApp best practices applicable to this solution configuration are documented in NetApp’s TR-
3428: NetApp and VMware Virtual Infrastructure 3 Storage Best Practices, TR-3705: NetApp and
VMware View Solution Guide and TR-3505: NetApp Deduplication for FAS Deployment and
Implementation Guide and have been used in the creation and validation of this environment.
3 HARDWARE AND SOFTWARE REQUIREMENTS
3.1 TERMINOLOGY
Term Definition
Aggregate Pool of physical storage that contains logical volumes
CIFS Common Internet File System
Deduplication A technology that seeks out duplicate data, removes the duplicate data and replaces
it with a reference pointer to the previously stored, identical object
2
NFS Network File System Protocol
NIC Network Interface Card
RAID Redundant Array of Independent Disks
Snapshot Read only copies of an entire file system in Data ONTAP
VMware View
Manager
VMware View Manager manages secure access to virtual desktops, works
with VMware vCenter Server to provide advanced management capabilities
VC VMware vCenter Server
VIF Virtual Interface
VLAN Virtual Local Area Network
VMware View
A set of software products that provide services and management
infrastructure for centralization of desktop operating environments using
virtual machine technology.
Volume Logical storage container on Data ONTAP that organizes user and system files and
directories
Table 1: Glossary of terms
3
T
.2 HARDWARE RESOURCES
he following equipment was used in this configuration:
Description Minimum Revision
One NetApp FAS2050HA Cluster Data ONTAP 7.3.1; NFS
Two shelves of disks 28 disks (14 per shelf); Each disk 300GB / 15K/ FC
2 Cisco 3750 stackable switches
1 dual port Ethernet NIC per FAS2050
controller
3
Ten Servers (Configured as follows)
128 GB RAM
4 Quad Core Xeon Processors
2 On-board Ethernet NICs
2 Quad port Ethernet NICs
Table 2: Hardware Configuration
3.3 SOFTWARE RESOURCES
The following software was used in the configuration:
Description Minimum Revision
Data ONTAP® 7.3.1
NFS License N/A
VMware ESX Servers 3.5 Update 3
VMware vCenter Server 2.5 Update 3
Windows Servers for vCenter Microsoft Windows Server 2003 Enterprise Edition SP 2
(32-Bit)
Desktops/Virtual Machines Windows XP Service Pack 3 (32-Bit)
VMware Tools 3.5
Windows Server for View connection server Microsoft Windows Server 2003 Enterprise Edition SP 2
(32-Bit)
Infrastructure servers (AD, DHCP, DNS) Microsoft Windows Server 2003 Enterprise Edition SP 2
(32-Bit)
4
Table 3) Software Resources
4 PHYSICAL ARCHITECTURE
Figure 1) Physical Architecture Overview.
4.1 NETWORK ARCHITECTURE
The networks used for this test were dedicated 1Gb Ethernet. This network was split into three VLANs.
One VLAN was for administrative/public traffic and CIFS access, and the other two were non-routable
VLANs designed for storage and VMotion traffic. All virtual desktops were assigned an IP address using
a DHCP server.
The VMware ESX Server’s networking configuration consisted of ten 1Gb Ethernet Controllers (or NICs).
Two were configured as NIC Teaming ports for NFS traffic and assigned to a pre-defined VMkernel port
used for NFS access with a pre-defined IP address on the non-routable VLAN (i.e. 192.168.1.x). Two
NICs were configured as NIC Teaming ports for VMotion traffic and assigned to a pre-defined, VMotion
enabled VMkernel port with a pre-defined IP address on another non-routable VLAN used solely for
VMotion traffic (i.e. 192.168.0.x). Two NICs were configured as NIC Teaming ports for the Service
Console and assigned to the administrative VLAN. The last four NICs were also configured as NIC
5
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
reboot of the storage controller at a future time. In the event the management/CIFS VIF needs to be
created after the initial setup of the FAS2050, please refer to the Data ONTAP® Software Setup Guide for
irections in rerunning the setup process for the storage controller.d
1. For each NetApp controller, open NetApp FilerView® and click Network->Add Virtual Interfaces.
2. Name the new VIF.
3. Select the two network interfaces that will make-up the NFS VIF.
4. For Trunk Mode press the drop down arrow and select Multiple.
5. For Load Balancing press the drop down arrow and select IP.
6. Click Apply.
Figure 3) AS2050 NFS VIF setup –Create Virtual Interface.F
1. At the Manage Network Interfaces screen, click on Modify for the new VIF that was created in the
previous steps.
2. At the Modify Network Interfaces screen enter a private IP Address that will be used for ESX host
NFS connectivity and then enter the Netmask and click Apply.
3. At the Manage Network Interfaces screen click on Up for the new VIF in order to activate it.
7
Figure 4) FAS2050 NFS VIF setup – Modify virtual interface.
The ESX hosts will need to be configured as well. For each ESX host, configure NFS connections to the
storage controllers using a VMkernel port group. The network ports for this NFS VMkernel port group
should be on a non-routable NFS VLAN. For each ESX host, the virtual switch for the NFS VMkernel
should have two network ports that each go to different switches in the network. These two switches are
stacked together with link aggregation configured for the uplink vmnics.
Note: This should be configured as a standard port channel, not using any link aggregation protocols
such as LACP.
To configure an ESX server for NFS connectivity follow the below steps:
•Configuration Tab > Networking > Add networking > VMKernel > Create a New switch
•Provide a Network Label – Example: VMkernel NFS
•Set a VLAN tag (optional)
•rovide the IP address and subnet maskP
NOTE: While performing the network setup the VMotion VMkernel port group and a public Virtual
Machine port group should be configured as well. Also, ensure that the redundant Service Console NIC
is placed in the Service Console port group for redundancy. Depicted below is an example of the
etworking setup for an ESX host for the environment detailed in this document.
n
8
Physical Adapters
Physical Adapters
VM Network
VMkernel NFS
192.168.1.101
Service Console
vswif0: 10.10.10.10
Virtual Switch: vSwitch2
VMkernel Port
ESX Host
Virtual Machine Port Group
Virtual Switch: vSwitch1
Virtual Machine 1
Virtual Machine 2
Virtual Machine 3
Virtual Machine 4
Virtual Switch: vSwitch0
Service Console Port Physical Adapters
VMotion
192.168.0.111
Virtual Switch: vSwitch3
VMkernel Port
Remove… Properties...
Remove… Properties...
Remove… Properties...
Remove… Properties...
Physical Adapters
Figure 5) VMware ESX server NIC configuration
4.2 STORAGE ARCHITECTURE
The NetApp FAS2050HA was configured with one aggregate and six volumes per controller. Each
storage controller had one shelf of 300GB/15K RPM disks (with 12 disks in an aggregate and two
spares). Using NetApp’s RAID-DP to create one 12 disks aggregate enabled all virtual desktops
hosted on the storage controller to use the pooled performance capability as required. RAID-DP
also allows higher levels of resiliency as compared to RAID-5.
NetApp Storage Controller Objects Configuration
Volume for Parent VM
Initial volume storage capacity 25GB
NFS capacity 25GB
9
Table des matières
Manuels Stockage populaires d'autres marques
Spectra Logic
Spectra Logic T-Series Spectra T50e Manuel utilisateur
Panasonic
Panasonic LKM-F931-1 Manuel utilisateur
Tabernus
Tabernus Enterprise Erase E2400 Manuel utilisateur
Rocstor
Rocstor COMMANDER 3F series Manuel utilisateur
HP
HP P9000 Manuel utilisateur
Western Digital
Western Digital Ultrastar Data60 Manuel utilisateur