Dell EMC VxFlex Ready Node 14G User manual

Quick Start Guide
14G Servers
Dell EMC VxFlex Ready Node
Deploying VxFlex OS in a 2-Layer Environment
P/N 302-004-163
REV 03
June 2018
Note
Previous versions of Dell EMC VxFlex Ready Node were marketed under the name Dell
EMC ScaleIO Ready Node.
All software and technical aspects described in this document apply equally, regardless
of how the product was branded.
Topics include:
lPreface...................................................................................................................2
lSystem requirements..............................................................................................3
lBefore You Begin.................................................................................................... 8
lPreparing the Linux environment............................................................................ 9
lStart the Linux deployment.................................................................................... 9
lMonitoring the deployment.................................................................................... 11
lRegistering the vSphere plug-in............................................................................ 12
lInstalling SDC on ESX with vSphere plug-in.......................................................... 13
lAdding an external SDC to an existing VxFlex OS system......................................14
lEnabling storage....................................................................................................17
lInstalling and opening the VxFlex OS GUI.............................................................. 17
lRetrieve device paths in a Linux server..................................................................18

Preface
As part of an effort to improve its product lines, Dell EMC periodically releases
revisions of its software and hardware. Therefore, some functions described in this
document might not be supported by all versions of the software or hardware
currently in use. The product release notes provide the most up-to-date information
on product features.
Contact your Dell EMC technical support professional if a product does not function
properly or does not function as described in this document.
Note
This document was accurate at publication time. Go to Dell EMC Online Support
(https://support.emc.com) to ensure that you are using the latest version of this
document.
Previous versions of Dell EMC VxFlex OS were marketed under the name Dell EMC
ScaleIO.
Similarly, previous versions of Dell EMC VxFlex Ready Node were marketed under the
name Dell EMC ScaleIO Ready Node.
References to the old names in the product, documentation, or software, etc. will
change over time.
Note
Software and technical aspects apply equally, regardless of the branding of the
product.
Related documentation
The release notes for your version includes the latest information for your product.
The following Dell EMC publication sets provide information about your VxFlex OS or
VxFlex Ready Node product:
lVxFlex OS software (downloadable as VxFlex OS Software <version>
Documentation set)
lVxFlex Ready Node with AMS (downloadable as VxFlex Ready Node with AMS
Documentation set)
lVxFlex Ready Node no AMS (downloadable as VxFlex Ready Node no AMS
Documentation set)
lVxRack Node 100 Series (downloadable as VxRack Node 100 Series
Documentation set)
You can download the release notes, the document sets, and other related
documentation from Dell EMC Online Support.
Typographical conventions
Dell EMC uses the following type style conventions in this document:
Bold Used for names of interface elements, such as names of windows,
dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)
Italic Used for full titles of publications referenced in text
Quick Start Guide
2VxFlex Ready Node Quick Start Guide

Monospace Used for:
lSystem code
lSystem output, such as an error message or script
lPathnames, filenames, prompts, and syntax
lCommands and options
Monospace italic Used for variables
Monospace bold Used for user input
[ ] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{ } Braces enclose content that the user must specify, such as x or y or
z
... Ellipses indicate nonessential information omitted from the example
Where to get help
Dell EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about Dell
EMC products, go to Dell EMC Online Support at https://support.emc.com.
Technical support
Go to Dell EMC Online Support and click Service Center. You will see several
options for contacting Dell EMC Technical Support. Note that to open a service
request, you must have a valid support agreement. Contact your Dell EMC sales
representative for details about obtaining a valid support agreement or with
questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Send your opinions of this document to
[email protected].
System requirements
This section lists the requirements for system components.
This section is specific to VxFlex OS software deployments.
For VxFlex Ready Node systems, refer to your product's Hardware Configuration and
Operating System Installation Guide.
VxFlex OS cluster components
List of required VxFlex OS servers.
lVxFlex OS component servers:
n3-node cluster
– One Master MDM
Deploying VxFlex OS in a 2-Layer Environment
System requirements 3

