VxRail 7.0.XXX Planning

VXRAIL 7.0.
241
PLANNING
DOWNLOADABLE CONTENT
DOWNLOADABLE CONTENT
Table of Contents
Plan for a VxRail Deployment ...................................................................................... 1

VxRail Architecture Overview ...................................................................................................1
VxRail Deployment Process Overview ....................................................................................2
vCenter Options for a VxRail Deployment ...............................................................................3
vCenter Option 1: Use the VxRail vCenter Server...................................................................3
vCenter Option 2: Join an Existing vCenter Server .................................................................4
VxRail Network Switches .........................................................................................................7
VxRail Network Interface Cards ...............................................................................................8
Virtual Networking Overview ....................................................................................................8
VxRail VDS Predefined Network Profile Considerations ...................................................... 10
VxRail VDS Predefined Network Profile Configuration ......................................................... 11
VxRail VDS Custom Network Profile with a New VDS Type ................................................ 15
VxRail VDS Custom Network Profile with an Existing VDS Type ........................................ 16
DNS Considerations .............................................................................................................. 17
VxRail Automatic Discovery .................................................................................................. 17
VxRail IP Address Discovery................................................................................................. 18
Knowledge Check: Plan For a VxRail Deployment............................................................... 19
VxRail Configuration Portal ....................................................................................... 22

VxRail Configuration Portal Overview ................................................................................... 22
VxRail Configuration Portal Project ....................................................................................... 22
VxRail Configuration Portal Cluster Configuration ................................................................ 23
Demonstration: Create a Cluster in the VxRail Configuration Portal .................................... 24
Interaction: Create a Cluster Configuration in the VxRail Configuration Portal ................... 24
VxRail Cluster Configuration Report and Pre-Deployment Checklist................................... 25
VxRail Cluster Configuration Report ..................................................................................... 25
Pre-deployment Checklist ..................................................................................................... 26
Interaction: Export a Configuration Report and Complete the Pre-Deployment Checklist .. 27
Download VxRail Cluster Configuration File for Deployment ............................................... 27
Knowledge Check: Use VxRail Configuration Portal to Prepare for a VxRail Deployment . 28
You Have Completed This Content....................................................................................... 30
VxRail 7.0.241 Planning-SSP - Lesson
Page ii © Copyright 2021 Dell Inc.

Appendix.................................................................................................31
Glossary..................................................................................................38
© Copyright 2020 Dell Inc. Page iii

Plan for a VxRail Deployment
VxRail Architecture Overview
In a VxRail environment, the cluster is the primary unit of deployment.
A standard VxRail cluster is made up of the following components:

• Hardware
− VxRail Nodes - Dell PowerEdge servers that are configured and optimized
to support the VMware and VxRail software components. A standard VxRail
cluster is made up of 3 - 64 nodes.
− Top of Rack (ToR) Switches - Physical Ethernet switches that carry
internode network traffic and link the VxRail cluster to the data center
network. A VxRail cluster supports one or more ToR switches.
− Out-of-Band (OOB) Management Switch - Physical Ethernet switch that
provides separate connections for the iDRAC management interface on
each VxRail node. Separating iDRAC management connections from the
ToR switches is optional.
• VMware Technologies
− ESXi - A hypervisor that is installed locally onto VxRail nodes. ESXi provides
virtualized compute, network, and storage resources for virtual machines
and containers. ESXi is also the base platform for vSAN and VDS
technologies.
− vSAN - Storage virtualization technology that combines individual VxRail
node disks and presents the storage to the cluster as a single datastore.
− vSphere Distributed Switch (VDS) - Network switch virtualization
technology that spans all nodes in a cluster. VDS enables simplified
management and virtual machine network connectivity.
© Copyright 2021 Dell Inc. Page 1

− vCenter Server - Centralized platform that provides management and

monitoring capabilities for VMware server virtualization, vSAN, VDS, and
VxRail nodes. A new vCenter virtual appliance is deployed within the cluster,
or the cluster is joined to an existing vCenter.
• VxRail Manager - A virtual appliance that provides the discrete UI for VxRail
cluster deployment and a vCenter plug-in for postdeployment operations. VxRail
Manager also has other VxRail HCI components such as APIs and ecosystem
connectors.
ToR Switches
Management Switch
VxRail Cluster
VxRail Manager
vCenter Server
VDS
vSAN
ESXi
VxRail Nodes
Standard VxRail Architecture
VxRail Deployment Process Overview
The deployment process includes planning, predeployment steps, cluster build, and
postdeployment steps.
To learn about the deployment process, watch the video below.
Movie:
The web version of this content contains a movie.
Page 2 © Copyright 2021 Dell Inc

.
https://players.brightcove.net/6057277730001/default_default/index.html?videoId=1
710762632297803170
For more information, read the Dell VxRail 7.0.x Deployment Guide.
vCenter Options for a VxRail Deployment
vCenter Server:
• A centralized platform for managing VMware server virtualization and vSAN
• The primary point of management for VxRail clusters using the VxRail Plugin
vCenter Server Options:
VxRail clusters are deployed with one of two vCenter options; Use the VxRail
vCenter Server or Join an existing vCenter Server.
VxRail Deployment Wizard and Configuration Portal - vCenter Server Options
For detailed information, see the VxRail vCenter Server Planning Guide.
vCenter Option 1: Use the VxRail vCenter Server
A new VxRail-managed vCenter Server is deployed on a new VxRail cluster. This

