Dell XC630-10 Nutanix on Hyper-V reference architecture

TABLE OF CONTENTS
Table of contents.....................................................................................2
Executive summary..................................................................................4
Introduction........................................................................................4
Objective.............................................................................................4
Audience.............................................................................................4
Product Overview ....................................................................................5
About the Dell XC630 Web-Scale Converged Appliance ....................5
About the Dell Networking S4048-ON top-of-rack switch .................5
Software solutions...................................................................................6
Operating systems..............................................................................6
Solution design and configuration ............................................................7
Overview of the scope of this guide ...................................................7
Before you begin.................................................................................7
Assumptions of this guide...................................................................7
Introduction to Nutanix architecture .................................................8
Solution architecture and diagrams ...................................................8
Creating the Nutanix cluster............................................................ 11
Configuring Nutanix storage............................................................ 19
Joining the domain and creating the failover cluster...................... 22
Configuring Hyper-V Manager to use the Nutanix storage cluster
SMB share........................................................................................ 24
Configuring Live Migration .............................................................. 25
About the test environment...................................................................31
Workloads.............................................................................................32
OLTP database workload: DVD Store .............................................. 32
Exchange workload: Microsoft Load Generator 2013..................... 32
Disk activity workload: Iometer....................................................... 33
Validation and test results......................................................................34
Nutanix storage cluster on XC630 supporting all application
workloads ........................................................................................ 34
Summary...............................................................................................36
Appendix A – Detailed system configuration...........................................37
Appendix B – Detailed configuration methodology .................................39
Configuring application VMs............................................................ 39
Creating VMs for Hyper-V in PowerShell......................................... 39
Configuring Microsoft Exchange 2013 for Load Generator 2013.... 39
Installing Exchange Server 2013 SP1 Mailbox and Client Access
Server roles...................................................................................... 40
Configuring Exchange ...................................................................... 41

Installing and configuring the Exchange 2013 mail test clients and
completing LoadGen configuration on the Exchange 2013............. 45
Installing Load Generator ................................................................ 46
Installing and configuring Iometer................................................... 47
Configuring the database workload client....................................... 49
Running the test .............................................................................. 50
Appendix C – S4048-ON Switch configuration .........................................51
About Principled Technologies ...............................................................54

A Principled Technologies reference architecture 4Dell XC630-10 Nutanix on Hyper-V reference architecture
EXECUTIVE SUMMARY
Introduction
For years, traditional datacenters have encountered problems
stemming from the separation of compute and storage resources. This
separation can negatively affect performance, scalability, and cost.
Hyperconverged solutions, in which compute and storage share a chassis, aim to
fix these problems by bringing resources closer together.
One such solution is the Dell XC630-10 system powered by Intel
processors E5-2630 v3 and using Nutanix software. This solution takes up
minimal space in the datacenter, which could potentially help you save on
power and cooling costs. Its unique architecture combines 1U form factor Dell
XC630-10 appliances, Intel processors, onboard storage, and Nutanix cluster
software in a flexible and scalable package.
In the Principled Technologies datacenter, we set up the Dell and Intel
hyperconverged solution as a Microsoft Windows Server 2012 R2 cluster with
Microsoft Hyper-V. To prove that the solution functioned well with Microsoft
Hyper-V, we tested a mixed workload, which included Microsoft Exchange
Server, Microsoft SQL Server, file and print activity, and disk activity simulating a
web server. Together, this workload mimics the kind of work a small to medium-
sized company might do on a daily basis.
This reference architecture explains our findings and offers a guide and
best practices for implementing this solution in your datacenter.
Objective
This reference architecture aims to demonstrate how the Dell XC630-10
system powered by the Intel Xeon processor E5-2630 v3 and using Nutanix
software functioned well with mixed workloads when configured as a Microsoft
Windows Server 2012 R2 cluster with Microsoft Hyper-V. Additionally, it
provides best practices and a configuration guide for setting up this Dell and
Intel solution running Hyper-V in the datacenter of a medium-sized business.
Audience
This reference architecture is intended for an audience of IT
administrators at small to medium businesses with several hundred employees.
This reference architecture does not describe every possible configuration of
each component in the Dell and Intel solution.

PRODUCT OVERVIEW
About the Dell XC630 Web-Scale Converged Appliance
Dell XC Series Web-Scale Converged Appliances, powered by Nutanix
software, let you consolidate compute and storage into a single chassis.
According to Dell, these appliances install quickly, integrate easily into any data
center, and can be deployed for multiple virtualized workloads including
desktop virtualization, database, and private cloud projects. They let your
enterprise grow incrementally with pay-as-you-grow, scale-out expansion;
increase capacity and performance one node at a time; and meet future needs
without over-provisioning.
The Dell XC630-10 is a compact 1U compute/storage node, making it
attractive to companies with limited rack space or those deploying VDI and
other virtualized workloads. It has 10 drive slots that can be populated with up
to four SSDs (two SSDs being mandatory) and up to eight HDDs.
Learn more at www.dell.com/us/business/p/dell-xc-series/pd.
About the Dell Networking S4048-ON top-of-rack switch
The Dell Networking S4048-ON 10/40 GbE top-of-rack Open Networking
switch, Dell’s latest datacenter networking solution, is built to optimize
performance, efficiency, flexibility, and availability in the modern datacenter.
According to Dell, it offers a range of benefits, including:
 Low latency. To deliver the strongest performance, the S4048-ON
leverages a non-blocking architecture to deliver line-rate L2 and L3
forwarding – ideal for use in high-speed, business-sensitive deployments.
 High density. The S4048-ON takes up only a single rack unit but offers 48
dual-speed 1/10GbE (SFP+) ports and six 40GbE uplinks. In addition to
saving space, this specific level of density may simplify your migration to
40Gbps in the core of the datacenter.
 Flexibility in the datacenter. The S4048-ON includes several
architectural features that can help you keep your datacenter running
smoothly. Its I/O panel to PSU or PSU to I/O panel airflow give you more
flexibility with your hot/cold aisle arrangements, and it offers redundant,
hot-swappable power supplies and fans to reduce the cost of datacenter
maintenance.
Learn more at i.dell.com/sites/doccontent/shared-content/data-
sheets/en/Documents/FY16Q1_201_Dell_Networking_S4048-
ON_SpecSheet_040215.pdf.

SOFTWARE SOLUTIONS
Operating systems
About Microsoft Windows Server 2012 R2
Windows Server 2012 R2, the latest release of this server OS from
Microsoft, includes many new features and enhancements. According to
Microsoft, Windows Server 2012 R2 focuses on four core areas:
 Beyond virtualization. Windows Server 2012 R2 provides a robust and
dynamic virtualization platform through Hyper-V, and includes new
features that provide flexible options for delivering cloud services.
 The power of many servers, the simplicity of one. Windows Server 2012
R2 offers improvements in its features that allow for better-than-ever
high availability and ease of management for multiple-server
infrastructures.
 Every app, any cloud. Windows Server 2012 R2 delivers a scalable and
flexible Web and application platform by providing a consistent and open
set of tools and frameworks that apply to applications on-premises, in the
cloud, or in a hybrid environment.
 Modern work style, enabled. Microsoft Windows Server 2012 R2
empowers users and IT staff with remote access to data, applications, and
simpler management tools while strengthening security and compliance.
About Nutanix OS 4.1
According to Nutanix, the Nutanix Operating System, NOS 4.1, offers
rich enterprise capabilities to meet the needs of the most demanding
applications and critical infrastructure requirements in the datacenter.
The 4.1 release includes the following new capabilities:
 Metro Availability, which provides continuous data availability for