– One Slave MDM
– One Tie Breaker
– Minimum of three SDSs (on the same servers as the above components, or
on three different servers)
– SDCs, up to the maximum allowed (on the same servers as the above
components, or on different servers)
n5-node cluster
– One Master MDM
– Two Slave MDMs
– Two Tie Breakers
– Minimum of three SDSs (on the same servers as the above components, or
on three different servers)
– SDCs, up to the maximum allowed (on the same servers as the above
components, or on different servers)
lVxFlex OS Gateway server on a separate server, or together with an MDM or SDS.
Do not install the VxFlex OS Gateway on an SDC server or on an SDS on which
RFcache will be enabled.
Physical server requirements
Table 1 Server physical requirements
Component Requirement
Processor One of the following:
lIntel or AMD x86 64-bit (recommended)
lIntel or AMD x86 32-bit (for Xen only)
Physical memory VxFlex OS component requirements:
l500 MB RAM for the Meta Data Manager (MDM)
l500 MB RAM for each VxFlex OS Data Server (SDS)
l50 MB RAM for each VxFlex OS Data Client (SDC)
Disk space l1 GB for each physical node or Xen hypervisor
l10 GB for VMware topologies
Connectivity One of the following:
l1/10/25/40/50/100 GbE network
lIP-over-InfiniBand network
Dual-port network interface cards (recommended)
Ensure the following:
lThere is network connectivity between all components.
lNetwork bandwidth and latency between all nodes is acceptable, according to application
demands.
lEthernet switch supports the bandwidth between network nodes.
lMTU settings are consistent across all servers and switches.
Quick Start Guide
4VxFlex Ready Node Quick Start Guide

Table 1 Server physical requirements (continued)
Component Requirement
lThe following TCP ports are not used by any other application, and are open in the local
firewall of the server:
nMDM: 6611 and 9011
nSDS: 7072 (for multiple SDS, ports 7073-7076)
nLight Installation Agent (LIA): 9099
nSDBG ports: MDM 25620, SDS 25640, Multiple SDS 25641-25644 (not 25640).
These ports are used by VxFlex OS internal debugging tools to extract live information
from the system for debugging purposes.
lThe following UDP port is open in the local firewall of the server:
nSNMP traps: 162
Note
You can change the default ports. For more information, see “Changing default ports” in the
user documentation.
Supported operating systems
The following is a list of operating systems supported by this version of VxFlex OS.
For the most updated list, see the EMC Simple Support Matrix (ESSM) at https://
elabnavigator.emc.com/eln/elnhome.
Table 2 Supported operating systems -VxFlex OS components
Operating system Requirement
Linux Supported versions ( for exact versions, see the ESSM):
lRHEL 7.3, 7.4
lSUSE 12.2
Packages required for all components, all Linux flavors:
lnumactl
llibaio
Additional needs for specific operating systems:
lSUSE 12.2
nhwinfo
nnet-tools
npciutils
nethtool
lHypervisor support: Red Hat KVM
Additional packages required for MDM components:
lbash-completion (for SCLI completion)
Deploying VxFlex OS in a 2-Layer Environment
Supported operating systems 5