option is used for a stand-alone cluster deployment or the first cluster in a
multicluster deployment.

vCenter Server VxRail Manager
ESXi ESXi
ESXi ESXi
New VxRail Cluster
Data Center
New VxRail-managed vCenter Server
Planning Considerations:
• Includes a nontransferable standard vCenter license
• Uses VxRail Lifecycle Management for vCenter software upgrades
• Does not support vCenter High Availability
• Deployed with a noncustomizable vSphere Single Sign-on (SSO) domain called
vsphere.local
• Supports internal or external DNS server options
• Supports VxRail-deployed Virtual Distributed Switches
• Supports Enhanced Link Mode with other VxRail-managed vCenter Servers
Prerequisites:
• If internal DNS is selected, an IP address and DNS name must be available
during deployment. These values are added to the DNS service running on the
VxRail Manager VM.
• If external DNS is selected, forward and reverse DNS entries must be
preconfigured on a DNS server in the customer environment.
vCenter Option 2: Join an Existing vCenter Server
The Join an existing vCenter Server option can be further divided into two
options, each with its own planning considerations.
To learn more about the deployment options, select each tab below.

.
Existing VxRail-managed vCenter Server
A new VxRail cluster is deployed with an existing VxRail-managed vCenter Server

that is on another cluster. This option is used for a second or subsequent cluster
deployments.
VxRail Manager vCenter Server VxRail Manager
ESXi ESXi ESXi ESXi
ESXi ESXi ESXi ESXi
New VxRail Cluster Existing VxRail Cluster
Data Center
New Cluster with an Existing VxRail-managed vCenter
• Includes a nontransferable standard vCenter license
• Uses VxRail Lifecycle Management for software upgrades
• Does not support vCenter High Availability
• Uses existing noncustomizable vSphere SSO domain called vsphere.local
• Requires an external DNS server
• Supports a new VxRail-deployed or existing Virtual Distributed Switches
Prerequisites:
• Preconfigured forward and reverse DNS entries
• Compatible vCenter and VxRail versions
• Existing SSO domain
• Preconfigured VxRail management and administrator user accounts in vCenter
• Preconfigured data center in vCenter

Existing Customer-supplied vCenter Server
A new VxRail cluster is deployed with an existing vCenter server that runs on
infrastructure that is external to a VxRail cluster. This option is used for single or
multiple cluster deployments.
VxRail Manager vCenter Server
ESXi ESXi
ESXi ESXi
New VxRail Cluster
Data Center
New Cluster with an Existing Customer-supplied vCenter
• Requires a separate vCenter license
• Uses customer-defined procedures for software upgrades
• Supports vCenter HA
• Supports a custom vSphere SSO domain
• Requires an external DNS server
• Supports a new VxRail-deployed or existing Virtual Distributed Switches
Prerequisites:
• Preconfigured forward and reverse DNS entries
• Compatible vCenter and VxRail versions
• Existing SSO domain
• Preconfigured VxRail management and administrator user accounts in vCenter
• Preconfigured data center in vCenter

.
VxRail Network Switches
VxRail nodes connect to one or more ToR network switches and are configured as
a VxRail cluster. The physical switch infrastructure supports all the network traffic
for the VxRail cluster. VxRail logical networking depends on the ToR switches for
physical connectivity between the nodes, and to the core production network.
VxRail network traffic is configured for Layer 2 networking. For supported VxRail
network speeds and interfaces, see the Dell VxRail Spec Sheet. Each node has an
Integrated Dell Remote Access Controller (iDRAC) which requires a connection to
a management switch.
Management Core Production Core
ToR Switches
Management Switch
VxRail Cluster
VxRail nodes with four 10 GbE interfaces and two ToR switches.
• VxRail is compatible with most Ethernet switches.
• Layer 2 switches are required. If the customer requires, Layer 3 switches may
be used.
• Two or more ToR switches are required for increased performance and high
availability.
• A minimum of 10 GbE is required for All-flash and NVMe clusters, but 25 GbE
or faster is recommended.

VxRail Network Interface Cards
VxRail models support various configurations of the integrated network interface

card (NIC). Most VxRail models also support optional PCIe NICs. Each VxRail
node also has a 1 GbE RJ45 port for Integrated Dell Remote Access Controller
(iDRAC) connectivity. View the VxRail Specification Sheet for the supported
network card options.
PCIe NIC
iDRAC Integrated NIC
VxRail node with integrated and PCIe NICs
• Using network ports across the integrated and PCIe NICs is required for high
availability.
• Network ports that are selected during the VxRail initial build process are
reserved exclusively for VxRail usage.
• Ports on the integrated and PCIe NICs can run at different speeds. For
instance, the integrated NIC ports can support 10 GbE and the ports on the
PCIe NIC support 25 GbE.
• Network adapter ports must match the type and speed of the ToR switches.
Virtual Networking Overview
In a standard VxRail cluster, a vSphere Distributed Switch (VDS) provides virtual

networking capabilities for hosts and virtual machines. A VDS has two types of port
groups. Distributed port groups connect virtual machines and host services to the
VDS. Uplink port groups map to the host NICs and provide a connection to the
upstream physical switches. Uplink port groups use NIC port aliases like vmnic0 for
the physical NIC ports.