business-critical applications during planned maintenance or
unplanned disasters that affect entire sites.
 Cloud Connect, which seamlessly integrates public cloud services,
such as Amazon Web Services (AWS), with Nutanix-powered private
cloud environments.
 Encryption Support, encrypting user and application data to a level of
FIPS 140-2 Level 2 compliance.
 Simplified Hypervisor Upgrade, with support for VMware ESXi,
Microsoft Hyper-V, and KVM.
 Security/STIG Enhancements

Learn more at www.nutanix.com/2015/01/29/announcing-general-
availability-nutanix-operating-system-4-1/.
SOLUTION DESIGN AND CONFIGURATION
Overview of the scope of this guide
In this guide, we will walk through the various aspects of setting up a
working Nutanix cluster on a three-node Dell XC630 appliance configuration. We
will cover the network setup, including cabling, switch configurations, and VLAN
tagging; initial cluster creation for Nutanix and Windows Server 2012 R2; and
cluster storage configuration for a three-node cluster of Dell XC630-10
appliances. We will also highlight best practices as appropriate.
Before you begin
In preparation for setting up your Nutanix environment on Hyper-V with
XC630 hosts, you will need one IP address available for the cluster’s IP address
and at least three IP addresses per host: one each for the host’s CVM, the host’s
management, and the host’s IPMI interface. In our environment, we used VLAN
tagging to keep the IPMI network separate from the CVM traffic, but a flat
network could also be set up to avoid our more complex network design. The
IPMI interfaces are required for successful cluster deployment, even though
their reachability does not affect the normal functioning of the Nutanix cluster
post-install. Also, note that if your IPMI interfaces are not configured with
routable IP addresses, some support and management functionality could
potentially be impacted.
Assumptions of this guide
We will assume in this guide that each Dell XC630 appliance has had
Windows Server 2012 R2 pre-installed and the Nutanix Phoenix flashing process
performed already (Phoenix takes care of configuring disks, networking, and
Nutanix Controller VM creation). We also assume the administrator following
this guide has an existing Active Directory server, DNS server, and gateway in
their environment. Before beginning the methodology steps, we will assume
you have configured the CVMs and iDRAC/IPMI interfaces on each host with an
IP address and subnet mask, and provided them with the existing DNS and
gateway addresses.
From a networking perspective, we designed this guide to be
representative of a real-world enterprise environment, rather than a basic flat
network. Though we cover setup for a more complex network infrastructure,
including redundant switches, VLAN tagging to segregate traffic, and virtual link

trunking, Nutanix can be deployed on a Hyper-V environment in a similar
fashion on a simpler network.
Introduction to Nutanix architecture
Nutanix uses a hyperconverged infrastructure to provide a tiered
storage solution to VMs. Every host in a Nutanix cluster houses a Controller VM
(CVM), which runs the Nutanix software and handles all storage I/O operations
for the host’s hypervisor and all the VMs residing on that host. In the case of
Hyper-V, the host appliance’s SSDs and hard disk drives are directly passed
through to the CVM for management.
Administrators can create a storage container from the Nutanix cluster’s
disks to be used as storage for all the cluster’s hosted VMs. Nutanix cluster
nodes typically have a small number of fast but low-capacity SSDs and a larger
number of slower but high-capacity HDDs. Nutanix storage tiering/prioritization
works to move data to the most appropriate location (either local SSDs, cluster
SSDs, or HDDs) based on availability of fast storage and how frequently the data
in question is accessed. By converging compute and storage resources into
single appliance nodes, scaling Nutanix clusters out is easy and flexible.
Solution architecture and diagrams
Every Dell XC630 appliance in a Nutanix cluster has the same basic
configuration: a tier of SSD-based flash storage, a tier of hard disk drives,
compute resources in the form of two Intel Xeon processors E5-2630 v3, and
192 GB of DDR4 RAM. At the hypervisor layer, each host runs Hyper-V on
Windows Server 2012 R2, which hosts a single Nutanix Controller VM, and as
many other VMs as you configure for your environment (see Figure 1).

Figure 1: The structure of each node in our Nutanix cluster.
Once the cluster has been created, the flash and hard disk storage
resources from each node are logically grouped and defined through software
as a storage pool. From there, a container is created and used for housing the
virtual hard disks and virtual machine configuration files for your environment.
Although we did not use these features, Nutanix offers storage efficiency
technologies such as deduplication, which removes duplicate data to increase
the effective amount of storage resources available and accelerate
performance, as well as thin provisioning, which allows a LUN to be created
without allocating physical storage space that would go unused initially (more
physical space is used as the actual space fills up). For more information on
deduplication as provided by Nutanix, go to
www.nutanix.com/products/features/enterprise-storage/deduplication/. Figure
2 shows how the storage for the three-node cluster we tested is configured.

Figure 2: The Nutanix storage cluster’s container is comprised of the flash and hard disk
storage from each host.
Our environment used redundant 10 Gbps Dell Networking S4048-ON
switches for cluster/VM traffic and live migration, and redundant 1 Gbps Dell
Networking 5448 switches for IPMI traffic. We used VLAN tagging to segregate
the public traffic from the Live Migration traffic, Dell virtual link trunking (VLT)
between the S4048-ON switches, and 1 Gbps links between the S4048-ON
switches and the 5448 switches (see Figure 3).
Figure 3: The network configuration for the Nutanix cluster we tested on Dell XC630 appliances.

The Dell XC630 is configured (by the Phoenix flashing process) with a
NIC team (configured with switch independent teaming mode and dynamic load
balancing) created from the two 10 Gbps SFP ports on the Intel X520/i350
network daughter card. Two virtual switches come preconfigured as well, one
for traffic between the host and the Nutanix CVM, and one for Nutanix cluster
and VM traffic. We will later create another virtual network adapter on that NIC
team for running live migration traffic once the failover cluster is created (see
Figure 4).
Figure 4: The structure of each XC630 host’s NIC team, formed from the two 10 Gbps ports, and
their virtual switches and network adapters. Note that the 1 Gbps ports are unused.
Creating the Nutanix cluster
1. On the Windows 7 management system, be sure that Mozilla Firefox and
Bonjour (which is included with iTunes or downloadable from
support.apple.com/kb/DL999) are installed.
2. Determine the IPv6 service name for one of the Dell XC630 nodes that will
be added to the cluster. IPv6 service names are uniquely generated at the
factory and have the following form (note the final period): NTNX-
system_service_tag-node_location-CVM.local. On the front
left side of the system is a slide-out label that contains the
system_service_tag (for example, B57PW12). The node_location
is A for one-node blocks.
3. In the Windows 7 management system, launch Mozilla Firefox, and in the
URL bar, enter
http://cvm_ipv6_addr:2100/cluster_init.html, replacing

cvm_ipv6_addr with the IPv6 service name determined in step 2. For
example, the URL we accessed was http://NTNX-2PSNS52-A-
CVM.local.:2100/cluster_init.html. Be careful to include the
period after the word “local” in the URL.
Figure 5: Providing a cluster name, external IP, CVM DNS server, and CVM NTP server.
4. Provide an appropriate name (of 15 characters or fewer) for your Nutanix
Cluster in the Cluster Name field.
5. Provide an appropriate IP address for your Nutanix Cluster in the Cluster
External IP field. This IP can be used to access the web console and nCLI
once the cluster is created.
6. Leave the Cluster Max Redundancy Factor at 2, since we are using only
three nodes. A cluster must have at least five nodes to use a redundancy
factor of 3, but that configuration is beyond the scope of this guide.
7. Provide the IP address(es) of the Active Directory domain controller(s) in the
CVM DNS Servers and CVM NTP Servers fields.