Table 2 Supported operating systems -VxFlex OS components (continued)
Operating system Requirement
lLatest version of Python 2.X
When installing the MDM component on Linux CentOS 6 or RHEL 6 hosts (for software-only
systems), set the shared memory parameter in the /etc/sysctl.conf file to at least the
following value: kernel.shmmax=209715200. To use this value, type the sysctl -p
command.
To use the secure authentication mode, ensure that OpenSSL 64-bit v1.0.1 or later (v1.1,
however, is not supported) is installed on all servers in the system.
llibopenssl1_0_0-1.0.1g-0.40.1.x86_64.rpm
lopenssl1-1.0.1g-0.40.1.x86_64.rpm
To use LDAP, ensure that OpenLDAP 2.4 is installed on all servers.
Hypervisors lVMware ESXi operating systems: 6.0 U3 or 6.5, managed by vCenter 6.0 or 6.5
lRed Hat KVM
External SDC support
In addition to being supported on all VxFlex OS operating systems, SDC can be
deployed on external servers.
Component Requirement
Supported external servers lUNIX: AIX 7.2
lhLinux: 4.x/5.x
VxFlex OS GUI server requirements
Component Requirement
Supported operating systems lWindows:
n7, 2008 R2, 10, 2012 or 2012 R2, 2016.
Server Core editions are not supported.
lLinux:
nCentOS 6.x-7.x, Oracle Linux 6.5/7.x
nRed Hat 6.x-7.x
nSUSE 11.3, 11.4, 12, 12.1, 12.2
nUbuntu 14.04, Ubuntu 16.04
Other lv1.8 (64-bit), build 149 or earlier.
You can download previous versions from this link: http://www.oracle.com/technetwork/
java/javase/downloads/java-archive-javase8-2177648.html
Quick Start Guide
6VxFlex Ready Node Quick Start Guide

Component Requirement
For SUSE 12, see “Installing Java on SUSE 12 servers.” in the VxFlex OS Deployment Guide
or the VxFlex OS User Guide .)
lScreen resolution: 1366 x 768 minimum
VxFlex OS Gateway server requirements
Component Requirement
Supported operating systems lWindows 2008 R2, 2012 R2, or 2016, including the Visual C++ redistributable 2010
package, 64-bit. Server Core editions are not supported.
lLinux RHEL 6.x or 7.0, SUSE 11.3, and SUSE 12
Every server requires 2 cores and a minimum of 3 GB available RAM.
Connectivity The following TCP ports are not used by any other application, and are open in the local
firewall of the server: 80 and 443 (or 8080 and 8443).
You can change the default ports. For more information, see “Changing default ports” in the
user documentation.
Supported web browsers lInternet Explorer 10, or later
lFirefox, version 42, or later
lChrome, version 45, or later
Java lv1.8 (64-bit), build 149 or earlier.
You can download previous versions from this link: http://www.oracle.com/technetwork/
java/javase/downloads/java-archive-javase8-2177648.html
Other lFor a VxFlex OS Gateway server on a Windows node, the Windows Management
Instrumentation service must be enabled on the VxFlex OS Installation Manager server
and on all Windows VxFlex OS nodes.
lDo not install the VxFlex OS Gateway on a server on which RFcache will be enabled or on
which SDC will be installed.
lThe VxFlex OS Gateway server must have connectivity to all the nodes that are being
installed. If you are using separate networks for management and data, the server must be
able to communicate with both networks.
Other requirements
VxFlex OS requires that you use a minimum of three SDS servers, with a combined
free capacity of at least 300 GB. These minimum values are true per system and per
Storage Pool.
All VxRack Node 100 Series nodes have the minimum disk size as part of the node
specification.
Supported hardware configurations
The supported hardware configurations are listed in the Simple Support Matrix for
your software version. Download this file from https://elabnavigator.emc.com/eln/
Deploying VxFlex OS in a 2-Layer Environment
VxFlex OS Gateway server requirements 7