.
During the initial build of a VxRail Cluster, a predefined or custom network profile is
selected. These profiles determine the number of VDSs, number of uplink port
groups, and uplink failover policy for each distributed port group to be configured.
The VxRail configuration portal groups VxRail networking into six types of traffic.
Each traffic type is associated with a distributed port group that exists on one or
two VDSs. VxRail supports IPv6 for discovery traffic only. All other types of traffic
must be IPv4.
ToR Switches
VxRail Node
Uplink 1 Uplink 2
VDS
vSAN vMotion Mgmt. vCenter Server Discovery Guest VM
VxRail VDS Overview
VxRail network traffic types:

• Discovery
− Usage: Internal network for VxRail node discovery during initial
implementation and cluster expansion
− VLAN ID: Configurable, default 3939
• Management 1
− Usage: External network for ESXi host management
− VLAN ID: Configurable, default untagged
• vCenter Server 1
− Usage: External network for vCenter Server and VxRail Manager
management
− VLAN ID: Configurable, default untagged
• vMotion
− Usage: Internal network for cluster vMotion traffic

− VLAN ID: Configurable

• vSAN
− Usage: Internal network for cluster vSAN traffic
• Guest VM (optional)
− Usage: External network for production VMs

1 Although Management and vCenter Server are considered different traffic types,
the VLAN is the same for both.
VxRail VDS Predefined Network Profile Considerations
A VDS predefined network profile contains default configuration settings for a VDS.
The settings reflect VxRail cluster deployment best practices for common
configurations. The profile is used to create a VDS at the time of cluster
deployment.
The predefined profile:

• Is not customizable.
• Defines a single VDS only.
• Supports specific NIC configurations.
• Defines standard port group names.
Traffic Type Port Group Name
Discovery VxRail Management-<UUID>
Management Management Network-<UUID>
vCenter Server vCenter Server Network-<UUID>

.
vMotion vSphere vMotion-<UUID>
vSAN Virtual SAN-<UUID>
Guest VM (optional) VM Guest Network
Example - VxRail VDS Distributed Port Groups
VxRail VDS Predefined Network Profile Configuration
The uplink port group configuration for the VDS depends on the number and type
of NICs that are used for VxRail traffic. Two uplinks are configured for each
distributed port group, one active and one standby. For the VDS predefined
network profiles, the NICs must be cabled in a specific manner.
To learn more about the cabling and port group configurations, select each tab
below.

2x10 GbE or 2x25 GbE (Integrated NIC)
ToR Switches
P0 - vmnic0 P1 - vmnic1
Integrated NIC
Uplink 1 Uplink 2
VDS
Failover Pair
Cabling - 2x10 GbE or 2x25 GbE (Integrated NIC ports)
Teaming Policy
Port Group Uplink1 - Integrated NIC Uplink2 - Integrated NIC

Port 0/vmnic0 Port 1/vmnic1
Management Network Active Standby
vSphere vMotion Active Standby
Virtual SAN Standby Active
vCenter Server Network Active Standby
VxRail Management Active Standby

.
4x10 GbE (Integrated NIC)
ToR Switches
P0 - vmnic0 P1 - vmnic1 P2 - vmnic2 P3 - vmnic3
Integrated NIC
Uplink 1 Uplink 2 Uplink 3 Uplink 4

VDS
Failover Pair Failover Pair
Cabling - 4x10 GbE (Integrated NIC ports)
Teaming Policy
Port Group Uplink1 - Uplink2 - Uplink3 - Uplink4 -

Integrated Integrated Integrated Integrated
NIC Port NIC Port NIC Port NIC Port
0/vmnic0 1/vmnic1 2/vmnic2 3/vmnic3
Management Standby Active Unused Unused

Network
vSphere Unused Unused Standby Active

vMotion
Virtual SAN Unused Unused Active Standby
vCenter Active Standby Unused Unused

Server
Network
VxRail Standby Active Unused Unused

Management

4x25 GbE (Integrated and PCIe NICs)
ToR Switches
P0 - vmnic0 P1 - vmnic1 P0 - vmnic2 P1 - vmnic3
Integrated
PCIe NIC
NIC
Uplink 1 Uplink 2 Uplink 3 Uplink 4

VDS
Failover Pairs
Cabling - 2x25 GbE Integrated + 2x25 GbE PCIe NICs
Teaming Policy
Port Group Uplink1 - Uplink2 - Uplink3 - Uplink4 -

Integrated Integrated PCIe NIC Port PCIe NIC Port
NIC Port NIC Port 0/vmnic2 1/vmnic3
0/vmnic0 1/vmnic1
Management Active Unused Standby Unused

Network
vSphere Unused Standby Unused Active

vMotion
Virtual SAN Unused Active Unused Standby
vCenter Standby Unused Active Unused

Server
Network
VxRail Active Unused Standby Unused

Management

.
The cabling for this configuration is different than the 4x10GbE configuration. The
integrated NIC Port 0 is cabled to Switch 1 and PCIe NIC Port 0 is cabled to Switch
2. These two ports form a failover pair. The integrated NIC Port 1 is cabled to
Switch 2, while PCIe NIC Port 1 is cabled to Switch 1. These two ports form an HA
failover pair as well.
VxRail VDS Custom Network Profile with a New VDS Type
A VDS custom network profile enables implementers to configure settings for a

VDS. The custom profile is selected when customers require more flexibility in the
virtual network configuration. There are two types of custom profiles, New and
Existing. When the new type is selected, VxRail Manager deploys a VDS with the
specified configuration. When the existing type is selected, VxRail Manager uses a
VDS that has already been created.
The new profile type contains the following options:

