XtremIO Initial Configuration

Welcome to XtremIO Initial Configuration.
Copyright ©2015 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the
information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION 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 EMC software described in this publication requires an applicable
software license. The trademarks, logos, and service marks (collectively "Trademarks") appearing in this
publication are the property of EMC Corporation and other parties. Nothing contained in this publication
should be construed as granting any license or right to use any Trademark without the prior written
permission of the party that owns the Trademark.
Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica,

Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva,
Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack,
ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model,
Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender,
Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences,
Documentum, elnput, E-Lab, EmailXaminer, EmailXtender , EMC2, EMC, EMC Centera, EMC
ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage
Administrator, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony,
Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape,
Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView,
Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap,
QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope,
SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder,
UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix
Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist, WebXtender,
xPression, xPresso, YottaYotta
Revision Date: 7/2015
Revision Number: MR-7WP-XIOINITC
Copyright 2015 EMC Corporation. All rights reserved. XtremIO Initial Configuration 1
This course covers tasks required to initially deploy a XMS into a XtremIO storage solution. The
key tasks covered in this course include, implementation and deployment of an XtremIO
Management Server, initialization and registration of an XtremIO system, configuring ESRS
options and verify proper XtremIO operations.
This module focuses on the processes and procedures required to successfully install a XtremIO
Management Server (XMS) in an XtremIO cluster environment. Once deployed, students will learn
to initialize or form the cluster and verify the cluster installation using simple xmcli commands.
Other topics are discussed such as configuring DNS and NTP, accessing the XMS, and registering
the XtremIO storage system in the Install Base using the Business Services portal and generating
log bundles. The module assumes the installation of the hardware, power and cabling have been
successfully completed.
The XtremIO Management Server is a required server used to manage the XtremIO storage
system. The XMS is preinstalled with the CLI and GUI. Also a RESTful API allows HTTP based
interface for automation, orchestration, query and provisioning capabilities. With the RESTful API,
third party applications can be used to control and fully administer the array.
The XMS can be deployed on a dedicated physical XMS server, or as a virtual machine on VMware
using an OVF template. It is not supported on Hyper-V. The XMS must access all management
ports on the X-Brick Storage Controllers, and must be accessible by any GUI/CLI client host
machine. Since all communications use standard TCP/IP connections, the XMS can be located
anywhere that satisfies these requirements.
Note with earlier XtremIO software versions (< 4.0) customers were limited to managing a single
cluster per XMS, with XtremIO v4.0, you can now manage up to eight clusters with a single XMS,
thereby minimizing the complexity and reducing the XMS footprint.
Note; Multiple cluster support is available when performing fresh install of XMS only. A single XMS
can manage clusters with different 4.x versions. The only requirement is for the managing XMS to
have the latest version of all the clusters. An XMS can manage clusters that have the same or
lower version numbers. All of this applies only to 4.0 and above versions.
XMS provides:
• Cluster health, events, and cluster performance statistics history database
• Volume management
• Data protection groups operation logic
• Stopping, starting, and restarting of the cluster
The CLI allows cluster administrators and operators to perform supported management
operations. It is pre-installed on the XMS, and can also be accessed using standard SSH
programs.
The virtual XMS VM should be provisioned on RAID protected storage however the storage should
NOT be on a XtremIO system. The OVA package from which the virtual XMS is deployed contains
VMware tools. Therefore, no VMware tools upgrade is required or recommended by EMC following
virtual XMS deployment.
Since the XMS is not in the data path, it can be disconnected from the XtremIO cluster without
affecting the I/O. An XMS failure only affects monitoring and configuration activities, such as
creating and deleting volumes. However, when using a virtual XMS topology, it is possible to take
advantage of VMware vSphere HA features to easily overcome such failures.
XtremIO with the release of version 4.0 now support Multi-cluster management where, up to
eight clusters can be managed with a single XMS. This significantly reduces the XMS footprint and
minimizes the management complexity. Clusters can be created and added to the existing XMS
over time. You can also move clusters from one XMS to another. Make sure that all the clusters
that are managed in a multi-cluster environment must be at XtremIO 4.0 version and above. Also
the XMS version must be equal to or higher than all the versions of its managed clusters. There
are some limitations involved in a multi-cluster management. First, all clusters must be located at
the same site. Second, the scalability numbers apply to all clusters, so there can only be 8192
volumes configured per XMS regardless of how many clusters being managed. Also, all the users
configured on XMS have access to all the clusters, if a particular cluster requires unique users
then it must be managed by a separate XMS.
After the Storage Controllers are configured, you need to install an XMS. If the virtual appliance
option is chosen, navigate to support.emc.com > Downloads and locate the OVA file. The OVA
image includes all the required packages for installing the XMS. Download the OVA file to your
workstation or laptop.
To deploy the OVA image, launch the appropriate vSphere interface, select File from the menu
toolbar and select “Deploy OVF Template”. Select the location from which the OVA file is located,
use the browse option if needed.
You will need to supply a machine name and select a datastore for it (you can rename it later
after it is created).
Starting with virtual XMS version (vxms-master-v3.0.1_v2.ova), the XtremIO Software

