This post is more than 5 years old
2 Intern
•
214 Posts
0
867
August 27th, 2014 03:00
VPLEX lun SP distribution
Very quick question, is there any reason why all the luns for VPLEX would be assigned to a single SP? I have a customer which has this and I would have thought having them distributed between SPs would be preferable.
*Edit* I'm 99% sure that they do need to be distributed evenly, is there any issue with moving them via Unisphere?
Thanks,
Ed
No Events found!
garyo
89 Posts
0
August 28th, 2014 09:00
Hi Ed,
VPLEX back-end leverages ALUA for path management when talking to VNX arrays (and other supported arrays advertising ALUA).
For ideal performance, you most definitely want to balance the LUN assignments across both VNX SPs.
So long as you have the proper ALUA settings configured on the VNX for VPLEX, the trespassing when performed on the VNX should be seamless.
The VPLEX best practices guide on support.emc.com (https://support.emc.com/docu9765_Technical_Notes:_Implementation_and_Planning_Best_Practices_for_EMC_VPLEX.pdf?language=… ) states that:
When provisioning storage to VPLEX, ensure that mode 4 (ALUA) or mode 1 set
during VPLEX initiator registration prior to device presentation. Don’t try to change it
after devices are already presented.
So long as you have that set properly on the VNX, you should be fine.
Gary
Intech1
57 Posts
0
August 28th, 2014 05:00
Hi Ed,
Are you talking about the Backend paths to a VNX?
Steve
Sent from my iPhone
Intech1
57 Posts
1
August 28th, 2014 06:00
VNX should be set to spread io across both SPs. This is basic config stuff. Think of the VPlex as a server supporting multiple virtualized io loads from servers zoned to the VPlex front end ports. Spread io across both VNX sp's storage ports.
Steve
Sent from my iPhone
edhoward
2 Intern
•
214 Posts
0
August 28th, 2014 06:00
Yes that is correct.
edhoward
2 Intern
•
214 Posts
0
August 28th, 2014 08:00
I thought that would be the case, any issue with trespassing luns between the SPs while they're being managed by VPLEX?