• Number of VDS - VxRail Network traffic is assigned to a single switch or split
across two switches.
• Network Traffic Type - When two VDSs are selected, each VxRail network
traffic type (distributed port group) is assigned to a VDS.
• MTU - The Maximum Transmission Unit (MTU) value is set for each VDS.
• Host NICS - The number of uplinks are set to two or four for each VDS.
• NIC Configuration - Physical NIC ports are assigned to uplink port groups for
each VDS.
• VDS Port Group Teaming and Failover - Distributed port groups are
configured with required teaming and load-balancing policies, and MTU for the
associated VMkernel port.
Example: Custom Network Profile with two New VDSs
• With a custom uplink assignment, resource-intense networks like vSAN can be
assigned to higher speed uplinks.
• If the customer requires enhanced security in vCenter, management and
nonmanagement port groups can be split across two VDSs.

• For resource-intense networks like vSAN, a higher MTU (jumbo frames) can be
set to improve performance.
• Unlike the predefined network profile, the custom network profile supports
active/active teaming policies for distributed port groups.
• Link aggregation can be configured on the new VDS after the VxRail cluster
build is complete.
• VMkernel MTU must be less than or equal to the VDS MTU.
VxRail VDS Custom Network Profile with an Existing VDS

Type
The custom network profile with an existing VDS requires that a VDS be configured
before the VxRail cluster is deployed. This profile is only available if the VxRail
cluster is joined to an existing vCenter Server. This custom profile is the only profile
that supports Link Aggregation Groups (LAG).
The existing profile type contains the following options:

• Number of VDS - VxRail Network traffic is assigned to a single switch or split
across two switches.
• Network Traffic Type - When two VDSs are selected, each VxRail network
traffic type (distributed port group) is assigned to a VDS.
• VDS Name - The name of the existing VDS in vCenter is required.
• Host NICS - The number of uplinks are set to two or four for each VDS.
• VDS LAG - If yes, LAG options are enabled.
• NIC Configuration - In a non-LAG configuration, the existing uplink port group
names in vCenter, and the physical NIC port assignments are required. In a
LAG configuration, the LAG uplink name in vCenter and the physical NIC port
assignments are required.
• VDS Port Group Teaming and Failover - The existing port group names in
vCenter and MTU for the associated VMkernel port are required.
Example: Custom network profile with two existing VDSs
• Port groups for each VxRail traffic type must be created on the VDS.

.
• Names for the VDS, distributed port groups, and uplinks are case-sensitive and
must match the names in vCenter.
• The port group for the Guest VM network is not required for the VxRail initial
build and can be created later.
• LAG for nonmanagement distributed port groups is supported.
• Static LAG and Link Aggregation Control Protocol (LACP) for dynamic LAG are
supported.
DNS Considerations
Domain Name System (DNS) is required to deploy the VxRail cluster and for
ongoing operations. VxRail supports internal or external DNS options. The internal
DNS service runs on the VxRail Manager VM.
• If a VxRail-managed vCenter is used, the internal or external DNS option is
supported.
• If joining an existing vCenter, only an external DNS option is supported.
• VxRail components that are connected to the Management or vCenter Server
port groups must be able to access the DNS server. These components include
VxRail Manager, vCenter Server, Log Insight (optional), and each ESXi host in
the VxRail cluster.
• For the external DNS option, forward and reverse lookup records must be
created for each component before cluster deployment.
• The internal DNS option only supports naming services for the VxRail cluster
components and does not support naming services outside of the cluster.
• vMotion and vSAN IP addresses do not require DNS entries.
• If an internal DNS is deployed, it can be migrated to an external DNS or a
forwarder to an upstream DNS may be added later.
VxRail Automatic Discovery
For a VxRail deployment, the automatic discovery option enables a simplified

method for detecting cluster nodes. When powered on, VxRail Manager uses IPv6

multicast network protocols to discover VxRail nodes. The IPv6 multicast traffic is
sent over internal management network that is used for discovery only. The default
VLAN ID assigned to the internal management network is 3939 and can be
changed.
Each VxRail node runs the VMware Loudmouth service and an election service to
support build process automation. VxRail Manager also runs the VMware
Loudmouth service.
• The internal management VLAN (discovery) must be configured on the ToR
switches for node ports and Inter-Switch Links (ISLs).
• ToR switches must be configured to allow IPv6 multicast network protocols.
• IPv6 multicast network protocols must be allowed in the customer environment.
VxRail IP Address Discovery
For a VxRail deployment, the IP address discovery option is a manual method for
detecting cluster nodes. Each VxRail node management IP address is manually set
in the ESXi shell on the node. On the primary node, the VxRail Manager VM is
manually configured with an IP address. The external management network is used
for IP address discovery.
The IP address discovery option is used when the customer has concerns about
using either IPv6 or multicast network protocols. Since nodes are available over the
external management network, the default ESXi root password can be changed to
address security concerns.
• IPv6 multicast network protocols are not required.

.
• The internal management VLAN (3939) is not configured on ToR switches.

