Dell EMC Ready Stack: Microsoft Hyper-V on PowerEdge 14G … · 2005-07-14 · Chapter 1: Introduction 6 Dell EMC Ready Stack: Microsoft Hyper-V on PowerEdge 14G Servers and Unity

Dell EMC Ready Stack: Microsoft Hyper-V on PowerEdge 14G Servers and Unity Storage

January 2019

H17514

Deployment Guide

Abstract

This deployment guide describes how to implement a converged infrastructure for Microsoft Hyper-V with Dell EMC 14G rack servers, Unity storage, S-Series switches, and data protection products.

Dell EMC Solutions

Copyright

2 Dell EMC Ready Stack: Microsoft Hyper-V on PowerEdge 14G Servers and Unity Storage Deployment Guide

The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any software described in this publication requires an applicable software license.

Copyright © 2019 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Intel, the Intel logo, the Intel Inside logo and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Other trademarks may be trademarks of their respective owners. Published in the USA 01/19 Deployment Guide H17514.

Dell Inc. believes the information in this document is accurate as of its publication date. The information is subject to change without notice.

Contents


Contents

Chapter 1 Introduction 5

Business value ...................................................................................................... 6

Document scope ................................................................................................... 6

We value your feedback ........................................................................................ 6

Chapter 2 Before You Start 7

Introduction ........................................................................................................... 8

Data center requirements ...................................................................................... 8

Site survey information .......................................................................................... 8

Chapter 3 Technology Overview 9

Ready Stack overview ......................................................................................... 10

Dell EMC components ........................................................................................ 10

Recommended hardware and software ............................................................... 10

Rack layout ......................................................................................................... 11

Cabling ................................................................................................................ 12

Hardware installation checklist ............................................................................ 13

Chapter 4 Configuring Networking 14

Introduction ......................................................................................................... 15

Configuring Dell EMC Networking S5248F-ON switches ..................................... 17

Configuring the Dell EMC Networking S3048-ON switch ..................................... 22

Networking configuration checklist ...................................................................... 24

Chapter 5 Deploying SAN Storage 25

Introduction ......................................................................................................... 26

Deploying Dell EMC Unity storage ...................................................................... 26

Deploying Connectrix DS-6500 switches ............................................................. 26

FC SAN site survey example .............................................................................. 27

Zoning host servers to storage controllers ........................................................... 28

Adding cluster hosts to the storage array ............................................................ 31

Creating a LUN ................................................................................................... 31

Management VMs ............................................................................................... 33

Storage deployment and configuration checklist ................................................. 34

Chapter 6 Deploying the Management Cluster 35

Introduction ......................................................................................................... 36

Preparing management hosts for Windows Server 2016 with Hyper-V ............... 36

Contents


Installing Windows Server 2016 and network drivers on the management server .......................................................................................................... 40

Enabling Hyper-V, failover clustering, and multipath features .............................. 41

Management cluster configuration checklist ........................................................ 44

Chapter 7 Deploying the Compute Cluster 45

Introduction ......................................................................................................... 46

Creating a cluster ................................................................................................ 46

Establishing VM-to-SAN connectivity .................................................................. 46

Creating a VM ..................................................................................................... 47

Verifying the compute cluster deployment ........................................................... 48

Chapter 8 Deploying the Software Components 49

Introduction ......................................................................................................... 50

Deploying the integration and management applications .................................... 50

Deploying the Dell EMC Integrated Data Protection Appliance ........................... 51

Software deployment checklist ............................................................................ 51

Chapter 9 References 52

Dell EMC documentation..................................................................................... 53

Microsoft documentation ..................................................................................... 53

Appendix A Site Survey 54

Site survey tables ................................................................................................ 55

Chapter 1: Introduction


Chapter 1 Introduction

This chapter presents the following topics:

Business value .................................................................................................... 6

Document scope ................................................................................................. 6

We value your feedback ..................................................................................... 6

Chapter 1: Introduction


Business value

Dell EMC Ready Stack presents enterprise-class hardware from Dell EMC in combination

with Microsoft Hyper-V on Microsoft Windows Server 2016 software. Ready Stack is a

flexible architecture model that offers customers a choice in the selection of server,

storage, and networking components. The Ready Stack architecture is designed to scale,

and you can administer and monitor multiple clusters from a single management cluster.

This Ready Stack is designed to provide a stable, highly available platform on which to

run Windows Server 2016 Hyper-V based workloads.

Document scope

This guide describes the steps for deploying Dell EMC Ready Stack for Microsoft Hyper-V on

Windows Server 2016 on the following Dell EMC products: 14G PowerEdge Rack servers,

Unity storage, S-Series and Connectrix switches, and the Integrated Data Protection

Appliance (IDPA). This guide addresses deployment only. For information about the

Ready Stack architecture, see the Dell EMC Ready Stack: Microsoft Hyper-V on PowerEdge

14G Servers and Unity Storage Design Guide.

Dell EMC takes no responsibility for any issues that may be caused to existing

infrastructure components during the deployment of the Ready Stack. While deviations from

the recommended configuration in this guide might be necessary to meet unique

requirements, no warranty is implied or given as to the operation of the Dell EMC Ready

Stack when it is deployed in a modified configuration.

This guide is for Dell EMC personnel, channel partners, and customers. It provides

sample deployment information that Dell EMC Engineering used to test and validate the

Ready Stack. Deployment of individual technology components that are mentioned in this

guide might require specific training, certification, competencies, and other prerequisites.

Deployment personnel must have the required prerequisites and knowledge of data center

infrastructure best practices for servers, storage, networking, data protection, power, and

cooling. To learn more about product competency training and requirements, contact your

Dell EMC Partner or Dell EMC Services.

We value your feedback

Dell EMC and the authors of this document welcome your feedback on the Ready Stack

and the Ready Stack documentation. Contact the Dell EMC Solutions team by email or

provide your comments by completing our documentation survey.

Authors: Scott Stanford, Tom Chatham, David Hartman, Curtis Bunch, Aighne Kearney

Note: For links to additional Ready Stack documentation, see Dell EMC Ready Stack on

DellEMC.com.

Audience

https://www.dellemc.com/resources/en-us/asset/technical-guides-support-information/products/data-protection/h17455_readystack_hyper_v_unity_sg.pdf


mailto:[email protected]?subject=Feedback:%20Dell%20EMC%20Ready%20Stack:%20Microsoft%20Hyper-V%20on%20PowerEdge%2014G%20Servers%20and%20Unity%20Storage%20Deployment%20Guide%20(H17514)

https://www.surveymonkey.com/r/SolutionsSurveyExt

https://www.dellemc.com/en-us/solutions/ready/readystack.htm

Chapter 2: Before You Start


Chapter 2 Before You Start


Introduction ......................................................................................................... 8

Data center requirements .................................................................................... 8

Site survey information ...................................................................................... 8

Chapter 2: Before You Start


Introduction

This guide makes assumptions about your existing infrastructure and the services that are

available on your network. Ensure that your environment meets the predeployment

requirements that are described in this chapter.

Data center requirements

The customer environment must include:

An existing Ethernet infrastructure. Ready Stack components require Dell EMC

Networking S5248F-ON switches or other Dell EMC Networking or customer-

provided switches that support 10/25 GbE and 40/100 GbE uplinks to an existing

Ethernet infrastructure. Additional components such as Dell EMC network cables

and transceivers are also needed.

Active Directory Services, Domain Name System (DNS), and Network Time

Protocol (NTP) services on the management network. While it is possible to use IP

address management services such as Dynamic Host Configuration Protocol

(DHCP), we recommend static IP assignments for all Ready Stack components.

Sufficient power and cooling to support all components. For more information, see

the relevant product documentation.

Site survey information

A site survey is an inspection of a proposed deployment site to collect information about

the initial tasks that are required for the deployment.

Appendix A describes the network information that is required to deploy this Dell EMC

Ready Stack. We recommend that you collect this information before starting the

deployment. The examples that we use throughout this guide contain data that is typical of

information that is collected during a standard site survey.

Before starting deployment, read the Dell EMC Ready Stack: Microsoft Hyper-V on

PowerEdge 14G Servers and Unity Storage Design Guide.

Essential

reading



Chapter 3: Technology Overview


Chapter 3 Technology Overview


Ready Stack overview ...................................................................................... 10

Dell EMC components ...................................................................................... 10

Recommended hardware and software ........................................................... 10

Rack layout ........................................................................................................ 11

Cabling ............................................................................................................... 12

Hardware installation checklist ........................................................................ 13



Ready Stack overview

This chapter describes the components of the Ready Stack and their physical layout if

installed in a single rack that includes cabling for power and network connectivity.

For instructions about rack installation of individual components, see the relevant product

documentation on Dell EMC Online Support.

