The Blog is Back!and I Made a Change!
Learn more featured post
March, 2014

XtremIO: The Out of the Box Experience

EDIT 1: All XtremIO bricks ship with both 8Gb FC and 10Gb iSCSI.  You do not have to specify that when ordering.

EDIT2: EMC has asked me to remove the listing of default passwords.

EDIT3: The Xbricks ship with XtremIO Software on them but it’s still highly recommended to do an install to the latest GA code on installation.

Often when customers buy a new storage array they don’t get to see the entire installation process.  Usually, it’s not a big deal as it’s a bit tricky and not that exciting.  It’s mostly tasks that are only used once and then never needed again.  But when installing our XtremIO brick in the Varrow lab I thought it might be fun to walk through the installation of that system.  If you’re like me you probably think installing new gear is fun and I thought it might be interesting to see.

Note that I’m also doing a training course for PluralSight on XtremIO that shows this process in more detail with lab videos.  So look for that coming soon.

If you are unfamiliar with XtremIO or need a refresh  you can check out the post I did here when it originally launched late last year.

Physical Installation

The physical install is very easy.  Below is the layout for a single XBrick.

As you can see, from the bottom, it goes Controller 1, disk enclosure, Controller 2, and then two battery backup units.  When you install this you need to confirm your cabling.  It’s well documented and simple…just confirm it.  I won’t go through that in detail since the documentation lays it out as simple as wiring up a BluRay player.  The Infiniband ports go to there other controller in a single brick install or to the IB switch in a multi-brick install.  The SAS connections go to the DAE.  Your brick may have both iSCSI ports and FC or it may not.  It depends on what you order.  Each brick has both 8Gb FC and 10Gb iSCSI ports.  Power from each controller goes to the battery backup units.

Ports on the Controllers
Ports on the Controllers

It’s also highly recommended you lay out the physical gear as in the diagram above.  You do name things based on where they are, such as Controller 1 being on the bottom.  Obviously Controller 1 doesn’t know if it’s on the bottom but it will help you remember which one is which later.

Also note that there is an option for a physical XMS, XtremIO Management Server.  This would be an additional 1U server that runs the management UI for all of the XBricks in your cluster.  But most people will just use the virtual XMS.  To me it’s better to use the virtual since you can just run it as a VM and protect it like you would any other VM with tools such as VMware HA.  If the XMS is down for any reason the cluster will continue to service hosts, you just can’t make any changes until it is back up.  If you completely lose the XMS and need to reinstall it’s not a big deal as you just point it to your existing cluster and it will read in all configuration information.

Here is a two-XBrick configuration.

Notice that the main difference is the addition of the two Infiniband switches in the middle.  When you have a single XBrick the two controllers are cabled to each other for the backplane, but when you go to multiple XBricks you connect them to the Infiniband switches.

 Initial Configuration

Before you being you’ll need to gather some information, namely IP addresses.  You’ll need 5 total IPs for one brick:

  • One for each controller’s management
  • One for each controller’s lights-out management port
  • One for the XMS

You’ll also want to get the default logins for the different steps.  While the install documentation for XtremIO tells you which user account to log in as in each step they do not tell you the password.  EMC has this documented in KB 000172817 on  The title of the article is “XtremIO: Default System / Cluster Access Credentials for XtremIO”.  If you are not a partner you may not have access to that article so I’ll give you the ones you need for the install here.  Not that these are current as of GA Code 2.2.3-17:


Let’s get going!  Confirm that your cabling is correct and everything is powered on.

Management and Tech Interfaces
Management and Tech Interfaces