Installation and Upgrade Guide recommends to deploy the virtual XMS 900GB virtual disk using
the "thin" format. The XMS will then allocate and commit disk space on demand.
Note: Previous virtual XMS versions were configured with an 80GB virtual disk. When deployed
using "eager zero thick" formatting the virtual XMS will allocate 80GB from the datastore.
This lab covers the deployment of an OVF file using vSphere Client.
To view this demo go to the following URL:

https://edutube.emc.com/Player.aspx?vno=Lz/wpMdhabvNT07J30CJ/w==&autoplay=true
Connecting to the XMS depends on whether you are connecting via a physical or virtual XMS
deployment. For a physical deployment, connect to the server via the console using a monitor and
keyboard or via an SSH session using the Tech port. Make sure the XMS is powered up and wait
for the OS to load. After the XMS has booted, it must be configured using the Easy-Install CLI
menu. If the Tech port connection fails or the OS fails to load, re-install the physical XMS with the
appropriate Rescue Image. The Tech Ethernet port has the following pre-configured IP address:
169.254.254.1/20
The following IP settings may be used in the station connecting to the XMS:
IP 169.254.254.2
Subnet mask 255.255.240.0
If the implementation utilizes a virtual appliance for the XMS, launch the vSphere Client and
navigate to Inventory > Hosts and Clusters. Under Inventory, locate and right click on the Virtual
XMS VM and click Open Console. Users can also open a connection to the Web client application
as an alternative.
Once a virtual XMS has been deployed, open a console session to the virtual XMS by right clicking
and selecting Open Console from the vSphere Client menu.
The example displays the Install Menu when logging into the XMS and logging on as user
“xinstall” with the appropriate password.
After a successful login, you will be presented with the Easy-Install menu. From the menu, select
the appropriate action depending on the action you intend to perform. Select option “2” to check
the current XMS configuration, this option will look for duplicate management IP addresses.
Selecting option “3” displays the current configuration such as the system name, management IP
address, netmask and gateway, as well as the domain and DNS configuration. The next step is to
install the XMS software.
To configure the XMS, first check the configuration and ensure the version of the code you are
installing matches code displayed by selecting option “4” from the menu.
Selecting option “1” Configure XMS allows users to configure the XMS parameters. You will be
prompted for the XMS host name, domain name (this must be filled out with the domain name if
ESRS will be used) management IP address, netmask and gateway.
The XMS IP information will be used to set the management Ethernet port to allow communication
with the Storage Controllers. After a script checks the configuration for correctness, you will be
prompted to execute the configuration change. This process will take a few moments to
complete. Validate the configuration using xmcli commands.
This lab covers configuring the XMS management interface

https://edutube.emc.com/Player.aspx?vno=nfhiD2/Uldc6g0wttoUF8g==&autoplay=true
When performing a installation of new cluster, both the XMS and Storage Controller software
should be installed. In the case where the XMS is running an older version of the xtremapp than
the one being installed, upgrade the XMS. Before installing the XtremIO software on the cluster,
upload the software package to the XMS using winSCP or SFTP. Software can be found and loaded
from the EMC Support page (support.emc.com).
If you are adding clusters to existing clusters in a multiple cluster configuration, the XMS is
already deployed and there is no need to install it.
Access the EMC support page for XtremIO to upload the latest version of XtremIO software. The
latest Xtremapp software must be copied into the /images/ directory of the XMS. This file will be
used to install the XMS Xtremapp software on the XMS, and upgrade the Storage Controllers
Xtremapp software to the latest version.
Locate the XtremIO 4.0.x link on support.emc.com. Use WinSCP or Filezilla (any tool supporting
the SFTP protocol) and enter the IP address of the XMS, the user name xmsupload, and the
proper password, and click Login. Contact EMC Support for the proper password. You will be
presented with a view of the directories in your local machine and the /images directory on the
XMS. Verify the package version you are installing is the latest released. Also verify the MD5
checksum matches the package. Issues with installing the code typically have to do with the file
not being transferred properly to the XMS resulting in a failure of the installation.
Using WinSCP you can drag the file from the local directory to the XMS directory, or select it and
hit F5. The dialog box shown here will be displayed. Click Copy to proceed. It will take a few
moments to copy, depending on the network connection.
The slide shows a code of 4.0.x being used, ALWAYS refer to, and use the latest available code
support.emc.com
This lab covers the deployment of the xtremapp onto the XMS