Dell EMC components

This Ready Stack uses the following Dell EMC components:

Unity All Flash and Hybrid Flash storage

14G PowerEdge rack servers

S-Series S5248F-ON and S3048-ON switches

Connectrix DS-6500B series switches

IDPA DP4400 data protection

Recommended hardware and software

The following table lists the minimum software and firmware versions that Dell EMC

recommends for use with this Ready Stack release.

Table 1. Recommended hardware and software

Layer Device Version

Server PowerEdge R640 BIOS 1.3.7

iDRAC 3.15.17.15 PowerEdge R740/R740xd

Mellanox CX4 LX dual-port rNDC Driver 1.80.06

Firmware 2.0

QLogic 2692 dual-port Fibre Channel HBA Driver 34.07.00

Firmware 14.07.05

Dell EMC PERC H730p Driver 6.604.06.00

Firmware 25.5.5.0005

Dell EMC BOSS controller card+ with 2 x M.2 sticks 120 GB (RAID 1), LP

Driver 1.2.0.1048

Firmware 2.5.13.3011

Network Dell EMC Networking S3048-ON OS 10.4.2.0

Dell EMC Networking S5248F-ON OS 10.4.2.0

Storage Dell EMC Unity x50F 4.4.1

Connectrix DS-6500 Fabric OS 8.2.0

https://www.dell.com/support/home/us/en/04/product-support/product/poweredge-r740/drivers



Layer Device Version

Software Windows Server 2016 with Hyper-V Role Version 1803

Microsoft System Center Configuration Manager (SCCM)

1802

Microsoft System Center Virtual Machine Manager (SCVMM)

1801

Dell EMC OpenManage Integration for Microsoft System Center (OMIMSSC)

7.0

Dell EMC IDPA DP4400 2.2

Note: The BIOS, driver, and firmware versions are subject to change. For more information, see

Dell EMC Online Support. As an example, at Support for PowerEdge R740, under Drivers &

downloads, you can search by keyword or filter by category to locate a specific device.

Rack layout

The Ready Stack physical rack layout is flexible and can accommodate many data center

dependencies on power, thermals, and weight. PowerEdge rack servers require either 1U

or 2U of rack space depending on the model, and the compute server quantity can

change depending on the needs of the organization. Dell EMC Unity storage can require

fewer or more disk enclosures depending on the storage capacity and SSD drive type.

The following figure shows an example of the Ready Stack Enterprise Large configuration.

Figure 1. Ready Stack components in Enterprise Large configuration: Front rack view

https://www.dell.com/support/home/us/en/04/




Cabling

The following figure shows the cabling diagram for all the Ready Stack components.

100 GbE requires QSFP28 cabling and 25 GbE requires SFP28 cabling. We recommend

Dell EMC Networking passive copper direct attach cables. These cables are available in

various lengths based on the rack layout. Dell EMC Networking active optical cables are

also available for longer distances and dense rack configurations.

Figure 2. Ready Stack network cabling diagram

Connectrix DS-6500 switches are prepopulated with the required Fibre Channel (FC)

optics. The following is a high-level summary of the required cable components for the

switches, servers, and storage that are shown in Figure 2:

Additional 16 GB SFP FC adapters for Unity arrays and PowerEdge servers.

An LC-LC optical multimode cable between PowerEdge servers and Unity arrays

to Connectrix FC switches.

Cat 5e Ethernet cabling for Dell EMC iDRAC, Connectrix, and Unity management.

For small configurations, it is possible to cable 1 GbE devices to top-of-rack (ToR)

switches using a 1000Base-T small form-factor pluggable (SFP) transceiver.

Doing this can eliminate the need for the Dell Networking S3048-ON switch in

some cases. However, as a best practice, we recommend using a dedicated out-

of-band (OOB) management switch.



Hardware installation checklist

Ensure that the following hardware installation procedures are complete:

Hardware components (switches, storage, and servers) are installed into racks.

Network connections are cabled from switches to servers, as shown in Figure 2.

Power is cabled to each component (not shown for all components in Figure 2).

Chapter 4: Configuring Networking


Chapter 4 Configuring Networking


Introduction ....................................................................................................... 15

Configuring Dell EMC Networking S5248F-ON switches ............................... 17

Configuring the Dell EMC Networking S3048-ON switch ............................... 22

Networking configuration checklist ................................................................. 24



Introduction

This chapter describes how to configure this Ready Stack for Networking S3048-ON OOB

management and S5248F-ON ToR switches. These steps are provided as an example of a

working configuration. Ensure that you review the steps with your site networking team

before performing them.

Note: This Ready Stack solution supports other switch models in the Dell EMC Networking

portfolio, such as the S4148T-ON and the S5232-ON switches. However, the S5232F-ON and

S3048-ON switches that this sample configuration uses do not require additional breakout cabling

for lower-link speed devices and may help reduce cost and cabling complexity.

This networking site survey topology is intended as an example. Before starting

deployment, complete the full survey, which is available in Appendix A.

Confirm all the information in the following tables, especially Spanning Tree Protocol

(STP) information, with the personnel who are responsible for the network configuration in

your environment.

Table 2. Switch hostnames example

Switch Hostname VLT backup address VLT ports

S3048-ON SWOOB

S5248F-Top SW1 192.168.1.253/24 Ethernet 1/1/53-1/1/54

S5248F-Bottom SW2 192.168.1.252/24 Ethernet 1/1/53-1/1/54

Table 3. VLAN information example

Network type

VLAN ID

S5248F-Top IP CIDR

S5248F-Bottom IP CIDR

VRRP IP address

VRRP group

S3048-ON IP

OOB 100 172.90.100.252/24 172.90.100.253/24 172.90.100.254 1 172.90.100.25

Management 110 172.90.110.252/24 172.90.110.253/24 172.90.110.254 2

Live migration

120 172.90.120.252/24 172.90.120.253/24 172.90.120.254 3

Compute 210 172.90.210.252/24 172.90.210.253/24 172.90.210.254 4

Table 4. Customer network services example

Service IP address

Core network gateway 172.90.100.250

Networking site

survey

information



Table 5. Switch port mappings example

Component S5248F-Top S5248F-Bottom S3048-ON

Server NIC Port 1 NIC Port 2 iDRAC

Mgmt1 Ethernet 1/1/1 Ethernet 1/1/1 Ethernet 1/1/1

Mgmt2 Ethernet 1/2/1 Ethernet 1/2/1 Ethernet 1/2/1

Comp1 Ethernet 1/3/1 Ethernet 1/3/1 Ethernet 1/3/1



You need a laptop with a serial connection and terminal emulation software such as

PuTTY.

This guide uses certain typographical conventions to mark commands and screen output.

Information that is specific to your environment or site survey is placed inside <> symbols

and presented in italics. For example:

Deployment guide command reference: OS10(config)# hostname

<hostname>

On the top S5248F-ON switch, enter: OS10(config)# hostname SW1

On the bottom S5248F-ON switch, enter: OS10(config)# hostname SW2

When an input command is different between the top and the bottom switch but the

information is not part of the site survey, an indentation identifies the different commands.

Use the command with the preceding hostname for the switch you are configuring. For

example:

SW1(config)# spanning-tree mode rstp #Command entered on both

switches

SW1(config)# spanning-tree rstp priority 4096 #Command for

Top S5248F-ON

SW2(config)# spanning-tree rstp priority 8192 #Command for

Bottom S5248F-ON

Screen output is presented in bold. Optional commands are shown in bold italics.

Prerequisites

Typographical

conventions



Configuring Dell EMC Networking S5248F-ON switches

This section describes a minimal configuration for your Dell EMC Networking S5248F-ON

switches to support the Ready Stack. Additional configuration might be necessary for your

environment and to configure communication to your core data center network.

If you are not familiar with configuring the Dell EMC Networking S5248F-ON switch, see

the S5248F-ON documentation on Dell EMC Online Support.

Configure the S5248F-ON switches:

1. Using the RJ45 serial cable included with your switch, connect one end to your

workstation and the other end to the RS-232 console port of the switch.

The following figure shows the console and management ports. The console port

is located on the upper right side of the switch when you are looking at the back

portion near the fans and power supplies.

Figure 3. Serial port

2. Using terminal emulation software, configure the appropriate COM port as follows:

15200 baud rate

No parity/no flow control

8 data bits/1 stop bit

3. When the connection is successful, enter configuration mode by running the

following command:

OS10# configure terminal

4. Configure the hostname and time zone and set a username and password for

EXEC mode by running the following commands:

OS10(config)# hostname <hostname>

SW1(config)# username <username> password <password> role

sysadmin

SW1(config)# clock timezone <time zone, for example, CST -6

0>

Configure the

S5248F-ON

switchesProcedu

re