elnhome. Click Simple Support Matrices > Storage and select the desired product
and version.
Before You Begin
This topic provides an overview of deploying VxFlex OS in a 2-layer configuration.
Deployment begins with preparing the Linux Backend, using the VxFlex OS Installation
Manager.
For Linux and Windows SDC servers, you can install the SDC using the VxFlex OS
Installation Manager, or you can install the SDC manually. Both methods are described
in this document.
For ESXi SDC servers, it is recommended to install the SDC using the VMware plug-in,
or you can install it manually. Both methods are described in this document.
For all other cases and customization options, use the procedures described in the
VxFlex OS Deployment Guide .
Note
The EMC-supplied hardware configurations satisfy all of the hardware requirements.
Before deploying VxFlex OS on ESX servers:
lThe host from which you run the PowerShell (.ps1) script must meet the following
prerequisites:
nRuns on supported Windows OS
nPowerCLI is installed
nJava is installed
nHas incoming and outgoing communication access to the vCenter
lThe vSphere web client (Virgo) server must have network connectivity to the host
on which the PowerShell script will be used.
lConfigure the required network interfaces and IP addresses, and configure disks.
For more information, see the VxFlex Ready Node Hardware Configuration and
Operating System Installation Guide .
These documents are available from EMC Online Support (https://
support.emc.com).
lFor the most up-to-date information about this release, see
VxFlex OS Release
Notes for your version, available from Online Support.
VxFlex OS deployment steps:
1. Prepare the Linux environment.
2. Start the Linux deployment. For Linux and Windows SDC servers, this may include
installing SDCs.
3. Monitor the deployment.
4. For ESX servers, register the vSphere plug-in and install and configure the SDCs.
5. Manually install and configure SDCs (if you have not done so yet).
6. Post-deployment:
lEnable storage.
Quick Start Guide
8VxFlex Ready Node Quick Start Guide

lRun the VxFlex OS GUI.
Preparing the Linux environment
Prepare the Linux environment before deploying VxFlex OS.
Before you begin
Ensure that all VxFlex OS components and the VxFlex OS Gateway server meet the
system requirements.
This step prepares the VxFlex OS Gateway server. The VxFlex OS Gateway includes
the VxFlex OS Installation Manager, which is used to deploy the system in the next
steps. The VxFlex OS Gateway server can be a Windows or Linux server.
Procedure
1. From the Online Support site https://support.emc.com/products/33925,
download and extract the complete software download for this version.
2. Create the VxFlex OS Gateway server by running the following command (all on
one line), where
new_GW_admin_password is a password that you define to
access the VxFlex OS Installation Manager:
GATEWAY_ADMIN_PASSWORD=<new_GW_admin_password> rpm -U /tmp/
EMC-ScaleIO-gateway-2.6-<build>.X.x86_64.rpm --nodeps
The VxFlex OS Gateway server is ready.
3. Log in to the VxFlex OS Gateway server by typing the following URL in your
browser: https:// <GW_Server_IP_Address> , where GW_Server_IP_Address is
the IP address of the server where you installed the VxFlex OS Gateway
package.
Use the default username, admin, and the password you created in the previous
step.
4. Accept the certificate warning; alternatively, install your own certificate for the
Tomcat server.
The Installation Manager Welcome screen appears.
Note
If the Welcome screen does not appear, see the "Troubleshooting" section in
the VxFlex OS Deployment Guide .
Start the Linux deployment
Use the VxFlex OS Installation Manager to start the Linux deployment.
Procedure
1. Upload packages:
a. From the Welcome screen, select the Packages tab.
The Manage Installation Packages window appears.
b. Click Browse, and select all the extracted VxFlex OS component installation
packages, for all relevant operating systems.
Deploying VxFlex OS in a 2-Layer Environment
Preparing the Linux environment 9

Minimally, you must select these packages:
lLIA
lMDM
lSDC
lSDS (The SDSx packages are not needed.)
c. Click Open.
d. Click Upload.
The packages are uploaded to the VxFlex OS Installation Manager, and are
displayed in the file table.
2. Click Proceed to Install.
3. Prepare the CSV topology file:
a. Enter the Backend node information in the CSV topology file:
In 2-layer configuration, the Linux servers will form the MDM cluster, and
each of those servers will also be SDS.
The following example shows a sample CSV topology file. Only those
columns with values in them are shown:
Note
When specifying the Linux SDS devices, use persistent device names. You
can find these names by running the command: # ls -l /dev/disk/by-
id/ *.
b. Add SDCs to the CSV (or later in the process), according to the following
table:
SDC
server
OS
Add SDCs by one of the following methods:
Linux or
Windows
lWith the VxFlex OS Installation Manager, by adding a row to the
CSV for each SDC, as described in CSV topology file for 2-layer
deployment on page 11.
lManually after deploying the system, as described in Adding an
external SDC to an existing VxFlex OS system on page 14.
ESXi lWith the vSphere plug-in, later in the process, as described later in
this document.
lManually after deploying the system, as described in Adding an
external SDC to an existing VxFlex OS system on page 14.
The CSV is complete.
Quick Start Guide
10 VxFlex Ready Node Quick Start Guide