This can be a little odd so follow along.  On the back of each controller is a Tech interface.  Think of it like a console interface but over SSH.  The Tech interface has a hardcoded IP address of (

Every controller has the same IP on the Tech interface!  Don’t connect them to a switch or you’ll get duplicate IP problems!

The idea is that you will connect your notebook directly to the Tech interface on each controller, one at a time.  These interfaces do not need to be connected once the initial configuration is done.  If you’re doing this in a lab, like me, you can connect both to a switch but only activate one port at a time.

Connect your notebook to the Tech interface on Controller 1, the one on the bottom of the stack.  Assign the IP of to your NIC.  SSH in to and login as xinstall.


Connecting to the Tech Interface
Connecting to the Tech Interface


You’ll be presented with the menu shown in the screenshot.  We’ll perform the base configuration here for each controller.  Select Option 2 – Configuration.

Going Through Option 2
Going Through Option 2


You’ll be prompted for the following information:

  • Cluster Name – Logical name you are assigning to the cluster.  Pick something that means something and remember it.
  • Brick Number – This is the number for the brick that this controller belongs to and starts at the bottom with number 1.  If you only have one brick just say 1.  This is where physical placement becomes important to helping you remember your configuration items.
  • Controller ID – The ID of the controller you are configuring.  This is either 1 or 2 (two controllers per brick).  Controller 1 is on the bottom of the brick, 2 is on top.  See note above about physical placement.
  • Management IP Information – IP address, subnet mask, and default gateway for the controller’s Management Ethernet interface.
  • KVM IP Address Information – IP address, subnet mask, and default gateway for the controller’s Lights-Out KVM interface.
Confirming Configuration
Confirming Configuration


One the script configures the controller I suggest you do Option 3 and then Option 4 to confirm the configuration is correct.  You’ll also see the configuration script assign some IPs to the interfaces ib0 and ib1.  These are the back-end Infiniband interfaces and the IPs are automatically assigned for those.  Go ahead and Exit.

Displaying the Configuration
Displaying the Configuration


Now go and do the same thing to the second controller in the brick but be sure to use the same cluster name, but different controller ID and IP information.

At this point your two (or more if you have more bricks) have their basic configuration and should being talking to each other.  The next step is to go ahead and install the XMS.

 Deploying the XMS

As I said earlier, the XtremIO Management Server (XMS) is the management front-end for your XtremIO cluster.  You have one of these per cluster, not per brick.  You have the option to order a physical XMS but most will prefer the virtual one.  The configuration is basically the same.  The only difference is that with the virtual XMS we will just do the initial configuration using the VM’s console in vCenter.  If you have the physical XMS you’ll connect to the appliances Tech port just like we did in the controller config above.  Else they are the same…in fact, if you look at the XMS VM you’ll see there are two NICs but only one is connected.  The disconnected NIC is actually the Tech interface that isn’t used by the VM.  So you can see that it’s the same software image for both.

The Physical XMS Tech interface has the same IP scheme as the controllers:

The XMS is not in the data path at all.  It’s just there for visibility and management changes.  If it goes down the cluster continues to operate just fine.  You can even delete and deploy a new XMS if you want and connect it to your cluster.  For this reason I like the virtual XMS using resiliency features like VMware HA.  By default is uses 2 vCPUs or I’d recommend VMware FT…but not yet…

To deploy the XMS you first go to and download the latest version.  This will be in OVA format.  You then deploy that OVA just as you would any other.  I’m not going to go through that here as that’s a common task.  The XMS has the following configuration:

  • 4GB of RAM
  • 2 vCPUs
  • 1 NIC (and 1 disconnected)
  • 80GB of HD space (thick provisioning recommended but not required)

Once the XMS is deployed and booted open the VM console and login as xinstall and choose Option 2 for Configuration.  You’ll be prompted for the following information:

  • Cluster Name – This is the same cluster name you used during the controller configuration
  • Management Network Information – IP address, subnet mask, and default gateway for the XMS’ management interface

When finished display the configuration and confirm that it is correct and then Exit.

Installing the XtremIO Software

The XtremIO controllers don’t actually ship with the XtremIO software on them.  They only ship with a basic Linux OS installed so you have to deploy the actual XtremIO OS to them.  Before you can do that you need to go to and download the latest version.  Once you’ve downloaded the file you need to copy that file to the XMS.  You can use this using whatever SCP tool you prefer.  You just need to copy it over and put it in the /var/lib/xms/images/ directory on the XMS.  I normally use the root account for authentication.

After you copy the XtremIO Software file to the XMS you’ll need to SSH to the XMS and login as xinstall.  From here you want to choose Option 6, Fresh Install.

Performing Fresh Install
Performing Fresh Install

You’ll be prompted for some information:

  • Management Node – Give it the management IP address of a controller in the cluster.  Doesn’t matter which one.
  • Expected Number of Bricks – How many bricks should there be?  The install wants to confirm that all controllers and bricks are talking.
  • Installation Image Filename – Give it the name of the file for the XtremIO software.  Just the filename and not the path!  Example, upgrade-to-2.2.3-17.tgz

It may seem odd that filename for the XtremIO Software is called upgrade-to-<version>.tgz but you use the same file for both new installs and upgrades.  You aren’t doing anything wrong.

Once you give it the correct information the scripts does a number of things.  You can see a lot of it in the screenshot above.  It will go out and confirm communication to all expected bricks and controllers.  If you tell it to expect 2 bricks and it only finds 2 controllers, instead of 4, it will error out.  If it does confirm everything is cabled correctly.  Little bit of advice….  I’ve found that I can get through this process so fast that I get to this point before my controllers have a chance to establish communication.  Therefore I’ll often wait 10 minutes between finishing the controller configuration and this step to give them time.

Assuming everything works fine it’ll install the software to all controllers and reboot them.  When it is done choose Exit.

Creating the Cluster

Almost done!  The last major step is to create your XtremIO cluster…meaning, bringing all of your bricks and controllers together.  To do this SSH in to the XMS and login as xmsadmin.  Oddly enough you’ll next be presented with a Username: prompt.  Login to that as tech.  This is the XMS management shell where you can execute CLI commands.

XMS CLI Interface
XMS CLI Interface


Once at the CLI enter the command:

create-cluster expected-number-of-bricks=<i> sc-mgr-host=”<j>” cluster-name=”<k>” 


  • i is the number of bricks that the creation tool should expect to see
  • j is the management IP address of any controller.   It doesn’t matter which one.
  • k is the name of the cluster that you want to use.
Cluster Creation Process
Cluster Creation Process


This process may take some time to complete…10 or 15 minutes.  Just watch it and confirm there are no errors.

Cluster Information
Cluster Information


Once the process is done I like to run a show-clusters-info command to confirm the configuration.  At this point you are basically done.  You can point a web browser to the IP address of the XMS and login as admin to make sure the XMS is monitoring and managing your cluster.



There are a few more minor steps such as configuring call home support but at this point you have a working, functional, super-fast all flash array.


While it might seem like there are a lot of steps here there really aren’t.  You’re just standing up your controllers, management station, and tying it all together.  Now that I’ve done a few of these I’ve found I can rebuild our XtremIO in the lab in under 45 minutes, start to finish.  Now that doesn’t include time for racking the gear, cabling it, configuring the network, or connecting hosts but it shows that the array itself is very easy to stand up.

Soon I’ll be posting more articles and videos on using and managing XtremIO.  It’s amazingly simple.


5 thoughts on “XtremIO: The Out of the Box Experience”

  1. You show in your two x-brick picture that 1 x-brick is on top and 2 x-brick is on the bottom. They are numbered from bottom up in a standard stacking order. Additionally, you only have one Infiniband switch pictured, when there should be two which a gap inbetween.

  2. Thanks for the detailed instructions. We are purchasing two bricks and this little tutorial helped me decide that we don’t need professional services. Much appreciated.

  3. Have just received a new 10TB XBrick and trying to use your guide to set it up, but unable to get any response from the TECH port of either controller using IP has there been any change since you wrote this guide?

  4. In XtremIO v4 you just plug a monitor and keyboard into the storage controller to configure the management IPs. One note, if the XtremApp software hasn’t been install on the storage controllers, it will have to be loaded, and I still haven’t found out how to get that done outside of an SR.

Leave a Reply

Your email address will not be published. Required fields are marked *