https://www.dell.com/support/home/us/en/04/product-support/product/networking-s5248f-on/manuals



5. Configure routing to your default gateway, and save the configuration by running

the following commands:

SW1(config)# ip route 0.0.0.0/0 <core network gateway>

SW1(config)# do write memory

The VLTi heartbeat uses the management interface on the back of the Dell EMC

Networking S5248F-ON switch, which is connected with a Cat 5e Ethernet network cable

from the top S5248F-ON switch to the bottom S5248F-ON switch. To configure the

management interface, go into global configuration mode on the switch and follow these

steps:

1. Configure the management port by running the following commands:

SW1(config)# interface mgmt 1/1

SW1(conf-if-ma-1/1/1)# no ip address dhcp

SW1(conf-if-ma-1/1/1)# ip address 192.168.1.252/24

SW2(conf-if-ma-1/1/1)# no ip address dhcp

SW2(conf-if-ma-1/1/1)# ip address 192.168.1.253/24

SW1(conf-if-ma-1/1/1)# exit

2. Enable SPT by running the following commands:

SW1(config)# spanning-tree mode rstp

SW1(config)# spanning-tree rstp priority 16384

SW2(config)# spanning-tree rstp priority 32768

Caution: Ensure that the personnel responsible for network management in your

environment have reviewed the configuration for SPT because incorrect settings may

cause network issues. The values provided here are examples only.

Configure the ports to be used for VLTi traffic:

1. Run the following commands:

SW1(config)# interface range ethernet 1/1/53-1/1/54

SW1(conf-range-eth1/1/53-1/1/54)# description VLTi

SW1(conf-range-eth1/1/53-1/1/54)# no switchport

SW1(conf-range-eth1/1/53-1/1/54)# exit

2. Create the VLT domain and add the discovery interfaces:

SW1(config)# vlt-domain 1

SW1(conf-vlt-1)# backup destination 192.168.1.253

SW2(conf-vlt-1)# backup destination 192.168.1.252

SW1(conf-vlt-1)# discovery-interface ethernet 1/1/53-1/1/54

SW1(conf-vlt-1)# do write memory

3. Ensure that the VLT domain is properly configured by running the following

command in enable mode:

SW1# show vlt 1 | find Status

The following output appears:

Configure the

management

interface

Configure the

VLTi



VLTi Link Status

port-channel1000 : up

VLT Peer

Unit ID System MAC Address Status IP Address Version

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

1 54:bf:64:be:f7:40 up 192.168.1.253 2.0

4. Run the following commands to configure the ports that the servers are connected

to on the switch. Based on the site survey example, ports Ethernet 1/1/1 through

Ethernet 1/1/16 are in use on each switch.

SW1(config)# interface range ethernet 1/1/1-1/1/16

SW1(conf-range-eth1/1/1-1/1/16)# no ip address

SW1(conf-range-eth1/1/1-1/1/16)# mtu 9216

SW1(conf-range-eth1/1/1-1/1/16)# switchport mode trunk

SW1(conf-range-eth1/1/1-1/1/16)# switchport access vlan 100

SW1(conf-range-eth1/1/1-1/1/16)# switchport trunk allowed

vlan 110,120,210

SW1(conf-range-eth1/1/1-1/1/16)# spanning-tree port type

edge

SW1(conf-range-eth1/1/1-1/1/16)# spanning-tree guard root

SW1(conf-range-eth1/1/1-1/1/16)# no shutdown

5. Verify that the ports are properly configured by running the following command:

SW1(conf-range-eth1/1/1-1/1/16)# show config

The output for each port appears as follows:

interface ethernet1/1/1

no shutdown

switchport mode trunk

switchport access vlan 100

switchport trunk allowed vlan 110,120,210

mtu 9216

flowcontrol receive off

spanning-tree guard root

spanning-tree port type edge

!

…

This section describes how to configure the VLANs on the S5248F-ON switch. The

examples show how to configure each VLAN in the site survey. Server NIC ports 1 and 2

are used for all traffic. If your configuration does not use spine/leaf network architecture or

if you do not want VLAN traffic to be routed by the S5248F-ON switches, skip the

commands in bold italics.

Follow these steps:

1. Configure the OOB VLAN:

SW1(config)# interface vlan 100

SW1(conf-if-vl-100)# description “out-of-band VLAN”

Configure the

VLANs



SW1(conf-if-vl-100)# ip address 172.90.100.252/24

SW1(conf-if-vl-100)# mtu 9216

SW1(conf-if-vl-100)# vrrp-group 1

SW1(conf-if-vlan100-vrid-1)# virtual-address 172.90.100.254

SW1(conf-if-vlan100-vrid-1)# exit

SW1(conf-if-vl-100)# no shutdown

SW1(conf-if-vl-100)# exit

SW1(config)# do write

Note: You can connect iDRAC ports to the ToR switch as necessary. Use the same

configuration as in this step. The configuration is the same as in the preceding steps. The

Virtual Router Redundancy Protocol (VRRP) implementation is optional.

2. Configure the management VLAN by running the following commands:


SW1(conf-if-vl-110)# description “Management VLAN”









3. Configure the live migration VLAN by running the following commands:


SW1(conf-if-vl-120)# description “Live Migration VLAN”









4. Configure the compute VM VLAN by running the following commands:


SW1(conf-if-vl-210)# description “Compute VM VLAN”











5. To verify that all the settings have been properly recorded, review the configuration

from enable mode by running the following command:

SW1# show running-config

6. Repeat the preceding steps to configure the bottom Dell EMC Networking

S5248F-ON switch in the configuration.

The Networking S3048-ON switch connects to the network through the Networking

S5248F-ON switches using a port channel that consists of one interface on each

Networking S5248F-ON switch. Follow these steps:

1. Configure the port-channel that will be used by running these commands:

SW1(config)# interface port-channel 101

SW1(conf-if-po-101)# description “OOB uplink”

SW1(conf-if-po-101)# no shutdown

SW1(conf-if-po-101)# switchport mode trunk

SW1(conf-if-po-101)# switchport trunk allowed vlan

100,110,120,210

SW1(conf-if-po-101)# mtu 9216

SW1(conf-if-po-101)# vlt-port-channel 101

SW1(conf-if-po-101)# exit

2. Configure the port that will be used for the port channel by running these

commands:

SW1(config)# port-group 1/1/12

SW1(conf-pg-1/1/12)# mode Eth 10g-4x

SW1(conf-pg-1/1/12)# exit

SW1(config)# interface ethernet 1/1/48:1

SW1(conf-if-eth1/1/48:1)# no shutdown

SW1(conf-if-eth1/1/48:1)# description “OOB uplink”

SW1(conf-if-eth1/1/48:1)# channel-group 101 mode active

SW1(conf-if-eth1/1/48:1)# mtu 9216

SW1(conf-if-eth1/1/48:1)# exit

3. Repeat the preceding steps to configure the bottom Dell EMC Networking S5248F-

ON switch.

Configure the

port channel



Configuring the Dell EMC Networking S3048-ON switch

The Dell EMC Networking S3048-ON switch serves as the OOB management switch for

the Ready Stack. A single switch is used because this connectivity is not considered

critical for workload operations. To begin configuring the switch, use a laptop with a serial

connection and terminal emulator software such as PuTTY.

Perform the following steps to configure the Dell EMC Networking S3048-ON switch.

Note: After Step 2, the commands are the same as for configuration of the S5248F-ON switch.

See Configuring Dell EMC Networking S5248F-ON switches on page 17.

1. Using an RJ45 to serial cable included with your switch, connect one end to your

workstation and the other end to the RS-232 console port of the switch, as shown

in the following figure.

Figure 4. Serial port

2. Using terminal emulation software, configure the appropriate COM port as follows:

115200 baud rate



3. After a successful connection, enter configuration mode by running the following

commands:

OS10# configure terminal

4. Configure the hostname and time zone, and set a username/password for EXEC

mode by running the following commands:

OS10(config)# hostname SWOOB

SWOOB(config)# username <username> password <password> role

sysadmin

SWOOB(config)# clock timezone <time zone, example CST -6 0>

5. Configure routing to your default gateway and save the configuration by running

the following commands:

SWOOB(config)# ip route 0.0.0.0/0 172.90.100.254

SWOOB(config)# do write

Configure the

S3048-ON switch



Configure the ports that the management servers’ iDRAC cards are connected to on the

switch. In this example, ports 1/1 to 1/3 are used for the management server’s iDRAC.

1. Run the following commands:

SWOOB(config)# interface range ethernet 1/1/1-1/1/3

SWOOB(conf-range-eth1/1/1-1/1/3)# no shutdown

SWOOB(conf-range-eth1/1/1-1/1/3)# no ip address

SWOOB(conf-range-eth1/1/1-1/1/3)# switchport access vlan 100