• IP address discovery and automatic discovery modes cannot be mixed.
• Host console access over the iDRAC management network is required for
remote configuration.
Knowledge Check: Plan For a VxRail Deployment
Knowledge Check: Plan For a VxRail Deployment (1/4)
1. Why would the "Join an existing vCenter Server" option be selected for
vCenter deployment? Select three (3).
a. To deploy a second VxRail cluster and minimize the number of vCenter
servers.
b. To deploy a VxRail cluster in a customer's VMware environment.
c. To deploy a VxRail cluster and use a preconfigured virtual distributed
switch.
d. To deploy a stand-alone single VxRail cluster.
e. To deploy the first of many VxRail clusters with a VxRail-managed vCenter.
2. A customer is using the VxRail Configuration Portal to build a cluster

configuration for the second VxRail cluster in a data center. The customer
wants to use the VxRail-managed vCenter Server that is deployed on the first
VxRail cluster. For the VDS, the customer is willing to use the default
configuration settings that follow VxRail best practices. The customer would
like to automate the deployment tasks when possible. Each node has an
integrated 4x10 GbE NIC. IPv6 multicast traffic is allowed in the data center.
Which configuration options must be selected to build this second VxRail cluster
configuration? Select three (3).
a. VDS Predefined Network Profile Configuration
b. VDS Custom Network Profile
c. Use the VxRail vCenter Server
d. Join an Existing vCenter Server

e. Automatic Discovery
f. IP Address Discovery

configuration for the first VxRail cluster in a data center. The customer wants to
use the vCenter that is deployed in the environment and use an existing VDS.
The customer would like to automate the deployment tasks when possible.
Each node has an integrated 4x10 GbE NIC. IPv6 multicast traffic is not
allowed in the data center.
Which configuration options must be selected to build this cluster configuration?

Select three (3).

configuration for the first VxRail cluster in a data center. The customer has no
existing vCenter. For the VDS, the customer is willing to use the default
configuration settings that follow VxRail best practices. The customer would
like to automate the deployment tasks when possible. Each node has an
integrated 2x25 GbE NIC. Only IPv4 traffic is allowed in the data center.
Which configuration options must be selected to build this cluster configuration?

Select three (3).

.

VxRail Configuration Portal
VxRail Configuration Portal Overview
The VxRail Configuration Portal is a central interface to plan and prepare VxRail
cluster deployments. Project and cluster configuration information is entered using
wizards. Checklists, cluster reports, and configuration files are then available once
the configurations are saved.
To learn about the configuration portal, watch the video below.
Movie:
VxRail Configuration Portal Overview
https://players.brightcove.net/6057277730001/default_default/index.html?videoId=1
710762632463449907
Access the portal at https://vxrailconfiguration.dellemc.com/getStarted.
VxRail Configuration Portal Project
A VxRail Configuration Portal project contains customer and delivery service

provider contact information. A project is associated with a single customer and can
be associated with up to 200 VxRail cluster configurations. Contacts with a Dell
Technologies Support account can be granted access to a project and the
associated cluster configurations.
This example shows a new project with customer and service provider contacts.
The project has been associated with a cluster.

.
VxRail Configuration Portal - My Projects page
VxRail Configuration Portal Cluster Configuration
A VxRail Configuration Portal cluster configuration contains settings that are used
to deploy a VxRail Cluster. Project team members enter configuration information
using a wizard. The information is validated, and a configuration file is created that
can be used for deployment. A cluster configuration is associated with only one
project.
Configuration information is gathered during the planning phase of a VxRail

deployment project. The configuration information includes: cluster name, project
name, cluster type, vCenter deployment type, VDS settings, node information, and
network settings.
This example shows the cluster configuration categories that are covered in the
wizard.

VxRail Cluster Configuration Categories
VxRail Configuration Portal cluster configuration
Demonstration: Create a Cluster in the VxRail Configuration

Portal
To learn about Creating a Cluster in the VxRail Configuration Portal, watch the
video below.
Movie:
Interaction: Create a Cluster Configuration in the VxRail

Configuration Portal
The Online Course Contains an Interaction Here.

[Detailed description of the Interaction for Guides]

.
VxRail Cluster Configuration Report and Pre-Deployment

Checklist
VxRail Cluster Configuration Report
The VxRail cluster configuration report contains the configuration settings,

configuration status, warnings, and errors. The report provides a more readable
format of the configuration than the JSON formatted configuration file. The
configuration report can be used to:
• Validate the environment before deployment.

• Validate the configuration settings before downloading the JSON configuration
file.
• Create backup documentation for disaster recovery plans.
To learn about how to access the HTML version of the report or export a Microsoft
Word version, select each tab below.
View HTML Page
To access the configuration report, select the My Clusters tab, select the cluster in
the list, and click the VIEW REPORT button.
My Clusters tab of the VxRail Configuration Portal

Example Report: HTML
Export Microsoft Word Document
On the HTML version of the report, click the EXPORT CONFIGURATION REPORT
button to export a Microsoft Word document version.
VxRail Configuration Report Heading
Example Report: Microsoft Word
Pre-deployment Checklist
The pre-deployment checklist provides the tasks that must be completed before
beginning a VxRail cluster deployment. The checklist also provides links to online
help which contains additional links to resources used to complete the checklist.
To access the pre-deployment checklist, select the My Pre-deployment

Checklists tab, select the cluster in the list, and click the VIEW CHECKLIST
button.

.
My Pre-deployments Checklist tab on the VxRail Configuration Portal
Example: Checklist
Interaction: Export a Configuration Report and Complete the

Pre-Deployment Checklist
[Detailed description of the Interaction for Guides]
Download VxRail Cluster Configuration File for Deployment
The cluster configuration file is a JSON file that contains the complete set of
configuration properties for a cluster. The file can be used to build a cluster.
The My Deployments view of the VxRail Configuration Portal provides two