Figure 6: Providing the appropriate subnet masks and default gateways in the Cluster-wide Network settings.
8. Provide the IP address(es) of the Active Directory domain controller(s) as
well as 8.8.8.8 in the Hypervisor DNS Servers field.
9. Leave the Hypervisor NTP Servers field blank, as this does not apply to a
Hyper-V cluster.
10. Provide the subnet masks and default gateways for each Controller,
Hypervisor, and IPMI into the Cluster-wide Network Settings table, if they
are not already populated.

Figure 7: If IPv6 link-local connectivity is working properly, your nodes should appear in the list of Discovered nodes.
11. Check the box next to each node that you want to add to the cluster.
12. Provide an appropriate IP address for all the components in the cluster, if
the values are not already populated. The discovered nodes are not listed in
a particular order, so be sure to assign the intended IP addresses to each
node.

Figure 8: Provide IP addresses for the Controller, Hypervisor, and IPMI for each discovered node.
13. When you are ready to create the cluster, click Create.
14. Wait until the Log Messages section of the page indicates that the cluster
has been successfully configured. The cluster starts automatically after
creation succeeds.

Figure 9: Log Messages output indicating successful creation of the Nutanix cluster.
15. Log onto any Controller VM with SSH.
16. Verify that all services are up on all Controller VMs by entering the
command cluster status.
Figure 10: Verifying that all cluster services are running properly on each node in the cluster.

17. On the Windows 7 management system, enter the cluster IP address into
the URL bar, and press Enter.
18. Enter a password for the cluster admin account, and re-enter it. Click the
arrow button when finished.
Figure 11: Providing an admin password for the Nutanix cluster.
19. Enter the admin credentials at the login prompt, and click the arrow button
to log in.

Figure 12: The Nutanix Web Console dashboard page.

Configuring Nutanix storage
After creating the cluster, you need to create a storage pool and a
container. For most organizations, creating a storage pool comprising all the
physical disks in the cluster, and then a container using all available capacity in
the storage pool will be suitable.
1. From the Nutanix Web Console main page, click the Home drop-down
menu, and select Storage.
Figure 13: The Storage drop-down menu selection.

2. Click the + Storage Pool button in the top-right corner. The Create Storage
Pool dialog box appears.
Figure 14: The Nutanix Web Console Storage page.

3. Provide a name for the storage pool, and be sure “Use unallocated capacity”
is checked, since that will be suitable for most environments.
Figure 15: Creating a storage pool in the Nutanix Web Console.
4. Click Save.
5. On the Storage page, click the + Container button. The Create Container
dialog box appears.
6. Provide a name for the container, check that the container will be created in
the intended storage pool, and click Save. More options are available by
clicking Advanced Settings, but they are beyond the scope of this guide.

Figure 16: Creating a container in the Nutanix Web Console.
Joining the domain and creating the failover cluster
After creating the storage on the Nutanix cluster, you need to join the
Hyper-V hosts and Nutanix storage cluster to the domain. After that, you have
to create the Hyper-V failover cluster. You will complete all of these steps
through commands in any CVM’s shell.
1. Log onto any CVM in the cluster via SSH.
2. Run the command setup_hyperv.py setup_hosts to start
joining the Hyper-V hosts to the domain.
3. When prompted, enter the IP address of the domain controller.
4. Enter the fully qualified domain name (FQDN) to which the hosts
will be joined. We used test.local.
5. Answer Y or N depending on whether you will use a 10G switch for
the cluster. We answered Y.

6. Enter the domain account you will use to join the hosts to a new
domain. We used test.localadministrator.
7. Provide that domain account’s password.
8. Provide a name for the Hyper-V cluster.
9. Provide custom names for your hosts when prompted, or use the
defaults by pressing Enter without entering anything.
10. Provide a custom name for accessing your Nutanix SMB shares, or
use the default by pressing Enter without entering anything. A
success message is displayed, and the hosts will restart to complete
joining the domain. Allow about 5 minutes before proceeding.
11. Log onto any CVM in the cluster via SSH.
12. Run the command setup_hyperv.py
create_failover_cluster to start creating the Hyper-V
failover cluster.
13. When prompted, provide a custom name for your cluster, or use
the default, as specified in the last set of prompts.
14. Enter a domain account with local administrator rights on the hosts.
For us, this was test.localadministrator.
15. Provide that domain account’s password.
16. Provide an external IP address to be used for the Hyper-V failover
cluster. The script will add the hosts to the new failover cluster.
Wait until this completes before proceeding.
17. Enter ncli into the shell to enter the Nutanix CLI.
18. Allow your management console workstation to access the cluster
entities by entering the following, using the workstation’s IP address
and subnet mask in place of the placeholder text: cluster add-
to-nfs-whitelist ip-subnet-
masks=ip_address/subnetmask.
19. Specify the timezone of the cluster by entering the following, using
your timezone in place of the placeholder text: cluster set-
timezone timezone=cluster_timezone.
20. Restart all CVMs in the cluster after changing the timezone. Because
a three-node cluster can tolerate only a single CVM unavailable at
any one time, restart them in a series, waiting until one has finished
restarting before proceeding to the next.

Configuring Hyper-V Manager to use the Nutanix storage cluster SMB share
1. Log into the Hyper-V Manager.
2. Right-click the Hyper-V Manager, and select Connect to Server.
3. Type the name of the host you want to add, and click OK.
4. Right-click the host and select Hyper-V Settings.
5. Click Virtual Disks, and specify the default folder to store virtual
hard disk files. For us, this was hvcluster-
smbcontainerdisks.
6. Click Virtual Machines and specify the default folder to store virtual
machine configuration files. For us, this was hvcluster-
smbcontainer.
7. Repeat steps 3 through 6 for each Hyper-V host to be configured.
Note: Virtual machines created using Hyper-V should never be
defined on storage using IP-based SMB share locations.
Figure 17: Hyper-V Settings for one of our hosts with properly configured storage locations for
virtual hard disks and virtual machine files.

Configuring Live Migration
Here, we create VLAN 101-tagged virtual switches on each XC630
Hyper-V host’s 10 Gbps NIC Team, and configure them for our failover cluster’s
Live Migration network.
1. Open PowerShell on one of the Hyper-V hosts.
2. Run the following commands to create a virtual NIC and tag it with
VLAN 101:
 Add-VMNetworkAdapter –ManagementOS –Name
LiveMigrationVLAN101 –SwitchName
ExternalSwitch
 Set-VMNetworkAdapterVlan –ManagementOS –
VMNetworkAdapterName
“LiveMigrationVLAN101” –Access –VlanID 101
3. In Windows, navigate to Network Connections, and open the
Properties for the new virtual adapter.
4. Select Internet Protocol Version 4 (TCP/IPv4), and click Properties.
5. Provide an IP address and subnet mask for the host’s Live Migration
network.
6. Repeat steps 1 through 5 for all three hosts.
7. On one of the hosts, open the Failover Cluster Manager.
8. Navigate to your cluster’s Networks folder in the left pane, and note
the cluster network whose subnet matches that of the virtual
adapter that was just configured for Live Migration.

Figure 18: Failover Cluster Manager’s Networks page; note the network you intend to use for Live Migration traffic.
9. Click Live Migration Settings.

10. Select the networks to be used for Live Migration, and use the Up
and Down buttons to set their order of preference. We selected
only the virtual NIC we just created, and moved it to the top of the
list.
Figure 19: Setting the Live Migration network for the failover
cluster. Choose the network noted in the previous section.
11. Click OK.
12. In Failover Cluster Manager, navigate to the cluster’s Roles tab.
13. Click Configure Role…