SWOOB(conf-range-eth1/1/1-1/1/3)# spanning-tree port type edge

SWOOB(conf-range-eth1/1/1-1/1/3)# mtu 9216

2. Verify that the ports are properly configured by running the following command:

SWOOB(conf-range-eth1/1/1-1/1/3)# show configuration

The following output is displayed for each port:

interface ethernet1/1/1

no shutdown

switchport access vlan 100

mtu 9216

flowcontrol receive on

spanning-tree port type edge

!

…

The Dell EMC Networking S3048-ON switch connects to the network through the Dell

EMC Networking S5248F-ON VLT domain using a port channel consisting of two 10 GbE

ports on the Networking S3048-ON switch. Follow these steps to first configure the ports

for the port channel and then create the port channel.

1. Configure the OOB VLAN on the switch by running the following commands:

SWOOB(config)# interface vlan 100

SWOOB(conf-if-vl-100)# description “out-of-band VLAN”

SWOOB(conf-if-vl-100)# no shutdown

SWOOB(conf-if-vl-100)# ip address 172.90.100.25/24

SWOOB(conf-if-vl-100)# mtu 9216

SWOOB(conf-if-vl-100)# exit

SWOOB(config)# do write

2. Create the port channel by running the following commands:

SWOOB(config)# interface port-channel 101

SWOOB(conf-if-po-101)# description “OOB uplink”

SWOOB(conf-if-po-101)# no shutdown

SWOOB(conf-if-po-101)# switchport mode trunk

SWOOB(conf-if-po-101)# switchport trunk allowed vlan 100

SWOOB(conf-if-po-101)# mtu 9216

SWOOB(conf-if-po-101)# exit

3. Configure the ports that will be used for the port channel by running the following

commands:

Configure the

management

interface

Configure the

port channel



SWOOB(config)# interface range ethernet 1/1/49-1/1/50

SWOOB(conf-range-eth1/1/49-1/1/50)# description “OOB uplink”

SWOOB(conf-range-eth1/1/49-1/1/50)# no shutdown

SWOOB(conf-range-eth1/1/49-1/1/50)# channel-group 101 mode

active

SWOOB(conf-range-eth1/1/49-1/1/50)# mtu 9216

SWOOB(conf-range-eth1/1/49-1/1/50)# exit

4. Verify that the port-channel to the S5248F-ON is up by running the following

command:

SW00B# show interface port-channel summary

LAG Mode Status Uptime Ports

10 L2-HYBRID up 2 days Eth 1/1/49 (Up)

Eth 1/1/50 (Up)

Networking configuration checklist

Ensure that the following network configurations are complete:

S5248F-ON switches are configured.

S5248F-ON switches are connected to the corporate network.

S3048-ON switch is configured.

S3048-ON switch is connected to the S5248F-ON switches.

Chapter 5: Deploying SAN Storage


Chapter 5 Deploying SAN Storage


Introduction ....................................................................................................... 26

Deploying Dell EMC Unity storage ................................................................... 26

Deploying Connectrix DS-6500 switches ........................................................ 26

FC SAN site survey example ............................................................................ 27

Zoning host servers to storage controllers ..................................................... 28

Adding cluster hosts to the storage array ....................................................... 31

Creating a LUN .................................................................................................. 31

Management VMs .............................................................................................. 33

Storage deployment and configuration checklist ........................................... 34



Introduction

This chapter describes how to deploy the Unity storage array for the Ready Stack. For

enclosure cabling guidelines, consult your Dell EMC Sales representative.

Deploying Dell EMC Unity storage

1. Connect all power cords and management cables to the appropriate networks.

2. Ensure that any additional drive array enclosures are connected.

3. Connect the Unity array to the network.

A best practice is to configure the array with a static IP address. You can assign

the management IP address for the Unity system statically or dynamically:

Dynamic―If DHCP is supported on your network, the Unity system

automatically obtains a network address when you power it up.

Static―Download, install, and run the Connection Utility software on a

computer with access to the subnet where you installed your Unity system.

Ensure that you have the serial number of the Unity system, and the IP

address, the subnet mask, and the default gateway that you want to use. This

information is part of the site survey in Appendix A.

4. Launch Unisphere storage management:

a. Open your web browser, enter the IP address from step 3 as the destination,

and log in with the default credentials:

Username―admin

Password―Password123#

Follow the initial configuration wizard through basic settings such as

licensing, storage pool creation, alerts, support, and networking.

You can perform these tasks from the Dell EMC Unisphere interface at any

time by clicking the gear icon in the top menu bar to open the Settings page.

Deploying Connectrix DS-6500 switches

The Ready Stack uses Dell EMC Connectrix switches for FC storage traffic. Two

Connectrix DS-6505B or DS-6510B series switches make up the FC fabrics. For FC

guidelines for storage array and hosts, consult your Dell EMC Sales representative.

1. Connect all power cords and management cables.

2. Connect your setup computer COM port to the serial port on the switch using the

serial cable that shipped with the switch.

The serial connection settings are as follows:

9600 bits per second





3. Open a terminal emulator program such as PuTTY.

4. Power on the switch.

5. Verify that the switch has completed the boot process and that the operating

system image is available.

6. From the terminal emulator program, log in to the switch console using the default

credentials:

Username: admin

Password: password

7. When prompted, change the password.

8. Type ipAddrSet and press Enter to start the IP configuration dialog, and then

configure the following settings:

DHCP—Select On or Off (the default is Off).

Ethernet IP Address—Set the IP address for the switch.

Ethernet Subnet mask—Set the subnet mask for the switch.

Gateway IP Address—Set the default gateway for the switch.

9. Close the terminal emulator program and disconnect the serial cable from the

switch.

10. Repeat the process on the bottom switch if necessary.

11. Verify that the FC switches are visible on the network.

FC SAN site survey example

The following table shows an example of FC port mappings.

Table 6. FC port mappings example

FC port WWN Alias

SP-A P0 50:06:01:64:47:e0:01:96 spa_p0

SP-A P1 50:06:01:65:47:e0:01:96 spa_p1

SP-A P2 50:06:01:66:47:e0:01:96 spa_p2

SP-A P3 50:06:01:67:47:e0:01:96 spa_p3

SP-B P0 50:06:01:6c:47:e0:01:96 spb_p0

SP-B P1 50:06:01:6d:47:e0:01:96 spb_p1

SP-B P2 50:06:01:6e:47:e0:01:96 spb_p2

SP-B P3 50:06:01:6f:47:e0:01:96 spb_p3

Mgmt1 P1 21:00:00:24:ff:7d:9a:35 mgmt1_p1

Mgmt1 P2 21:00:00:24:ff:7d:9a:34 mgmt1_p2



FC port WWN Alias

Mgmt2 P1 21:00:00:24:ff:7d:9a:33 mgmt2_p1

Mgmt2 P2 21:00:00:24:ff:7d:9a:32 mgmt2_p2

Comp1 P1 21:00:00:24:ff:7f:09:51 comp1_p1

Comp1 P2 21:00:00:24:ff:7f:09:50 comp1_p2

Comp2 P1 21:00:00:24:ff:7f:08:f9 comp2_p1

Comp2 P2 21:00:00:24:ff:7f:08:f8 comp2_p2

Comp3 P1 21:00:00:24:ff:7f:08:cf comp3_p1

Comp3 P2 21:00:00:24:ff:7f:08:ce comp3_p2

Zoning host servers to storage controllers

Zone the management and compute hosts to the storage controllers:

1. From a web browser, start Brocade Web Tools by entering the IP address of the

switch in the address bar.

If Java issues prevent you from accessing Web Tools from a browser, run the

following command from a command prompt:

javaws "http://[your switch ip

address]/switchExplorer_installed.html"

2. Create a zone configuration:

a. Log in to Web Tools with administrator credentials.

b. Select Configure > Zone Admin.

The Zone Administration window appears, as shown in the following figure.



Figure 5. Zone Administration screen

On the Zone Config tab, click New Zone Config.

A Create New Config dialog box appears

d. Enter a name for the new configuration and click OK.

3. Create aliases for the storage controller front-end FC ports:

a. On the Alias tab in the Zone Administration window, click New Alias.

A Create New Alias dialog box appears.

b. Enter a name for the new alias, for example, Unity_SPA_P0, and then click

OK.

c. Select Member Selection List > Ports & Attached Devices to view the

nested elements.

d. Expand the port that contains the WWN for the alias being created, as shown

in the following figure.

You can find the WWNs of Unity front-end ports in Unisphere storage

management.

Figure 6. Port with WWN



Click the port WWN, and then click the right arrow to add the WWN to the

Alias Members list.

Repeat steps a through e to create aliases for all storage controller front-end

ports.

Select Action > Save Config to save your configuration changes.