4. Upload the installation CSV file.
For more information, see the "Upload CSV file" section
5. In the Review Installation Configuration window, enter the required
passwords and other optional information.
6. Click Start Installation.
CSV topology file for 2-layer deployment
When deploying SDC nodes on a Linux or Windows server in a 2-layer environment,
add SDC rows to the CSV that only contain the values listed in this table.
Table 3 CSV topology spreadsheet-2-layer
Field Description Required
Domain If using a domain user, the name of the domain (not relevant for Linux)
Username
The name of the user. In Linux, this value is always root; in Windows, a user
with administrator rights (default: administrator).
Yes
Password
Password used to log in to the node. In Linux, the root password. In Windows,
the password of a user with administrator rights.
Yes
Operating System The server’s OS: linux or windows Yes
SDS-SDC Only IPs
SDS IP addresses to be used for communication among SDS and SDC nodes
only. Comma-separated, no spaces.
Note
For SDC-only nodes, enter the IP in this column.
Yes
Is SDC Yes Yes
perfProfileForSDC
Optional performance profile to set for SDCs. High or Default (same as
leaving this field empty).
SDC Name Name for the SDC.
Monitoring the deployment
Monitor and advance the VxFlex OS deployment.
The deployment wizard performs the following phases: query, upload, install, and
configure. You must monitor and approve moving from one phase to the next.
Procedure
1. Click the Monitor tab.
The Install-query screen appears:
Deploying VxFlex OS in a 2-Layer Environment
CSV topology file for 2-layer deployment 11

When each step completes, a message appears that describes the step
progress.
2. When the query phase is complete, click Start upload phase.
The Install - upload screen appears, displaying which VxFlex OS packages are
being uploaded to each server, and the status of each command.
3. When the previous phase is complete, click Start install phase.
The Install - install screen appears, displaying the status of the installation
commands.
4. When the previous phase is complete, click Start configure phase.
The Install - configure screen appears, displaying the status of the
configuration commands.
5. When the Completed Install Operation message appears, click Mark
operation completed.
Results
The wizard installation creates one Protection Domain and one Storage Pool, both
with default names, and used for creating volumes from devices.
Registering the vSphere plug-in
This topic describes how to register the VxFlex OS vSphere plug-in.
Procedure
1. Prepare the files:
a. From the Online Support site https://support.emc.com/products/33925,
download and extract the Complete Software download for this version.
b. From the extracted files, copy the following file to your designated host:
EMC-ScaleIO-vSphere-plugin-installer-2.6-<build>.X.zip
c. Extract the contents of the zip file.
2. With PowerCLI for VMware, set to Run as administrator, run the following
script:
VxFlexOSPluginSetup-2.6-<build>.X.ps1
Quick Start Guide
12 VxFlex Ready Node Quick Start Guide

