Unsolved
This post is more than 5 years old
20 Posts
1
933
June 5th, 2016 12:00
VMAX3 connectivity
I am connecting a VPLEX to a 4-engine VMAX3. Does it make sense to spread the paths (max 4 per VPLEX director) for each VPLEX engine across all 4 VMAX3 engines (4 different directors each in a different engine)? Or should I spread the paths for each VPLEX director across 2 VMAX3 engines (4 different directors in 2 engines)? I am thinking that spreading the paths on 2 VMAX3 engines is more efficient since it would reduce the traffic on the dynamic virtual matrix. I don't believe communication between directors on the same engine go over the matrix. Thoughts?
Paths on 2 engines
VPLEX Engine 1 -> VMAX3 Engine 1/2
VPLEX Engine 2 -> VMAX3 Engine 1/2
VPLEX Engine 3 -> VMAX3 Engine 3/4
VPLEX Engine 4 -> VMAX3 Engine 3/4
Paths on 4 engines
VPLEX Engine 1 -> VMAX3 Engine 1/2/3/4
VPLEX Engine 2 -> VMAX3 Engine 1/2/3/4
VPLEX Engine 3 -> VMAX3 Engine 1/2/3/4
VPLEX Engine 4 -> VMAX3 Engine 1/2/3/4
0 events found
echolaughmk
2 Intern
•
522 Posts
0
June 7th, 2016 17:00
Hi
I don't think you will have issues either way as long as you stick to the ITL limit per LUN per VPLEX director. I have done it based on application segregation before which ends up usually being more like your example for the paths on 2 engines. It would more likely be how you want to zone the hosts to the VPLEX's to cut down on intra-cluster communication at that level. I don't think there will be any issues with the VMAX3 communication