Figure 20: The Roles screen of the Failover Cluster manager.
14. In the High Availability wizard, on the Before You Begin screen, click
Next.
15. On the Select Role screen, select Virtual Machine, and click Next.

Figure 21: Selecting the Virtual Machine role in the High Availability Wizard.
16. In the Select Virtual Machine screen, select all the VMs you want to
be highly available, and click Next. We created our VMs using the
script outlined in Appendix B, and arranged them as outlined in
Figure 22.
Figure 22: Selecting the VMs to configure for high availability.

17. Confirm that you have selected the VMs you wish to configure for
high availability, and click Next.
Figure 23: Summary of successful configuration of VMs for high availability.
18. When the Summary page appears with successful results, click
Finish. You can also click View Report… to see a detailed overview of
the tasks completed.

ABOUT THE TEST ENVIRONMENT
Figure 24 presents the test hardware we used and Figure 25 provides an
overview of the VMs in our testing.
Hardware Quantity
Dell XC630-10 1U appliance 3
Dell Networking S4048-ON 10 Gigabit Switch 2
Dell Networking 5448 Gigabit Switch 2
Figure 24: Test hardware.
VM Application Role Host
SQL-1A SQL Server 2014 Database server 1
SQL-1B SQL Server 2014 Database server 1
SQL-1C SQL Server 2014 Database server 1
CAS-1 Exchange Server 2013 Client Access server 1
MBOX-1 Exchange Server 2013 Mailbox server 1
CAS-2 Exchange Server 2013 Client Access server 2
MBOX-2 Exchange Server 2013 Mailbox server 2
Iometer-1A Iometer File/Print workload 1
Iometer-1B Iometer Web server workload 1
Figure 25: VM overview.

WORKLOADS
For the validation tests, we set up a mixed workload consisting of some
common business applications and simulated disk activity to run in concert over a 30-
minute period. We ran an OLTP database workload, a Microsoft Exchange workload, and
a simulated file/print server disk workload.
OLTP database workload: DVD Store
To simulate an OLTP workload, we used DVD Store 2.1, an open-source
application that models an online DVD store where customers log in, search for titles,
and purchase movies. We tested with Microsoft SQL Server 2014 as our database
server. Higher thread count and lower think times increase CPU utilization and IOPS. For
more information on DVD Store, please see
en.community.dell.com/techcenter/extras/w/wiki/dvd-store.aspx.
Testing parameters
 Database size: 4 GB
 Number of databases: one per VM
 Number of threads per VM: 64
 Actual test run time: 50 minutes
 Percentage of new customers: 15
 Number of line items: 2
 Think time: 0 seconds
 Warm-up time: 10 minutes
 Ramp rate: 10
Additional VM parameters
 Each SQL VM was built with VHDXs for the OS, SQL Database, and SQL Logs
 Each SQL VM was configured as per best practices (E:SQL Database, F:SQL
Logs)
Output
 Orders per minute (OPM)
Exchange workload: Microsoft Load Generator 2013
The Microsoft Load Generator 2013 (LoadGen) benchmark performs tasks to
simulate a typical user generating mail activity on Microsoft Exchange Server 2013. We
divided our users into two mailbox databases, each with 100 users, for a total of 200
users/mailboxes. We ensured that performance was within acceptable RPC average
latency thresholds. For more information on Microsoft Load Generator 2013, please see
https://www.microsoft.com/en-in/download/details.aspx?id=40726.
Parameters
 Simulation: 8 hours
 Time: 30-minute duration
 100 users per database (200 total)

 Client: Outlook 2007 Cached
 Action profile: Outlook_50
 Mailbox profile: 2 MB
Output
 Success/failure
Disk activity workload: Iometer
To simulate disk workloads for a file/print server and for a web server, we used
Iometer, an application that allows various access specifications to be run against your
disk I/O subsystem, including read/write percentages, sequential/random percentages,
and block sizes. For more information on Iometer, please see www.iometer.org/.
Testing parameters for file/print server
 Test file size: 2 GB
 Number of outstanding I/Os: 1 per target
 Transfer request size: 512 KB
 Percentage Read/Write Distribution: 20% Write, 80% Read
 Percentage Random/Sequential Distribution: 100% Random
 Transfer delay: 70 ms
 Burst length: 1 I/O
 Warm-up time: 1 minute
Testing parameters for web server
 Test file size: 2 GB
 Number of outstanding I/Os: 1 per target
 Transfer request size: 512 B
 Percentage Read/Write Distribution: 100% Read
 Percentage Random/Sequential Distribution: 100% Random
 Transfer delay: 0 ms
 Burst length: 1 I/O
 Warm-up time: 1 minute
Additional VM parameters
 Each test file took up the entirety of a 2GB VHDX, on a separate volume
from the OS
Output
 Latency, IOPS, MBps

VALIDATION AND TEST RESULTS
Nutanix storage cluster on XC630 supporting all application workloads
 SQL/OLTP: 9 instances of SQL 2014 databases (3 per host) - ~340,000 OPM
 LoadGen/Exchange profile: Outlook_50 – 200 mailboxes
 Iometer – File/print workload
 Iometer – Web server workload
Our validation test showed that running nine SQL Server 2014 workloads with
DVD Store, two Microsoft Exchange Server 2013 environments, and six disk workloads
could be readily handled by a three-node cluster of Dell XC630 appliances backed by
Nutanix tiered storage. Median CPU usage on each host was 46.8 percent, so your
business would have room to grow from the configuration validated here (see Figure
26). Storage response time remained low (2.1 milliseconds median) after a slight peak
at the start of the testing as the SQL Server 2014 databases loaded into memory, in spite
of the demand placed on the cluster disks by the Intel Xeon processors E5-2630 v3 (see
Figure 27). The average disk queue length peaked at the beginning as well, though after
that point the queue length stayed consistently sub-20 (see Figure 28). Over the course
of the test, the hosts’ disks put out a median of 7,096 IOPS per host (see Figure 29).
Figure 26: Percentage of processor time used by each Dell XC630 host over the test run.

Figure 27: Average disk queue length for each Dell XC630 host’s disks.
Figure 28: Total disk IOPS performed for each Dell XC630 host’s disks.

Figure 29: Average disk latency for each Dell XC630 host’s disks.
SUMMARY
As this guide has shown, if your business could benefit from using a
hyperconverged computer/storage solution rather than disparate dedicated appliances,
a Nutanix storage cluster powered by Dell XC630 appliances could be the right way to
go. Able to handle nine SQL Server 2014 OLTP workloads at over 340,000 OPM, 200
mailboxes in Microsoft Exchange 2013, as well as file/print and web server disk
workloads, the powerful Dell appliances with the help of Intel processors can keep up
with your current business, with room to grow in the future. With software-defined
tiered storage, high availability, and a redundant network architecture, the small form
factor of the Dell XC630 appliances can help keep your business moving.

APPENDIX A – DETAILED SYSTEM CONFIGURATION
Figure 30 shows the configuration details of the test system.
System Dell XC630-10
Power supplies
Total number 2
Vendor and model number Dell 0TFR9VA01
Wattage of each (W) 1100
General
Number of processor packages 2
Number of cores per processor 8
Number of hardware threads per core 2
System power management policy Performance Per Watt (OS)
CPU
Vendor Intel
Name Xeon
Model number E5-2630 v3
Socket type FCLGA2011-3
Core frequency (GHz) 2.4
Bus frequency 8 GT/s
L1 cache 32 + 32 KB (per core)
L2 cache 256 KB (per core)
L3 cache 20 MB
Platform
Vendor and model number Dell XC630-10
Motherboard model number 0CNCJW
BIOS name and version 1.3.6
BIOS settings Defaults
Memory module(s)
Total RAM in system (GB) 192
Vendor and model number Micron® 36ASF2G72PZ-2G1A2
Type PC4-2133
Speed (MHz) 1,866
Speed running in the system (MHz) 1,866
Size (GB) 16
Number of RAM module(s) 12
Chip organization Double-sided
Rank 2Rx4
Operating system
Name Microsoft® Windows Server® 2012 R2 Datacenter Edition
Build number 9600
Kernel ACPI x64-based PC