a. Enter vCenter name or IP address, username, and password.
b. For Choose Mode, choose option 1, Register VxFlex OS plug-in.
c. Read the upgrade notice, and enter yto continue.
d. For Registration, choose either Standard (simplified, using embedded
Tomcat), or Advanced (to use an external web server or previously installed
VxFlex OS gateway).
To use the advanced options, refer to the VxFlex OS Deployment Guide .
e. Accept the thumbprint (if required).
3. Load the plug-in by logging out, and then logging back in to the vSphere web
client.
4. Return to the PowerCLI window, and press ENTER to return to the script menu
and complete the plug-in installation.
5. Go to the Home tab and verify that the VxFlex OS icon is visible in the
Inventories section.
The plug-in is registered. If the VxFlex OS icon is missing, the vSphere web
client server failed to register the plug-in, due to one of the following reasons:
lConnectivity problem between the vSphere web client server and the web
server storing the plug-in (for example, network / firewall etc.). Resolution:
Verify that there is communication between the vSphere web client server
and the web server storing the plug-in.
lURL problem when using an external web server. Resolution: Verify that the
URL is https:// and is pointing to the correct web server IP address (VxFlex
OS Gateway).
Installing SDC on ESX with vSphere plug-in
Use the VxFlex OS vSphere plug-in to install the SDC on ESX servers and deploy a
VxFlex OS system.
Procedure
1. Prepare the ESXi hosts:
a. Log in to the vSphere web client.
b. Open the VxFlex OS screen by clicking the VxFlex OS icon.
c. From the Basic Tasks section of the VxFlex OS screen, click Pre-
Deployment Actions.
The Pre-Deployment Actions screen appears.
d. Drill-down on the vCenter to display connected ESXi hosts.
e. For every ESXi host that might be part of this VxFlex OS system (even if
only in the future):
a. Select Install SDC.
b. To configure DirectPath (optional), select Configure DirectPath. (This
step selects the Install SDC, too.)
c. Select Convert ISO.
d. Type ESXi Root Password.
Deploying VxFlex OS in a 2-Layer Environment
Installing SDC on ESX with vSphere plug-in 13

f. Click Run.
The status appears in the dialog.
g. When finished, click Finish.
h. You must restart the ESXi hosts before proceeding.
2. Register the system:
a. From the VMware plug-in VxFlex OS screen, click Register VxFlex OS
system.
b. Enter the credentials of the system.
c. Click OK.
3. Deploy VxFlex OS:
a. From the VxFlex OS screen, click Deploy VxFlex OS environment.
The VxFlex OS deployment wizard is displayed.
b. In the Select Installation screen, select Add servers to a registered
VxFlex OS system, and select the system that you want to extend.
c. Continue with the deployment steps, adding the new SDC nodes.
You can skip steps that do not need to be changed. When adding
components, the wizard adjusts the displayed screens to options that are
relevant to the current VxFlex OS system.
4. Complete the deployment.
For further details, see the
VxFlex OS Deployment Guide .
Adding an external SDC to an existing VxFlex OS system
In a 2-layer architecture, after deploying the system, install the SDC according to the
operating system-specific instructions in the following section. The SDCs will be
connected to the existing system.
Install the SDC on an ESX server and connect it to VxFlex OS
Install the SDC with the appropriate parameters to connect it to an existing VxFlex OS
system.
Before you begin
Ensure that you have:
lThe virtual IP address or MDM IP address of the existing system
lLogin credentials for the SDC
lThe appropriate installation packages for the SDC
lAccess to the drv_cfg tool. Contact Customer Support for access to this tool on
ESX.
The following procedure describes installing an external SDC on an ESX server using
the esxcli. Alternatively, you can install the external SDC using the vSphere plug-in.
For more information, see "Installing the SDC on ESX hosts" in the VxFlex OS
Deployment Guide .
Quick Start Guide
14 VxFlex Ready Node Quick Start Guide

Procedure
1. On the ESX on which you are installing the SDC, set the acceptance level:
esxcli --server=<SERVER_NAME> software acceptance set --
level=PartnerSupported
where
<SERVER_NAME> is the ESX on which you are installing the SDC.
2. Install the SDC:
esxcli software vib update –d “Full Path”
3. Set the IP address of the MDM:
esxcli system module parameters set -m scini -p
"IoctlIniGuidStr=<XXXXXX> IoctlMdmIPStr=<LIST_VIP_MDM_IPS>"
where
l
<LIST_VIP_MDM_IPS> is a comma-separated list of the MDM IP addresses
or the virtual IP address of the MDM
l
<XXXXXX> is the version
Results
The SDC is installed on the ESX server and is connected to VxFlex OS.
Installing SDC on a Linux server and connecting it to VxFlex OS
Install the SDC with the appropriate parameters to connect it to an existing VxFlex OS
system.
Before you begin
Ensure that you have:
lThe virtual IP address or MDM IP address of the existing system
lLogin credentials for the SDC
lThe appropriate installation packages for the SDC
The following procedure describes manually installing an external SDC on a Linux
server. On most servers (with the exception of hLinux), you can install the external
SDC using the VxFlex OS Installation Manager. For more information, see "Extending
an existing VxFlex OS system" in the VxFlex OS Deployment Guide .
Note
External SDC on RHEL 7.4 is supported on bare-metal servers only, not as guests on a
hypervisor.
Procedure
1. Install the SDC:
lRHEL/CentOS /Oracle Linux
MDM_IP=<LIST_VIP_MDM_IPS> rpm -i <SDC_PATH>.rpm
Deploying VxFlex OS in a 2-Layer Environment
Installing SDC on a Linux server and connecting it to VxFlex OS 15