methods for installing clusters using the JSON file:
• Wizard - A JSON file is downloaded from the portal. This file can be imported
into the VxRail Deployment wizard.
• Command line interface (CLI) tools - The JSON file and a PowerShell module
are downloaded from the portal. The module is installed on a Windows machine
and then run using the JSON file for configuration inputs.

VxRail Configuration Portal - My Deployments
The cluster configuration file can be downloaded from two other locations in the
portal.
Knowledge Check: Use VxRail Configuration Portal to Prepare

for a VxRail Deployment
Knowledge Check: Use VxRail Configuration Portal to Prepare for a

VxRail Deployment (1/2)
1. What is the purpose of creating a cluster in the VxRail Configuration portal?

a. To build and validate a configuration file that is used to later deploy a
VxRail cluster.
b. To deploy a VxRail cluster and ToR switches in a data center.
c. To build and validate a bill of materials for a VxRail cluster purchase.
d. To deploy a vCenter Server and multiple VxRail nodes in a data center.
Knowledge Check: Use VxRail Configuration Portal to Prepare for a

VxRail Deployment (2/2)
2. An implementer wants to prepare a data center for an upcoming VxRail cluster

.
deployment. What should the implementer reference to find guidance and

documentation for completing preparation tasks?
a. Pre-deployment Checklist
b. Configuration Report
c. Configuration File
d. Final Checklist

You Have Completed This Content
Click the Save Progress and Exit button in the course menu or below to
record this content as complete.
Go to the next learning or assessment, if applicable.

.
Appendix
Custom Network Profile with Two New VDSs
Number of VDS
Distributed port
groups assigned
to each VDS
VDS MTU
Number of NICs
assigned to the
Host NICs
assigned to each
Active/standby
teaming and
load-balancing
VDS MTU
Active/active
teaming and
load-balancing

Appendix
Custom Network Profile with two New VDSs
Custom Network Profile with Two Existing VDSs
Number of VDS
Distributed port groups

assigned to each VDS
Name of the existing VDS
Number of NICs assigned

to the VDS
Host NICs assigned to

each uplink port group
Distributed port group

names on the VDS
Is LAG configured?
Host NICs assigned to the

LAG uplink on the VDS
Custom network profile with two existing VDSs
Page 32 © Copyright 2020 Dell Inc.

Appendix
VMware Loudmouth Service

VMware Loudmouth is a service that runs on VxRail nodes and the VxRail Manager
VM. The service enables automatic discovery of nodes. The service is used during
Initial cluster configuration, cluster expansion, and failed node replacement.
Loudmouth is an implementation of Zero Configuration Networking which enables
networking without having to configure a DHCP, DNS, and static network settings.
Loudmouth uses IPv6 multicast network protocols.
Loudmouth command syntax for:

• VxRail nodes - /etc/init.d/loudmouth <status> <stop> <start>
<restart>
• VxRail Manager VM - systemctl <status> <stop> <start>
<restart> vmware-loudmouth
VxRail Election Service

The VxRail election service runs on all the VxRail nodes. The election process
elects one node to host the VxRail Manager VM, and this node becomes the
primary node. The VxRail Manager VM is powered on automatically on this node.
The primary node is the node with the lowest product ID/SN (PSNT).
Election service command syntax for VxRail nodes: /etc/init.d/vxrail-

election <start> <stop> <status> <restart>
To learn more about the election service and how to force a node to become the
primary, review KB 5801.

Appendix
VxRail Cluster Configuration Report - HTML

Appendix
VxRail Cluster Configuration Report - Microsoft Word

Appendix
Completed Pre-deployment Checklist with Help
Cluster Configuration JSON File

The cluster configuration file is a text-based file with structured data that follows the
JavaScript Object Notation (JSON) standard format.
Example VxRail cluster configuration JSON file

Appendix
Cluster Configuration File Download Locations

Download the file from the cluster Validate Configuration File tab when editing a
cluster, or from the My Clusters view in the VxRail Configuration Portal.
Cluster configuration file download locations

Glossary
Affinity Rules
The Affinity rule is used to specify which site (Preferred or Secondary) a vSAN
object resides on. It is only honored when a Primary Failures to Tolerate rule is set
to 0. Since the Affinity rule is a Storage Policy rule, it only pertains to vSAN objects
and not virtual machine placement.
Application Virtual Network (AVN)

Application Virtual Network (AVN), also known as NSX-T Virtual Network Segments
are software defined overlay networks that can span a defined zone of clusters.
The AVNs provides connectivity for the vRealize suite of management applications
and enables connectivity to the upstream external network.
Bearer Authentication
HTTP authentication method that uses a token instead of a username and
password combination.
Dell Security Advisory (DSA) and Dell Technical Advisory (DTA)

A Dell Security Advisory (DSA) and a Dell Technical Advisory (DTA) may map to
multiple publicly known Common Vulnerabilities and Exposures (CVEs). CVEs
includes items from both Dell, VMware, Open software, so on consisting of a VxRail
solution. When you signs-up for DSA notifications, you are alerted accordingly. You
see these same CVEs on VMware's site if applicable.
Dell Upgrade Packages (DUPs)