System Dell XC630-10
Language English
RAID controller
Vendor and model number PERC H730 Mini
Firmware version 25.3.0.0016
Cache size (GB) 1
RAID configuration None
Hard disk types
SSDs
Vendor and model number Intel SSDSC2BA200G3R
Number of disks 2
Size (GB) 200
RPM N/A
Type SATA 6 Gbps
HDDs
Vendor and model number Seagate® ST91000640SS
Number of disks 7
Size (GB) 1,000
RPM 7,200
Type SATA 6 Gbps
Ethernet adapters
Vendor and model number Intel 4-port X520/I350 rNDC
Firmware 15.0.28
Type On-board
USB ports
Number 2
Type USB 2.0
Figure 30: Configuration specifications of our test system.

APPENDIX B – DETAILED CONFIGURATION METHODOLOGY
Configuring application VMs
Here, we walk through how to configure the applications we tested. We created and configured VMs for
Exchange Server 2013, SQL Server 2014, and Iometer for Hyper-V via PowerShell. The Exchange CAS VMs were
configured with two vCPUs and 16 GB of RAM, and the Exchange Mailbox VMs were configured with four vCPUs and 16
GB of RAM. Each SQL Server 2014 VM was configured with four vCPUs and 24 GB of RAM, and each Iometer VM was
configured with one vCPU and 4 GB of RAM.
Creating VMs for Hyper-V in PowerShell
We used PowerShell to create the VMs for our application environments. Here is a generic sample of the script
we used, which can be readily adjusted as necessary, replacing the variables and paths as appropriate. We created the
VMs on the host we wanted them to reside on, though the host for each VM can be changed in Failover Cluster Manager
after configuring each VM as a role therein.
New-VM -Name $VMNAME -Path PATHTOVMs -Generation 2 -SwitchName
ExternalSwitch Set-VM -Name $VMNAME -MemoryStartupBytes $RAMAMOUNT –StaticMemory
Set-VMProcessor -VMName $VMNAME -Count $VCPUCOUNT
New-VHD -Fixed -SizeBytes $VHDSIZE -Path PATHTO$VHDNAME.vhdx
Add-VMHardDiskDrive -VMName $VMNAME -Path PATHTO$VHDNAME.vhdx
Add-VMDvdDrive -VMName $VMNAME -Path PATHTOINSTALLMEDIA.iso
$dvd = Get-VMDvdDrive -VMName $VMNAME
Set-VMFirmware -VMName $VMNAME -FirstBootDevice $dvd
Start-VM -Name $VMNAME
Configuring Microsoft Exchange 2013 for Load Generator 2013
Preparing AD for Exchange
Perform the following steps once on your infrastructure’s Active Directory server.
1. Insert the Exchange 2012 SP1 Installation ISO in the AD VM DVD drive.
2. In Windows Explorer, double-click the Exchange DVD icon.
3. In the Exchange installation folder, hold down shift, and right-click.
4. Choose Open a command window here.
5. Run the following command: Setup.exe /PrepareSchema
/IAcceptExchangeServerLicenseTerms
6. When the previous command completes, run the following command: Setup.exe /PrepareAD
/OrganizationName:”organization name”
/IAcceptExchangeServerLicenseTerms
7. Close the command window when the setup finishes.

Installing Active Directory Certificate Services
8. Launch Server Manager, and select Add roles and features.
9. At the Add Roles and Features Wizard, click Next.
10. Select Role-based or feature-based installation, and click Next.
11. Choose Active Directory Certificate Services.
12. Click Add Features, if prompted, to install any required features.
13. Click Next.
14. Click Next.
15. Click Next.
16. Choose Certificate Authority and Certification Authority Web Enrollment.
17. Click Add Features, if prompted, to install any required features.
18. Click Next.
19. Leave defaults, and click Next.
20. Click Install.
21. Click Close when the install finishes.
22. Click on the yellow warning symbol in the Server Manager, and click Configure Active Directory
Certificate Services
24. Check both Certification Authority and Certification Authority Web Enrollment, and click Next.
25. Choose Enterprise CA, and click Next.
26. Choose Root CA, and click Next.
27. Choose Create a new private key, and click Next.
30. Leave 5 years, and click Next.
31. Leave default locations, and click Next.
32. Click Configure.
33. Close when the configuration finishes.
34. Open Internet Explorer and navigate to localhost/certsrv/Default.asp to verify that the installation
succeeded.
Installing Exchange Server 2013 SP1 Mailbox and Client Access Server roles
We created two VMs each to serve as Mailbox and CAS servers for our Exchange environments. Edit the
hardware settings in each. The Mailbox servers should have four vCPUs and 16 GB of memory, and the CAS servers
should have two vCPUs and 16 GB of memory. We also provided the Mailbox VMs with an 800GB data disk and a 200GB
logs disk each for Exchange’s database and logs, respectively. We gave each CAS VM a 100GB disk onto which Exchange
will be installed. Set static IPs on all the VMs and join the domain. Run the following commands on both Mailbox VMs
and both CAS VMs as appropriate. By the end of these steps, we had two functional and separate Exchange Server
setups, sharing an Active Directory.

1. On each Mailbox and CAS server, log into the server using domain administrator credentials.
2. Open Windows PowerShell and run the following command:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-
Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-
Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-
PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-
Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-
Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-
Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console,
Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-
Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content,
Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
3. Restart the server.
4. Download the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit.
(go.microsoft.com/fwlink/p/?linkId=258269)
5. Run UcmaRuntimeSetup.exe.
6. When the installation completes, click Finish.
7. Navigate to the location of the Exchange installation media, and double-click Setup.exe.
8. At the Check for Updates? screen, check the Connect to the Internet and check for updates checkbox, and
click Next.
9. When the updates complete, click Next.
10. At the Introduction screen, click Next.
11. At the License Agreement screen, check the box to accept the terms, and click Next.
12. At the Recommended Settings screen, check the Don’t use recommended settings checkbox, and click Next.
13. At the Server Role Selection, select Mailbox or Client Access role as appropriate, and click Next.
14. At the Installation Space and Location screen, provide an appropriate location for the installation, and click
Next.
15. At the Malware Protection Settings, select yes to disable, and click Next.
16. At the Readiness Checks screen, allow the verification to complete. If there are no failures, click Install.
17. When the installation completes, click Finish, and restart the server.
18. Repeat steps 1 through 17 for the remaining Exchange VMs.
Configuring Exchange
1. On the CAS server, open the Exchange Admin Center by using a browser and navigating to
https://localhost/ecp
2. Enter the domain administrator credentials, and click Sign in.
3. If prompted, select the language and time zone, and click Save.
4. In the left pane, click Mail flow, then click Send connectors.
5. On the Send connectors page, click the New icon.