lUbuntu/hLinux. These files must be extracted before use, as described in
the "Manual deployment on physical servers" section of the
VxFlex OS
Deployment Guide .
MDM_IP=<LIST_VIP_MDM_IPS> dpkg -i <SDC_PATH>.deb
lCoreOS
MDM_IP=<LIST_VIP_MDM_IPS> ./<LIST_VIP_MDM_IPS>.bsx
where
l
<LIST_VIP_MDM_IPS> is a comma-separated list of the MDM IP addresses
or the virtual IP address of the MDM
l
<SDC_PATH> is the path where the SDC installation package is located
Results
The SDC is installed on the Linux server and is connected to VxFlex OS.
Installing SDC on a Windows server and connecting it to VxFlex OS
Install the SDC with the appropriate parameters to connect it to an existing VxFlex OS
system.
Before you begin
Ensure that you have:
lThe virtual IP address or MDM IP address of the existing system
lLogin credentials for the SDC
lThe appropriate installation packages for the SDC
The following procedure describes manually installing an external SDC on a Windows
server. Alternatively, you can install the external SDC using the VxFlex OS Installation
Manager. For more information, see "Extending an existing VxFlex OS system" in the
VxFlex OS Deployment Guide .
Procedure
1. On the Windows server on which you are installing the SDC, run:
msiexec /i <SDC_PATH>.msi MDM_IP=<LIST_VIP_MDM_IPS>
where
l
<SDC_PATH> is the path where the SDC installation package is located
l
<LIST_VIP_MDM_IPS> is a comma-separated list of the MDM IP addresses
or the virtual IP address of the MDM
Results
The SDC is installed on the Windows server and is connected to VxFlex OS.
Quick Start Guide
16 VxFlex Ready Node Quick Start Guide

Enabling storage
This section describes how to use the plug-in to create and map volumes. You can
map volumes to SDCs in the same step, or you can map volumes after it has been
created.
Volumes are created from devices in a Storage Pool. The steps described here can be
performed from the VxFlex OS GUI Frontend tab, too.
Procedure
1. From the Storage Pool screen, click Actions > Create volume.
The Create Volume dialog appears.
2. Enter the following information:
lVolume name
lNumber of volumes to create
lVolume size
lVolume provisioning
lUse RAM Read Cache
3. To map the volumes to ESXs, perform the following:
a. Select Map volume to ESXs.
b. In the Select ESXs area, select the clusters or ESXs to which this volume
should be mapped.
4. Click OK.
5. Enter the password for the VxFlex OS admin user.
Results
The volume creating and mapping results are displayed.
Installing and opening the VxFlex OS GUI
You can open the VxFlex OS GUI after it is installed on your workstation.
Perform the instructions in the following topics to install and open the VxFlex OS GUI.
Install the VxFlex OS GUI
You can install the VxFlex OS GUI.
Before you begin
lEnsure that the workstation satisfies the requirements described in the "System
Requirements" section of the documentation.
lGet the installation file either from the product ISO or the Support Site.
Procedure
1. Install the VxFlex OS GUI:
lWindows:
EMC-ScaleIO-gui-2.6-<build>.X.msi
Deploying VxFlex OS in a 2-Layer Environment
Enabling storage 17

