EMC XtremIO – 4.0 Maximums

The following details the maximum values common to all four X-Brick models and the maximums applicable to each specific X-Brick model. As of XtremIO Verison 4.0 there are four types of X-Brick model to chose from:

1. 5TB Starter X-Brick
2. 10TB X-Brick
3. 20TB X-Brick
4. 40TB X-Brick

An XtremIO storage system has a Scale-Out architecture and can include a single X-Brick or a cluster of multiple XBricks(2,4,6 or 8 X-Brick clusters):
XtremIO 4 MAX

Universal Maximums
Maximum values common to all 4 X-Brick models:
• Storage Controllers per X-Brick = 2
• A single Xtremio Management Stations(XMS) can manage up to 8 clusters. XMS Multi-cluster support is a new feature of 4.0 and allows clusters running 4.x code and above to be managed by a single XMS. When an XtremIO 3.0 cluster is upgraded to 4.x then it can be added to an XMS 4.x managing multiple clusters.
• Initiators per cluster(FC or iSCSI) = 1024
If you consider a host has 2 initiators this would imply a max of 512 hosts.
• Initiators per Initiator Group = 64
If you consider a host has 2 initiators this would imply a max of 32 hosts per Initiator Group.
• Initiator Groups per cluster = 1024
• Volumes per cluster = 8192
• Number of Initiator Groups mappings per Volume = 64
• Number of Volumes mappings per Initiator Group = 2048

• Mappings per cluster (10 Volumes mapped to 10 Initiator Groups results in 100 mappings) = 16,384
Example: Maximum Mappings per cluster:
The only way we would ever reach the maximum of 16,384 mapping is if volumes were shared across multiple initiator groups. Example maximum mapping configuration:
2048volumes assigned to IG1 & IG2 = 4096 mappings
2048volumes assigned to IG3 & IG4 = 4096 mappings
2048volumes assigned to IG5 & IG6 = 4096 mappings
2048volumes assigned to IG7 & IG8 = 4096 mappings
TOTAL = 8192volumes / 16,384 mappings

• Snapshots per production Volume = 512
• Consistency Groups = 512
• Volumes per Consistency Groups = 256
• Consistency Groups per Volume = 4
• iSCSI portals per X-Brick = 16
• Physical iSCSI 10Gb/s Ethernet ports per X-Brick = 4
• iSCSI routes per cluster = 32
• Physical FC 8Gb/s ports per X-Brick = 4
• Largest block size supported = 4MB
• Maximum Volume size = 281.4TB / 256TiB (Starter X-Brick = 132TB / 120TiB)
• Maximum volumes presented to VPLEX = 4096

40TB X-Brick
25*1600 GB eMLC SSDs per X-Brick
• Number of X-Bricks per cluster = 8
• Raw Capacity = 40TB / 36.4TiB
• Usable physical capacity per X-Brick = 33.6TB / 30.55TiB (with no data reduction)
• Maximum logical capacity per X-Brick = 201.6TB / 183.3TiB (with the use of data reduction techniques such as Thin Provisioning, inline compression and inline deduplication. As you can see these figures are based on a 6:1 ratio (33.6TB * 6 = 201.6TB) and will vary depending on types of data sets residing on XtremIO.)

20TB X-Brick
25*800 GB eMLC SSDs per X-Brick
• Number of X-Bricks per cluster = 8
• Raw Capacity = 20TB / 18.2TiB
• Usable physical capacity per X-Brick = 16.7TB / 15.2TiB (with no data reduction)
• Maximum logical capacity per X-Brick = 100.2TB / 91.2TiB (with the use of data reduction techniques based on a 6:1 ratio (16.7TB * 6 = 100.2TB))

10TB X-Brick
25*800 GB eMLC SSDs per X-Brick
• Number of X-Bricks per cluster = 4
• Raw Capacity = 10TB / 9.1TiB
• Usable physical capacity per X-Brick = 8.33TB / 7.6TiB (with no data reduction)
• Maximum logical capacity per X-Brick = 50TB / 45.5TiB (with the use of data reduction techniques based on a 6:1 ratio (8.33TB * 6 = 50TB))

5TB Starter X-Brick
13*400 GB eMLC SSDs
A starter X-Brick has 13 eMLC SSDs(a standard X-Brick has 25 eMLC SSDs), a starter X-Brick can be expanded to a standard 10TB X-Brick by adding 12 SSDs. Once the starter X-Brick has been expanded to a 10TB X-Brick then it may be scaled-out as per a std. 10TB X-Brick to two and four X-Brick clusters.
• Number of X-Bricks per cluster = 1
• Raw Capacity = 5.2TB / 4.7TiB
• Usable physical capacity per X-Brick = 3.6TB / 3.3TiB (with no data reduction)
• Maximum logical capacity per X-Brick = 21.5TB / 19.5TiB (with the use of data reduction techniques based on a 6:1 ratio (3.6TB * 6 = 21.5TB))

Note: 1 Kilobyte = 1000 bytes whereas 1 Kibibyte = 1024 bytes ( 1TB = 1000(bytes)4 & 1TiB = 1024(bytes)4)

PERFORMANCE
Referenced from the following data sheet: EMC XTREMIO 4.0 SYSTEM SPECIFICATIONS
XtremIO 4 MAX2

12 thoughts on “EMC XtremIO – 4.0 Maximums

  1. Hi Dave,

    Excellent post!

    Another useful one may be max clusters per XMS is now 8 instead of 1.

    Keep them coming 🙂

    Thanks
    Victor

  2. HI David,

    Thanks for the Post 🙂

    I have question on DATA AT REST ENCRYPTION, is it enabled as default feature in 4.0 Maximums?

    Regards,
    Ravi Alluri

    • Hi Ravi,

      As David mentioned you choose during install. The SED (self encrypting drives) are used in encryption supported Array (you may have to check is the array has SED’s or not). You can find that in Powerlink or from Solve desktop.
      A unique Data Encryption Key (DEK) is created during the drive manufacturing process. The key does not leave the drive at any time.
      The SED’s are in unlocked state. In unlocked drives the data is always encrypted, but the DEK is
      always decrypted and no authentication is required
      In order to ensure that only authorized hosts can access the data on the SED, the DEK is protected by an Authentication Key (AK). Without this key the DEK is encrypted and cannot be used to encrypt or decrypt data. Locking the drive is made possible by changing the default drive’s AK to a new

      In short the AK is changed from default to a new value when you enable encryption by running command — modify-clusters-configuration encryptioncommand=”switch-mode” encryption-mode=”self”.

      This AK is generated for each disk individually. Disabling and enabling encryption need the cluster not to be servicing any IO. I hope this clarifies.

  3. @DavidCRing is there a cmd line to check the XMS type physical or Virtual in CLI without collecting the Log Bundle #xtremio #xms #emc

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s