This post is more than 5 years old
522 Posts
0
8456
Multi-Cluster XMS Scalability Limits
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
Kumar_A
727 Posts
0
December 15th, 2015 07:00
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.
echolaughmk
522 Posts
0
December 15th, 2015 13:00
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.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 15th, 2015 14:00
so if you are managing two distinct XtremIO clusters with one XMS, you can only create 8192 volumes between the two ?
Kumar_A
727 Posts
1
December 15th, 2015 19:00
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.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 18th, 2015 03:00
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 ?
echolaughmk
522 Posts
0
December 18th, 2015 05:00
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:
4. Add the cluster to the new vXMS
I'm sure others will chime in from EMC if I am off base.
Kumar_A
727 Posts
0
December 18th, 2015 07:00
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.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
July 26th, 2017 11:00
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?
mabela
33 Posts
0
July 28th, 2017 09:00
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-Installation-and-Upgrade-Gu… under the section Installing XtremIO in multiple cluster configuration.
gvaidman
20 Posts
0
December 13th, 2017 05:00
Just wanted to note, that 2 years after this comment, these limits are still in place, as per Release Notes for 4.0.25-27 (P/N 302-004-060, REV 02, October 17, 2017). Per those release notes, the scalability numbers of the XMS have not changed since at least 4.0.0-64, circa June 2015 (that was the earliest release note available in SolVe Desktop for XtremIO 4.0, which was when multiple clusters per XMS was introduced).
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 13th, 2017 07:00
Hi,
With the soon to be released XMS 6.0.1 that manages both X1 and X2 clusters, there are XMS scalability number improvements. XMS 6.0.1 supports up to 32K volumes. For more details either contact me directly or wait for the release and review XMS 6.0.1 Release Notes.
Regards, Iris
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 13th, 2017 08:00
Iris,
How soon is "soon", i have two X2 on the floor waiting to be installed. Waiting on NVRAM replacement cards first.
Thanks
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
December 13th, 2017 22:00
X2s? Cool!! Are those your first XtremIOs?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 14th, 2017 10:00
We have had X1 for about 3 year now, good array, easy to manage.
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
December 14th, 2017 23:00
but that seems to be a trend: Unity hasn't got host groups either. That takes more time to mask LUNs to a group of hosts. I wish they would put host groups back in Unity and introduce them to XtremIO.