Hi Keith,  1. Yes, you have to register XtremIO on a 1:1 basis and this is a VIAS limitation today.  If you weren't using VIAS then you could do XMS consolidation.  2. Due to system limitations exposed in large scale environments we have been reconsidering best practices.  We have come to the decision to create two initiator groups for VPLEX.  You would put the VPLEX backend ports FC00 and FC01 for each director into one initiator group and then put ports FC02 and FC03 in a second initiator group.  This will allow you to double the total volumes provisioned to VPLEX to 4096.  VIAS will work with this configuration by placing the newly provisioned volumes into the initiator group with the fewest number of volumes.  --Mike
Hello,  In anticipation of going to 5.5, I had a couple questions I was seeking clarification to with regards to ensuring best practices are met for XtremIO and VPLEX integration. From reading some of the guides and training manuals, the following questions don't seem to be called out so I wanted to validate:  1. The docs stats that each XtremIO is registered to the VPLEX cluster in a 1:1 fashion and that multiple XtremIO arrays have to be registered separately. This is OK, but what is the limitation around an XMS managing multiple XtremIO clusters today? Do I have to revert the XMS consolidation back to a legacy 1:1 mapping of XMS to XtremIO array if I want to have more than 1 XtremIO cluster registered with the VPLEX? It seems that way and this seems counter-productive to consolidating XMS's so I wanted to validate if there was a way to utilize a multi-cluster XMS with VIAS or if I had to go back to 1:1 and re-deploy XMS's to make them 1:1 again?  2. Is there a hard requirements to have ONLY a SINGLE IG created with all VPLEX BE ports on it registered in the XtremIO array or can VIAS operate when the VPLEX is registered using multiple IG's?  Thanks,  -Keith
VPLEX with VIAS and XtremIO