The "Consistent LUN Violation" error you see occurs when adding the LUNs with the same LUN ID across all FAs is not possible.  For example, the LUN IDs on one of the FAs you're mapping to already has that LUN ID in use.  If you want to map the LUNs with the same masking view, you'll have to manually select the LUN IDs you wish to use.  You'll have to find LUN IDs that are not in use on all of the FAs in the masking view.  Let us know if that helps!  Karl
I'm trying to understand the process of introducing new vSphere 5.1 hosts to an initiator group that it tied to a storage group that has recoverpoint volumes inside it.  When I try to add the new hosts into the initiator group that has access to the TDEV that are enabled for recoverpoint I get an error through SMC.  Is there an official process I should when introducing new hosts to VMAX tdevs that are recoverpoint enabled.
Recoverpoint TDEVS + Initiator Group + New Hosts +VMAXe10K