https://edutube.emc.com/Player.aspx?vno=PGrWVHXrxCaHkMsCTU1c2w==&autoplay=true
Once the xtremapp file is transferred, login to the XMS using the “xinstall” user credentials. From
the Install Menu, select item 5, “Perform XMS Installation only”.
You will be prompted to enter a installation image filename, for example: “upgrade-to-4.0.0-
xxx.tar”. Once the installation completes, reboot the XMS.
After the XMS reboots, login to the XMS with the “xinstall” user credentials to proceed to installing
the storage controllers.
To install the Storage Controller software, login to the XMS using the “xinstall” user credentials.
From the Install Menu, select item 6, Install storage controllers only. You will be prompted to
enter the management storage controller IP address (recommended to use X1-SC1), enter the
expected number of bricks and installation image filename, for example: “upgrade-to-4.0.0-
xxx.tar”.
Once the installation completes, reboot the XMS.
After the XMS reboots, login to the XMS with the “xinstall” user credentials to proceed. You can
use the menu options from the menu to check and display the configuration.
This lab covers the installation of the XtremIO software on the XMS and Storage Controllers

https://edutube.emc.com/Player.aspx?vno=J1e4JHHPPFRW1tNWmh4rlQ==&autoplay=true
When performing an installation of XtremIO software in multiple cluster configurations, there are
two options, all the clusters are new, or some of the clusters and the XMS are already deployed,
and one or more clusters are being added to the existing configuration.
This slide shows the steps needed to install XtremIO software in a new multiple cluster
configuration. The steps have already been explained in previous slides for a single XMS so you
can refer to the earlier slides for details.
• Configure the XMS management interface
• Configure the first cluster
• Install the XMS software
• Install the first cluster’s storage controllers software
• Create the cluster
• Configure the next cluster with xinstall
• Install the storage controllers of the cluster
• Create the cluster
• Repeat step for the all remaining clusters
• Note the Storage Controller auto discovery process is performed for each cluster separately
This slide shows the steps needed to install XtremIO software to an already existing multiple
cluster configuration. The steps have already been explained in previous slides for a single XMS so
you can refer to the earlier slides for details.
From the xinstall menu display the XMS version
Configure the first cluster using xinstall
Install the first clusters storage controllers
Create the cluster
Repeat step for the all remaining clusters
Once the XMS and Storage Controllers are all at the proper software level, you can create the
cluster using the create-cluster CLI command. Note users must use the “tech” username for this
operation.
Open an SSH session to the XMS and log in as xmsadmin. Next, log in as the “tech” user and
issue the create-cluster command.
Required parameters include the Cluster Name, the expected number of X-Bricks, and the IP
address of X1-SC1.
Important: The cluster name must be the same as the system name entered when the Storage
Controllers and XMS were configured.
The example displays a single X-Brick cluster being created with a cluster name of “xbc2” using
storage controller 10.127.98.233.
The process will discover the configuration, establish RDMA connections to the storage controllers,
and upgrade SSD firmware. Upon completing the cluster build, it is recommended that users run
a BBUs connectivity check, select “Yes” when prompted. The BBU test runs several minutes and
displays the message “Connectivity validation passed” Powering on X1-BBU port 1” when
complete for each BBU it tests. This process continues for all four BBUs (two per SC), upon
completion the message: “Success” BBU to Storage Controllers power scheme is according to EMC
recommendations” should be displayed.
Note: Clusters that support encryption will be encrypted by default.
This lab covers the commands used to form a cluster.

https://edutube.emc.com/Player.aspx?vno=gtJRMAzrBGuVg7BH9yj9Dg==&autoplay=true
You are required to run certain CLI commands on the XMS after the successful creation of a
cluster. The commands shown in the slide should be run on all Storage Controllers and cluster
components to verify proper operation.
Look for positive output, such as healthy, active, and connected, for the various commands you
run. Negative output typically requires calling support. Refer to the XtremIO Software
Installation and Upgrade Guide.
In the example we can see the state of the “show-clusters-info” command displayed a “active and
connected”. This is normal state for a configured cluster. From this command, verify the PSNT
matches the PSNT tag shipped with the cluster.
Important: If this is not properly configured, contact EMC Support before continuing with the
cluster initialization as this will impact some of the XtremIO features.
The show-storage-controllers command should return a state of “healthy and connected”.
The “show-xenvs” command displays the state of the storage controller xenvs, they should show
a state of “active”.
This lab covers the commands used to verify proper cluster configuration.