6. In the new Send connectors wizard, specify an appropriate name and select Internet as the type. Click Next.
7. In the Network settings screen, choose MX record associated with recipient domain, and click Next.
8. In the Address space screen, click Add.
9. In the Add domain window, enter the desired address space in the Fully Qualified Domain Name (FQDN)
field, and click Save.
10. Click Next.
11. In Source server screen, click the Add icon.
12. In the Select a Server window, select the mailbox server, click Add, and click OK.
13. Click Finish.
14. In the left pane of the EAC, click servers, select the name of the CAS server, and click Edit.
15. Click Outlook Anywhere, and enter the appropriate FQDN of the Client Access Server for the external and
internal hostname field. For example, exchangeserver.test.local.
16. Choose NTLM as the authentication method, and click Save.
17. Click Virtual Directories, and click the Configure external access domain icon.
18. In the Select the Client Access servers to use with the external URL window, click Add.
19. Select the CAS server, and click Add. Click OK.
20. Type the FQDN of the CAS server in the Enter the domain, and click Save.
21. Log into the Active Directory server using administrator credentials, and complete the following steps:
a. Open Server Manager, then click ToolsDNS
b. In DNS Manager, expand the Active Directory server nameForward Lookup Zonestest.local in
the left pane.
c. In the right pane, verify or create the DNS records as presented in Figure 31.
Type
Host or child
domain/alias name
FQDN
FQDN of mail
server
Mail Exchanger (MX) Leave blank domain.com casserver.domain.com
Alias (CNAME) Autodiscover Autodiscover.domain.com casserver.domain.com
Alias (CNAME) Owa Owa.domain.com casserver.domain.com
Figure 31: DNS records.
22. Log back into your CAS server.
23. In the Exchange Power Shell, run the following commands replacing “$HostName” with the host name (not
FQDN) of your CAS server.
Set-EcpVirtualDirectory "$HostNameECP (Default Web Site)" -InternalUrl
((Get-EcpVirtualDirectory "$HostNameECP (Default Web
Site)").ExternalUrl)
Set-WebServicesVirtualDirectory "$HostNameEWS (Default Web Site)" -
InternalUrl ((get-WebServicesVirtualDirectory "$HostNameEWS (Default Web

Set-ActiveSyncVirtualDirectory "$HostNameMicrosoft-Server-ActiveSync
(Default Web Site)" -InternalUrl ((Get-ActiveSyncVirtualDirectory
"$HostNameMicrosoft-Server-ActiveSync (Default Web Site)").ExternalUrl)
Set-OabVirtualDirectory "$HostNameOAB (Default Web Site)" -InternalUrl
((Get-OabVirtualDirectory "$HostNameOAB (Default Web
Set-OwaVirtualDirectory "$HostNameOWA (Default Web Site)" -InternalUrl
((Get-OwaVirtualDirectory "$HostNameOWA (Default Web
Set-PowerShellVirtualDirectory "$HostNamePowerShell (Default Web Site)"
-InternalUrl ((Get-PowerShellVirtualDirectory "$HostNamePowerShell
(Default Web Site)").ExternalUrl)
Get-OfflineAddressBook | Set-OfflineAddressBook -
GlobalWebDistributionEnabled $True -VirtualDirectories $Null
24. Create a folder at the root of C: on the CAS server, and share it to Everyone with read/write permissions.
25. Log back into the Exchange admin center, and navigate to Serverscertificates.
26. Choose the CAS server in the drop-down menu, and click the plus sign to create a new certificate.
27. Choose Create a request for a certificate from a certification authority, and click Next.
28. Name the certificate, and click Next.
29. Do not request a wildcard certificate, and click Next.
30. Click Browse, choose the CAS server, and click Ok. Click Next.
33. Enter your organization information, and click Next.
34. Enter the path to the share you created on the CAS server, and click Finish. Example:
cassharemyrequest.REQ
35. Log into the AD server, and open Internet Explorer.
36. Browse to localhost/CertSrv
37. Click Request a certificate.
38. Choose advanced certificate request.
39. Choose Submit a certificate request by using a base-64-endcoded CMC…

40. Open Windows Explorer and navigate to the share folder on the CAS server where the certificate request is
stored.
41. Open the certificate with notepad and copy the content between BEGIN NEW CERTIFICATE REQUEST and
END NEW CERTIFICATE REQUEST.
42. Paste the copied content into the Saved Request window.
43. Choose Web Server in the Certificate Template drop-down menu, and click Submit.
44. Choose Base 64 encoded, and download the certificate.
45. Copy the new certificate into the share folder on the CAS server.
46. Log back into the CAS server and open the Exchange Admin Center.
47. Go to serverscertificates, and highlight the certificate you began before (should say Pending request in the
status column).
48. Click Complete on the right side.
49. Type the path to the certificate, including the certificate name, and click ok. Example:
cassharecertnew.CER
50. Verify that the status has changed to Valid.
51. Edit the new entry, and click Edit.
52. Go to services and check SMTP and IIS, click Save.
53. On the warning message, click yes.
54. Perform the following steps on the CAS and AD servers:
a. Click Start, and type MMC
b. Click FileAdd/Remove Snap-in.
c. Choose Certificates, and click Add.
d. Choose Computer account, and click Next.
e. Choose Local computer, and click Finish.
f. Click OK.
g. Expand CertificatesTrusted Root Certificate AuthoritiesCertificates.
h. Click ActionAll TasksImport.
i. Click Next.
j. Browse to the share folder on the CAS server, and choose the new certificate you created. Click
Next.
k. Leave defaults, and click Next.
l. Click Finish.
m. On the Import was successful message, click OK.
55. Log into the CAS server, and open the Exchange admin center.
56. Navigate to serversdatabases.
57. Restart the Microsoft Exchange Information Store service on the MB server.
58. Using the Edit button, disable the maintenance schedule and enable circular logging for each mailbox
database.
59. Dismount and remount the databases.

60. Open Exchange Management shell, and enter the following to move the paths of the default mailbox:
Move-Databasepath “DatabaseName” –EdbFilepath “E:NewlocationDBname.edb”
–LogFolderpath “F:Newlocation”
61. When prompted, type A and press enter.
62. Open Exchange Management Shell, and enter the following:
Get-OutlookAnywhere |Set-OutlookAnywhere -ExternalHostname cas.domain.com
-DefaultAuthenticationMethod NTLM -ExternalClientsRequireSsl $true
Installing and configuring the Exchange 2013 mail test clients and completing LoadGen
configuration on the Exchange 2013
For our testing, we used one virtual client machine to run each instance Load Generator 2013. To create the mail
clients, we installed several software components. We followed this process for each installation:
Installing Windows Server 2008 R2 SP1 Enterprise Edition
1. Insert the installation DVD for Windows Server 2008 R2 SP1 Enterprise into the DVD drive.
2. At the Language Selection Screen, click Next.
3. Click Install Now.
4. Select Windows Server 2008 R2 Enterprise (Full Installation), and click Next.
5. Click the I accept the license terms checkbox, and click Next.
6. Click Custom.
7. Click Next.
8. At the User’s password must be changed before logging on warning screen, click OK.
9. Enter the desired password for the administrator in both fields, and click the arrow to continue.
10. At the Your password has been changed screen, click OK.
11. Click Start, type change power-saving settings and press Enter.
12. Click Change plan settings.
13. Change the Turn off the display drop-down menu to Never.
14. Click Save changes, and close the Power Options, Screen Saver Settings, and Personalization screens.
To set up this server, we had to install several additional software components. The following subsections detail
the necessary installation processes.
Joining the domain
1. Set a static IP.
2. Select StartControl PanelNetwork ConnectionsLocal Area Connection.
3. Click Properties.
4. Highlight Internet Protocol (TCP/IP), and click Properties.
5. Select the Use the following DNS server addresses radio button, and enter the IP of the DNS server in the
Preferred DNS server field. Click OK.
6. Right-click My Computer, and select Properties.
7. Under the Computer Name tab, click Change.

8. In the Computer Name Changes screen, under the Member of section, select the Domain radial box, and
type test.local.
9. Select OK to start joining the domain.
10. When the screen appears asking for a person qualified on the domain, type Administrator as the
username and Password1 as the password.
11. At the Welcome pop-up window and the window warning that you must reset the computer for the changes
to take effect, click OK.
12. At the System Properties screen, click OK.
13. When a pop-up appears asking if you want to restart now, click Yes to restart your computer.
Installing Internet Information Services
1. Click StartAdministrative ToolsServer Manager.
2. On the left pane, click Roles.
3. Click Add Roles.
4. Click the Application Server checkbox.
5. When the Add features required for Application Server? screen appears, click Add Required Features.
6. Click Next.
7. Click Next.
8. At the Select Role Services page for Application Server, click the Web Server (IIS) Support checkbox.
9. Click Add Required Support Role Services.
10. Click Next.
11. Click Next.
12. At the Select Role Services page for Web Server (IIS), click IIS 6 Management Compatibility, ASP, and CGI
checkboxes; and click Next.
13. Click Install.
14. Click Close.
Installing Load Generator
Download and install Load Generator 2013 using all defaults.
Importing the certificate and editing the hosts file
1. Click Start, and type MMC.
2. Click FileAdd/Remove Snap-in.
3. Choose Certificates, and click Add.
4. Choose Computer account, and click Next.
5. Choose Local computer, and click Finish.
6. Click OK.
7. Expand CertificatesTrusted Root Certificate AuthoritiesCertificates.
8. Click ActionAll TasksImport.
9. Click Next.
10. Browse to the share folder on the CAS server, and choose the new certificate you created. Click Next.

12. Click Finish.
13. On the Import was successful message, click OK.
14. Open the Notepad program, and use FileOpen to open the hosts file stored at
C:WindowsSystem32driversetc.
15. Add the IP and FQDN of the CAS server.
16. Save and close Notepad.
Preparing Load Generator
1. Log into the mail client.
2. Select StartAll ProgramsMicrosoft ExchangeExchange Load Generator 2013.
3. When the Load Generator screen appears, select Start a new test.
4. Select Create a new test configuration, and click Continue.
5. Change the total length of simulation to 1 hour.
6. In the Specify test settings screen, type Password1 as the Directory Access Password and Mailbox Account
Master Password, and click Continue with recipient management.
7. Create 750 users in the Mailbox Database, and click Continue.
8. To accept defaults for Advanced recipient settings, click Continue.
9. In the Specify test user groups screen, select the plus sign to add a user group.
10. Change the Client Type to Outlook 2007 Cached, the action profile to Outlook_200, and the Mailbox size to
250 MB, and click Continue.
11. In Remote configurations, click Continue.
12. Click Save the configuration file as, and name it testcfg.xml
13. Click Start the initialization phase (recommended before running the test).
14. Once you have initialized the database, create a backup copy of the Exchange mailbox databases.
Installing and configuring Iometer
1. On the Iometer VMs, navigate to sourceforge.net/projects/Iometer/files/Iometer-stable/1.1.0/Iometer-
1.1.0-win64.x86_64-bin.zip/download in a web browser.
2. Run the installer wizard with defaults.
3. Launch Iometer.
4. In the Topology pane, click the manager with the VM’s host name.
5. In the Disk Targets tab, check the box next to the empty disk to be used for testing.
6. In the Access Specifications tab, click New.
7. Select the new specification, and click Edit.
8. Set the parameters based on the workload you want to test.
9. Click OK.
10. Click Add.
11. In the Test Setup tab, enter the run time details and provide a description for the test.
12. When ready to test, click the green flag button, and provide an output file path.
Installing Microsoft SQL Server 2014
1. Insert the installation DVD for SQL Server 2014 into the DVD drive.

2. Click Run SETUP.EXE. If Autoplay does not begin the installation, navigate to the SQL Server 2014 DVD, and
double-click.
3. If the installer prompts you with a .NET installation prompt, click Yes to enable the .NET Framework Core
role.
4. In the left pane, click Installation.
5. Click New installation or add features to an existing installation.
6. At the Setup Support Rules screen, wait for the check to complete. If there are no failures or relevant
warnings, click OK.
7. Select the Evaluation edition, and click Next.
8. Click the checkbox to accept the license terms, and click Next.
9. Click Install to install the setup support files.
10. If there are no failures displayed, click Next. You may see a Computer domain controller warning and a
Windows Firewall warning. For now, ignore these.
11. At the Setup Role screen, choose SQL Server Feature Installation.
12. At the Feature Selection screen, select Database Engine Services, Full-Text Search, Client Tools Connectivity,
Client Tools Backwards Compatibility, Management Tools – Basic, and Management Tools – Complete. Click
Next.
13. At the Installation Rules screen, once the check completes, click Next.
14. At the Instance configuration screen, leave the default selection of default instance, and click Next.
15. At the Disk space requirements screen, click Next.
16. At the Server configuration screen, choose NT ServiceSQLSERVERAGENT for SQL Server Agent, and choose
NT ServiceMSSQLSERVER for SQL Server Database Engine. Change the SQL Server Agent Startup Type to
Automatic. Click Next.
17. On the Data Directories tab, enter the SQL Server directories of the data and logs volumes created earlier.
18. At the Database Engine Configuration screen, select Mixed Mode.
19. Enter and confirm a password for the system administrator account.
20. Click Add Current user. This may take several seconds.
21. Click Next.
22. At the Error and usage reporting screen, click Next.
23. At the Installation Configuration rules screen, check that there are no failures or relevant warnings, and click
Next.
24. At the Ready to Install screen, click Install.
25. After installation completes, click Close.
26. Download and install Cumulative Update 6 for SQL Server 2014 at support.microsoft.com/en-
us/kb/3031047.

Configuring the database workload client
For our testing, we used a virtual client for the Microsoft SQL Server client. To create this client, we installed
Windows Server 2008 R2, assigned a static IP address, and installed .NET 3.5.
Configuring the database
We generated the data using the Install.pl script included with DVD Store version 2.1 (DS2), providing the
parameters for our 4GB database size and the database platform on which we ran, Microsoft SQL Server 2014. We ran
the Install.pl script on a utility system running Linux. The database schema was also generated by the Install.pl script.
After processing the data generation, we transferred the data files and schema creation files to a Windows-
based system running SQL Server 2014. We built the database in SQL Server 2014, and then performed a full backup,
storing the backup file on the C: drive for quick access. We used that backup file to restore the server between test runs.
The only modification we made to the schema creation scripts were the specified file sizes for our database. We
deliberately set the file sizes higher than necessary to ensure that no file-growth activity would affect the outputs of the
test. Besides this file size modification, the database schema was created and loaded according to the DVD Store
documentation. Specifically, we performed the following steps:
1. We generated the data and created the database and file structure using database creation scripts in the
DS2 download. We made size modifications specific to our database and the appropriate changes to drive
letters.
2. We transferred the files from our Linux data generation system to a Windows system running SQL Server.
3. We created database tables, stored procedures, and objects using the provided DVD Store scripts.
4. We set the database recovery model to bulk-logged to prevent excess logging.
5. We loaded the data we generated into the database. For data loading, we used the import wizard in SQL
Server Management Studio. Where necessary, we retained options from the original scripts, such as Enable
Identity Insert.
6. We created indices, full-text catalogs, primary keys, and foreign keys using the database-creation scripts.
7. We updated statistics on each table according to database-creation scripts, which sample 18 percent of the
table data.
8. On the SQL Server instance, we created a ds2user SQL Server login using the following Transact SQL (TSQL)
script:
USE [master]
GO
CREATE LOGIN [ds2user] WITH PASSWORD=N’’,
DEFAULT_DATABASE=[master],
DEFAULT_LANGUAGE=[us_english],
CHECK_EXPIRATION=OFF,
CHECK_POLICY=OFF
GO

9. We set the database recovery model back to full.
10. We created the necessary full text index using SQL Server Management Studio.
11. We created a database user and mapped this user to the SQL Server login.
12. We then performed a full backup of the database. This backup allowed us to restore the databases to a
pristine state relatively quickly between tests.
Running the test
Test start and run times
We ran the workloads with one client per target database. The specific testing parameters we used for the
benchmark are included below.
About running the DVD Store tests
We created a series of batch files, SQL scripts, and shell scripts to automate the complete test cycle. DVD Store
outputs an orders-per-minute metric, which is a running average calculated through the test. In this report, we report
the aggregate OPM reported by the clients for each run.
Each complete test cycle consisted of the general steps listed below.
1. Clean up prior outputs from the target system and the client driver system.
2. Drop the database from the target servers.
3. Restore the database on the target servers.
4. Shut down the target.
5. Reboot the host and client systems.
6. Wait for a ping response from the server under test (the hypervisor system), the client system, and the
target.
7. Let the test server idle for 10 minutes.
8. Start the DVD Store driver on each client.
We used the following DVD Store parameters for testing:
ds2sqlserverdriver.exe --target=<target_IP> --ramp_rate=10 --run_time=20
--n_threads=64 --db_size=4GB --think_time=0 --detailed_view=Y --
warmup_time=10 --csv_output=<drive path>

APPENDIX C – S4048-ON SWITCH CONFIGURATION
! Version 9.8(0.0P5)
! Last configuration change at Sat Sep 22 06:03:25 2015 by admin
! Startup-config last updated at Sat Sep 22 05:38:40 2015 by default
!
boot system stack-unit 1 primary system: A:
boot system stack-unit 1 secondary system: B:
!
redundancy auto-synchronize full
!
hostname Switch-A
!
default-vlan disable
!
protocol spanning-tree rstp
no disable
bridge-priority 0
!
vlt domain 100
peer-link port-channel 100
back-up destination 192.168.0.82
!
stack-unit 1 provision S4048-ON
!
interface TenGigabitEthernet 1/1
description "uplink to 5448 switch"
no ip address
mtu 12000
speed 1000
!
port-channel-protocol LACP
port-channel 111 mode active
dampening 10 100 1000 60
no shutdown
!
description "XC-node-1a"
no ip address
mtu 12000
portmode hybrid
switchport
no shutdown
!
no ip address
mtu 12000
portmode hybrid
switchport
no shutdown

!
no ip address
mtu 12000
portmode hybrid
switchport
no shutdown
!
!
interface fortyGigE 1/49
description VLT-peerlink
no ip address
no shutdown
!
interface fortyGigE 1/50
description VLT-peerlink
no ip address
no shutdown
!
interface ManagementEthernet 1/1
ip address 192.168.0.81/23
no shutdown
!
interface Port-channel 100
description "VLTi - interconnect link"
no ip address
channel-member fortyGigE 1/49,1/50
no shutdown
!
interface Port-channel 111
description lacp to dell tor
no ip address
mtu 12000
switchport
vlt-peer-lag port-channel 100
no shutdown
!
interface Vlan 1
!
interface Vlan 10
description public-net
no ip address
tagged TenGigabitEthernet 1/2-1/13
tagged fortyGigE 1/51
tagged Port-channel 100,111
no shutdown
!
interface Vlan 100
description priv-net
no ip address

mtu 12000
tagged fortyGigE 1/51
tagged Port-channel 100,111
untagged TenGigabitEthernet 1/2-1/13
no shutdown
!
interface Vlan 101
description Live-Migration
no ip address
mtu 12000
tagged TenGigabitEthernet 1/2-1/13
tagged Port-channel 111
no shutdown
!
ip ssh server enable
!
protocol lldp
advertise management-tlv system-description system-name
!
line console 0
line vty 0
line vty 1
line vty 2
line vty 3
line vty 4
line vty 5
line vty 6
line vty 7
line vty 8
line vty 9
!
reload-type
boot-type normal-reload
config-scr-download enable
!
end

ABOUT PRINCIPLED TECHNOLOGIES
We provide industry-leading technology assessment and fact-based
marketing services. We bring to every assignment extensive experience
with and expertise in all aspects of technology testing and analysis, from
researching new technologies, to developing new methodologies, to
testing with existing and new tools.
When the assessment is complete, we know how to present the results
to a broad range of target audiences. We provide our clients with the
materials they need, from market-focused data to use in their own
collateral to custom sales aids, such as test reports, performance
assessments, and white papers. Every document reflects the results of
our trusted independent analysis.
We provide customized services that focus on our clients’ individual
requirements. Whether the technology involves hardware, software,
Web sites, or services, we offer the experience, expertise, and tools to
help our clients assess how it will fare against its competition, its
performance, its market readiness, and its quality and reliability.
Our founders, Mark L. Van Name and Bill Catchings, have worked
together in technology assessment for over 20 years. As journalists,
they published over a thousand articles on a wide array of technology
subjects. They created and led the Ziff-Davis Benchmark Operation,
which developed such industry-standard benchmarks as Ziff Davis
Media’s Winstone and WebBench. They founded and led eTesting Labs,
and after the acquisition of that company by Lionbridge Technologies
were the head and CTO of VeriTest.
Principled Technologies, Inc.
1007 Slater Road, Suite 300
Durham, NC, 27703
www.principledtechnologies.com
Principled Technologies is a registered trademark of Principled Technologies, Inc.
All other product names are the trademarks of their respective owners.
Disclaimer of Warranties; Limitation of Liability:
PRINCIPLED TECHNOLOGIES, INC. HAS MADE REASONABLE EFFORTS TO ENSURE THE ACCURACY AND VALIDITY OF ITS TESTING, HOWEVER,
PRINCIPLED TECHNOLOGIES, INC. SPECIFICALLY DISCLAIMS ANY WARRANTY, EXPRESSED OR IMPLIED, RELATING TO THE TEST RESULTS AND
ANALYSIS, THEIR ACCURACY, COMPLETENESS OR QUALITY, INCLUDING ANY IMPLIED WARRANTY OF FITNESS FOR ANY PARTICULAR PURPOSE. ALL
PERSONS OR ENTITIES RELYING ON THE RESULTS OF ANY TESTING DO SO AT THEIR OWN RISK, AND AGREE THAT PRINCIPLED TECHNOLOGIES, INC.,
ITS EMPLOYEES AND ITS SUBCONTRACTORS SHALL HAVE NO LIABILITY WHATSOEVER FROM ANY CLAIM OF LOSS OR DAMAGE ON ACCOUNT OF
ANY ALLEGED ERROR OR DEFECT IN ANY TESTING PROCEDURE OR RESULT.
IN NO EVENT SHALL PRINCIPLED TECHNOLOGIES, INC. BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH ITS TESTING, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL PRINCIPLED TECHNOLOGIES, INC.’S
LIABILITY, INCLUDING FOR DIRECT DAMAGES, EXCEED THE AMOUNTS PAID IN CONNECTION WITH PRINCIPLED TECHNOLOGIES, INC.’S TESTING.
CUSTOMER’S SOLE AND EXCLUSIVE REMEDIES ARE AS SET FORTH HEREIN.

Dell XC630-10 Nutanix on Hyper-V reference architecture

More Related Content

What's hot (16)

Similar to Dell XC630-10 Nutanix on Hyper-V reference architecture (20)

More from Principled Technologies (20)

Recently uploaded (20)

Dell XC630-10 Nutanix on Hyper-V reference architecture