the interaction between softwares at SMI-S point of contact is still undergoing testing.  current default recommendation is to keep them separate to avoid troubleshooting ambiguity in case issues do arise.  the impact, if any to be seen, will probably depend on the scale of environment under control, SMI-S host resources, network latencies, bandwidth, and other variables.
Hello,   Are there any guidelines about using one shared SMI-S provider for managing VMAX/VNX with VIPR SRM and VIPR Controller or does SRM and Controller each need their own dedicated SMI-S provider? It this documented anywhere?  Thanks  Francis
Shared SMI-S provider for Vipr SRM + Controller?