https://edutube.emc.com/Player.aspx?vno=4ZXiI4O0MYO8kT5AnlEsKQ==&autoplay=true
During the initialization of the cluster, it is recommended that both DNS and NTP servers be
configured.
The slide shows the commands for configuration DNS and NTP, if DNS was not already setup
during the Easy-Install menu. The command can be used to setup both a primary DNS server as
shown in the slide and a secondary server by providing a “secondary=<server IP address>”
Following each command, the XMS will ping the servers, if it fails, a warning will be displayed.
This lab covers the commands used to configure DNS and NTP servers

https://edutube.emc.com/Player.aspx?vno=4E9uYGSABC4XT1k8AMDygw==&autoplay=true
The XMS requires HTTPS access, including a self-assigned certificate that matches the XMS
server name at the time of the installation or upgrade. Trying to access the XMS with a different
server name or URL may result in a certificate mismatch and prevent the GUI from loading.
If you are in a environment that supports DNS and would like to configure access to the XMS via a
URL. Log in to the XMS using the “admin” account.
Configure the DNS server using the “xmcli (admin)> modify-server-name enable-user-url
command. This allows access using the XMS server name according to the user’s URL request.
Open a browser and type in http://url. If you get a certificate warning that indicates a
mismatched server name, acknowledge it.
Verify the server certificate with the “xmcli (admin)> show-server-certificate” command and
compare the two.
Modify-server-name options;
enable-reverse-dns
enable-user-url
server-name |e.g. xms.example.com
If your environment does not support DNS and you want to access the XMS using the server
name that was defined during the installation process, or using an IP address, use the following
procedure:
Verify that your client can resolve “server name” or edit your hosts file to include an entry for
“server IP address” and “server name” (the hosts file location depends on your client operating
system). Open a browser.
If you receive a certificate warning, click on the “View Error” tab.
“View Certificates “ to see the server name to which the certificate was issued.
Open an SSH connection to the XMS and log in as xmsadmin, then log in to XMCLI as admin.
Change the server name to the name that appears in the certificate, by running the following
command: modify-server-name server-name="server_name“
Open a browser and enter https://server name/ in the URL address bar.
This lab covers the commands used to allow access the XMS.

https://edutube.emc.com/Player.aspx?vno=cCYJvZLdkDbvd2wK7kaOFA==&autoplay=true
With latest release of XtremIO code 4.0.x, users can customize the XMS login banner by adding
text. This allows users in a multi-cluster environment to easily distinguish the clusters XMS from
other XMSs.
In the example the command “modify-login-banner banner=“XMS for cluster_, cluster_2”

command has been issued via the xmcli.
Once the user logs on, the banner will be displayed in the login box.
This lab covers how to configure a new login banner.