Dell Upgrade Packages (DUPs) are upgrade packages for the BIOS, iDRAC,
Network Controller firmware, RAID Controller firmware, and so on. The DUPs are
included as part of the VxRail RASR images. The required firmware is updated as
needed, as part of the RASR or factory reset process of a VxRail node.
Fault Domain
A fault domain consist of one or more vSAN hosts grouped according to their
physical location in the data center. Fault domains enable vSAN to tolerate failures
of entire physical racks and failures of a single host, capacity device, network link,
or a network switch dedicated to a fault domain. When fault domains are not
configured, hosts behave as individual fault domains.

JSON
JavaScript Object Notation (JSON) is a lightweight, text-based, language-
independent data interchange format. JSON uses human-readable text to store
and transmit data objects consisting of attribute-value pairs and array datatypes.
Go to https://www.json.org/json-en.html for more information.
LZ4
LZ4 is a lossless data compression algorithm that is focused on compression and
decompression speed.
Network Validation Tool (NVT)

The Network Validation Tool (NVT) for VxRail automates validation of network
readiness at the customer site before deployment of the VxRail system. New
deployments require a set of reserved IP addresses for VMware ESXi hosts and
service virtual machines. The customer should also configure fully qualified domain
names in their DNS server and complete the top-of-rack switch configuration (if
customer is bringing their own switch). This tool ensures that there is no missing
configuration. If there is any missing configuration, customer can complete it before
scheduling deployment.
NIC Port Aliases

On a VxRail node physical NIC, ports start at number zero and go up to four,
depending on the port count on the NIC. ESXi assigns aliases to these ports. The
aliases are assigned first to the integrated NIC and then the PCI NICs in order of
location on the PCI bus. The aliases start with "vmnic" and count from "vmnic0" to
"vmnicX" where X is the total number of ports across all NICs.
NIC Port Aliases

On a VxRail node physical NIC, ports start at number zero and go up to four,
depending on the port count on the NIC. ESXi assigns aliases to these ports. The
aliases are assigned first to the integrated NIC and then the PCI NICs in order of
location on the PCI bus. The aliases start with "vmnic" and count from "vmnic0" to
"vmnicX" where X is the total number of ports across all NICs.
NSX-T Federation

NSX-T Federation enables administrators to manage multiple NSX-T deployments,
create global networking with failover capabilities, and enable disaster recovery
solution. NSX-T Federation includes Global Manager. The NSX-T Global Manager
a central component that is deployed as a cluster which has global reach and
manages one or more Local Managers.
Pre-engagement Questionnaire (PEQ)

The PEQ is a macro enabled spreadsheet that is used to document the VxRail
deployment parameters. It is used to hand-off information between Presales,
Project Management and the Delivery staff. The PEQ version maps to a specific
VxRail version. It improves deployment accuracy, efficiency, and customer
satisfaction. It creates a configuration file that is used to configure the VxRail
cluster.
Preferred and Secondary Site

The Preferred site is the site that must remain active when there is a failure and the
site can no longer communicate. In an active/active configuration, the virtual
machines can run on any of the two data sites. When network connectivity between
the sites is lost, but both the sites have connectivity to the Witness. The Witness
chooses the Preferred site to remain active. The components of the Preferred site
remain active while the Secondary site is marked down and its components are
marked as absent.
RAID 1 Mirroring
Mirroring can accommodate an FTT setting of 1, 2, or 3. If FTM is set to mirroring,
for the N number of failures that are tolerated, N+1 copies of the object are created.
Mirroring requires witness components. The number of witnesses is equal to the
FTT setting. RAID 1 with FTT setting of 1 requires a minimum of 3 hosts. RAID 1
with FTT setting of 2 requires a minimum of 5 hosts and, RAID 1 with FTT setting of
3 requires a minimum of 7 hosts.
RAID 5/6 Erasure Coding

Erasure coding can only accommodate FTT=1 (RAID 5) or FTT=2 (RAID 6).
Erasure coding does not require a witness disk stripe per object. Objects are
objects on disk like snapshots, VMDK files, and witnesses. VMware recommends
leaving the default value of one. Force provisioning can be used to override select
variables. RAID 5 (Erasure coding) with FTT setting of 1 requires a minimum of 4
hosts.

RAID 6 Erasure Coding
RAID 6 (Erasure Coding) with FTT setting of 2 requires a minimum of 6 hosts.
Remaining write endurance

SSDs have a finite number of program and erase cycles. Each SSD is warranted to
a maximum amount of data that is written to the device in total bytes written. The
SSD self-monitors for the remaining write endurance limits. Software management
applications can provide notifications on the remaining write endurance limits.
RESTful API
A useful analogy for APIs is human language. Language enables humans to
communicate with each other by providing structure for how that communication
takes place. Application Programming Interfaces (APIs) function in a similar
manner.
APIs establish rules that enable a client and server to communicate data that would
otherwise be unmanageable. Representation State Transfer (REST) API is a
specific design methodology for API communications. REST API is an architectural
style for client/server communications because it promotes scalability, simplicity of
interface, and independence of communications.
Secure Hash Algorithm (SHA-1)

SHA-1 is a cryptographic hash function standard that is used for data integrity
verification (and digital signatures). SHA-1 produces a 20 bytes (160-bit) signature.
SmartFabric Service
VxRail systems that are configured with SmartFabric Services automatically detect
VxRail nodes during expansion. VxRail nodes advertise NIC port information,
system name, and description via the LLDP protocol to the SmartFabric. The
SmartFabric uses the internal management network to apply network state
changes to the top-of-rack (ToR) switches. SmartFabric configuration includes
creating and configuring L2 VLANs and bonded port channels.
Spanning Tree Protocol (STP)