4. Create aliases for the WWN of the management and compute servers:

a. In the Zone Administration window, on the Alias tab, click New Alias.

The Create New Alias dialog box appears.

Enter a name for the new alias, for example, MGMT_SVR_P1, and then click

OK.

Select Member Selection List > Ports & Attached Devices to view the nested

elements.

Expand the port that contains the WWN for the alias being created.

Click the port WWN, and then click the right arrow to add the WWN to the

Alias Members list.

You can find server HBA WWNs in the iDRAC console hardware inventory.

Repeat steps a through e to create aliases for all management and compute

server HBAs.

Select Action > Save Config to save your configuration changes.

5. Create zones:

In Web Tools, click Configure > Zone Admin.

The Zone Config panel appears, as shown in the following figure.

Figure 7. Zone Config panel

Click New Zone.

Enter a name for the new zone in the field that is provided and click OK.

6. Create aliases:

Select Member Selection List > Aliases to view the nested elements.

In the Member Selection List, select all the aliases of the Unity storage

ports and the server WWN to be included in the zone.



Click the right arrow to add the aliases to Zone Members.

Repeat steps 5b through 6c to create zones for all management and

compute servers

Select Zoning Actions > Save Config to save the configuration changes.

7. Enable configuration:

a. Select the Zone Config tab,.

Under Member Selection List, expand Zones to view the nested elements.

Select all the zones that you created for the management and compute hosts

in the preceding steps.

Click the right arrow to move the selected zones in the Member Selection

List to Zone Config Members.

Click Save Config to save the configuration.

Click Enable Config and select the name of the zone configuration.

Click OK to enable the zone configuration.

Adding cluster hosts to the storage array

Add cluster hosts to the storage array:

1. For each server to be added to the storage array, obtain the HBA’s WWNs from

the server’s iDRAC:

a. Log in to the iDRAC, expand Hardware, and then click Fibre Channel

devices.

Expand any device under Fibre Channel Ports to view the port’s WWN.

2. Log in to Unisphere storage management.

3. Select Access > Hosts.

4. In the upper left of the Hosts pane, click the plus sign (+).

5. In the Name field, enter the server name and click Next.

All discovered initiators are shown under Automatically Discovered Initiators.

6. Select the WWN of the server that is being added to the storage array, and then

click Next.

7. Review the selections and, if you are satisfied, click Finish.

8. Repeat steps 5 through 7 for all management and compute servers to be added

to the storage array.

Creating a LUN

The LUNs that you create and present to the management cluster are used as datastores

for the management virtual machines (VMs). You can also create any additional LUNs

that you need for management and compute clusters.



To create a LUN, log in to Unisphere storage management and follow these steps:

1. Create the required number of storage pools.

For size requirements, see Table 7, Management VM space requirements.

The number and size of the required pools depend on the specific needs of the

environment and the number of available drive types in the storage array.

2. In the left navigation pane, click Block.

3. In the upper left of the LUNs pane, click the plus sign (+).

4. In the Create LUNs wizard:

a. From the Number of LUNs list, select 1.

In the Name field, enter a name for the LUN.

From the Pool list, select the pool from which the LUN is to be created.

In the Size field, enter the size of the LUN.

Table 7 lists the management VM space requirements. For information about

the storage requirements for the VMs, see Chapter 8, Deploying the

Software Components.

5. If a thin LUN is required, select the Thin option.

A thick LUN is created by default.

6. Click Next.

7. In the upper left of the Configure Access pane, click the plus sign (+).

8. In the Select Host Access window, select the management hosts that require

access to the LUN, and then click OK.

9. In the Access pane, review the host selection and click Next.

10. In the Snapshot pane, select Enable Automatic Snapshot Creation, if required,

and then click Obtain the HBA’s WWNs.

11. In the Replication pane, if replication is being configured for the LUN, select

Enable Replication and then select your required replication settings.

12. In the Summary pane, review the selections and, if you are satisfied, click Finish.

13. In the Results pane, click Close.

14. If additional LUNs are required for additional management VMs, repeat steps 4

through 12 to create a datastore of a size that can accommodate all the

management VMs.

For the example in Table 8, a 2 TB LUN is sufficient.

15. Repeat steps 4 through 13 to create additional LUNs as needed and assign them

to appropriate hosts.



Management VMs

The following table provides an overview of the requirements for the management VM

resources, along with additional reference information.

Note: The sizes might require adjustment based on customer requirements.

Table 7. Management VM space requirements

Resource Requirements

Hyper-V Cluster

For more information, see Use Cluster Shared Volumes in a failover cluster in Windows IT Pro Center.

Cluster shared volume: 2 TB

Quorum volume: 1 GB

SCVMM

For more information, see the following articles in Windows IT Pro Center:

System requirements for System Center Virtual Machine Manager

Plan VMM installation

Dell EMC recommends that you allow more than the 32 GB absolute minimum for Windows Server 2016 disk space requirements. For more information, see the System Requirements for Windows Server 2016 in Windows IT Pro Center.

VMM server: 10 GB

VMM database: 200 GB

We recommend separate disks for database, logs, and backup.

Disk sizes vary based on the deployment requirements.

VMM library: Depends on number of files stored

VMM console: 10 GB

Windows Server 2016 guest operating system: 240 GB

If you plan to run each SCVMM feature in a separate guest operating system, size the LUN to allow for three additional 240 GB guest operating systems.

SQL Server

For more information, see Hardware and Software Requirements for Installing SQL Server in Windows IT Pro Center.

All features: 8.03 GB

We recommend separate disks for database, logs, and backup.


SCOM

For more information, see Recommended hardware for System Center Configuration Manager in Windows IT Pro Center.

All features (minimum disk space): 125 GB


OMIMSSC

For more information, see OpenManage Integration Version 7.0 for Microsoft System Center Installation Guide on Dell EMC Online Support.

2.18 GB

Because OMIMSSC is a virtual appliance, an additional guest operating system volume is not required.

Management VM

space

requirements

https://docs.microsoft.com/en-us/windows-server/failover-clustering/failover-cluster-csvs

https://docs.microsoft.com/en-us/windows-server/failover-clustering/failover-cluster-csvs

https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-1807


https://docs.microsoft.com/en-us/system-center/vmm/plan-install?view=sc-vmm-1807

https://docs.microsoft.com/en-us/windows-server/get-started/system-requirements

https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2017



https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/recommended-hardware



https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=P3PFX&osCode=WST14&productCode=poweredge-r640





The following table provides sample sizing information that is based on the function of the

management VM.

Table 8. Management VM size example

Component VMs RAM (GB) Operating system (GB)

SCVMM server 1 16 240

SCVMM database 1 8 240

SCVMM library 1 4 240

SCVMM console 1 4 240

SQL Server

Note: Additional SQL Server VMs and

database instances might be required. For more information, see the Microsoft SCVMM and SCOM documentation.

1 8 240

SCOM

If additional roles are required, see System requirements for System Center Operations Manager.

1 8 240

OMIMSSC

For more information, see the OpenManage Integration Version 7.0 for Microsoft System Center Installation Guide.

1 8 See the installation wizard for details.

Storage deployment and configuration checklist

Ensure that the following storage deployment and configuration tasks are complete:

Unity storage is deployed.

Connectrix DS6500 switches are deployed.

Storage and server zoning is configured.

Servers have FC access to Unity storage.

The management LUN has been presented to the management servers.

Management VM

sizing example

https://docs.microsoft.com/en-us/system-center/scom/plan-system-requirements?view=sc-om-1807






Chapter 6: Deploying the Management Cluster


Chapter 6 Deploying the Management Cluster


Introduction ....................................................................................................... 36

Preparing management hosts for Windows Server 2016 with Hyper-V ........ 36

Installing Windows Server 2016 and network drivers on the management server .......................................................................................................... 40

Enabling Hyper-V, failover clustering, and multipath features ...................... 41

Management cluster configuration checklist .................................................. 44



Introduction

This chapter describes the basic requirements and configuration steps for deploying the

management cluster.

Install Windows Server 2016 with Hyper-V on each of the PowerEdge management hosts

that will be part of the management cluster. You can order PowerEdge servers with

Windows Server 2016 preinstalled from Dell EMC or perform the installation locally or

remotely through the iDRAC web interface. This chapter describes how to perform the

installation remotely.

Note: In our example, we assign static IP addresses to the management interfaces of the

Windows Server 2016 hosts. Using DHCP is not recommended for IP allocation of management

hosts.

Preparing management hosts for Windows Server 2016 with Hyper-V

To complete these procedures, you need:

For iDRAC: IP addresses or FQDNs, login credentials, and Enterprise license

applied on all nodes.

Windows Server 2016 operating image. Note the image location on your system

because that is needed for mounting virtual media.

