Ok, so we figured out the problem. 4 of my FA Ports did not have the "Common Serial Number" flag enabled, so the RPA's were seeing multiple repository volumes presented to it, even though there was only one. I'm not sure how this happened, because it's something that's generally set by default, or at least when the array is brought online. I pulled back the zoning for those ports for the time being, but they have volumes on them that need to use RecoverPoint. So now, I'm wondering about the ramifications of enabling it while there are production volumes on it. Anyone know, or should I ask in the Symmetrix forum?  Thank you  JTB
Hello. We are having a problem with our RecoverPoint implementation. Locally I have a 4 node cluster of Physical RPA's, and my VMAX and local VNX are connected to it. Professional services did the initial set-up on it, but when they got the following error, he threw his hands up, and basically left. We've been trying to get this resolved for longer than I care to admit. But currently my RecoverPoint is not working, at all, nor has it ever worked.  ERROR: The following devices are mapped to FA ports that are not exposed to RPAs. Writes sent through these FA ports will disrupt replication. Please fix mapping configuration in storage. RPA1 Devices: 10B3, RPA2 Devices: 10B3, RPA3 Devices: 10B3, RPA4 Devices: 10B3 ; RP_XXXXXXX_PDC ; SYMM-000XXXXXXXXX  This has been checked and re-checked and re-checked again with another set of eyes. All of the zoning and mapping is correct. If I pull back the zoning, it complains that it can no longer see the Repository volume 10B3, yet when I re-enable the zoning, I always get the above error.   So far the troubleshooting items we've turned up online had us compare the number of devices that the VMAX believed it was exposing to the RP cluster, vs the number of devices the RP cluster was seeing fro the VMAX. If they were off, the fix was to reboot the RP cluster. Our's matched, but we rebooted the cluster just in case. The only other thing I found penetrating to this error had to do with a syntax error in the Symauth command, which would cause an authentication problem. We ran the Symauth command both ways, and confirmed the entries it created in the VMAX. But there was some confusion as to whether or not that was still a problem when using AD authentication vs local user accounts. We are using AD authentication.  Any assistance would be greatly appreciated.   Thank you
ERROR: The following devices are mapped to FA ports that are not exposed to 
RPAs.