STP is a network protocol that builds a logical loop-free topology for Ethernet
networks. The basic function of STP is to prevent bridge loops and the broadcast
radiation that results from them. During the execution of the Spanning-Tree
Algorithm, STP forces the ports to go into five different states: Blocked, Listen,
Learn, Forward and Disabled. All ports start in the blocked mode to prevent the
switch from creating a loop.
STP is running by default on all ports of the switch. STP makes each port wait up to
50 s before data can be sent on the port. This delay in turn can cause problems
with some applications or protocols including VxRail nodes.
Cisco devices implemented PortFast to alleviate problems that are related to this
delay. The terminology might differ between different vendor devices. PortFast
causes a port to enter the forwarding state almost immediately by dramatically
decreasing the time of the listening and learning states. PortFast minimizes the
time that it takes for the server to come online, thus preventing problems with
applications such as DHCP and DNS. The use of PortFast should only be
implemented when the port on the switch is directly connected to a server and
never to another switch.
Transport Layer Security (TLS)

Transport Layer Security (TLS) is a cryptographic protocol that encrypts data that is
shared between applications over the Internet.
VxRail RASR ISO

VxRail version-specific ISO package is used to reset Dell PowerEdge based VxRail
nodes to a factory state. The RASR ISO package for different VxRail versions can
be downloaded from the Dell Support site by authorized personnel -
https://www.dell.com/support/home/en-us/product-support/product/vxrail-appliance-
series/drivers.
VxRail RASR USB

USB drive with version and model-specific VxRail software image that is used to
reset VxRail nodes to factory state. The VxRail RASR USB is created from the
version-specific VxRail RASR ISO. Follow the SolVe procedure to create version
and model-specific VxRail RASR USB.
VxRail-managed vCenter

A vCenter that is deployed during an initial VxRail cluster build and is upgraded
using VxRail Manager.
VxRail-managed vCenter
A vCenter that is deployed during an initial VxRail cluster build and is upgraded
using VxRail Manager.
Witness Traffic Separation (WTS)

Witness Traffic Separation (WTS) allows an alternate VMkernel interface to be
designated to carry Witness traffic. This feature supports more flexible network
configurations by allowing separate networks for node-to-node and node-to-witness
traffic.

VxRail 7.0.XXX Planning

Uploaded by

Copyright:

Available Formats

VxRail 7.0.XXX Planning

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VxRail 7.0.XXX Planning

Uploaded by

Copyright:

Available Formats

VXRAIL 7.0.

Plan for a VxRail Deployment ...................................................................................... 1

VxRail Configuration Portal ....................................................................................... 22

VxRail 7.0.241 Planning-SSP - Lesson

Page ii © Copyright 2021 Dell Inc.

VxRail 7.0.241 Planning-SSP - Lesson

© Copyright 2020 Dell Inc. Page iii

Plan for a VxRail Deployment

VxRail Architecture Overview

In a VxRail environment, the cluster is the primary unit of deployment.

A standard VxRail cluster is made up of the following components:

VxRail 7.0.241 Planning-SSP - Lesson

© Copyright 2021 Dell Inc. Page 1

− vCenter Server - Centralized platform that provides management and

Standard VxRail Architecture

VxRail Deployment Process Overview

To learn about the deployment process, watch the video below.

The web version of this content contains a movie.

VxRail 7.0.241 Planning-SSP - Lesson

Page 2 © Copyright 2021 Dell Inc

vCenter Options for a VxRail Deployment

vCenter Server Options:

VxRail Deployment Wizard and Configuration Portal - vCenter Server Options

vCenter Option 1: Use the VxRail vCenter Server

A new VxRail-managed vCenter Server is deployed on a new VxRail cluster. This

VxRail 7.0.241 Planning-SSP - Lesson

© Copyright 2021 Dell Inc. Page 3

vCenter Server VxRail Manager

New VxRail Cluster

New VxRail-managed vCenter Server

vCenter Option 2: Join an Existing vCenter Server

VxRail 7.0.241 Planning-SSP - Lesson

Page 4 © Copyright 2021 Dell Inc

Existing VxRail-managed vCenter Server

A new VxRail cluster is deployed with an existing VxRail-managed vCenter Server

VxRail Manager vCenter Server VxRail Manager

ESXi ESXi ESXi ESXi

ESXi ESXi ESXi ESXi

New VxRail Cluster Existing VxRail Cluster

New Cluster with an Existing VxRail-managed vCenter

VxRail 7.0.241 Planning-SSP - Lesson

© Copyright 2021 Dell Inc. Page 5

Existing Customer-supplied vCenter Server

VxRail Manager vCenter Server

New VxRail Cluster

New Cluster with an Existing Customer-supplied vCenter

VxRail 7.0.241 Planning-SSP - Lesson

Page 6 © Copyright 2021 Dell Inc

VxRail Network Switches

Management Core Production Core

VxRail 7.0.241 Planning-SSP - Lesson

© Copyright 2021 Dell Inc. Page 7

VxRail Network Interface Cards

VxRail models support various configurations of the integrated network interface

iDRAC Integrated NIC

VxRail node with integrated and PCIe NICs

Virtual Networking Overview

In a standard VxRail cluster, a vSphere Distributed Switch (VDS) provides virtual

VxRail 7.0.241 Planning-SSP - Lesson

Page 8 © Copyright 2021 Dell Inc