Host names, management VLAN ID, and IP address information.

Active Directory site name and administrative credentials.

Credentials for the administrative account to be used to install Windows.

Static IP addresses for each of the management servers.

Optional: Records for hostnames added to the DNS server.

Note: For information about setting up iDRAC, including configuring the IP address, see the iDRAC

user guide at Support for PowerEdge R640 on Dell EMC Online Support.

Note: Performing this step depends on customer workload and operational requirements.

Apply a BIOS settings profile (optional)

Optionally, apply the BIOS settings profile that is optimized for maximum virtualization

performance as follows.

Note: You can achieve the same result by using other means, such as remote racadm. This

procedure is the quickest approach for most environments.

1. Connect to the iDRAC IP address of one of the management hosts by using an

SSH client such as PuTTY.

2. Log in with the default credentials:

Deployment

prerequisites

Configure BIOS

settings and

connect to

iDRAC

https://www.dell.com/support/home/us/en/04/product-support/product/poweredge-r640/manuals



Username: root

Password: calvin

3. At the /admin1 prompt, enter the following command:

racadm set bios.sysprofilesettings.WorkloadProfile

VtOptimizedProfile

4. Press Enter.

A success message appears, as shown in the following figure.

Figure 8. iDRAC connection message

5. Create a job to process the change:

racadm jobqueue create BIOS.Setup.1-1

6. Press Enter.

A success message appears.

7. Reboot the management host.

8. Repeat the preceding steps for all the remaining management hosts.

Configure the BIOS settings

1. Using a web browser, go to the iDRAC web interface at https://<iDRAC

address>.

2. Log in with the default credentials:

Username: root

Password: calvin

3. Click Virtual Console Preview to open the remote console.

Ensure that you enable pop-up support in your browser for each iDRAC.

The iDRAC virtual console appears, as shown in the following figure.



Figure 9. Virtual console preview

4. Attach the virtual media by selecting Virtual Media > Connect Virtual Media.

5. Mount the Windows Server 2016 ISO image by selecting Virtual Media > Map

CD/DVD.

6. Click Browse, go to the location of the Windows Server 2016 ISO, and then click

Open.

This location must be available throughout the installation of Windows Server 2016

on all servers.

You are returned to the Virtual Media – Map CD/DVD menu.

Configure a virtual disk for operating system deployment on the PowerEdge14G server:

1. If you are not already connected to iDRAC, log in to iDRAC and launch the virtual

console.

2. From the Power menu, select Power on the system.

The following message appears:

You are about to execute a server control action. Are you

sure you want to continue?

3. Click Yes.

The system restarts.

4. To run the RAID configuration utility, press Ctrl+R when the following message

appears:

press CTRL + R to Run configuration utility

5. In the configuration utility, select PERC H730, and then press F2 to enable

operations.

6. From the list box, select Create New VD.

7. Complete the following selections:

Configure a

virtual disk for

operating

system

deployment



Set RAID Level to RAID-1.

Select physical disks.

Set the basic settings.

Use the default virtual disk size and virtual disk name.

Note: The operating system partition is not I/O-intensive. Use RAID 1 for operating

system partitions so that they have hardware redundancy.

8. Click OK.


It is recommended that all newly created logical drives be

initialized unless you are attempting to recreate a previous

configuration and recover data as initialization is a

destructive process. Are you sure you want to skip

initialization?

9. Click OK to create the virtual disk.

10. Exit Setup and restart the server.

Boot to the installation media:

1. Click Map Device.

2. From the Virtual Console menu bar, select Next Boot.

3. From the list, select Virtual CD/DVD/ISO.

4. Click OK to continue.

The location of the ISO that you have mapped must be available throughout the

installation process.

5. From the Virtual Console menu bar, select Power.

6. From the list, select Power on System or, if the power is already on, select

Power Cycle System (cold boot).

After the server powers on, the following message appears, followed by the

Windows Server setup:

Booting from Virtual CD

Press any key to boot from CD or DVD.

Boot to the

installation

media



Installing Windows Server 2016 and network drivers on the management server

Install Windows Server 2016 on the management server:

1. Select a language preference, time and currency format, and keyboard or input

method, and then click Next.

2. In Windows Setup, click Install now.

3. Enter the product key, and then click Next.

4. Select OS > Windows Server 2016 Datacenter (Server with GUI), and then

click Next.

5. Select I accept the license terms, and then click Next.

6. In Installation type, select Custom: Install Windows only (advanced).

7. Select Drive0 Unallocated Space and click New to create the partition.

8. Click Next.


To ensure that all Windows features work correctly, Windows

might create additional partitions for system files

9. Click OK.

10. After the installation is complete, on the Settings page, set the username and

password.

Install the Mellanox driver on Windows Server 2016:

1. After the server reboots, open the iDRAC Virtual Console.

2. Log in to the PowerEdge R740 server.

3. Browse to the location to where you downloaded the file and double-click the new

file.

You can download driver files from Support for PowerEdge R740 on Dell EMC

Online Support.

4. Read the release information that is presented in the dialog box.

5. Download and install any prerequisites that are identified in the dialog box.

6. Click Install.

7. Follow the remaining prompts to perform the installation.

8. To view the network card configuration, select Start > Run on the Windows

desktop, open the following file:

ncpa.cpl

The Network Connections window displays all the NIC cards.

Install Windows

Server 2016

Install the

Mellanox CX4 LX

Dual Port rNDC

driver




Install the QLogic driver:

1. Browse to the download location and double-click the file.



4. Click Install.


This procedure might be optional―the driver might be already available in the Windows

Server 2016 ISO. Install the PERC driver, if necessary, as follows:

1. Browse to the download location and double-click the new file.



4. Click Install.


This procedure might be optional―the driver might be already available in the Windows

Server 2016 ISO. Install the BOSS-S1 driver, if necessary, as follows:

1. Browse to the download location and double-click the new file.



4. Click Install.


Enabling Hyper-V, failover clustering, and multipath features

To install the Windows Hyper-V, failover clustering, and multipath features, enter the

following Windows PowerShell command.

Note: In Windows Server 2016, run the Windows PowerShell command as an administrator. This

step requires a restart.

Install-WindowsFeature –Name Failover-Clustering, Multipath-IO,

Hyper-V–IncludeManagementTools – Restart

Set up NIC teaming:

1. In Server Manager, select Local Server.

2. In Properties, click NIC Teaming status – Disabled.

3. In NIC Teaming, from TASKS, select New Team.

4. Enter the team name, for example, ConvergedNet Team, and then select the

NICs that you want to include in the team.

Install the

QLogic 2692

dual-port Fibre

Channel HBA

driver

Install the PERC

H730p driver

Install the BOSS-

S1 driver

Set up NIC

teaming in

Windows Server

2016



5. In Additional properties:

Set Teaming mode to Switch Independent.

Set Load balancing mode to Dynamic.

Note: The dynamic mode is a new feature of Windows Server 2016. The load

balancing algorithm, which balances traffic using flowlets, can spread both inbound

and outbound traffic. The Hyper-V port algorithm forces all VM traffic through only

one physical NIC, whereas the dynamic mode spreads traffic across all the NICs,

regardless of workload.

6. Click OK.

7. Verify that the NICs are active.

On the PowerEdge 14G server, start Windows PowerShell as an administrator and

configure the network as follows.

Note: For larger deployments or for future use as the environment scales, consider SCVMM

networking. For more information, see the following Microsoft articles: Plan the VMM networking

fabric, Set up the VMM networking fabric, and Set up networking for Hyper-V hosts and clusters in

the VMM fabric.

1. Create a VM switch:

New-VMSwitch –AllowManagementOS 1 –Name ConvergedNetSwitch –

MinimumBandwidthmode weight – Verbose

NetAdapterName: ConvergedNet Team

2. Create a VM network adapter for the cluster:

Add-VMNetworkAdapter –ManagementOS –SwitchName

ConvergedNetSwitch –Name Cluster –Verbose

3. Create a VM network adapter for a live migration:

Add-VMNetworkAdapter –ManagementOS –SwitchName

ConvergedNetSwitch –Name LiveMigration – Verbose

4. Set VLAN access properties for the management network adapter:

Set-VMNetworkAdapterVlan –ManagementOS –VMNetworkAdapterName

ConvergedNetSwitch –Access – VlanId 110

5. Set VLAN access properties for the cluster network adapter:


Cluster –Access –VlanId 210

6. Set VLAN access properties to LiveMigration:


LiveMigration –Access –VlanId 120

7. Set the minimum bandwidth reservation for the management network adapter:

Configure

Hyper-V

networking in

Windows Server

2016

https://docs.microsoft.com/en-us/system-center/vmm/plan-network?view=sc-vmm-1807


https://docs.microsoft.com/en-us/system-center/vmm/manage-networks?view=sc-vmm-1807