https://edutube.emc.com/Player.aspx?vno=MVryCoxssffrGZyoTm0b5g==&autoplay=true
The XMS is a single component in the XtremIO cluster and is hence vulnerable to host and
network failures. When such failures do occur, I/O to the XtremIO storage array continue and are
not affected. Users will however, be unable to monitor or configure the XtremIO storage system.
When using a virtual XMS topology, it is possible to take advantage of vSphere HA features to
overcome these failures.
The virtual XMS should be configured to withstand the following failures:
• Power Loss or hardware malfunction to the physical host running the XMS
• Loss of network connectivity to the physical host running the XMS
The EMC Business Services Portal provides a centralized location for users to submit requests
directly to the Install Base Group. The Install Base Group provides services to update the Install
Base. The services provided include: IB Status Change, PDR Update, Move or Party Change,
Upgrade/Conversion, Debrief, Model Separation, Model Quantity Update, Microcode Update,
Secure Credentials, or Other.
The portal is accessible outside of the EMC intranet and fully replaces the Microsoft Outlook IB
Form process used in the past. You must complete the first section of the Case Creation
Application, complete the Case Details section and the Remote Connection section. When the
information is correctly input, select the “submit” button and look for the Case number to be
displayed at the top of the page. Save the page or copy the Case Number. Select the “Create
Another Case if needed.
If you are a partner, instructions on how to register an XtremIO cluster are displayed here.
https://servicepartners.emc.com/restricted. Once on the page, select “Tools and Forms”. The
Partner Notification Tool is a web form that allows partners to submit detailed information about
the installs that they have completed on EMC Products. Manual Partner Notification forms are also
available here. (Follow the link: https://www.emc.com/auth/rpage/delivery-resources.htm)
This lab covers the process to register a new cluster.

https://edutube.emc.com/Player.aspx?vno=pHipyb6SgjET3bihW13CqQ==&autoplay=true
In order to reflect current microcode versions it is required to update the Install Base records
after completing a software upgrade on the XtremIO cluster. In situations where there is no
inbound or outbound connection to the XtremIO cluster because of security restrictions, this is
very important!
To update the EMC Install Base for the XtremIO cluster follow the guidelines below:
1. From the Business Services Portal, (http://emc.force.com/BusinessServices) locate the “Post

Sales” section and select “Install Base“.
2. From the “Case Sub type” use the dropdown to select “Microcode Update”
3. Enter your EMC Email address and “Contact Email” field.
4. Select the customers region from the ”Theater” dropdown menu.
5. Select “Federal Case” if applicable.
6. In the “Subject” field, enter requesting XtremIO Microcode Update for PSNT <serial number of
the Cluster>
7. In the “Description” field, enter a string indicating your intent to update the microcode such as
“Please update the XtremIO microcode version within the EMC Install Base for XtremIO PSNT
<serial number of the cluster>.
8. In the “Product Family” menu select “All Other Families” then click the Right arrow to add the
option to the list of selected products.
9. In the “Serial#/Instance” field, enter the PSNT of the cluster for which you are requesting a
upgrade of the code.
10. In the “Microcode” field, enter the XtremIO software version to which you recently upgraded
and the select “Submit”
This lab covers the process for updating the install base after a upgrade

https://edutube.emc.com/Player.aspx?vno=JytqHNrC+HhfwH1NfIzYbQ==&autoplay=true
As part of the installation, an Initial Setup Log Bundle needs to be generated. A Log Bundle is a
compressed file that includes the XMS and Storage Controller logs and other valuable data for
debugging. To create the Log Bundle, log into the system as tech and issue the command shown.
It will take a few minutes to create the package. After the script has completed, an http link will
be displayed. You may also save the log bundle to a local directory. Copy and paste the link into
your browser and download the file in preparation for uploading the log bundle.
This lab covers the process for manually generating a log bundle

https://edutube.emc.com/Player.aspx?vno=GhZgn0udaTgEnFRTCWT6Fg==&autoplay=true
The ability to collect a Log Bundle after a failed Cluster creation enables key EMC support
personnel to better understand and resolve issues faster.
Users can log into the XMS with the xinstall credentials and select the “Collect log bundle option
from the menu (13).
Once selected, a series of questions will be presented, users can take the default answers by
hitting the “enter” key or change the defaults if needed. Since the cluster failed to create, there
will be no access to the storage controllers so users should provide the IP address of one of the
storage controllers. To remove debug info use the following command:
xmcli> remove-debug-info debug-info-id=1
Are you sure you want to remove Debug Info [1]? (Yes/No): Yes
Removed Debug Info [1]
This lab covers the process for generating a log bundle after a cluster creation failure.

https://edutube.emc.com/Player.aspx?vno=I4SbXLv4BLObO5fzOzE6fw==&autoplay=true
The slide shows the process to upload the log bundle using the FTP site, this can be done using
one of the following methods.
With FTP client, by connecting to: //ftp.xtremio.com/ and using xinstall user credentials, or as
shown in the slide, using a browser, and entering //ftp.emc.com/.
If not already selected, use the “Domain” dropdown to select “XtremIO”
Enter a username of “xinstall” and the password for the xinstall account.
Select “Login”
From the XtremIO window select the “New Directory” and give the directory a name. Typically,
this will be the customer’s name and the PSNT of the cluster.
Next, select “Add” and use the browse option to locate the tar.gz file created during the collection
process.
Once added, select “Upload” the display will show the upload progress and when complete,
displays a “Files uploaded successfully message.
Note: if the end user implements ESRS, the Initial Setup Log Bundle will be uploaded via Connect
EMC.
This lab covers the process for uploading a log bundle.

https://edutube.emc.com/Player.aspx?vno=CtapzNj3CG3g38JpyMjXyA==&autoplay=true
This module covered the process and procedures required to successfully install a XtremIO
Management Server (XMS) in an XtremIO cluster environment. We looked at how to initialize the
cluster and verify the cluster installation using simple xmcli commands. We discussed the DNS
and NTP configuration parameters and looked at how to access and register the XtremIO storage
system using the Business Service portal web site. Finally, we showed the methods for generating
log bundles and uploading them to EMC.
This module focuses on methods for performing service activities. This module will also discuss
the configuration options for ESRS and Connect Home.
EMC Secure Remote Support (ESRS) provides a secure, IP-based, distributed remote support
solution that enables command, control, and visibility of remote support access. ESRS fulfills the
requirements for authentication, authorization, and auditing with a secure, highly scalable, fault-
tolerant system. This IP-based, firewall-friendly remote access architecture initiates all
connections from the customer's site.
ESRS provides rapid remote support through two phases:
• Automated recognition and notification from the customer's site to EMC.
• Interpretation and response from EMC.
ESRS configuration options with XtremIO are ESRS Gateway (GW), ESRS Virtual Edition (VE) and
ESRS IP Client. These three configuration options provide Connect-In and Connect-Home
functionality.
Since these configuration options provide the best level of remote support to the cluster, it is
highly recommended that you select one of them when completing XMS installation. If the
customer refuses to use ESRS as a connectivity solution, you must configure the XMS to Connect-
Home only. The Connect-Home only options with XtremIO are Email or FTPS. These two options
do not provide Connect-In functionality.
When deploying ESRS and Connect-Home on the customer site there are some pre-conditions
that should be met. Additional information can be found in the EMC XtremIO Storage Array Site
Preparation Guide.
The cluster used for ESRS must have a valid PSNT configured, this PSNT is used to identify the
cluster to the ESRS.
A site name should be specified for easy cluster location and identification. This field enables EMC
to further identify the clusters location along with the PSNT. If this unavailable, enter the
customer’s name.
To connect to ESRS using a URL, DNS should be configured on the XMS.
Shown on this screen are the steps for deploying a ESRS GW or ESRS VE configuration on the
XMS. This configuration provides Connect-In and Connect-Home to and from the XMS.
First connect to the XMS using the admin account.
Execute the command “test-xms-tcp-connectivity” to confirm the XMS can successfully reach the
ESRS GW server.
For example; test-xms-tcp-connectivity port=443 server="esrs.emc.com or ip address"
Configure Connect-Home with the a connection type of ‘esrsgw’ by issuing the command
xmcli (admin) > modify-syr-notifier enable site-name=“<customer site name>”
connection-type=esrsgw esrs-gw-host=“<URL or IP address of ESRS GW or ESRS VE>”
Next, approve the registration of the cluster as an XtremIO managed device on the ESRS GW
from the ServiceLink portal.
Finally, check ESRS and Connect-Home configuration on the XMS using the “xmcli (admin) >
“test-xms-tcp-connectivity port=“port number” server=“server ip address” command.
Note at this time, XtremIO is not yet ESRS RESTful API aware. XtremIO devices can be deployed
using ESRS VE without issue, as the underlining ESRS management modules within XtremIO are
backward compatible with ESRS VE.
The slide details the precondition requirements for deploying a ESRS IP Client configuration on
XtremIO.
The customer should deploy ESRS Integration as part of the XtremIO deployment, using an IP
Client agent that will be configured on the XMS.
The customer should open HTTP connection on TCP/IP port 443/8443 outbound between the XMS
and the EMC ESRS server at https://esrs.emc.com.
The opening of the HTTPS connection can be done directly or through a proxy-server. If using a
proxy-server, ask the customer to provide the proxy-server data for:
• Proxy-server type
• Proxy-server address
• Port number used by the proxy-server
• User-name and password for the proxy-server
• Lastly, make sure the XtremIO cluster is in the EMC Install Base
Once these conditions are met, proceed and deploy the Connect-Home integration with Email
configuration as part of your XtremIO installation.
This slide displays the pre-conditions for deploying Connect-Home integration on XtremIO using
Email.
The customer should deploy connect-home integration as part of the XtremIO installation, using
Email configuration on the XMS.
The customer should open an email connection via TCP/IP port 25 between the XMS and the
customer SMTP server.
The XtremIO cluster should be in the Install Base (assigned a formal PSNT).
This slide displays the pre-conditions for deploying Connect-Home on the XMS.
The customer should deploy Connect-Home integration as part of the XtremIO installation, using
FTPS configuration on the XMS.
The customer should open an FTPS connection via TCP/IP port 989/990 between the XMS and the
EMC FTP server at corpusfep3.emc.com.
The XtremIO cluster should be in the Install Base (assigned a formal PSNT).
The slide show the steps for deploying a ESRS IP client configuration on the XMS. This
configuration provides Connect-In and Connect-Home to and from the XMS. The process involves
the loading of the Easy-Install CLI to begin the configuration.
Before installing the IP client on the XMS, you need to install the DC agent. To do so, there are
four possible installation scenarios for installing the DC agent.
Initial deployment without a proxy server - this option should be selected if the cluster has never
been installed with the IP Client previously and the XMS has direct connectivity to ESRS.
Re-deployment without a proxy-server – the IP Client needs to be re-deployed. This would be the
case when the XMS was recovered or replaced and the XMS has direct connectivity to ESRS.
Initial deployment with a proxy server – the XtremIO cluster was installed with the IP Client
previously, and the XMS has connectivity to ESRS via a proxy-server.
Re-deployment with a proxy-server – the IP Client needs to be re-deployed. This would be the
case when the XMS was recovered or replaced and the XMS has connectivity to ESRS via a proxy-
server.
If using a proxy-server, gather the following information from the customer:
• Proxy-server address
• Port number used by the proxy-server
• User-name and password for the proxy-server
To set the IP Client DC agent installation options you must first login to the XMS as ‘xinstall” and
provide the “xinstall” password. From the “xinstall” main menu, select option 7 to “Configure
ESRS IP Client Configuration”. Next, you will be asked to provide your Windows NT ID credentials.
Answer the question: “Enter selection for re-provisioning of the IP Client DC Agent” (yes/no).
Select no for initial deployment or yes for re-deployment.
Answer the question: “Enter selection of Proxy-server configuration” (yes/no). Select no if the DC
agent should be deployed without a proxy-server or yes otherwise. Note if you select the
deployment with a proxy-server, you will be asked to respond to the following questions:
• Proxy type (http or socks)
• Proxy-server IP address
• Proxy-server port number
• Proxy-server user-name (if used)
Once complete, you are ready to install the ESRS IP Client DC agent.
To start the IP Client DC Agent installation, select the option 8, “Install ESRS IP Client” from the
“xinstall” main menu. Answer “Yes” to the license EULA agreement.
When prompted, type in the RSA SecureID token number that is used for your Windows NT ID
account.
When prompted, type in the proxy-user account password if a proxy-server is used.
Once entered, the system will perform an installation of the DC agent software, launch the
required IP Client services on the XMS and register the XtremIO cluster in ESRS if this was an
initial deployment.
Note the IP Client DC Agent can be configured on a customer ESRS Policy Manager as well. See
the XtremIO Software Planning Guide for details on setting up the Policy Manager.
Set the IP Client configuration on the XMS by logging onto the XMS server as “admin”. Once at
the xmcli (admin) > prompt, issue the “xmcli (admin) > modify-syr-notifier enable site-
name=“customer site name” connection-type=ipclient.
Verify the ESRS Connect-Home on the XMS by issuing the “xmcli (admin) > show-syr-notifier”
command.
Connect-Home Integration applies to Email and FTPS only configurations. These configurations do
not provide Connect-In functionality. Note when using email connectivity, adding a footer
(disclaimer) to email messages may impact the processing of SYR notifications from the XMS. You
can avoid this by ensuring the customer’s SMTP server is configured to prevent the XMS from
adding a footer to outgoing email messages.
To deploy email configuration on the XMS, log onto the XMS as “admin”. Configure Connect-Home
with the email connection type.
xmcli (admin) > modify-syr-notifier enable site-name=“customer site name” connection-

type=email email-server=“URL or IP of SMTP server” email sender=“sender email address” email-
user=“user in SMTP server” email-password=“password in SMTP server”
Note the email-user and email-password are optional. Use these if the SMTP server requires
authentication.
Check the ESRS configuration with the “xmcli (admin) > show-syr-notifier” command.
To deploy an FTPS configuration on the XMS, log onto the XMS as “admin”.
Configure Connect-Home with the “ftps” connection type.
xmcli (admin) > modify-syr-notifier enable site-name=“customer site name” connection-

type=ftps
Check the ESRS configuration with the “xmcli (admin) > show-syr-notifier” command.
This screen displays the output of the ESRS IP Client configuration setup when using the “show-
syr-notifier” command from the XMS.
To check Connect-Home from the XMS, run the command “xmcli (admin) > send-syr-notification”.
You should receive a confirmation message of “SYR notification sent”.
Look for the “Connection status” to be “Connected” and verify the Site Name and PSNT number
are correct.
Testing Connect-Home functionality should be used to verify the XtremIO storage array is
correctly initialized by the field support specialist.
The send-syr-notification command will initiate a connect home session with a small health
snapshot attached, which takes time, so wait for verification message “SYR notification sent”.
The send-syr-notification test-event command will trigger the generation of a small XML file on
the XMS without creating a Dossier file which will be relayed home to SYR with a symptom code of
'XTR000000‘.
In addition to executing the commands, service personnel should also launch the ESRS CLIviaSSH
remote application from ServiceLink to check Connect-In functionallity to the XMS.
Note this step is only applicable for customer environments that include ESRS GW or ESRS IP
client configurations.
To locate the page for your XtremIO Cluster on ServiceLink, log on to the ServiceLink portal page
at https://esrs.emc.com/portal using your RSA SecureID credentials.
The ServiceLink Homepage includes several menu options or portlets to increase ease of use.
Portlets within the Homepage display information specific to ESRS-IP Solution devices only. The
portlets include: Browse for Devices, Devices with Alarms, Recent Devices, Devices in Watch List,
ESRS Message Board, and Helpful Hints.
Type in the clusters PSNT making sure to precede it with a “%” sign and do a search for the
name.
From the list, choose your cluster.
Make sure the “Status” displays “Good” as indicated by the green icon.
Click “Add Device to WatchList”. This will make it easier to access the device’s status screen from
the ServiceLink portal.
With ESRS it is possible to launch remote applications on a managed device.
The CLIviaSSH can be downloaded using the URL “http://10.15.54.82/esrs/putty/Putty.zip” and

providing the username of “cecuser” and a password of “Password!”
Open the package using WinZip (or 7-zip) and extract it to the C:\Users\Public\Desktops directory
on your local laptop as ServiceLink expects to find the utility there.
To launch the CLIviaSSH session, connect to ServiceLink page for the XtremIO managed device,
confirm the status shows “Good” and click on CLIviaSSH to open a remote session to the device.
Note: If the ServiceLink GUI Launch Application buttons fails, follow the instructions in the
XtremIO Software Installation and Upgrade Guide to override the default behavior.
This lab covers the commands used to configure ESRS.

https://edutube.emc.com/Player.aspx?vno=vimfVB9T4KbIhzo8wnAtEQ==&autoplay=true
This module covered the methods for configuring and testing the options for performing service
activities. The module will also discuss the configurations options for ESRS and Connect Home
and the collection of Log Bundles.
The course covered how to prepare the customer environment for an XtremIO deployment. We
covered the task of implementing and deploying an XtremIO Management Server, as well as the
initialization and verification of the cluster using a set of xmcli commands. We also looked at the
configuration of DNS and NTP and how to access the cluster once it was built. Once the cluster
was up and running, it then had to be registered in the Install Base using the EMC Business
Service Portal. The course then covered the configuration of ESRS and the methods for calling
Connect-Home.

XtremIO Initial Configuration

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

XtremIO Initial Configuration

Uploaded by

Copyright:

Available Formats

Welcome to XtremIO Initial Configuration.

Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica,

Revision Date: 7/2015

Revision Number: MR-7WP-XIOINITC

• Cluster health, events, and cluster performance statistics history database

• Data protection groups operation logic

• Stopping, starting, and restarting of the cluster

Starting with virtual XMS version (vxms-master-v3.0.1_v2.ova), the XtremIO Software

To view this demo go to the following URL:

Subnet mask 255.255.240.0

To view this demo go to the following URL:

To view this demo go to the following URL:

Once the installation completes, reboot the XMS.

To view this demo go to the following URL:

• Configure the XMS management interface

• Configure the first cluster

• Install the XMS software

• Install the first cluster’s storage controllers software

• Create the cluster

• Configure the next cluster with xinstall

• Install the storage controllers of the cluster

• Create the cluster

• Repeat step for the all remaining clusters

From the xinstall menu display the XMS version

Configure the first cluster using xinstall

Install the first clusters storage controllers

Create the cluster

Repeat step for the all remaining clusters

Note: Clusters that support encryption will be encrypted by default.

To view this demo go to the following URL:

The show-storage-controllers command should return a state of “healthy and connected”.

To view this demo go to the following URL:

To view this demo go to the following URL:

server-name |e.g. xms.example.com

If you receive a certificate warning, click on the “View Error” tab.

To view this demo go to the following URL:

In the example the command “modify-login-banner banner=“XMS for cluster_, cluster_2”

To view this demo go to the following URL:

The virtual XMS should be configured to withstand the following failures:

• Loss of network connectivity to the physical host running the XMS

To view this demo go to the following URL:

1. From the Business Services Portal, (http://emc.force.com/BusinessServices) locate the “Post

3. Enter your EMC Email address and “Contact Email” field.

4. Select the customers region from the ”Theater” dropdown menu.

5. Select “Federal Case” if applicable.

To view this demo go to the following URL:

To view this demo go to the following URL:

xmcli> remove-debug-info debug-info-id=1

Removed Debug Info [1]

To view this demo go to the following URL:

If not already selected, use the “Domain” dropdown to select “XtremIO”

To view this demo go to the following URL:

ESRS provides rapid remote support through two phases:

• Automated recognition and notification from the customer's site to EMC.

• Interpretation and response from EMC.

To connect to ESRS using a URL, DNS should be configured on the XMS.

First connect to the XMS using the admin account.

For example; test-xms-tcp-connectivity port=443 server="esrs.emc.com or ip address"

xmcli (admin) > modify-syr-notifier enable site-name=“<customer site name>”

connection-type=esrsgw esrs-gw-host=“<URL or IP address of ESRS GW or ESRS VE>”

• Port number used by the proxy-server

• User-name and password for the proxy-server

If using a proxy-server, gather the following information from the customer:

• Port number used by the proxy-server