Highlighted
echolaughmk
3 Zinc

Multi-Cluster XMS Scalability Limits

Jump to solution

Hello,

Is there anything on the roadmap to allow for multiple XtremIO arrays managed by a single XMS management server to retain all of their individual array limits rather than consolidating to the single XMS limits?

Right now, it seems/states that when you manage multiple XtremIO arrays with the same XMS server, the scalability limits become global across all arrays managed by that XMS, so if I have 2 arrays managed by that XMS, I will still only ever be able to create, let's say, 8192 volumes total across all those arrays that are being managed by the single XMS. Whereas if I stick with a 1:1 XMS-to-XtremIO array management model, each array would have the limit applied to them of 8192 each.

Thanks,

-Keith

Tags (1)
Reply
1 Solution

Accepted Solutions
Highlighted
Avi3
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Thanks for the feedback Keith. We are looking at improving those scalability numbers in multiple ways. You will some of these numbers changing in our future releases. I don’t have a committed date for that change at this point of time.

View solution in original post

Reply
22 Replies
Highlighted
Avi3
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Thanks for the feedback Keith. We are looking at improving those scalability numbers in multiple ways. You will some of these numbers changing in our future releases. I don’t have a committed date for that change at this point of time.

View solution in original post

Reply
Highlighted
echolaughmk
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Thanks Avi...I will try to stay close to my account team as well. With one of my customers, I think I am going to break it back down to a 1:1 mapping of XMS to XtremIO array for the time being since RP replication is in place and I have concerns around the snap counts being global.

Reply
Highlighted
dynamox
6 Thallium

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

so if you are managing two distinct XtremIO clusters with one XMS, you can only create 8192 volumes between the two ?

Reply
Highlighted
Avi3
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

dynamox - thats correct. The maximum number of LUNs (8192 at this time) is defined at the XMS level. So, if you have two separate clusters being managed by the same XMS, you can have a maximum of 8192 LUNs across those two clusters.

Reply
Highlighted
dynamox
6 Thallium

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Avi,

Thanks.

Oh boy does XtremIO have a long way to go to catch up to your other element managers (Unisphere for VMAX and even VNX Unisphere). Let's assume someone did not know about this limitation, can they break off one cluster from an existing XMS and have it managed by another XMS ?

Reply
Highlighted
echolaughmk
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Hi Dynamox,

I have to do just this now given the VIAS limitations and after reviewing with EMC and having done something similar for a customer that lost their XMS, the answer is yes and the general process (to be performed by EMC or authorized personnel) is this:

  1. Deploy a new 4.x OVA
  2. Upgrade the OVA to the cluster version of the array you will be adding to it so they match (EMC/Partner does this)
  3. Remove the cluster from the existing multi-cluster vXMS

   4.  Add the cluster to the new vXMS

I'm sure others will chime in from EMC if I am off base.

Reply
Highlighted
Avi3
3 Zinc

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Re: “Let's assume someone did not know about this limitation, can they break off one cluster from an existing XMS and have it managed by another XMS?”.

Answer – yes. You can do that. You can always move the XtremIO from one XMS to the other. There are CLI commands (remove-cluster and add-cluster) that does exactly that.

Reply
Highlighted
stsabrmc
1 Copper

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Avi, what document outlines the use of a single XMS to manage and monitor multiple distinct XtremIO clusters and how to set this up?

IHAC that has XtremIO arrays deployed in 6 different sites across the country and would love a single pane of glass to manage and monitor them all.

Each site has between 1 and 2 distinct XtremIO single brick clusters (10TB). I am sure the ability to manage multiple XtremIO clusters with a single XMS does not correlate to the same capability that we have with VNX and Unisphere.

Any suggestions? Each XtremIO cluster behind 1 x 5-node ViPR Controller instance or ViPR SRM?

Reply
Highlighted
mabela
2 Bronze

Re: Multi-Cluster XMS Scalability Limits

Jump to solution

Hi,

You can find setup doc at https://support.emc.com/docu59666_XtremIO-4.0,-4.0.1,-4.0.2-and-4.0.4-Storage-Array-Software-Install... under the section Installing XtremIO in multiple cluster configuration.

Reply