https://docs.microsoft.com/en-us/system-center/vmm/hyper-v-network?view=sc-vmm-1807




Set-VMNetworkAdapter -ManagementOS -Name ConvergedNetSwitch

-MinimumBandwidthWeight 5

8. Set the minimum bandwidth reservation for the cluster network adapter:

Set-VMNetworkAdapter -ManagementOS -Name Cluster -

MinimumBandwidthWeight 40

9. Set the minimum bandwidth reservation for the live migration network adapter:

Set-VMNetworkAdapter -ManagementOS -Name LiveMigration -

MinimumBandwidthWeight 20

Note: You can view vEthernet (ConvergedNetSwitch) and adapters for the cluster and live

migration networks in Network Connections.

Configure the vEthernet switch:

1. In the Network Connections windows, right-click vEthernet

(ConvergedNetSwitch), and select Properties from the list box.

2. In vEthernet (ConvergedNetSwitch) Properties, configure IPV4 protocol

properties, include the IP address and DNS server details, and then click OK.

3. Ping the VLAN 210 network to test the network connection.

Rename and add servers:

1. Enter the following Windows PowerShell command:

Add-Computer -DomainName -NewName – Restart -Force

2. At the Windows prompt, type the credentials of the domain controller.

Install PowerPath software:

1. Download the PowerPath software from DellEMC.com.

2. Follow the instructions in the installation wizard to install the software.

3. Activate the PowerPath software using the license key that you received when

you purchased it.

Add volumes in the PowerEdge server:

1. Log in to the PowerEdge R740 server.

2. Right-click Start > Run, and then type:

diskmgmt.msc

3. In Disk Management:

a. Select the 1 GB disk.

Right-click New Disk and select Online.

Right-click the disk and select Initialize disk.

Configure the

vEthernet switch

in Windows

Server 2016

Rename and add

servers to the

domain

Install Dell EMC

PowerPath

software

Add volumes in

the PowerEdge

14G server

http://www.dellemc.com/



Right-click the disk and select New Simple Volume.

4. In the New Simple Volume wizard, click Next.

5. In Specify volume size in MB, use the default disk size, and then click Next.

6. In Assign Drive Letter or Path, select Do not assign a drive letter or drive

path, and then click Next.

7. In Format Partition:

a. Select Format this volume with the following settings.

b. Select the following settings:

File system—NTFS

Allocation unit size—64K

Volume label—Quorum

c. Select Perform a quick format.

d. Click Next.

8. In the Completing the New Simple Volume wizard, click Finish.

9. Repeat the preceding steps to create the second volume for storing the VHD files

of the VMs.

Management cluster configuration checklist

Ensure that the following management cluster configuration tasks are complete:

Windows Server 2016 is installed on the management servers.

Hyper-V is enabled and failover clustering, multipath I/O, and NIC teaming are

configured.

The host is renamed and the domain is joined.

PowerPath software is installed and volumes have been created.

Chapter 7: Deploying the Compute Cluster


Chapter 7 Deploying the Compute Cluster


Introduction ....................................................................................................... 46

Creating a cluster .............................................................................................. 46

Establishing VM-to-SAN connectivity .............................................................. 46

Creating a VM .................................................................................................... 47

Verifying the compute cluster deployment ..................................................... 48



Introduction

Perform the tasks described in this section once. You must be logged in with a domain

account that has administrator privileges.

Creating a cluster

To create a cluster, perform the following high-level tasks on the compute and

management servers that you are going to add to the cluster:

1. Validate the configuration.

2. Create a Hyper-V host cluster.

Verify that the configuration meets the guidelines for failover clustering:

1. Run the following command:

Test-Cluster –Node "Node1", "Node2" -Include "Storage",

Inventory, Network, "System Configuration"

After the test is complete, the results are displayed.

2. If any messages indicate failures with the tests, resolve the issues before

continuing.

Run the following command to create a two-node cluster with a static IP address.

The IP address is required for the cluster’s management connection.

New-Cluster –Name <"ClusterName"> –Node "Node1", "Node2" –

StaticAddress <IPaddress>

Establishing VM-to-SAN connectivity

The Hyper-V Virtual FC feature enables a VM to connect directly to a SAN through a

virtualized FC adapter. Establishing connectivity to the SAN by using a virtual FC adapter

is a two-step process:

1. Create a SAN.

2. Add a virtual FC adapter to the VM and connect it to the SAN.

Create a SAN:

1. On the Windows Start screen, click Server Manager.

2. Select Tools > Hyper-V Manager.

3. In the Action pane, click Virtual SAN Manager.

4. Click Create.

5. In the Name field, enter the name for the new SAN.

6. In the Notes field, enter any important information for the SAN.

Validate the

configuration

Create a Hyper-V

host cluster

Create a SAN



7. Ensure that you select at least one available WWN for the SAN to be used by the

virtual FC adapter.

8. Click OK.

9. In Hyper-V Manager, click VirtualSAN Manager to view the new SAN.

Add a virtual FC adapter to the VM and connect it ito the SAN:

1. On the Windows Start screen, click Server Manager.

2. Select Tools > Hyper-V Manager.

3. In Hyper-V Manager, under Virtual Machines, click the name of the VM that you

want to add, as described in Creating a VM on page 47.

4. In the Action panel, click Settings.

5. In Add Hardware, review a list of the hardware options that you can add to the

VM.

6. Click Fibre Channel Adapter, and then click Add.

7. In Settings, connect the virtual FC adapter to a SAN that you previously created:

Click the Virtual SAN list box that shows Not connected.

Select the name of the required SAN.

8. Configure the WWNs (Set A and Set B) for the virtual FC adapter.

You can use the automatically generated default WWNs or manually assign them.

9. Configure both WWN sets to ensure a successful live migration of the VM.

Creating a VM

To create a VM, run these PowerShell commands as an administrator:

1. To create a fixed VHD for better I/O performance, run the following command:

$VHDPath="C:\ClusteredStorage\volume1\HDD\<HDDname>.vhdx"

New-VHD -SizeBytes <size> –Path $VHDPath –Fixed

2. Create a VM:

$VMPath="C:\ClusteredStorage\volume1\VMs\<VMname>"

New-VM -Name SP -Path $VMPath -MemoryStartupBytes <Memory> -

BootDevice CD -SwitchName

<switchname> -VHDPath $VHDPath

3. Configure the VM:

Set-VMProcessor -VMName DB -Count <vcpu count>

Add-VMNetworkAdapter -VMName <VMName> -Name <Virtual Network

adapter>

Set-VMNetworkAdapterVlan -VMName <VMName>

-VMNetworkAdapterName

<Virtual Network adapter> - Access -VlanId <VLANID>

Add a virtual FC

adapter to the

VM and connect

it to the SAN



4. Add the vSAN switches to the VM:

Add-VMFibreChannelHba –VMName <VMName> –SanName <vSAN switch

name1>

Add-VMFibreChannelHba –VMName <VMname> –SanName <vSAN switch

name2>

Verifying the compute cluster deployment

After you complete the preceding deployment steps, verify the functionality as follows:

1. Migrate the VMs across the cluster and verify that the live migration is completed

without interruption.

2. Gracefully shut down one of the PowerEdge 14G servers and verify that VMs

migrate to another cluster host.

3. Power off one of the S5248F-ON switches and verify that the VMs continue to run

without any network impact.

Chapter 8: Deploying the Software Components


Chapter 8 Deploying the Software Components


Introduction ....................................................................................................... 50

Deploying the integration and management applications ............................. 50

Deploying the Dell EMC Integrated Data Protection Appliance ..................... 51

Software deployment checklist ........................................................................ 51



Introduction

This Ready Stack includes the following software applications:

Microsoft System Center Virtual Machine Manager (SCVMM)

Microsoft System Center Operations Manager (SCOM)

Dell EMC OpenManage Integration for Microsoft System Center (OMIMSSC)

Dell EMC IDPA DP4400

This chapter provides the high-level steps for deploying these applications. For detailed

instructions and advanced configuration options, see the relevant product documentation.

Ensure that the required software licenses are available and that you have adequate

system resources for the VMs, as shown in Table 8 on page 34.

Deploying the integration and management applications

The Dell EMC OMIMSSC appliance facilitates operating system deployment, hardware

patching, firmware updates, and server maintenance. OMIMSSC provides integrations

with the Microsoft System Center suite of products that enable full lifecycle management

of the Dell EMC servers by using iDRAC with Lifecycle Controller (LC). With OMIMSSC,

you can either integrate with Microsoft SCCM for managing the Dell EMC servers or with

Microsoft SCVMM in virtualized or cloud environments.

Ensure that:

You use VM resource controls and settings to configure reservations that ensure

that necessary CPU and memory resources are available to the VMs.