After you finish
To log in to the VxFlex OS GUI, see "Log in to the VxFlex OS GUI."
Log in to the VxFlex OS GUI
Open and log in to the VxFlex OS GUI.
Before you begin
Ensure that:
lThe VxFlex OS GUI software is installed on the workstation. To install the VxFlex
OS GUI, see "Install the VxFlex OS GUI."
lYou have these credentials (available from the administrator):
nMDM management IP address or hostname
nUsername (default: admin)
nPassword (defined during deployment)
Procedure
1. Open the VxFlex OS GUI by selecting Start > All Programs > EMC > VxFlex OS
GUI.
The initial login screen is displayed.
2. Type the IP address or hostname and click Connect.
If a certificate notice is displayed, review and accept the certificate.
If a login banner is displayed, confirm it to continue.
3. In the login screen, type the username and password, and click Login.
Results
The VxFlex OS GUI is displayed.
After you finish
Users and passwords are configured with the VxFlex OS CLI. For more information,
see the "Security" chapter of the
VxFlex OS Ready Node User Guide .
Retrieve device paths in a Linux server
The manner of retrieving device paths in a Linux-based VxFlex Ready Node server
differs, depending on the type of controller card in the node.
Proceed to the section that matches your configuration:
lRetrieve device paths in a Linux server with an HBA330 controller on page 19
lRetrieving device paths in a Linux server with an H730p/H740p controller on page
19
lRetrieving device paths in a Linux server with NVME devices configured on page
20
Quick Start Guide
18 VxFlex Ready Node Quick Start Guide

Retrieve device paths in a Linux server with an HBA330 controller
Retrieve the OS device paths in a Linux-based VxFlex Ready Node server with an
HBA330 controller.
In Linux servers, the OS device path is in the following format: /dev/sdX, where X is
a sequential letter of the alphabet in lowercase, in single or multiple format. For
example: a, b, c...z, followed by aa, ab, ac...zz.
Procedure
1. Log in to the server.
2. Display the device list:
ls –l /dev/disk/by-path/
Output similar to the following appears:
3. In the output, search for the lines starting with:
pci-0000:0#:00.0-sas-
where # is a number. (For example: 2 or 3.)
4. In the lines you just located, search for sdXat the end of the lines.
The devices paths are /dev/sdX. Use these paths when adding devices to a
VxFlex OS SDS.
Retrieving device paths in a Linux server with an H730p/H740p controller
Retrieve the OS device path for a specific virtual disk (VD) in a Linux-based VxFlex
Ready Node server with an H730p/H740p controller.
Before you begin
Ensure that you have root access to the server.
In Linux servers, the OS device path is in the format: /dev/sdX, where X is a
sequential letter of the alphabet in lowercase, in single or multiple format. For
example: a, b, c...z, followed by aa, ab, ac...zz.
Procedure
1. Log in to the server.
2. Display the VD information:
/opt/MegaRAID/perccli/perccli64 /c0/vall show
Deploying VxFlex OS in a 2-Layer Environment
Retrieve device paths in a Linux server with an HBA330 controller 19

Output similar to the following appears:
The output displays the device groups (DG) and their associated VD.
3. Match a VD to a device path:
a. Run the following command:
ls –l /dev/disk/by-path/
Output similar to the following appears:
b. In the command output, search for the line:
pci-0000:02:00.0-scsi-0:2:X:0
where X is the number assigned to the VD.
c. In the line you just located, search for the sdXat the end of the line.
The device path for the VD is /dev/sdX.
Use this path when adding devices to a VxFlex OS SDS.
Retrieving device paths in a Linux server with NVME devices configured
Retrieve the OS device paths in a Linux-based VxFlex Ready Node server with NVME
devices configured.
Before you begin
Ensure that you have root access to the server
Quick Start Guide
20 VxFlex Ready Node Quick Start Guide