The VMs have network access to the iDRACs, the hosts, the cluster, and the

management network.

SCVMM is one of Microsoft's System Center VM management and reporting tools,

alongside established tools such as SCOM. For more information, see the Microsoft

article What is Virtual Machine Manager?

To deploy SCVMM:

1. Go to the Microsoft article System requirements for System Center Virtual

Machine Manager.

2. Click Plan VVM installation in the left navigation bar to access the deployment

requirements.

3. To perform the deployment, follow the instructions under Install VVM.

To deploy SCOM:

1. Go to the Microsoft Operations Manager Planning Guide

Overview

Prerequisites

Overview

Deploy SCVMM

Deploy SCOM

https://docs.microsoft.com/en-us/system-center/vmm/overview?view=sc-vmm-1807



https://docs.microsoft.com/en-us/system-center/vmm/plan-install?view=sc-vmm-1807

https://docs.microsoft.com/en-us/system-center/vmm/install?view=sc-vmm-1807

https://docs.microsoft.com/en-us/system-center/scom/plan-overview?view=sc-om-1807



2. Click Plan in the left navigation bar to access the deployment requirements.

3. To perform the deployment, follow the instructions under Deploy.

To deploy OMISCC:

1. Download OMIMSSC from Dell EMC Online Support and save the file to your

hard drive.

2. Extract the files:

a. Browse to the location where you downloaded the file and double-click the

file to unzip the download package.

Click Continue.

Specify the location to which you want to extract the files.

Click OK to extract the files.

The message All files were successfully unzipped appears.

Click OK to exit.

3. Install the files:

a. Browse to the location of the extracted files.

b. Complete the installation by following the instructions in the OpenManage

Integration Version 7.0 for Microsoft System Center Installation Guide.

Note: If you have not already done so, register with Dell EMC Online Support for

product support.

Deploying the Dell EMC Integrated Data Protection Appliance

IDPA DP4400 is a 2U appliance that provides comprehensive data protection that is

simple to manage, deploy, and upgrade from 24 TB to 96 TB without any additional

hardware. IDPA DP4400 also delivers an average data deduplication rate of 55:1 and

shortens backup windows by up to two times.

To deploy the IDPA DP4400, follow the instructions in the Dell EMC Integrated Data Protection Appliance Getting Started Guide.

Software deployment checklist

Ensure that the following software components are deployed:

SCVMM

SCOM

OMIMSSC

IDPA DP4400

Deploy

OMIMSCC

https://docs.microsoft.com/en-us/system-center/scom/plan-overview?view=sc-om-1807

https://docs.microsoft.com/en-us/system-center/scom/deploy-overview?view=sc-om-1807

https://support.emc.com/

https://www.dell.com/support/manuals/us/en/19/omimssc-v7.0/lc_integration_7.0_ig/introduction?guid=guid-04f19e2d-6142-404c-bd65-e1210cc21da9&lang=en-us

https://www.dell.com/support/manuals/us/en/19/omimssc-v7.0/lc_integration_7.0_ig/introduction?guid=guid-04f19e2d-6142-404c-bd65-e1210cc21da9&lang=en-us

https://www.dell.com/support/

https://www.emc.com/collateral/TechnicalDocument/docu89626.pdf


Chapter 9: References


Chapter 9 References


Dell EMC documentation .................................................................................. 53

Microsoft documentation ................................................................................. 53

Chapter 9: References


Dell EMC documentation

The following Dell EMC documentation provides additional and relevant information.

Access to these documents depends on your login credentials. If you do not have access

to a document, contact your Dell EMC representative.

Dell EMC Ready Bundle for Microsoft SQL Server 2016 Deployment Guide

Integrated Dell Remote Access Controller 9 User's Guide

iDRAC9 Home (Knowledge Base)

Dell Support for OpenManage Integration Version 7.0 for Microsoft System Center

Dell Support for Dell EMC OpenManage Server Administrator 9.1.0

Dell EMC Unity: Best Practices Guide

Dell EMC Unity Family: Unisphere Command Line Interlace User Guide

Support for Dell Networking S3048-ON—Manuals and Documents

S3048-ON Installation Guide

S5200F-ON Series Installation Guide

Support for Dell Networking S5232F-ON—Manuals & documents

Connectrix DS-6510B—Documentation

Dell EMC Integrated Data Protection Appliance Getting Started

Microsoft documentation

The following Microsoft documentation provides additional and relevant information:

What is Virtual Machine Manager

Operations Manager

System Requirements for System Center Virtual Machine Manager

System Center Configuration Manager

Plan the VMM networking fabric

Set up the VMM networking fabric

Set up networking for Hyper-V hosts and clusters in the VMM fabric

https://www.emc.com/collateral/technical-documentation/h16851-ready-sql-server-dg.pdf

https://topics-cdn.dell.com/pdf/idrac9-lifecycle-controller-v3212121_users-guide_en-us.pdf

https://www.dell.com/support/article/us/en/19/sln311300/idrac9-home?lang=en

https://www.dell.com/support/home/us/en/04/product-support/product/omimssc-v7.0/research

https://www.dell.com/support/contents/us/en/04/article/product-support/self-support-knowledgebase/enterprise-resource-center/systemsmanagement/omsa

https://www.emc.com/collateral/white-papers/h15093-dell-emc-unity-best-practices-guide.pdf


https://www.dell.com/support/home/us/en/04/product-support/product/force10-s3048-on/manuals

https://www.dell.com/support/manuals/us/en/04/force10-s3048-on/s3048_on_install_pub/about-this-guide?guid=guid-c4e4b187-79a0-4baf-b750-ed70e5fffc1a&lang=en-us

https://topics-cdn.dell.com/pdf/networking-s5248f-on_install-guide_en-us.pdf

https://www.dell.com/support/home/us/en/04/product-support/product/networking-s5232f-on/manuals

https://support.emc.com/products/16423_Connectrix-DS-6510B/Documentation/

https://support.emc.com/docu89626_Integrated-Data-Protection-Appliance-2.2-Getting-Started-Guide.pdf

https://support.emc.com/docu89626_Integrated-Data-Protection-Appliance-2.2-Getting-Started-Guide.pdf

https://docs.microsoft.com/en-us/system-center/vmm/overview?view=sc-vmm-1807

https://docs.microsoft.com/en-us/system-center/scom/welcome?view=sc-om-1807


https://www.microsoft.com/en-us/cloud-platform/system-center-configuration-manager


https://docs.microsoft.com/en-us/system-center/vmm/manage-networks?view=sc-vmm-1807


Appendix A: Site Survey


Appendix A Site Survey

This appendix presents the following topic:

Site survey tables.............................................................................................. 55



Site survey tables

The tables in this section detail the network information that is required to deploy the

Ready Stack. We recommend that you collect this information before starting the

deployment.

Table 9. Network topology: Switch hostnames

Switch Hostname Management IP address

Gateway IP address

VLT ports

S3048

S5248F-Top

S5248F-Bottom

Additional configuration notes (Spanning Tree Protocol, routing protocol, and so on, as applicable):

Table 10. VLAN information

Table 11. Customer network services

Next hop/default gateway

DNS [1, 2]:

NTP [1, 2]:

Table 12. Switch port mappings

S5232F-Top S5232F-Bottom S3048

Server NIC Port 1 NIC Port 2 iDRAC

Mgmt1

Mgmt2

Comp1

Comp2

Comp3

Unity storage array

Network type VLAN ID

S5232F-Top IP CIDR

S5232F-Bottom IP CIDR

VRRP IP address

VRRP group group

S3048 IP address

OOB 100

Management 110

Live migration 120

Compute VM 210



S5232F-Top S5232F-Bottom S3048

DS-6500-Top

DS-6500-Bottom

Table 13. Port channel configuration

Name Role Number Switch Port(s)

VLTi peer-link Not applicable S5232F-Top

S5248F-Bottom

OOB standard 101 S5248F-Top

S5248F-Bottom

S3048-OOB

Table 14. Management host information

Table 15. Host information

Hostname Management Live migration iDRAC IP address

Mgmt1

Mgmt2

Comp1

Comp2

Comp3

Table 16. Management virtual machines

Hostname IP address Subnet mask Gateway VLAN

SCVMM

SCOM

OMISSC

IDPA DP4400

Table 17. Hyper-V HA cluster information

Cluster details Site A Management cluster name

MgmtPod

Cluster hosts Mgmt1, Mgmt2

Cluster name Site A Compute cluster name ComputePod

Cluster hosts Comp1, Comp2, Comp3

Hostname Management Live migration iDRAC IP address Service tag



Table 18. Unity storage array information

Hostname IP address Subnet mask Gateway

Table 19. Connectrix DS-6500 information

Hostname IP address Subnet mask Gateway